From what's been said historically, the most likely barrier to them implementing this is the amount of permissions to edit the sites underlying behavior required to make a class vs literally anything else.
Classes are, for lack of a better word, definitional—they define what other things can do and there are almost no restrictions. Almost every class has at least 1 unique resource; bardic inspiration, rage, wild shape, action surge, focus points, sorcery points, etc. Many classes have a uniquely defined feature such as eldritch invocations, metamagic, replicating magic items. And then there's fact that virtually no two classes have the same progression in terms subclasses and feats.
Basically a class is a blank canvas and to implement a blank canvas in a tool such as D&D Beyond you need a high level of access and permissions to build those things so they can be used in the backend. Compare that to a subclass, which is very much "defined" rather than does the defining. It has features at specific levels, it grants features in addition to base class features in an additive manner. And even then, DDB doesn't/can't support all the wild and wacky stuff people want to do with subclasses (such as granting spellslots for non-caster classes outside of fighter and rogue).
So yeah, I suspect that to have an even vaguely functional class creator tool that works within DDB requires too much access to be safe or stable.
we got HB subclasses why not HB classes?
best wibesite for dnd on the internet
and as a heads up, if u blame the code im going to say skill issue
From what's been said historically, the most likely barrier to them implementing this is the amount of permissions to edit the sites underlying behavior required to make a class vs literally anything else.
Classes are, for lack of a better word, definitional—they define what other things can do and there are almost no restrictions. Almost every class has at least 1 unique resource; bardic inspiration, rage, wild shape, action surge, focus points, sorcery points, etc. Many classes have a uniquely defined feature such as eldritch invocations, metamagic, replicating magic items. And then there's fact that virtually no two classes have the same progression in terms subclasses and feats.
Basically a class is a blank canvas and to implement a blank canvas in a tool such as D&D Beyond you need a high level of access and permissions to build those things so they can be used in the backend. Compare that to a subclass, which is very much "defined" rather than does the defining. It has features at specific levels, it grants features in addition to base class features in an additive manner. And even then, DDB doesn't/can't support all the wild and wacky stuff people want to do with subclasses (such as granting spellslots for non-caster classes outside of fighter and rogue).
So yeah, I suspect that to have an even vaguely functional class creator tool that works within DDB requires too much access to be safe or stable.
Find my D&D Beyond articles here