[MC-2353] Beacon problems Created: 05/Nov/12  Updated: 12/Jan/14  Resolved: 06/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: John Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

OSX 10.8.1


Attachments: PNG File 2012-11-05_11.45.36.png     PNG File 2012-11-05_11.45.48.png    
Issue Links:
Duplicate
duplicates MC-586 Beacon light does not travel through ... Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

The bug:
I am not exactly sure what could cause this bug, but their seems to be a bug with beacon blocks.
It affects only one of my worlds, I use no mods/texture packs. So I laid down a pyramid of diamond blocks(I have tried this with iron,gold,diamond,and lapis) and then laid down my beacon block, I opened the GUI and put one diamond ingot in, and nothing. It appears to not realize that their is a pyramid under it. The beacon works on all my worlds except this world. I have tried force updating. I have spent some time online trying to find similar cases, with no luck. I am sorry about any bad grammar/spelling, but my natural language is not english.
Edit: I do not have any solid blocks above it. Their is some water 20 blocks above it, but that is not considered a solid block, is it?



 Comments   
Comment by Tokes [ 12/Jan/14 ]

It's because the water reduces the light level. That's also why lava doesn't block it.

Comment by John [ 07/Nov/12 ]

Removing the water seemed to let the beacon operate, hopefully in a future update this will not be the case with water.
Thanks Anon Ymus for noting that Lapis does not work for the beacons pyramid.

Comment by Anon Ymus [ 06/Nov/12 ]

Lapis does not work for pyramid construction. I think you mean Emerald.

Comment by Do [ 06/Nov/12 ]

Looks like the same issue as MC-586

Comment by [Mod] CubeTheThird [ 06/Nov/12 ]

If that water is taken away, does it function as it should?

Generated at Sun Jan 12 11:57:34 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.