-
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
Number on aplhanumeric part of keyboard can be binded to custom action and colide with wiel item change without warning #15746
Comments
What is the expected outcome? What should be done to prevent key collisions? It's the player's responsibility to configure the hotkeys such that they are usable. |
Can you see if it helps resolve the issue by adding the following settings to
If yes, then I assume that this issue (similar to #15729) would fall under the scope of #10927 / #11209; maybe we can make this a sub-issue. |
@SmallJoker If should show a warning about "Key is already in use". |
@y5nw It results in slot changing stops to work. |
Ok, so it seems like I misread the issue here; this is about collision warnings being missing. Looking at the source code, it appears that, in general, keybinding settings that do not appear in the key change menu are not taken into consideration when checking for collisions: luanti/src/gui/guiKeyChangeMenu.cpp Lines 272 to 280 in 568f7a8
luanti/src/gui/guiKeyChangeMenu.cpp Lines 355 to 403 in 568f7a8
|
@y5nw I updated the description, based on @SmallJoker comment. |
Luanti version
Operating system and version
Tested on MacOS and Linux Arch.
CPU model
No response
GPU model
No response
Active renderer
No response
Summary
Users can rebind alphanumeric numbers to custom actions, which cause control collision. There is no warning about key collisions in this case.
Steps to reproduce
Start the game, rebind forward, backward, left, and right to some numbers on the alphanumeric keyboard (you will see no warning about key collision), and try to walk.
You should observe the change of wield item and move at the same time.
The text was updated successfully, but these errors were encountered: