What is it?
A Season 1 alliance that trades the city/influence race for a development-and-logistics path. Confirmed Mechanic It’s available only in weeks 4–7 and cannot be reversed during that season. Lead every conversation about it with that irreversibility — it’s the whole decision.
Who is it actually for?
The official article carries one line suggesting builder rewards suit powerful large alliances, but the surrounding text repeatedly recommends small–medium, casual and support alliances. We treat that single line as a translation/editing error and follow the body of the guidance: Corroborated Strategy this route is for an alliance that realistically cannot rank in the city/influence competition, or that wants to become a logistics/support backbone for fighting alliances in its warzone.
Entry conditions
| Requirement | Official condition |
|---|---|
| Timing | Season 1 weeks 4–7 |
| Member power | At least 10 members at ≥10M power |
| Influence | ≤1,000,000 |
| Cities | Abandon captured cities |
| Fortresses | No more than 3 captured per warzone |
| Authority | R5 or R4 Management |
| After switch | No Alliance Ranking participation; no city declarations |
| Reversal | Not permitted for the rest of the season |
Facilities and effects
| Facility | Effect | Scope |
|---|---|---|
| Iron / Food / Coin Factory | Resource output up; Base Durability +10% | Broad / warzone per tooltip |
| Collection Depot | Gathering Speed +10%; Durability +10% | Broad / warzone |
| Engineering Hub | Construction Speed +10%; Durability +10% | Broad / warzone |
| Research Lab | Research Speed +10%; Durability +10% | Broad / warzone |
| Training Center | Training Speed +5%; Durability +10% | Broad / warzone |
| Medical Facility | PvP unit death rate −5% | Same warzone |
| Radar Station | Hero DEF +5% | Same warzone |
| Armory | Hero ATK +5% | Same warzone |
When to switch — the decision model
| Question | Switch pressure |
|---|---|
| Can the alliance realistically rank in the city/influence race? | If no — builder gains value. |
| Can leadership field capture attendance at the required server times? | Poor time-zone fit strongly favors builder. |
| Does the warzone need a support/logistics alliance? | Builder facilities create warzone-wide value. |
| Will members accept the irreversible loss of city declarations? | If no — do not switch. |
| Are the 10 qualified members + influence/territory conditions met? | All must be satisfied first. |
| Will members donate daily materials? | Low participation wastes the conversion. |
Common mistakes
- Switching on the alliance’s aspirational city ceiling instead of its realistic one.
- Converting without recorded member consent to the irreversible trade-off.
- Abandoning cities and reducing fortresses before confirming the switch window and all power conditions.
- Placing facilities where their buffs aren’t operationally useful to fighting allies.
- Forgetting new members can’t donate for 24 hours.
Leadership protocol
Calculate the realistic city/influence reward ceiling. Publish the irreversible trade-off at least 48 hours before conversion and record consent. Abandon cities and reduce fortresses only after confirming the window and member-power conditions. Assign an R4 to own facility placement and donation reporting, prioritize Engineering Hub / Research Lab / Training Center and combat-support facilities, and coordinate placement with the fighting alliances who’ll use the buffs. Leadership Protocol
The one official line praising “powerful large alliances” contradicts the rest of the same page, which repeatedly recommends small/medium, casual and support alliances — a documented conflict we resolve as a translation error rather than flattening it. Post-switch operational edge cases (strongholds, outposts and reward-day membership behaviour) are reported by players but not fully confirmed officially; the official restrictions — no cities, no Alliance Ranking, fortress prerequisite — are the solid part. Treat the rest as live-test items on your own server.