Tell apart tutorial steps where players get stuck and steps they just skip past

Two tutorial steps can lose the same share of people for opposite reasons: one confuses them, the other bores them. The fix differs, so the numbers have to say which it is. This entry shows what to compare and when there is too little data to say.

Why this works

Leaving is a symptom, and the time spent before leaving tells the cause. Someone who tried hard and gave up was stuck, someone who left at once was bored or put off, so the same loss needs opposite cures.

When not to use it

Skip it when you have only a few players, when a step is made to wait by design, or when your tutorial is a single short screen. Watch real people go through it instead and ask them what went wrong.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Tell apart tutorial steps where players get stuck and steps they just skip past" (read_entry tutorial-step-stuck-or-bored) 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