Keep a quick second swipe instead of dropping it while tiles are still sliding

In sliding-number puzzles fast players swipe again before the last move has finished. Ignoring the swipe feels broken, accepting every one makes moves pile up and run on long after the fingers stop. Here is a small rule for exactly one waiting move and a speed-up that keeps the game snappy.

Why this works

Fast fingers should never be wasted, yet a long backlog is just as bad. Keeping exactly one waiting move, and speeding up the running picture to make room for it, lets the board keep up with intent without playing on after the player has stopped.

When not to use it

Do not use it in careful, turn-by-turn puzzles where a stray swipe could ruin a plan, or when each move is slow on purpose. Ignore input during the move, or ask for a confirm.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 28 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Keep a quick second swipe instead of dropping it while tiles are still sliding" (read_entry puzzle-queue-one-swipe-during-a-slide) 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