Moderation
Raid protection
When a wave of new accounts hits the door, you need a gate β and a latch. ModShield screens joiners and can lock the front door the moment velocity spikes.
- Account age gate
- Avatar requirements
- Latching velocity lockdown
- Operator-controlled lift
Why teams turn it on
Join gate
Kick, ban, or quarantine accounts that are too new or have no avatar β thresholds you set per server, not a one-size global guess.
Velocity lockdown
When joins exceed your rate, lockdown latches and screens every arrival until a human lifts it β raids do not βtime outβ into free entry.
Operator control
You decide the bar for βsuspiciousβ and when the server is ready to open again. The bot enforces; staff command the all-clear.
Pairs with flood defence
Join protection stops the door. Flood filter cleans the people who already got inside with message storms.
How it works
1. Someone joins
Account age and avatar rules run immediately. Accounts that fail the gate never settle into the member list as trusted chatters.
2. Velocity is watched
If joins per minute spike, lockdown engages and stays engaged until lifted β not a brief blip attackers wait out.
3. Staff clear the flag
When the wave ends, you lift lockdown from the dashboard or commands and normal joins resume under your gate rules.
Real situations
Token / bot account waves
Brand-new accounts with default avatars fail the gate while legitimate users with history pass.
Coordinated raid hour
Velocity lockdown freezes the door so mods can clean channels without a firehose of new IDs.
Event launches
Temporarily relax age rules for a big launch day, then tighten again β without rewriting your whole stack.
FAQ
Will real new users get kicked?
Set age low enough for your community, or use quarantine instead of ban. Exemptions and tuning are part of setup.
Does lockdown ban everyone?
Lockdown screens arrivals by your policy until you lift it β it is a latch, not an automatic mass ban of existing members.