Attempting to bind a game control to the "settings"/"config" key on your keyboard will instead result in that control being bound to F13. This did not happen in the previous snapshot.
To reproduce, simply try to bind a game control to the settings key on your keyboard. If your keyboard does not have this key, a key press can be simulated using the attached script (Linux only):
download the attached Python script and put it in a folder somewhere
open the terminal in this window and run the following command: ./simulate-keys 'sleep 2' 'press 171' 'sleep 0.1' 'release 171'
within two seconds, click on one of the rebindable buttons in the controls menu and wait for a control to be bound to it
This issue may be Linux-exclusive - I do not know how to test this on Windows.
Attachments
Comments 3
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
Well… I can’t exactly say I’m not amused by this ticket’s Works As Intended resolution, now that I’ve figured out the root cause behind this allegedly intended design decision.
It turns out that rather than pointing to scancodes_linux.h as one would expect, SDL3 instead uses scancodes_xfree86/h for Linux desktop inputs, and this document for some reason maps the settings button to F13 rather than to Unknown (for a lack of a dedicated SDL settings keyboard code).
I’ve sent in a PR that fixes this issue, alongside the five related tickets MC-310845, MC-310982, MC-310984, MC-311025 and MC-311320: https://github.com/libsdl-org/SDL/pull/16239 - all that needs done now is for the next full release of SDL to come out and for Minecraft to then update to it for this issue to be fixed.
With this newly unearthed information in mind: is there any chance that the resolution of this ticket could be reconsidered?
Thank you for helping us improve Minecraft! We saved your files: