Some chord mappings conflict with system shortcuts and need detection

What it is

Shortcut conflict detection identifies, before a player saves a chord or a remap, whether that key combination competes with the operating system, the platform, an IME, a screen reader, or an existing in-game command. This builds on complete remapping — where complete remapping solves "can it be changed at all," shortcut conflict detection solves "once changed, can this combination actually be used." The harm a conflict causes goes well beyond an action simply failing to trigger: what actually happens can be a focus shift away from the game, the game window minimizing itself, a system-level interface popping up unexpectedly, or assistive technology a player depends on suddenly failing — none of these sit in the same league of frustration as a simple unresponsive button press.

Why it happens

Processing a key combination passes through several priority layers: the operating system itself, whatever IME is active, any assistive technology running, and the game — each of which may interpret the same combination differently. If a game's remapping system was designed with only its own internal binding table in mind, with no awareness that a given combination gets intercepted first by a higher-priority platform layer, a configuration a player saves may look completely fine during ordinary menu navigation, and only reveal itself as entirely unusable once the player is deep in a high-pressure moment that demands fast, repeated presses — precisely the moment players have the least patience to troubleshoot and are most likely to blame "bad hardware" or "my reflexes" instead. Detecting this at save time turns a configuration that would otherwise only expose itself as unusable at the worst possible moment into a choice players can understand and consciously weigh right there in the settings screen, cutting off this kind of misattributed frustration at the root.

Where it stops holding

The specific list of system-reserved keys shifts with operating-system version, platform, and a player's locale IME, so maintaining one universal blacklist and assuming it stays valid forever is not adequate. Nor should every detected conflict be forbidden outright: some conflicts only actually occur under specific conditions — say, only in windowed rather than fullscreen mode, or only when the game window lacks system focus — and can be used safely once those conditions are accounted for. This calls for handling three distinct severity levels differently: a combination that is genuinely unusable must be hard-blocked from saving, a combination with conditional risk should carry a warning the player can knowingly override, and a duplicate binding purely within the game's own internal logic is a third case — and each one needs to tell the player exactly what will happen, rather than a generic "conflict detected."

Applying it

• Maintain, separately per platform, a complete list of reserved keys, shortcuts commonly used by assistive technology, and the game's own existing bindings, and validate against it the instant a player saves a new key configuration, rather than troubleshooting only after something goes wrong.
• Block saving outright for combinations confirmed to be hard, unusable conflicts; for combinations carrying conditional risk, state specifically under what circumstances a problem would occur and proactively suggest a viable alternative key.
• How to check: on every target platform, across different window display modes (fullscreen, windowed), and with different IME activation states, automatically trigger every combination a player has saved in sequence, checking one by one that the in-game action, system focus ownership, and platform-level behavior all match expectations.

Related

• Same group: W3.04.1 Remapping must cover every actionable key, not only common ones · W3.04.3 Controller and keyboard-mouse remaps need independent saving · W3.04.4 A hidden remapping entry lets the default layout deter players
• Nearby: W3.03 Control mapping · W3.04 Key remapping · W8.04 One-handed and switch-device operation
• Search terms: shortcut conflict detection · reserved keys · key chord · input validation