Moderation Best Practices¶
This guide covers recommended moderation workflows, auto-mod configuration, and escalation strategies for Armory Bot.
Prerequisites¶
- permission or higher
- Logging configured (recommended — see Logging Setup)
Membership Monitoring Quick Start¶
Use this short flow for streamlined membership and role-monitoring workflows.
-
Grant command access:
-
Review members for a role:
-
Export the same list as CSV when needed:
-
Assign or remove roles:
-
Set or reset nicknames:
Recommended Workflow¶
Escalation Ladder¶
A clear escalation path keeps moderation fair and consistent:
| Step | Action | Command | When |
|---|---|---|---|
| 1 | Verbal warning | (manual message) | First minor offense |
| 2 | Formal warning | /mod warn |
Repeated minor offense |
| 3 | Timeout | /mod timeout duration:60 |
Continued disruption |
| 4 | Kick | /mod kick |
After timeout, still disruptive |
| 5 | Temp ban | /mod tempban duration:7d |
Serious violation |
| 6 | Permanent ban | /mod ban |
Severe or repeated violations |
Logging Every Action¶
Always provide a reason with every moderation command:
/mod warn member:@username reason:"Spam in #general — first warning"
/mod timeout member:@username duration:60 reason:"Continued spam after warning"
Reasons are stored in the mod case system and visible in audit logs.
Auto-Moderation¶
Configure automated moderation rules to catch issues before moderators need to act.
Auto-moderation policy settings are managed through the Dashboard/API moderation configuration routes in the current command surface.
Auto-mod supports multiple rule types with configurable actions:
| Rule Type | What It Catches |
|---|---|
| Spam detection | Repeated messages, message flooding |
| Link filtering | Unapproved links and invite spam |
| Word filter | Blocked words and phrases |
| Mention spam | Mass mentions of users or roles |
| Caps filter | Excessive capitalization |
Rule Action Responses¶
Each auto-mod rule applies a configured enforcement action and logs the event:
- Delete only
- Timeout
- Kick
- Ban
Warning System¶
How Warnings Work¶
Warnings accumulate per member. Use thresholds to trigger automatic escalation:
Clearing Warnings¶
Remove a specific warning:
Clear all warnings for a member:
Bulk Actions¶
Purge Messages¶
Delete messages in bulk:
Nickname Intervention¶
Set or clear nicknames when needed for moderation and impersonation cleanup:
Role Management At Scale¶
Review members for a role with a compact, readable embed:
Export the same result when needed:
These monitoring commands require Admin permission or Manage Server permission.
Apply role changes with existing role commands:
/mod addrole member:@username role:@EventParticipant reason:"Event enrollment"
/mod removerole member:@username role:@Muted reason:"Post-incident cleanup"
Channel Lockdown¶
Lock a specific channel during an incident:
For full-server lockdown operations, administrators can use /server lockdown and /server unlockdown.
Mod Cases¶
Every moderation action creates a case entry you can review later:
Cases include: action type, moderator, target, reason, timestamp, and any related messages.
Best Practices¶
- Be consistent — Apply the same rules to everyone. Document your escalation policy.
- Always log a reason — Future moderators need context for past actions.
- Use timeouts before bans — Give members a chance to course-correct.
- Configure auto-mod for common issues — Let automation handle spam so moderators can focus on judgment calls.
- Review mod cases regularly — Spot patterns like repeat offenders or overzealous moderation.