Server Command

Each alliance appoints up to four current members as representatives. That opt-in is the boundary for server proposal and notice notifications; alliances that do not appoint representatives are not pulled into the council workflow.

Officers can open proposals with a bounded set of options. Each alliance gets one current ballot, regardless of member count, and can replace that ballot while the proposal remains open. This keeps large alliances from dominating by account volume.

A server operation names the objective, timing and responsibility of every participating alliance. An assignment starts as proposed; the receiving alliance accepts or declines it and later marks it complete. Edits do not resend the same assignment notification.

Season Map Studio gives R4 and R5 officers a shared planning draft for Seasons 1–6 while every alliance member can inspect the plan. Each season uses its real territory types, holding guidance and difficulty scale; the S5 and S6 mega-maps open one warzone or central region at a time so they remain usable on phones.

Choose the season, plot only the cities and route your alliance can realistically capture and hold, then compare the proposed allocation with the season's holding limits. S5 and S6 drafts are clearly identified as your server's proposal across the wider season-group map—not approval from the other warzones.

Live edits and ballot counts refresh for connected participants, but individual votes never repaint the approved map. The whole candidate becomes the current source of truth only after the vote reaches quorum and its approval threshold.

The server board supports structured announcements, recruitment openings and migration notices. Publishers can add a localized title and body for international servers; readers automatically see their matching translation when one is available.