D&D Homebrew Subclasses Creation Part 1: Crafting Strong Themes
Updated: Aug 20
Want to create a D&D homebrew subclass?
Do not start with abilities. Start with the theme.
When I create one, I usually begin with a simple idea:
What would an Arsonist Rogue look like?
What about a Wizard who hates magic?
No damage dice. No level features. No balance yet.
Just the idea.
My 3-Step Process
Find the theme
Choose the class
Build and balance the abilities
This article is Step 1.
Start With the Character Fantasy
For me, a subclass usually starts with a question:
What would this character actually feel like to play?
A lot of my ideas come from anime, TV, Westerns, villains, criminals, and other character concepts.
The goal is not to build abilities yet.
The goal is to find a fantasy strong enough to build around.
Example: My Outlaw Rogue
I love Westerns, so I eventually thought:
Why not make a cowboy Rogue?
I broke that idea down into two things:
Guns
Lasso
That was enough.
Once I knew those were the core ideas, building the subclass became much easier.
That leads to one of my biggest rules.
Keep It to 1–2 Core Ideas
If your subclass is trying to do too much, it becomes messy fast.
Fire-based subclasses are a good example.
Fire can mean:
Burns
Explosions
Beams
Overheating
Fire magic
Damage over time
Suddenly one theme has six different mechanics.
Instead, narrow it down.
For my Outlaw Rogue, it was:
Guns + Lasso
For my Blast Fist Monk, it was:
Explosive punches
Simple themes are easier to build and easier for players to understand.
A Cool Idea That Did Not Work
I once tried to make a Teleporter Rogue.
The idea sounded awesome:
A Rogue teleporting across the battlefield, appearing behind enemies, attacking, then disappearing.
The problem?
After "teleporting," I did not know what the subclass was actually supposed to do next.
I could keep creating more teleport abilities, but eventually I was just repeating the same idea.
That taught me something important:
A cool character idea is not always a good subclass idea.
The concept needs enough room to grow.
Fun First. Balance Later.
I do not start by worrying about perfect balance.
First, I want the subclass to make someone say:
"I want to play that."
Then I scale it.
Later, when I start creating abilities, I compare them to official subclasses and look at things like:
Damage
Charges and uses
Short or long rest recovery
Non-combat abilities
How the subclass interacts with the base class
You can fix numbers later.
It is much harder to fix a subclass that is not fun.
Quick Theme Test
Before moving on, ask yourself:
Can I explain the subclass in one sentence?
If not, simplify it.
Can I reduce it to one or two core ideas?
That usually means the theme is focused.
Can those ideas support several features?
You do not need the abilities yet. You just need somewhere to go.
Am I trying to make it do too much?
If you have five different mechanics already, cut some.
Does it sound fun?
If someone hears the idea and immediately wants to play it, that is a good sign.
Keep It Simple
The biggest mistake I see in homebrew subclass design is making things too complicated.
Too many mechanics.
Too many limits.
Too much text.
Start with the fantasy.
Keep it focused.
Then build from there.
What Comes Next?
Once you have the theme, the next question is:
What D&D class should actually use it?
That is Step 2.
Comments