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.
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.