-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keybindings menu can screw up? (“(If this menu screws up …)”) #8064
Comments
So. So far, nobody has brought up documentation on how this menu could be broken. Also, I had this menu never fail for me after all these years. The warning isn't even helpful. Even IF the menu screws up, the message is not really helpful for non-experts. What is the “stuff” that people have to remove from minetest.conf? |
It should rather be a comment in the code instead of a visible label in-game. It's supposed to say that more key bindings may result in a barely usable dialogue due to its size. If more settings should be configurable in-game, another design is needed. |
I think it means "if you mess up the keys, a way to reset them is to remove stuff from the config file". By 'stuff' it means the keybindings. |
The menu IS broken as of 5.3.0 Windows 10 64 bit, and does not save the keybindings upon game close. I am running the game as the administrator user. |
@thelabcat Please press the "Save" button on the bottom left to apply the changes. The key bindings will be applied instantly and the configuration file will be updated/written when closing Minetest in a proper manner. |
Confirmed, I pressed the save button. No go. |
Issue type
Minetest version
0.4.17.1
Summary
The keybindings menu has that weird warning at the top:
Is this warning still relevant? I think this warning has been in Minetest since ages, yet it's still there.
If the warning is still relevant, please write down (in this issue) what's wrong with it and why it could screw up. Then the menu should be fixed so it cannot screw up anymore and the warning should be removed.
But if the warning is already not relevant anymore, it should be removed.
The text was updated successfully, but these errors were encountered: