Minecraft:Java Edition untranslated keys: Difference between revisions
From SAS Gaming Wiki
More actions
Sync: updated from Minecraft |
Sync: updated from Minecraft |
||
| Line 29: | Line 29: | ||
| | | | ||
| {{bug|MC-310991}} | | {{bug|MC-310991}} | ||
|- | |- | ||
| {{code|key.keyboard.155}} | | {{code|key.keyboard.155}} | ||
| Line 117: | Line 45: | ||
| | | | ||
| {{bug|MC-311035}} | | {{bug|MC-311035}} | ||
|- | |- | ||
| {{code|key.keyboard.257}} | | {{code|key.keyboard.257}} | ||
Revision as of 11:34, 18 August 2026
Template:Exclusive Template:In development This page is a list of keyboard keys that can have game controls bound to them Template:In, but do not have a name or ID (i.e. non-placeholder Minecraft:key codes) properly assigned to them.
Recognised as distinct
For Linux, the correspondence between evdev codes and SDL3 codes is mostly dictated by this document. However, there are some exceptions:Template:Info needed
- Template:Code should map to Template:Code, but instead is recognised as Template:Code<ref>Template:Bug</ref>
- Template:Code and unnamed key 195 both map to Template:Code, despite the former being defined as mapping to Template:Code and the latter being left as "Unknown"<ref>Template:Bug</ref>
- Template:Code and Template:Code should both map to Template:Code, but only the former appears to do this, with the latter instead binding to "Not Bound"<ref>Template:Bug</ref>
- Template:Code should map to Template:Code, but instead binds to Template:Code, resulting in a conflict with Template:Code<ref>Template:Bug</ref>
Does not bind correctly
Several controls, rather than being bound to distinct controls, will instead display "Not Bound" rather than being assigned a proper, unique key bind.