Discord integration

1. 1

   Add Last Command to Discord

   Use the Add to Discord button on the Discord bot page. Choose a server where you have Manage Server permission.

2. 2

   Generate a link code

   In Last Command, open Settings → Discord and generate a short-lived bot link code. This is different from the alliance member join code.

3. 3

   Link the server

   In Discord, run /lc link code:YOUR-CODE. The code anchors the server to the alliance and links the officer who minted it.

4. 4

   Choose the notification channel

   Pro alliances run /lc channel and choose where automatic posts should appear. Give the bot View Channel, Send Messages and Embed Links there.

5. 5

   Run the guided check

   Run /lc setup. It privately checks the server link, officer identity, tested notification channel and member identity adoption.

• /lc help — command overview.
• /lc schedule — upcoming Desert Storm and Canyon Storm matches.
• /lc train — today's conductor and VIP.
• /lc roster — alliance roster overview.
• /lc me — your signup, assignment and train duties.
• /lc signup — the next match signup link.
• /lc invite — post a tracked alliance member invite.
• /lc recruit — branded recruitment card with open roles.
• /lc poll — attendance, safe-time or officer-decision poll.
• /lc claim — claim your in-game roster identity.
• /lc claims — R4/R5 review of pending identity claims.
• /lc match — next match battle plan (Pro).
• /lc pulse — private, actionable R4/R5 summary (Pro).
• /lc briefing — preview or schedule a weekly briefing (Pro).
• /lc report — public branded seven-day report card.
• /lc setup — private guided setup checklist.
• /lc status — link, tier and channel status.

A member runs /lc claim and selects their in-game name from the roster. The bot never treats a typed display name as identity: the selection carries the stable member ID. An R4/R5 officer approves or denies the claim before personal duties and targeted mentions become available.

During initial setup, Manage Server is a narrow bootstrap only while no officer identity is linked. It cannot approve an R4/R5 identity claim, and it closes once an officer is linked.

Pro alliances can post match creation, signup requests, results and officer announcements automatically. Match reminders mention assigned players and provide one-tap attendance buttons. The fire handler always reads current match and member state before posting, so schedule changes do not produce stale instructions.

Members can control personal reminder channels from My hub → Notifications.

Existing webhook connections continue to work for announcement and event posts, but the bot is the recommended setup because it also supports slash commands, identity links, buttons and targeted mentions. You can switch in Settings → Discord.

If you keep a webhook, create it under Edit channel → Integrations → Webhooks, paste its URL into Last Command settings, save, and send a test post. Treat the webhook URL as a secret: anyone who has it can post to that channel.