Plan a city siege as an alliance, not a last-hit race

Check eligibility before announcing the march

The listed rules allow an alliance with no cities to start with a level-one city. After that, adjacency, unlocked city levels and the remaining declaration allowance matter.

An R4 or R5 makes the declaration. If the interface asks for declaration content, enter a short attack message; the reference does not require a secret phrase. Confirm the target and the war window before asking members to mobilize.

Understand what decides ownership

In city scoring, 100 damage to defending troops earns one alliance point, and removing one durability earns five points. Members’ contributions add to the alliance total.

When durability is exhausted, the highest-scoring alliance takes the city. A final hit is therefore not a substitute for a sustained, coordinated contribution. Confirm the active mode’s rules before relying on a previous siege plan.

Keep the plan grounded in the live target

Client defense settings are not a live garrison report or a guaranteed minimum army size. Check the actual City Info, loss rules and countdown in your game.

Scheduled wars can fail if eligibility changes before they begin. Recheck adjacency, city limits and declarations near the scheduled start instead of assuming that yesterday’s plan still works.

Plan the handover after capture

• Tell members which rewards require participation and which are alliance-wide.
• Review the captured city’s own bonus rather than assuming every city of that level grants the same one.
• Arrange City Lord and Knight responsibilities for tasks, decrees and funds.
• Use server time when coordinating weekly tasks and reset-sensitive items.