Custom commands
Key features
Guild-owned slash commands
Create Discord guild application commands with names, descriptions, and behaviour tailored to your community.
Ordered action chains
Each command runs one to four actions, including replies, channel sends, role assignment/removal, and nickname prefix or suffix updates.
Requirements and cooldown
Gate who can run a command by member level, currency balance, or membership age, and add a per-user or whole-guild cooldown. Role and permission access is configured through Discord's slash-command permissions.
Dashboard lifecycle management
Admins create, edit, and delete commands from settings. Nox creates, patches, and removes the matching Discord guild command.
Best-effort action execution
Duplicate interactions are guarded. If a later action fails, earlier Discord effects remain and Nox records the failure on the Errors page.
Best for
Frequently repeated answers, resource links, onboarding prompts, and staff shortcuts.
Lightweight automation where a simple command should perform a few Discord actions.
Communities that want custom slash commands without writing or hosting bot code.
How it works
Build the command
Admins choose a lowercase underscore command name, a description, and an ordered action list. Every command must include at least one reply action.
Nox creates the Discord command
Saving creates or updates the Discord guild application command and stores the command configuration used when members run it.
A member invokes the slash command
Discord sends the command interaction. Built-in commands are checked first, then Custom Commands, then Forms.
Actions run in order
Nox replies or follows up, sends configured channel messages, and applies role or nickname mutations through Discord permissions.
Setup checklist
Choose a command name from 3 to 32 characters using lowercase letters and underscores.
Write a command description from 10 to 100 characters.
Add one to four actions, including at least one reply action.
Confirm reply and send actions contain message content.
Add any requirement gates (level, currency, or membership age) and a cooldown when a command should be limited or rate limited, and set who can see it in Discord's command permissions.
Grant channel, Manage Roles, and Manage Nicknames permissions when actions need those Discord side effects.
Actions, parameters, and requirements
A command runs an ordered list of actions when it is used.
| Action | What it does |
|---|---|
| Reply | Respond to the member who ran the command |
| Random reply | Reply with one of several messages chosen at random |
| Send message | Post a message to a chosen channel |
| Assign or remove role | Grant or take a role from the member |
| Timed role | Grant a role for a set number of minutes, then remove it |
| Nickname prefix, suffix, or clear | Add to, append to, or reset the member's nickname |
| Deduct currency | Subtract an amount from the member's balance |
A command runs one to four actions and must include at least one reply. A reply action can appear at most once.
Parameters collect input when the command is run, and their values can be reused inside actions.
| Parameter type | Collects |
|---|---|
| Text | A free-text value |
| User | A member picker |
| Channel | A channel picker |
| Role | A role picker |
Up to 25 parameters per command, and required parameters must be listed before optional ones.
Requirements gate who is allowed to run the command, and a cooldown limits how often it can run.
| Gate (minimum or maximum) | Checks the member's… |
|---|---|
| Level | levelling level |
| Currency | currency balance |
| Membership age | time since they joined the server |
Add up to five requirements. A cooldown applies per member or to the whole guild, from off up to 30 days. Who can see the command is set in Discord's command permissions.
Important notes
Custom Commands share Discord's guild application-command namespace with Forms and other guild commands, so command names must not collide.
Runtime action execution is best effort. Earlier actions are not rolled back when a later role, nickname, or send action fails.
There are no Custom Commands buttons, select menus, modals, autocomplete, webhooks, DMs, or public HTTP routes.
Deleting a custom command removes the Discord command, saved configuration, and message images owned by reply/send actions.
Dynamic custom commands do not appear as static command prefixes on this page because each guild defines its own names.
Troubleshooting
The command does not appear in Discord
Check for name conflicts or Discord command creation errors. Discord may also take time to make newly-created guild commands visible.
A role action failed
Confirm Nox has Manage Roles and that its highest role sits above the role it is trying to assign or remove. Earlier actions in the chain may already have completed.
A nickname action failed
Confirm Nox has Manage Nicknames and that its highest role sits above the member's highest role. Discord also never lets bots change the server owner's nickname, so nickname actions always fail for the owner.
A stale command remains
Use the guild command resources view to compare Discord commands with custom-command ownership and delete orphaned resources where appropriate.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
