Custom Commands
Build your own simple slash (and optionally prefix-triggered) commands from the dashboard — a static text or embed reply, no code required.
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 a response — either plain text or an embed (with an optional title and color). 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 — there's no support for placeholders/variables, role changes, or any other action. If you need conditional logic, 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.
Prefix Trigger (Optional)
Turning on Custom Command Prefix (dashboard → Commands → Command Settings) lets members also trigger your custom commands by typing a short text prefix (default example a, up to 10 characters) instead of the slash command — e.g. arules alongside /rules. This only ever works for commands you've created yourself; there's no way to trigger built-in commands like /kick via prefix.
Limits
There's no explicit cap on how many custom commands you can create — the practical ceiling is Discord's own 100-commands-per-server limit, shared with every built-in Aegis command and context-menu action. If you're running close to that combined total, new custom commands may fail to register.