The rule that was written for one person

Read any long-running server's rules carefully and you can date them. Somewhere in the list is a clause so specific that it can only have been written the morning after something happened, and the person it was written about left years ago.

Rules accumulate this way on every server, and the accumulation is not a drafting failure. It is what happens when policy is written by incident.

How the clause gets there

Something occurs that the existing rules do not cover. An admin makes a call, somebody argues that it was not against the rules, and the admin is technically wrong.

So the rule is added, worded narrowly around what actually happened, and the argument is closed. This is a sensible response to that afternoon and a bad way to build a document, because the next incident is also unlike anything covered and the list grows again.

Ten years of this produces rules that read as a history of grievances rather than a description of how to behave, which is precisely what makes a rules page nobody finishes reading.

Why nobody deletes anything

Removing a rule feels like permitting the thing. It is not (the behaviour would still be handled), but it reads that way to anybody watching, and the admin who deletes a clause is inviting somebody to test it.

There is also no moment when deletion is obviously due. A rule that has not been needed in four years is not visibly costing anything, and the cost it does impose is diffuse: a longer document, read by fewer people, understood by almost none.

So the list only grows, and every server converges on the same shape.

What the accumulation actually does

It teaches players to read legalistically. A long list of specific prohibitions invites the reading that anything unlisted is allowed, which is the opposite of the intended effect and produces the exact arguments the specificity was meant to prevent.

It makes admins inconsistent. Nobody has the whole list memorised. Enforcement drifts toward the six rules everybody remembers, and the rest become clauses that apply only when somebody looks them up to win an argument.

It hides the rules that matter. The three principles the community actually runs on are in there somewhere, between clause 14 about build height and clause 22 about a specific exploit in a version the server no longer runs.

The alternative that works

A short document of principles, plus a separate and openly editable list of specific rulings.

The principles do not change: do not ruin the game for other people, do not use bugs to win, do the thing you would be comfortable explaining. The rulings are examples (this is what we decided about that) and can be added to freely because nobody reads a precedent list as a contract.

That split matters because the two documents have different jobs. One is read once by every newcomer and should be short enough that they do. The other is consulted by admins and by anybody arguing a case, and its length is not a problem. Rules a player reads before joining are the first document; everything else is the second.

The annual deletion

The practice worth adopting is a scheduled read-through — once a year, the whole list, deleting anything written for a person who is gone or a mechanic that no longer exists.

It takes twenty minutes, it always finds something, and it is one of the few maintenance tasks on a server that nothing forces you to do. Which is why it does not happen, and why some servers are still prohibiting an exploit patched in 2019.

The rule that was never written down at all

The opposite failure is worth naming, because servers that keep their rules short frequently end up with the same problem from the other direction.

A short document plus years of precedent produces a server where the actual rules are known only to the people who were present when they were decided. Newcomers read three principles, break something that everybody else understood was forbidden, and are corrected for violating a rule that exists nowhere.

That is worse than a long list, because a long list is at least readable. An unwritten convention cannot be looked up, cannot be argued with, and cannot be complied with in advance, and enforcing one puts the newcomer in the position of having been wrong about something they had no way to know.

Which is why the rulings list matters as much as the principles. It is not a legal document. It is the record of what the community has already decided, and its job is to let somebody who arrived last week find out what everybody else already knows.

What the specific clause is really for

Worth naming, because it is not nothing: a rule written about one person is frequently an admin documenting that they were right.

The dispute was never really about whether the behaviour was acceptable. It was about whether the admin had the standing to act, and adding the clause settles that permanently. Understanding this makes the clauses easier to delete later — the authority they were establishing is long since established, and the standing an admin actually has does not come from the document anyway.