Some sessions look inhuman: how to find automatic tapping in my numbers

In idle and tapping games a few sessions play with a rhythm no hand can keep, and they bend every average of progress and speed. This entry shows the one property that gives a clicker script away, what limit to use and when not to judge at all.

Why this works

A hand cannot keep a perfect rhythm. Even a fast human wobbles from tap to tap, while a script repeats itself almost exactly. The evenness of the gaps gives a script away far better than the sheer speed does.

When not to use it

Do not use it in a game about rhythm, where people tap evenly on purpose, nor for assistive devices that tap at a steady pace for a person who cannot. There, judge the timing against the music or ask the player.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 19 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 sessions look inhuman: how to find automatic tapping in my numbers" (read_entry tell-bot-taps-from-human-taps) 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