Combine two alliance rosters, handle the 100-member cap, plan who moves and who stays, assign post-merge leadership, and export a step-by-step plan for merge day.
Alliance A is the absorbing alliance — it stays open and receives members. Alliance B dissolves — its members move to A. If you set them up backwards, use the ⇄ Swap A ↔ B button in Step 1.
Ranks: R5 is the sole leader (one per alliance). R4s can hold named officer roles: Warlord, Recruiter, Butler, and Muse — maximum 10 R4s per alliance. R3–R1 are general members.
Key concepts: Mark members as ★ Core to protect them from cuts and move them first. Mark members as ✈ Departing if they're leaving to a different alliance entirely — they're excluded from all calculations. Use Core only scope if not everyone from B is joining A.
Power shown is post-merge — it reflects only the members who will actually end up in the merged alliance, after cuts and exclusions.
☆ Core — Protected from cuts; moves first. · ✈ Departing — Leaving to another alliance; excluded from all calculations. · Power is entered in millions (e.g. 350 = 350M).
One member per line: Name, Rank, PowerMil, active/inactive
e.g. Azumatt, R5, 350, active
One member per line: Name, Rank, PowerMil, active/inactive
e.g. Azumatt, R5, 350, active
Reflects only members who will actually join (non-departing, non-cut, in-scope). Excludes building, territory, and research power.
Optional. Enter other alliances from your server to see where the merged alliance would rank by power. The merged alliance's post-merge power is inserted automatically.
The R5 is the sole leader — only one exists per alliance. The four officer roles (Warlord, Recruiter, Butler, Muse) can only be held by R4 members. Assign these now so the move sequence includes your post-merge officer setup.
Cut priority order (highest first): Inactive members → below minimum power → lower rank (R1 before R2, etc.) → lower power. Core members (★) and assigned role holders are always protected. Alliance A members shown as Remove (active action); Alliance B members shown as Left behind (they simply don't move).
Generated from your roster data. Only Alliance B members are described as moving — Alliance A stays open and receives them. The B leader is second-to-last to leave B; they promote a successor immediately before departing. The successor is the last to leave, at which point B dissolves automatically.
A summary of everything above in a copyable format. Share in Discord, alliance chat, or with your officers before merge day.
Add members and assign roles to generate the merge plan.