D&D (2024) What Exactly Are You Meant To Do, Here?

[Parmandur]

This is breaking backwards-compatibility at the class/subclass level.

Why do you say that, it works as written now, and there is plenty of time to smooth out a conversion process.

 

[Horwath]

This is breaking backwards-compatibility at the class/subclass level.

sometime you must break something first in order to fix it.

 

[doctorbadwolf]

Yeah, don't overthink it, it's pretty straightforward currently: take a 2014 Subclass, and the specific progression of the original Subclass overrides the general rule of the OneD&D test Class. Currently inelegant because of dead Levels, doubled up Levels, and a straight up missing level for Bard...but should work, particularly for now.

Yeah the more I think about it the more I think that it will end up being a bonus feat.

When they've nailed down the Core Classes, and gotten those more settled, I expect to see more explicit conversion notes ("move this Level here, take a Feat there..."), UT this will function for now...particularly starting at Level 1, most of the issues won't crop up for about a year of regular play.

Nah, people are going to start at all kinds of levels to test this stuff, so the issues will crop up this week, next week, and continuing from there.

 

[UngeheuerLich]

I have to wonder if player feedback has flipped over the years to a desire for normalized design, or if the team is just tired of not having any normalized guideposts and is making the game better fit what they personally want.

I think part of the decision to not have normalized design was that 4e was still to close. They deviated from normalized design a bit with essentials, but they really did not want to have obvious 4e design in 5e.

 

[doctorbadwolf]

I think part of the decision to not have normalized design was that 4e was still to close. They deviated from normalized design a bit with essentials, but they really did not want to have obvious 4e design in 5e.

I disagree.

 

[Azzy]

Why do you say that, it works as written now, and there is plenty of time to smooth out a conversion process.

It's a kludge (at best) as written now. The old subclasses are going to need rewrites to fit the new subclass structure.

 

[UngeheuerLich]

I disagree.

Ok. Maybe it was not the only reason, but 4e design was obfuscated in 2014 D&D and I think they can risk a bit more now.

 

[Azzy]

sometime you must break something first in order to fix it.

I can't deny, I'm just saying that some existing subclasses are going to require more effort to work than the kludge we've got.

 

[Parmandur]

Yeah the more I think about it the more I think that it will end up being a bonus feat.

Nah, people are going to start at all kinds of levels to test this stuff, so the issues will crop up this week, next week, and continuing from there.

It may come up, but it shouldn't be a major balance concern in play. Should still be cleaned up before primitive, but it's early days yet.

 

[Parmandur]

It's a kludge (at best) as written now. The old subclasses are going to need rewrites to fit the new subclass structure.

Not really, as written these will work, and for the final version they just need to provide guidance on where you switch Levels around. The old Subclasses look to play well with the new Classes, however, and by design.