Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Content

When you have a design goal, ideally your efforts should put you closer to that goal than what you already have. That didn't happen this time.

Files

Previews only

maxresdefault.jpg

If you like what I do and would consider supporting this channel through Patreon: https://www.patreon.com/Treantmonkstemple Timestamps: 0:00 Intro 4:14 Design Goal - discourage 1 level dips 5:47 Why dip cleric? 11:29 One D&D Cleric dip 15:37 Why they failed hard 18:16 Proficiency bonus and class features 19:35 Not scaling first level features 21:42 Scaling with ability scores 22:11 The best solution 24:33 Wrap up Join my discord: https://discord.gg/6z97aaq Follow me on Twitter: https://twitter.com/ChrisHonkala

Comments

Falcon_Neil

It's a mistake for sure. But something to do constructive feedback on, and be proud of identifying/communicating. We shouldn't mock the developers for inconsistancies in a playtest.

Bolduin

I thought a lot about this... And i think i got to a great solution: At first Level you get "Feature" with 2 uses per long rest and 2 dice per use. And it doesn't scale on its own. At 5th Level, you get "Improved Feature", wich says: now you can use "Feature" a number of times equal to your proficiency bonus per long rest and the number of dice per use equals your proficiency bonus as well. Now a straight-classed Character doesn't see any difference. But you'd need 5-Levels in a class to use the Feature to it's full potential. And you can give this to every class!