Custom Commands — Aegis Docs

Creating One

From the dashboard's Commands page: pick a name (lowercase letters/numbers/hyphens/underscores only), a description shown in Discord's command picker, and the message it replies with. You can also mark it ephemeral so only the user who ran it sees the reply. The name can't be changed after creation without deleting and recreating it.

💡

A custom command is a static reply only. It always says the same thing — there are no variables, no role changes and no conditional logic. If you need any of that, this isn't the tool for it.

Naming Restrictions

You can't reuse the name of any built-in command (/rank, /kick, etc.). The dashboard blocks this before you can save, and the backend double-checks it too. Two custom commands in the same server also can't share a name.

The Response

Every custom command answers with an embed, footed Custom command so members can always tell one from a built-in. You control the title, the message, an optional image and the colour down the side.

To point someone at a channel, use the Link a channel dropdown above the message box. Pick the channel and Aegis drops the link in wherever your cursor is — it shows up as a normal clickable #channel and you never have to go looking for an ID.

The image takes a direct link to a picture, the kind ending in .png or .jpg. Anything that isn't a plain http or https address is ignored rather than sent, because a broken image makes Discord reject the whole embed and the command would answer with nothing at all.

Limits

Each server can have up to 50 custom commands. Discord allows a server 100 commands of its own, counted separately from Aegis’s built-in ones, so 50 leaves half that budget spare. The dashboard stops you at the limit rather than letting a save fail.