Measure how long a level really took without the time the phone sat on the table

On a phone, people put the game down mid-level and come back minutes later. If you time levels from start to finish, those pauses make an easy level look slow. This entry shows how to count only the time someone was actually playing.

Why this works

A phone is interrupted all the time, so the clock on the wall mostly measures life, not the level. A long silence is almost always the player being somewhere else, so treating it as a short pause keeps real thinking and drops the tea break.

When not to use it

Do not use it where long silence is the point, such as a game that asks you to wait or to watch something unfold. And it does not measure skill, since slow careful play still counts in full. Compare with moves or results to judge skill.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 22 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 "Measure how long a level really took without the time the phone sat on the table" (read_entry mobile-active-time-idle-gap-cap) 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