Custom commands

Custom Commands turn the answers your team gives over and over — the rules link, support hours, how to apply — into commands anyone can call on demand. Define them once; members pull them up whenever they need them.

Beta — tested, but still young.

Add a command

1. Enable the Custom Commands plugin in the Plugin Market.
2. On the Custom Commands page → Add command:
   • a trigger (e.g. !rules, apply, socials), plus optional aliases (up to 15)
   • a match mode — Exact (the default), Whole word, Substring, Wildcard or Regex
   • a reply text (up to 2,000 characters, Discord markdown), plus an optional embed title — set it and the reply is sent as an embed
   • a per-user cooldown in seconds (default 3, 0 = none, up to 3,600)

How it works

These are not Discord slash commands. Members type the trigger as a normal message (e.g. !rules), and CloudMod replies to it. The answer is always identical and current, and never depends on a moderator being online. The per-user cooldown stops anyone from spamming a command to flood the channel.

Replies can use variables: {user} (pings the member, plain-text replies only), {username}, {channel}, {#channel-name} and {server}. @everyone and role mentions never ping.

Custom commands vs auto-responses

• Custom commands are deliberate — a member calls them by name. Use them for "give me the info I asked for."
• Auto-responses are automatic — they trigger themselves when a message matches a pattern. Use them to "react when someone mentions X."

They complement each other; many servers run both. If a trigger is also an Auto-Response trigger, both fire and the member gets two replies — the dashboard warns you about this.

Setup notes

• Only admins define commands, so the list stays intentional. Up to 50 commands per network.
• One list covers your whole network; restrict a command to specific servers with Where active.
• Requirement: Send Messages, Read Message History and (for embed replies) Embed Links in the channels where commands are used.