What is a typical run in a score-based casual game when a few players score huge?

In endless games a few superb runs drag the average far from what most people experience. This entry shows which numbers to read instead and how to place new obstacles by how many players will see them.

Why this works

A few spectacular runs drag the average far above what most people ever get, so the average describes nobody. Points that mark where a given share of runs ended tell you what a normal player reaches, and let you place new content where it will be seen.

When not to use it

It is not needed when scores are bounded and evenly spread, as in a game with a fixed maximum. And do not use it to set difficulty alone, since a score says little about how a run felt. Pair it with where players quit and what they say.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 31 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 "What is a typical run in a score-based casual game when a few players score huge?" (read_entry casual-score-skew-typical-run) 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