This is going to sound cliché, but I'm just more disappointed in DNDBeyond than angry. I'm trying to practice patience. I'm a computer science major in college, and I can totally understand the difficulty in major system changes. But they are just practicing horrible business practices (poor communication chief among them). If I knew all that I do now about the error's with Tasha's when I purchased it I would not have bought it. I was even motivated to look at class action lawsuit stuff for a while, considering they are simply not fully providing the service people are paying for. But frankly, I don't want to see DNDB sued (at least not yet) (and frankly, it probably wouldn't even qualify, I'm not savvy in that kind of thing). Even if these bugs are eventually fixed, that will not change the fact that consumers had to spend a year (or even much longer in the case of the divine soul sorcerer) without being given what they paid for. It is just sad situation overall. I don't think I'll be purchasing from DNDB anymore unless some serious changes are made (and hopefully, a public apology is given).
Sorry to go full keyboard warrior about this, I just wanted to put my feelings down.
Not posting very often, but have to give a bump that Genie’s Wrath is apparently still not implemented in the character sheets. (Genie Warlock patron lvl1 feature)
Is there still work being done on this?
I also still see this issue. At one point the text of the feature was listed under the Bottled Respite feature, but now the text does not show at all.
So a reminder 11/4/19 was when the UA that most of these features were released to the public. We were told for a year that a massive re-write of the underlying systems would be needed to support those sort of changes, and that instead of putting in the UA (which they could have hard coded) they were going to spend the time to fix the system as a whole to be ready for when those changes went to a live book.
So they spent a year not really giving updates, but we all had faith that they were acting in good faith and that they would be relatively ready for Tasha's. Then Tasha's dropped and nearly nothing was implemented at first. And for a few months we saw update after update of features being implemented. Bugs being fixed. And then half the company seemed to abandon ship in Feb with Adam. Already poor communication vanished to nothing. I just went staff post to staff post in this entire thread, and since Adam left, there has been about 3 bug fixes. In the last month we have had 1 staff post, and since September its been like 3 or 4. Since June maybe 6.
I am not saying the ship is going down, nor the sky is falling. But I am saying that this is a concerning pattern. There seems to be no real transparency as to what the hold up is, nor why they just aren't band aiding features in so we can use the tool as intended til they finish their re-write.
I mean add Sidekick classes to player classes, and let us just make characters as our sidekicks (we could even put in stats and home brew racial traits for when we sidekick flame skulls and the like). If you want to implement clockwork/divine/aberrent options, in the class feature, it can offer you an option where you tell it how many spells you have traded, and it removes that number from the total you can know, and gives drop downs of spells that qualify as "automatically known spells." If you know too many, it could even throw up an error to let you know you cant move on til you remove some (you could even have a button to clear all so you can try again if needed).
I know a lot is likely going on behind the scenes, but 2 years is a hell of a long time in the world of software development. And when you have a passing of the torch, or changing of the guard, that's not a good time to suddenly have communication black out. It just doesn't look good.
At this point my question is, how far along is the complete system re-write? How many people are dedicated to getting that up and running? Optics... Transparency... these are things that make delays in releases become manageable. It would be nice to get some clarity on why something that has been 2 years in the making appears to have 0 progress. Do a little PR (once a month maybe) so that we are reassured that things are moving forward. Because it really feels like it isn't.
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
I would call this a bug. Tasha's is a setting-neutral rules expansion, not a Magic: The Gathering supplement.
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
I would call this a bug. Tasha's is a setting-neutral rules expansion, not a Magic: The Gathering supplement.
Yep. They removed the need to have "Eberron content" enabled for the Artificer when Tasha's was released; the inconsistency between that and the MtG subclasses is inexplicable.
And if I have Sword Coast Adventurer's Guide downloaded in the app, it shows only the Sword Coast version of the Bladesinging Wizard subclass, not the Tasha's version, which is most noticeable in the different versions of the Extra Attack feature.
I have to keep Sword Coast Adventurers Guide deleted in order to correctly see the current Bladesinging subclass in the app.
Sword Coast has a restriction for Elves only, and its extra Attack rule is:
Extra Attack 6th-level Bladesinging feature
Starting at 6th level you can attack twice, instead of once, whenever you take the Attack action on your turn.
Tasha's Extra Attack rule is:
Extra Attack 6th-level Bladesinging feature
You can attack twice, instead of once, whenever you take the Attack action on your turn. Moreover, you can cast one of your cantrips in place of one of those attacks.
DnD Beyond replaces the rules on the website, if that's where you were looking. You have to view the book in the app or under the "Listings" feature.
Sword Coast has a restriction for Elves only, and its extra Attack rule is:
Extra Attack 6th-level Bladesinging feature
Starting at 6th level you can attack twice, instead of once, whenever you take the Attack action on your turn.
Tasha's Extra Attack rule is:
Extra Attack 6th-level Bladesinging feature
You can attack twice, instead of once, whenever you take the Attack action on your turn. Moreover, you can cast one of your cantrips in place of one of those attacks.
DnD Beyond replaces the rules on the website, if that's where you were looking. You have to view the book in the app or under the "Listings" feature.
SCAG was errata'd after Tasha's got published to match with the republished version. The website version is correct, but as you noted, the SCAG on the App is still the old version.
So yes, can confirm, the SCAG on the App needs to be corrected.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's great that clockwork soul and Aberrant mind sorcerer get the extra spells but it would be really great if you could change them out for the optional spells from abjuration/transmutation spells from wizard, warlock and sorcerer. Without that option, the two subclasses are much harder to play. How many times have I explained why I've customized alarm to be something else and of course when I cast it the customization part doesn't even show up. I'm casting mage armor but it comes up as alarm. *Cries*
Rollback Post to RevisionRollBack
Kato
Life gives you lemons, make lemonade, life gives you a sword? You make corpses of your enemies, sorcery is a good sword life has given you. (Stolen from friend)
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
I would call this a bug. Tasha's is a setting-neutral rules expansion, not a Magic: The Gathering supplement.
Yep. They removed the need to have "Eberron content" enabled for the Artificer when Tasha's was released; the inconsistency between that and the MtG subclasses is inexplicable.
This is because the artificer is the exception to source categorisation, rather than the rule. All other content is still categorised by first published source and as such Oath of Glory requiring MtG content enabled is not a bug, it is the content management system behaving as intended.
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
I would call this a bug. Tasha's is a setting-neutral rules expansion, not a Magic: The Gathering supplement.
Yep. They removed the need to have "Eberron content" enabled for the Artificer when Tasha's was released; the inconsistency between that and the MtG subclasses is inexplicable.
This is because the artificer is the exception to source categorisation, rather than the rule. All other content is still categorised by first published source and as such Oath of Glory requiring MtG content enabled is not a bug, it is the content management system behaving as intended.
That’s not an explanation. What DDB have said in the past is that because the Artificer is in Tasha’s it’s now “core D&D,” which is why it’s no longer gated behind the toggle. These subclasses appear in Tasha’s so they’re also now “core D&D.”
You can’t justify an “exception” with reasoning that is equally true for other things you refuse to make that same exception for and expect people to take you seriously. The number of people coming into this thread asking why they can’t use the Oath of Glory or whatever that they paid for should tell you that this decision is very user-unfriendly, and given that no one has ever actually explained it, I stand by my statement that it’s inexplicable.
Is anyone having this issue? My DM has all the core books, including Tasha's, but the only subclass option for barbarian that pops up is beserker. I tried in a different campaign with another DM who has a full library, and same results. Thanks!
Is anyone having this issue? My DM has all the core books, including Tasha's, but the only subclass option for barbarian that pops up is beserker. I tried in a different campaign with another DM who has a full library, and same results. Thanks!
Berserker is the only subclass available for Barbarian in the Basic Rules. Do the DMs have Content Sharing enabled for their campaigns?
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's been a year and we still can't trade out spells on dnd beyond with the New sorcerers subclasses.How has this not been implemented yet?
No, it has not been implemented yet. Keep in mind this is also still true for Divine Soul Sorcerer, which has been out much longer. Apparently it’s a harder fix on the back end than it appears to be from our vantage point.
This is going to sound cliché, but I'm just more disappointed in DNDBeyond than angry. I'm trying to practice patience. I'm a computer science major in college, and I can totally understand the difficulty in major system changes. But they are just practicing horrible business practices (poor communication chief among them). If I knew all that I do now about the error's with Tasha's when I purchased it I would not have bought it. I was even motivated to look at class action lawsuit stuff for a while, considering they are simply not fully providing the service people are paying for. But frankly, I don't want to see DNDB sued (at least not yet) (and frankly, it probably wouldn't even qualify, I'm not savvy in that kind of thing). Even if these bugs are eventually fixed, that will not change the fact that consumers had to spend a year (or even much longer in the case of the divine soul sorcerer) without being given what they paid for. It is just sad situation overall. I don't think I'll be purchasing from DNDB anymore unless some serious changes are made (and hopefully, a public apology is given).
Sorry to go full keyboard warrior about this, I just wanted to put my feelings down.
What am I supposed to do with a signature?
Egg
I also still see this issue. At one point the text of the feature was listed under the Bottled Respite feature, but now the text does not show at all.
So a reminder 11/4/19 was when the UA that most of these features were released to the public. We were told for a year that a massive re-write of the underlying systems would be needed to support those sort of changes, and that instead of putting in the UA (which they could have hard coded) they were going to spend the time to fix the system as a whole to be ready for when those changes went to a live book.
So they spent a year not really giving updates, but we all had faith that they were acting in good faith and that they would be relatively ready for Tasha's. Then Tasha's dropped and nearly nothing was implemented at first. And for a few months we saw update after update of features being implemented. Bugs being fixed. And then half the company seemed to abandon ship in Feb with Adam. Already poor communication vanished to nothing. I just went staff post to staff post in this entire thread, and since Adam left, there has been about 3 bug fixes. In the last month we have had 1 staff post, and since September its been like 3 or 4. Since June maybe 6.
I am not saying the ship is going down, nor the sky is falling. But I am saying that this is a concerning pattern. There seems to be no real transparency as to what the hold up is, nor why they just aren't band aiding features in so we can use the tool as intended til they finish their re-write.
I mean add Sidekick classes to player classes, and let us just make characters as our sidekicks (we could even put in stats and home brew racial traits for when we sidekick flame skulls and the like). If you want to implement clockwork/divine/aberrent options, in the class feature, it can offer you an option where you tell it how many spells you have traded, and it removes that number from the total you can know, and gives drop downs of spells that qualify as "automatically known spells." If you know too many, it could even throw up an error to let you know you cant move on til you remove some (you could even have a button to clear all so you can try again if needed).
I know a lot is likely going on behind the scenes, but 2 years is a hell of a long time in the world of software development. And when you have a passing of the torch, or changing of the guard, that's not a good time to suddenly have communication black out. It just doesn't look good.
At this point my question is, how far along is the complete system re-write? How many people are dedicated to getting that up and running? Optics... Transparency... these are things that make delays in releases become manageable. It would be nice to get some clarity on why something that has been 2 years in the making appears to have 0 progress. Do a little PR (once a month maybe) so that we are reassured that things are moving forward. Because it really feels like it isn't.
Oath of valor paladin isn't anywhere to be selected
T Flores EMT-P
Oath of glory isn't anywhere to be selected 0.0
T Flores EMT-P
Oath of valor is not an official paladin subclass
You need to have Magic: the Gathering Content enabled. The subclass was first printed in Mythic Odyssey of Theros, so is classes under Magic: the Gathering content.
Find my D&D Beyond articles here
I would call this a bug. Tasha's is a setting-neutral rules expansion, not a Magic: The Gathering supplement.
Yep. They removed the need to have "Eberron content" enabled for the Artificer when Tasha's was released; the inconsistency between that and the MtG subclasses is inexplicable.
And if I have Sword Coast Adventurer's Guide downloaded in the app, it shows only the Sword Coast version of the Bladesinging Wizard subclass, not the Tasha's version, which is most noticeable in the different versions of the Extra Attack feature.
I have to keep Sword Coast Adventurers Guide deleted in order to correctly see the current Bladesinging subclass in the app.
Sword Coast has a restriction for Elves only, and its extra Attack rule is:
Extra Attack
6th-level Bladesinging feature
Starting at 6th level you can attack twice, instead of once, whenever you take the Attack action on your turn.
Tasha's Extra Attack rule is:
Extra Attack
6th-level Bladesinging feature
You can attack twice, instead of once, whenever you take the Attack action on your turn. Moreover, you can cast one of your cantrips in place of one of those attacks.
DnD Beyond replaces the rules on the website, if that's where you were looking. You have to view the book in the app or under the "Listings" feature.
SCAG was errata'd after Tasha's got published to match with the republished version. The website version is correct, but as you noted, the SCAG on the App is still the old version.
So yes, can confirm, the SCAG on the App needs to be corrected.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's great that clockwork soul and Aberrant mind sorcerer get the extra spells but it would be really great if you could change them out for the optional spells from abjuration/transmutation spells from wizard, warlock and sorcerer. Without that option, the two subclasses are much harder to play. How many times have I explained why I've customized alarm to be something else and of course when I cast it the customization part doesn't even show up. I'm casting mage armor but it comes up as alarm. *Cries*
Kato
Life gives you lemons, make lemonade, life gives you a sword? You make corpses of your enemies, sorcery is a good sword life has given you. (Stolen from friend)
This is because the artificer is the exception to source categorisation, rather than the rule. All other content is still categorised by first published source and as such Oath of Glory requiring MtG content enabled is not a bug, it is the content management system behaving as intended.
Find my D&D Beyond articles here
That's ridiculous. If that's true, then their intent is bad.
That’s not an explanation. What DDB have said in the past is that because the Artificer is in Tasha’s it’s now “core D&D,” which is why it’s no longer gated behind the toggle. These subclasses appear in Tasha’s so they’re also now “core D&D.”
You can’t justify an “exception” with reasoning that is equally true for other things you refuse to make that same exception for and expect people to take you seriously. The number of people coming into this thread asking why they can’t use the Oath of Glory or whatever that they paid for should tell you that this decision is very user-unfriendly, and given that no one has ever actually explained it, I stand by my statement that it’s inexplicable.
Is anyone having this issue? My DM has all the core books, including Tasha's, but the only subclass option for barbarian that pops up is beserker. I tried in a different campaign with another DM who has a full library, and same results. Thanks!
Berserker is the only subclass available for Barbarian in the Basic Rules. Do the DMs have Content Sharing enabled for their campaigns?
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's been a year and we still can't trade out spells on dnd beyond with the New sorcerers subclasses.How has this not been implemented yet?
No, it has not been implemented yet. Keep in mind this is also still true for Divine Soul Sorcerer, which has been out much longer. Apparently it’s a harder fix on the back end than it appears to be from our vantage point.
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
TBH I don't believe this at all feel more like laziness.