My hint text vanishes quickly: do players have time to read it?

A line of help that fades away or gets tapped past can be gone before anyone understood it. This entry shows how to work out how long a text needs on screen, how to spot from the logs that people are skipping it, and why the language changes the answer.

Why this works

Reading takes a fixed amount of time per letter, plus a moment to notice the text. Time on screen below that cannot be read, however clever the wording. Measuring how fast people close it shows whether the text is read or just tapped away.

When not to use it

A fixed reading speed fits plain instructions, not a few big words people know already or a long story passage that readers take at their own speed. For those, let the text wait until the player taps, rather than timing it.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 13 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 "My hint text vanishes quickly: do players have time to read it?" (read_entry tutorial-text-disappears-before-it-can-be-read) 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