Custom commands

Create prefix commands that reply or send a configured message.

Before you start

Sign in and select a server you can manage. April must be in the server and able to read commands and send messages in the relevant channels, with embed or attachment permissions where needed. Role hierarchy matters only for separate role features; see hierarchy. Check the server’s prefix.

Create and use

1. Open Administration > Custom Command, create a command, and enter a name and optional aliases and description.
2. Add Reply with message or Send message actions; select a destination channel for the latter. Compose content and configure role and channel permissions, then enable and save.
3. If the prefix is ! and the name is rules, send !rules in an allowed server channel. Check the resulting Discord message; the editor preview alone does not send it.

Non-premium servers can create up to 20 custom commands. Triggers are case-insensitive and consist of the prefix plus exactly one space-separated command or alias word; command parameters are not supported. The Worker executes at most the first three actions even if the editor permits four. Hiding a command from the public list does not prevent execution. Use formatting variables supported by the command’s context.

Local setup: name and describe the unsaved command.

Local setup: configure the initial reply action.

Settings

Setting	Effect and creation-form default
Enabled	New commands start enabled.
Command and aliases	The name and each alias are case-insensitive triggers; aliases start empty.
Role and channel permissions	Allow mode requires a match; deny mode excludes matches. New forms start in deny mode with empty lists.
Public visibility	The command starts visible in the public list. Hiding it removes it from that list but does not disable its trigger.
Actions and random messages	Reply in the invoking channel or send to a chosen channel. Random selects one configured message for that action; without it the action uses its configured message. The initial action starts with random and private reply off. Only the first three actions run.

Change or troubleshoot

Edit, disable, or delete the command from the list. If the list is empty, create one; wait for loading and retry failed saves after checking access. If no response appears, check the prefix, spelling, enabled state, role/channel restrictions and April’s channel permissions. For a send action confirm that its destination still exists. Discord delivery failures can prevent output; correct access before retrying.

Before setup, see sign in and select a server. For maintainers, see the administration technical record.