Your Homebrew Isn't Done Until It Survives Contact With Your Table

Writing the cool ability is maybe 30% of the job. Here's the actual workflow for playtesting, formatting, and versioning homebrew so it's ready to hand off — not just ready to admire in a doc.

Every table has that one homebrew subclass sitting in a doc since March. You built it, you love it, and you genuinely have no idea if it's going to break your campaign in half the first time someone rolls well with it. That's not a homebrew problem. That's a "skipped the boring part" problem.

Here's the thing nobody tells new homebrewers: writing the cool ability is maybe 30% of the job. The rest is making sure it works at the table, and that you can hand it to someone without three follow-up texts explaining what you actually meant. We built ContentCraft because we got tired of watching great ideas die in a Discord thread nobody could find again. Here's the workflow we'd recommend, whether or not you're using our tools for it.

Playtest it like you don't trust it

Before a homebrew item, monster, or subclass leaves your table, run it through a short one-shot or a single combat encounter and treat it as an alpha build — tell your players up front it's getting tweaked. Don't rely on your own math. Pull up an official option at the same level or challenge rating and compare damage output, action economy, and resource cost side by side. If your homebrew fighter subclass is outdamaging the Battle Master for free, that's not balance, that's a favor to one player at the expense of everyone else's spotlight.

A structured way to do it: pick a design goal (what should this feel like to play), set a power budget against an existing baseline, build one or two scenarios that would actually stress it, and run those before you touch a "final" draft.

Format it so someone else could run it cold

If your homebrew only makes sense because you wrote it and remember your own intent, it's not finished — it's notes. Stat blocks need to be scannable at a glance, not paragraphs someone has to parse mid-combat. Break mechanics into small, labeled chunks instead of one wall of flavor text with the actual rule buried in the middle. That's the real difference between content you use and content you just posted.

Version it like you expect to be wrong

You will nerf this thing. Everyone does. The fix isn't perfection on draft one — it's making draft two not confusing. Keep a simple changelog, even something as plain as "v1.2: reduced bonus action heal to 1/rest, clarified it doesn't stack with Bless," so your players aren't relearning a class every two sessions without knowing why. This is the single most skipped step in homebrew, and it's the reason most homebrew dies after one campaign instead of getting reused.

None of this requires anything fancy. A doc, a changelog, and one honest playtest will get you further than another week of polishing flavor text nobody's tested. If you're using ContentCraft to track those versions and hand finished content to your table without the copy-paste archaeology, great — that's what it's for. If you're doing it in a shared folder with a naming convention only you understand, also fine. Just, for the love of your players, write the changelog.

What's the worst homebrew balance mistake you've shipped to your table? We want the war stories.

Your Homebrew Isn't Done Until It Survives Contact With Your Table