Represent modifiers and control groups honestly
Dota layouts often rely on modifiers, unit selection and item slots. Write compound bindings explicitly and group them by the context in which they compete.
A direct conflict checker cannot decide strategic preference. It can expose accidental duplicates and produce a portable plan for the physical test.
Repeatable checklist
- List modifiers explicitly
- Separate unit and menu contexts
- Export the reviewed plan
Test the real combination after the logical map
Keyboard matrix limits appear in exact physical clusters, not in an abstract action list. Hold the movement, modifier and ability group that fails and confirm every code reaches the browser.
For mouse symptoms, inspect button down/up before double-click intervals. This order distinguishes a missing button path from suspicious repeated click delivery.
Repeatable checklist
- Run intended key clusters
- Check button down/up pairs
- Compare the same action in game
Game-specific boundary: Keymap does not read Steam or Dota configuration files. Imported plans use the local Keymap JSON format only.