Horizon Docs
Custom Commands
Create advanced non-slash prefix commands from the dashboard.
Feature guide
Custom Commands
Create advanced non-slash prefix commands from the dashboard.
What it does
- Creates normal prefix commands such as !rules or ?info without registering a slash command.
- Lets each command send a normal message, a Discord embed, or both together.
- Includes per-command permissions, optional role and channel restrictions, cooldowns, aliases, trigger deletion, replies, controlled mentions, a live preview, embed fields and media, and up to five link buttons.
- Supports placeholders that are replaced when a member runs the command.
How to configure it
- Open Dashboard → your server → Configure → Custom Commands.
- Enable the feature and press Create command.
- In Command, choose the prefix, command name, and optional aliases.
- In Access, choose who can use it, optional allowed roles or channels, cooldown, reply behavior, trigger deletion, and mention behavior.
- Choose Message, Embed, or Both. The editor only shows the sections used by that response type.
- Build the response in the Message, Embed, and Buttons sections while checking the Discord preview on the right.
- Save changes, then run the prefix command in an allowed Discord channel.
Good to know
- Custom Commands creates prefix commands only. It does not create slash commands.
- Selected-role access is strict: server owners and administrators do not bypass the selected roles.
- Supported placeholders include {user}, {mention}, {username}, {display_name}, {user_id}, {server}, {server_id}, {member_count}, {channel}, {channel_name}, {channel_id}, and {args}.
- User and role mentions are disabled unless Allow user and role mentions is enabled. @everyone and @here are still blocked.
- A server can store up to 100 custom commands. Prefixes may be up to 8 characters with no spaces, and command names and aliases use letters, numbers, hyphens, or underscores.
- Links used for titles, images, icons, or buttons must start with http:// or https://.
Common check
If something does not work, check these first: Horizon has the needed Discord permissions, the bot role is high enough, the channel still exists, and the right staff roles are selected in Configure.