The number action does not fire#
Confirm you are on Windows, the plugin is enabled, and Digits is on. Check the action is bound to One through Zero and focus the game viewport before testing.
Use KeyboardLayout.Debug 1 for a local check, then turn it off with KeyboardLayout.Debug 0.
Positional movement does not work#
Enable Physical and test in a game viewport. Physical mode does not apply to editor letter shortcuts, text boxes, or the open console.
The key prompt shows the wrong letter#
Use Get Key Display Name (Keyboard Layout) and refresh it after On Keyboard Layout Changed. Check that the font includes the returned character.
The key left of 1 does not open the console#
Check Console Key is on and the project's Console Keys include Tilde. The build must also provide a console. A digit key in that position keeps its digit behavior under the default correction.
The game works, but editor number shortcuts do not#
Enable Fix Number Row In Editor, and check that Digits is on too; the editor fix needs both. A Set Digits Enabled call with Digits off during Play In Editor also turns the editor fix off until you restart the editor or turn Digits back on. Letter shortcuts intentionally keep their ordinary editor behavior.
Custom bindings moved after switching modes#
Physical mode changes what saved letter and punctuation bindings mean. Reset, convert, or rebind them as part of your game's mode-change workflow.
My option resets after restarting#
Blueprint setters are session-only. Save the choice in your game settings and reapply it when starting.
Only streamed or simulated input fails#
Pixel Streaming, browser-widget input, widget interactions, IME-managed keys, and the GameInput keyboard route are not covered by the normal Windows-keyboard correction.
Another input plugin changes the result#
Test with the same layout and a minimal project to identify the conflict. For help, include the active layout, expected key, actual action, input plugins, plugin and engine versions, and whether the issue is in the editor or game.