A01Purpose & Audience
The rulebook IS the game
Without the rules, the box is only components; the rulebook is the only universal interface every board game shares.
Punchboard argues that the rulebook converts a box of tokens into the designer's actual game. Michael Heron notes there is no shared interface across board games 'except the manual' — which makes manuals a universal accessibility surface.
"Without the rules, all you're left with is a box full of tokens and pieces."
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
A02Purpose & Audience
Minimise cognitive load — the one-sentence rule
Every editorial decision should be judged by whether it reduces the effort required to learn and remember the game.
Curby's entire 13,000-word style guide reduces to this maxim, and explicitly says to break any other rule in the guide when breaking it serves the reader.
"If someone can't learn the game, they won't play the game."
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
A03Purpose & Audience
A rulebook has (at least) three audiences
First-time learner, mid-game look-up, and returning player after months away. All three must be served by the same document.
Entro Games names these three; Curby expands the list to include teachers preparing to teach, veterans checking edition changes, and readers who only want the setup diagram.
Optimise for as many relevant use cases as possible, not just the first read.
Source: How to Write a Rulebook for Your Board Game – Entro Games
A04Purpose & Audience
Write to a defined audience, not to everyone
Gateway games and hobbyist games justify different jargon levels, tone and depth. Decide who you are writing for before you write.
BGG designer J C Lawrence: 'Know your audience. If your audience does not include light players learning the game, then there is no need to address or support them.' BA Games counters that you cannot be everything to everyone — follow industry norms instead.
Tone and conventions should fit the target audience without alienating a wider audience.
Source: BGG: In-depth information about designing a good rulebook
A05Purpose & Audience
Most people do not learn from the rulebook — but someone has to
In practice one person reads the rules and teaches the group. The rulebook's job is to start that chain reaction and then answer questions during play.
Repeated observation across BGG threads. This reframes the rulebook as (a) a teaching enablement tool and (b) an in-play reference, not a self-study textbook.
"The purpose of the rulebook is to get the chain reaction started and to answer questions that come up during play."
Source: BGG: Tutorial differences between videogames and board games
A06Purpose & Audience
Nobody starts a thread to say the rules were clear
Rules-forum volume is a biased sample; absence of complaints is invisible. Use it as a signal, not a verdict.
Counterpoint raised in the text-comprehension thread. Chris Wray nonetheless attempted to quantify rulebook quality by counting BGG rules questions per game.
Repeated queries on the same rule on a game's BGG page reliably indicate that rule is unclear.
Source: BGG: Rulebooks and text comprehension. A history of misunderstandings.
B01Structure
General-to-specific, and follow the arc of a session
Proceed from generalities to details, tracking a game session from setup to scoring, so readers build a mental model before receiving detail.
Curby's canonical ordering; echoed by nearly every other source. This is the single most agreed-upon principle in the corpus.
Rulebooks should build a lexicon first (theme -> goal -> components -> setup) then spend it (gameplay -> end -> reference).
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
B02Structure
State the goal / victory condition early
Readers who know the objective can attach every subsequent rule to a purpose. Burying the win condition wastes the whole first read.
Herc du Preez places Victory Condition before the detailed rules explicitly: 'Having the goal in mind gives context to all actions.' Entro says how-to-win belongs in the opening paragraph.
"The goal is the game."
Source: BGG: Rules Writing 101 (with an example)
B03Structure
Do not open with Setup
Setup instructions are meaningless before the reader knows the theme, the goal and the rough shape of a turn.
A veteran teacher in the comprehension thread: 'A typical rulebook begins with set-up. Please don't do that. I don't know what those pieces are... I have no context.'
Order should follow conceptual assimilation, not necessarily temporal order of the game.
Source: BGG: Rulebooks and text comprehension. A history of misunderstandings.
B04Structure
Illustrated component list before anything else mechanical
A labelled picture of every component lets buyers verify the box, learn the vocabulary, and anchor later references.
The most frequently repeated concrete request in the whole corpus. Paul Grogan lists 'a detailed components list with images' as a requirement for an excellent rulebook.
"First page should have an inventory of all the parts, including pictures of each piece."
Source: BGG: What makes a good rulebook? (2021)
B05Structure
Setup deserves a full diagram, not just prose
A labelled photo/diagram of the initial table state lets a reader check their work visually while following the numbered steps.
Requested repeatedly; Entro suggests even a Tabletop Simulator screenshot with letters added is enough during development.
Use non-numeric labels (A, B, C) in setup diagrams so numbers are not misread as quantities.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
B06Structure
Overview before detail (two passes over the same material)
Give a short bullet list of what a turn contains, then explain each item. Readers learn the map before the terrain.
Boardtastic guide formalises this as Theme -> Overview -> Structure -> Actions -> Rules -> Exceptions -> Victory -> Summary -> Strategy.
Explaining the same concept twice at different resolutions is a feature, not redundancy.
Source: BGG: The Boardtastic Guide to Explaining Rules... Good
B07Structure
Group rules where players will look them up
Place a rule under the heading a confused player will reach for mid-game, even if that is not where it first becomes relevant.
Shellhead: break rules down so they are covered in the relevant phase, 'so if people have a rules question at any point, they at least know they can find the answer in that phase section.'
Organisation is a retrieval problem as much as a teaching problem.
Source: Best rulebooks? – There Will Be Games forum
B08Structure
Short rulebooks teach in play order; long ones need alphabetical or subject grouping
Under ~4 pages, present rules in the order they arise. Over ~20 pages, group by subject and add an index — or order the reference alphabetically.
marc lecours' rule of thumb, with wargames cited as the canonical example of a conventional, predictable section order.
Wargames are readable despite length because they always use the same conventional order.
Source: BGG: What makes a good rulebook? (2021)
B09Structure
Isolate exceptions and special cases into their own section
Core rules get cluttered and unlearnable when every edge case is inlined. Teach the common path, then handle exceptions.
Herc du Preez: 'Core rules are often unnecessarily cluttered with exceptions that should not even be mentioned at that stage.' Jamey Stegmaier treats the word 'exception' as a design smell.
"In 99% of cases, if I use the word 'exception' in the rulebook, it's a sign of something that should be removed from the gameplay."
Source: What Makes a Great Rulebook? – Stonemaier Games
B10Structure
Callouts: rules that live outside the linear flow
Procedures triggered at many different times deserve a titled, visually-distinct callout box, referenced by name and listed in the TOC and index.
Curby treats callouts as first-class rulebook sections — unlike examples and diagrams, callouts may introduce new rules.
Give each callout a title, place it near first mention, and index it.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
B11Structure
Be willing to break conventional order when the game demands it
Section order serves learning and retrieval, not tradition.
Jamey Stegmaier confirms he reordered sections for Vantage and others when the flow of the game required it.
"My goal is always to structure each rulebook so it (a) helps players learn and (b) helps players find answers."
Source: What Makes a Great Rulebook? – Stonemaier Games
B12Structure
Avoid walls of text
Err on the side of too many paragraph breaks; combine later. Walls of text defeat both reading and skimming.
Curby; C.J.C. (a lawyer who explains complex law for a living) lists 'use lots of empty space' among eight technical-writing rules for rulebooks.
"Walls of text overwhelm people."
Source: BGG: how to write rule book
B13Structure
The chicken-and-egg problem is real and unsolvable — choose the lesser confusion
Games are loops; no rulebook can be fully linear. At some point you must reference an undefined concept.
Resonym demonstrates this with a two-paragraph game (Buffalo) and concludes there is no trick — only judgement about which ordering confuses less.
If you must forward-reference, cite the target explicitly: '(see 10.0 Retreat)'.
Source: Resonym | Writing Rulebooks
B14Structure
One linear read should be enough
A useful quality metric: how much did the reader have to jump around, and how many undefined concepts appeared before definition?
Ryan Migalla's proposed core principle, endorsed in the Stonemaier comments thread.
"A rulebook should only have to be read through once, linearly, to understand the game."
Source: What Makes a Great Rulebook? – Stonemaier Games
B15Structure
Define every term at first use
Using a game-specific noun before defining it is the most commonly cited reader irritation in the corpus.
Sophie's opening post in 'What makes a good rulebook?'; echoed in the Pathfinder ACG criticism.
"Using game-specific terms before explaining them is always an absolutely terrible idea."
Source: BGG: Worst rulebook ever!
C01Teach vs Reference
The central tension: one document, two incompatible jobs
A rulebook must be a linear tutorial for new players AND a random-access reference for experienced ones. These demand opposite organisations.
Named independently by Resonym ('the single biggest challenge'), Isaac on BGG, and Entro. Isaac concludes moderate-to-heavy games need two documents.
"Trying to make a well-written rulebook that has the dual purpose of teaching and serving as a reference is a self-defeating endeavor."
Source: BGG: Worst/Best written rules
C02Teach vs Reference
The dual-document model (Learn to Play + Rules Reference)
Book 1 tells the story of playing the game in play order; Book 2 is a formal, alphabetical or subject-indexed reference for established players.
Popularised by Fantasy Flight Games (Marvel Champions, Arkham Horror LCG); praised repeatedly on BGG for letting you 'find anything you need in seconds'.
Computer manuals have always shipped this pair: a how-to book and a lexical reference.
Source: BGG: Examples of well-written game rules?
C03Teach vs Reference
Dual-document failure mode: rules that exist in only one book
If the Learn-to-Play contains rules absent from the Reference, the Reference stops being trustworthy and players lose faith in both.
Documented in detail for Gloomhaven: Jaws of the Lion — e.g. the 10-curse limit appeared only in the LTP book, not the Glossary.
"Every rule should be every place you would expect it to be in the Glossary — or else the Glossary stops being very useful."
Source: BGG: Sometimes finding the rulebook organization annoying (Jaws of the Lion)
C04Teach vs Reference
The Playbook / walkthrough model
A separate booklet walks players through a scripted opening (often with unshuffled decks) so the first game teaches itself.
GMT/COIN wargames pioneered this; Root's walkthrough book is credited with making a wargame-shaped design mainstream. Fog of Love instructs players not to shuffle on first play so the guide can predict their hands.
"Stop — read the playbook and play through using the physical game. Then use the rule book as reference."
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
C05Teach vs Reference
Tutorial-style rulebooks trade look-up for onboarding
Progressive-disclosure rulebooks (Jaws of the Lion, Avalon Hill 'Programmed Instruction') teach beautifully but scatter rules, making later reference painful.
Consistent complaint across the Tutorializing and JotL threads: 'You would encounter new rules in odd little places... it was difficult to look up rules.'
If you tutorialise, you owe players a complete, separately-organised reference.
Source: BGG: Tutorial differences between videogames and board games
C06Teach vs Reference
Video tutorials complement, they do not replace
Not every buyer has internet, a tablet, or the inclination. The printed book must stand alone.
Curby is explicit. Meeple Mountain adds: do not let blind playtesters use how-to-play videos, because not all owners will have them.
"The rulebook included with the game should be able to stand on its own as a complete resource."
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
C07Teach vs Reference
Diátaxis: four documentation modes, cleanly separated
Tutorial / How-to / Reference / Explanation are distinct genres with distinct rules. Mixing them is why documentation feels wrong.
Recommended in the Stonemaier comments as a transferable framework: the Playbook is a Tutorial, the rulebook body is How-to, the appendix is Reference, designer notes are Explanation.
Separating the four modes explains most rulebook structure debates.
Source: Diátaxis – a systematic framework for technical documentation
C08Teach vs Reference
Board games cannot rely on tutorials the way video games can
Software enforces its own rules; a board game's players must enforce them, so every rule must be stated somewhere retrievable.
Repeatedly argued in the Tutorializing thread. Also: mixed-experience tables make mandatory tutorials socially unworkable.
"Video games enforce the rules, so you don't really need to know the rules, just how to play."
Source: BGG: Tutorializing
D01Language
Framing: link the new concept to a familiar mental model first
Rephrase a confusing rule so it first establishes the frame, then states the change within that frame.
Curby's second key skill, with four worked before/after examples. E.g. 'Take 1 of each type of resource you roll' -> 'For each type of resource you roll, take 1 die of that type.'
Reframing removes ambiguity without adding words.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D02Language
Conditions and triggers before effects
'If you roll a 5 or higher, draw a card' beats 'Draw a card if you roll a 5 or higher' — skimmers can skip effects whose condition is unmet.
Curby; also C.J.C.'s rule 5: 'always put the most important clause of your sentence first.' Put the failure branch in a separate sentence.
Front-loaded conditions cause fewer misplays (applying an effect at the wrong time).
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D03Language
Short sentences, one action each
Split any sentence that describes multiple actions, or that contains parentheses plus a calculation.
Curby; Entro's 'one-breath rule': if you cannot speak the sentence in one breath, it is too long.
"When in doubt, make your sentence shorter. Or make a list."
Source: BGG: how to write rule book
D04Language
Active voice, second person, imperative
'Pay $1 to gain 2 resources' beats 'The player pays $1...'. Reserve passive voice for global prohibitions and flavour.
Stonemaier house style; Curby adds the useful exception: 'Mountain tiles cannot be removed from the map' states a universal truth that 'Players may not remove mountain tiles' does not.
Start sentences with verbs where possible — the verb is the instruction.
Source: What Makes a Great Rulebook? – Stonemaier Games
D05Language
Modal verbs are load-bearing: may / may not / cannot / must / should
may = optional action. may not = forbidden though desirable. cannot = physically impossible. must = compelled (use sparingly). should = avoid entirely in rules.
Curby's canonical breakdown. All rules are requirements by default, so 'must' should be reserved to flag an action a player would rather avoid.
Stonemaier: 'Remove all instances of should and highlight any instances of except and remember.'
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D06Language
gain / take / give / earn are not synonyms
gain = from an unlimited supply. take = from a limited supply or from another player. give = grant to another player. earn = generic.
Curby's distinction, adopted almost verbatim in the Stonemaier style guide ('Use gain, not take, when referring to a player earning something from the general supply').
The distinction silently communicates whether an action affects other players.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D07Language
Turn / Round / Phase / Step must be defined and never overloaded
Pick one hierarchy and never reuse a level's name for another level. Wargames traditionally invert Turn and Round relative to modern eurogames.
Extended discussion in the Rulebook Editing Style Guide thread; Curby codifies turn -> round -> (act/epoch/season), with phases and steps subdividing turns.
"Do not reuse 'phase' within a single game to describe multiple levels of this framework."
Source: BGG: Rulebook Editing Style Guide (2020)
D08Language
each vs every vs all
each = applies individually to distinct members. every / all = applies to the group as a whole.
Curby. Misuse here silently changes whether an effect resolves once or N times.
'Each card is scored according to its Infamy stat' vs 'every Hero enters the dungeon'.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D09Language
when / whenever / if / at
when = once, at a predictable time. whenever = repeatable, many causes. if = might never happen. at = focuses on a point in time.
Curby. Choosing 'when' for something that may never happen implies to the reader that it will.
"If activated, draw two cards and discard one."
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D10Language
Singular 'they' — and when to replace it
Use they/them/their. Never he, she, (s)he, he or she. Where 'they' could bind to the wrong plural noun, replace with 'that player'.
Curby, Resonym, Stonemaier and multiple BGG editors agree. The ambiguity case was raised by Joe Farrell in the style-guide thread and folded into the guide.
'If a player has no Scientists, that player may not research Technologies.'
Source: BGG: Rulebook Editing Style Guide (2020)
D11Language
Hyphenate face-up / face-down for reading flow
Grammar says hyphenate only as a pre-noun adjective, but consistent hyphenation removes a real stumbling point observed in blind tests.
Andy Van Zandt observed readers audibly stumble on 'faceup' during read-alouds; 'face down' also collides with the idiom 'to face down'.
"You will see this when you blind playtest rules and someone reading them aloud hits 'faceup' and stumbles."
Source: BGG blog: Writing Rules – facing up to breaking the rules (Andy Van Zandt)
D12Language
Prefer 'dice' as both singular and plural in rules
'Die' collides with the verb 'to die', which frequently appears in game contexts; consistent 'dice' reduces parse failures.
Andy Van Zandt's argument; Curby notes the regional split and simply asks for consistency.
"The goal is for players to have a smooth and seamless read-through."
Source: BGG blog: Writing Rules – facing up to breaking the rules (Andy Van Zandt)
D13Language
Delete 'simply'
'Simply' adds words, adds no information, and reads as condescending when the reader is in fact confused.
Michael Berg's correction inside Rules Writing 101, which the author accepted and edited into the original post.
"One does not simply write a rulebook."
Source: BGG: Rules Writing 101 (with an example)
D14Language
Mechanical phrasing over thematic phrasing (usually)
'Place 2 Cog Tokens on each Machine Card' is safer than 'Upgrade each Machine with 2 Cogs' — components and actions are unambiguous.
Curby, with caveats for highly thematic games; Entro agrees: pair the mechanical noun with a thematic qualifier ('Resource tiles' vs 'Scoring tiles').
Components are the player's most direct interface; name them literally.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D15Language
Piggyback on knowledge players already have
If a well-known word already maps to a concept, use it. A 'Flying' character is learned instantly; an 'Aether Jaunt' ability is not.
Curby, citing Mark Rosewater's term. Applies to keywords, phrasing and icon choice alike.
Do not fight what people already know — never reuse a familiar word for an unfamiliar concept.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D16Language
Avoid Latin abbreviations, contractions and ampersands
i.e., e.g., etc., cont., approx., & — each is a small comprehension tax, and heavier for non-native readers.
Curby recommends expanding them when space allows and, if used, using them correctly (i.e. = restatement, e.g. = example).
Stonemaier's house style nonetheless permits 'e.g.,' inside parentheses — consistency matters more than the choice.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D17Language
Numbers: digits for game quantities, words for flavour
Use digits when counting components or mechanical values; spell out small thematic numbers and any number starting a sentence.
Stonemaier ('use numerals whenever possible, but not at the beginning of a sentence') and Curby, who adds the mixed-case trick: 'Place 3 two-headed dragons in the Dragons' Nest.'
For small ranges, listing every value ('0, 1, or 2') can beat 'fewer than 3'.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
D18Language
Parentheses clarify; they never introduce rules
A parenthetical must be removable without losing a rule. Never bury a rule in an aside — or in an example.
Curby; Paul Grogan lists 'rules hidden only in examples' as a red flag he actively hunts for.
"A lack of examples, lack of images... Rules hidden only in examples is another one."
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
E01Terminology
One concept, one word — forever
Never use gratuitous synonyms. If it is an Attack, it is never a Strike or an Assault.
The single most repeated piece of advice in the entire corpus, from Cardboard Edison to Russ on BGG to every professional style guide.
"Refer to the same actions, components and game sections by the same terms every time in rules, card text and reference materials."
Source: Cardboard Edison – Best Practices / blog
E02Terminology
Consistency AND deliberate inconsistency
Things should look and sound the same only if they are the same — and different only if they are different.
Curby's sharpest formulation. Deliberate difference is how players spot that two similar-looking abilities behave differently.
"When players can confidently identify similarities, differences are also more easily identified."
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E03Terminology
Name similar concepts so they cannot be conflated
Two commerce roles should not be 'Traders' and 'Merchants'. Prefer keywords starting with different letters, especially for headings.
Curby. If you cannot find a meaningful distinction between two names, that is evidence the two concepts should be merged.
Avoid 'Shipyards' and 'Shipbuilding' as sibling headings.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E04Terminology
Templating: things that work the same should look the same
Develop one syntactic pattern for each family of effects (all character abilities, all card costs) and apply it everywhere.
Curby's third key skill. 'Draw a card into your hand' vs 'Take 1 card from the deck' forces players to hunt for a difference that does not exist.
Consistent application of even a mediocre template beats a chaotic mix of good ones.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E05Terminology
Capitalise selectively — capitals are a limited budget
Capitalise only instances that refer to a specific in-game component, action or value. Over-capitalisation dilutes attention and stalls reading.
Curby's balanced method; Resonym: 'If you have too much capitalization, it all blends together and is useless.'
'Gain 5 Gold from the central supply' vs 'each player keeps their gold on their player mat'.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E06Terminology
Fix a canonical order for repeated sets
If resources are labour/stone/wood, list them in that order in the component list, setup, every cost, and every diagram.
Curby, with a worked consistency table. Even the regions that produce those resources should be listed in the same order.
This is invisible when done and quietly exhausting when not.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E07Terminology
Board vs mat, and other component-noun discipline
A 'mat' is unique to a player; a 'board' is shared. Small distinctions like this remove a whole class of ambiguity.
Stonemaier house style. A commenter reports this one line immediately fixed their naming confusion.
"A 'mat' is unique to a player. A 'board' is available to all players."
Source: The Stonemaier Games Style Guide
E08Terminology
Keep the keyword count low
Every keyword is a word the player must learn. Dominion's power comes from having only Action, Buy, Gain, Card — used with absolute consistency.
I Slay the Dragon's analysis: because Dominion's few keywords never drift, brand-new cards are parseable at a glance.
"No one wants to learn a language to learn a new game."
Source: Laying Down the Law (a guide to rulebook writing) – I Slay the Dragon
E09Terminology
Avoid hobby jargon in gateway games
'Tableau', 'rondel', 'engine' are fan service to insiders and a wall to newcomers. Use descriptive terms or define on first use.
Curby suggests 'collection' and 'action wheel' as replacements.
Jargon can be a wink to those in the know — and a door closed on everyone else.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
E10Terminology
Write a style guide before you write the rules
Even a whiteboard listing your capitalisation, terminology and formatting choices prevents most consistency defects.
Stonemaier's explicit 'core recommendation'; Entro says the same. This is cheaper than any editing pass.
"The core recommendation I'm trying to make today is that you have a written style guide."
Source: The Stonemaier Games Style Guide
F01Examples
Examples earn their space by covering edge cases, not obvious cases
Do not illustrate the move everyone already understands. Illustrate the interaction that will otherwise become a forum thread.
I Slay the Dragon; Russ gives the canonical test case: if archer OR catapult gives +1, show an example with BOTH to settle whether it is +1 or +2.
"If you don't illustrate edge cases, you'll send players directly to the forums."
Source: Laying Down the Law (a guide to rulebook writing) – I Slay the Dragon
F02Examples
Maximise example 'coverage'
One diagram should resolve several questions at once — scoring and non-scoring cases, diagonals, shared adjacency, depleted tiles.
Curby's worked Blacksmith/Iron Mine example enumerates five distinct questions a single richer diagram can answer.
"A simple diagram that only shows one Blacksmith flanked by two Mines is not very useful."
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
F03Examples
Make clear what in an example is arbitrary
Readers infer rules from examples. If your tableau always shows five cards, some readers will believe tableaus must have five cards.
Curby warns this can actively limit how players play, robbing the design of depth.
Examples can accidentally introduce unintended rules.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
F04Examples
Long walkthroughs beat many isolated snippets
One multi-turn worked example shows the system interacting with itself; a dozen one-line examples only show parts.
Argued on BGG (t897413) and repeatedly praised in 1960: The Making of the President and Combat Commander.
A full example of play over two consecutive turns is a widely-requested feature.
Source: BGG: In-depth information about designing a good rulebook
F05Examples
Examples should show motivation, not just legality
'Alice takes Recruit Troops because Bob already took Take Stone' teaches the game's texture, not merely its syntax.
Raised on BGG as a strong plus, especially for readers deciding whether to buy.
Beware the counter-view: J C Lawrence argues rules should never suggest evaluations or strategies.
Source: BGG: Examples of well-written game rules?
F06Examples
Diagrams beat examples where space allows
Spatial, adjacency and setup rules are almost always clearer as a labelled picture than as prose.
Resonym ranks diagrams above examples; I Slay the Dragon and Meeple Mountain both call for figure numbers referenced from the text.
Label figures (Figure 1, Figure 2) and reference them explicitly from the rules text.
Source: Top Six Rules for Rulebook Writing – Meeple Mountain
F07Examples
Include an 'anatomy' diagram for information-dense components
Label every zone of a card, tile or player mat once, then refer to those labels by name thereafter.
Resonym; Herc du Preez calls this the Component Breakdown and places it before the rules.
Anatomy diagrams convert a component into shared vocabulary.
Source: Resonym | Writing Rulebooks
F08Examples
Set examples visually apart from rules
Italics, tint blocks or sidebars — anything that lets a re-reader skip examples and lets a learner find them.
Curby (italics for examples, bold for keywords); Meeple Mountain (italics for side notes and examples).
Never set rules themselves in italic.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
G01Layout
Minimum body text 10pt; err larger
Jamey Stegmaier: 10pt is the bare minimum, sometimes larger depending on typeface. Accessibility guidance pushes towards 12pt.
BGG's classic complaint set includes Race for the Galaxy's ~6-8pt text. Accessibility sources put 'clear print' minimum at 12pt and large print at 16pt Arial.
"10pt is the bare minimum, but sometimes we go bigger based on font type."
Source: What Makes a Great Rulebook? – Stonemaier Games
G02Layout
180 x 240 mm is a sweet-spot rulebook size
Big enough for visuals and examples, small enough to leave open on the table during play.
Stonemaier's stated preference. A5 booklets fit smaller boxes; A4 allows larger setup diagrams.
Page count must be divisible by 4 — plan spreads, not pages.
Source: What Makes a Great Rulebook? – Stonemaier Games
G03Layout
Use facing pages deliberately
If component list and setup will not fit on one page, make them facing pages so the reader never turns back mid-setup.
Resonym. Curby adds: short sections should not break across page boundaries, and 2-page sections belong on facing pages.
Books come in spreads of 4 pages; design for the open book, not the single page.
Source: Resonym | Writing Rulebooks
G04Layout
High contrast for rules text; save low contrast for decoration
WCAG-style targets: 4.5:1 for body text, 3:1 for large or bold text. Test by converting the page to greyscale.
MINIFINITI's analysis. Never print rules on textured art or dark backgrounds — a recurring BGG complaint since 2007.
"Never print rules against a dark colored background or pattern."
Source: BGG: Examples of well-written game rules?
G05Layout
Emphasis hierarchy: bold for keywords, italic for supplemental, no underline
Underlines clash with descenders and hurt legibility. All-caps is less readable than sentence case; prefer real small caps.
Curby; Stonemaier bans underlining outright. Meeple Mountain reserves ALL CAPS for the very few rules players most often miss.
Overuse of emphasis 'leads to a cacophony of competing voices'.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
G06Layout
Sans-serif, plain background, generous white space
The most common reader-preference profile in the corpus: sans serif, simple layout, sensible order, light on jargon, concise, correct grammar.
A BGG user's six-word answer to 'what makes a good rulebook'; supported by dyslexia guidance (Arial/Verdana/Tahoma, 1.5 line height, avoid italics for long passages).
"Background art/texture behind text: ugh, it makes it harder to read. Blank background, please."
Source: BGG: What makes a good rulebook? (2021)
G07Layout
Marginal summaries are a proven hybrid
Alea-style rulebooks run the full explanation in the main column and a one-line summary in the margin — teaching and reference on the same page.
Praised repeatedly for Castles of Burgundy and the Alea series. Rio Grande's side-strip is an older variant of the same idea.
"Long form rules, and then in the margins, just the short form rule."
Source: BGG: Good Rulebooks (2021)
G08Layout
Use the back cover — it is the most valuable page in the book
Turn overview, icon key, setup quantities by player count, and often the index belong on the outside back cover.
Multiple independent requests; Stonemaier reserves the last page for icon guide, game flow and/or index.
"Use the back cover as a player aid. So many rulebooks waste this really useful space."
Source: BGG: What makes a good rulebook? (2021)
G09Layout
Compose in a word processor, lay out in InDesign
Text first, layout second. Word/Google Docs for drafting and sharing; InDesign (or equivalent) only once content is stable.
Consensus in the rulebook-design thread. Google Docs specifically recommended for sharing drafts with test readers.
Editing before layout lets an editor reorder whole sections without costly re-layout.
Source: Michael Lee, Editor — editing.curby.net
G10Layout
Layout cannot rescue bad writing
Sidebars, boxes and illustrations can absorb definitions and flavour, but they do not fix unclear sentences.
Rob Harper in Rules Writing 101, and echoed by an editor: 'Flavor, humor, indexing and diagrams are all useless if the sentence structure and flow of your rules stink.'
"Of course, layout is no substitute for badly written rules."
Source: BGG: Rules Writing 101 (with an example)
H01Reference
Index vs table of contents are different tools
A TOC lists sections in order; an index maps keywords — including words that are not section names — to pages. Long rulebooks need both.
Debated at length on BGG. Wargamers insist on 'an exhaustive or close to exhaustive index'. A keyword index remains useful long after the TOC stops being.
"An alphabetical index is recommended as that's how people look things up."
Source: BGG: Glossary or alphabetical TOC/Index really needed?
H02Reference
Missing index is a top-tier complaint
Mice & Mystics and Space Base are both cited primarily for lacking an index, not for being badly written.
Going Analog's 'absent index' verdict on Space Base; the Mice & Mystics complaint recurs across a decade of threads.
"They could have at least put an index in there, as I spend a lot of time looking up rules."
Source: BGG: Worst rulebook ever!
H03Reference
Glossary placement: front adds friction, back adds page-flipping
Front-loaded glossaries delay the rules; back glossaries require flipping. Practical compromise: define at first use, put the glossary on the inside back cover, and index everything.
Argued out in Rules Writing 101 between Herc du Preez and ampoliros; Matthew Proper-Lee proposes inside-back-cover glossary, outside-back-cover icon key and flow.
"Having to page back and forth is the hallmark of a badly written boardgame rulebook."
Source: BGG: Rules Writing 101 (with an example)
H04Reference
A card/action appendix beats a scattered FAQ
Alphabetical per-card clarifications (Dominion, Ark Nova, Puerto Rico's per-building notes) resolve most questions without a separate FAQ.
Praised repeatedly; Puerto Rico is singled out for putting clarifications directly under each building description.
"Every building has helpful clarifications right underneath its description, eliminating the need for supplemental online FAQs."
Source: Laying Down the Law (a guide to rulebook writing) – I Slay the Dragon
H05Reference
If a rule confuses testers, rewrite it — do not bolt on an FAQ
An FAQ entry is a patch over a defect in the rules text. Prefer to fix the rule; use FAQs for genuinely rare interactions.
Russ on BGG; Entro says the same and adds 'sometimes the best thing to do is to engineer them out'.
"If a rule is found to be confusing for significant numbers of readers, rewrite the rule; don't add a separate FAQ at the end."
Source: BGG: Good Rulebooks (2021)
H06Reference
A graphical / iconographic index is a strong pattern
Gloomhaven's picture-led index is repeatedly named as best-in-class for mid-game look-up in a dungeon crawler.
Cited in the Sword & Sorcery glossary discussion. Wikipedia-style glossaries are noted to fail when pictures are not adjacent to their definitions.
"IMO the graphical index Gloomhaven uses is unsurpassed."
Source: BGG: Glossary or alphabetical TOC/Index really needed?
H07Reference
An 'often forgotten' / 'oft-missed rules' section is cheap and valuable
A short end-of-book list of rules groups commonly get wrong on their first game prevents a whole class of misplays.
Attika and Brass are both praised for this. It is one of the highest value-per-word features available.
"A very helpful thing at the end of the rules is a list of a few things often forgotten in a first game."
Source: BGG: Best Rule Book (In Your Humble Opinion)
H08Reference
Digital and living rules are now expected
A searchable, hyperlinked PDF answers questions that no index can. Maintain a public living-rules page for errata.
Curby endorses digital rulebooks as a complement; players report using PDF text search as a substitute for a missing glossary.
Ctrl-F is the index that every game already ships with — if you publish the PDF.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
I01Player Aids
Write player aids before you write the rulebook
During early playtesting rules are in flux; player aids capture what actually matters and become a shipped component later.
Jamey Stegmaier's stated workflow; Cole Wehrle and Sen-Foong Lim independently reported the same practice.
"For initial local playtesting, I create player aids instead of a rulebook."
Source: What Makes a Great Rulebook? – Stonemaier Games
I02Player Aids
Player aids should duplicate, not replace, rulebook content
If a rule exists only on a player aid, players who lose the aid lose the rule — and reviewers will notice.
Stated forcefully on BGG about Mage Knight, whose reference cards hold rules absent from the book.
"Reference cards should be used as a rules reference, as their name implies."
Source: BGG: Rules missing from Rulebook v1.0 (Triplock)
I03Player Aids
One aid per player, always
Shared aids create queues and reading-over-shoulders; per-player aids also let players self-serve instead of interrupting the teacher.
Board Game Sanctuary's blunt version: 'NEVER cheapen out on summary action cards for EVERY PLAYER.'
Merchants & Marauders is repeatedly cited as a game whose aid carries most of the teaching load.
Source: BGG blog: 10 Board Games Rules Mistakes I Have Made
I04Player Aids
Push rules onto the components themselves
Text on cards, icons on player mats, reminders on the board — every rule the components can carry is a rule players never look up.
Stonemaier's philosophy is text (not icon soup) on cards, self-sufficient enough that no appendix is needed.
Move icons to high-traffic surfaces (player mats), keep card text word-only where space allows.
Source: What Makes a Great Rulebook? – Stonemaier Games
I05Player Aids
Setup information must not live only on a player aid
Setup quantities by player count are the single most re-looked-up fact in most games. Put them in the book AND on the aid.
A specific, repeated annoyance on BGG. Also: 'have key setup information — starting resources and differences based on player count — somewhere easy to find.'
"Setup being only on a player aid sheet tends to really annoy me."
Source: BGG: Worst/Best written rules
J01Process
Write the rulebook early enough to iterate, late enough to be stable
Player aids during early testing; first real draft when approaching blind playtesting; expect at least three full rewrites.
Stonemaier's timing; Carl Nyberg's rule of thumb: 'write the whole thing, then rewrite it two times. The third iteration will be way better than the first.'
Keep the rulebook version-synced with component versions — mismatch is a classic defect source.
Source: What Makes a Great Rulebook? – Stonemaier Games
J02Process
Blind playtesting is primarily a rulebook test
By the time you blind test, you should already believe the game is fun. What you are testing is whether the document works alone.
Hilko on BGG: 'To me, blind testing is testing the written rules.' Stonemaier assigns blind testing 25% weight for rulebook improvement specifically.
"The goal of a blind playtest should not be to improve game design. It's a rules test only."
Source: Top Six Rules for Rulebook Writing – Meeple Mountain
J03Process
Do not help blind testers
Intervening trains testers to look at you instead of the page, and destroys the data you came for.
Resonym's Tip 4, with a worked example of letting testers play an entire game wrongly rather than correcting them. Intervene only when a misreading will invalidate the rest of the test.
"If you swoop in to save your players from mistakes, they become reliant on you."
Source: Resonym | Writing Rulebooks
J04Process
Warn blind testers what they are in for
Rulebook tests are not fun. Say so up front, and make clear that confusion is the document's fault, not the tester's.
Resonym: 'After the time my wife broke down in tears during a rulebook test, I always make sure playtesters know what they're getting into.'
Set expectations: half the evening may be spent on rules, and that is the point.
Source: Resonym | Writing Rulebooks
J05Process
Test with non-gamers
Experienced gamers are skilled rulebook readers and will paper over your defects with genre knowledge.
Resonym Tip 2. Brandon the Game Dev extends this to recruiting non-native English speakers and professional writers as beta readers.
"If your rulebook can teach your grandma how to play your game, then it can teach anyone."
Source: Resonym | Writing Rulebooks
J06Process
Play dumb: 'What do I do now?'
Ask the tester to teach you, and stop yourself at every juncture that historically trips players up. Optionally, do it wrong on purpose and see if they catch you.
Resonym Tip 3 — the most actionable observation technique in the corpus.
"Another one of my favorite phrases is: How should I make that decision?"
Source: Resonym | Writing Rulebooks
J07Process
Read the rulebook backwards, section by section
Reading in reverse order prevents you from skimming ahead on autopilot and surfaces isolated defects.
Jamey Stegmaier's personal QA technique.
"I find it helpful to review a rulebook backwards (section by section)."
Source: What Makes a Great Rulebook? – Stonemaier Games
J08Process
Time the look-up, not just the read
At pre-production copy stage, test how fast a player can find a specific answer mid-game. Slow look-up is a structural defect.
Stonemaier's explicit PPC test criterion.
If you cannot find the answer quickly, revise the structure — not the sentence.
Source: What Makes a Great Rulebook? – Stonemaier Games
J09Process
Hire a professional editor and a separate proofreader
Editors catch 80-95% of errors on a pass; two sets of eyes at different stages is materially better than one.
Curby cites The Copyeditor's Handbook. Meeple Mountain quotes typical freelance rates of USD 25-50/hour. Obsession's designer publicly documents deciding a proofreader was unnecessary — and regretting it.
"I have learned a lesson that a professional proofreader is required in all future projects."
Source: BGG: OFFICIAL Obsession Rulebook and Glossary (errata thread)
J10Process
Edit before layout, proofread after
Developmental/copyediting happens on the text so sections can be reordered freely; proofreading happens on the laid-out file to catch layout-introduced errors.
Michael Lee's stated professional workflow.
"This allows me to reorder and rewrite entire sections without requiring costly graphic design updates."
Source: Michael Lee, Editor — editing.curby.net
J11Process
Rulebook exchanges and design communities are free QA
Designers swap rulebooks and blind tests; Discords (Break My Game, Editors' Hangout) and BGG threads provide structured critique at no cost.
Multiple BGG threads organise exactly this. Break My Game is recommended in the Stonemaier comments.
"A good rulebook is just as important as having good blind playtests."
Source: BGG: How do you go about blind playtesting?
J12Process
Ask the winner how they would teach the game
Post-playtest, the winner's spontaneous teach reveals the order in which the game actually makes sense to a learner.
Entro Games' technique for discovering natural structure.
Their spin on the teach is data about your structure.
Source: How to Write a Rulebook for Your Board Game – Entro Games
K01Accessibility
Double-code every distinction
Never carry meaning by colour alone. Pair colour with shape, icon, texture or label.
Curby's inclusive-design section; Stonemaier lists 'dual-coded icons' and 'uniquely shaped tokens' among its accessibility metrics.
Helps colour-vision-deficient players, and also everyone playing in dim light.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
K02Accessibility
Contrast targets: 4.5:1 body, 3:1 large text
Meet WCAG-style ratios for anything a player must read; reserve low contrast for decorative elements only.
MINIFINITI. Colour blindness affects roughly 8% of men and 0.5% of women — around 300 million people globally.
Greyscale test: if the page is unreadable in greyscale, contrast is too low.
Source: Rulebook Design: Contrast and Readability – MINIFINITI
K03Accessibility
Dyslexia-friendly typography
Plain evenly-spaced sans serif (Arial, Verdana, Tahoma, Century Gothic, Trebuchet), 12-14pt, line-height >= 1.5, bold not italic for emphasis, avoid block capitals.
Synthesised from dyslexia style guidance and reflected in Curby's emphasis rules (avoid underline, avoid all-caps, use bold sparingly).
Avoid underlining and long italic passages — they make text appear to run together.
Source: Rulebook Design: Contrast and Readability – MINIFINITI
K04Accessibility
Accessibility is a whole-product property, not a rulebook property
Stonemaier's working model spans nine categories: Learning, Retention, Time, Visuals, Presence, Language, Purchase, Scope, Inclusion.
A useful audit frame: the rulebook contributes to Learning, Retention, Visuals and Language, but the game as a whole determines accessibility.
"You can make a really accessible game without checking every single box."
Source: How Do You Measure Accessibility? – Stonemaier Games
K05Accessibility
Reviewers who flag bad rulebooks are doing accessibility work
For visually impaired and non-native-speaking players, a rulebook without readable layout, clear hierarchy, diagrams and an index is not merely annoying — it is unplayable.
A powerful reader response in the 1 Player Guild thread pushes back on the idea that rulebook criticism is petty.
"If a rulebook doesn't have a readable layout, a clear hierarchy of information, adequate diagrams and an index, then it's useless to me."
Source: BGG: Do you get upset when reviewers complain about rulebooks/inserts?
L01Localization
Assume non-native readers
A large share of your audience reads your rules in a second language. Short sentences, plain vocabulary and no idiom are accessibility features.
BGG thread with non-native English speakers; Brandon the Game Dev recommends including non-native speakers among beta readers.
"Avoid slang, Americanisms / Britishisms, or cultural references."
Source: How to Write a Rulebook for Your Board Game – Entro Games
L02Localization
Translation is a technical-writing job, not a language job
Bad translations produce inconsistent terminology and broken rules. Use board-game-literate translators; back-translate and proofread.
The Andoria team spent over six months translating German rules to English and advise double-double-checking before handing to the graphic designer.
"Double double check everything before giving it to the designer for a graphic version."
Source: BGG: How to best do rulebook design?
L03Localization
A bad translation can sink a good game
Heroes of Normandie and multiple Kickstarter titles are cited as good games crippled by disjointed, poorly translated rules.
Recurring across worst-rulebook threads; also documented for a Spanish-to-English title rewritten by a fan over many months.
Fan rewrites are a symptom, not a solution — they signal a publisher failure.
Source: BGG: Worst rulebook ever!
L04Localization
Terminology consistency is what survives translation
Templated, consistently-worded rules translate mechanically. Synonym-rich prose multiplies translator judgement calls and errors.
Implied throughout the corpus; directly supported by Magic: The Gathering's templating discipline being cited as the model.
MTG developed strict templating precisely because most of its rules live on components.
Source: BGG: Rulebook Editing Style Guide (2020)
M01Failure Modes
Missing rules — the rule simply is not there
The most damaging defect class. Players cannot distinguish 'not stated' from 'we missed it', so they house-rule or stop playing.
Documented live in threads for Inferno, Raising Robots: Pets, Triplock and Imperium: Classics (a solo-bot rule omitted entirely).
Blind testing is the only reliable detector: 'situations occur which are not in the rulebook'.
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
M02Failure Modes
Undefined term used as if defined
Caper used the word 'set' repeatedly for scoring without ever defining it, producing years of forum argument and two-way misplay.
A near-perfect case study: two independent groups arrived at the same wrong-but-sensible reading, and the designer had to answer on BGG.
"Referring to 'set' a number of times without clarifying what a 'set' is has to be one of the biggest rules boners I've seen."
Source: BGG: Clarity in the Rulebook (Caper)
M03Failure Modes
Rules scattered across multiple documents
Mage Knight (rules in three places), A Feast for Odin and 7 Wonders (wrong booklet every time), Ulm (rules split over two booklets) are all cited.
The complaint is never about total length; it is about not knowing which artefact to pick up.
"Mage Knight is a mess, with rules in 3 different places, with no consistency."
Source: BGG: Worst/Best written rules
M04Failure Modes
Humour and flavour mixed into rules text
Galaxy Trucker and Dungeon Lords are simultaneously loved and cursed: entertaining to read once, painful to reference.
The most polarised topic in the corpus. Consensus compromise: humour and flavour are fine in visually separated sidebars.
"Don't mix humorous statements or theme elements with the rules. Keep them separated."
Source: BGG: Rules Writing 101 (with an example)
M05Failure Modes
Icon soup without a reference page
Heavy iconography with no single icon key forces constant hunting. Icons must be double-coded and collected in one place.
Cited for a Heroes of Might & Magic adaptation: 'A lot of icons spread around, but no reference page at the end of the rules.'
If you use icons, the icon key belongs on the back cover.
Source: BGG: Worst/Best written rules
M06Failure Modes
Rules that exist only in an example or a caption
Paul Grogan hunts for this specifically. Readers skip examples on re-read, so a rule hidden there is effectively invisible.
Named as one of his primary red flags when receiving a draft.
Parentheses, captions and examples clarify — they never introduce.
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
M07Failure Modes
Recursive and circular cross-references
'See section 3, which refers to section 7, which refers back to section 3.' Root is criticised for law-style back-references.
Herc du Preez calls this a personal pet peeve; a BGG user makes the same complaint about Root specifically.
"I don't want to read a 'law' that gives me a rule and then tells me to refer back to paragraph 2B. Just repeat the point if necessary."
Source: BGG: Tutorial differences between videogames and board games
M08Failure Modes
Errata churn and version drift
Publishing rulebook v1.0, then v1.5, then a designer-authored replacement ruleset destroys player trust even when the final text is good.
Coffee Traders is the flagship case: publisher rewrote the rulebook two years after release, and a physical copy cost an extra USD 7.
Maintain a public living-rules page and a dated changelog instead of silent revisions.
Source: 4 terrible board game rulebooks that really don’t rule – Going Analog
M09Failure Modes
Inconsistent counts between rulebook, components and player aids
Obsession shipped with component counts wrong in both rulebook and glossary, and a player aid stating 2 reputation where the board said 4.
A rare public, itemised errata post from a designer — an excellent QA checklist in negative form.
Cross-reference every number in the component list against the actual print run.
Source: BGG: OFFICIAL Obsession Rulebook and Glossary (errata thread)
M10Failure Modes
Rules on a 'thematic' surface that cannot be read
Rules printed on a faux treasure map, on dark art, or in a decorative display face are a recurring cause of games being shelved.
Multiple examples across worst-rulebook threads, including a game whose rules required angling the page against a light source.
"Legibility is more important than cutesy letters."
Source: BGG: Examples of well-written game rules?
M11Failure Modes
Over-explanation is also a failure
24 pages for a game that needs 12 is criticised as 'book bloat'; some readers find heavy example coverage actively harder to navigate.
A genuine minority-but-real position on BGG, and a reminder that page count should track complexity.
"I'd rather flip through twenty pages and glance the content of each page in an instant than plough through ten pages that are walls of text."
Source: BGG: What makes a good rulebook? (2021)
M12Failure Modes
Kickstarter/expansion sprawl merged into one book
Combining editions, variants, stretch goals and expansions haphazardly into one rulebook is a named modern anti-pattern.
Vinhos Deluxe with KS expansions cited as a specific example.
Base-game rulebooks should describe only the base game; expansions get supplements.
Source: Board Game Editing Style Guide (Michael "Curby" Lee)
N01Impact
A bad rulebook can sink a good game
First Martians and Batman: Gotham City Chronicles are named by a professional editor as games killed commercially by their rulebooks.
Paul Grogan, interviewed by Punchboard.
"There are a number of examples of how a poor rulebook killed a game."
Source: Playing By The Rules (incl. Paul Grogan interview) – Punchboard
N02Impact
Awards juries now reject games over rulebook quality
The Spiel des Jahres jury publicly stated it had to rule out otherwise-good games because their rulebooks did not meet expected quality.
Quoted via Joshua Yearsley in the 'Every Board Game Rulebook is Awful' essay.
"We jury members no longer wish to see ourselves in the role of beta-testers for rulebooks."
Source: BGG blog: Every Board Game Rulebook is Awful (Dean Ray Johnson)
N03Impact
Rulebook quality is a purchase factor
Buyers report avoiding games whose reviews mention rulebook problems; reviewers treat it as playability, not a cosmetic concern.
Strongly argued in the 1 Player Guild thread; Chris Wray attempted to quantify quality via BGG rules-question volume.
"I am less likely to buy a game if reviews complain about the rulebook."
Source: BGG: In-depth information about designing a good rulebook
N04Impact
Rulebook writing is a distinct profession
Rules editing is a specialised technical-writing discipline; designing a game and writing a game are different crafts.
Michael Lee has edited 100+ titles; Paul Grogan ~100 rulebooks including Vital Lacerda's heaviest designs.
"Writing instructions is not easy; that is why people make careers as technical writers."
Source: BGG: Tutorial differences between videogames and board games
N05Impact
Even good rulebooks generate questions — that is not proof of failure
Thousands of players will always find ambiguities a small design team missed. Distinguish genuine defects from statistical inevitability.
A balanced counterpoint in the text-comprehension thread, alongside evidence that many 'unclear rulebook' complaints are actually reading failures.
"Why would the small number of people who touch a game during design outperform thousands of players at finding bugs?"
Source: BGG: Rulebooks and text comprehension. A history of misunderstandings.
N06Impact
Fan-made summaries are a diagnostic signal
When the community produces rules summaries, indexes and rewrites (Universal Head / Esoteric Order of Gamers, Robinson Crusoe FAQ packs), the official document has failed at reference.
Robinson Crusoe's fan FAQ and rewrite ecosystem is the canonical example.
Check BGG's Files section for your genre's leaders — what fans build is what your book omitted.
Source: The Esoteric Order of Gamers – Robinson Crusoe rules summaries