JoinGG

A player banned somewhere else: three workable positions

You do not know what happened and cannot find out. Decide the policy before it arrives, because improvising is what communities argue about.

SweetMask · 5 min read

Sooner or later somebody tells you that a player on your server was banned from another one. What you do next is a policy question, and improvising it produces exactly the inconsistency communities argue about for months.

Why this is harder than it looks

The instinct splits two ways and both are defensible.

Ban them. Somebody with a history of griefing is a risk you can avoid for free, and the other server's admins presumably had a reason.

Ignore it. They have done nothing on your server. You have no evidence, no context, and no way to know whether the other ban was fair.

Neither is obviously right, which is why this needs a decided position rather than a case-by-case judgement made under pressure.

What you do not know

The report you receive is missing most of what would let you decide well:

  • Why they were banned. "Griefing" covers stealing a diamond and burning down a town.
  • Whether it was fair. Some servers ban for disagreeing with an admin.
  • When. Two years ago and last week are different facts.
  • Whether they are the same person. Names are reused, accounts are sold, and alt accounts exist.
  • Who is telling you. A grudge from another community is a common reason for this message to arrive.

That last one is worth taking seriously. A meaningful share of cross-server ban reports come from somebody pursuing an argument rather than protecting anyone.

The three workable positions

PositionWhat it meansSuits
Clean slateOnly your rules, only your serverMost public servers
Case by caseLook at it, decide, record whyWhitelisted communities
Shared bansFormal agreement with named serversNetworks and alliances

Clean slate is the right default for a public server. It is defensible in every argument, it does not require you to adjudicate somebody else's incident, and it means every player knows the rules are the ones written down.

Case by case is honest for a whitelist server, because you are already selecting who gets in and a history is legitimately part of that.

Shared bans only work between servers that actually trust each other, with an explicit agreement about what is shareable. Informal versions — "we ban whoever the big server bans" — end badly, because you have outsourced your moderation to people who owe you nothing.

If you do look into it

Some things make the report much stronger:

Evidence rather than assertion. A screenshot of the ban with a reason, or a log entry. Not "everyone knows".

A reason that would break your rules too. Somebody banned for cheating is relevant to you. Somebody banned for arguing with a moderator may not be.

Recency. A ban from three years ago about somebody who has played elsewhere without incident since is weak evidence about today.

Multiple independent sources. One person is a report; three unconnected servers is a pattern.

And one thing that makes it much weaker: the reporter has a personal stake. Not disqualifying, but it changes how much corroboration you want.

Tell the player

If you act on a cross-server report, the person deserves to know that is what happened. A ban with no explanation, for something they did somewhere else, is the single most alienating moderation action available — and it will be discussed publicly by somebody, without your side of it.

"We were told about X on another server and we have decided not to take the risk" is a complete explanation. It is also honest about the fact that you are managing risk rather than punishing an offence.

Whether you offer an appeal is up to you, but a decision made on second-hand information is exactly the kind that benefits from one. An appeals process that works costs little and catches the cases where you were wrong.

Whatever you decide, put it in writing where players can read it. A policy announced in advance is defensible; one produced during an argument is not, and a changelog entry is the cheapest place to put it.

The reverse situation

You will also be on the other end: somebody asking whether a player was banned from your server, and why.

Decide in advance what you share. A reasonable position is to confirm a ban exists and give a category — cheating, griefing, harassment — without the detail. That is useful to the asker and does not publish somebody's incident to whoever asks.

Sharing full logs and chat history with anyone who requests it is a privacy decision you probably have not thought through, and it will eventually be requested by somebody with bad intent.

Where records help

All of this is easier if your own reports and bans are written down with reasons. When somebody asks about a player from two years ago, a record answers in seconds and memory does not answer at all.

It also protects you. A ban you can explain, with a date and a reason, survives being questioned publicly. One you cannot explain does not, regardless of whether it was correct.

The short version

Clean slate is the right default for a public server: your rules, your server, no adjudicating somebody else's incident on second-hand information. Case by case fits a whitelist. Formal shared bans work only between servers that genuinely trust each other.

If you do act on an outside report, want evidence, recency and independent sources — and tell the player it is what happened. And decide now what you will disclose when somebody asks you the same question, because you will be asked.

Tags
moderationcommunity serversserver admin
Share

SweetMask

Published · 5 min read

All articles

Keep reading

Guides

Whitelisting, and who it keeps out

The most effective moderation tool and the most expensive one. The cost is your growth rate, and nobody evaluates that part.

· 3 min read
Guides

Running several game servers on one box

They cannot see each other and they are competing. CPU contention, the memory arithmetic, and the port map nobody writes down.

· 4 min read
Guides

Reading server logs without drowning

Four categories, two that need you. Start at the top rather than the bottom, and learn what a quiet log looks like.

· 4 min read