A real mission order, not a Discord post-it
Most tools stop at a Discord message with reservation emojis. You know who signed up, you don't know who does what. The Idris bridge is a gray zone until contact.
Mission Control gives you a four-tab editor — Orders, Roster, Sections, Logistics — to build a real order of battle. You write the directive (Situation, Mission, Execution, Admin, Command), you assemble the available roster, you build units by section (PHOENIX, DRAGON, GRIFFON, CERBERUS), you assign members and ships, and you configure logistics flows between units on a graph. When it's ready, you publish the ORBAT by section: a Discord embed hits the op channel, and each participant gets their OPARD — their individual order of battle — on their personal space, published as readable Markdown.
- Four-tab editor: Orders / Roster / Sections / Logistics — one screen, not ten Google Docs
- Structured SMEAC briefing per section (Situation, Mission, Execution, Admin, Command)
- ORBAT publishing per section independently — push DRAGON without blocking PHOENIX
- Interactive logistics graph: who delivers what to whom, which ship picks up which cargo where
Seat by seat: every turret has its gunner
An Idris-P doesn't have three pilots — it has over twenty stations to man: captain, second, engineering, engine room, and most importantly the named turrets — forward-left laser, forward-right laser, port-flank laser, starboard-flank laser, torpedo station. If you write «Idris: Vega, Sigma, Tango» on Discord, you show up to combat with no one on the turrets. Not three pilots on the bridge: no one on the turrets.
Mission Control lets you configure your own stations per ship and per mission type — each org decides its nomenclature: a mining convoy doesn't need the same stations as a PvP raid, and your escort Idris-P doesn't have the same grid as your neighbor's. Once the grid is set, you drag your members onto specific seats. The assignment engine auto-suggests the right profiles by matching the member's tactical role (gunnery, engineering, piloting…) with the station name.
- Stations configurable by your org — no imposed grid, name your seats however you want
- A different grid per mission type: convoy, PvP raid, escort, exploration
- Drag-assign with suggestions: the member's tactical role matches the station name
- Manning visible in real time: 16/20 stations filled — you see what's missing before start
Three ship sources, one Manifest
Your ships don't all come from the same pocket. For this op, the Idris-P comes from the org pool, your Hercules C2 comes from a member's personal hangar lending it out, and the evac Cutlass Red is an inter-unit loan between your logistics section and your medical section.
The Manifest merges those three sources into a single mission inventory. You see at a glance what's available, what's already committed, and who owns what. For the SC cargo module, each ship shows its remaining SCU capacity as a bar, you assign holds to a supplier and a recipient, and the logistics graph reflects the flows automatically. No more cargo forgotten on a Lorville pad because nobody wrote down we were stopping there.
- Three unified sources: org pool, member personal hangar, inter-unit loan
- SCU capacity visible per ship, per hold, per item category
- Typed holds with supplier and recipient — the logistics graph updates itself
- Preset crews: a pilot/gunner/engineer trio that works reuses in one click on the next op
The chain of command mirrors your org
On a 30-player op, who answers to whom? Who makes the call if the captain goes down? Who can redeploy the escort without asking the fleet commander?
Mission Control splits each member in a unit along two axes: the command role (unit lead, second, etc.) and the tactical role (gunnery, piloting, engineering…). The command role builds the chain of command, which is computed automatically on each player's brief by following your org's hierarchy graph. The tactical role triggers auto-injection of notes from your role playbook: a lead gunner on an Idris automatically receives the standards you wrote once for that role. No more retyping standards for every mission.
- Two axes per member: command role (hierarchy) + tactical role (combat)
- Chain of command computed from your org chart — every player sees it on their brief
- Role playbook: notes/instructions tied to a role auto-inject into the player's brief
- Impersonation view for leaders: see one of your people's brief before validating the op
Your TeamSpeak channels, computed per player
On a multi-unit op, the general voice channel saturates in thirty seconds. Command needs to talk to wing leads without the whole fleet hearing, gunnery needs to coordinate with CP without disturbing logistics. That's exactly what whisper lists do on TeamSpeak — and precisely what Discord can't do natively. Many serious orgs keep TeamSpeak for big ops exactly for this.
Mission Control generates each player's TeamSpeak config from the ORBAT. On their personal brief, the player opens the Radio Binds modal and finds the channels to bind on their Whisper keys: Unit-Gunnery channel (reason: Gunnery → Command link), Dragon-Bridge (reason: fleet coordination), with the target unit's logo and the exact channel name. One click copies the channel name, they paste it into TeamSpeak. No export file to maintain, no wiki wall, no screenshot that's stale by the next mission.
- Whisper lists auto-generated from the chain of command and unit links
- Personal config per player: each one only sees the channels they need to bind
- Copy-clipboard on each channel: one click, and the name is in the clipboard
- Differentiator: Discord has no native whisper — Game Org keeps TeamSpeak usable without overloading a leader with config
FAQ