I was trying to mine obsidian, I had my beacon set to Speed II so I went and set the beacon to Haste II using an emerald and went mining. When I came back, I tried to set the beacon back to Speed II but I couldn't. I realized that in the UI, the beacon was still set to Speed II, but I had the Haste II effect applied instead, so it wouldn't let me change the effect because it was "already set" to Speed II when it was actually giving me Haste II.
What I expected to happen was:
When I set the beacon to Haste II, the UI should've updated properly to that effect, and therefore, the beacon should let me set it back to Speed II.
What actually happened was:
When I set the beacon to Haste II, Speed II was still selected in the UI, even though it was giving me the Haste II effect, and it wouldn't let me set it back to Speed II because I can't set the beacon to the already selected effect in the UI.
Steps to Reproduce:
Open a level 1+ beacon
Set it to any effect using any material
You'll notice how the beacon gives you the effect you just set, but in the UI no effects are selected, because of this, you can "change" the effect that the beacon is giving you to that same effect, wasting the material you put.
In my case it happened a little bit different because I had the beacon already set to Speed II before I updated my world to the first affected version (1.16.0.2).
I can set my beacon to any effect, except Speed II, because in the UI, Speed II is selected and the UI doesn't update properly. Therefore, Speed II will always be selected and you can't change the beacon to the already selected effect, which should be the same effect that the beacon is giving you, but it isn't.
As you can see in the screenshots below, it's giving me Haste II, even though in the UI no effects are selected.
Linked issues
is duplicated by 1
Attachments
Comments 3
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please make sure the ticket description contains the following information:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
It's still a bug in 1.18.10.
What happens is that whenever you open a beacon and set it to an effect, the UI doesn't update properly, even though it gives you that effect.
Due to that bug, you can select Haste I on a level 1 beacon, then change it to Haste I again using a valid item, and again, and again, and so on... just wasting materials. This exact situation isn't a big deal, since you can just not select the same effect to not waste materials.
However, the real problem comes when you load a world that was created in a version prior to the bug that has a beacon already set to an effect, Speed II for example. When you try to change the effect to Haste II on a newer version affected by the bug, you perfectly can, even though in the UI Speed II will still be selected, but when you try to change it back to Speed II, you just can't, since the UI thinks it's still on Speed II.
@Amanda Davidson:
Your comment has been removed because it contains profanity, it's irrelevant to this ticket, and it does not add helpful information to the report.
The issue you reported yesterday was about the color of the beacon beam. This report is about the status effects given by the beacon and its GUI. There is no connection between these issues. Your report was resolved Invalid because you reported it to the wrong project (Java) for your edition of the game (Bedrock). You are welcome to make a new report for your issue in the Bedrock project.