Templates & Recurring Ops¶

Set your weekly ops up once and stop rebuilding them every Friday afternoon.

Templates¶

A template is the shape of an op saved for reuse: its groups, roles, vehicle slots, description — plus where it announces and who it pings.

Find them under Events & Ops → Event Templates, or from Discord:

Command	What it does
`/templates`	List the templates you can use — 🌐 global, 🏠 your server's
`/create_template <name> [description]`	Start a new template, then build it out with buttons
`/create_event <template> <title> <time> [date]`	Launch an op from one; `time` is required (e.g. `20:00 UTC`), `date` defaults to today

The reply to /create_template is private, and only you or an officer can use its builder buttons.

Global templates

Templates marked 🌐 ship with Star Org Labs — common op shapes you can use straight away. Your own 🏠 templates stay private to your server.

Announcement routing¶

Each template can carry its own events channel and ping roles. Every way of creating an event honours them — web wizard, bot command, recurring schedule, roulette — falling back to your server default when the template leaves them blank. If you leave Ping Roles untouched, the template pings your server's default roles. Clearing the selection sets the template to announce without pinging anyone, and Use server default switches it back.

Voice comms¶

A template also carries the op's voice comms choice — Discord, Star Comms or both — and, for Star Comms, a Meet Up net and a net per team (an existing one or a new one by name). Every event made from the template, including recurring and roulette runs, gets the same choice; a template only plans new nets — each event creates its own on the shard. A new Meet Up net needs a name: Save stays blocked ("Name the new Meet Up net") until you give it one. See Running an op on Star Comms.

The editor also has a Meet Up channel picker: the voice channel ops from this template muster in before launch. Leave it on Server default to use your server's Meet Up channel.

Building a template on the web¶

Sections. The editor groups its fields into The Basics, When & Where, Announcements and Behaviour & Voice. Collapse a section you're done with and its header shows a one-line summary. In Basic mode the less-used fields — the poster image, the events-channel override, auto-share orgs and alliances, and extra voice channels — sit behind More options, which says how many of them are set. A template that already uses one opens with it showing.
Basic or Advanced is remembered from your last choice. In Basic, an asset with nested sub-assets or crew roles says how many are saved, with Show advanced to see them.
Location unlocks once you pick a System; the events-channel override shows which channel the server uses by default.
Event shape. In a multi-game server, pick Fleet, Roster or RSVP. An RSVP template has no teams — just going, maybe and can't — so it saves with only a name. Switching a fleet template to RSVP drops its teams when you save. Changing the game or the shape away from Roster also clears the Mythic+ requirement, which only a roster template can hold. The Signups choice (open or curated) sits in the roster section, beside the Mythic+ score.
A game your server switched off. A template already tagged with a game, or set to Roster or RSVP, keeps the Game and Event shape pickers even after your server drops to one game, so you can move it to the game you still run or to Shared / no game.
Meetup Offset must be filled in: use 0 for no muster period. Clearing it used to save 30 without telling you.
Reminders. A new template uses the server's reminder times.
Why Save is greyed out, and any reason the server turned the save down, show in the box above the buttons. The server's reason clears once you change something.
Live Preview sits beside the form on very wide screens and under it everywhere else. It shows your server's default pings when Ping Roles is untouched, and none when you've cleared it.
Nothing is lost by accident. Closing a template you changed asks first. A new template is kept as a draft for this server: Create Template brings it back, and Discard draft clears it. If you switch servers while the editor is open, it closes, so nothing from one server gets saved into another. The draft stays with the server you started it in.
Template cards count units by amount: a team with four Prospectors on one line shows 4 units, the same number the event wizard shows.

Recurring schedules¶

A recurring schedule posts an event automatically on a cron schedule. Manage them on the Recurring tab of the Events page, or from Discord.

On the web, Create Schedule walks you through five short steps:

What runs: a name, plus one template or a rotation between missions. With no templates yet, it says so and links to Templates.
When: daily or chosen weekdays, a time, a timezone and how far ahead the event posts, or a cron expression. You see the next three runs before you save.
Mission vote: only for a rotation: whether members vote, when the vote closes, the officer window and auto-confirm. A close time the vote could never reach is caught here.
Where it posts: the announce, vote, ops-board and ping destinations are listed. Open Change channels and pings to change any of them.
Review: your answers grouped by step, each with Edit and Back to review. Start the schedule as soon as it is created is here too; turn it off to create it paused.

The labelled steps along the top show where you are. If you close the wizard partway through it asks first, and your answers are kept as a draft: the next Create Schedule offers Resume draft or Discard draft. To change an existing schedule, use Edit on its card, which still opens the single form.

From Discord:

Command	What it does
`/recurring list`	Your schedules
`/recurring create <name> <cron> [days]`	Create one. `cron` is a cron line (minute hour day month weekday) in UTC, e.g. `0 20 * * 5` is Fridays 20:00 UTC. To schedule in your own timezone (and follow daylight saving), use Create Schedule on the web instead.
`/recurring add_template <id> <template>`	Attach a template to a schedule
`/recurring toggle_active <id>`	Pause or resume
`/recurring skip_next <id>`	Take one night off — the schedule keeps running
`/recurring unskip_next <id>`	Changed your mind; put that night back

days is how far in advance the event posts (default 2 days), so members have notice.

A schedule can override the template's announcement channel and ping roles, which means one template can serve several schedules that each shout in a different place.

Planning queue¶

Want Friday to be Siege of Orison, then Tech Smugglers, then whatever wins the vote? Open the Event Planner (Events & Ops in the sidebar, or Open planner on a schedule card) and line the next few weeks up.

Pick a schedule at the top. Each row shows the date the op is projected to run on.
Upvote the ops you want. Votes are advice for officers, not a draw — tap again to take yours back.
Officers can add an op from any template (with a title, description or notes just for that night), drag rows to reorder, pin an op to a specific date, remove it, or hit Sort by votes once to put the most-wanted first. The queue holds up to 26 ops.
Each run takes the top of the queue. Once an op is created it shows 🔒 and can no longer be moved or voted on; if the event is cancelled before it starts, the op goes back to the top.
Dates you are skipping show as Skipped, and a date that already has a member vote open shows as Voting — the queue leaves both alone.
History (collapsed at the bottom) lists what ran, what was cancelled and what was removed.

The queue comes first

While anything is queued, the schedule runs the queue instead of opening a vote or spinning the roulette. Roulette and polls pick again as soon as the queue is empty.

If two people change the queue at once — a drag, an add, a pin, even a vote — the second change is refused and the planner reloads the latest queue, so nobody silently overwrites anyone else. Just redo it.

Everyone sees the "queue comes first" note on the planner when the schedule would otherwise vote or spin. Queued ops that have not been created yet also appear on the org dashboard's calendar as dashed planned entries — click one to open the planner. They turn into normal events once the schedule creates them.

If Trigger now can't create the queued op, you'll see "Nothing was scheduled; try again" — the queue is unchanged, so it's safe to retry.

A schedule can also keep an Upcoming ops board posted in a Discord channel: pick an Upcoming Ops Board Channel when you create or edit the schedule.

Mission Roulette¶

Attach several templates to a schedule, turn roulette on, and each occurrence draws one at random. Nobody knows if Friday is bounty hunting or salvage until it posts.

Command	What it does
`/recurring toggle_roulette <id>`	Random template per run
`/recurring toggle_poll <id>`	Let members vote on the draw
`/recurring polls`	Live tallies for open polls
`/recurring one_off <name> <templates> <date> <time>`	A one-night roulette with no schedule behind it

Letting members vote¶

With polls on, members vote on the template pool ahead of the run — from the poll board on the Events page or straight from a Discord select menu. Votes weight the draw rather than deciding it: a template with three votes is likelier, not guaranteed. An officer confirms (or overrides) the drawn mission before the event is created, and an auto-confirm fallback handles the nights nobody gets to it.

Keep voting chatter out of your announcements

Roulette polls can post to their own channel, separate from where events announce. If a poll gets buried under newer messages, it can be reposted at the bottom of its channel automatically — off by default, since not every org wants the bump.

Next: Events & Ops · Loot Hub