A player report process that still works at 3am

Every server eventually needs a way for players to say "this person is ruining it". Most servers handle this by having somebody message an admin, which works until the day it does not, and the day it does not is usually the day it mattered.

Why an informal process fails

It works when the community is small and the admin is always on. It fails in three predictable ways:

Nothing is recorded. A player reported three times by three different people over two months looks like three isolated incidents, because nobody joined them up.

It depends on one person. Reports go to whoever is visible, which means the same admin handles everything and burns out, and nothing happens when they are away.

Reporters get no feedback. Somebody takes the trouble to report and hears nothing. They conclude reporting does not work, and they stop — which means the next problem reaches you later, or not at all.

That third one is the expensive one, because it is invisible. A server where nobody reports anything is not necessarily a server with no problems.

The minimum that works

You do not need a ticket system. You need four things:

One place to report. A channel, a form, a command — one, and everybody knows which. Two places means half the reports go somewhere nobody is watching.

A record. Whatever was reported, about whom, by whom, when, and what happened. A spreadsheet is fine. The point is that the fourth report about somebody is visibly the fourth.

More than one person who can act. Not necessarily equal authority — but somebody who can respond when the owner is asleep.

A reply to the reporter. Even "we looked at this and decided not to act" is a reply. It is the thing that keeps reports coming.

What to ask for

Reports arrive as "X is being annoying", which is not actionable. What you need:

Asking for those four in the report channel's topic gets you them most of the time. Asking after the fact means going back to a player who has already lost interest.

Evidence is not required. A rule that says "no evidence, no action" sounds fair and quietly disables reporting for everything that happens too fast to capture — which is most of it. Evidence raises confidence; its absence does not close the case.

Handling the report itself

Do not act in the moment on one account. The exception is anything actively destructive, where stopping it comes first and investigating comes second.

Check the logs before the story. Server logs are the closest thing to a neutral witness you have, and reading them before hearing the explanation stops you being talked out of a fact. Which logs to keep, and for how long, is worth deciding before the incident rather than during it.

Talk to the accused. Not always, and not for obvious cases. But a surprising proportion of reports are misunderstandings between two people, and the version where you ban somebody without asking is the version you regret.

Decide, and write down why. The reason matters more than the decision, because in four months you will not remember either and somebody will be arguing about it — the same reason a written record beats memory everywhere else.

Feedback to the reporter, without the details

Tell them something happened. Do not tell them what.

"Thanks, we have dealt with it" is the right amount. Publishing punishments turns moderation into a spectacle and creates an incentive for people to report in order to see something happen. It also invites arguments about proportionality from people who do not have the full picture.

The exception is a public rule change caused by an incident, which is worth announcing without naming anybody.

The pattern nobody sees without records

The single strongest argument for writing reports down is that individual incidents are ambiguous and patterns are not.

One report about somebody being rude is a bad evening. Five reports over three months, from five different people, none of them severe, is a person who makes your server slightly worse for everyone and never quite crosses a line. That pattern is invisible without a record and obvious with one.

The same works in reverse: three reports from the same person about three different people is its own signal.

It is also worth deciding what the process is for reports about staff, because that is the case an informal system handles worst and the one where getting it wrong is most expensive. The same applies to reports that arrive after somebody has already left the server — a pattern that only becomes visible once the community spans several timezones and nobody sees the whole day.

Scaling it

Below about thirty regulars, a channel and a spreadsheet is genuinely enough. Above that, the pressure is toward tooling — a bot, a ticket system, a web form.

Be careful what you buy. Moderation tooling has a cost beyond the licence: another system to maintain, another thing that breaks on update day, and a process that is harder to change once it is encoded. The tool should follow the process, not create it.

Reports about behaviour elsewhere

Somebody will report a player for something they did on another server, or in a Discord, or years ago. This needs a decided position rather than an improvised one, because improvising produces inconsistency and inconsistency is what communities argue about. What to do with a player banned somewhere else is its own question and worth settling before it arrives — the short answer for a public server is that your rules are the ones that apply.

One thing not to rank or publish: report counts, staff activity leaderboards, anything that turns moderation into a scoreboard. Whatever you rank gets farmed, and that is the last place you want it.

For players making a report

Name, behaviour, roughly when, and evidence if you have it. Skip the interpretation — "he was being toxic" is less useful than what he actually said.

And report once. Reporting the same thing in three channels does not make it more urgent; it makes it three records of one incident and makes the pattern harder to read.

The short version

One place to report, a record so patterns are visible, more than one person who can act, and a reply to whoever bothered to tell you. Ask for who, what, when and evidence — but do not require evidence, because requiring it silently switches reporting off.

Check the logs before the story, write down the reason rather than the verdict, and tell the reporter something happened without telling them what.