Who Makes the Rules

This chapter's thesis: Minecraft's power to design is split across three layers — engine legislation (the officials, written in code), server legislation (operators, written in plugins), and an unwritten constitution (the community, written in convention). All three can genuinely change "what this game is," and when any one layer goes missing, the other two fill in on their own. If repealing the entire output of any one layer left the "game" as players recognize it completely unchanged, this thesis would be wrong.

1The problem

"Is this official design?" — in most games that is a checkable question of fact. In Minecraft, it is often unanswerable. The rules you play under tonight may have been written into the code by Mojang (the creeper's explosion), paid for and installed on a server by an operator (this patch of ground will not break), or laid down in a forum post a decade ago and never enforced by any program (what you take off the ground gets returned).

Three layers of rules stack on top of you looking almost identical: all of them say "how things are done in this world." Players never need to tell them apart — until someone asks "who designed this?" and the answer turns out to be plural. This chapter takes the three legislations apart layer by layer and draws up a comparison table, then borrows the anarchy server for a closing thought experiment: take the first two layers away entirely, and see whether the third grows back on its own.

2Turn off mob drops — is it still the same game?

Warm up with the lightest layer. Open the settings of a singleplayer world and, without installing anything third-party, you can make these changes: twist difficulty down to Peaceful (the Peaceful player from chapter 3, Survival as a Meaning Machine); switch off death drops (what you carry no longer scatters); switch off fire spread (your wooden house is fireproof from here on); switch off the daylight cycle (permanent noon).

Every one of these is an official switch, and every one genuinely changes "what this game is." Turn off drops, and survival's death penalty changes character (chapter 3's restraint of "it drops, but does not destroy," manually repealed); turn off the cycle, and the meaning machine of chapter 3 loses a wheel; turn off mob griefing (mobGriefing), and the creeper is demoted from "the invisible legislator of building codes" (chapter 9, Mobs, Combat, and Threats) to an ordinary bomb. Behind none of these switches is there a "correct setting" — the officials provide; they do not adjudicate. So is what you play after flipping them still Minecraft? The players' daily practice answered long ago: yes — and no. It is a new game running on the same engine, and that one sentence is the starting point of this chapter's entire discussion: the engine lets players legislate on top of the official rules, and the result of that legislation is still called Minecraft.

Put the three legislations in one table, then take them layer by layer:

3Engine legislation: switches for sale, no verdicts

The first layer's lawmaker is Mojang, and its tool is a whole row of official switches¹. Chapter 8, Commands, Datapacks, and Maps, covered this layer's extension end (datapacks, experimental gameplay), and chapter 4, Creative Mode Is Not a Level Editor, its mode and difficulty axes; what concerns us here is the layer's legislative style: what the officials provide has never been rules — it is interfaces to rules.

Set it against the alternative and the style shows. Most games weld their rules into the code: difficulty is a set of presets, immovable; the rules of death are hardcoded, immovable; the developer's word is final. Minecraft took a batch of things "the designer could have decided" and shipped them as switches — whether death drops, whether mobs alter terrain, whether day follows night — clauses that in any traditional studio rank as "core experience, not negotiable." The restraint of official legislation lies here: it legislates parameters, not gameplay — how the gameplay grows is left to the two layers above.

The style has a consistent design history: from the Alpha era on, the officials kept converting arbitration into interface (Volume I chapter 9, Version Evolution and Update Strategy, covered co-creation institutions like snapshots and the mob vote). To interface-ize is to admit: a world with hundreds of millions of residents cannot have its rules pre-written in full by one company — better to sell the legislative power in layers, and let the officials monopolize only the bottom layer, physics.

Interface-ization also turned the officials' defaults into public issues. The "can mobs change the terrain" switch (mobGriefing) is a standing controversy: on, and creepers and endermen keep their full destructive power, so defense becomes a discipline; off, and the world turns much gentler, but the "threat-driven building" machinery of chapter 9 loosens with it. On or off, the officials never rule, and the community has argued for a decade without reaching consensus — which is exactly the proof that the legislation was genuinely handed over: even "what the default should be" has become each world's domestic affair.

4Server legislation: local government and case law

The second layer's lawmaker is the operator, and its tool is the plugin. Volume I chapter 5, The Server Is the New Game, called this layer "local government" and settled its accounts in fiscal terms; this chapter switches to a legislator's eye and watches how it legislates.

Plugin legislation covers every legal department you can name: land-claim plugins are property law (drawing boundaries that may not be violated), economy plugins are currency law (defining what counts as money and how prices form), minigame plugins are gameplay constitutions (dictating outright "what the game is here"), bans and mutes are criminal law, and the admin is the judge. But what really makes this layer resemble "legislation" is three traits of how it runs. One, limited jurisdiction: its laws take effect within a single server, and past the gate lies another jurisdiction — players therefore trained the political instinct of "when in Rome" inside one and the same game. Two, amendment at any hour: rules change tonight and take effect tomorrow morning, with no version number and no referendum — legislative efficiency thousands of times the officials', at the price of stability resting entirely on the operator's self-discipline. Three, case law: most servers have no written code; precedent accumulates from the admin's ruling, case by case — "he did that last time and got banned, so it doesn't fly this time either." Put the three together and every server is a small common-law jurisdiction: the same engine, thousands of judicial practices.

This layer bears most directly on this book's overall thesis: "what the game is" gets rewritten deepest here. A survival server running economy and land-claim plugins and an anarchy server are two social experiments — on the same official code. Where "the server is replaceable" was first argued, the architectural reasons were given (Servers and Scale); this chapter adds the political consequence: a replaceable server means replaceable law.

5The unwritten constitution: rules with no code

The third layer is the strangest: the lawmaker is the entire community, the tool is convention, enforcement runs on reputation, and violation carries no penalty — yet it governs millions.

Its clauses were never written down, yet everyone can recite them: don't demolish what others built (even on a server with no land protection whatsoever, even when nothing technically stops you); don't cheat (no x-ray, no grabbing items through Creative — and even in your own singleplayer world the community will look at you sideways; the "vanilla purity" covered in Version Evolution and Update Strategy is this constitution's attempt to write itself down); return what you borrow (the trust networks for borrowed gear on servers — chapter 11, Multiplayer Is the Default); and a whole set of aesthetic consensuses (what counts as a "good-looking" build and what counts as "crude" — nobody holds enforcement power, but your work is being silently judged).

The constitution's enforcement mechanism also appeared in chapter 11: settlement by reputation. A violator is not banned; the violator is remembered by name — and in a world where anyone can spin up an alt account, that looks soft and is in fact precise: what this constitution governs was never accounts; it is identity. Why is it obeyed? Because it maintains public goods: not demolishing others' things buys the expectation that your own things will not be demolished; not cheating buys "my results are valid for everyone" (Volume I likewise covered vanilla as the community's shared common language). Every clause of the constitution is a self-investment in a public good — rational enough to need no penalty clause at all.

Now and then it does get codified: servers post "rules" threads, community wikis record the conventions, veterans write "read this first" guides for newcomers. But the written text always trails the convention by half a step — what gets written down is the clauses that have already stabilized, while the constitution's growth happens where the text cannot reach: every argument and arbitration over "how does this one count." The written constitution is this body of law's commemorative photograph, not its life.

Put the three layers side by side and the division of labor, and the dependence, come into view: engine legislation supplies the possible boundary of physics; server legislation slices that boundary into jurisdictions; the unwritten constitution lays a layer of shared expectation across all the jurisdictions. The engine legislates physics, servers legislate gameplay law, the community writes the constitution. An upper layer can override a lower one (the anarchy server abolishes the second layer), but it can never abolish the third — which leads into this chapter's final experiment.

62b2t: take two layers away and see whether the third grows

The anarchy server makes "no rules" its founding identity: no admins, no plugin legislation, no whitelist — everything the officials permit is legal. Earlier chapters have already used it from two angles (the limit sample in The Server Is the New Game, the state of nature in Multiplayer Is the Default); this chapter uses it for one last thought experiment: strip away both legislations beyond the engine — does the third layer vanish?

The observation came out exactly backwards: the anarchy server is where the unwritten constitution is most developed. It has its own creation myths and historical narrative (which team built what, and when, and in which battle it fell), its own taboos (settling down uninvited near someone's base is read as a declaration of war), its own ethical controversies (does cheating count as "unconstitutional" — in a world where even cheating is not a crime, the community managed to argue for a decade over the "respectable use" of cheats), even its own historiographical tradition (dedicated chroniclers keep the annals, and events are divided into "before the era of so-and-so"). A world that refuses all legislation grew the thickest layer of convention.

The experiment's conclusion is this chapter's thesis in its hardest form: legislation is an emergent property of the system, not any designer's achievement. Mojang legislated the physics; operators legislated their communities' modern law; and given no more than two players and a little time, the third layer starts writing itself. The anarchy server is not the proof of "a world without rules" — it is the proof that "rules cannot be eliminated." Volume I called it the limit sample; this chapter completes its identity: it is the microscope that made the third layer visible, the layer that stays transparent everywhere else.

Return to the opening question: who is the real designer? The answer no longer needs to hesitate: Mojang designed the legislative system; the operators legislate within it; the community writes the constitution — the designer is plural, and three generations of lawmakers live under one roof. Chapter 13, Mods as Design Method, discusses what the officials ought to absorb; this chapter supplies its premise: "absorbing things from the community" is, at bottom, moving clauses between the three legislations — what to move, and how, depends on the officials' judgment of which layer legislates best at which kind of law.

7What this chapter leaves behind

• For players: the rules you keep on a server that nobody enforces are as much this game's real law as Mojang's code — you have been a lawmaker all along; the position simply never paid a salary.
• For developers: what you can take away is the layering of legislation — the officials monopolize the physics layer alone, leave the gameplay layer to operators and the convention layer to the community, and accept that "your code is only the thinnest of the three layers." What you cannot take away is the third layer's generation time: a constitution sediments on a scale of decades, and what it trusts is not your design documents but your irreversibility.

注释

1. Minecraft Wiki, "Game rule" (the official world-level rule switches: keepInventory, mobGriefing, doDaylightCycle, and others), minecraft.wiki, retrieved 2026-09-18: see https://minecraft.wiki/w/Game_rule . ↩