To be precise, before following the above commands, do:
Set world to “Peaceful”
Run the second command above (This may not be necessary)
Set the world to “Normal”
Run the second command above again
The bee will do nothing.
OK, now I know what was missing: If I set the world to “Peaceful”, run the second command, of course nothing happens. BUT then I set it “Normal” and still nothing happens. I had done that in the world before running into the problem, but didn’t know it was connected.
Yes, this is the solution I’d suggest as well. I’m asking Mojang to do what you suggest to restore the status quo, because red sand has been allowed for a long time.
I don’t see this in 25w43a.
The golem: 12 100 45
Closest banner: -42 101 -22
30-40 blocks away there are many, but nothing closer than that.
I don’t understand what you’re saying/asking
Shouldn’t the mannequin’s head move in sync with the body while in the boat, and face the direction any entity would initially after leaving a boat, with the head and body in sync? (or is that what you’re saying and I’m just not getting it?)
By “ESC never worked”, I mean it never got the popped up UI dialog to release the focus, or maybe more precisely it just grabbed it right back.
I had this same issue, which was resolved as a duplicate of this. However, this seems to be stuck on the creator responding, so the bug isn’t being fixed. I uploaded a video in my bug: MC-301287. Is that enough? I can also verify the bug still exists in 25w35a, which should also cover reinstalling. I’m using MacOS. For me the ESC never worked. I had modified “use” to be a key. Minecraft works as intended if the default binding for “use” is used.
Sorry, I thought lantern was also renamed, not just chain. Please close this, since I can’t (can I?)
No, Use Item is on “Hold”.
However, I have bound it to a keyboard shortcut (“<option>” on my Mac). And when I reset that binding and use the mouse (actually a special click on my trackpad) the behavior goes away.
This is the setting I’ve had forever, at least as far back as 1.8. However, this certainly could be why others are not seeing it (which I presume they aren’t). And this did not happen as recently as 25w33a.
Here it is. Are you not seeing this?
I just copied my details into the older, closed bug. If I had done that originally, would that have re-opened that bug?
I just tested it on pre-release 3 and it’s working now, so this is fixed.
… by which I mean you can reproduce it with:
/dialog show @a minecraft:custom_options
and doing the actions above: Click the button, dismiss the warning with “back”, look at the button.
FWIW, it happens in all dialogs afaict.
can confirm in 1.21.11