Clan In A Box
Discord That Doesn’t Melt
Design your clan once, scale calmly, and keep drama on mute.
Why servers melt (and how to dodge it)
- Everything channel syndrome: 40 channels on day one; nobody knows where to talk; mods can’t find problems.
- Permission spaghetti: ad-hoc roles that contradict each other.
- Onboarding void: new folks say “hi,” get ignored, leave.
- No event loop: activity depends on leader being online.
Good servers are boring in the best way: they’re predictable. People know where to go, what to click, and when play happens.
Blueprint (channels that do work)
Stage 1 — Launch (≤ 12 channels)
#welcome — start here; rules + quick role buttons #announcements — events & releases #general — the main hangout #lfg — “looking for group” with simple form #clips-screens — media dump (ratelimited) #help-desk — tech + game Qs, marked solved Voice: 2 rooms — “Squad A”, “Squad B” Mods: #mod-log (locked), #reports (locked)
Stage 2 — Grow (≤ 18 channels)
- Split lfg by region/time if it’s scrolling too fast.
- Add builds-lab (PC help), looking-to-trade (if the game allows).
- Open a creator-corner for guides and UGC (not live stream links).
Roles & permissions (predictable beats fancy)
Minimum viable roles
- @everyone: read-only in welcome, post in general after onboarding.
- Member: standard posting rights; attach media in media channels only.
- Trusted: can create threads and stage community nights.
- Mod: manage messages, mute/kick; no admin unless lead.
- Admin: server config; 2FA required.
Permission rules
- Grant on roles, not channels, then override only where needed.
- Log every escalate/de-escalate in #mod-log.
- Use role colors sparingly—rank ≠ rainbow.
Onboarding (fast & friendly)
One-screen join
- Welcome message → rules summary → “Accept & Continue” button.
- Reaction roles: region, platform, skill level.
- Auto-DM: “Reply with your favorite mode to unlock lfg.”
LFG form (copyable)
IGN: Region/Time: Platform: Mic? (Y/N) Tonight’s plan (mode/level): Slots open: Notes:
Safety & moderation tools
- Enable server verification (email/phone) and media-scan in image channels.
- Rate-limit: 10 sec slowmode on media channels; captcha on join if raided.
- Auto-mod for slurs/spam domains; quarantine channel for appeals.
- Have a 3-step ladder: warn → temp mute → kick/ban (logged).
- Minors policy: no voice DMs with adults; public channels only.
Incident flow: 1) Acknowledge reporter in-thread (thank + log ID) 2) Preserve evidence (message links / screenshots) 3) Apply ladder (warn/mute/kick/ban) 4) Note resolution in #mod-log (who/what/when/why) 5) If unclear: escalate to admin for final call
Events loop (so the server lives when you’re AFK)
Weekly skeleton
- Mon: help-desk hour (tech/builds).
- Wed: training lobby (beginners welcome).
- Fri: casual tournament (prizes = roles/badges, not money).
- Sun: screenshot showcase + voting.
Runbook
- Announce 48 h prior; pin rules; lock check-in 5 min before start.
- Use threads per team; archive 24 h after.
- Publish recap in announcements with 3 screenshots.
Culture & rules (short, enforceable)
Server rules (v1.0) 1) Don’t be a jerk. Attack ideas, not people. 2) Keep content PG-13 in public. 18+ channels are opt-in and mod-visible. 3) No slurs, harassment, or dogpiles. Zero tolerance on doxxing. 4) No spam links or crypto/promo DMs. Report within server, don’t “name and shame.” 5) Respect platform TOS and local laws. 6) Mods apply the ladder (warn → mute → kick/ban). Appeal in #appeals.
Metrics that matter (ignore vanity)
- 7-day retention of new members (goal ≥ 35%).
- Active posters per day (not total members).
- Join → first LFG post conversion.
- Reports resolved within 24 h.
Growth without spam
- Create a simple how to join page on your site; link in social bios.
- Invite via events and guides, not mass DMs. Quality beats blast.
- Cross-post screenshots and build sheets; keep replies in server.
Pocket checklist
[ ] Stage-1 channels created (≤ 12) [ ] Roles: Member/Trusted/Mod/Admin (2FA on admin) [ ] Onboarding buttons + LFG form [ ] Auto-mod: filters, slowmode, media scan [ ] #mod-log + incident flow pinned [ ] Weekly events scheduled 30 days out [ ] Metrics dashboard: retention, LFG conversion [ ] Appeal path exists and is staffed