Mojang, Beta, and the Release Version

This chapter's thesis: the release version of November 18, 2011 did not end Minecraft's design — it ended design by one person's say-so. The real turning point was not the game becoming complete; it was design authority shifting from one man's intuition into an organization's hands.

1The problem

November 18, 2011, Las Vegas, the Mandalay Bay hotel. Several thousand players fill the hall to watch Notch pull a lever on stage — the same kind of lever that flips a redstone circuit in game — and declare Minecraft 1.0 released.¹² You could not ask for a better prop to declare this game "done" than its most classic switch.

The event had one strange feature: almost everyone in the audience had owned the game for a year or two already. They were not waiting for a product to buy; they were attending the dedication ceremony of a world they had long since moved into. And after that day, the game in their hands barely changed — it updated the very next morning as usual, with changes neither bigger nor smaller than before.

So what exactly did "release" make official? Answering that means looking back two years: when one person's project became a studio, what happened to design authority — who decides where the game goes, and how was that power unbundled and handed around?

One piece of version background: in this chapter's era (2010–2011) Minecraft existed only as the Java Edition; the later Java/Bedrock fork had not happened yet. Everything in this chapter concerns a single game file.

2Did the game actually finish on release day?

The facts first. From May 13, 2009 — "a technical test where you can dig blocks" — to November 18, 2011 is 919 days.¹ Through all 919 of them the game never stopped selling: players bought a half-finished thing, played a half-finished thing, and watched it change under their feet. Nearly every other game of the time shipped only once finished; Minecraft reversed the order — sell first, finish in front of millions of eyes.

What technical transformation happened on the day of "completion"? Almost none. The team could not make the game flip itself into the release version at a precise moment, so the actual release act was performed manually backstage by a few developers; the lever Notch pulled on stage was ceremony. And the "release version" handed out there differed from the pre-release demo build, playable hours earlier, by a single line of code — a fix to login authentication.¹ This version was originally numbered Beta 1.9 and ended up shipping as 1.0.0. Renaming "the ninth beta iteration" to "1.0" was a change of name about promise, not a leap of content.

In other words: no technical moment of completion ever existed. "Complete" is a declared state — and what it declared was less "the game is finished" than "the way of making the game has changed." Changed into what? That starts with a small Swedish studio.

3Becoming a studio: roles, promises, MineCon

In June 2009, Notch registered the trade name "Mojang Specifications" as a personal business — a name picked back up from Wurm Online, the online game he had worked on earlier; mojäng is Swedish for "gadget." The real company, Mojang AB, was founded on September 17, 2010, with Jakob Porsér as co-founder and Carl Manneh as CEO.³ From that day on, Minecraft's development was no longer one person's affair — legally or organizationally.

The change landed in three places.

First, division of labor. Notch was no longer the only one writing code; Jens Bergensten and others joined the team. When a single person decides whether a mechanic changes, the decision depends on "do I feel like it today"; with a second and a third person it becomes a process of discussing, aligning, persuading. Every hire is one more dilution of "what this game is." The personal project's great advantage — zero-latency decisions — began depreciating the day the company was founded, traded for output that could be sustained.

Second, promises had to be put in writing. In June 2011 the studio publicly announced the Adventure Update, originally planned for Beta 1.7 and slipped to 1.8 because there was too much content.⁴ For a personal project, a slip costs nothing — nobody signed a schedule with you. For a studio, a slip is a public breach. The roadmap is itself a constraint on design authority: promise strongholds and villages in public, and you have to build them. From then on, Notch's intuition had to be translated into a roadmap before players took it seriously.

Third, ceremony. In August 2010, Notch shouted an invitation on his blog: players who wanted to meet him could come to Bellevue, Washington — his family hosted that gathering.² One year later, the same kind of gathering had a commercial name: MineCon 2011, Mandalay Bay, four to five thousand attendees, each going home with an in-game reward — a cape with a creeper pattern.² From living room to Las Vegas took twelve months. Earlier in 2010, players had also organized an online get-together by themselves through the forums, all crowding onto one server; that event had nothing to do with the company. MineCon's work, then, was not creating a public but plugging an existing one into a stage. A studio needs ceremony because ceremony turns players scattered across thousands of servers into a visible "public" — and the public is the foundation a brand stands on. That the public's coronation was scheduled at the 1.0 launch is no accident: for a studio, ceremony and "completion" are two faces of the same thing.

Looking back, nobody was dragged into this expansion. A game selling thousands of copies a day brings support mail, payment disputes, piracy, partnership talks — any one of them could drown the creator personally. People were hired first so that the designer could keep designing, not to make bigger designs. But the cost was just as real: from the moment one person becomes a company, "where should the game go" can no longer be answered with "because I feel like it." One seed of later history was planted here too: once work is divided, the person leading design has, for the first time, the option of handing a whole gameplay system away — an option that did not exist when one person carried everything.

4Beta 1.8: hunger, the Adventure Update, a split player base

If you may pick a single version to watch a studio exercise design authority, it is Beta 1.8.

Released on September 14, 2011, this version's official name was the first half of the "Adventure Update."⁴ What it added reads like common sense today: hunger, experience orbs, Creative mode, endermen, villages, strongholds, abandoned mineshafts, sprinting, charged bows. But every one of those items was editing the same thing — the behavioral logic of Survival mode.

Hunger first. Before it, food played the role of "portable first aid": take a hit, eat a porkchop, health returns on the spot. As long as your farm kept you in porkchops, Survival had no real pressure of death. Hunger inverted that logic: food stopped healing directly and started filling a hunger meter; health crept back only while you were well fed, and sprinting drained the meter too. Food went from first-aid kit to logistics — you had to keep a supply chain of food running, not carry a pickled medpack.

Why hunger, rather than some other difficulty lever? Make equipment wear out and players grieve for their property; spawn stronger monsters and players just stack better gear — both punish the player for getting stronger. Hunger is different: it confiscates a default state, "hoard enough food and you cannot die," and turns "staying alive" from a one-time achievement into a daily practice that needs continuous investment. The change later became a foundation of Survival mode — but the foundation was poured underneath a house other people had already built. That is exactly Beta 1.8's dilemma.

Then the other half of the Adventure Update's intent. It buried strongholds in the world — stone fortresses hidden deep underground, leading to The End that only opened in 1.0. It added endermen — the tall black figures that grow angry when you look at them, teleport, and can pick up blocks. It added villages and mineshafts — "human traces" on the surface and below it. Killing mobs began to drop experience orbs, even though experience had no use yet; that waited for the enchanting table in the release version. All of it pointed the same direction: give a sandbox that had been famous for over two years for "having no goals" its first goals designed by an organization.

One easily missed change in the same version: Creative mode became a formal option when creating a new world — infinite blocks, free flight, no health bar. That was the official acknowledgment that "building things" and "staying alive" are two parallel ways to play, not an accessory bolted onto Survival. Convergence and loosening happened in the same release: the mainline tightened, and the exit got wider too.

This was the game's first "convergence toward a game": the divergent sandbox began closing in around a designed mainline. You could still play purely to build houses — but the world now shipped with a schedule attached.

The players split. Both sides had defensible ground.

The question worth asking: why did the split erupt at 1.8 and not earlier? Every update before had been almost purely additive — new blocks, new mobs, the old stuff untouched. 1.8 was the first to do three sensitive things at once: change rules (hunger), delete content (old biomes, the Far Lands), and declare a direction (the adventure mainline). Addition never touches a world anyone has settled into. All three of these did.

The opponents said: I bought a sandbox where I set my own goals, and now it ships with a plot line; hunger changed "what do I want to do today" into "what do I owe the meter first"; a batch of old biomes got deleted, so the seed I knew never generates the same world again; even the Far Lands — the shattered terrain generated far out at the world's edge by floating-point error, holy ground to countless explorers — vanished in this version's terrain rewrite.⁴ Their one-line version: my house was renovated without my consent.

The supporters said: porkchops that heal instantly made death a formality, danger was no threat, Survival did not live up to its own name; endermen made the world "look back at you" for the first time — eyes on you wherever you walk; villages and strongholds finally gave you a reason to set out. Their one-line version: the game finally has weight.

Both sides were right, because they were not arguing about the same question. The opponents were defending "what did I buy"; the supporters were debating "what should the game become." The two collided head-on in 2011 for a reason buried in the business model: buying once meant every later update was free — but nothing in that contract said the updates had to listen to you.

For the studio, the substance of the uproar was this: players had discovered for the first time that the game's direction was no longer decided by "Notch's mood today," but by an institution with a roadmap and a division of labor. The anger on the forums was, at bottom, an open negotiation over design authority. The negotiation produced no winner, but it set a precedent — the studio may change anything, the players may complain forever, and both are legal.

5The ethics of the price tag: buy once

Half of the transfer of design authority is written on the price tag.

The price ladder was public: 9.95 euros during Alpha; on December 11, 2010, Notch announced the game would enter Beta on December 20 and the price would rise to 14.95 euros; the published plan was that the price would keep rising toward release, landing around 20 euros at 1.0.⁵ And the ladder's core clause was one sentence: everyone who had already bought once receives all future updates free.

One detail is often missed: the rise was announced in advance. Notch published the date and the new price nine days ahead of time; buying early or buying late was the player's own choice. The same price increase reads as "thank you for coming early" when it is announced beforehand, and as a backstab when it is slipped in afterward. Also worth noting: Minecraft in this era had no persistent online verification — buy it, download it, and it runs with the cable pulled. Players bought more than a version; they bought an offline game that belonged entirely to them.

Why a buyout, rather than the subscription model or "free to play, pay to win" then on the rise? At least three reasons, each layer deeper than the last.

The shallowest is cash flow. Alpha's word-of-mouth sales already fed the team — Notch quit his day job during Alpha (how that way of selling got started is the previous chapter's story) — so no subscription was needed to secure revenue.

The middle layer is the structure of trust. Buy-once turned "buying early" into a wager: you bet that a half-finished thing would become a good game, and the price ladder gave that bet a discount. In exchange, players held a promise about the future — the game will be finished, and the updates after that carry your name on them too. The promise was later kept to a startling degree: the bone-deep overhauls after the release version (hunger was only the first of them) never charged old players a single cent.

The deepest layer is that the buyout constrained design authority itself. Under subscription or microtransactions, different player groups contribute different revenue, and "design for whoever pays the most" acquires a financial rationale. Under a buyout, each player's contribution settles once and forever; Mojang faced no pressure to optimize for any segment, and design debates could stay on the ground of "what is good for the game." This is the ground note of every revenue-model conflict since: when Bedrock's official store (the Marketplace) began selling paid content, the veterans' instinctive rebuttal was one line — "I already bought this game." The conflict was not born back then; the contract was signed in 2010, just not yet in force (that thread continues in "Revenue Structures").

Buy once

groundworkbuy once includes lifetime updates → every existing owner is a creditor of future updates → any new charge must first cross this default contract

6Ceremony, not system: 1.0 did not end design

Now the opening question can be answered.

1.0 closed a narrative, not a system. The line the Adventure Update drew — strongholds, endermen, The End — got its endpoint in 1.0: the Ender Dragon. Defeat it, and the game rolls a credits screen. This was Minecraft's first "completion," and its appearance inside the release version is no coincidence: an organization that needs a "release version" needs a mainline that can be walked to the end, to prove that "release" means something. But for most of the people living in that world, you beat the dragon and go home to mine — from then on, "beating the game" was merely an optional item in Minecraft (that thread continues in "Survival as a Meaning Machine").

One more detail shows how diluted "release" already was: before MineCon, Mojang had publicly shipped several 1.0 pre-releases that any player could play early. By November 18, the release version held almost no surprise for anyone; on launch night, the hottest topic in the community was already "what will 1.1 bring." For players, "completion" was never an engineering event — it was a psychological event, and psychological events need a ceremony.

What 1.0 actually completed that day, then, were three things with nothing technical among them. A renaming: Beta 1.9 became 1.0.0, a number used as rhetoric, declaring "safe to entrust yourself to."¹ A ceremony: released by hand backstage, crowned by a lever on stage¹ — a ritual marking a moment that never existed at the technical layer. And a fulfillment: Alpha buyers went on receiving every later update free; the promise at the top of the ladder was not taken back.

Whether this chapter's thesis holds can be judged by one checkable standard: if 1.0 had closed the system, design afterward should have converged, settled, stopped. The opposite happened. Less than a month after release, on December 2, 2011, Notch handed lead design of Minecraft to Jens Bergensten and moved on to a new project.⁶ Version numbers kept climbing, and the changes kept getting bigger. Nor was the handover a retirement: Notch's name faded from the changelogs, while several of the game's largest expansions happened precisely after he stepped back. After the "release version," Minecraft's design history was barely half written.

So the thesis, stated so that it can be tested: what was sent into history on November 18, 2011 was not this game's design, but the rule that "design is decided by one person's intuition." Every major change after that had to be argued in the studio's name; it could no longer be announced in a genius's name. If Minecraft's design after 2011 were still Notch's alone, or if the game had set into its final form that winter and stopped evolving, this thesis would be wrong. Neither happened.

A system you can live in requires its designers to give up "finishing" it. 1.0's real legacy was writing "unfinished" into the product's identity: from that day on, "done" in Minecraft is not a state but a milestone — and after a milestone, the roads still get repaired and the houses still get built.

7What this chapter leaves behind

• For players: the "one-person Minecraft" you miss did not die on release day — it died at Beta 1.8, and the player split was the sound of it being taken over by an organization.
• For developers: what you can copy is the trio — buy-once pricing with lifetime updates, a public roadmap used as a commitment that binds your own design authority, and ritual in place of "done" for managing expectations. What you cannot copy is the first users and the cash flow that Alpha's word of mouth piled up — that capital is what every kept promise is paid out of.

注释

1. Minecraft Wiki, "Java Edition 1.0," minecraft.wiki, retrieved 2026-09-17; see https://minecraft.wiki/w/Java_Edition_1.0 ↩ ↩² ↩³ ↩⁴ ↩⁵

2. Minecraft Wiki, "MineCon," minecraft.wiki, retrieved 2026-09-17; see https://minecraft.wiki/w/MineCon ↩ ↩² ↩³

3. Wikipedia editors, "Mojang Studios," Wikipedia, retrieved 2026-09-17; see https://en.wikipedia.org/wiki/Mojang_Studios ↩

4. Minecraft Wiki, "Java Edition Beta 1.8," minecraft.wiki, retrieved 2026-09-17; see https://minecraft.wiki/w/Java_Edition_Beta_1.8 ↩ ↩² ↩³

5. Minecraft Wiki, "Java Edition Alpha," minecraft.wiki, retrieved 2026-09-17; see https://minecraft.wiki/w/Java_Edition_Alpha ↩

6. Minecraft Wiki, "Markus Persson," minecraft.wiki, retrieved 2026-09-17; see https://minecraft.wiki/w/Markus_Persson ↩