Events & Ops¶
Everything that happens between "we should fly Friday" and the after-action report.
An op has four beats: plan it, fill the roster, fly it, close it out. Star Org Labs covers all four — you plan from the web, your members sign up in Discord, and attendance and loot settle themselves.
1. Plan the op¶
Open Events & Ops → Events and create an event. You get a guided wizard that walks you through the mission, and a drag-and-drop board if you'd rather shape the roster by hand — same event, two ways of building it.
An event carries:
- Groups — the squads or wings people join (Alpha, Escort, Salvage Crew…)
- Roles — the jobs inside a group (Pilot, Turret, Medic…)
- Vehicle slots — ships the op needs, which members fill from their Personal Hangar
Prefer Discord? /create_event <template> <title> [date] [time] launches an op from a saved
template. Date defaults to today, time to 20:00 UTC.
Build it once, reuse it forever
Almost nobody builds an op from scratch twice. Save the shape as a template and every future run starts pre-filled — see
Where the announcement lands¶
Each event announces to a channel and pings a set of roles. Star Org Labs resolves that in
order: the recurring schedule's override, then the template's channel and ping
roles, then your server default from Server Settings. So your mining runs can ping
@Miners in #industry while your combat ops ping @Combat in #ops, with no per-event
fiddling.
2. Fill the roster¶
The event posts to Discord as an interactive embed. Members click buttons — join, pick a group, pick a role, bring a ship. Nobody has to learn a command.
| If you'd rather type | What it does |
|---|---|
/events |
List every upcoming op this server can see |
/event <id> |
Post that op's signup embed with all its buttons |
/join_event <id> |
Sign up directly |
/bring_ship <id> |
Sign up and commit one of your ships |
Ship selection reads straight from your Personal Hangar, so "who's bringing the Reclaimer" answers itself.
Not sure when to fly?
Post an availability poll first — Fleet Availability in the sidebar, or
/poll create. It builds a timezone-aware heatmap of when your members can actually
show up, so you schedule around your org instead of guessing.
3. Fly it¶
When it's time, the op runs itself as much as possible.
- Voice channels — the event can create temporary channels for its groups.
/create_vcs <id>makes any that are missing, and they're cleaned up when the op ends. - Gather the crew —
/move_event_crew <id>pulls every confirmed attendee into your current voice channel. - Chase the stragglers —
/start_op <id>pings and DMs signed-up members who aren't in voice yet. - Split and regather — the event's tactical controls on the web split your crew into squad channels and pull them back together for the debrief.
- Auto-launch — if your attendees are sitting in the meetup channel at start time, the op launches on its own.
- Repost —
/refresh_event_embed <id>puts the event back at the bottom of a busy channel.
4. Close it out¶
Attendance is automatic. At each lifecycle step — and whenever you regather — the bot scans the event's voice channels and records who was actually there. That includes walk-ins: people who never signed up but flew anyway are credited too, and listed on the report.
The after-action report. When the op ends, the Mission Lead gets a DM asking for an AAR. Fill in the short web form and it posts to your AAR channel with the attendance attached, and is kept for your org's stats.
Anonymous feedback. If your server has event feedback enabled, the finished event shows a Give Feedback button. Participants leave a 1–5 rating and an optional comment, stored with no link back to who wrote it — officers see only the aggregate on the event card. Use it to find out which ops people actually enjoyed.
Attendance stats. Over time, Events & Ops → Attendance turns all of that into reliability: who shows up, who signs up and vanishes, who quietly carries every run.
Cancelling — and un-cancelling¶
/delete_event <id> (or the web equivalent) cancels an op. It notifies your signups and
tears down the Discord channels, announcement and scheduled event — but it does not
throw anything away. The event, its signups and its attendance all survive; it renders
struck through with a CANCELLED badge, and you can restore it from the web app if the
call was premature.
Flying with other orgs¶
Events can be shared with allied orgs through the Alliance Hub, so a joint op has one
roster instead of three. Members of an allied server see the shared event in /events and
sign up from their own Discord. Events that belong to another org and were never shared with
you stay invisible — an event id from someone else's server simply answers "not found."
Next: Templates & Recurring Ops · Loot Hub · Fleet & Hangar