Skip to main content

​
How events work

Events are individual misery behaviors — auto responders, snipe, link reposting, and so on. By default they run everywhere. If a feature doesn’t fit a particular channel, you can switch it off there without affecting the rest of your server.
All event commands require the Manage Server permission.

​
Disabling an event

Point it at a channel and name the event you want silenced there.
Syntax
Example

​
Across every channel

Use all instead of a channel to shut an event off server-wide.
Syntax
Example
After ,event disable all, you can still switch it back on in a single channel with ,event enable #channel (event).

​
Reviewing what’s off

Run ,event list for a breakdown of every event currently disabled and where.

​
Clearing everything

,event reset wipes all your disabled-event entries at once, putting every feature back in play.

​
Re-enabling an event

Undo a single channel’s restriction:
Syntax
Example
Or lift it everywhere at once:
Syntax
Example

​
Event reference

​
Bot responses

​
Reaction triggers

Reposting is the most common thing servers scope down — leaving it on in a media channel while disabling it elsewhere keeps chat readable.

​
Disabling commands

Commands work the same way, and can also be switched off for a single member:
Syntax
Example
,command enable, ,command list, and ,command reset mirror the event commands above. The server owner and Administrators can still use disabled commands.