My hero sometimes stops dead in a wall while I hold the run button

Standing still against a wall is fine, but standing still for a second while falling or sliding is not, and a recording cannot tell the two apart by eye. This helper finds the stretches where a held button produced no movement at all, and how long each lasted.

Why this works

Stuck means no movement in either direction while the player is pushing. Requiring both directions to be still excludes a hero that is falling, and requiring a minimum time excludes the normal moment of touching a wall.

When not to use it

A hero who is meant to stop, like one pushing a heavy block or charging an attack, will show up as stuck. Mark those moments in the recording so that they are not reported.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 39 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "My hero sometimes stops dead in a wall while I hold the run button" (read_entry work-act-hero-stuck-in-wall-finder) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP