Your own test runs and bots make the quit chart look strange: how to filter them out

A story game that you or a helper click through to check a fix, or a program that walks it, produces runs that read impossibly fast or with identical timings. They pull every rate toward a finish that real people never reach. This entry shows how to recognise such runs from timing alone.

Why this works

Your own test runs and scripts behave unlike readers: too fast to read, or with the same wait every time. Judging each session by its own rhythm needs no personal marker and respects privacy. Listing the reasons lets a person check the first cases before trusting the filter.

When not to use it

Do not use it where real readers can be very fast, such as people replaying text they know, or where skipping is a feature. They would be thrown out wrongly. Mark test runs at the source if you can, and use this only as a second check.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 25 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 "Your own test runs and bots make the quit chart look strange: how to filter them out" (read_entry story-test-and-bot-runs-filter) 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