Thank you so much Slappy Sloth.
I believe all these issues are related to each other and thought it would be easier for them to just fix all of it in one go. But I guess they think otherwise.
Maybe you could link to the other tickets here? I don't see them.
Steps to Reproduce:
Go to controls>keybinds, set hotbar load or save to V
Observed Results:
It becomes yellow
Expected Results:
It should not become yellow
Just pressing V doesn't do anything and F3 + V and V + 1 are not going to interfere. No need to show a conflict.
FYI, I press just F3, however I have it set up so hitboxes show up when pressing just F3. just wanted to clarify.
Can we reopen the bug as I am using the default launcher and got the same issue:
However, it was just while pressing F3 for the first time on the snapshot. not specifically debug hitboxes.
Why do you need a video? It's literally 2 steps.
Spawn a mob. Check their data. A Mojang employee has personally already confirmed the bug and asked me to report it. How much more do you need?
`/data get entity @n[type=ghast]` returns the data seen in screenshot.
That's the bug.
I am unable to put a video on here.
For your exquisite request I shall formalize the description for thee. Even tho it already was quite clear…
Description updated to be more Formal. (originally written on mobile) Please re-open.
Yes. also happens in 1.21.1 and 1.20.6 and 1.19.4
I only noticed this now though.
Weird that it only happens when F3 is open and V-sync + more than V-sync FPS is set.
Idk what I could change about my hardware settings. the drivers are already up to date. Maybe the latest drivers have a bug?
My last driver update: https://www.nvidia.com/en-us/drivers/details/230853/
You see, I tried disabling my NVIDIA and running Minecraft on integrated. but it simply refuses to launch giving just a 'error ding' sound when I try to.
I tried going through the windows settings and choosing "Power saving" for the MC launcher, the javaw.exe (runtime-delta) and it still launched with the dedicated card. You sure MC latest version supports integrated?
Is there any additional information I can provide to help pinpoint the source of the bug? like any hardware specs?
Confirmed also for 1.21
As can be seen the output from `/loot` is correct using the item_name.
the output from `/say` is incorrect.
Item:
minecraft:diamond_pickaxe[minecraft:item_name='"Diamond Hammer"']Added a step by step reproduction
I don't think you need any steps tbf. You just need to observe the item tooltip and associated data with commands.
I added them regardless.
Datapack has been attached. for convenience sake.
Additionally. Note that it doesn't just include F3+F4, F3+N, /gamemode command by the host self in chat.
But also, if any other player changes the host’s game mode, a datapack changes the host's game mode.
I haven't tested this, but, probably also if the host dies in a hardcore LAN world and is thus changed gamemode to spectator. If someone could confirm this?
It seems ANY change of the host’s gamemode regardless of method, will adjust the defaultgamemode of the world.