Capture requirement
Maintained-current rule:
- the target City must directly connect to a Military Stronghold currently controlled by the alliance.
A City cannot be treated as an isolated target on the map.
City unlock schedule
Maintained modern calendar:
| Season Day |
Unlock |
| 3 |
Lv1 City |
| 7 |
Lv2 City |
| 10 |
Lv3 City |
| 14 |
Lv4 City |
| 17 |
Lv5 City |
| 21 |
Lv6 City |
| 28 |
Apocalypse City / Capitol |
Static pages should show these expected days with a visible check the live City Clash timer note.
Declaration limit
Once the relevant declaration system is available:
- up to 2 City declarations per day.
The newer Warzone Expedition research confirms:
- 2 Stronghold captures + 2 City declarations are separate daily limits.
One City attack at a time
Maintained-current map guidance:
- only one City siege can be active at a time for the alliance;
- after declaration, the alliance has 1 hour to complete the capture.
This is important for R4/R5 sequencing on declaration days.
City ownership limits
Maintained-current map guidance:
- up to 4 Cities in the alliance's home/starting zone;
- up to 4 additional Cities in other warzones;
- 8 total across home + foreign territory.
Current retained evidence separately confirms a 4-City cross-warzone cap, strengthening the foreign half of this rule.
Publication confidence: high for the foreign cap; maintained-current for the complete 4 + 4 = 8 model until the live City List/current client exposes the total directly.
City protection — precise current-client rule
Current client key provides the best rule:
- City protection ends at 12:00 server time.
- Normally, it ends at 12:00 on the next calendar day after six full days have elapsed since battle end.
- After Warzone Declaration is active, the endpoint moves to 12:00 on the next Wednesday/Saturday declaration day that occurs after the six-day period.
- A declaration can last up to 1 hour.
- The contest stage closes at 24:00 that day.
Player-facing simplification
Cities are protected for roughly a week. Use the live City countdown for the exact attackable time.
R4/R5 wording
City protection is declaration-calendar aligned, not simply “capture timestamp + 168 hours.”
This replaces the old bare “7 days” rule wherever exact scheduling matters.
Why City routing matters
Cities do several jobs at once:
- advance the alliance deeper into the map;
- increase Stronghold capacity;
- create Influence / settlement value;
- enable better future routes;
- become required stepping stones toward Lv6 / Capitol positioning.
Therefore the correct target is not always “the strongest City we can currently beat.”
The correct target is:
the City that gives the best next route while remaining defensible and compatible with protection timing.
City common mistakes
- Declaring without a live Stronghold connection.
- Choosing a City only for immediate rewards.
- Ignoring protection expiry when planning the next declaration day.
- Holding a City that blocks a more valuable route because the alliance did not plan the Stronghold cap.
- Assuming two declarations means two simultaneous sieges.
- Treating the public “7-day” shorthand as an exact 168-hour timer.
