Audit high-frequency actions first
Abilities, items, camera controls, attack-move and communication create a dense layout. Enter the actual physical code and context rather than only the printed character.
Resolve direct collisions, then test the movement-hand combination and mouse buttons. Comfort and accessibility still need a real-session check.
Repeatable checklist
- Enter champion and global actions
- Check same-context duplicates
- Test side buttons and keyboard cluster
Separate click evidence from game command behavior
The double-click lab can show whether slow single clicks produce unusually close browser events. It cannot see how the game queues or interprets commands.
If browser events are clean while the symptom remains in League, preserve the current config and compare one game setting or software overlay at a time.
Repeatable checklist
- Run 30+ slow single clicks
- Compare another port or mouse
- Retest the exact in-game command
Game-specific boundary: Browser clicks and key events do not reproduce the game’s command queue, network state or server response.