By Mara Voss — Mara has run tables for every edition since 3.5 and writes about rules design and homebrew balance.

Every long-running tabletop group eventually houserules something — a clunky spell, an underwhelming class feature, a rule that just doesn’t fit the table’s tone. Homebrewing is one of the best parts of running a game: it’s how a rented rulebook becomes your rulebook. But safe homebrewing is a skill, and plenty of well-intentioned changes quietly break a game’s balance months before anyone notices why combat feels off or why one player is steamrolling every encounter. Here’s how to modify your system without wrecking it.

Start with the problem, not the fix

The biggest source of bad homebrew is skipping straight to a solution. Before changing a rule, write down, in one sentence, what’s actually not working: \”grappling never comes up because it’s not worth the action economy,\” not \”grappling should deal damage.\” A precise problem statement keeps your fix narrow and makes it much easier to predict side effects. Vague dissatisfaction, like spellcasters feeling too strong overall, tends to produce sweeping changes that fix one thing and break three others.

Playtest before you trust it

Any rule change that touches combat math, resource economy, or character power should be tested at the table before it’s treated as permanent — ideally across more than one session, since a single lucky or unlucky roll can make a balanced rule look broken or a broken rule look fine. Tell your players a rule is on trial so nobody feels blindsided if you walk it back. Keep quick notes on what happened each time it came up; memory alone is unreliable once three sessions have passed.

Common balance pitfalls

• Stacking bonuses. A small buff in isolation is fine; the same buff combined with three other small buffs a system already allows can multiply out of control. Always check how a change interacts with existing feats, spells, or class features, not just the base rules.
• Removing costs without removing the benefit. Rules exist in pairs — a powerful ability usually has a resource cost, a cooldown, or a risk attached. Homebrew that quietly drops the cost while keeping the benefit is the single most common way a table ends up with an unkillable character.
• Changing math without changing the curve. Bumping a damage die or a save DC by what feels like a little can shift outcomes more than expected, especially at low levels where numbers are small and swingy.
• One-player rules. A change built to fix one character’s frustration often needs to apply system-wide, or it creates resentment at the table. Ask whether the fix should be universal before rolling it out for just one person.

When to homebrew vs. use an existing subsystem

Not every itch needs a custom rule. Many major systems already publish optional or variant subsystems — alternate crafting rules, chase mechanics, downtime activities — that have been tested far more than anything a home table can playtest in a few sessions. Before writing something from scratch, check whether the official rules reference, an official supplement, or a well-regarded third-party sourcebook already solves the problem; adapting an existing subsystem is usually faster and safer than inventing one. Save fully custom homebrew for things that are genuinely specific to your campaign or setting, where no published rule could reasonably exist.

Document changes so they stick

Nothing sinks a homebrew rule faster than nobody remembering the exact wording three sessions later. Keep a single running document — a shared doc, a pinned message, or notes attached to your campaign — listing every active house rule, the date it was adopted, and why. This also makes it much easier to roll a rule back cleanly if it doesn’t work out, since you can point to the original problem statement instead of relitigating the whole thing at the table. It’s worth keeping this list somewhere players can reference it too, whichever character sheet tool or app your group uses to track the rest of the campaign, so nobody is caught off guard mid-session.

The bottom line

Good homebrew is targeted, tested, and written down. Bad homebrew is a vibes-based fix applied under pressure mid-session and never revisited. The difference isn’t creativity — plenty of great house rules are simple — it’s discipline about naming the problem, testing the fix, and being willing to undo it if the numbers don’t hold up. For more on the underlying concept, game balance is a well-studied idea across all of tabletop and video game design, not just TTRPGs.

Photo by RDNE Stock project on Pexels