City Siege

🟦 Facts

City siege troops are affected by seasonal toxins; Virus Resistance reduces the impact.
A portion of units is directly killed; the exact ratio is displayed on each City.
First-time participants receive rewards, and the alliance receives City rewards and loot chests.
After defenders are cleared, attackers must continue damaging City durability until it reaches zero.

After capture, City protection runs to the game-specified 12:00 server-time point about six days later.
After abandoning a City, the same alliance waits approximately five days before declaring on it again.

Confirm the City is the correct route target and that declaration requirements are satisfied.
Warn members about direct troop deaths before they blindly send every march.
Identify the strongest rally or attack squads for the defenders and keep enough marches available to finish durability.
Tell members whether leadership wants broad first-capture participation before the City is finished.
After capture, immediately review the new adjacency, protection timer, heat, and alliance buff before choosing the next target.

Do not judge a City only by whether the defenders can be beaten. The alliance must also have enough sustained participation to finish durability efficiently.
For harder Cities, coordinate attack waves instead of letting strong squads arrive randomly while others are still marching.

The word “approximately” is intentional for protection/abandonment timing; use the live City timer when it differs.

The City’s first protection period ends at 12:00 server time.
After capture, the game describes protection lasting to the specified 12:00 server-time point about six days later; use the live City timer for the exact calendar date.