Discord Moderation Guide

DisNCord uses a large set of moderation tools, and guidelines to ease the burden of server administration. The intent is to make moderation quick and easy to review, while still being able to handle large scale raids and other server events are handled. At the moment, this document only covers the Discord server, but should probably be expanded in time to cover YouTube, Fediverse, and this wiki.

Bots

To aid staff, and moderations, as well as improve the general user experience, multiple bots have been added to DisNCord; here's an overview, combined with how they interact with moderation.

YAGPDB.yxz

Yet Another General Purpose Discord Bot or YAGPDB.yxz handles most of the basic moderation tasks on the server, as well as handling stream announcements, incident longing and more.

At the moment, YAGPDB is responsible for the following

• Streaming Announcements
• Fun/Community items such as reputation, customs commands and more
• Warnings
• Flexible Timeouts/Mutes
• Kick/Ban logging, and Notification DMs
• Deleted Message logging

While YAGPDB.yxz does offer a ticket system, its somewhat difficult to use, and requires bot commands, so we're not using it as such.

SlashBot

SlashBot handles mostly role selection, and is used in #role-select. It will likely be used in the future for premium configuration options and more. It might be replaced in the future with a simpler bot, or with YAGPDB replacing it.

Actions

Moderators on DisNCord can take various actions in regards to tickets and incidents. Actions, unless noted, should be done through either Tickets or YAGPDB as is necessary.

Note

Sometimes a ticket comes in, or a borderline action is witnessed, that warrants an official comment from a moderator, but doesn't reach the point that an actual warning should be raised.

In these cases, a ticket should be opened by the moderator, and pull in any relevant offending users. If a moderator is acting on another ticket, the reporter should not be pulled in. Exposing a reporter of an issue opens them up to retaliation; a moderator speaking in a ticket is speaking on behalf of the server. Any relevant conversation should be held, and then the moderator should close ticket should be closed with a comment explaining why no action was taken. The log will be saved.

These actions represent "we talked to someone about X", and will essentially be forgotten if the issue doesn't come up again