Commands
How exceed's command system works — prefix, categories, usage syntax and permissions — plus a link to the full live command reference.
The full command list lives here
exceed has hundreds of commands, and the complete list is generated live from the bot's real catalog so it never goes stale. Browse, search and filter it at the Commands reference — every command, with its aliases, usage and required permission.
This page explains how the command system works so the reference makes sense at a glance.
The prefix
Every text command starts with your server's prefix. The default is , — for example:
,help
,ban @user spamming
,voicetop week
You can change the prefix on the dashboard's General page. If you do, substitute your own prefix everywhere these docs show ,. exceed also responds to @exceed (a mention) as a prefix, which is handy if you ever forget what you set.
Tip: Run ,help for an overview, or ,help <command> to see the usage, aliases and required permissions for any single command.
Slash commands
Most actions are available as Discord slash commands too — type / in any channel and start typing the command name. Slash commands ignore the prefix and give you Discord's built-in autocomplete and argument hints, so they're a great way to discover what's available.
Categories
Commands are grouped into categories that mirror the feature areas in the dashboard sidebar. The live reference is organised the same way, so you can jump from a feature's docs to its commands and back. The main categories are:
| Category | What's inside |
|---|---|
| Moderation | ban, kick, warn, mute, timeout, jail, purge, cases and more |
| Antinuke / Antiraid | server protection, whitelists, lockdown and raid controls |
| Automod | spam, link, word and content filters |
| Config | per-server settings, toggles and setup commands |
| Information | user, server, role, avatar and lookup commands |
| Leveling | rank, levels, leaderboard and XP commands |
| Music | play, queue, skip, filters and player controls |
| Voicemaster | temporary voice-channel controls |
| Roles | reaction roles, self roles, sticky and temp roles |
| Feeds | YouTube, Twitch, TikTok and other social notifications |
| Tickets | support panels and ticket management |
| Fun | games and lighthearted commands |
| Utility | reminders, timers, embeds, AFK and helpers |
Reading the usage syntax
The reference shows a usage string for each command. Read it like this:
<required>— angle brackets mean you must supply this argument.[optional]— square brackets mean the argument is optional.@user,#channel,@role— supply a mention, ID or (usually) a name....— the argument can be a longer block of text (like a reason or a message).
For example, ,ban <user> [reason] means the user is required and the reason is optional, so both ,ban @spammer and ,ban @spammer raiding are valid.
Aliases
Many commands have shorter aliases so you can type less. The reference lists them next to each command — for instance a command might accept ,p as well as ,play. You can also add your own custom aliases per command on the dashboard's Commands page.
Permissions
Each command has default permissions — the Discord permission a member needs before they can run it. Moderation commands typically require Ban Members, Kick Members or Manage Messages; admin-level commands require Administrator or Manage Guild. The required permission is shown in the live reference for every command.
You can override these on the dashboard's Commands page, where you can:
- Disable a command server-wide.
- Restrict a command to specific roles.
- Change the required permission for a command.
- Block a command in certain channels.
Note: Command-level permission overrides are separate from a feature being on or off. If a whole feature isn't responding, check that feature's dashboard page first — most features are disabled by default. See the FAQ for help.
Where to go next
- Browse the full Commands reference
- FAQ — common "why isn't this working?" answers
- Glossary — quick definitions of terms used throughout the docs