When beacon power level is changed, the GUI doesn't update until closed and reopened
The bug
An open beacon GUI does not update whenever beacon power level or active state changes.
How to reproduce
- Place this
structure file in .minecraft\saves\<world_name>\generated\minecraft\structures. - Go in that world and run:
/setblock ~ ~ ~ structure_block{mode:"LOAD",name:"mc-1429",showboundingbox:1} - Get an iron ingot, stand on the pressure plate and put the iron in the beacon.
→
After the beacon is deactived, you can still select an effect
Created Issue:
Beacon GUI
Beacon GUI does not come up right away when you place the block down. You have to either wait for the beam to come out or right click it again.
Environment
Windows 7 32bit, Java 7 Update 9
is duplicated by
relates to
is duplicated by
Beacon GUI does not come up right away when you place the block down. You have to either wait for the beam to come out or right click it again.
When beacon power level is changed, the GUI doesn't update until closed and reopened.
Beacon GUIWhen beacon power level is changed, the GUI doesn't update until closed and reopened / Beacons don't power up straight away when placed
When beacon power level is changed, the GUI doesn't update until closed and reopened/ Beacons don't power up straight away when placed
Beacon GUI does notcome up right away when you place the block down. You have to either wait for the beam to come out or right click it again.When beacon power level is changed, the GUI doesn't update until closed and reopened.
An open beacon GUI does not update whenever beacon power level or active state changes.
The bug
An open beacon GUI does not update whenever beacon power level or active state changes.
How to reproduce
- Place this
structure file in .minecraft\saves\<world_name>\generated\minecraft\structures.
- Go in that world and run:
/setblock ~ ~ ~ structure_block{mode:"LOAD",name:"mc-1429",showboundingbox:1}- Get an iron ingot, stand on the pressure plate and put the iron in the beacon.
→After the beacon is deactived, you can still select an effect
relates to
relates to
MC-100233
[Mod] Chandler wants to marry [Mod] LateLag
DrownedZombie wants to marry Fabian Röling
[~Awesoman3000] wants to marry [Mojang] Adrian Östergård
[Mod] markderickson wants to marry [Mod] Anthony Cicinelli
[Mod] violine1101 wants to marry Dmitry Konev
Galaxy_2Alex wants to marry bugsbugsbugs
[Mod] Avoma wants to marry SlicedBlock
[Mojang] slicedlime wants to marry [Mod] SPGoding
W_V wants to marry [Mod] EVGENSYPERPRO
[Mod] tryashtar wants to marry [Mod] Neko
[Helper] Jack McKalling wants to marry [Mod] redstonehelper
[Mod] Sonicwave wants to marry [Mod] Ezekiel (ezfe).
Ok, prepare for something... Could please a mod mark the versions for every bug I tell you here? That would be nice.
I have a world set up for fast bug testing. That means that going into each bug report and saying "Confirmed for 1.10.1" is way more work than actually testing it. So I want to confirm for 1.10.1 with this comment:
MC-4, MC-9, MC-14, MC-87, MC-112, MC-201, MC-212, MC-234, MC-258, MC-460, MC-577, MC-667, MC-679, MC-696, MC-697, MC-849, MC-868, MC-926, MC-957, MC-997, MC-1040, MC-1127, MC-1133, MC-1168, MC-1207, MC-1218, MC-1297, MC-1390, MC-1429, MC-1530, MC-1531, MC-1538, MC-1541, MC-1555, MC-1578, MC-1673, MC-1685, MC-1691, MC-1981 and MC-2023.
All of these are tested in 1.10.1. For some others I have additional information:
MC-711 not testable with my setup because of a crash that's new in 1.10.1.
MC-779: At least some appear outside, didn't test all. What's sure is that no general solution got introduced.
Confirmed MC-1511 for stone button, lever, torch, redstone dust, normal rail, end rod, tripwire hook, ladder and flower pot. Others are untested.
Confirmed MC-1874 for chest, brewing stand, enchanting table and flower pot. Others are untested. It's apparent that there isn't a general solution here either.

Confirmed.
Could not reproduce in 13w04a creative or survival — as soon as I've placed a beacon, I can right-click it and get the GUI regardless of whether the beam is active or a pyramid is underneath.
Yes, but before the beam kicks in there are the effects missing in the GUI.
The beacon block checks only every few seconds (I assume for performance reasions), if it is placed on a legit pyramid and what kind of pyramid, and depending on that result the icons for the effects are shown.
Possible fix: The beacon block should do an additional check for legit pyramid immideatly after placing.
The interface does not appear right regardless in 14w02c, even if you wait for beam to appear or replace the beacon. See bug
MC-44907Still a concern in 1.7.5 and 14w10c
Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
The described behavior still occurs in 14w30c.
Still in 1.8
Confirmed in 1.8.3. Could someone update the description to something clearer, like "When beacon power level is changed, the GUI doesn't update until closed and reopened."?
Confirmed for
Confirmed for
Still a problem in 16w02a
WAI, see
MC-78446. Note that beacons now do power up straight away when placed.Are you sure that this is WAI? The reason is apparently a different one as the GUI will never update until you reopen it.
Oh, I misread the report. Reopening.
I placed a beacon in 1.10 (just on normal ground) and quickly clicked on it. The GUI showed no choices (effects). Does that mean it's confirmed for 1.10?
Confirmed for 1.10.1.
In 1.16.1 and 20w29a.