Snapshot 7 introduced a separate ID for the numeric keypad comma key, but actually trying to use this key will result in a control being bound to the dot/decimal point/period key instead, which judging by this it is not supposed to do.
The SDL3 Linux key codes list (https://github.com/libsdl-org/SDL/blob/855cbec702f246661ff00a0bce9e0683012840c2/src/events/scancodes_linux.h ) indicate that it is, indeed, separate from the standard decimal point key (dot is 83 whereas comma is 121), so I don’t know why it maps to the dot key. Perhaps this is a keyboard layout issue, but that seems unlikely since I presume the game checks for the key, not the output character.
Attachments
Comments 4
Thank you for your report!
After consideration, the issue is being closed as Won't Fix.
Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
After doing some further research into this issue, I can trace the root cause down to a single file that casts a “Won’t Fix” into question, since the same file is responsible for the very much triaged MC-310982, MC-310984, MC-311035 and MC-311320 (and the hilariously WAI-resolved MC-310119).
Instead of the dedicated Linux scancodes list (scancodes_linux.h), Minecraft on Linux instead points to the second table in scancodes_xfree86.h. This is why most keystrokes on Linux match up perfectly with the Linux sheet, with the occasional divergence.
A fix for this disparity, bringing both sheets up to parity with each other (https://github.com/libsdl-org/SDL/pull/16239), has already been merged into the main repository, meaning that “Won’t Fix” with current knowledge seems like a very inappropriate resolution - the second this change gets into a monthly full release of SDL, and Minecraft changes to using that build, this issue will be very much fixed. Is there any chance this could get looked at again now that this information has come to light?
Thank you for helping us improve Minecraft! We saved your files: