The bug
MC-300695 and MC-300718 were only fixed for keybord buttons, the bug still occurs when you assign the associated key to a mouse button.
It doesn’t happen in 1.21.8 or in versions prior to 25w32a.
How to reproduce
Just assign the Sprint key, the Sneak key, the Attack/Destroy key or even the Use Item/Place Block key to a mouse button
Got to “Options”, “Controls” and put these actions to “Toggle”
Press the assigned button to start the toggle
Open the inventory
→ ❌ the toggle stat reset
Linked issues
is duplicated by 10
Attachments
Comments 5
So I’m requesting a review for this ticket. Normally, the Toggle Stat allows you to continue to perform actions even when the associated key is no longer pressed. Recently, a bug appeared in recent snapshots that broke this functionality if we open an interface (like for sprinting or sneaking). This has been fixed for keys associated with a keyboard but it’s still the case for keys associated with a mouse. I don't understand why the resolution is WAI because it breaks the principe of the “Toggle” since this was not the case in versions before 25w32a. Also why it should be different if the concerned key is associated to a mouse button ?
Thank you for reading this comment and I hope that the resolution while be reverted.
We closed this ticket as Working as Intended because the toggle version of a keymapping should behave the same way as if you’d hold the key with the toggle option is set to hold.
If you continuously hold a mouse button and open a screen, it will not continue to be held once the screen is closed. This is, however, not the case for keyboard mappings. Hence the separation
I think the sprint and sneak state part of this should be reconsidered in a future update.
It makes sense to have the hold and toggle options act the same way when exiting screens, but there shouldn't be different behaviour for those using mouse keys for toggle sprint/sneak.
If you continuously hold a mouse button and open a screen, it will not continue to be held once the screen is closed. This is, however, not the case for keyboard mappings. Hence the separation
This is not true. Your reasoning is built on a false pretense.
On 1.21.11, contrary to what you describe, all actions set to “Hold” do not reactivate upon exiting a GUI, even if bound to a keyboard button. When set “Toggle”, Attack/Destroy and Use Item/Place Block never reactivate, while Sneak and Sprint only reactivate if bound to a keyboard button, but not if bound to a mouse button. Do you see the discrepancy now?
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki