Overview#
Custom commands are the answers you find yourself typing twice a week. Write one once and it replies for you, either as a command members run on purpose or as a trigger that fires on plain chat.
A prefix command is typed deliberately: .rules returns your rules. A text trigger watches conversation instead, so somebody asking how to verify gets the answer without having known there was a command for it.
The reply is plain text or a full embed, and usage is counted so you can see which ones earn their place.
Setup#
- Open the dashboard and go to Server > Custom Commands.
- Press Create Command.
- Choose Prefix command or Text trigger under How is it triggered?
- Enter the Command name, or the Trigger words and when they should fire.
- Write the Response, or fill in the embed fields for something richer.
- Restrict it with Allowed roles if not everybody should be able to use it, then save.
Settings#
Commands#
Permissions#
What it looks like#
Tips and gotchas#
A custom command shadows a built-in one.
Built-in commands win. Pick a name Iris does not already use, and check /help if you are unsure.
The trigger fires on bot messages.
It does not. Only member messages are checked.
Can a command take arguments?
No. The reply is fixed text or a fixed embed, the same every time.
Can I stop a command working in one channel?
Add that channel to the ignore list in command management, which covers every command at once.