Both players order a move into the same square at the same time

When all orders are carried out together, someone has to lose a collision, and the answer must not depend on who happens to be listed first. Swaps, chains and units that stand still make the rules harder than they look. This entry gives a set that always settles.

Why this works

Fairness means the answer cannot depend on who is listed first. Judging every move against the same picture of the board, and only then applying the blocks together, makes the outcome a property of the situation, not of the order of writing.

When not to use it

Not for turn-based games where one player moves at a time, and not when you want a clear winner of a clash, such as the stronger or faster unit pushing the other away. Then settle each clash by strength or speed instead of blocking both.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 25 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 "Both players order a move into the same square at the same time" (read_entry simultaneous-moves-collisions-and-swaps) 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