Custom Commands
Adding predifined messages to your server
To access these settings:
Custom Commands are used to send a predefined response to your channels using a text command. Common uses are FAQs, Help Commands, and/or General information.
The Custom Commands tab shows currently configured Custom Commands and allows you to create and edit Custom Commands.
To create a Custom Command, press the green
+ New
button in the top left corner of the Custom Commands page. When creating a Custom Command, give it a name to identify your Custom Command.
A New Custom Command
- To delete a custom commands click the Bin icon that's next to the command name.
- You can clone custom commands by clicking the Copy icon next to delete button.
You can always set a new name for your Custom Command by editing it on the top left corner of it's settings
You can create groups to categorize your Custom Commands! Type a name in the box to look for already made groups or click in the name you typed to create a new one!
Here you can insert a custom description you had like the command to have, this is only visible on your dashboard and does not affect in any way the output on your Discord server.
If enabled, the user who triggers the custom command will receive the [Message] on it's Direct Messages (DMs)
When enabled, users with a Dashboard Role,
Administrative Permissions
, and the Owner
can trigger this tag.You can choose one of 3 trigger types for your commands:
- Strict
- Wildcard
- Regex
Note that the server's prefix won't affect at all the command trigger!
Trigger Settings
- Enabling the
Case sensitive
will make the triggers check for the specific case you stated. - When enabled, the user’s message that triggered the custom command will be deleted after the message has been sent.
Strict
This type will be triggered by a match of the command trigger, this is the standard trigger formerly known as Tags which now supports the
Case Sensitive
setting.Wildcard
By inserting the
*
character on the trigger, instead of the asterisk, the command will check for any characters, for instance:Fish*
will match any message starting byFish
(orfish
if not case sensitive) e.gFishdom
,Fish11111
, etc...*fish
will match any message ending byfish
, e.gbreadfish
,clownfish
, etc...f*ish
will match messages that start withf
, end withish
and have any characters in between, e.g.friedish
,fbreadish
. etc...
RegEx
This is the most advanced type of trigger type, for most of the uses, we recommend you use the Strict and Wildcard types. For instance we'll provide you with some of the most common use cases you'll find for this type of trigger are:
- Multiple triggers for a single custom command. For example, if your trigger is set to
bread|fish
your command will be triggered by any text starting withbread
or withfish
. - If you want the trigger to only match the start of a string, use the
^
character on the beggining of the pattern.
We suggest you test your RegEx triggers by using sites such as RegExr in which you'll be able to identify which messages will trigger your command. If you had like to learn more about RegEx you can check MDN's RegEx Cheatsheet
RegEx Named Groups
We also support RegEx named groups, which you can access to by using the
{regex.NAME}
or {regex.INDEX}
variables (replacing the name or index but it's value). An small sample of how you can use this feature is shown below:
Dashboard

Output
Make sure to always save changes using the pop-up shown whenever a change is done.
Last modified 4mo ago