Summary
Custom Hotbar input actions (HotbarMapping / IA_CustomHotbarSlot1-8) never fire on AZERTY keyboards
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
- On a Windows PC with a French AZERTY keyboard layout (fr-FR), create a Verse device.
- Add the hotbar mapping to the player: GetPlayerInput[Player].AddInputMapping(HotbarMapping) (/Verse.org/Input/Gameplay).
- Get the events of IA_CustomHotbarSlot1 with GetInputEvents and subscribe to BeginDetectEvent, TriggerActivationEvent and CancelActivationEvent, printing a log line in each.
- Launch a session, hold Left Shift (IA_CustomHotbarModifier) and press the top-row “1” key.
- Switch Windows to an English (US) QWERTY layout (Win + Space) without changing anything else, then hold Left Shift and press the top-row “1” key again.
Expected Result
Holding the Custom Hotbar modifier and pressing the top-row 1..8 keys triggers IA_CustomHotbarSlot1..8 on any keyboard layout, like the default Fortnite weapon slot keys do.
Observed Result
On the AZERTY layout nothing happens: no BeginDetectEvent, no TriggerActivationEvent, no CancelActivationEvent, with or without Shift held. The input action widget still displays “Shift + 1” on screen, so players believe the key should work.
On the QWERTY layout, with the exact same session and code, Shift + 1 / 2 / 3 immediately fire the events.
The default key mappings of IMC_HotbarMapping are bound to the keys One..Eight. On AZERTY, Unreal reports the top-row keys as Ampersand, E_AccentAigu, Quote, etc., so the key “One” is never produced and the slot actions can never trigger.
Platform(s)
Windows/PC
Additional Notes
- This affects every player using an AZERTY keyboard (France, Belgium): they cannot use any Custom Hotbar slot unless they manually rebind each slot in the Fortnite settings, which they have no reason to guess.
- Gamepad (RB + D-pad) and QWERTY keyboards work.
- Separate from FORT-1128779 (Shift modifier required, closed as “working as intended”): here the modifier is held and the action still never fires.
- Suggested fix: provide layout-aware default mappings for the Custom Hotbar slots (as done for the standard Fortnite key bindings), or bind them by physical key / scan code.
- Related request: the on-screen prompt and documentation should mention that the modifier must be held.
