How to Read This Book
The reading contract and route table. The two audiences need not read the same line — players come for "so that's why," developers for principles with their non-transferable conditions. You may skip around, but not past Volume II's first four chapters.
This chapter's thesis: you may skip around this book, but you may not skip Volume II's first four chapters — voxel, verbs, survival, Creative mode are the frozen layer every later judgment stands on; skip them and what you read in Volumes III and IV is bare assertion.
1What this book is not
Not a walkthrough — no steps. Not a wiki — no completeness. Not a nostalgia album — the feelings of 2012 are research material here, not conclusions. Not an indictment — Microsoft and the Marketplace are treated as checkable business and governance questions.
It is a book of "why": why the block is one meter; why there is no skill tree; why one bug fix made server admins patch overnight; why "the next Minecraft" has not appeared.
2Two audiences, two routes
If you are a veteran player: read in volume order. Start each chapter from the "thesis" box and the "problem" section; sink into the sections that interest you. Developer-heavy chapters (most of Volume III; chapters 8, 15, 16 of Volume II) can be read at thesis-and-closing only. Your payoff is "so that's why" — swapping ten years of intuition for sayable reasons.
If you are a developer: suggested route is Prelude → all of Volume II → Volume I chapters 4–6 and 12 → close with Volume III chapters 17–18; dip into Volume III's details as needed. Your payoff is principles with non-transferable conditions — every transferable principle lists the premises under which it holds. Do not treat the premises as footnotes.
| Reader | Route | May skip |
|---|---|---|
| Veteran, front to back | volume order | dev-heavy chapters at thesis + closing |
| Gameplay designer | Prelude → all Vol. II → Vol. I 4–6, 12 → Vol. III 17–18 | Vol. III implementation detail |
| Engine/tech programmer | Prelude → Vol. II 1–2, 7 → all Vol. III → Vol. IV | Vol. I chapter 6 |
| Producer / business | all Vol. I → Vol. II 11–16 → Vol. III 15–17 | redstone and rendering |
Each volume opens with a short introduction stating the volume's thesis and a map of its parts. The appendix holds a timeline, people, a two-edition comparison table, and a glossary — for reference, not argument.
3Why the book starts from the voxel
Volume II chapters 1–4 (voxel, verbs, survival, Creative mode) are the book's frozen layer — every later "Minecraft feel" judgment routes back to them. They sit after history and before technology because history supplies the evidence of where they came from and technology supplies the price they cost. Skip them and every later judgment is an assertion you can neither agree with nor refute.
4Where to start
Volume I opens with From Infiniminer to Cave Game — the natural entrance for most readers. If you care about why the system works, go straight to Volume II; if engines and scale pull you, Volume III is open. Leave Volume IV for last — it is an exam, and exams presuppose the course. If you have not yet read The Thesis of This Book and Method and Standards, read those two first: one says what the book is proving, the other says why it deserves your trust.
5What this chapter leaves behind
- For players: this book translates "feelings" into "mechanics"; bring your play experience and audit the translation.
- For developers: the skipping routes are designed — but Volume II's first four chapters are not skippable. Three hours saved on the foundation becomes threefold confusion in Volume IV.