Arcade-game bug reports: capture timing and input conditions

Arcade bugs often depend on timing, frame rate, or focus. Name the game under Arcade Games, mode, score, device, browser, and input method.

Record the starting state and exact sequence: when the key or touch was pressed, whether the page lost focus, what the game should have done, and what happened. For collision bugs, include a short recording or screenshots and the approximate frame. For score or high-score issues, test after a restart without destroying the original evidence. Note reduced-motion and accessibility settings if they may affect animation.

Separate a balance complaint from a reproducible rule failure. A useful report lets a developer recreate the same moment and see whether it is an input-handling, physics, or persistence problem.