Rules Are a Draft, Not a Constitution: Making Peace With Your Favorite Game's Messiest Corners
Rules Are a Draft, Not a Constitution: Making Peace With Your Favorite Game's Messiest Corner
Every TTRPG player has a moment of reckoning with a rule that just doesn't add up. You read the passage twice, check the index, maybe post in a forum at 11pm, and eventually conclude either that the designers made a mistake or that you're fundamentally misunderstanding the English language. Sometimes it's the latter. But sometimes — more often than most people assume — you've stumbled onto something that was left fuzzy on purpose.
Game design is a weird discipline. It's part mathematics, part creative writing, part social engineering, and the final product has to function in the hands of thousands of different groups with wildly different expectations, play styles, and tolerance for complexity. The idea that a finished rulebook should read like a legal contract is a fantasy. The designers know this. The good ones plan for it.
The Myth of the Complete Ruleset
There's a persistent assumption in gaming communities — especially online — that a well-designed game should have a clear, unambiguous answer for every situation. That any gap or contradiction represents a failure of craft. It's a reasonable assumption on its face, and it's mostly wrong.
Consider D&D 5e's famously loose action economy. The rules around what constitutes a "free action" versus a "bonus action" versus an "interaction" have generated more forum arguments than almost any other corner of the game. But Mike Mearls and Jeremy Crawford have both said explicitly that this looseness was intentional. The goal was to keep the game moving at the table, to trust DMs to make calls, and to avoid the kind of rules-lawyer paralysis that made some earlier editions feel more like litigation than adventure.
The ambiguity isn't a bug left in by an overworked editing team. It's a design value. The game is deliberately asking DMs to be co-authors of the ruleset, not just executors of it.
Pathfinder 2e and the Other Approach
Of course, not every system makes the same bet. Pathfinder 2e went in a fundamentally different direction — dense, comprehensive, with a three-action economy that tries to account for most edge cases explicitly. The design philosophy there is that clarity reduces table conflict and makes the game more equitable, since everyone is working from the same precise framework.
And it does do those things. PF2e tables tend to have fewer "wait, can I actually do that?" arguments. But even Paizo's team has acknowledged that no ruleset can be fully exhaustive. Their system still has gaps — they're just smaller and less frequent. The GM is still expected to adjudicate novel situations, just within a tighter structure.
The interesting thing is that neither approach is objectively superior. They're serving different audiences with different priorities. 5e's looseness is a feature for tables that value narrative flow and DM creativity. PF2e's density is a feature for tables that value consistency and tactical depth. Calling one "better designed" usually says more about your personal play style than about design quality.
Indie Systems and Intentional Incompleteness
Where this philosophy gets really explicit is in the indie TTRPG space. Games like Ironsworn, Blades in the Dark, and Apocalypse World don't just tolerate ambiguity — they build it in as a core mechanic. Blades in the Dark famously tells its GM (the "Blademaster") to "be a fan of the players" and offers principles rather than exhaustive procedures. The rules are a vocabulary, not a script.
Sean Nittner, one of the contributors to Blades in the Dark, has talked about how deliberate gaps in procedural games force players to engage with the fiction rather than retreating to the rulebook. When the rules don't tell you exactly what to do, you have to ask what makes sense in the story. That's a feature. It keeps the game world feeling like a place rather than a spreadsheet.
This is a fundamentally different relationship with rules than most players raised on D&D are used to. But it's worth sitting with, because it reframes what a rulebook actually is. It's not a complete simulation. It's a starting point for a conversation.
When Ambiguity Actually Fails
None of this is to say that every confusing rule is secretly brilliant. Some ambiguities genuinely are oversights, and some of them cause real problems at the table.
The clearest sign that a gap is a genuine design failure rather than an intentional one is when it creates equity issues — when the ambiguity consistently benefits one type of player or one type of character over others in ways that undermine the game's internal logic. A rule that's fuzzy about flavor is usually fine. A rule that's fuzzy about who gets to do something powerful is a problem.
Similarly, when an ambiguity requires constant DM adjudication in high-stakes moments — combat, social encounters with major consequences — it creates inconsistency that players notice and resent. If your DM rules one way in session 4 and a different way in session 12 because the rule genuinely doesn't specify, that's a design gap that's doing harm.
The test isn't "is this rule clear?" It's "does the ambiguity create better play, or does it create friction that serves nobody?"
House-Ruling Without the Guilt
One of the stranger cultural artifacts in TTRPG communities is the guilt some players feel about house-ruling. There's a sense that deviating from the printed text is somehow cheating, or at least disrespectful to the designers' intentions.
This is worth pushing back on firmly. Most game designers — especially in the TTRPG space — explicitly want their rules to be modified. The Dungeon Master's Guide for 5e literally includes a chapter on variant rules and encourages DMs to change things that don't work for their table. Pathfinder 2e's GM guide does the same. The designers know they're not writing for a single canonical experience.
When you house-rule a confusing or broken rule, you're not violating the spirit of the game. In most cases, you're doing exactly what the designers hoped someone would do — taking ownership of the system and shaping it into something that serves your table.
The only real caveat is transparency. House rules work best when everyone at the table knows about them before they matter. Springing a modified rule on a player mid-encounter feels like the rug being pulled. Establishing it at Session Zero feels like collaborative design.
Reading the Rulebook Differently
The next time you hit a rule that doesn't quite parse, try approaching it as a question the designer left open rather than a problem they forgot to solve. Ask what the rule is trying to do — what behavior it's incentivizing, what kind of play it's protecting — and then ask whether the ambiguity serves that goal or undermines it.
Sometimes you'll conclude it's a genuine oversight and house-rule accordingly. Sometimes you'll realize the fuzziness is doing quiet, important work. Either way, you'll be engaging with game design as the collaborative, living thing it actually is — not as a fixed text handed down from on high.
The parchment is a starting point. The polyhedral does the rest.
