SPUNKY: Using Moderation

With Spunky you have many moderation tools to help you with your community; in this blog post, we will be going over the different options you have, and how to use them.

With Spunky you have many moderation tools to help you with your community; in this blog post, we will be going over the different options you have, and how to use them.


What is moderation?

Moderation can do basic things like edit/delete messages, ban/kick people who violate any rules the moderators put in place, and make sure the Discord guild is a safe, healthy environment for others.

You can see what moderation commands we have and how to use them below!


Moderation Commands

Banning:

To ban a person you will simply need to type in this: !ban <username>[|reason]

Simply put the username you want to be banned and add a reason as to why you did ban them. Banning then will also delete all the user's messages.

If you do not wish to delete the user's messages you can do: softban <username>[|reason]

If you would like to unban a user you can type: !unban <username>[|reason]

Kick:

Much like banning a user, this will instead kick them from the guild, they will be able to rejoin, however: !kick <username>[|reason]

Mute:

This command will mute the specified user in a particular channel (with a given reason if provided), removing the user's permission to send messages in that channel.
!mute <username>[|reason]

And again, if you would like to unmute a user you can type: !unmute <username>[|reason]

Warning:

!warn <username>[|reason]

Issues a strike against the username specified in the command, recording a given reason if provided. This will be added to the modlog, as well as the user's bot profile (viewable with the profile or strikes commands). The user will receive a PM notifying them that they have received a strike and the reason why (if provided).

Tip: strikes can be removed from within the admin console under Management -> Moderation -> Strikes.

Reason:

!reason <case ID> <reason>

This command works with Modlog to set the reason for a particular admin action (e.g. warn, kick, ban, etc), to change the reason, or to add a reason if one was not specified in the initial command.

Modlog:

!modlog enable <channel>
Spunky's moderation logging feature makes it easy for moderators to keep track of why members have been muted, kicked, and banned. It is integrated with other Spunky moderation commands: ban, kick, mute, reason, softban, unban, unmute, warn. Moderation logging works as a full replacement for kick/ban status messages, and stores incidents as cases with reasons for each action. Whenever an incident occurs, the bot will post a message in the channel where moderation logging has been enabled.

Moderation logging may be enabled/disabled from within the admin console under Management -> Moderation -> Logging

Alternatively, the above could be accomplished by a bot admin using the modlog command (modlog enable #testing), without having to log in to the bot's admin console. Likewise, moderation logging may be disabled by running !modlog disable. Individual infractions may be removed from the moderation log by running !modlog remove <case ID>

Nuke:

Deletes messages in a channel, all or from a user. The last x number of messages may be deleted with nuke nuke <search limit> Alternatively, it is possible to remove the last x number of messages containing a word or string: for example, after a series of users spamming the word "noob" in a channel, a bot admin could run !nuke 50 noob to search the last 50 messages in the channel for messages "noob" and delete only those messages. It is also possible to delete all messages within the search limit except those matching :query Another option is to delete all messages from a particular user i.e. !nuke 50 <username>

The final option is to delete a number of messages before or after a specific message, by providing the ID of that message. To allow you to get a message's ID, go to Discord settings -> Appearance and tick Developer Mode.

Imagine there was a spam attack in a channel, followed by users continuing an on-topic conversation. Simply purging the last x messages would also purge a relevant discussion. Instead, we can find the message ID of the last genuine message before the spam attack. If the ID of the above message (copied to clipboard) is '273859885995917313', we can delete the next 20 messages after that message with nuke 20 >273859885995917313.