From 306bc9cd3516cc5cc7e978bb0ce844d78472bd82 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Thu, 19 Oct 2023 14:22:28 +0200 Subject: [PATCH] Add initial content for Discord moderation (#216) --- docs/SUMMARY.md | 1 + docs/other/moderation.md | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+) create mode 100644 docs/other/moderation.md diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index da572769..2befa783 100644 --- a/docs/SUMMARY.md +++ b/docs/SUMMARY.md @@ -61,4 +61,5 @@ ## Other +* [Discord moderation](other/moderation.md) * [Credits](other/credits.md) diff --git a/docs/other/moderation.md b/docs/other/moderation.md new file mode 100644 index 00000000..5459e021 --- /dev/null +++ b/docs/other/moderation.md @@ -0,0 +1,18 @@ +# Moderation + +{% hint style="info" %} +This page contains information targetted at Discord moderators. +{% endhint %} + + +## General stuff + +- **Communication:** Communication is key. Any changes and actions should be discussed with other moderators unless they are very obvious (e.g. scambans). + Any changes to permissions etc should be discussed first in `#staff-suggestions`. Any changes performed should also be manually written down in `#changelog` so that everyone is on the same page. +- **Use Dyno:** Use dyno commands to perform actions like mutes and bans. Dyno log is way easier to search than Discord's native audit log and helps us keep track of who did what. +- **Staff tickets:** User requests like receiving _Contributor_/_Modder_ role should be handled handled via staff ticket. This way other moderators can chime in and public channels are not clogged with unnecessary info. +- **Warn liberally:** User warns are stored in Dyno log. They should be performed as a first measure on misconduct. It's better to warn once too many times than ban someone without warning. + +## Useful commands + +- `!scamban UID`: Bans a user with a message telling them that their account has been compromised and has been spreading scam.