pistonpoek

I had some time to properly test and it seems that the issue still persists in the last two versions. The 26.3 Pre-Release 1 change did partially fix unbound key mappings being triggered by unknown key events, but it did so only in various screens.

For example in snapshot 10, setting the Advancements key bind to Not Bound and pressing and unknown key, such as Fn + Z caused it to open the advancements menu and pressing it again would close it again. In 26.3 Pre-Release 1 it will also open it, but closing it does not happen. So unbound key mappings are still triggered by a key press from an unknown key, but only some actions are now activated by that key trigger.

On a technical note, the clickCount and isDown values are still updated for an unbound key mapping. Causing calls on a key mapping like consumeClick and isDown to activate actions like opening the advancement menu or smooth camera, which should not occur. In various screens the matches method of a key mapping is used to check if a key event should trigger an action, which now correctly does not trigger as matches now returns false for unbound key mappings.

Pre-Release 1 changed key mappings in the code to not match any key when it is set to Not Bound, so it will not be triggered. This changes solves this ticket and others that just mention the triggering of not bound key mappings by a specific key.

Yes, also ticket MC-311424 and MC-310522 (Which seems to have gotten resolved last friday for the coming update 26.3 Pre-Release 1). I think these and possibly other tickets mainly describe two distinct issues. With MC-310108 having a focus on the degradation of the amount of possible key binds and MC-310522 mentioning that an unknown key triggers key mappings that are set to Not Bound.

Also affects version 26.3 Snapshot 10.

From what I found, the issue is more generic than the keys Fn + Esc. When a unknown key is pressed it will trigger all key mappings for key binds that are Not Bound. By default only the key bind Toggle Cinematic Camera is set to Not Bound. So if you set for example the Jump key bind to Not Bound, then pressing Fn + Z in game causes the player to jump and toggle cinematic camera.

More technically when a key event with key org.lwjgl.sdl.SDLScancode.SDL_SCANCODE_UNKNOWN (int 0) is triggered the client will update the key mapping for the matching unknown key. Then all key mappings that are specified for the unknown key, which are those that display as Not Bound, will perform their action.

There may be a check missing to not trigger the key mapping on an key event that is unknown or maybe the key binds that are unbound should not be set to the unknown key event.
As a side note, a setting in the Mouse Settings control options to manually toggle the cinematic camera and to see its current value might be valuable.

For players stuck on cinematic camera, either press the same button(s) again that caused the issue or configure the key bind to toggle it. Configuring the key bind can be done by going to Options (Esc) / Controls… / Key Binds… and then set Toggle Cinematic Camera to a key by clicking the Not Bound button and pressing an unused key. Close the options menu (Esc) and press the configured key.

When searching for a matching bug report there were also reports mentioning a right shift button on a specific locale, so they may partially or in whole overlap with this bug report.