Last Command 常见问题解答

Last Command is a coordination platform for active alliances. It runs Desert Storm matches end-to-end, scans in-game event screenshots into structured data, generates the weekly train rota, tracks every member's history, and pushes the right notifications to the right officers — all in one screen instead of three spreadsheets and a Discord thread.

Active alliances that take Desert Storm seriously and have outgrown spreadsheets — typically 30+ members with R5 and R4 officers who actually run the events. The Free plan covers small or casual alliances; Pro is for alliances that want auto-scheduling, AI scanning, analytics, and Discord integration.

No — everything works in any modern browser (desktop, tablet, or phone), with nothing to install to get started, no game mod, and no overlay. There is also an optional iOS app. Members use the same Last Command account on web and iOS, so their alliance, profile and subscription stay connected.

Roughly five minutes for an R5 to create the alliance, set the server number and Desert Storm time, and share an invite link. Members trickle in over a few days. The platform pre-creates placeholder profiles for everyone in your in-game roster, so officers can start tracking attendance and donations before every member has signed up.

Not at all — they’re complements. Discord is your chat. Last Command replaces the spreadsheets, screenshots, and tracking grids that get pasted into chat. Most alliances keep Discord exactly as is and use Last Command for event coordination, with announcements optionally mirrored into a Discord channel via webhook.

Yes. No credit card, no time limit, no surprise downgrade. The Free plan covers manual Desert Storm match creation, the building planner, member profiles, the Shield Board, all six event trackers (Marshal’s Guard, Zombie Siege, Alliance Duel, Donations, Shield, General’s Trial), the train schedule view, NAP and treaty management, the season checklist, and safe-time voting. It’s built for alliances that want coordination without paying.

On the web, Pro is £7.99 per month per alliance. The iOS app shows Apple’s current App Store price for your storefront. One subscription covers your entire roster — there’s no per-seat pricing — and the same alliance entitlement works on web and iOS. Cancel through the provider used to subscribe.

Yes. Your login and alliance are the same on web and iOS. Sign in to the same Last Command account and an Apple or Stripe subscription unlocks that alliance on both platforms. If an Apple entitlement does not refresh after reinstalling, sign in first and use Restore Purchases. The original billing owner manages cancellation through the provider used to subscribe.

The Free plan is genuinely usable — no fake feature paywalls — but a few things are narrower in scope so the upgrade path is honest. Match history shows the last 4 Desert Storm matches (Pro: unlimited — page back through everything). The leaderboard sorts by attendance only (Pro: win rate, avg score, total score). The event calendar shows the full in-game week on Free — VS days, Arms Race, shield days, the season schedule, Marshal’s Guard, train slots, and treaty/NAP deadlines (Pro adds your own scheduled announcements and custom recurring events, each with reminders). VS and donation ranking input is capped at 30 entries (Pro: up to 200 — a full roster). Custom alliance guides are capped at 10 (Pro: unlimited). Match-page coordination uses 30-second auto-refresh on Free instead of the WebSocket sync on Pro.

Real-time officer collaboration over WebSockets, Desert Storm auto-scheduling on Friday or Saturday, AI scanning for supported event, roster, mail, and result screens (up to 300 extractions a month, 20 screenshots per scan), train rota auto-generation, full leaderboard sort axes (win rate, avg score, total score), Officer Pulse with at-risk detection, Power Tracker historical charts, Hive Map planning, rich-text Announcements, Discord webhook integration, unlimited guides, and full-roster ranking entries.

Eligible billing accounts can start with a 14-day free trial; Stripe or Apple confirms eligibility and shows the renewal price before you subscribe. Cancel during the trial through the same provider and you won’t be billed. If you continue, the alliance stays Pro at the price shown at checkout. Your alliance data remains intact if the plan later returns to Free.

Your alliance drops back to Free at the end of the current billing period. Pro features (auto-scheduling, AI scanning, analytics dashboards, Discord webhook delivery) stop, but every member, every match, every screenshot extraction, and every score stays exactly where it is. Resubscribe at any time and Pro flips back on.

On Pro, set your Desert Storm day plus separate Team A and Team B start times. Every Monday morning the platform creates both matches in planning state at their configured times, ready for signups. Every assigned starter and substitute receives a reminder at their chosen lead time. On Free you create matches manually — same building planner, same attendance tracking, just no auto-create.

Sixty minutes before each match’s scheduled start time. Reminders go to every player who’s been assigned to a slot or is on the substitute list, via whichever channels they’ve enabled (push and in-app are on by default; email and Discord are off by default and toggle per category in My Hub → Notifications).

The platform auto-creates the Friday match, no one signs up, and the week passes — common enough. From the match page, an officer hits Mark as not played. The match stays visible in history with a muted "Not played" badge but is excluded from attendance stats and Officer Pulse, so members aren’t penalised for an officer-side miss.

Yes — every Desert Storm coordination feature works on Free except auto-scheduling. R5 and R4 officers can create matches manually, build the roster, drag players to building positions, mark attendance, and record results. The match page auto-refreshes every 30 seconds so officers stay in sync without manual reload. Two depth limits to know about: history is capped at the last 4 matches (Pro: unlimited, paged back on demand), and the leaderboard sorts by attendance only (Pro: win rate, avg score, total score, attendance). Plenty for a casual alliance to run weekly DS without paying.

It previews a 20-starter and 10-reserve roster using approved volunteers first, then availability, activity, power, attendance and saved role preferences. It can suggest strategic roles where no preference exists. Strategy Assign then places unassigned starters into a role-aware opening with mobile jumpers and strong/weaker pairs across key buildings. Officers review before applying either proposal.

Drop in a supported game screenshot and the vision model reads player names, scores, waves, damage, signups and roles into a reviewable draft. Screenshot Inbox can classify a mixed batch and route each image to its matching tool. The platform never saves extracted data without an officer’s confirmation.

Supported workflows include Marshal’s Guard, Sandworm Battle, Alliance Duel, Tech Donations, Kills, Zombie Siege, in-game member lists (for placeholder bulk-import), Hero Power lists, Desert Storm rosters and participant mail, and Desert Storm or Canyon Storm result screens. The universal Screenshot Inbox can also classify a mixed batch and route each result to the right review flow.

Around 95%+ on player names and 99%+ on numbers from a clean in-game screenshot. Common failure modes are unusual characters in player names (the in-game font is tight on accented characters and emoji) and very low-resolution captures from older devices. Every extracted row hits a review screen first — the platform never auto-saves scanned data without an officer’s confirmation.

Pro alliances get 300 extractions per month. Each extraction can include up to 20 screenshots, so a long leaderboard counts as a single scan. That’s well above what an active alliance uses even when scanning Marshal’s Guard, Alliance Duel, donations, and Desert Storm results every cycle. The cap exists to keep cost predictable, not to meter normal use.

Auto-generation is opt-in. Enable it and set conductor or VIP rules such as VS rank or donations; the Pro schedule builds each Monday from the latest data. If automation is enabled with no rules, Last Command uses a fair random fallback. If it is disabled, nothing is generated. Officers can override any day or reset the week.

The game uses five alliance ranks. R5 leads and R4s are officers; R3, R2 and R1 are members. Last Command mirrors that control model: officers drive alliance operations, while members use My Hub to follow their week, request Storm places, maintain availability, complete assigned season tasks and track targets and contributions.

My Hub gives every member today’s asks, a seven-day agenda, Storm signup and roster status, train duties, assigned season tasks, readiness, weekly VS and donation targets, announcements, season guidance and last week’s personal standing. Members update their own information and act on the plan; R4/R5 retain alliance-wide controls.

A first-class member record for a player who hasn’t signed up to Last Command yet. Officers create placeholders manually or by AI-scanning the in-game alliance roster. Placeholders show up in Officer Pulse, donation rankings, attendance counts, and the members directory — the only thing they don’t do is sign in. When the player eventually creates a Last Command account, an officer merges the placeholder into the new account and the full history (donations, DS attendance, hero builds, train slots) follows automatically.

The handover is atomic — the full transfer either succeeds or nothing changes. The new R5 inherits every permission, every setting, and the billing context in one transaction. The outgoing R5 is automatically demoted to R4. No partial states, no orphaned access, no data loss.

Five: live in-app collaboration (Pro real-time, Free 30-second auto-refresh), the in-app notification bell, email, web push, and Discord. Each member toggles channels independently from My Hub → Notifications. Defaults are push and in-app on, email and Discord off.

In Discord, go to your channel’s settings → Integrations → Webhooks → New webhook, name it "Last Command", and copy the URL. In Last Command, open Settings → Discord (Pro feature), paste the URL, and hit Send test post. From then on, alliance announcements and Desert Storm match-lifecycle events post to your chosen Discord channel automatically. Personal reminders (your own DS in 1h) deliberately go via push by default so they don’t spam the alliance channel.

Most often it’s notification preferences — push and in-app are on by default but a member may have toggled them off. There’s no officer audit view of personal preferences (privacy), so the conversation has to happen in chat. For email reminders specifically, members need to opt in (email is off by default to keep inboxes clean). If web push isn’t firing, check that the member granted the browser permission when prompted.

Yes — same server or cross-server. Record a one-sided NAP for your own tracking, or send a treaty request to another alliance for a mutual handshake. Both sides see matching records, get a reminder three days before the agreement expires, and can cancel cleanly. It’s the bit no spreadsheet can replicate, and it works on the Free plan.

A NAP (non-aggression pact) is a one-sided record — you’re writing down "we agreed not to attack each other" without needing the other alliance to confirm in Last Command. A treaty is a mutual handshake: you send a request to another alliance on Last Command, they accept on theirs, and both sides get matching records that update together when either side cancels. Use NAP when the other alliance isn’t on Last Command yet; use treaty when they are.

Yes. All data is encrypted in transit (TLS) and at rest (AES-256 via AWS-managed keys). Each alliance’s data is fully isolated — no other alliance can see your members, scores, signups, or strategies. Sign-in uses AWS Cognito with secure password hashing; passwords are never stored in plaintext or visible to our team.

On AWS in the eu-west-2 region (London). Last Command is built and hosted by Instance Labs Ltd, a UK company. We never sell data, never share it with third parties for advertising, and don’t use member data to train AI models.

Yes. Last Command supports both data export and full account deletion (DSAR — Data Subject Access Request) per GDPR. From your account settings, request an export and you’ll get an email with your data; request deletion and your records are anonymised across every service within 30 days. Billing records from Stripe or Apple may be retained where required for financial, fraud-prevention, or legal obligations.

Yes. Last Command is an independent alliance management tool built by Instance Labs Ltd, with no publisher affiliation or endorsement. The platform reads what your officers paste in (screenshots and manual entries) and never connects to in-game APIs.