Trying to make an acolyte and the Magic Initiate Origin Feat is only showing cleric, but I should be able to choose druid or wizard as well, correct? I am making a cleric, but I should be able take spells from those other classes correct?
The background comes specifically with the cleric version of the feat.
Can't take the Elemental Adept feat despite being high enough level and having the Spellcasting feature.
As others have noted, I can choose to take a Fighting Style but no dropdown is presented to choose which Fighting Style Feat.
I am using a Legacy Race and a 2024 Background and it lets me double up on ability score bonuses (chooses them both in the Background and the Abilities dialog).
Oath spells do not appear automatically as known (I am using a legacy subclass).
Divine Smith shows up in the spell list to be chosen even though it is always prepared.
I can now choose Elemental Adept. (FIXED)
I can now choose a Fighting Style. (FIXED)
Oath Spells still aren't show up for my legacy subclass (Redemption).
Divine Smite is still showing up on the Add Spells list.
Noticed another issue:
Channel Divinity isn't properly showing the number of uses in Features or under the Limited Use tab.
It is not DDB's goal to meet that expectation to attract those customers, unless attracting those customers is worth the effort put into attracting them. If it's literally 20 of you asking for it, that's not worth their while. They can focus on something 100 people asked for. The idea that someone is entitled to a change just because they asked for it is an egotistical fallacy.
I'll chip in and say I do want them to actually add full backwards compatibility as promised.
Backwards compability means anything that wasn't included in the PHB revision is still legal and accessible, and are valid choices by the PHBs own description: "But the book contains many new or redesigned elements, and the versions of things in this book replace versions from older books." - The book does not invalidate all of the existing options from Xanathar's and Tasha's, on the contrary. It specifically says it only updates the PHB. This is not a new edition. It is a revision, hence why DNDBeyond doesn't even list a lot of XGtE and TCoE options as Legacy: Because they are not.
You're also making an assumption of how many people want X over Y. I can promise you, we are a lot more than 20 people asking for the full backwards compatibility with al older books that wasn't updated/redesigned.
You're stuck on the number "20" instead of the economic concept I am attempting to explain to you. The actual number of you is irrelevant to this scenario, EXCEPT in regard to the potential acquisition/retention of customers it presents in relation to other items they can work on. There could be 1 million of you who want that. But if there 100 billion who want something else more, it makes more sense for them to serve the 100 billion before getting to the million. The payoff for the one million is insignificant compared to the 100 billion.
The real issue here, is we don't have any of those numbers. However, I do know Hasbro loves money, so if they thought there was significant money/acquisition/retention in doing what you are asking, there would be a distinct push to do that thing as soon as possible. You are free to believe different. I am not arguing the point with you any longer.
The Channel Divinity feature for Paladin does not display the Divine Sense option on the character sheet. In fact, Channel Divinity does not seem to appear at all outside of the subclass features, so the explanation of how many uses it has is hard to find. Because of this, it also lacks any check boxes to track its uses in the character sheet.
There is also a weird glitch when viewing the "Manage Spells" sidebar where the Aid spell is listed as Always Prepared despite not actually being prepared. It also still has a "Learn" button underneath the "Always Prepared" statement, and clicking on it prepares the spell but doesn't remove the "Always Prepared" statement.
The Chef feat also does not display limited use tracking fields in the actions tab like the Tasha's version did. Additionally, when calculating the number of people eligible for the Refreshing Meal portion of the feat, the snippet reads "4 +3". If the snippet code used here was instead "4+proficiency#unsigned" then the actual total number would be legible.
Leomund's Tiny Hut and Detect Magic, as well as surely many other spells I haven't noticed yet, all lack the ritual tag that they should have.
Harness Divine Power, from Tasha's, is not available when you make a new character with the 2024 rules. I have a Twilight Cleric where all features seem to be there except this one (we are level 4 though).
This is deliberate. The Tasha's features were to upgrade classes, and the 2024 classes have been rebalanced. Some of the Tasha's features were ported over, some have become irrelevant in various ways, and some presumably they didn't feel were necessary.
How can you be sure? Is this posted somewhere officially or just your opinion?
When in the character sheet, clicking the dice to roll either the to Hit and Damage, or just the damage separately, it is adding both the Bludgeoning damage and the Force damage to the Total damage (it should be one or the other, but not both together). This looks impressive but is misleading.
Harness Divine Power, from Tasha's, is not available when you make a new character with the 2024 rules. I have a Twilight Cleric where all features seem to be there except this one (we are level 4 though).
This is deliberate. The Tasha's features were to upgrade classes, and the 2024 classes have been rebalanced. Some of the Tasha's features were ported over, some have become irrelevant in various ways, and some presumably they didn't feel were necessary.
How can you be sure? Is this posted somewhere officially or just your opinion?
Are you honestly going to look at the new classes, see that some of the Tasha's features are baked in standard but not all, and say "oh, that must be an accident, they couldn't possibly have chosen not to use those features"?
The intent is clear by the design. Anyone who argues otherwise is just looking to argue, not actually paying attention to the game.
Trying to make an acolyte and the Magic Initiate Origin Feat is only showing cleric, but I should be able to choose druid or wizard as well, correct? I am making a cleric, but I should be able take spells from those other classes correct?
Nope. Each of the new 2024 Backgrounds has one, and only one, specific origin feat attached to it. If you choose Acolyte, you get Magic Initiate: Cleric. That's it. That's what comes with that background; that particular feat and nothing else. If you want Magic Initiate: Druid, you must select Guide as your background. If you want Magic Initiate: Wizard, you must select Sage as your background.
That's it. Those are your choices. The new backgrounds will shoehorn you specifically in one direction and one direction only. Personally, I hate them. In an effort to remove racism, WotC has instead opted to add classism to the game. A noble will inherently be smarter and more personable than a farmer, because that's the way the rules work now. Bravo, WotC! *slow sarcastic applause* Braaaaa-VO!
(Yeah, that particular change has made me cranky. Sorry if I offend.)
Sear Undead seems to be broken on DND Beyond... under Actions, it's listed as an attack but it doesn't show the Saving Throw DC and it lists damage as only 1d8, instead of the correct 1d8 per Wisdom bonus modifier.
I "advanced search"ed this thread, and didn't find that anyone else listed this bug yet.
What background would you rather have? You can make up your own backgrounds.
Forcing us to make up our own defeats the purpose of using DND Beyond to make character creation quick and easy. It's nice that we have the option to bypass this ignorant new core rule, but it would be better if it weren't necessary.
Personally, I just continue to use the 2014 Backgrounds, and add an origin feat of my choice manually; whichever one seems to fit that character's nature and personality the best. As for stats, if you don't use 2024 Backgrounds (and instead stick with the ones available before this update), you can add your ability score bonuses wherever you please in DND Beyond, under 4. Abilities.
My grief with WotC is that they claimed to abolish the racial restrictions on ability scores to make the game more evolved and accepting to everyone, and instead saddled us with classism in lieu of racism. They've fixed nothing by this pointless change, only shifted the issue from restrictive races to restrictive backgrounds. Tasha's already fixed the racial ability stats four years ago by letting players put their ability score mods where they pleased, but instead of codifying that optional rule, they enforced a new one that is just as bad as the one they tried to fix.
Since Tasha's changed the attribute bonuses, your species become pretty much irrelevant for that. Given that, moving the attribute modifier to Backgrounds made sense.
I am sure they will add more backgrounds over time, but if there is something that you come up with that you want to use now, I would do that. It is really easy to make up custom stuff. The downside is that people often make up stuff that is way OP. Sometimes on purpose, but more often due to a lack of overall game sense.
Ideally, a made up background would add something to a particular game world. That would help characters to fit the setting better. Of course, if you come up with a good generic one, please share.
Sear Undead seems to be broken on DND Beyond... under Actions, it's listed as an attack but it doesn't show the Saving Throw DC and it lists damage as only 1d8, instead of the correct 1d8 per Wisdom bonus modifier.
I "advanced search"ed this thread, and didn't find that anyone else listed this bug yet.
"number of d? equal to ? score mod" is not a function that the D&D Beyond system is designed to support.
Sear Undead does not have a saving throw - it only applies to the undead that fail Turn Undead which has a saving throw - the DC is found under Spells. The main point of the section you're looking at is to see Attacks and Turn Undead is not an attack. The purpose of the action is for the damage but is limited by an unsupported feature.
Now, having said that, I do agree it is poorly implemented even when factoring the unsupported damage function. It would be simple enough for the system to add the Saving Throw DC in there for Turn Undead for easier reference.
Hopefully this is something they will get around to.
In the meantime I would recommend clicking the Sear Undead action, customise it and uncheck the Display As Attack to remove the utterly pointless action from the list. I would then create a custom action to input the damage for Sear Undead and another one for Turn Undead for showing the Save DC. This way you have easy and clear reference to both features. If anyone would like me to make a video showing how to do this please let me know and I will see if I can make one.
This is the test account of Cyb3rM1nd. Posting through this because my main account is locked out of forums due to a glitch.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
Since Tasha's changed the attribute bonuses, your species become pretty much irrelevant for that. Given that, moving the attribute modifier to Backgrounds made sense.
I am sure they will add more backgrounds over time, but if there is something that you come up with that you want to use now, I would do that. It is really easy to make up custom stuff. The downside is that people often make up stuff that is way OP. Sometimes on purpose, but more often due to a lack of overall game sense.
Ideally, a made up background would add something to a particular game world. That would help characters to fit the setting better. Of course, if you come up with a good generic one, please share.
The point being made (quite valid) is that Tasha's took us in a good direction, untethering stats from race and background, even talking about how the PCs are adventurers which are already examples of people that stand out in a crowd for being exceptional. Now they're tying certain stats to certain backgrounds? Make it make sense. They should have left all characters at a +2/+1 or +1/+1/+1 spread of their choice and any origin feat. Backgrounds could still have basic RP-relevant features like they used to until recently and starting equipment.
What background would you rather have? You can make up your own backgrounds.
Forcing us to make up our own defeats the purpose of using DND Beyond to make character creation quick and easy. It's nice that we have the option to bypass this ignorant new core rule, but it would be better if it weren't necessary.
Personally, I just continue to use the 2014 Backgrounds, and add an origin feat of my choice manually; whichever one seems to fit that character's nature and personality the best. As for stats, if you don't use 2024 Backgrounds (and instead stick with the ones available before this update), you can add your ability score bonuses wherever you please in DND Beyond, under 4. Abilities.
My grief with WotC is that they claimed to abolish the racial restrictions on ability scores to make the game more evolved and accepting to everyone, and instead saddled us with classism in lieu of racism. They've fixed nothing by this pointless change, only shifted the issue from restrictive races to restrictive backgrounds. Tasha's already fixed the racial ability stats four years ago by letting players put their ability score mods where they pleased, but instead of codifying that optional rule, they enforced a new one that is just as bad as the one they tried to fix.
Yeah I'm going to agree with this. The ability scores listed should be there as a suggestion not a restriction. The floating ASIs introduced in Tasha's was perfect. Those who wanted to limit them to the species or background would still do that and those that didn't want to could customise. This satisfied the requirements for everyone without any restriction. The 2024 rules on D&D Beyond implementing this as a restriction is a significant step backwards.
The "just make custom background" is not a real solution, just a bandaid, and currently homebrewing 2024 backgrounds is confusing because you can't put the ASI choice there presently, and if using a 2024 species and class, you basically don't get any option to input any ASI anywhere. The workaround is sheet customising but for new people this is confusing especially because even this support thread and changelog don't tell you that you can even do that.
The workaround is if usng a 2024 background and not agreeing to the restricted ASIs just leave blank. On the sheet itself click the Ability Score you would want and in the 'Other Modifier' box put in your 1 or 2 bonus there. Or, as mentioned correctly by Maveric28, use a 2014 Background, add the ASI under the Abilities Tab which will now let you, and you can add an Origin feat manually on the sheet (features > manage feats).
Rollback Post to RevisionRollBack
This is the test account of Cyb3rM1nd. Posting through this because my main account is locked out of forums due to a glitch.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
Maybe I'm missing something here, but I seem unable to select 2024 class backdrops for my characters. When I make one with an updated class, I get the corresponding backdrop, but if I then switch to something else, I don't see any way to change back.
Maybe I'm missing something here, but I seem unable to select 2024 class backdrops for my characters. When I make one with an updated class, I get the corresponding backdrop, but if I then switch to something else, I don't see any way to change back.
Nope, you're not missing anything. I've just personally confirmed that all the 2024 class backdrops are not selectable from the Character Backdrops listing which is accessible from the Character Sheet view by clicking the "Manage" button next to the character name. Call this either a bug or an "unimplemented feature" (a term from my days of working as a software engineer).
Rollback Post to RevisionRollBack
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming "Wow! What a Ride!" - Hunter S. Thompson
When life is bleak, all hope is lost, a wall is at your back, you always have one option left...attack! Attack! ATTACK! - Me
Are you honestly going to look at the new classes, see that some of the Tasha's features are baked in standard but not all, and say "oh, that must be an accident, they couldn't possibly have chosen not to use those features"?
The intent is clear by the design. Anyone who argues otherwise is just looking to argue, not actually paying attention to the game.
This is a very dishonest way to argue. Several subclasses are also missing, and the book itself quite clearly just says it only replaces older elements, it does not say that several options are gone.
What’s new in the 2024 Version?
This is the 2024 version of the fifth edition Player’s Handbook. If you’ve read the 2014 version, much of this book will feel familiar, since the fundamental rules of the game are the same. But the book contains many new or redesigned elements, and the versions of things in this book replace versions from older books.
The actual answer is that DNDBeyond doesn't support it, yet.
It is not DDB's goal to meet that expectation to attract those customers, unless attracting those customers is worth the effort put into attracting them. If it's literally 20 of you asking for it, that's not worth their while. They can focus on something 100 people asked for. The idea that someone is entitled to a change just because they asked for it is an egotistical fallacy.
I'll chip in and say I do want them to actually add full backwards compatibility as promised.
Backwards compability means anything that wasn't included in the PHB revision is still legal and accessible, and are valid choices by the PHBs own description: "But the book contains many new or redesigned elements, and the versions of things in this book replace versions from older books." - The book does not invalidate all of the existing options from Xanathar's and Tasha's, on the contrary. It specifically says it only updates the PHB. This is not a new edition. It is a revision, hence why DNDBeyond doesn't even list a lot of XGtE and TCoE options as Legacy: Because they are not.
You're also making an assumption of how many people want X over Y. I can promise you, we are a lot more than 20 people asking for the full backwards compatibility with al older books that wasn't updated/redesigned.
You're stuck on the number "20" instead of the economic concept I am attempting to explain to you. The actual number of you is irrelevant to this scenario, EXCEPT in regard to the potential acquisition/retention of customers it presents in relation to other items they can work on. There could be 1 million of you who want that. But if there 100 billion who want something else more, it makes more sense for them to serve the 100 billion before getting to the million. The payoff for the one million is insignificant compared to the 100 billion.
The real issue here, is we don't have any of those numbers. However, I do know Hasbro loves money, so if they thought there was significant money/acquisition/retention in doing what you are asking, there would be a distinct push to do that thing as soon as possible. You are free to believe different. I am not arguing the point with you any longer.
The issue isn't the number itself, it is that you assume those you disagree with is an insignificant minority. You could just as well be that minority.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The background comes specifically with the cleric version of the feat.
Noticed another issue:
You're stuck on the number "20" instead of the economic concept I am attempting to explain to you. The actual number of you is irrelevant to this scenario, EXCEPT in regard to the potential acquisition/retention of customers it presents in relation to other items they can work on. There could be 1 million of you who want that. But if there 100 billion who want something else more, it makes more sense for them to serve the 100 billion before getting to the million. The payoff for the one million is insignificant compared to the 100 billion.
The real issue here, is we don't have any of those numbers. However, I do know Hasbro loves money, so if they thought there was significant money/acquisition/retention in doing what you are asking, there would be a distinct push to do that thing as soon as possible. You are free to believe different. I am not arguing the point with you any longer.
The Channel Divinity feature for Paladin does not display the Divine Sense option on the character sheet. In fact, Channel Divinity does not seem to appear at all outside of the subclass features, so the explanation of how many uses it has is hard to find. Because of this, it also lacks any check boxes to track its uses in the character sheet.
There is also a weird glitch when viewing the "Manage Spells" sidebar where the Aid spell is listed as Always Prepared despite not actually being prepared. It also still has a "Learn" button underneath the "Always Prepared" statement, and clicking on it prepares the spell but doesn't remove the "Always Prepared" statement.
The Chef feat also does not display limited use tracking fields in the actions tab like the Tasha's version did. Additionally, when calculating the number of people eligible for the Refreshing Meal portion of the feat, the snippet reads "4 +3". If the snippet code used here was instead "4+proficiency#unsigned" then the actual total number would be legible.
Leomund's Tiny Hut and Detect Magic, as well as surely many other spells I haven't noticed yet, all lack the ritual tag that they should have.
How can you be sure? Is this posted somewhere officially or just your opinion?
Shillelagh spell.
When in the character sheet, clicking the dice to roll either the to Hit and Damage, or just the damage separately, it is adding both the Bludgeoning damage and the Force damage to the Total damage (it should be one or the other, but not both together). This looks impressive but is misleading.
Are you honestly going to look at the new classes, see that some of the Tasha's features are baked in standard but not all, and say "oh, that must be an accident, they couldn't possibly have chosen not to use those features"?
The intent is clear by the design. Anyone who argues otherwise is just looking to argue, not actually paying attention to the game.
So, Lessons of the First Ones Invocation now can select a feat, yet there are no updates notes on what has been fixed since 17 September.
Nope. Each of the new 2024 Backgrounds has one, and only one, specific origin feat attached to it. If you choose Acolyte, you get Magic Initiate: Cleric. That's it. That's what comes with that background; that particular feat and nothing else.
If you want Magic Initiate: Druid, you must select Guide as your background. If you want Magic Initiate: Wizard, you must select Sage as your background.
That's it. Those are your choices. The new backgrounds will shoehorn you specifically in one direction and one direction only. Personally, I hate them. In an effort to remove racism, WotC has instead opted to add classism to the game. A noble will inherently be smarter and more personable than a farmer, because that's the way the rules work now. Bravo, WotC! *slow sarcastic applause* Braaaaa-VO!
(Yeah, that particular change has made me cranky. Sorry if I offend.)
What background would you rather have? You can make up your own backgrounds.
Sear Undead seems to be broken on DND Beyond... under Actions, it's listed as an attack but it doesn't show the Saving Throw DC and it lists damage as only 1d8, instead of the correct 1d8 per Wisdom bonus modifier.
I "advanced search"ed this thread, and didn't find that anyone else listed this bug yet.
Forcing us to make up our own defeats the purpose of using DND Beyond to make character creation quick and easy. It's nice that we have the option to bypass this ignorant new core rule, but it would be better if it weren't necessary.
Personally, I just continue to use the 2014 Backgrounds, and add an origin feat of my choice manually; whichever one seems to fit that character's nature and personality the best. As for stats, if you don't use 2024 Backgrounds (and instead stick with the ones available before this update), you can add your ability score bonuses wherever you please in DND Beyond, under 4. Abilities.
My grief with WotC is that they claimed to abolish the racial restrictions on ability scores to make the game more evolved and accepting to everyone, and instead saddled us with classism in lieu of racism. They've fixed nothing by this pointless change, only shifted the issue from restrictive races to restrictive backgrounds. Tasha's already fixed the racial ability stats four years ago by letting players put their ability score mods where they pleased, but instead of codifying that optional rule, they enforced a new one that is just as bad as the one they tried to fix.
Since Tasha's changed the attribute bonuses, your species become pretty much irrelevant for that. Given that, moving the attribute modifier to Backgrounds made sense.
I am sure they will add more backgrounds over time, but if there is something that you come up with that you want to use now, I would do that. It is really easy to make up custom stuff. The downside is that people often make up stuff that is way OP. Sometimes on purpose, but more often due to a lack of overall game sense.
Ideally, a made up background would add something to a particular game world. That would help characters to fit the setting better. Of course, if you come up with a good generic one, please share.
"number of d? equal to ? score mod" is not a function that the D&D Beyond system is designed to support.
Sear Undead does not have a saving throw - it only applies to the undead that fail Turn Undead which has a saving throw - the DC is found under Spells. The main point of the section you're looking at is to see Attacks and Turn Undead is not an attack. The purpose of the action is for the damage but is limited by an unsupported feature.
Now, having said that, I do agree it is poorly implemented even when factoring the unsupported damage function. It would be simple enough for the system to add the Saving Throw DC in there for Turn Undead for easier reference.
Hopefully this is something they will get around to.
In the meantime I would recommend clicking the Sear Undead action, customise it and uncheck the Display As Attack to remove the utterly pointless action from the list. I would then create a custom action to input the damage for Sear Undead and another one for Turn Undead for showing the Save DC. This way you have easy and clear reference to both features. If anyone would like me to make a video showing how to do this please let me know and I will see if I can make one.
This is the test account of Cyb3rM1nd. Posting through this because my main account is locked out of forums due to a glitch.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
The point being made (quite valid) is that Tasha's took us in a good direction, untethering stats from race and background, even talking about how the PCs are adventurers which are already examples of people that stand out in a crowd for being exceptional. Now they're tying certain stats to certain backgrounds? Make it make sense. They should have left all characters at a +2/+1 or +1/+1/+1 spread of their choice and any origin feat. Backgrounds could still have basic RP-relevant features like they used to until recently and starting equipment.
Yeah I'm going to agree with this. The ability scores listed should be there as a suggestion not a restriction. The floating ASIs introduced in Tasha's was perfect. Those who wanted to limit them to the species or background would still do that and those that didn't want to could customise. This satisfied the requirements for everyone without any restriction. The 2024 rules on D&D Beyond implementing this as a restriction is a significant step backwards.
The "just make custom background" is not a real solution, just a bandaid, and currently homebrewing 2024 backgrounds is confusing because you can't put the ASI choice there presently, and if using a 2024 species and class, you basically don't get any option to input any ASI anywhere. The workaround is sheet customising but for new people this is confusing especially because even this support thread and changelog don't tell you that you can even do that.
The workaround is if usng a 2024 background and not agreeing to the restricted ASIs just leave blank. On the sheet itself click the Ability Score you would want and in the 'Other Modifier' box put in your 1 or 2 bonus there. Or, as mentioned correctly by Maveric28, use a 2014 Background, add the ASI under the Abilities Tab which will now let you, and you can add an Origin feat manually on the sheet (features > manage feats).
This is the test account of Cyb3rM1nd. Posting through this because my main account is locked out of forums due to a glitch.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
Maybe I'm missing something here, but I seem unable to select 2024 class backdrops for my characters. When I make one with an updated class, I get the corresponding backdrop, but if I then switch to something else, I don't see any way to change back.
Nope, you're not missing anything. I've just personally confirmed that all the 2024 class backdrops are not selectable from the Character Backdrops listing which is accessible from the Character Sheet view by clicking the "Manage" button next to the character name. Call this either a bug or an "unimplemented feature" (a term from my days of working as a software engineer).
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming "Wow! What a Ride!"
- Hunter S. Thompson
When life is bleak, all hope is lost, a wall is at your back, you always have one option left...attack! Attack! ATTACK!
- Me
This is a very dishonest way to argue. Several subclasses are also missing, and the book itself quite clearly just says it only replaces older elements, it does not say that several options are gone.
The actual answer is that DNDBeyond doesn't support it, yet.
The issue isn't the number itself, it is that you assume those you disagree with is an insignificant minority. You could just as well be that minority.