One tap moves the dialogue on twice and a line is skipped

Phones send a touch and then a mouse click for the same tap, and a player who taps to finish a line often taps again as the text ends. Both skip a line unseen. Here is the rule that tells apart "finish this line", "go on" and "that was an echo".

Why this works

One tap can arrive as two events, and a hurried tap can land just after the text finishes. What the player meant matters more than what the device reported. So the game judges each tap by what just happened, and ignores the echo.

When not to use it

Do not add waiting time to a game where fast reactions matter, such as a rhythm or quick-reply scene. There the delay feels like lag. Use one input event only, and do not protect against double taps.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 28 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 "One tap moves the dialogue on twice and a line is skipped" (read_entry one-tap-advances-dialogue-twice) 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