Four evenings that changed what a rule was for

The OSR argument

Returning to the 1974 assumptions is itself a design position about where authority should sit.

A photocopied booklet and staples on a desk — A stapled booklet: the form the argument took as much as the argument itself.

Recovering old rules is a claim about where power belongs at the table.

What the letters actually mean

OSR — Old School Renaissance, or Revival, depending on who you ask — is not a genre preference. It is a design position, and the thing it positions itself against is legible once you see it: the steady migration of authority away from the referee and toward codified, player-accessible procedure. The movement, which crystallised around 2008 with publications like OSRIC and Labyrinth Lord, went back to the text of Dungeons & Dragons as Gary Gygax and Dave Arneson produced it in Lake Geneva, Wisconsin in 1974 and asked what had been quietly discarded in the decades since.

The answer was significant. The original game said almost nothing about what a character could attempt. It described combat procedures, dungeon movement rates, and reaction rolls — the dice that settle a monster's disposition before a fight begins — but it left vast tracts of the situation to the referee's judgement. A player who wanted to climb a wall, negotiate an armistice, or identify a poison had no skill list to consult. The referee listened, thought, and decided. Authority was concentrated, local, and fast.

The design argument underneath the nostalgia

Later editions of D&D, and especially the shift that D&D 3rd edition formalised in 2000, moved in a different direction. Skill systems gave players a printed number to invoke. Feats gave them explicit options to declare. The game's resolution surface expanded enormously, which meant the referee's adjudicative space contracted by roughly the same amount. This is not a value judgement — it is a structural description. Player-facing rules shift something real: they relocate the burden of knowing the system, and with it a slice of narrative power.

OSR design treats that migration as a loss rather than a gain. The exploration turn — a strict unit of dungeon time that makes torches burn and wandering-monster dice tick — is not recovered because it is charming; it is recovered because it exerts pressure on the player through resource attrition rather than through a character-sheet number. The referee does not need to invent tension. The procedure generates it. This is the structural claim: old mechanics do specific work that skill systems do not, and that work concerns who feels accountable for the outcome.

The dice pool, the roll-under stat test, the ascending versus descending armour class dispute — these are surface features. The deeper argument is about authority: who can say whether an action succeeds, and on what grounds. In a system with comprehensive skill coverage, a player can reasonably expect the rules to have an answer for most situations. In a system deliberately built with gaps, the referee's answer is the system, which changes the social contract at the table in a way that no errata can patch.

A hand-drawn level map on graph paper with numbered rooms — Rooms numbered before play: the dungeon constrains the referee as much as the players.

Why "renaissance" rather than "retrieval"

Pure retrieval would just be reprinting the 1974 booklets. What OSR designers actually did was more argumentative than that. They read the sparse original text as a set of design priorities — rulings over rules, attrition over combat resolution, the dungeon as a machine that runs on player choices — and used those priorities to build new games. Matt Finch's A Quick Primer for Old School Gaming, Ben Milton's Knave, Chris McDowall's Into the Odd: these are not facsimiles. They are games that reverse-engineered a philosophy and rebuilt it with contemporary craft.

The Braunstein lineage matters here because it shows that the original referee role was never about improvisation as a personal style — it was about adjudicating situations that the rules had not anticipated, which is a structural feature inherited from wargame umpiring. OSR design tries to preserve that inheritance deliberately, rather than letting later design layers erode it without noticing. When a contemporary OSR text says rulings, not rules, it is not romanticising the past. It is defending a theory of where legitimate authority over fictional events should be generated — in the room, from the situation, by a person — rather than pre-distributed across a character sheet before anyone sits down.

A stack of well-used rulebooks with broken spines — Going back to the 1974 assumptions is a position about authority, not nostalgia.