The unwritten contract between a server and its regulars

Every server has a rules page and every server has a second set of rules that is not written anywhere. The second set is the one people leave over.

It is not hidden. It is simply never stated, because it consists of expectations that formed by precedent and that nobody thought to articulate: until the day one of them is broken and a third of the regulars are furious about something the rules page explicitly permits.

What the unwritten contract contains

Four things, on almost every server:

Continuity. Whatever players built is assumed to persist. Nothing in the rules promises this. Everyone believes it anyway, which is why a wipe announced as routine reads as a betrayal to people who were not expecting one.

Consistency of enforcement. Not fairness in the abstract: consistency with what happened last time. A ban that would have been a warning six months ago produces an argument about the ban, and the argument is really about the change.

Access to the people who run it. On a small server the owner is reachable. That stops being true as it grows, and the moment it stops is felt as the server becoming corporate, even when nothing about the policies changed.

Standing. A regular expects their history to count for something. Not immunity, but the benefit of the doubt. Treating a two-year veteran exactly like a first-day arrival is defensible and it is also the thing that makes veterans stop feeling like veterans.

Why it never gets written down

Partly because it is invisible until violated. Mostly because writing it down means making commitments, and the owner correctly senses that a promise of continuity is one they may not be able to keep.

So the contract stays implicit, which has the effect of making every promise unlimited. An unstated expectation has no exceptions, no scope and no expiry, and it is negotiated only at the moment it fails.

The wipe is the clearest case

Games with scheduled resets: Rust most obviously — have solved this by making the reset explicit and rhythmic. Everyone knows a wipe is coming, so nothing is betrayed when it does.

Games without a built-in reset have the opposite problem. A Minecraft server that wipes has broken something, even when there was an excellent reason, because nothing ever said the world was temporary. The same action, in two contexts, and only one of them costs the server its regulars.

The lesson is not "never wipe". It is that the expectation has to be set long before the event, and that a server which cannot commit to permanence should say so early rather than discover the assumption at the worst moment.

The moderation version

The unwritten enforcement standard is the one that catches new admins.

A moderator who joins and starts enforcing the written rules strictly is doing exactly what they were asked, and they will immediately generate complaints, because they are enforcing the stated rules rather than the actual ones. The actual rules are the stated ones plus every precedent set since launch, and those precedents live in the heads of people who have been there long enough to remember them.

The fix is to write the precedents down when you notice them, which means treating the rules page as a record of decisions rather than as a document authored once. Most servers never do this, which is why rules that people actually read are short, and why short rules require a moderation team that talks to each other.

The clause about the owner

There is one term in the contract the owner never notices signing, which is that they will keep being the person the regulars met.

Communities form around a particular way of running things, and the people who stayed are the ones that way suited. When the owner changes, whether through burnout, a new job, a shift in what they want from the server, the regulars experience it as the agreement being altered without discussion, and they are not entirely wrong.

This is the mechanism behind a failure that looks mysterious from inside. Nothing broke, no policy changed, and the regulars drifted anyway. What changed was the owner's attention or temperament, which was never a stated term and was always the most load-bearing one.

The only useful response is to say it. A server whose owner explains that they have less time this year keeps people who would otherwise conclude the place has gone off, and the explanation costs nothing except admitting that the server depends on a person.

Renegotiating it deliberately

Say what you are not promising. That sentence is the whole intervention.

"This world is permanent unless something forces our hand, and if that happens you will get a month's notice." "Staff decisions are final but you can appeal once." "I read everything but I cannot answer everything." Each one closes an assumption that would otherwise be unlimited.

None of it is exciting to write and all of it is cheaper than the conversation it prevents. A community that knows the boundaries of what it is owed can be disappointed by an event without feeling deceived by it, and the difference between those two reactions is the difference between a bad week and a server that quietly empties afterwards.