Did the tester stop playing because they were scared or because they were bored?

Two testers close the game at the same scene. One was shaken, the other was yawning, and they need opposite fixes. This entry reads the last minutes before a quit to tell them apart, and keeps test sessions that simply ran out of time from muddying the picture.

Why this works

People who stop out of fear and people who stop out of boredom leave different traces: one has just been startled, the other has stopped touching the controls. Reading the minutes before the exit is cheaper and more honest than asking afterwards.

When not to use it

Do not use it for short demos where people leave to do something else in their day, or when the game can crash and look like a quit. There, ask the tester directly in a short talk right after the session.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Did the tester stop playing because they were scared or because they were bored?" (read_entry quit-after-a-scare-or-out-of-boredom) 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