Handle hero-specific layouts without duplicate noise
A large hero roster creates legitimate key reuse. The checker groups rows by context so a collision appears only when the same key competes inside the same active layer.
Use clear action names and preserve the exported JSON locally. A structured record makes later patch changes easier to audit than screenshots.
Repeatable checklist
- Separate global and hero contexts
- Resolve only active-layer collisions
- Export the final local binding plan
Baseline hardware before response settings
Run a center test, full sweep and button check before adjusting curves. If a directional shortfall repeats in the browser, increasing an in-game curve may only mask the symptom.
Mouse players should repeat the distance sample rather than treating a single DPI estimate as exact. Desk measurement error is visible when the runs disagree.
Repeatable checklist
- Run device-specific baseline
- Repeat suspicious observations
- Tune only after the signal is stable
Game-specific boundary: Hero-specific behavior can change. Keep the hero and update context with every saved settings note.