Everything I've tried to get it to show has failed - is there a way to get it to show once more?
I've deselected Core, I've deselected everything but 2014. I am trying to recreate a character to use as an NPC.
You would need to use the 2014 version of the Warlock class instead. They’re two separate classes as far as D&D Beyond is concerned. Go to the Class tab and remove the class you have selected, then select the 2014 Warlock instead. You might need to scroll down to find it.
Everything I've tried to get it to show has failed - is there a way to get it to show once more?
I've deselected Core, I've deselected everything but 2014. I am trying to recreate a character to use as an NPC.
You would need to use the 2014 version of the Warlock class instead. They’re two separate classes as far as D&D Beyond is concerned. Go to the Class tab and remove the class you have selected, then select the 2014 Warlock instead. You might need to scroll down to find it.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
I'm speaking from a coding standpoint. That's missing code, not bugged code.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
To be fair, no one said DND Beyond 2024 would be backward compatible.
Sure, it's a bunch of baloney - there can be no doubt in their minds that subscribers fully expected everything to work properly re backward compatibility. And it should. We paid money for a product and a service, and we cannot use them effectively. It's total minotaur droppings.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
To be fair, no one said DND Beyond 2024 would be backward compatible.
They did. THEY said it. On their changelogs, and even on the DNDB marketplace right now, both TCoE and XGtE has a "COMPATIBLE WITH THE NEW CORE RULEBOOKS" affixed on the covers.
As a paid subscriber, I would just like to have them fully deliver on this as opposed to me having to homebrew a band-aid solution. Despite on the their changelog they put this in bold:
Players will not need to rely on Homebrew to use their 2014 player options, including spells and magic items, as recommended in previous changelogs.
Trying to hold them accountable to their promises nearly 2 years into their implementation isn't unreasonable.
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
To be fair, no one said DND Beyond 2024 would be backward compatible.
They did. THEY said it. On their changelogs, and even on the DNDB marketplace right now, both TCoE and XGtE has a "COMPATIBLE WITH THE NEW CORE RULEBOOKS" affixed on the covers.
As a paid subscriber, I would just like to have them fully deliver on this as opposed to me having to homebrew a band-aid solution. Despite on the their changelog they put this in bold:
Players will not need to rely on Homebrew to use their 2014 player options, including spells and magic items, as recommended in previous changelogs.
Trying to hold them accountable to their promises nearly 2 years into their implementation isn't unreasonable.
I do not disagree that DND Beyond should be fully backwards compatible, and it should have been that way from Minute One of the release (including early release for subscribers).
I guess I missed that part you bolded for emphasis. Or just did not remember it from a year ago. I stand corrected, well played.
Well, now. They really have 0 excuse for a shitty product, lol. It's really starting to piss me off and turn me off from the game I have loved since 1981 (12 years old).
Tasha's Cauldron of Everything's feats, Eldritch Adept and Metamagic Adept, are not utilizing the 2024 equivalents (Pact of the Blade, Agonizing Blast, Twinned Spell, etc.).
Oath of the Crown Paladin subclass from Sword Coast Adventurer's Guide isn't showing oath spells as always prepared.
Warlock's Eldritch Invocations for Agonizing Blast is STILL auto-selecting Eldritch Blast when 2024 allows it to be applied to any Warlock cantrip
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
I'm speaking from a coding standpoint. That's missing code, not bugged code.
Semantics aside, it's an issue. It's not working and requires a homebrew from the user-end to band-aid it. Missing/Bugged code is all the same to an end-user. Not trying to split hairs: just pointing out that at the end of August 2025, it's STILL not working.
You can play all of them using the legacy characters they added to being the sub-classes they have not updated in line with the 2024 rules. Are they the same as playing a 2024 sub-class in terms of prepared spells, etc, No. But you can play them and they work at the table. No homebrew needed.
You paid for the 2014 game. This is the 2024 game. They are updating the sub-classes as they go, Oath of Conquest Paladin is a playable option, you just don't get the additional spells added a s prepared spells, because the 2014 version just added them to your spell lsit -- which the expanded sub-class for the Oath of Conquest does add them to your spell list. This means your Oath of Conquest paladin is compatible with the 2024 rules and playable. They told us we would get 4 sub-classes per class in the 2024 PHB, and that's what we got. This is more than in the 2014 PHB, and they have created bridge sub-classes for all the ones that have not got the full update. Seems pretty good to me, and I have a character in my campaign multiclassed in two expanded classes, and he does not feel like he is under powered and is enjoying playing his character. Just as with any update, some things will be updated sooner than others. In the meantime, there are playable options for the older subclasses. I think your expectation of everything you ever bought, core, non-core, 3rd party is more than we can reasonably expect at this point.
The coding problems are different, and I hope they get resolved soon.
Oath of Conquest Paladin is a playable option, you just don't get the additional spells added a s prepared spells, because the 2014 version just added them to your spell lsit -- which the expanded sub-class for the Oath of Conquest does add them to your spell list. This means your Oath of Conquest paladin is compatible with the 2024 rules and playable.
Just for the record, this isn’t correct; both versions of Oath of Conquest (and all other Paladin subclasses) are supposed to provide Oath Spells as “always prepared”, not just added to the spell list.
D&D Beyond’s character builder doesn’t do this for 2014 subclasses used with the 2024 Paladin class. This is not correct behavior; it’s an outstanding bug that’s been present since the launch of the 2024 updates a year ago, and it’s reasonable for people to be frustrated about that.
You are correct, and I am incorrect. I apologize. I had thought it was like other classes thast just added the listed spells to your available spells, I went and double-checked the 2014 PHB, and it says for paladins they gain their oath spells as prepared and not just added to the spell list. Thanks for the polite correction.
Oath Spells
Each oath has a list of associated spells. You gain access to these spells at the levels specified in the oath description. Once you gain access to an oath spell, you always have it prepared. Oath spells don’t count against the number of spells you can prepare each day.
You are correct, and I am incorrect. I apologize. I had thought it was like other classes thast just added the listed spells to your available spells, I went and double-checked the 2014 PHB, and it says for paladins they gain their oath spells as prepared and not just added to the spell list. Thanks for the polite correction.
The only 5e class where the subclasses just added their special spells to the spell list, without making them always prepared, was the 2014 Warlock. That was wisely corrected in the 2024 version.
I think your expectation of everything you ever bought, core, non-core, 3rd party is more than we can reasonably expect at this point.
The coding problems are different, and I hope they get resolved soon.
My expectation is based on their promises: backwards compatibility and no need to home-brew 2014 options for 2024 ruleset. I didn't set that expectation. THEY did. Not unreasonable for me to expect that deliver on that. Also, this isn't like a month or two into the implementation. We are nearing the end of Q3 of 2025, and there are STILL a myriad of issues that have NOT been resolved yet. It's unreasonable to NOT be frustrated about this. It's unreasonable that I have to homebrew or customize on my end to make things work as intended. And DNDB isn't some third-party non-affiliated platform: it is THE official digital platform for D&D that is OWNED by very people who publish the game. One would reasonably expect that would prioritize fixes to the official digital platform for their game in which they updated.
I think your expectation of everything you ever bought, core, non-core, 3rd party is more than we can reasonably expect at this point.
The coding problems are different, and I hope they get resolved soon.
My expectation is based on their promises: backwards compatibility and no need to home-brew 2014 options for 2024 ruleset. I didn't set that expectation. THEY did. Not unreasonable for me to expect that deliver on that. Also, this isn't like a month or two into the implementation. We are nearing the end of Q3 of 2025, and there are STILL a myriad of issues that have NOT been resolved yet. It's unreasonable to NOT be frustrated about this. It's unreasonable that I have to homebrew or customize on my end to make things work as intended. And DNDB isn't some third-party non-affiliated platform: it is THE official digital platform for D&D that is OWNED by very people who publish the game. One would reasonably expect that would prioritize fixes to the official digital platform for their game in which they updated.
100%! BRAVO!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Everything I've tried to get it to show has failed - is there a way to get it to show once more?
I've deselected Core, I've deselected everything but 2014. I am trying to recreate a character to use as an NPC.
You would need to use the 2014 version of the Warlock class instead. They’re two separate classes as far as D&D Beyond is concerned. Go to the Class tab and remove the class you have selected, then select the 2014 Warlock instead. You might need to scroll down to find it.
pronouns: he/she/they
I think I love you....
Any updates when these will be fixed?
First isn't a bug. They would need to implement a 2024 version of the feats to do that because of the way it's listed in the system.
To me, it's a bug when TCoE and XGtE specifically state they are backwards compatible and they're not. If it's supposedly backwards compatible to the 2024 ruleset, they should be pulling the 2024 rules.
I'm speaking from a coding standpoint. That's missing code, not bugged code.
To be fair, no one said DND Beyond 2024 would be backward compatible.
Sure, it's a bunch of baloney - there can be no doubt in their minds that subscribers fully expected everything to work properly re backward compatibility. And it should. We paid money for a product and a service, and we cannot use them effectively. It's total minotaur droppings.
They did. THEY said it. On their changelogs, and even on the DNDB marketplace right now, both TCoE and XGtE has a "COMPATIBLE WITH THE NEW CORE RULEBOOKS" affixed on the covers.
As a paid subscriber, I would just like to have them fully deliver on this as opposed to me having to homebrew a band-aid solution. Despite on the their changelog they put this in bold:
Players will not need to rely on Homebrew to use their 2014 player options, including spells and magic items, as recommended in previous changelogs.
Trying to hold them accountable to their promises nearly 2 years into their implementation isn't unreasonable.
I do not disagree that DND Beyond should be fully backwards compatible, and it should have been that way from Minute One of the release (including early release for subscribers).
I guess I missed that part you bolded for emphasis. Or just did not remember it from a year ago. I stand corrected, well played.
Well, now. They really have 0 excuse for a shitty product, lol. It's really starting to piss me off and turn me off from the game I have loved since 1981 (12 years old).
Semantics aside, it's an issue. It's not working and requires a homebrew from the user-end to band-aid it. Missing/Bugged code is all the same to an end-user. Not trying to split hairs: just pointing out that at the end of August 2025, it's STILL not working.
You can play all of them using the legacy characters they added to being the sub-classes they have not updated in line with the 2024 rules. Are they the same as playing a 2024 sub-class in terms of prepared spells, etc, No. But you can play them and they work at the table. No homebrew needed.
You paid for the 2014 game. This is the 2024 game. They are updating the sub-classes as they go, Oath of Conquest Paladin is a playable option, you just don't get the additional spells added a s prepared spells, because the 2014 version just added them to your spell lsit -- which the expanded sub-class for the Oath of Conquest does add them to your spell list. This means your Oath of Conquest paladin is compatible with the 2024 rules and playable. They told us we would get 4 sub-classes per class in the 2024 PHB, and that's what we got. This is more than in the 2014 PHB, and they have created bridge sub-classes for all the ones that have not got the full update. Seems pretty good to me, and I have a character in my campaign multiclassed in two expanded classes, and he does not feel like he is under powered and is enjoying playing his character. Just as with any update, some things will be updated sooner than others. In the meantime, there are playable options for the older subclasses. I think your expectation of everything you ever bought, core, non-core, 3rd party is more than we can reasonably expect at this point.
The coding problems are different, and I hope they get resolved soon.
Just for the record, this isn’t correct; both versions of Oath of Conquest (and all other Paladin subclasses) are supposed to provide Oath Spells as “always prepared”, not just added to the spell list.
D&D Beyond’s character builder doesn’t do this for 2014 subclasses used with the 2024 Paladin class. This is not correct behavior; it’s an outstanding bug that’s been present since the launch of the 2024 updates a year ago, and it’s reasonable for people to be frustrated about that.
pronouns: he/she/they
You are correct, and I am incorrect. I apologize. I had thought it was like other classes thast just added the listed spells to your available spells, I went and double-checked the 2014 PHB, and it says for paladins they gain their oath spells as prepared and not just added to the spell list. Thanks for the polite correction.
Oath Spells
Each oath has a list of associated spells. You gain access to these spells at the levels specified in the oath description. Once you gain access to an oath spell, you always have it prepared. Oath spells don’t count against the number of spells you can prepare each day.
The only 5e class where the subclasses just added their special spells to the spell list, without making them always prepared, was the 2014 Warlock. That was wisely corrected in the 2024 version.
pronouns: he/she/they
My expectation is based on their promises: backwards compatibility and no need to home-brew 2014 options for 2024 ruleset. I didn't set that expectation. THEY did. Not unreasonable for me to expect that deliver on that. Also, this isn't like a month or two into the implementation. We are nearing the end of Q3 of 2025, and there are STILL a myriad of issues that have NOT been resolved yet. It's unreasonable to NOT be frustrated about this. It's unreasonable that I have to homebrew or customize on my end to make things work as intended. And DNDB isn't some third-party non-affiliated platform: it is THE official digital platform for D&D that is OWNED by very people who publish the game. One would reasonably expect that would prioritize fixes to the official digital platform for their game in which they updated.
100%! BRAVO!