D&D (2024) Collage of Dance Reveal

[CapnZapp]

"should never be allowed" - you're clearly not familiar with American capitalism...

 

[fluffybunbunkittens]

If Monk is any indicator, WotC wants to discourage multiclassing now.

I really wouldn't say that, when MonkX/Rogue1 is vastly superior to the pure Monk...

And they buffed Warlock dips, surely the most common dip, by giving them more invocations right away.

 

[Staffan]

Wouldn't that layer be feats?

Could be, but you're getting so few of those, and your early ones are usually best spent on ASIs.

 

[Not a Decepticon]

"should never be allowed" - you're clearly not familiar with American capitalism...

I know enough to understand it's horrible and this is just one of many, many examples.

I really wouldn't say that, when MonkX/Rogue1 is vastly superior to the pure Monk...

I am tlaking about 2024 version, where 1 level dip locks you out of 24 DEX and WIS

 

[Remathilis]

I know enough to understand it's horrible and this is just one of many, many examples.

I am tlaking about 2024 version, where 1 level dip locks you out of 24 DEX and WIS

It's almost like multi classing should have trade offs and not just stacking synergies.

 

[Horwath]

I feel like making subclasses that would work with any class would also work against class fantasy. It might still create a fun game, but it wouldn't be a game with strong niche protection, which has always been one of D&D's hallmarks and, arguably, strengths.

most subclass features now are just fixed feat slots.
95% of subclass features can be turned into feats/half-feat with some prerquirements and level gating.

 

[Not a Decepticon]

It's almost like multi classing should have trade offs and not just stacking synergies.

the trade-off is usually what you won't be getting from the original class, both in short and long term.

 

[Horwath]

If Monk is any indicator, WotC wants to discourage multiclassing now.

that is true.

personally for multiclassing, a class feature number of usages(if it's multiple) should scale with character level or proficiency bonus, while power or effect should scale with class level.

I.E. barbarian rage:
make usage a number of times equal to prof bonus, but bonus damage and additional effects based on barbarian level.

oh, and get away form usages per ability bonus, we do not need to pressure people to min max stats outside primary attack/DC ability.

 

[Horwath]

It's almost like multi classing should have trade offs and not just stacking synergies.

this, you trade vertical for horizontal power generation.

 

[jayoungr]

most subclass features now are just fixed feat slots.
95% of subclass features can be turned into feats/half-feat with some prerquirements and level gating.

Fixed feat slots that reinforce the class fantasy and refine it into a more specific archetype, hence, subclass. Portable "subclasses" that are designed to work with multiple different classes won't reinforce and refine the base class fantasy--quite the opposite. They'll tend to de-emphasize the class, making it effectively a subflavor (the difference between a beastmaster fighter and a beastmaster ranger would be their class abilities).

Now, portable subclasses are not a terrible idea in and of themselves. There are probably games already that use them, calling them templates or some such thing. But I feel that they would pull D&D toward being a different sort of game and rob it of one of its strengths.