Quick answer: Buffer recent inputs and match motions with a forgiving window, tolerate minor deviations and extra directions, and prioritize the most complex matching motion.
Special moves that drop are an input-interpretation problem. A forgiving motion detector fixes it. Here is how.
How to fix it
1. Buffer the input history
Keep a short rolling history of directional and button inputs with timestamps, and scan it for motions. Checking only the current frame misses motions that span several frames.
2. Match with a forgiving window
Allow the motion's directions within a window of frames and tolerate minor deviations (a diagonal read slightly off, an extra neutral). Requiring a frame-perfect, exact sequence rejects inputs players feel they hit.
3. Prioritize complex motions
When several motions could match the recent inputs, pick the most complex one (a dragon punch over a fireball) so the intended hard input is not eaten by an easier overlapping one.
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.