I created a Paladin Subclass that has some additional spells added to the Paladin Spell list. I added them to the subclass as Spells on a Class Feature and set:
Consumes Spell Slot: Yes
Counts as Known Spell: Yes
Always Prepared: No
However, when I assign the subclass to a character, they do not show up in my Known Spell list and they do show up as always prepared. It would seem that neither of these drop-downs is doing what it says on the tin.
There is no way to add spells to the spell list for a specific Paladin subclass and not have them automatically prepared. That’s just how Paladins are designed. Those drop downs would work that way for a known spellcaster such as a Sorcerer or Bard.
There is no way to add spells to the spell list for a specific Paladin subclass and not have them automatically prepared. That’s just how Paladins are designed. Those drop downs would work that way for a known spellcaster such as a Sorcerer or Bard.
This aligns with what I have discovered. I still think this is a bug though as those drop downs *very clearly* express what they do, and they definitely do not do what they say they do. The bug may be that "those dropdowns shouldn't exist" or the bug may be that "those drop downs are not behaving properly", but I can not imagine that a designer somewhere said, "lets create some dropdowns that say they do X and then have them do Y instead".
It certainly feels like a silly constraint to say that no Paladin Subclass can ever have additional spells known that are not always prepared. My guess is that they either haven't actually implemented the feature that those drop-downs are supposed to provide, or they implemented it and there is a bug that makes it not work for most classes.
There is no way to add spells to the spell list for a specific Paladin subclass and not have them automatically prepared. That’s just how Paladins are designed. Those drop downs would work that way for a known spellcaster such as a Sorcerer or Bard.
This aligns with what I have discovered. I still think this is a bug though as those drop downs *very clearly* express what they do, and they definitely do not do what they say they do. The bug may be that "those dropdowns shouldn't exist" or the bug may be that "those drop downs are not behaving properly", but I can not imagine that a designer somewhere said, "lets create some dropdowns that say they do X and then have them do Y instead".
It certainly feels like a silly constraint to say that no Paladin Subclass can ever have additional spells known that are not always prepared. My guess is that they either haven't actually implemented the feature that those drop-downs are supposed to provide, or they implemented it and there is a bug that makes it not work for most classes.
Because there was no homebrew creator originally. It was only ever intended for the developers to use, and when they got permission from the games publisher to implement a homebrew generator they quickly locked some stuff behind admin privileges and opened it up to the public. We are lucky to have a homebrew creator at all, since originally WotC (the game’s publisher) had prohibited this website from doing it by contract, and we only have the privilege available to us at all because the head of the company personally and singlehandedly fought for our privilege to homebrew for over a year.
There is no way to add spells to the spell list for a specific Paladin subclass and not have them automatically prepared. That’s just how Paladins are designed. Those drop downs would work that way for a known spellcaster such as a Sorcerer or Bard.
This aligns with what I have discovered. I still think this is a bug though as those drop downs *very clearly* express what they do, and they definitely do not do what they say they do. The bug may be that "those dropdowns shouldn't exist" or the bug may be that "those drop downs are not behaving properly", but I can not imagine that a designer somewhere said, "lets create some dropdowns that say they do X and then have them do Y instead".
It certainly feels like a silly constraint to say that no Paladin Subclass can ever have additional spells known that are not always prepared. My guess is that they either haven't actually implemented the feature that those drop-downs are supposed to provide, or they implemented it and there is a bug that makes it not work for most classes.
One way to do this—I think—with the current system is to homebrew the spells and specify the subclass in the “available to classes” box. My only hesitation is whether or not you can choose a homebrew subclass for that box.
One way to do this—I think—with the current system is to homebrew the spells and specify the subclass in the “available to classes” box. My only hesitation is whether or not you can choose a homebrew subclass for that box.
You want to create a homebrew version of the spell and make it available for Paladins. If you make it available to the subclass (where yes, you would be able to select a homebrew subclass), it will act as always prepared, but if you just make it generally available to Paladins, then your Paladin can treat it as a normal 'one of my spells I select to prepare after a long rest.'
I created a Paladin Subclass that has some additional spells added to the Paladin Spell list. I added them to the subclass as Spells on a Class Feature and set:
However, when I assign the subclass to a character, they do not show up in my Known Spell list and they do show up as always prepared. It would seem that neither of these drop-downs is doing what it says on the tin.
Pleas post a link to your homebrew. It doesn’t need to be published for moderators to see it.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
There is no way to add spells to the spell list for a specific Paladin subclass and not have them automatically prepared. That’s just how Paladins are designed. Those drop downs would work that way for a known spellcaster such as a Sorcerer or Bard.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
This aligns with what I have discovered. I still think this is a bug though as those drop downs *very clearly* express what they do, and they definitely do not do what they say they do. The bug may be that "those dropdowns shouldn't exist" or the bug may be that "those drop downs are not behaving properly", but I can not imagine that a designer somewhere said, "lets create some dropdowns that say they do X and then have them do Y instead".
It certainly feels like a silly constraint to say that no Paladin Subclass can ever have additional spells known that are not always prepared. My guess is that they either haven't actually implemented the feature that those drop-downs are supposed to provide, or they implemented it and there is a bug that makes it not work for most classes.
Because there was no homebrew creator originally. It was only ever intended for the developers to use, and when they got permission from the games publisher to implement a homebrew generator they quickly locked some stuff behind admin privileges and opened it up to the public. We are lucky to have a homebrew creator at all, since originally WotC (the game’s publisher) had prohibited this website from doing it by contract, and we only have the privilege available to us at all because the head of the company personally and singlehandedly fought for our privilege to homebrew for over a year.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
One way to do this—I think—with the current system is to homebrew the spells and specify the subclass in the “available to classes” box. My only hesitation is whether or not you can choose a homebrew subclass for that box.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
You want to create a homebrew version of the spell and make it available for Paladins. If you make it available to the subclass (where yes, you would be able to select a homebrew subclass), it will act as always prepared, but if you just make it generally available to Paladins, then your Paladin can treat it as a normal 'one of my spells I select to prepare after a long rest.'
Birgit | Shifter | Sorcerer | Dragonlords
Shayone | Hobgoblin | Sorcerer | Netherdeep