Model the bindings by context
Drone controls, infantry actions and menus can reuse a physical key safely. Add the correct context to each row before resolving collisions.
After the logical audit, test the physical clusters you actually hold: lean, movement, sprint, crouch and ability combinations. Browser-reserved shortcuts remain a documented limitation.
Repeatable checklist
- Import or enter bindings
- Assign each context
- Test high-frequency physical clusters
Refuse false precision in scope conversion
A number with many decimals is not automatically accurate. Per-optic and field-of-view behavior requires a defined model and verification path.
Use DPI measurement and hip-fire physical distance as baseline notes, then keep each scoped setting as an observed in-game record instead of forcing it through an unsupported ratio.
Repeatable checklist
- Record DPI and hip-fire baseline
- List each optic separately
- Validate with repeatable in-game motion
Game-specific boundary: Keymap deliberately does not output a universal per-optic conversion where the model is not documented and testable.