Some testers played twice: keep only the run where they didn't know the story

A tester who replays knows every twist and clicks through at speed, which makes your story look faster and less scary than it is for new players. This entry keeps the right runs, including the ones interrupted by a crash that were not really replays.

Why this works

Surprise, fear and reading speed only exist once. Someone who knows the story clicks faster and feels less, so numbers about first impressions must come from first runs only, while the replays answer a different question.

When not to use it

Do not drop replays when you want to know about mastery, hidden endings or what makes people start again. Those are exactly the questions replays answer. Keep them in a separate pile instead of throwing them away.

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 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Some testers played twice: keep only the run where they didn't know the story" (read_entry second-playthroughs-spoil-the-numbers) 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