🗺️

How to Plan a Server Map Together

Server map planning usually becomes a chain of screenshots, exported files and conflicting versions. The Server Map Planner replaces that process with one server-wide workspace. Registered alliance leaders on the same server can work on the same draft, see the latest assignments and publish a view-only link for everyone else.

One live plan for the whole server

Plans are separated by server number. Alliances registered on the same server share that server’s planning workspace, while alliances on other servers have completely independent plans.

Because everyone edits the same live draft, there is no master file to download, rename, upload or send back through chat. The plan shown in the platform is the current version.

Example: alliances registered on Server 1021 can collaborate on Server 1021 plans. An alliance on Server 1022 sees only Server 1022 plans and cannot alter the 1021 workspace.

Create the right seasonal map

Create a new plan and choose the season. The planner includes structured territory layouts for Seasons 0 through 6, including the correct city, stronghold and resource information for each map.

Give the plan a clear name, such as “Season 6 opening route” or “Week 2 territory plan”, so leaders can distinguish drafts when more than one plan is being discussed.

Assign territories collaboratively

Choose an alliance from the territory panel, then select its intended map areas. Alliance colours make ownership and proposed routes easy to compare. Zoom in for precise selections and use Fit map to return to the full overview.

Other authorised alliance leaders on the same server can open the plan and continue editing it. Changes are saved centrally instead of being trapped in one person’s browser or device.

  • Select the correct alliance before assigning areas.
  • Use zoom for crowded or overlapping map tiles.
  • Check city and stronghold totals shown beside each alliance.
  • Clear an incorrect territory by selecting it again or reset the plan when rebuilding.

Keep drafts private until ready

A draft remains inside the logged-in server workspace. Use it for discussion and changes without exposing unfinished plans to the wider server.

The draft owner can delete an unwanted draft. Publishing creates a fixed public snapshot, so later draft edits do not silently change what members were previously shown until the plan is published again.

Share without giving edit access

After publishing, enable the public view-only link and share it through alliance or server chat. Members do not need an account to open the published map.

The public view supports zooming and panning but cannot change territory assignments. This gives the wider server a clear plan while keeping editing with registered alliance leadership.

Avoid conflicting versions

Treat the shared planner as the source of truth. Do not continue editing downloaded screenshots or old copies after the server has moved to the live plan.

When the route changes, update the shared draft, publish the revised version and tell members that the public plan has been refreshed.

Leadership checklist

  • The correct season and server plan are selected.
  • Alliance colours and territory assignments are clear.
  • City and stronghold limits have been checked.
  • The draft has been reviewed by the relevant alliances.
  • The latest version has been published.
  • The view-only link has been shared with members.

Related guides

← All guidesCreate an account