When a city loses people, its policy slots shrink, so decide which policies pause

A town gets a new slot for a law or policy at each population milestone. Then people leave and a slot disappears. If the game deletes a chosen policy, the player pays again later; if it keeps all of them, the limit means nothing. This entry shows how to pause in a fixed order, keep the choices and bring them back in the same order.

Why this works

A choice the player paid for should survive a bad spell. Pausing instead of deleting keeps what was chosen and brings it back in the same order when things recover. Putting the newest on hold first follows a rule a player can guess before it happens.

When not to use it

Skip it when policies are cheap and meant to be swapped often, or when the slots never fall, as in a game where cities only grow. Then the pause rule adds nothing. Keep a plain list with a fixed limit.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 18 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 "When a city loses people, its policy slots shrink, so decide which policies pause" (read_entry policy-slots-shrink-when-the-city-shrinks) 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