[BUG] Use e.key instead of e.code in getKeyString(e) for proper numpad navigation support

[hospotho]

getKeyString(e) in WebUtils.mjs uses e.code, which returns physical key names. This breaks expected behavior: numpad arrow keys, PageUp/Down, Home/End etc. produce different strings than their main-keyboard equivalents, so they don't share the same functionality.

[Andrews54757]

that was intentional because it allows different keybinds to be mapped to different physical keys even if they have the same output value. also not every keyboard is the same, theres lots of different layouts out there so it made sense at the time to use code.

[hospotho]

I wont doubt the requirement exists. But right now it basically disables numpad navigation and ignores the nature of numpad, where most player wont do that.

For workaround, how do I map multiple keys (not only numpad keys) to the same action? Could not find any docs for this, and dont want to search through source code atm.

[Andrews54757]

It's not possible to map multiple keys right now but will be soon after I finish refactoring the configs.