ITS SM-CDT study materials
ITS SM-CDT study resources

Moderation crisis in an 18,000-member server

ITS SM-CDT · Put your knowledge to work in context.

All case studies

Moderation crisis in an 18,000-member server

PixelForge is an 18,000-member Discord server for a game community, run by six volunteer moderators across three time zones. The server averages 120 reports a day, with a median first response of nine hours. Last night, moderator Kestrel banned a streamer with 400,000 followers for posting a screenshot of an unreleased game build. The streamer said the image was already public. Within six hours, 2,000 new accounts joined, several channels were flooded with harassment, and Kestrel’s real name and employer were posted. The mod team is split: three want to reverse the ban to calm the server, three want to hold it. A private moderator channel was screenshotted and shared. There is no written escalation policy, no raid mode, and no appeal form. The game studio has not commented. What should the server leadership do?

1. Outline the first 24 hours of response, in order, and justify each step.

Read the worked answer

The first priority is safety, not the ban debate. Remove or hide the doxxing content immediately, preserve screenshots and message IDs for evidence, and report the harassment to the platform. Contact Kestrel privately, advise them not to engage, and offer to rotate them off visible duties. A volunteer should not have to defend their employer and real name in public.

Second, contain the raid. Enable verification, slow mode, and invite restrictions; temporarily lock high-traffic channels; and require a verified role before posting. Do not announce a lockdown as a punishment. State that new-member verification is on to protect the community while reports are reviewed.

Third, stabilize moderation. Freeze non-urgent decisions, require two moderators for any high-profile ban or reversal, and assign one person to log actions and one to watch reports. The split vote should not be resolved by whoever is loudest; it should go to a documented review with the evidence.

Fourth, publish a short statement: what is known, what rules apply, how to appeal, and when the next update will come. Do not debate the streamer or release private moderation chat. Reversing the ban solely because of a raid would reward harassment and make every future moderation call contestable. The ban may still be reversed after review, but the decision must be evidence-led, not crowd-led.

2. Design a moderation policy and staffing model that prevents a repeat.

Read the worked answer

The policy should turn discretion into a repeatable process. Define infractions in tiers: minor disruption, harassment, doxxing, ban evasion, and leaks of unreleased material. For each tier, specify warning, timeout, temporary ban, or permanent ban, and require evidence such as message links, timestamps, and moderator notes. High-profile or ambiguous cases need two-moderator review; a single moderator should not handle a creator with 400,000 followers alone.

Set response targets that match capacity. With 120 reports a day and six moderators, a nine-hour median is predictable. Aim for a two-hour first response on harassment and doxxing, and a twelve-hour response on general reports, with an on-call rotation. Publish an appeal form and a service level for appeals, such as 72 hours.

Staffing changes:

  • Rotate a lead moderator per time zone.
  • Keep a private incident log with access controls; never paste sensitive screenshots into general mod chat.
  • Give moderators a break after a raid and a clear way to report burnout.
  • Run a quarterly review of bans and appeals, and publish aggregate numbers without personal data.

Add a raid playbook: verification, slow mode, locked channels, a single spokesperson, and a checklist for doxxing. The goal is not to eliminate judgement but to make it reviewable.

3. How should the team communicate the outcome without inflaming the streamer’s audience?

Read the worked answer

Communicate through one spokesperson and one written update, not through scattered replies in the server. Separate the policy question from the person: state which rule was applied, what evidence was reviewed, and what appeal path exists. Do not publish private moderator chat, Kestrel’s personal information, or a blow-by-blow of the raid. That feeds the audience looking for conflict.

The update should acknowledge harm without conceding facts that are still under review. For example: the server removed doxxing content, is reviewing the ban under its appeals process, and will not tolerate harassment of volunteers. Avoid language that treats the streamer’s followers as a monolith; many new accounts may be curious, not hostile. Moderate behaviour, not affiliation.

If the ban is upheld, explain the category of rule and the evidence standard, not the streamer’s character. If it is overturned, state what new evidence changed the decision and what policy will be clarified. Either way, do not reverse or uphold because of a raid. Consistency is the message that survives the news cycle. After 72 hours, publish a short follow-up with the appeal outcome and any policy change.