Make a quest log glide after a flick and come to rest on an entry

A long journal that stops half-way through a quest title looks broken. Players want a flick to carry on a little and then settle with an entry neatly at the top, even when entries differ in height and the end of the list cannot reach the top.

Why this works

A flick carries an intention, so the place to stop is decided by where the list would drift to, not by where the finger was. Choosing the nearest entry to that guess feels like the list understood how hard you pushed.

When not to use it

Skip it for long text or maps that people read while scrolling, because snapping to entries cuts the reading in the middle. Let those scroll freely and stop wherever the glide ends.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 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 "Make a quest log glide after a flick and come to rest on an entry" (read_entry quest-log-scroll-glides-then-stops-on-an-entry) 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