Documentation

What custom commands are

A custom command is a reply you design on this dashboard: some text, up to 10 embeds, or both. When someone runs it, Sirius sends that reply, filling in live data like the current arbitration or the name of whoever ran it.

Hey {user.mention}! Arbitration is on {arbitration.node} ({arbitration.tier} tier), ends {arbitration.ends}.

Commands are made per server (anyone with dashboard access to it) or bot-wide by the bot owner (they work in every server and in DMs). If a server has a command with the same name as a bot-wide one, the server's wins there.

Your first command

1. Open your server → Commands → New command. You can start from a template (Sortie, Fissures, Baro…) or from scratch.
2. Name it. Lowercase, no spaces, e.g. arby. The description shows in Discord's command list.
3. Write the message in Message text and/or the embed. Click in any box to insert a placeholder.
4. Check the preview on the right. It's made by the bot itself with live data, so it's exactly what Discord will get.
5. Publish. Until then it's only a draft (autosaved). After publishing, run /c name:arby in Discord.

How people run them

Functions: When · Only if · Do

Every command is a function: When something happens (someone runs the command) → Only if some checks pass → Do some steps, in order. A plain command is just one step: “Send a message”. Add more steps to post in another channel too, show one of Sirius's own embeds, react, or clean up after a while.

Later steps read earlier steps' results as {steps.name.result}, where the name is the step's name (shown on its header, like send). For example {steps.send.link} is a link to the message step “send” sent.

Triggers

Buttons & role menus

A Send a message step can have up to 5 buttons and a role menu. A button can run a function (from the Buttons group), give / take a role, count (+1 into {vars.name}), open Sirius's own Set reminder / Set tracker, or open a link. Buttons can have a cooldown per person. They keep working after Sirius restarts.

Variables: the Set a variable step (and counter buttons) remember a value per server; use it anywhere as {vars.name}.

Checks (Only if)

Checks run top to bottom; the first one that fails stops the function. Each check has an Otherwise: stop quietly, or stop and reply with a short text only they can see (a DM for message functions; leave it empty for a sensible default). Message functions can also delete their message - the riven-channel template does exactly that for anything that isn't a screenshot.

Steps (Do)

Where a message goes: Reply · Reply only they can see · Same channel · A chosen channel · DM them. “Reply only they can see” works for commands. A function sends at most 5 messages per run, and a server can have up to 50 functions.

Builds (/build)

The Builds tab of a server keeps its loadouts: what the build is for, the aura or stance, exilus, up to 8 mods (with ranks), arcanes and archon shards, plus notes, other names and tags. People pull them up in Discord with:

The editor suggests warframes, weapons, mods and arcanes from the game data and checks the build as you type: mods that don't fit, exilus-only mods, the same mod twice, capacity (a rank-30 item with a reactor or catalyst, plus the aura's bonus). The checks are notes - they never stop you saving. Bot-wide builds work in every server; a server's own build with the same name replaces it there.

Functions can use builds too: the Show a build step posts one, compares two, or only looks one up so later steps can use {steps.build.found}, {steps.build.mods} or {steps.build.has}.

Text & embeds

A reply can have message text (normal chat text) and up to 10 embeds (the boxes with a coloured stripe). Both support Discord markdown: **bold**, *italic*, [link](https://…), `code`, > quote, # heading.

Only visible to them (on the command) makes the reply ephemeral: only the person who ran it sees it. The ⧉ button on an embed duplicates it.

Placeholders

A placeholder is a name in braces. When the command runs, it's replaced with a value.

• Dots go deeper: {user} is a name, {user.mention} pings them, {user.avatar} is their picture.
• Unknown names stay as written. {usr} is sent as the text "{usr}", so a typo is visible. The editor lists unknown names under the preview.
• Times like {sortie.ends} are Discord timestamps: everyone sees them in their own timezone.

You don't need to memorise names: the button and the Placeholders panel in the editor list everything available, including your parameters. The full list is in the Reference.

{user} checked the sortie: {sortie.boss}, ends {sortie.ends}.

Filters

Filters change how a value looks. Add them inside the braces after a |. You can chain several; they run left to right. Some take a setting after a colon: text goes in quotes.

{target.name | upper}
{amount | default: "1"}
{price | number} platinum
{name | trim | title}

Parameter basics

A parameter is a question the command asks when it runs: who?, which item?, which boss?. Its name becomes a placeholder: a parameter called target gives {target}, {target.mention} and more, depending on its type.

Every parameter also gives {name.given}: yes when the person filled it in themselves, empty when they didn't (even if a fallback was used). Use it to react to "nothing picked"; see Show things only sometimes.

Parameter types

The type decides what people enter and which placeholders you get. p below stands for your parameter's name.

You said: {msg}

{amount} × 20 = {if amount > 5}a lot{else}not much{end}

{hours | round: 1} hours

{if loud}**{msg | upper}**{else}{msg}{end}

{boss} drops {boss.shard} shards

{build}: {build.note}

{user} hugs {target.mention}!

{role} has {role.members} members

Moved to {where.mention}

{it.name}: {it.price | default: "not tradable"}

{node} is {node.tier} tier, next arbitration {node.next}

Image: {pic.url}

Choice & Long list

Both let people pick from a list you write. The difference is size and how they pick:

Each row has three parts

Title: {build}
Description: {build.note}
Big image: {build.image}

Filling it in quickly

Use Paste many rows at once: one row per line, parts separated by |, in this order: Label | value | column 1 | column 2…. Tabs work too, so you can copy cells straight from a spreadsheet.

Saryn Prime | saryn | Spores build | https://…/saryn.png
Mesa Prime | mesa | Peacemaker | https://…/mesa.png
Rhino Prime | | Tank | https://…/rhino.png

Allow any text (Long list)

Normally, text that isn't one of the rows is refused with "Couldn't find…". With Allow any text on, it's accepted as it is: {p} is what they typed, the extra columns are empty, and {p.found} tells you which case you're in (yes = it matched a row).

{if build.found}{build}: {build.note}{else}No build called “{build}” yet.{end}

Conditions

A condition is a yes/no question like "was a target picked?" or "is the boss Nira?". They're used by every tool in the next section. In conditions you write names without braces.

Show things only sometimes

There are four tools, from smallest to biggest. All of them use a condition.

{if} in text

Write {if condition}, the text, and {end}. Optionally add {elif another condition} and {else} in between.

{if target.given}Hey {target.mention}!{else}Hey everyone!{end}
That is {if amount > 10}a lot{elif amount > 1}a few{else}just one{end}.

Only show a field / an embed

Write the condition in the box; when it's false, the field or embed is left out. Example: an embed with Only show this embed if… set to boss.value == "nira" only appears when Nira was picked. Tip: a field whose value comes out empty is left out automatically, so often you don't even need a condition.

Own message text (an embed's text)

Turn on Own message text in an embed and write a text there. Whenever that embed is shown, its text is sent instead of the normal message text, so the two come as a pack. Combined with Only show this embed if… this is how you condition the message text: e.g. an embed shown only when boss.value == "nira" can bring its own "Nira is up!" text. If several shown embeds have their own text, the first one wins. An embed can even be just a text (no title or fields) to act as a conditional message.

Situations

A situation is a whole other message (its own text and embeds) plus a condition. When the command runs, situations are checked left to right and the first one whose condition is true is sent. If none match, the Default message is sent. Up to 10 per command.

Tip: Copy the default message here starts a situation from what you already have.

Lists & loops

Some data is a list: the fissures open right now, the sortie's 3 missions, Baro's inventory. To show a list, write the part for one entry once, between {each x in list} and {end}. It's repeated for every entry, and x (any name you like) is the current entry.

{each m in sortie.missions}{loop.index}. {m.node} — {m.type}
{end}

Which fields an entry has (node, type…) is listed in Warframe data. Put {else} inside to say something when the list is empty.

Picking and ordering entries

Add options after the list name, each after a |:

{each f in fissures | where: f.steel_path | sort: f.tier_num | limit: 3}{f.tier} {f.node} — {f.mission}
{else}No Steel Path fissures.{end}

Handy extras

Repeating fields

Instead of a loop inside one field, you can make one field per entry. Open a field → Repeat / show only if and fill in Repeat this field for each… with x in list. Use {x…} in the field's name and value.

Repeat for each:  m in sortie.missions
Field name:       {loop.index}. {m.node}
Field value:      {m.type}

The list options work here too, e.g. g in fissures | group: g.tier makes one field per relic tier.

Preview & testing

• Live preview is made by the bot with the same code it uses in Discord. Turn Live data off to see your raw template.
• Test values are pretend answers for your parameters, only for the preview. Change them to check every case.
• Under the preview, notes tell you about unknown placeholders, missing test values, and which situation your test values pick.
• Send a test posts what's in the editor to a channel, published or not.

Drafts & publishing

• Your work is autosaved as a draft a few seconds after you stop typing, even if it has errors. Save draft saves right away.
• Publish checks everything and makes it live in Discord. If something's wrong, the problems are listed and your work stays in the draft.
• Editing a live command doesn't change Discord until you publish; the list shows Unpublished changes. Discard changes goes back to the live version.
• New commands that were never published are listed under Drafts on the Commands page.
• History (in the editor's side panel) keeps the last 25 published versions and what changed in each. Restore puts an old version back in the editor as unpublished changes - publish it to make it live again.
• Export / import on the Functions page downloads every function as a file, or reads one back in (from a backup or another server). Imported functions come in as drafts, so nothing goes live until you check their channels and roles and publish them.

Slash commands & access

• Real slash command also registers the command as its own /name, with real options. Server administrators can turn it on for their server's commands (only that server gets it); only the bot owner can for bot-wide ones.
• It can't use the name of one of Sirius's own commands. Discord can take a moment to show a new slash command.
• Who can edit: the server's administrators, plus roles they allow on the Access tab.
• Replies can ping users, but never @everyone, @here or roles.

All placeholders

Always available, in every command. Your parameters add their own (see Parameter types).

You & the server

Time

Arbitration

Sortie

Archon Hunt

Baro Ki'Teer

Cycles

Circuit & Coda

Warframe data

More data you can read, updated live. list means it has several entries: use it with {each}; the last column is what each entry has.

Arbitration

Sortie

Archon Hunt

Fissures

Invasions

Nightwave

Bounties

Baro Ki'Teer

Steel Path

Cycles

Circuit & Coda

Sirius

Times come in four forms: ends ("in 2 hours"), ends_time ("18:00"), ends_date (full date) and ends_unix (a number, for sorting and comparing).

Emojis & pictures

The editor's placeholder panel lists every emoji and picture available.

Limits & auto-fit

Discord's limits apply to what's sent (after placeholders and loops are filled in). Sirius fits it for you:

Recipes

Colour from a placeholder:  {boss.color}
Thumbnail:                  {boss.image}
Title:                      {boss} drops {boss.shard} shards

Repeat for each:  d in arbitration.days
Field name:       {d}
Field value:      {each a in d.arbitrations | where: a.tier_rank >= 4}{a.starts_time} {a.tier_emoji} {a.node}
                  {else}nothing B+{end}

{if it.tradable == "Yes"}Lowest sell: **{it.price | default: "none online"}**{else}Not tradable.{end}

Templates

Every template on the New command page is a complete, working example; several rebuild Sirius's own commands:

Troubleshooting

A placeholder shows up as {something} in Discord.

That name doesn't exist (a typo, or a parameter that was renamed). The preview lists unknown names. If it may be missing on purpose, add | default: "…".

A field or embed is missing.

Its value came out empty (an empty list, or an {if} that was false), or its "only show if" condition is false.

"Couldn't find … for build".

The Long list has no such row. Add it, or turn on Allow any text.

My condition does nothing.

Conditions use names without braces (target.given, not {target.given}). For choices, compare .value: boss.value == "nira". The ✨ button writes it for you.

The preview shows a different message than the tab I'm editing.

The note under the preview says which situation your test values pick; change the test values or open that tab.

I can't publish.

The errors are listed at the top of the editor. Your work is safe in the draft meanwhile.