Which task did my five playtesters fail at, and where did they get stuck?

Watching a few people play is the cheapest test there is, if you note down the same few things every time. This entry turns your notes into a clear list of the tasks that failed, or that nearly did, with the numbers to back it up.

Why this works

Problems show up in what people fail to do, not in what they say, and a few testers reveal the big ones because big problems hit almost everyone. Splitting tasks into broken and confusing tells you whether to rebuild or to explain.

When not to use it

Skip it when the aim is to compare two versions or to measure how much players like the game; a handful of testers cannot answer that. For comparing, use many players and a count, and for taste, ask open questions.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 28 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 "Which task did my five playtesters fail at, and where did they get stuck?" (read_entry playtest-tasks-finished-and-stuck) 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