Build a sensitivity record you can reproduce
Start with the exact DPI reported by your mouse software, the in-game sensitivity and whether operating-system acceleration or vendor angle snapping is active. The Keymap result is a calculation record, not permission to skip the in-game check.
When moving from another supported FPS, preserve hip-fire angular distance first. Scoped and ability-specific behavior belongs in a separate test because field of view and zoom processing can change perceived speed.
Repeatable checklist
- Run the DPI distance sample three times
- Convert hip-fire sensitivity with the exact source value
- Verify a measured 360-degree turn in game
Treat keybinds as a conflict graph
A duplicate is not automatically wrong: one key can be safe in two mutually exclusive contexts. The conflict checker therefore separates global, combat and menu contexts.
High-frequency actions should be reachable without collapsing movement. Record the actual action names and test the cluster in the keyboard lab; a visually elegant layout that loses a movement key is not a good layout.
Repeatable checklist
- Enter combat bindings
- Resolve same-context duplicates
- Run the final movement-plus-ability cluster
Game-specific boundary: Keymap does not publish “best pro settings.” A copied value can hide differences in DPI, grip, display, role and training history.