Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove duplicate word #253

Merged
merged 1 commit into from
Nov 7, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/other/moderation.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This page contains information targetted at Discord moderators.
- **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.
- **Staff tickets:** User requests like receiving _Contributor_/_Modder_ role should be 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
Expand Down