Discord is the chat. Last Command is the coordination.

Most R5s arrive at Last Command after the same three problems pile up:

• Scrolling for data. “Who said they were going on holiday last week?” Scrolling chat for ten minutes to find the answer. There's no structured member record in Discord — every fact is buried in a message.
• Spreadsheets that don't sync. A Google Sheet that gets pasted screenshots from chat, transcribed by hand, then linked back into chat. Three steps where every step loses fidelity.
• Coordination latency. Officers in different timezones editing the same DS roster with no source of truth. A change made at 11pm UK time gets overwritten by an officer in Singapore who pulled an old copy.

Last Command is explicitly not a Discord replacement. We don't want to host your alliance's chat — chat is what Discord is great at. Voice channels for big DS coord sessions, memes in the off-topic channel, recruitment posts in the public area, late-night strategy debates — all stay on Discord.

The structured coordination layer. Concretely:

• Member profiles with attendance, donations, hero builds, and absences — searchable, filterable, and attached to every event the member played.
• Desert Storm match pages with a drag-and-drop building planner, sign-up tracking, role balancing, and post-match attendance.
• Event leaderboards for Marshal's Guard, Alliance Duel, Zombie Siege, donations, General's Trial, and the Shield Board. Pasted in Discord today; structured in Last Command tomorrow.
• Reminders that fire 60 minutes before every Desert Storm match and train slot, via push, email, in-app, or Discord (Pro).
• Officer Pulse, the weekly scorecard that surfaces who's drifting and who's climbing — backed by data, not memory.
• Diplomacy records: NAPs and treaties with other alliances, with expiry reminders three days before they lapse.

On the Pro plan, R5 can wire a Discord webhook into Last Command in about a minute. Once it's set up, alliance announcements you write in Last Command post automatically to the Discord channel of your choice, with optional @-mentions for any member who's linked their Discord ID to their profile. Desert Storm match-lifecycle events (created, signup requested, completed) also fan out to Discord automatically.

Personal reminders — the 60-minute heads-up before your DS match or train slot — deliberately go via push and in-app by default rather than Discord, so the alliance channel stays signal-heavy. Members can flip them on per category from My Hub → Notifications. Setup steps in Discord integration.

For an alliance running both Discord and Last Command, the split is straightforward: Discord stays the chat, Last Command becomes the source of truth for anything structured.

• Daily chat: Discord. Banter, voice for big coords, recruitment.
• Event results: Last Command. AI scanner from a screenshot, results structured against member profiles. Webhook posts a summary back to Discord on Pro.
• DS roster: Last Command. Real-time officer collaboration on Pro, 30-second auto-refresh on Free, both sides see the same map.
• Reminders: Push and in-app to members, Discord webhook to the alliance channel for big events.
• Promotion debates: Last Command for the data, Discord voice for the actual conversation.

The lowest-risk way to introduce Last Command is to add it as a parallel layer for one event type — usually Desert Storm, since that's where coordination overhead is highest. Run DS in Last Command for a few weeks, keep Discord exactly as is, see whether your officers want to move more events over.

Most alliances we've worked with end up using Last Command for every event tracker plus DS, and Discord for chat plus voice. Members link their Discord ID to their profile, the webhook posts announcements back to chat, and nobody has to leave the platform they're already in.