A downgraded or destroyed house must move its residents, not just lose them

When a house shrinks or burns, the people inside do not vanish. If the game just cuts the number, the population count drops for no reason and the city level wobbles. If it keeps them, houses burst past their limit. This entry shows how to move them to free rooms nearby in a fixed order and how to count the ones left without a home.

Why this works

People are not a number to be trimmed; they are somewhere or nowhere. Moving them in a fixed order keeps every head counted, and the ones with no room are named and kept, so the city can find them a home later instead of quietly shrinking.

When not to use it

Skip it when residents are only a stat with no individuals, or when losing a home is meant to cost people, as in a harsh survival game. Then letting the count fall, with a clear message, can be the better and more honest choice.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 29 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 "A downgraded or destroyed house must move its residents, not just lose them" (read_entry downgraded-house-must-move-its-residents-out) 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