MC-67727Beacons in Nether need clear path to "sky"
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue (MC-4405) regarding the need to clear a path to bedrock, which is still true, but is now even worse, as you need to also clear the bedrock itself (i.e. in creative mode).
Environment
MacOS X
Linked Issues
is duplicated by1
Created Issue:
Beacons in Nether need clear path to "sky"
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue regarding the need to clear a path to bedrock, which was still true until recently, but is not even worse, as you need to also clear the bedrock (i.e. in creative mode).
Environment
MacOS X
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue regarding the need to clear a path to bedrock, which was still true until recently, but is no
teven worse, as you need to also clear the bedrock (i.e. in creative mode).In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue regarding the need to clear a path to bedrock, which was still true until recently, but is now even worse, as you need to also clear the bedrock (i.e. in creative mode).
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue regarding the need to clear a path to bedrock, which was still true until recently, but is now even worse, as you need to also clear the bedrock (i.e. in creative mode).
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue (
MC-4405) regarding the need to clear a path to bedrock, which was still true until recently, but is now even worse, as you need to also clear the bedrock (i.e. in creative mode).
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue (
MC-4405) regarding the need to clear a path to bedrock, whichwas still trueuntil recently, but is now even worse, as you need to also clear the bedrock (i.e. in creative mode).In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue (
MC-4405) regarding the need to clear a path to bedrock, which is still true, but is now even worse, as you need to also clear the bedrock (i.e. in creative mode).
In 14w33c, I noticed that my nether beacons stopped working, however if I open up the bedrock, they come on. Possibly related to the recent changes regarding interaction with stained glass and other light-permitting blocks. I see there is an OLD issue (
MC-4405) regarding the need to clear a path to bedrock, which is still true, but is now even worse, as you need to also clear the bedrock itself (i.e. in creative mode).
relates to
is duplicated by
Actually, to be clear, I was ranting about you pointlessly pointing out that there is no official documentation for Minecraft. But, I'm over it now 😊 .
This issue is a duplicate of MC-67727. It has been linked to the original bugreport.
Please search before reporting any bugs, as it's likely that one exists already.
Dupe ofMC-4405MC-4405is related, but not a dupe.MC-4405is very old, and refers to needing to clear a path to the bedrock. Now, however, you actually need to clear the bedrock as well, for the beacon(s) to work.This might be OK behavior, except that it means you cannot create working beacons in the Nether without creative mode. It is not the documented behavior, though, which only says you need to have only "naturally placed" blocks above the beacon. The old bug meant you had to clear away all the non-bedrock, which was possible, though not particularly easy, in survival.
Yes. It is still the same. You have to break all the way through the bedrock to clear a path above the beacon before it will activate. I created a new beacon, just to be sure, but it also deactivates if the bedrock is replaced after breaking through, so It doesn't matter if it is "original" bedrock, or placed by the player. Any non -transparent material above the beacon deactivates it in the nether, as in the overworld, which prevents beacons from being used in the nether, without destroying bedrock.
As I mentioned, It might be OK that you can't use beacons in the Nether (without cheating), since they need a clear path above (in the Overworld and End), and there's no clear path in the Nether, but the documentation should be changed if this is the desired operational mode for beacons, particularly since it is even more strictly true since 1.8.
Still.. it looks like I'm no the only one whose beacons stopped working. It would be nice if it was fixed so we don't have to cheat, and other adventurers can beef themselves up with beacon-power in the nether.
Confirmed for 1.8.2-pre1 in Win7x64. Beacons need a revamp, imo. The whole 'path to sky' requirement seems unnecessary. Overhead path requirements should be more or less entirely removed in the Nether, in any case.
If by "documented behavior" you're referring to the wiki, note (1) that's not official documentation by any stretch of the imagination and (2) the whole bit there about "naturally generated" blocks being allowed seems likely to have been poorly describing the effect of bugs in the initialization of the chunk's "HeightMap" data (as recently as 1.7.10 it would be set to not include the topmost bedrock layer, and it seems to have been even worse in some 1.4.2 beta versions).
I've updated the unofficial documentation to coincide with the current behavior, and referenced this ticket.
Also, it seems like this (
MC-73406) is the same or strongly related, and a bit more root-cause-y, perhaps.I have no idea why you're ranting about the fact that the wiki isn't official documentation.
MC-73406is an actual bug where the beacon basically ignores the top half of the dimension. When it comes down to it, this is a feature request that the behavior of beacons should change, at least in the Nether.This sounds more like a feature request than a bug to me. Beacons require an unobstructed view of the sky to function; this ticket seems to be asking for that to be changed to allow them to function anywhere in the Nether. The only bug I see is that they ever worked in the Nether at all.
Technically, is a regression from previous behavior, because beacons activated in the Nether without cheats/creative prior to 1.8, and now do not. One could say it was a bug that they activated before, but I'm more inclined to think that they should be able to activate in all 3 dimensions of Minecraft, and they did in fact activate prior to 1.8.
Should be co-fixed with
MC-4405