Your House Rules Are Eating Your Game Alive

Every DM has been there. Someone at the table hated how grappling worked, so you patched it. Then encumbrance felt too punishing, so you softened it. Then a player asked if they could combine two actions under specific circumstances, and you said sure, why not — and wrote it down on a sticky note that has since migrated to a Google Doc, a Discord pin, and eventually a laminated sheet in a three-ring binder.

Congratulations. You have accidentally written a supplemental rulebook.

House rules are one of the great joys of tabletop RPGs. The ability to bend, fold, and reshape the official system is part of what makes this hobby feel personal and alive. But there's a version of that creative freedom that curdles — slowly, almost invisibly — into something that makes every session feel like navigating a bureaucratic maze. The homebrew trap isn't about bad intentions. It's about good intentions that never got edited.

How Rule Creep Actually Happens

Rule creep rarely announces itself. It doesn't show up one day demanding to be noticed. Instead, it accumulates like a junk drawer — each individual addition makes sense in isolation, but eventually you open that drawer and something falls out and rolls under the fridge.

The pattern usually goes like this: a rule in the official system creates friction. Maybe it's the death save mechanic, maybe it's the way concentration spells interact with certain conditions, maybe it's how the game handles stealth in social encounters. Someone at the table pushes back, and rather than sitting with the discomfort or doing a deeper dive into how the existing rule was meant to function, you patch it on the fly.

That patch works fine for a session or two. Then it bumps into another rule. So you patch the patch. Then a new player joins, and explaining the patches takes longer than explaining the original rules. Then someone asks what happens when Patch A and Patch C both apply at the same time, and suddenly you're adjudicating homebrew-on-homebrew combat while three players check their phones.

This is the moment most DMs realize something has gone sideways — but by then, the web is already tangled.

The Real Cost of a Bloated System

Slowing down gameplay is the obvious problem, but it's not the only one. A patchwork ruleset creates uneven player experiences. Veteran players who were there when each rule got added carry institutional knowledge that newer players simply don't have. That's not just a learning curve issue — it's a power dynamic issue. The table starts to develop a two-tiered citizenship: those who know the house lore and those who are still catching up.

There's also the contradiction problem. House rules written months apart, by a DM who was tired or improvising, don't always play nice together. You might have a rule that rewards cautious play in one subsystem and a different rule that penalizes the same behavior in another. Players notice these inconsistencies even if they can't articulate them, and it erodes trust in the table's fairness.

Finally — and this one stings — overly complicated homebrew can actually flatten creativity rather than expand it. When players spend cognitive energy tracking a dozen custom mechanics, they have less bandwidth to think about character choices, roleplay moments, and tactical creativity. The rules were supposed to support the story. Instead, they've become the story.

Running the Audit

Before you scrap anything, you need to actually map what you've got. Set aside an hour outside of session time and do a full inventory of every house rule currently in play at your table. Write them all down in one place — not in five different places.

For each rule, ask three questions:

1. What problem was this solving? If you can't remember, that's a red flag. Rules that outlive the problem they were fixing tend to create new problems without anyone noticing.

2. Is this rule still creating the outcome we wanted? Sometimes a house rule solved the original problem but introduced a different one. That's not a failure — that's just information. Use it.

3. Does this rule interact with anything else in a way that's hard to explain out loud? If you can't describe a rule in two sentences without caveats, it's probably too complicated. The two-sentence test is ruthless, but it's honest.

Once you've run each rule through those questions, sort them into three buckets: Keep, Revise, or Cut. Be honest with yourself. The goal isn't to throw out everything you've built — it's to identify what's earning its place at the table and what's just taking up space.

Simplifying Without Starting a Revolution

Here's the part that trips up a lot of DMs: some of those house rules have fans. A player lobbied hard for that custom crafting system. Another player's entire character concept is built around a homebrew ability you approved back in Session 2. You can't just announce a purge without some collateral damage to table morale.

The key is framing. Don't present the audit as "I've decided some of our rules were bad." Present it as "Our game has evolved, and I want to make sure the rules are still serving us." That's not spin — it's actually true. A rule that made sense at Session 5 might be genuinely obsolete by Session 30 because the game has changed shape.

For rules tied to specific characters or player investments, bring those players into the conversation privately before making any group announcements. Give them context, ask for their input, and where possible, find a simpler version of the rule that preserves what they care about. Most players don't love the complexity for its own sake — they love the effect the rule creates. Strip the complexity down to the effect, and you'll usually find a workable middle ground.

For rules that are just dead weight with no constituency, cut them cleanly and don't eulogize them. A brief "we're streamlining a few things" at the start of a session is all the ceremony that's required.

Staying Out of the Trap Going Forward

The best way to manage rule creep is to treat every proposed house rule like a probationary hire. It doesn't get permanent status until it's proven itself over multiple sessions, in multiple contexts, without creating new problems. Try it for three sessions. If it's still earning its place, codify it. If it's caused more confusion than it solved, let it go — and let it go without guilt.

It also helps to designate one canonical document for house rules. Not a Discord thread, not a shared Google Doc with seventeen comment threads, not a collection of sticky notes on your DM screen. One document. When a rule gets added, it goes in the document. When a rule gets cut, it comes out of the document. Simplicity in the meta-structure makes the rules themselves easier to trust.

The official system you're running — whatever it is — was playtested and revised by teams of people over years. That doesn't make it perfect. But it does mean the rules inside it were designed to work together. Every time you add a layer on top, you're taking on a small design debt. The good news is that debts can be paid down. The even better news is that a leaner, cleaner ruleset almost always makes for a better game — and your players will feel the difference, even if they can't name it.