Anarchy servers always grow rules

Sooner or later every server that promises no rules bans the same short list: crashing the server, lagging it on purpose, exploits aimed at the machine rather than the players, illegal material, and publishing someone's real name or address. None of that breaks the promise. 'No rules' was always a statement about the game, and those things happen to the server and to people outside it.

The short list, and why each item is forced

Lag machines come first because they turn up first. A redstone clock left running, or a pile of entities packed into one chunk, hurts nobody in the way the game intends and makes the game worse for everyone connected. An anarchy server ticking at a fraction of its normal rate is still anarchy in principle, but nobody can fight in it, and the players who came for the freedom leave for a server that moves.

Crash exploits are the same argument taken further. A crash ends every session at once, which gives one player with an exploit the same reach as whoever owns the power switch. Owners patch where they can instead of punishing, but a player who crashes the server over and over is removing the game for everyone else, and eventually gets removed.

Cheats are where the line gets precise. Anarchy servers generally allow hacked clients, and flying or seeing through walls is part of the fight. What they cannot allow is a client that attacks the server itself, flooding it with packets or forcing it to load and generate far more of the world than the game ever would. The cheat is tolerated because it acts on other players. The load is not, because it acts on the machine they share.

Illegal material and doxxing are the last two and the least negotiable, because neither has anything to do with the game. A server that holds material that is illegal to possess puts its owner and its host in a position no server philosophy covers, and no reputable host keeps such a machine online once it knows. Publishing a player's real name or address moves the harm off the screen, where 'no rules' never had any authority. Owners who pride themselves on never intervening still remove both, and they rarely call it moderation.

Rules written as configuration

What an anarchy server has instead of a rules page is configuration. On Paper, which a great many Minecraft servers run, paper-global.yml includes a packet limiter, and by default a player who sends more than 500 packets in seven seconds is kicked. The same file puts a ceiling on the size of written books, under book-size. Its 'unsupported settings' keep several vanilla exploits switched off by default, including piston duplication of TNT, carpets and rails, and the tricks used to break blocks that are meant to be unbreakable. Even the vanilla server.properties has a rate-limit on packets, disabled unless an owner sets it.

None of these reads like a rule, and that is why players accept them. A limit in code applies to everyone at the same moment and needs no admin to decide anything. Turning Paper's exploit settings back on, or leaving them off, is a policy decision about what kind of anarchy the server offers. It is made once in a text file and announced, if at all, in a changelog. Items the game could never produce, such as weapons enchanted far past the game's limits, often get the same treatment: a plugin sweeps them away and the change goes out as an exploit fix.

Game rules and platform rules

The useful distinction is between two kinds of rule. Game rules govern what players do to each other inside the game: who may kill whom, whose base may be burned, what may be said in chat, which clients are allowed. Platform rules govern what anyone does to the server or to people outside the game. An ordinary survival server writes both kinds on one page, and the usual advice on writing rules people read applies to both.

An anarchy server deletes the first kind entirely and keeps the second, usually without calling it rules at all. The players who choose anarchy understand the distinction well, since it is most of what separates the mode from the other kinds of Minecraft server. Keeping the machine up is also where anarchy looks most like everywhere else: it is ordinary security work, done against a crowd that tests it harder than most.

When an exception looks like taking sides

The anarchy label survives its exceptions for as long as they look like maintenance. A patch that closes an exploit for every player, or a limit that applies to every client, keeps the server in existence without taking a side, and players accept that even while they complain about it. The label starts to fail when an exception looks like a favour: an exploit closed a week after the admins' friends finished using it, or a ban for 'lag' on someone who was mostly winning. That is an admin choosing winners, and it is the thing anarchy players came to get away from.

The servers that keep the name for years tend to keep their exceptions short, enforce them in configuration wherever they can, and use the changelog to say plainly what changed and why. When you browse the anarchy servers currently listed, the one whose announcements explain each limit is usually the one whose 'no rules' you can rely on.