Skip to main content

Server directory

The server directory lists every alliance on your in-game server that's also using Last Command and has opted in to the public listing. Useful for treaty discovery, recruitment scouting, and seeing who's growing fastest in your region.

How it works

Each alliance card shows the basics — name, R5 leader, member count, total alliance power — alongside your own alliance's current relationship with that alliance: active NAP, pending treaty request, or none. R5/R4 see one-click action buttons (Request NAP / Propose peace treaty) on cards where the relationship is none.

Other servers appear collapsed below — click to expand and load that server's alliances. Useful when scouting before a cross-server event or planning a recruitment migration.

Try it

// LIVE DEMO · SAMPLE DATA

// EXTERNAL

Servers

Browse alliances on your server and across Last War. Reach out for non-aggression pacts or propose cross-server peace treaties.

Server 4815

Home·5 alliances

Last Command Sample

#LCS
Members
50 members
Power
4.8B
R5
Aurora_M
This is your alliance

NorthlineSyndicate

#NLS
Members
50 members
Power
6.9B
R5
TundraOrev

ScarletDawn

#SCD
Members
49 members
Power
4.3B
R5
RionMavros
No agreement with this alliance

// OTHER SERVERS · 2

The actual production view, running against a sample 4815 server with five alliances — including one active NAP, one pending inbound treaty request, and one with no relationship. Viewer rank is set to R3, so officer-only request actions are hidden in this demo.

Opting in (and out)

Public listing is opt-in per alliance. R5 toggles it from Settings → Server directory. When opted out the alliance simply doesn't appear here — same as if it weren't on Last Command at all. Toggling back on takes effect immediately.

// NOTE

Active NAPs are listed publicly by default since they influence diplomacy across the server, but each individual NAP has a “hide” flag so officers can keep sensitive arrangements off the public chip list.