Still not working. I created feats for my crown spells, but as mentioned above, I have to manage the spells slots manually. Seems like this should be an easy fix. Come on.
I just created a Paladin subclassed as Oath of the Crown, and I took don't have my Crown Oath Spells automatically prepared and if I select them, they take up my prepared spell slot when they shouldn't. Why is this still a bug and hasn't been fixed yet???
Having the same issue as the OP, replying here since I see the community has been waiting months for a patch to fix this bug. Oath spells from Oath of Vengeance and the other subclasses straight from the 2024 PHB, not expanded rules, still fail to appear in the spells list as always prepared. Although, the always-prepared spells correctly load in the character screen; that’s how I noticed accidental duplicates. Needing to remember the four oath spells plus Divine Smite that my paladin always has ready makes it very tedious to prepare spells, and it disincentivizes players from using the new 2024 rules, since oath spells and other features in the old 2015 classes continue to work as normal. Could we please get a fix for this soon, DDB?
I think the reason they haven't patched this quite annoying glitch, Ritual Caster, and Warlock Invocations is quite simple:
Monopoly Go!'s temporary fix in upping company profits, & thus the stock price, has diverted Hasbro bigwigs & investors yet again into being bad stewards of the Dungeons & Dragons brand by neutering WotC's remaining independence & neglecting DND Beyond's functions beyond a mostly domestic sales terminal, yet again as a result of post-2020 policy shifts in the US from its corporate scene at large. So there's(assertedly) no budget for even a temporary flotilla of gig programmers to work with the spaghetti coding, fix the litany of glitches, bugs & copy editing fails, &/or fulfill promises old & new in a Monopoly Go!-oriented company. Why spend money if you can just MAKE ALL THE MORE INFINITE MONEY via a app that costs less on Hasbro's end by paying a Saudi Arabian company to do all the dev work on it for a fraction of the price(Just like Game Freak/Nintendo/TPCI did by letting Niantic sell the development of Pokemon Go to the SAME company Hasbro hired to do Monopoly Go!...grumble grumble...)?
Wish Washington(The state) had a law saying you could challenge their ownership of Dungeons & Dragons based on how terrible their stewardship of the brand is. Some states do have these laws, but they don't apply to Washington.
Hire domestic human programmers to fix real problems, instead of relying on cheap money-spewing gambling apps to plug the inevitable net losses & slow death company-wide failures from all of these foolhardy attempts by servile executives at infinite endless upward growth & profit in order to appease their investor masters' greed. & don't turn WotC into a label like what was done to Parker Brothers. Those are the lessons here.
Rollback Post to RevisionRollBack
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
What's the point in having a forum for reporting bugs when the reports are not even acknowledged, never mind addressed?
This particular bug has been acknowledged many times — not in this particular thread, but there have been many threads reporting this same issue.
You're right that it should have been fixed many months ago, but they have made it clear to us they're aware of it.
I mean the fact that there have been many threads on this topic alone speaks volumes and their "awareness" has yet to translate into a solution. It's near the middle of 2025 already, and I've seen threads on this topic as early as 2017. I mean come on. Of course there'll be numerous threads about it because they haven't resolved them, and users bump this topic as a new thread because the old threads appear to be forgotten. I had to search for my own solution which was to home-brew the subclass to force those spells to appear as they were intended, instead of it being there after the PHB and the SCAG was purchased.
What's the point in having a forum for reporting bugs when the reports are not even acknowledged, never mind addressed?
This particular bug has been acknowledged many times — not in this particular thread, but there have been many threads reporting this same issue.
You're right that it should have been fixed many months ago, but they have made it clear to us they're aware of it.
I mean the fact that there have been many threads on this topic alone speaks volumes and their "awareness" has yet to translate into a solution. It's near the middle of 2025 already, and I've seen threads on this topic as early as 2017. I mean come on. Of course there'll be numerous threads about it because they haven't resolved them, and users bump this topic as a new thread because the old threads appear to be forgotten. I had to search for my own solution which was to home-brew the subclass to force those spells to appear as they were intended, instead of it being there after the PHB and the SCAG was purchased.
I get the frustration.
Oh, don’t get me wrong - I share the frustration too. It’s ridiculous that this got released with an issue this big in it, and even more ridiculous that it hasn’t been fixed in almost a year since then. But claiming that they haven’t acknowledged it as an issue is objectively false and doesn’t help anything.
You know what else doesn't help anything? Acknowledging a bug in some old thread that no one will ever find and thinking that's good enough.
I experienced this bug for the first time 2 months ago. I went looking for an old thread to see if there was any discussion or solutions. You know, as one does. I found this thread which was 8 months old at the time and I added my voice to the many others. This thread is 10 months old now and not a single person in here has been acknowledged. Not one.
Oath of the Crown still bugged. Any updates on this?
The only workaround I had was to home-brew the subclass.
Thankfully, you can just copy the Oath of the Crown subclass as a template. Then go into the class features sections, edit the oath spells. Scroll down to the spells section, and then manually add the 10 spells. When you add them, just choose the 2024 versions of the spells, and then go to the bottom, and select yes on consumes spell slot and always prepared: make sure you select no on counts as known spell. Ensure you're made them available for the specific character level. Then repeat until all 10 oath spells are listed. Then save on the section and then save on the subclass.
I've called the class Oath of the Crown (2024 Variant), and those spells will now appear on your character sheet as always prepared and don't count towards your prepared list when you select this home-brew subclass.
It took me about half an hour to add all 10 spells. It's not ideal, but it'll at least work.
Oath of the Crown still bugged. Any updates on this?
The only workaround I had was to home-brew the subclass.
Thankfully, you can just copy the Oath of the Crown subclass as a template. Then go into the class features sections, edit the oath spells. Scroll down to the spells section, and then manually add the 10 spells. When you add them, just choose the 2024 versions of the spells, and then go to the bottom, and select yes on consumes spell slot and always prepared: make sure you select no on counts as known spell. Ensure you're made them available for the specific character level. Then repeat until all 10 oath spells are listed. Then save on the section and then save on the subclass.
I've called the class Oath of the Crown (2024 Variant), and those spells will now appear on your character sheet as always prepared and don't count towards your prepared list when you select this home-brew subclass.
It took me about half an hour to add all 10 spells. It's not ideal, but it'll at least work.
Don't forget to also go into the description text for the feature and edit the markup tags for the spell names from "spell" to "spells".
I've toyed around with the idea of making a browser extension that you run from the D&D Beyond webpage that automates adding all of these Homebrews since you can't bloody share 'em. Eh...
If something takes a user 30 minutes to fix with homebrew, why can't they spare 30 minutes for someone to go in and fix the tagging/settings on the official subclass?
If something takes a user 30 minutes to fix with homebrew, why can't they spare 30 minutes for someone to go in and fix the tagging/settings on the official subclass?
Because Hasbro & its investors are American landlord-style cheap, & would rather make WotC & Beyond crumbling factories, & e-slums, respectfully, than spend a penny.
Rollback Post to RevisionRollBack
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
Oath of the Crown still bugged. Any updates on this?
The only workaround I had was to home-brew the subclass.
Thankfully, you can just copy the Oath of the Crown subclass as a template. Then go into the class features sections, edit the oath spells. Scroll down to the spells section, and then manually add the 10 spells. When you add them, just choose the 2024 versions of the spells, and then go to the bottom, and select yes on consumes spell slot and always prepared: make sure you select no on counts as known spell. Ensure you're made them available for the specific character level. Then repeat until all 10 oath spells are listed. Then save on the section and then save on the subclass.
I've called the class Oath of the Crown (2024 Variant), and those spells will now appear on your character sheet as always prepared and don't count towards your prepared list when you select this home-brew subclass.
It took me about half an hour to add all 10 spells. It's not ideal, but it'll at least work.
Don't forget to also go into the description text for the feature and edit the markup tags for the spell names from "spell" to "spells".
I've toyed around with the idea of making a browser extension that you run from the D&D Beyond webpage that automates adding all of these Homebrews since you can't bloody share 'em. Eh...
What does that do?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The final result is the same. The content is unavailable a year after this launched.
Still not working. I created feats for my crown spells, but as mentioned above, I have to manage the spells slots manually. Seems like this should be an easy fix. Come on.
I just created a Paladin subclassed as Oath of the Crown, and I took don't have my Crown Oath Spells automatically prepared and if I select them, they take up my prepared spell slot when they shouldn't. Why is this still a bug and hasn't been fixed yet???
How did you get the home-brew feat to get the spell to be always prepared?
Having the same issue as the OP, replying here since I see the community has been waiting months for a patch to fix this bug. Oath spells from Oath of Vengeance and the other subclasses straight from the 2024 PHB, not expanded rules, still fail to appear in the spells list as always prepared. Although, the always-prepared spells correctly load in the character screen; that’s how I noticed accidental duplicates. Needing to remember the four oath spells plus Divine Smite that my paladin always has ready makes it very tedious to prepare spells, and it disincentivizes players from using the new 2024 rules, since oath spells and other features in the old 2015 classes continue to work as normal. Could we please get a fix for this soon, DDB?
I think the reason they haven't patched this quite annoying glitch, Ritual Caster, and Warlock Invocations is quite simple:
Monopoly Go!'s temporary fix in upping company profits, & thus the stock price, has diverted Hasbro bigwigs & investors yet again into being bad stewards of the Dungeons & Dragons brand by neutering WotC's remaining independence & neglecting DND Beyond's functions beyond a mostly domestic sales terminal, yet again as a result of post-2020 policy shifts in the US from its corporate scene at large. So there's(assertedly) no budget for even a temporary flotilla of gig programmers to work with the spaghetti coding, fix the litany of glitches, bugs & copy editing fails, &/or fulfill promises old & new in a Monopoly Go!-oriented company. Why spend money if you can just MAKE ALL THE MORE INFINITE MONEY via a app that costs less on Hasbro's end by paying a Saudi Arabian company to do all the dev work on it for a fraction of the price(Just like Game Freak/Nintendo/TPCI did by letting Niantic sell the development of Pokemon Go to the SAME company Hasbro hired to do Monopoly Go!...grumble grumble...)?
Wish Washington(The state) had a law saying you could challenge their ownership of Dungeons & Dragons based on how terrible their stewardship of the brand is. Some states do have these laws, but they don't apply to Washington.
Hire domestic human programmers to fix real problems, instead of relying on cheap money-spewing gambling apps to plug the inevitable net losses & slow death company-wide failures from all of these foolhardy attempts by servile executives at infinite endless upward growth & profit in order to appease their investor masters' greed. & don't turn WotC into a label like what was done to Parker Brothers. Those are the lessons here.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
What's the point in having a forum for reporting bugs when the reports are not even acknowledged, never mind addressed?
This particular bug has been acknowledged many times — not in this particular thread, but there have been many threads reporting this same issue.
You're right that it should have been fixed many months ago, but they have made it clear to us they're aware of it.
pronouns: he/she/they
I'm so happy they are aware of it.
I mean the fact that there have been many threads on this topic alone speaks volumes and their "awareness" has yet to translate into a solution. It's near the middle of 2025 already, and I've seen threads on this topic as early as 2017. I mean come on. Of course there'll be numerous threads about it because they haven't resolved them, and users bump this topic as a new thread because the old threads appear to be forgotten. I had to search for my own solution which was to home-brew the subclass to force those spells to appear as they were intended, instead of it being there after the PHB and the SCAG was purchased.
I get the frustration.
Oh, don’t get me wrong - I share the frustration too. It’s ridiculous that this got released with an issue this big in it, and even more ridiculous that it hasn’t been fixed in almost a year since then. But claiming that they haven’t acknowledged it as an issue is objectively false and doesn’t help anything.
pronouns: he/she/they
Hello, Oath of the Watcher is still bugged for me :( any updates on fix?
You know what else doesn't help anything? Acknowledging a bug in some old thread that no one will ever find and thinking that's good enough.
I experienced this bug for the first time 2 months ago. I went looking for an old thread to see if there was any discussion or solutions. You know, as one does. I found this thread which was 8 months old at the time and I added my voice to the many others. This thread is 10 months old now and not a single person in here has been acknowledged. Not one.
Oath of the Crown still bugged. Any updates on this?
The only workaround I had was to home-brew the subclass.
Thankfully, you can just copy the Oath of the Crown subclass as a template. Then go into the class features sections, edit the oath spells. Scroll down to the spells section, and then manually add the 10 spells. When you add them, just choose the 2024 versions of the spells, and then go to the bottom, and select yes on consumes spell slot and always prepared: make sure you select no on counts as known spell. Ensure you're made them available for the specific character level. Then repeat until all 10 oath spells are listed. Then save on the section and then save on the subclass.
I've called the class Oath of the Crown (2024 Variant), and those spells will now appear on your character sheet as always prepared and don't count towards your prepared list when you select this home-brew subclass.
It took me about half an hour to add all 10 spells. It's not ideal, but it'll at least work.
Men it's been how long? And the issue is still at large. Why didn't they fix it yet? What a joke.
Don't forget to also go into the description text for the feature and edit the markup tags for the spell names from "spell" to "spells".
I've toyed around with the idea of making a browser extension that you run from the D&D Beyond webpage that automates adding all of these Homebrews since you can't bloody share 'em. Eh...
If something takes a user 30 minutes to fix with homebrew, why can't they spare 30 minutes for someone to go in and fix the tagging/settings on the official subclass?
Because Hasbro & its investors are American landlord-style cheap, & would rather make WotC & Beyond crumbling factories, & e-slums, respectfully, than spend a penny.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
What does that do?