Season 1 operating system for R4/R5
1. Route map
Maintain a live Stronghold → City route rather than choosing captures one at a time. Every capture should have a next purpose, especially before Lv5/Lv6 and cross-warzone expansion.
2. Protection calendar
Record the live countdown shown by every important Stronghold and City. Stronghold duration has a rollout conflict, and City protection is calendar/declaration aligned rather than a simple “+168 hours” rule.
3. Resistance roster
Know which members have the highest useful Virus Resistance and use them as rally leaders for difficult seasonal PvE. This prevents displayed squad power from choosing the wrong lead.
4. Expedition playbook
Before placing a foreign Outpost, map the first Stronghold and the City route it is supposed to unlock. Stage members, accelerate construction, and secure the foreign Stronghold quickly.
5. Builder decision
Use a value matrix, not emotion after a lost fight. Compare realistic Influence ceiling, activity coverage, diplomacy, defense capacity and the practical value of Builder facilities.
6. Octagon command
Move from alliance command to warzone command. Establish one coordination channel, attacker/defender assignments, rally and garrison leads, and an objective-first plan before Saturday.
7. Settlement policy
Publish reward criteria before Week 8. Attendance, territory work, server-war participation, defense, activity and leadership work are all defensible inputs; the important part is that members know the criteria before rewards are assigned.
