Did my rewritten scene keep more players? Comparing before and after a patch

After rewriting a scene it is tempting to compare the quit numbers of last week and this week and cheer. But players who were already halfway through, and plain luck with small numbers, can both fake a win. This entry shows who to count and how big a change must be to believe it.

Why this works

To judge a change, compare like with like: count each player once at first sight, assign them to the version they saw, and ask whether the gap is bigger than chance. That stops repeat visits and luck from passing as improvement.

When not to use it

Wrong with few players, or when other things changed in the same version, such as new music or an earlier scene. Then show the new scene to a random half of players at the same time and compare.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 39 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 "Did my rewritten scene keep more players? Comparing before and after a patch" (read_entry story-patch-before-after-quit-rate) 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