Skip to main content

Members directory

The members directory is the alliance roster — everyone in your alliance, with rank, profile data, power-history chart, train history, and per-event positions over the last 8 weeks. It also handles the messy reality that not every in-game player has signed up for the platform yet, via placeholder members.

Real and placeholder members

Most alliances have 50+ members, and at any given moment a chunk of those haven't signed up for Last Command directly. Officers still need to track them — donations, attendance, hero builds — so the platform lets you create placeholder members that look and behave like full members but don't need a real account behind them.

Placeholders show up in the directory, the Pulse leaderboard, donation rankings, Desert Storm rosters, and everywhere else a member can appear. The only flows they don't participate in are the auth-gated ones: they can't self-edit a profile or receive notifications, because there's no account to sign in with.

// NOTE

For everything officers care about — donations counted, attendance tracked, performance scored — placeholders are first-class members. Pulse, metrics, and at-risk lists all include them.

Try it

// LIVE DEMO · SAMPLE DATA
Alliance members
Member

Aurora_M

· You

R5·145M

R4

VexNova

R4·124M

R4

IrisStorm

R4·115M

R3

PaxBlackline

R3·93M

R3

KadeOnline

R3·95M

R3

LyraVox

Away · Travelling — back 2026-05-02

R3·88M

R3

RuneCallow

R3·78M

R2

JunoClipse

R2·82M

R2

Sable_X

R2·70M

R1

ArcSeven

R1·65M

D(

DustRanger (placeholder)

Placeholder

R1·54M

O(

OrinHale (placeholder)

Placeholder

R2·79M

A read-only mount of the production roster with twelve sample members — including two placeholders and one on declared absence. The search box, rank filter and previous-members toggle all work; the officer-only edit menus are hidden in this demo.

What's in a member profile

Each member page (real or placeholder) shows:

  • In-game name, rank, alliance tenure
  • Power level, HQ level, primary squad type, preferred role
  • Power history chart — power-level snapshots over time
  • Weekly availability grid (set by the member)
  • Train history — how many days they were conductor / VIP
  • Event history — best position and total score in the last 8 weeks of VS, Marshal's Guard, Zombie Siege and donation rankings

Hero data is also collected per member, but it's surfaced on a dedicated alliance-wide Hero Roster page rather than a per-member roster — officers usually want to ask “who has Murphy at SS+5?”, not “what does one player run?”.

Managing the roster

  1. 1

    Add a member

    R5/R4 use the Add member button. For players who haven't signed up yet, choose placeholder — they get an in-game name and rank, and you can fill in the rest of the profile yourself.

  2. 2

    Bulk import from a screenshot

    On Pro, upload a screenshot of your in-game alliance roster and the platform extracts names, ranks, and power levels into placeholder profiles in one shot. Saves an evening of typing.

  3. 3

    Send invites

    Generate invite codes from Settings → Invites. Members who join via an invite link are auto-linked to a member record. R5/R4 can also invite specific players directly.

  4. 4

    Mark someone as on break

    Set an absence on a member with a reason and end date. Pulse's at-risk list will exclude them with a “On break” note above the list, so officers don't accidentally pursue someone who's already explained.

Merging a placeholder when a player signs up

When an in-game player you've been tracking as a placeholder finally signs up to Last Command, an officer merges the placeholder profile into the new account. The merge keeps all history (donations, attendance, hero builds) attached to the real account. Until the merge happens both records exist side-by-side; they aren't auto-matched on name to avoid collisions.

// TIP

See the placeholder members page for a deeper walkthrough of the merge flow and edge cases (renamed players, players who left and rejoined, etc).