Which card may go on which pile, and how long a run can be moved at once

A card-stacking game needs a clear rule for every pile, and players expect to drag several cards at once, yet the number they can really move depends on spare spaces in a way most builders get wrong. This entry gives both the pile rules and the exact limit.

Why this works

Moving a group is really moving one card at a time with a place to park the rest. The more free places there are, the longer the group, which is why the limit is a calculation and not a fixed number.

When not to use it

If your game lets the player drag a whole group in one go without limit, or the game moves cards by itself, the park-and-move limit is not needed. Use it only when the rules should match what a person could really do by hand.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 32 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 "Which card may go on which pile, and how long a run can be moved at once" (read_entry card-pile-moves-and-run-limit) 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