I've been playing around in the homebrew stuff and it looks like if there was just a blank class that allowed me to add features for every level, I could put in all of the custom classes I've been wanting to play around with. I know it takes a lot to code for a new class, but if it's blank, would it be that bad? I could make a "template" file I can copy over to make the subclasses for it and just go from there. You'd have to be able to select the hit dice, but the rest can be created out of options, right?
Unfortunately, the issue is the interaction between the homebrew and the D&D Beyond character sheet. That interaction is complex, and makes it difficult for even subclasses to be customized meaningfully. The only way this could be implemented simply is if the custom class is literally just a markdown document that has no further functionality.
The homebrew infrastructure of D&D Beyond has been a jury-rigged afterthought since the beginning. I am certain that a better system could be implemented, but I am almost as certain that it will not.
I think that would be fine, as long as you can still set a rollable block and the customize options for rolls are available. Just a blank sheet you can modify with snippet codes the same way you can do the other stuff might be enough for most of us to get by. Not being easy is ok, not being possible is a problem.
Technically, you can overwrite class features in the subclass creator, so you could technically create a subclass of Fighter (or whatever), overwrite all their class features, make them invisible, then write in your own class features in their place, then take that as a "subclass." It... I think it would work...?
That is a lot of work, though, and I honestly don't know what it would do to the character sheet. Or if there's a class feature limit...
I haven't found a way to overwrite an existing class feature. I only see the replacement option for features I've made in the subclass. Am I looking in the wrong place? If I could make a "blank" template off of Fighter and could blank it all out myself, then rewrite it all from scratch, I would totally do that.
I dont remember the exact method, but if you create a class feature with the same name as another class feature, it shoul overwrite the old one. I don't know what happens if you then try to hide the class feature, though...
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've been playing around in the homebrew stuff and it looks like if there was just a blank class that allowed me to add features for every level, I could put in all of the custom classes I've been wanting to play around with. I know it takes a lot to code for a new class, but if it's blank, would it be that bad? I could make a "template" file I can copy over to make the subclasses for it and just go from there. You'd have to be able to select the hit dice, but the rest can be created out of options, right?
Unfortunately, the issue is the interaction between the homebrew and the D&D Beyond character sheet. That interaction is complex, and makes it difficult for even subclasses to be customized meaningfully. The only way this could be implemented simply is if the custom class is literally just a markdown document that has no further functionality.
The homebrew infrastructure of D&D Beyond has been a jury-rigged afterthought since the beginning. I am certain that a better system could be implemented, but I am almost as certain that it will not.
I think that would be fine, as long as you can still set a rollable block and the customize options for rolls are available. Just a blank sheet you can modify with snippet codes the same way you can do the other stuff might be enough for most of us to get by. Not being easy is ok, not being possible is a problem.
100% agree. I wish WotC would put some more work into the homebrew system.
Technically, you can overwrite class features in the subclass creator, so you could technically create a subclass of Fighter (or whatever), overwrite all their class features, make them invisible, then write in your own class features in their place, then take that as a "subclass." It... I think it would work...?
That is a lot of work, though, and I honestly don't know what it would do to the character sheet. Or if there's a class feature limit...
I haven't found a way to overwrite an existing class feature. I only see the replacement option for features I've made in the subclass. Am I looking in the wrong place? If I could make a "blank" template off of Fighter and could blank it all out myself, then rewrite it all from scratch, I would totally do that.
I dont remember the exact method, but if you create a class feature with the same name as another class feature, it shoul overwrite the old one. I don't know what happens if you then try to hide the class feature, though...