I think adding UA subclasses should be already a feature for homebrew creations. If there is something you wanna tweek for yourself or others in your party from an UA subclass you need to do all from scratch cuz the homebrew maker doesn't pull UA subclass content to take as a base. I was trying to tweek some aspects from Lurker of the Deep Warlock subclass that we discussed with my DM and I had to pretty much create the subclass from scratch even though all the info is already part of DDB database. It doesn't make any sense to penalize players who want to adjust certain aspects of an UA subclass when u guys already have all the info in there.
I just had to check this because I could have sworn I pulled from UA for my homebrews before. It looks like this is only true for subclasses. UA Items and Feats are in the homebrew creator. Maybe someone can answer why the subclasses aren't
We used to be able to pull from UA subclasses, but not anymore. I think that was to prevent us from making easy, free “homebrew versions” prior to archiving.
As far as I can remember, using UA subclasses as a base for copying hasn't ever been a thing. It's always been a thing for everything else, but not subclasses. I could be wrong, this is just going off my memory.
We used to be able to pull from UA subclasses, but not anymore. I think that was to prevent us from making easy, free “homebrew versions” prior to archiving.
the spirit of homebrewing is always to make things your own. Preventing to use UA subclasses only because of the reasoning of "free homebrew version" doesn't really make sense and it's unfair to all other players that simply want to tweek some aspects of UA subclasses. Following that same logic, then all UA should be as well blocked from the homebrew creator.
As far as I can remember, using UA subclasses as a base for copying hasn't ever been a thing. It's always been a thing for everything else, but not subclasses. I could be wrong, this is just going off my memory.
I really don't understand why this has to be a thing and from my perspective this is simply a deservice to players. Regardless if this was or wasn't a thing before, this needs to be allowed since UA content is getting constantly injected into the game and the flexibility to adjust features to shape your character shouldn't be restricted.
My point was more that it I believe it wasn't ever implemented as an option. The reason may actually be technical, due to subclasses working very differently from all other options.
My point was more that it I believe it wasn't ever implemented as an option. The reason may actually be technical, due to subclasses working very differently from all other options.
I don' think that UA classes are much more complicated than existing classes and either way the code is already in DDB as part of the subclass to be able to get added to your character sheet. If the same modifiers work in the funtional character sheet already, the only thing they need to do is open them to be part of the homebrew database. All the mechanical content from UA subclasses should already be optimized to work if allowed for homebrew.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I think adding UA subclasses should be already a feature for homebrew creations. If there is something you wanna tweek for yourself or others in your party from an UA subclass you need to do all from scratch cuz the homebrew maker doesn't pull UA subclass content to take as a base. I was trying to tweek some aspects from Lurker of the Deep Warlock subclass that we discussed with my DM and I had to pretty much create the subclass from scratch even though all the info is already part of DDB database. It doesn't make any sense to penalize players who want to adjust certain aspects of an UA subclass when u guys already have all the info in there.
I just had to check this because I could have sworn I pulled from UA for my homebrews before. It looks like this is only true for subclasses. UA Items and Feats are in the homebrew creator. Maybe someone can answer why the subclasses aren't
yeap I was surprised too tbh. and yes it seems it only applies to subclasses.
edit. added additional text to make this clear
We used to be able to pull from UA subclasses, but not anymore. I think that was to prevent us from making easy, free “homebrew versions” prior to archiving.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
As far as I can remember, using UA subclasses as a base for copying hasn't ever been a thing. It's always been a thing for everything else, but not subclasses. I could be wrong, this is just going off my memory.
Find my D&D Beyond articles here
the spirit of homebrewing is always to make things your own. Preventing to use UA subclasses only because of the reasoning of "free homebrew version" doesn't really make sense and it's unfair to all other players that simply want to tweek some aspects of UA subclasses. Following that same logic, then all UA should be as well blocked from the homebrew creator.
I really don't understand why this has to be a thing and from my perspective this is simply a deservice to players. Regardless if this was or wasn't a thing before, this needs to be allowed since UA content is getting constantly injected into the game and the flexibility to adjust features to shape your character shouldn't be restricted.
My point was more that it I believe it wasn't ever implemented as an option. The reason may actually be technical, due to subclasses working very differently from all other options.
Find my D&D Beyond articles here
My memory is not infallible. I might very well have misremembered. I am only human after all.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I don' think that UA classes are much more complicated than existing classes and either way the code is already in DDB as part of the subclass to be able to get added to your character sheet. If the same modifiers work in the funtional character sheet already, the only thing they need to do is open them to be part of the homebrew database. All the mechanical content from UA subclasses should already be optimized to work if allowed for homebrew.