Quick answer: Use a movement state machine with clear transitions, handle standing up blocked by a ceiling, and resolve conflicting inputs deliberately.

Crouch and sprint conflicts are unclear movement states. A state machine fixes them. Here is how.

How to fix it

1. Use a movement state machine

Model standing, crouching, and sprinting as states with defined transitions, rather than independent flags that can combine incorrectly. The state machine makes conflicts (sprint while crouched) impossible or deliberate.

2. Handle blocked stand-up

When the player tries to stand from crouch but there is a ceiling, keep them crouched until there is room. Without this check, standing up clips the player into the ceiling or gets them stuck.

3. Resolve conflicting inputs

Decide what happens when crouch and sprint are pressed together — one takes priority, or sprint cancels crouch — and apply it consistently. Unresolved conflicts make the character toggle or stick between states.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.