Spot bursts of undo presses that show a player fighting the controls

One undo is a correction. Ten in a few seconds is a person who does not understand what just happened. This entry shows how to find such bursts in a click log without flagging a player who simply undoes things slowly over a long session.

Why this works

One undo is a change of mind. Many in a few seconds is someone who does not understand what the controls did. Counting bursts, not presses, keeps one long panic from drowning out many small ones, and each burst points to a moment worth watching.

When not to use it

Do not use it in tools where fast repeated undo is normal, such as drawing, level editing or puzzles where you try and rewind on purpose. There it is skill, not confusion. Compare against how the same person worked earlier.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 23 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 "Spot bursts of undo presses that show a player fighting the controls" (read_entry undo-storms-as-confusion-signal) 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