I created a spell that is available for a Knowledge Domain cleric. It seems any Knowledge Domain cleric who has access to my Homebrew gets it as always prepared, but the remove button is there in the spell management also, and when clicking on it it throws an error.
You know how the prepared caster classes like Clerics, Druids, or Artificers, all have little mini spell lists for each subclass? Those mini spell lists all have a special rule as part of the class feature. For clerics it reads as follows:
Domain Spells
Each domain has a list of spells — its domain spells — that you gain at the cleric levels noted in the domain description. Once you gain a domain spell, you always have it prepared, and it doesn’t count against the number of spells you can prepare each day.
If you have a domain spell that doesn’t appear on the cleric spell list, the spell is nonetheless a cleric spell for you.
Notice the part I highlighted? Every one of those class feature descriptions include some version of that line. Whenever you list a specific subclass for any of the prepared spellcasters as a designated spell list in which the homebrew should appear, it has to follow those rules. Make sense?
This homebrew spell should NOT work like a domain spell. It should not be always prepared, but available to prepare for specific domains, and NOT clerics as a whole.
If I understand you right I can't create a spell like that, because as soon as I designate it available to a domain it becomes an always prepared domain spell?
And even if it should be always prepared, the bug that it shows the remove button below the always prepared flag for the spell remains.
Not necessarily, you might just have to rework it a bit. There’s another way to add spells to a subclass. How many spells are we talking about here, and are there any other relevant details I need to know?
Not much spells at the moment. These spells mostly would be like more unique divination based spells for knowledge domain (god of fate), or selectable damage+support spells for war domain.
You can add preparable spell this other way? Because that would be my main intrest. Otherwise I could make a cleric spell and put (for XY domain) in the description.
Well, not exactly, but kindasorta, but not really.
As part of a class feature, you can attach spells. If you were willing to be a little flexible, you might be able to pull off something close. When you attach a spell as part of a class feature, you have a whole bunch of options such as to “consumers spell slot: Y/N”, “counts as known: Y/N”, and “always prepared: Y/N”.
So, theoretical it might be possible to give them a class feature with an option of one of those two domains you listed. And then, as part of those options, add the spells. I’m not 100% sure it will work, but if you program those spells to “consume spell slot: Yes”, “counts as known: Yes”, and “always prepared: No”, you might be able to get it to do almost exactly the same thing. It might not, but I think it should work.
If not, then just go with your idea of putting it on the main spell list and putting the available subclasses in the description.
Sadly it is not working as hoped. The class feature adds them to the spell list automatically even if I set No to "always prepared".
The other interesting thing is that I set it to “counts as known”, and it shows that "*1 spells included from class features." but still does not appear in the list.
Seems I stuck with writing the restriction in the description.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I created a spell that is available for a Knowledge Domain cleric. It seems any Knowledge Domain cleric who has access to my Homebrew gets it as always prepared, but the remove button is there in the spell management also, and when clicking on it it throws an error.
You know how the prepared caster classes like Clerics, Druids, or Artificers, all have little mini spell lists for each subclass? Those mini spell lists all have a special rule as part of the class feature. For clerics it reads as follows:
Notice the part I highlighted? Every one of those class feature descriptions include some version of that line. Whenever you list a specific subclass for any of the prepared spellcasters as a designated spell list in which the homebrew should appear, it has to follow those rules. Make sense?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
This homebrew spell should NOT work like a domain spell. It should not be always prepared, but available to prepare for specific domains, and NOT clerics as a whole.
If I understand you right I can't create a spell like that, because as soon as I designate it available to a domain it becomes an always prepared domain spell?
And even if it should be always prepared, the bug that it shows the remove button below the always prepared flag for the spell remains.
You have in fact understood me correctly. And yes, that does in fact seem to be a separate bug.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Well, time to scrap my deity based spell ideas. Thanks for the clarification.
Not necessarily, you might just have to rework it a bit. There’s another way to add spells to a subclass. How many spells are we talking about here, and are there any other relevant details I need to know?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Not much spells at the moment. These spells mostly would be like more unique divination based spells for knowledge domain (god of fate), or selectable damage+support spells for war domain.
You can add preparable spell this other way? Because that would be my main intrest. Otherwise I could make a cleric spell and put (for XY domain) in the description.
Well, not exactly, but kindasorta, but not really.
As part of a class feature, you can attach spells. If you were willing to be a little flexible, you might be able to pull off something close. When you attach a spell as part of a class feature, you have a whole bunch of options such as to “consumers spell slot: Y/N”, “counts as known: Y/N”, and “always prepared: Y/N”.
So, theoretical it might be possible to give them a class feature with an option of one of those two domains you listed. And then, as part of those options, add the spells. I’m not 100% sure it will work, but if you program those spells to “consume spell slot: Yes”, “counts as known: Yes”, and “always prepared: No”, you might be able to get it to do almost exactly the same thing. It might not, but I think it should work.
If not, then just go with your idea of putting it on the main spell list and putting the available subclasses in the description.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Thanks for the advice.
Sadly it is not working as hoped. The class feature adds them to the spell list automatically even if I set No to "always prepared".
The other interesting thing is that I set it to “counts as known”, and it shows that "*1 spells included from class features." but still does not appear in the list.
Seems I stuck with writing the restriction in the description.