Sloth Lee for
Gaming servers.
Built for the rooms that go from 50 to 5,000 overnight.
Gaming communities scale unpredictably — a streamer mentions you, a tournament starts, a clip goes viral. Sloth Lee's defaults are tuned for this: stay quiet when nothing's happening, scale up cleanly when 200 people show up at once, and never embarrass you with a chatty bot that mods can't tune down.
What this audience tends to struggle with
- Raid waves when a streamer raids in or a clip drops on Twitter — your AutoMod has 30 seconds to tell newcomers from bots.
- Hot-take culture in the meta channels — heated debate is fine, slurs and pile-ons aren't, and your mods need consequence ladders that don't depend on who's online.
- Voice-channel chaos during launch night — text channel needs a calm anchor while voice is loud.
- Spike of new members who don't read the rules — verification gate that's friction-light but not bypassable.
The toolkit, framed for gaming servers
Raid protection
Sliding-window join-rate detection. When join rate spikes 10× in 60s, lockdown rolls automatically. Reverts itself once the pattern subsides — your mods don't have to manually unlock 20 minutes later.
AutoMod with sentiment
Pattern matching for slurs and known phishing URLs. VADER sentiment scoring escalates pile-ons before they hit your mod team. Review queue lets you approve/reject borderline calls without taking action automatically.
Verification gate
Members react to the rules channel to grab @member. Customisable: optional captcha, optional account-age gate, optional invite-link tracking so you know who funnelled them in.
Audit log
Every moderation action timestamped, attributed, and queryable. When the post-incident retro asks 'who timed out who at 02:14', you have the answer.
Tickets for tournaments / disputes
Member-initiated ticket flow with category routing. Tournament admin gets the dispute, support team gets the access issue, mod team gets the ban appeal.
A 5-step setup
1. Add the bot
Click Add to Discord, grant permissions on the gaming server. Sloth Lee posts a one-message intro in #general so members see the new presence.
2. Run the setup wizard
Dashboard → Setup wizard. ~5 minutes. Picks raid protection thresholds, sets AutoMod sensitivity to 'medium', wires audit log to a private mod channel.
3. Pick your three rules
Use the rules-channel template (linked from the wizard). Be kind / Stay on topic / Don't spam — with examples. Pin the message; React 👋 to grab @member.
4. Test the raid drill
Dashboard → Tools → Raid drill. Simulates a 100-member burst against a sandbox channel. Lets you confirm AutoMod and lockdown both fire correctly without an actual raid.
5. Set the mod escalation
Three timeouts before the ban kicks in. DMs the offender on each step so they know the floor. Mods can override mid-ladder for severe cases (slurs → immediate ban).
Most gaming servers get a usable baseline in under 30 minutes. The rest is tuning — a different AutoMod sensitivity for #general vs #tournament-chat, a stricter verification gate during a sponsored event, a quieter audit log channel during the off-season. The toolkit's there; the philosophy's calm.