-
Notifications
You must be signed in to change notification settings - Fork 123
Bot management (disabling commands)
CarlGroth edited this page Sep 4, 2018
·
3 revisions
| Name | Aliases | Args | Example | Usage |
|---|---|---|---|---|
| !ignore | -- | [channel] [command] [subcommand] | !ignore #general temp home | If no channel is specified, the current channel is ignored. If only a command is supplied, the command and all of its subcommands will be ignored in the specified channel. If everything is supplied, only the subcommand will be ignored in the specified channel. Mod (manage server) will bypass all of these. |
| !ignore server | -- | -- | -- | This will ignore all channels and is future-proof. |
| !ignore all | -- | [command] [subcommand] | !ignore all pc top | This is equal to typing !ignore channel command subcommand in all channels the bot can see, useful if you want to ignore a command in all channels except for one. This will not work for channels created in the future. If the command is already ignored in a channel, this will unignore it. |
| !unignore | -- | [channel] [command] | !unignore #general temp | Reverses what !ignore does |
| !unignore all | -- | -- | -- | Unignores all channels (this does not take ignored commands into account) |
| !disable | -- | command [subcommand] | !disable pc top | This really disables the command globally from the server, not even manage server bypasses this. |
| !disablemany | -- | command [subcommands...] | !disablemany "pc top" cat dog "tag get" | Like !disable except it takes more than one command |
| !enable | -- | -- | !enable pc top | Enables a previously disabled command. |
| !enablemany | -- | command [subcommands...] | !enablemany "pc top" cat dog "tag get" | Like !enable except it takes more than one command |
| !enable all | -- | -- | -- | Sets all commands to enabled. |
| !disable all | -- | -- | -- | Sets all commands to disabled. |
| !enable mod | -- | -- | -- | Enables all moderation commands |
| !disable mod | -- | -- | -- | Disables all moderation commands |
| !enable list | disable list | -- | -- | Shows all enabled/disabled commands. |
| !plonk | -- | member [command][subcommand] | !plonk @Carl#0080 tag create | This works almost exactly like !ignore but for users instead. If no command is specified, the user is banned from using the bot completely. |
| !unplonk | -- | member [command][subcommand] | !unplonk @Carl#0080 | Unbans the user from using the bot |
| !plonks | -- | -- | -- | Displays all plonked users. |
| !restrict | -- | command [subcommand] | !restrict define | This requires a bot channel to utilize. Makes it so that if the command is used outside of the bot channel, the bot will ping the user in the botchannel and give the results there instead. |
| !unrestrict | -- | command [subcommand] | !unrestrict d | Unrestricts it. Like all commands where you pass in a command, aliases work just as well. |
| !modonly | -- | command | !modonly echo | Makes a command usable by mods only |
| !unmodonly | -- | command | !unmodonly dog | Removes a command from the modonly list |
| !modrole | -- | role | !modrole bot commander | Makes it so that any member with the specified role is seen as a moderator by the bot, this means being able to invoke any command in bold on this page. Only exception to this is the !ban command which still requires the member to be able to ban the target normally. |