Capture the conditions that can change the result
Record the game version or link and when the issue occurred. Include browser and operating system when known, viewport size if layout matters, whether the page had just loaded, and any relevant run state. For a timing-sensitive jump, mention whether the tab had been hidden and reopened. Do not guess a technical cause; note concrete conditions that another person can repeat.
Check whether the issue is repeatable
Repeat the same steps a few times before adding workarounds. If the result appears intermittently, say so and count attempts rather than calling it random. Reset to the same starting state if possible. Then vary one factor: use a slower key press, change the viewport, or wait for a different platform position. This can reveal a useful boundary while keeping the original report intact.
Questions about reproducing game bugs
What if I cannot reproduce a game bug every time?
Keep the intermittent report and record how many attempts succeed, the starting state, and relevant timing. Change one factor per follow-up attempt and note when the failure stops appearing.
Should a bug report include a suspected cause?
You may add a clearly labeled hypothesis, but keep it separate from observed facts. Exact steps and expected-versus-actual behavior let a developer investigate without inheriting a guess.