How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Opposite Direction Inputs Causing No Movement (SOCD Cleaning)

Q: What causes opposite direction inputs causing no movement in your game?

When a player holds two opposing directions at once, your code adds +1 and -1 to the axis and gets zero, so the character stops instead of resolving to a sane direction.

Quick answer: Apply SOCD (simultaneous opposite cardinal direction) cleaning: choose last-input-wins or a fixed priority so two opposing presses produce one clear direction.

If holding left and right together makes your character stand still, you have unhandled SOCD. Picking a resolution rule fixes it and matches fighting-game conventions. Here is how.

How to apply SOCD cleaning

1. Pick a resolution rule

Decide between last-input-wins (the most recently pressed direction takes over) or a fixed priority (for vertical, up usually overrides down). Document the rule so it is consistent.

2. Track press order

Store the time or order each direction went down so you can resolve which one is most recent. Reading only the current held state cannot implement last-input-wins.

3. Clean before applying

Run the cleaning step on the raw input each frame and feed only the cleaned axis into movement and combo detection, so canceled pairs never reach gameplay logic.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.