Game Org module · Cross-game

Mission Control — plan your multi-unit operations without ever retyping the briefing

Saturday, 20:54. Your operation starts in six minutes. Two sections on the ground, one mobile section, and the squad leader is explaining for the third time which frequency binds to which ear. Or it's a GTA Online heist, with two assault teams, an extraction driver, a hacker to cover — and nobody knows who's watching the back door. Or a Star Citizen sortie: three ships, crews to assign, a rendezvous point half the fleet never wrote down.

Mission Control is Game Org's multi-unit operation planning tool. You build your milsim op, your heist or your fleet sortie in a four-tab editor — Orders, Personnel, Sections, Logistics — you assign every player to a precise role, and you publish the operation order section by section, independently. Each member gets their personal sheet on screen, with their unit, their authority role, their tactical functions, their instructions auto-injected from your library, and the list of voice channels to bind. No more retyping the org's standards before every op.

Mission Control is the military mode of operation composition. If your org runs MMO raids, the raid planner is the one for you: the twin mode, in guild vocabulary.

A structured editor, not a wall of Discord text

Most tools stop at a text message in a Discord channel. You know who signed up, you don't know who does what. On the day, half your briefing is spent assigning roles by voice while your players burn buffs early and you repeat the same instruction three times.

Mission Control gives you a four-tab editor to build a complete operation order without ever leaving the tool. In Orders, you write the overall directive — we use the military SMEAC format (Situation, Mission, Execution, Administration, Command) because it's designed to cover everything a participant needs without leaving gaps. In Roster, you gather the list of available, confirmed, or reserve members. In Sections, you build the units (your assault team, your medical team, your Alpha squad) and assign each member to their role. In Logistics, you describe the flows between units on a visual graph: who supplies what to whom, which vehicle or ship picks up which payload where.

  • Four-tab editor: Orders / Roster / Sections / Logistics — a single screen, not ten docs to keep in sync.
  • Structured briefing in SMEAC format (Situation, Mission, Execution, Administration, Command) per section.
  • Interactive logistics graph — dependencies between units are visible and drag-editable.
  • Fixed cells: a trio or group that works well gets reused on the next op in one click.
Mission Control editor with its four tabs Orders, Roster, Sections, Logistics and the per-section unit grid
Preparation and sections in the same rail: an op is built without ever leaving the screen.

Two axes per player: who commands, who does what

A twenty-five-person operation isn't "twenty-five people on the same level". There's an operation lead, section leaders, a logistics officer. And each of them also has a field function: pilot, engineer, medic, support gunner. The two axes are orthogonal — your best medic can also be a section leader. Same structure on a GTA op, an Arma mission, a Star Citizen sortie: hierarchy and function intersect but never merge.

Mission Control separates these two axes explicitly for every member assigned to a unit. The authority role (unit leader, second, assault lead…) builds the chain of command, propagated automatically onto every player's sheet by following your org chart. The tactical function (pilot, engineer, artillery, medic, radio operator…) triggers auto-injected instructions from your function library: you write the org's standards for a role once ("as section leader, you switch to frequency 2 on first contact"), and on every op where a player holds that role, the notes are added to their sheet.

  • Two axes per member: command role (hierarchy) + tactical function (what they do).
  • Chain of command computed from your org structure — every player sees it on their briefing.
  • Function library: directives tied to a role auto-inject on every op.
  • No more retyping your standards: they live in a library, never in a scrolling Discord.
A player card in the editor showing their authority role (section leader) and tactical function (medic), with auto-injected function notes
Command role + tactical function: two axes that build a player's personal briefing.

Publish section by section, personal briefing per player

When the op is ready, you don't have to publish everything at once. Mission Control lets you publish each section independently: your assault team is ready at 8:05 PM, you publish it, its members get their briefings. Your logistics group is still negotiating a replacement, you wait — nothing is blocked, the rest of the op keeps moving forward.

Each published section triggers two synchronized outputs: a clean Discord embed in the op's channel, with the unit summary, its members, its roles, and its section-specific directives; and the personal briefing for each player (their individual order) available in their Game Org space. The player finds their unit, their position in the chain of command, their tactical functions with the attached directives, and — if your org uses TeamSpeak — the voice channel binding modal.

  • Publish section by section independently — no need to wait for the whole op to be locked.
  • Automatic Discord embed in the op channel on every section publication.
  • Personal briefing per player: unit, chain of command, tactical functions, auto-injected directives.
  • Impersonation view for leads: check one of your men's briefings before signing off on the op.
Section publication view with the Discord embed and a player's personal briefing side by side
Publish per section: the Discord embed and the personal briefing go out in parallel.

A shared tactical map that moves live

A written operation order is no substitute for a diagram. Mission Control ships a tactical map: your zone background, your unit tokens, and a briefing broken into steps — approach, assault, exfiltration — that you run through like slides.

It is collaborative in real time: several leaders can build it at once, every move is merged and rebroadcast to the others. A member who opens it read-only watches it take shape, without waiting for a screenshot export.

When it's time to explain, presentation mode clears the interface and leaves three tools that steer attention while you share your screen: an ephemeral pencil whose stroke erases itself, a ping that points without drawing, and a spotlight that lifts one unit out while dimming the rest.

  • Sequences and steps: a briefing unfolds, it doesn't fit on one image.
  • Simultaneous editing, merged server-side.
  • Visible live even to those only watching.
  • Ephemeral pencil, ping and spotlight while screen-sharing.
  • Export to share outside the app.
Mission Control tactical map: unit tokens placed on a zone background, sequence and step panel, presentation toolbar.
The operation diagram is built together and read in steps, instead of being described over voice.

Your voice channels, computed for each player

On a multi-unit op, the general voice channel saturates immediately. Command needs to talk to group leads without the whole fleet hearing; the medical team wants to coordinate with HQ without disturbing the assault. That's what whisper lists do on TeamSpeak, and that's exactly what Discord can't do natively. Many orgs running large ops keep TeamSpeak for precisely this reason.

Mission Control automatically generates each player's voice configuration from the operation order. On their personal briefing, the player opens the Radio Binds modal and finds the list of channels to bind to their Whisper keys: Alpha-HQ (reason: escalation to command), Assault-Medic (reason: healing/assault coordination), each with the target unit's logo and the exact channel name. One click copies the name, they paste it into TeamSpeak. No wiki to maintain, no screenshot that goes stale.

  • Whisper lists generated automatically from the chain of command and inter-unit links.
  • Per-player configuration: each member sees only the channels they need to bind.
  • Copy-to-clipboard on each channel — one click, it's in the clipboard, ready to paste into TeamSpeak.
  • Discord stays perfect for simple ops; Mission Control forces nothing, you pick your voice tool.
Radio Binds modal in a player's sheet: for each linked unit, the TeamSpeak channel to bind and the reason for the link
Radio Binds: the voice configuration generated from the operation order, personalized for each player.

FAQ

Frequently asked questions

Does Mission Control work for anything other than Star Citizen?

Yes — it's built for any multi-unit operation: GTA Online heist, Arma milsim op, Star Citizen fleet, EVE expedition, and so on. The core of the product — four-tab editor, two-axis roles, function library, publication by section, personal sheet per player — is fully game-agnostic. For MMO raids you want the twin mode, the raid planner: same rigour, guild vocabulary. Per-game add-ons then bring in what only makes sense in one universe (see the Mission Control Star Citizen question below).

How does a player get their mission order once published?

As soon as the op lead publishes a section, each player accesses their personal briefing directly in Game Org. They find their unit, their roles, their position in the chain of command, the directives auto-injected from the function library, and the Radio Binds modal if your org uses TeamSpeak. In parallel, a section summary gets posted as a Discord embed in the op channel, with the member list and their roles.

Do I have to use TeamSpeak for whisper lists?

No. The Radio Binds modal is a bonus, not a requirement. For a simple op, Discord is perfectly enough and the modal just doesn't show up. For large multi-unit ops where the need for closed secondary channels is real, TeamSpeak becomes relevant again — and that's where Mission Control saves a lead from spending an hour distributing the config to twenty-five players.

Can I reuse the setup from a previous op?

Yes, that's what fixed cells are for. A pilot/lead/support trio that works well, a well-oiled medical team, an assault team that always runs together: you save them once as a fixed cell and reuse them in one click on the next op — Mission Control drops them into the editor with their roles pre-assigned. The function library, for its part, follows players automatically wherever they're placed.

What's the difference with Mission Control Star Citizen?

Mission Control is the multi-game foundation shared by every org. Mission Control Star Citizen is an add-on that brings in whatever only makes sense in the Star Citizen universe: the game's ship catalog, each player's personal hangar along with the org-wide fleet, and the ability to assign ships to present players then distribute them across the different seats of multicrew ships (named turrets, engineering, bridge, etc.). If you play something other than Star Citizen, this add-on doesn't concern you — the Mission Control foundation is enough to run your ops.

And how does it look in practice?

See how Game Org takes shape inside your guild.

Cross-gameRecruitmentDiscord-first candidate pipeline, returnee detection, configurable integration path.Explore Cross-gameWelcome BotYour recruits onboard themselves on Discord — your flows, your questions, the right role assigned automatically.Explore Cross-gameHuman resourcesPromote, validate, decorate, benchmark — in a single tooled console.Explore Cross-gameAbsencesTwo-click declaration, availability by group, and an engagement score that stops punishing the people who warn you.Explore Cross-gameTrainingCourse catalog, registration workflow, chained prerequisites, in-app learning material.Explore Cross-gameSkillsMembers × skills matrix, fully custom hierarchy, automatic promotion, evaluation rights scoped by role and section.Explore Cross-gameEvents & calendarPlan once, publish to Discord, bidirectional signups — in a single tool.Explore Cross-gameRaid plannerFrom declared characters to rosters, then to a tactical map narrated live — raid prep from end to end.Explore Cross-gameInsightsA command cockpit in six angles: engagement, members, operations, sections, decisions, events.Explore Cross-gameMiraYour Game Org copilot: a real face teaches you the app on video, an AI guides you day to day — and knows your whole org with Premium.Explore Cross-gameDiscord SyncYour members already live on Discord. So do your roles, your announcements, your signups.Explore Cross-gameSecurityGranular rights, per-org tenancy, no password to steal.Explore Add-on Star CitizenStar Citizen FleetDigitize hangars, aggregate collective power.Explore Add-on Star CitizenMission Control Star CitizenFrom the briefing to every gunner's brief — operations built seat by seat.Explore

Ready to run your next op without losing an hour on the briefing?

Create your Game Org space for free, structure your org, build your first mission. Discord auth, no member signups to manage, total isolation between orgs.