Discord Moderation Guide - Revision history

NCommander: /* Workflow */

2023-01-18T03:50:49Z

Workflow

2023-01-18T03:49:40Z

Workflow

← Older revision		Revision as of 03:49, 18 January 2023
Line 6:		Line 6:
	* Do moderation with YAGPDB		* Do moderation with YAGPDB
	* Use Tickets for documenting actions, and talking to people		* Use Tickets for documenting actions, and talking to people
	* Try to ~~de-escalate~~ as is possible		* Try to avoid escalating as is possible

	== Moderator Permissions ==		== Moderator Permissions ==

2023-01-18T03:49:25Z

Workflow

← Older revision		Revision as of 03:49, 18 January 2023
Line 3:		Line 3:

	== Workflow ==		== Workflow ==
			* Work through bots
			* Do moderation with YAGPDB
			* Use Tickets for documenting actions, and talking to people
			* Try to de-escalate as is possible

	== Moderator Permissions ==		== Moderator Permissions ==

2023-01-13T20:24:16Z

Bots

← Older revision		Revision as of 20:24, 13 January 2023
Line 47:		Line 47:

	=== Tickets ===		=== Tickets ===
			Tickets handles requests coming into the server. Right now, we just have a modmail ticket system which allows anyone to open a request to talk to the modteam. Moderators can discuss a report in depth, add other people who were there with "/addmember", and otherwise manage modteam/server affairs.

	=== SlashBot ===		=== SlashBot ===
Line 52:		Line 53:

	=== PluralKit ===		=== PluralKit ===
			PluralKit is available for members to use as they see fit, although excessive use of PK is discourages. PluralKit uses webhooks to allow a user to appear as multiple accounts (which show up with the bot label). By sending a "?" reaction to a PK message, you can see what actual Discord account sent the message.

	== Actions ==		== Actions ==

2023-01-09T13:55:12Z

Warnings

← Older revision		Revision as of 13:55, 9 January 2023
Line 73:		Line 73:

	[https://docs.yagpdb.xyz/commands/all-commands Full syntax] is available on the YAGPDB documentation page.		[https://docs.yagpdb.xyz/commands/all-commands Full syntax] is available on the YAGPDB documentation page.


	Warnings exist as an administrative function of the server, they do not have any penalty in and of themselves, but may influence further moderator decisions down the line. This is why warnings have to be documented. It's not uncommon that a user may need to have bad behavior corrected on more than one occasion. Documenting that warnings help the staff to understand where the rules need to be clarified, or be more stringent, as well as allowing for a way to handle disruptive behavior.		Warnings exist as an administrative function of the server, they do not have any penalty in and of themselves, but may influence further moderator decisions down the line. This is why warnings have to be documented. It's not uncommon that a user may need to have bad behavior corrected on more than one occasion. Documenting that warnings help the staff to understand where the rules need to be clarified, or be more stringent, as well as allowing for a way to handle disruptive behavior.

2023-01-09T13:53:25Z

Kicks

← Older revision		Revision as of 13:53, 9 January 2023
Line 112:		Line 112:
	</pre>		</pre>

	Kicking should be used as a last resort to bans. Like warnings and mutes, kicks should be done through the bot and documented the same. A warning should also be applied to make record of the kick in ~~'''~~/listwarnings~~'''~~		Kicking should be used as a last resort to bans. Like warnings and mutes, kicks should be done through the bot and documented the same. A warning should also be applied to make record of the kick in /listwarnings

	Kicks, by their nature, can't be appealed; you just need to rejoin the server, and any new user filtering such as rules review must be redone. It also resets the join date.		Kicks, by their nature, can't be appealed; you just need to rejoin the server, and any new user filtering such as rules review must be redone. It also resets the join date.

2023-01-09T13:53:14Z

Kicks

← Older revision		Revision as of 13:53, 9 January 2023
Line 112:		Line 112:
	</pre>		</pre>

	Kicking should be used as a last resort to bans. Like warnings and mutes, kicks should be done through the bot and documented the same.		Kicking should be used as a last resort to bans. Like warnings and mutes, kicks should be done through the bot and documented the same. A warning should also be applied to make record of the kick in '''/listwarnings'''

	Kicks, by their nature, can't be appealed; you just need to rejoin the server, and any new user filtering such as rules review must be redone. It also resets the join date.		Kicks, by their nature, can't be appealed; you just need to rejoin the server, and any new user filtering such as rules review must be redone. It also resets the join date.

2023-01-09T13:51:22Z

Warnings

← Older revision		Revision as of 13:51, 9 January 2023
Line 81:		Line 81:
	If necessary, moderators can capture a log from the bot on behalf of another user.		If necessary, moderators can capture a log from the bot on behalf of another user.

	Warnings may be appealed by a user by submitting a ticket.		Warnings may be appealed by a user by submitting a ticket. Furthermore, after an extended period, a user may request that their warning record be expunged.

	=== Timeouts/Mutes ===		=== Timeouts/Mutes ===

2023-01-09T12:46:44Z

Actions

← Older revision		Revision as of 12:46, 9 January 2023
Line 132:		Line 132:

	Server moderators may use the Discord ban function if message deletion is needed to combat spam attacks due to it being easier to use than YAGPDB.xyz slash commands. The audit log must be filled out, and a note must be left in enforcement action that it was used.		Server moderators may use the Discord ban function if message deletion is needed to combat spam attacks due to it being easier to use than YAGPDB.xyz slash commands. The audit log must be filled out, and a note must be left in enforcement action that it was used.

			Bans, like all other mod actions may be appealed through email or DM with a moderator. A ban may be downgraded from a lifetime ban to a temporary ban, or a temporary ban may be shortened.

	=== A Note On Message Deletion ===		=== A Note On Message Deletion ===
			By and large, messages should only be deleted if they violate the Discord TOS, and to preserve context. Users may delete their own messages, and mods may request this, however, its generally worth filing a note if nothing else.

2023-01-08T21:26:30Z

Bans

← Older revision		Revision as of 21:26, 8 January 2023
Line 121:		Line 121:
	Bans are the highest level of action a moderator can take, and can extend past Discord and include things like a wiki account, Patreon access or more, depending on severity. Bans are also used as a method to combat raids, and with combined with the Discord security level, provides key tools in keeping the server usable in times of strife and more.		Bans are the highest level of action a moderator can take, and can extend past Discord and include things like a wiki account, Patreon access or more, depending on severity. Bans are also used as a method to combat raids, and with combined with the Discord security level, provides key tools in keeping the server usable in times of strife and more.

	Bans are classified into anti-spam, and as a punishment for rules violations. Bans may be time limited, or may be ~~permamement~~.		Bans are classified into anti-spam, and as a punishment for rules violations. Bans may be time limited, or may be permanent.

	Ban should be done YAGPDB ban command, which is a slash command.		Ban should be done YAGPDB ban command, which is a slash command.