D&D Homebrew Subclasses Creation Part 2: Choosing the Right Class

Apr 24
4 min read

Updated: 5 days ago

A square, high-detail fantasy image showing multiple Dungeons & Dragons character classes—including fighter, barbarian, druid, monk, wizard, rogue, paladin, sorcerer, cleric, and artificer—arranged in a circle. Each character is depicted using their signature abilities, with glowing magical energy linking them to a central D20 symbol. — A vibrant fantasy illustration of Dungeons & Dragons classes united, showcasing their unique roles and abilities as magical energy connects them around a central arcane symbol.

You have a theme for your D&D homebrew subclass.

Now you need to decide:

Which D&D class actually fits it?

For me, choosing the right class comes down to one question:

How does the theme work with the base class's existing mechanics?

A Fighter has Action Surge.

A Rogue has Sneak Attack.

A Barbarian has Rage.

Your subclass should build on those features—not make the player choose between their class and their subclass.

My 3-Step Homebrew Subclass Process

Find the subclass theme
Choose the right D&D class ← You are here
Create and balance the subclass features

If you do not have your theme yet, start with Step 1: How to Create a D&D Homebrew Subclass Theme.

How Do You Choose the Right Class for a Homebrew Subclass?

I start with the base class.

I ask:

What does this class already do, and how can my theme make that more interesting?

For example:

Fighter: Action Surge and weapon combat
Rogue: Sneak Attack, skills, and mobility
Barbarian: Rage and durability
Bard: Bardic Inspiration and support
Sorcerer: Magical resources and spell manipulation

You do not need to reinvent the class.

You need to find where your theme fits inside it.

A table showing Dungeons & Dragons classes (Artificer, Barbarian, Bard, Cleric, Druid, Fighter, Monk, Paladin, Ranger, Rogue, Sorcerer, Warlock, Wizard) rated from 1 to 3 in categories: Environmental, Exploration, Combat (Grunts), Combat (Tank), Combat (Glass Cannon), and Social, representing each class’s strengths and overall role in gameplay. — Class role evaluation chart for Dungeons & Dragons, comparing each class across environmental challenges, exploration, combat roles, and social interaction using a 1–3 effectiveness scale.

Example: My Hound Master Fighter

One of my favorite examples is my Hound Master Fighter.

When the Fighter uses Action Surge, spectral hounds attack creatures around them.

The important part?

I did not replace Action Surge. I made it more interesting.

The Fighter can still use that extra action to:

Attack
Give someone a potion
Use the Help action
Move the fight in another direction

The spectral hounds still appear.

That means the subclass works with the Fighter's core mechanics instead of competing with them.

Your Subclass Should Not Fight the Base Class

This is one of the biggest mistakes I look for.

Imagine giving a Rogue a subclass ability that forces them to give up Sneak Attack every time they use it.

Now the player has to decide:

Do I play my Rogue or do I play my subclass?

I generally do not want that.

A subclass should make someone feel like a different type of Rogue, Fighter, Monk, or Wizard.

It should not make them stop using the features that define that class.

One Theme Can Fit Multiple D&D Classes

Some themes can work with several classes.

My Arcane Marksman is a good example.

It could work as:

Ranger: magical ranged attacks and exploration
Fighter: charged weapon abilities and combat techniques
Warlock: magical attacks powered by supernatural abilities

None of those are necessarily wrong.

The real question is:

How do I want this character to play?

The theme might stay the same.

The base class changes the gameplay.

Don't Replace Another D&D Class

A subclass can borrow ideas from another class.

But there is a limit.

For example:

If I make a Rogue that can freely transform into animals, the Druid may start feeling a lot less special.

That is where I think a subclass has gone too far.

Borrow ideas. Do not steal another class's identity.

A Rogue can have Ranger-like abilities.

A Fighter can gain some magic.

A Monk can support allies.

But they should still feel like their original class.

Look at Official D&D Subclasses

Before I settle on a class, I look at official subclasses.

I want to see:

How they use base-class mechanics
How much they change the class
What resources they use
Whether a similar idea already exists
Whether my theme fits naturally

Then I ask:

Does my idea work with this class's architecture?

If yes, I probably have the right class.

Quick Test: Did You Choose the Right Class?

Before moving to Step 3, ask:

Does my theme use the base class mechanics?

If not, another class may fit better.

Does the subclass enhance the class?

It should build on features like Action Surge, Sneak Attack, Rage, or other core mechanics.

Does the player still feel like the base class?

A Rogue should still feel like a Rogue.

A Fighter should still feel like a Fighter.

Am I replacing another class?

Borrowing is fine.

Replacing is not.

Could this theme work better as another class?

Think about how you want the character to play, not just what sounds right.

The Theme Gives You the Idea. The Class Gives You the Structure.

That is how I think about it.

Your theme tells you what the character is.

Your base class tells you how the character plays.

When those two things fit together, creating the actual subclass abilities becomes much easier.

What's Next?

Now you have:

Theme + Base Class

Next comes Step 3:

Creating and balancing the actual subclass features.

Step 1 — How to Create a D&D Homebrew Subclass Theme

Step 3 — How to Create and Balance D&D Homebrew Subclass Features