Anybody who's still curious about this, the team just announced that they will no longer be supporting Unearthed Arcana content so they can focus on resolving existing issues like this one. So hopefully that speeds up our timeline a bit.
The bug has still not been fixed. If your class has a class feature that give you a list of spell that are known and doesn’t count against the number of spells you know for that class. And it also, let you change out that list of spell for other spells. The Sorcerer; Divine Soul, Divine magic or the Aberrent Mind, Psionic Spell. D&D Beyond will not let you change those spell that you get from those abilities.
I can't believe it, but this bug is now 4.5 YEARS OLD. It is unlikely that the first person to look at solving this still works at the company.
It also applies to the Aberrant Mind Sorcerer subclass ability which has its own thread about the same issue.
The Divine Soul Sorcerer was first published in Xanathar's Guide to Everything, which was published in late November 2017. So, the bug isn't quite yet 4 years old. (For what it's worth.)
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
I can't believe it, but this bug is now 4.5 YEARS OLD. It is unlikely that the first person to look at solving this still works at the company.
It also applies to the Aberrant Mind Sorcerer subclass ability which has its own thread about the same issue.
The Divine Soul Sorcerer was first published in Xanathar's Guide to Everything, which was published in late November 2017. So, the bug isn't quite yet 4 years old. (For what it's worth.)
I see, you are correct. I would say that it's my bad, but I think we all know what has done the bad thing here.
The Devs are working it, which has been confirmed. This will be resolved when they've overhauled the class features system - which they have confirmed is being worked on. No amount of "is it fixed yet" posts will change priority as that is factored by a whole host of other things.
Without you even posting, they will already be aware of the desire for this - which is why they are already working on it. The speed of implementation has nothing to do with post count.
Nagging somebody to do something they are already doing is more inclined to decrease productivity, if anything.
Everyone could have stopped posting years ago - and you'll end up getting it at the same time regardless.
Seriously why do people post "still not fixed"?
Wouldn't it be better to just edit subclass and swap manually - something even a newbie can do in like 3 minutes - and just move the fluff on? Seems a more productive use of your time.
When it is implemented, rejoice, but until then just do it manually. It's the tiniest of inconveniences and still considerably superior to pen & paper.
I don't understand, at all. O.o
Rollback Post to RevisionRollBack
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.
Why are you attacking users for continuing to show interest in a fix to an issue with a core book class?
It seems to me that you are implying that users are stupid for not having knowledge of development priorities. Which after more than 4 years of promised fixes clearly this issue has not made it high enough on to any priority list to be fixed and published to users.
Can you show me a link to when they started on the fix, what phase of work or testing the bug is in, or what its timetable for release is?
It also seems to me that you are Implying that users are stupid for not having the speed and understanding to use the homebrew system to hack in their own fix for an unresolved issue that has been outstanding for years. Many, and my guess is most, users do not use this platform for its homebrew capabilities, nor do they have a DM who wants to spend hours to figure out how to modify something as complex as a subclass and then have to test that their changes did not break anything or cause unintended bugs in their players character sheets. I highly disagree that any newbie can (or would want to) home brew a subclass "in like 3 minutes".
Yes there is a script to follow to create homebrew workaround for this, but forcing players to spend hours hacking through or searching for workarounds is no excuse for a bugs continued existence.
Homebrew is very exacting, buggy, does not update in a timely fashion and in many cases is not allowed. We are asking for a solution that works for everyone not just homebrew power users.
It seems to me that you are implying that users are stupid for not having knowledge of development priorities.
Nothing about my post implies such a thing. This is your inference not my implication. Are you projecting some insecurity here? I don't understand your inference at all. I don't imply statements of stupidity - if I think you were stupid, I would state so. I did not, so I do not.
Which after more than 4 years of promised fixes clearly this issue has not made it high enough on to any priority list to be fixed and published to users.
It's been less than 4 years. As was explained in multiple dev updates and posts they made regarding a previous fix that took years (life cleric features) implementing a fix is not as simple as many might assume. They have realised a failure in their base framework which needs to be adjusted. This is priority because all the other requested implementations will become much easier and possible. However, editing something that affects literally everything is a very delicate and time-consuming processing. Edit one thing, and something else gets affected. So the Class Features system they are working on will take time.
It's easy to say "we want this, look at how many, it must be high priority" - but in many cases this isn't how priority works. Prioritising things must also factor the difficulty of the task, how that task affects other planned things for the future, and juggled with other responsibilities like making new content available within the deadlines given to them. The rate that new content is being published by WotC takes a massive amount of time and effort to introduce into their sheet, searches, crosslinking and more. These must be prioritised - partially from contractual obligations but also with marketing as having your release days, or even weeks, behind your other competitors is going to seriously screw over your customer base and drive sales to the competitors.
And you then have to factor manpower because it isn't like you just have an army's worth of devs at your disposal - it's invariably just a few guys working hard.
I do appreciate not everyone is aware of how prioritisation works but it has already been proven numerous times that post count in a thread doesn't adjust the prioritisation at all. Most devs don't even look at the forum at all. One or two do, but not often.
Let's put it another way,
If you were making something and working as fast as you possibly can while trying to provide something high quality, that will have least amount of imperfections, and without the limits of the company requirements and other such. Point is, you're doing all you possibly can. Now imagine somebody coming to you and saying "work faster". There's only going to be 3 possible effects this is going to have.
1 - You're already at your best, so you can't do as requested. You just keep ploughing on and ignore the nagging. 2 - You try to do better but only end up stressing yourself, become unhealthy, and end up slower. 3 - You are magically gifted supernatural power to break beyond limits and provide the product faster.
Since we live in a real world that only realistically leaves 1 or 2. Neither results in anything beneficial.
I thought that this was obvious, really. But perhaps I was mistaken?
Can you show me a link to when they started on the fix, what phase of work or testing the bug is in, or what its timetable for release is?
They have discussed they are working on it on this thread and in their dev updates. Multiples times in both. I don't need to provide links to either: they're already on the page you're viewing because you're already in the thread and the dev updates can be accessed using the above menu. Go find out yourself, the same as everyone.
As for "phase of work" or "timetable" these are not provided. Phase is simply "we're working on it" along with everything else they have to. Timetables are a bad idea because of how insanely complicated the Class Features Overhaul is and it is better to say "in progress" than give an estimated date they may end up failing to meet due to the huge amount of possible unforeseen circumstances.
They could explain the complexity - but most aren't going to understand even if they did and that's a lot of time to explain for very little point when they could instead be working on the issues. They already tried explaining before with the cleric issue - and so many didn't care and here we are with a lot of people still going "is it done yet". So, clearly taking the time to stop and explain is pointless.
Given what happened with that, their responses so far on this, its very clear they will be done, when they're done, and no amount of "is it fixed yet" will change that.
It also seems to me that you are Implying that users are stupid for not having the speed and understanding to use the homebrew system to hack in their own fix for an unresolved issue that has been outstanding for years.
Again with the seeming/implying thing. This is a nasty habit you have. It's incredibly antagonistic. Please focus on the words I use, not the ones you make up. It's insulting.
-
The homebrew workaround isn't difficult.
Copy Subclass
Change Spell
Save
And you're done. If you are used to the homebrew interface it can take about 40 seconds. I can't comment on how easy it would be for me as a newbie as when I first started using D&D beyond I had a lot of programming and web development knowledge, plus in my 30s. I have, however, played with somebody who edited a wizard subclass to swap out the minor illusion cantrip to a different one - something that requires the same process - in under 2 minutes. First day using D&D beyond. They were 15.
The homebrew interface is daunting and clunky - but intuitive enough.
But perhaps my experience was a one-off and I'm blinded by that, if so I apologise. When I have more time, perhaps I will make a guide to show how to swap the spells manually. I'm pretty sure somebody has already done that somewhere, but I can't find it. If I remember I will make the guide later.
Anyway, my point is ultimately: "posting 'not fixed yet' doesn't do anything at all, why do it?" out of curiosity and confusion.
Rollback Post to RevisionRollBack
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.
No amount of "is it fixed yet" posts will change priority as that is factored by a whole host of other things.
Without you even posting, they will already be aware of the desire for this - which is why they are already working on it. The speed of implementation has nothing to do with post count.
Nagging somebody to do something they are already doing is more inclined to decrease productivity, if anything.
Everyone could have stopped posting years ago - and you'll end up getting it at the same time regardless.
As a professional software developer, this is utter nonsense. Having paying customers raising the same issue and adding to the tracker count absolutely has an effect on prioritization. If something is so minor no actual customer complains, then it might stagnate in the backlog for years. You are correct that often times an overhaul is required and preferable to some hacky fix that will just cause other regressions.
No amount of "is it fixed yet" posts will change priority as that is factored by a whole host of other things.
Without you even posting, they will already be aware of the desire for this - which is why they are already working on it. The speed of implementation has nothing to do with post count.
Nagging somebody to do something they are already doing is more inclined to decrease productivity, if anything.
Everyone could have stopped posting years ago - and you'll end up getting it at the same time regardless.
As a professional software developer, this is utter nonsense. Having paying customers raising the same issue and adding to the tracker count absolutely has an effect on prioritization. If something is so minor no actual customer complains, then it might stagnate in the backlog for years. You are correct that often times an overhaul is required and preferable to some hacky fix that will just cause other regressions.
Except this forum is not used as a tracker count.
Rollback Post to RevisionRollBack
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.
No amount of "is it fixed yet" posts will change priority as that is factored by a whole host of other things.
Without you even posting, they will already be aware of the desire for this - which is why they are already working on it. The speed of implementation has nothing to do with post count.
Nagging somebody to do something they are already doing is more inclined to decrease productivity, if anything.
Everyone could have stopped posting years ago - and you'll end up getting it at the same time regardless.
As a professional software developer, this is utter nonsense. Having paying customers raising the same issue and adding to the tracker count absolutely has an effect on prioritization. If something is so minor no actual customer complains, then it might stagnate in the backlog for years. You are correct that often times an overhaul is required and preferable to some hacky fix that will just cause other regressions.
Except this forum is not used as a tracker count.
If they choose not to acknowledge or to otherwise engage with their customers making a very reasonable and very long lasting issue, that is a choice.
Basically, every time someone posts here, it's a chance for Dndbeyond to do the smart thing, the right thing, and actually communicate about the issue.
And every time that they choose not to, they follow the soulless, corporate approach that treats their customers and inhuman lumps and fears openness integrity, or really even basic respect.
Thing is, they have communicated. They do advise you they are working on it. They explain and advise in the multiple forum threads and in their dev updates. Making them stop what they're doing to come into the forums and repeat themselves over and over isn't helping them or you or anybody - it's time they could be working, instead.
Rollback Post to RevisionRollBack
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.
For anyone wondering how to get this on your character sheet as a workaround, while you wait for D&D Beyond to implement this, I made a video showing how. It's bad quality with a really shitty mic - this is not something I normally do. But who knows, maybe it will still help somebody.
Rollback Post to RevisionRollBack
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.
In February, I'll have been playing a Divine Soul Sorcerer for 4 years. Still hoping for a fix to this issue.
Thanks for the workaround video. I actually just customized Cure Wounds by renaming it to Healing Word and adding 60' and 1d4+4 to the description instead.
It would be nice to be able to update this in the "Class Features" section where you already indicate your alignment anyway.
As a workaround for this I find it most efficacious to add a 6th option to the Divine Soul’s Divine Magic feature (so it always works correctly RAW from 1st level to 20th):
Anybody who's still curious about this, the team just announced that they will no longer be supporting Unearthed Arcana content so they can focus on resolving existing issues like this one. So hopefully that speeds up our timeline a bit.
The bug has still not been fixed. If your class has a class feature that give you a list of spell that are known and doesn’t count against the number of spells you know for that class. And it also, let you change out that list of spell for other spells. The Sorcerer; Divine Soul, Divine magic or the Aberrent Mind, Psionic Spell. D&D Beyond will not let you change those spell that you get from those abilities.
Well it's been what, almost four years for this bug?
We have a joke in the industry about "bugs which are old enough to vote".
Maybe this one could be fixed before it gets to grade school?
I can't believe it, but this bug is now 4.5 YEARS OLD. It is unlikely that the first person to look at solving this still works at the company.
It also applies to the Aberrant Mind Sorcerer subclass ability which has its own thread about the same issue.
The Divine Soul Sorcerer was first published in Xanathar's Guide to Everything, which was published in late November 2017. So, the bug isn't quite yet 4 years old. (For what it's worth.)
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
I see, you are correct.
I see, you are correct. I would say that it's my bad, but I think we all know what has done the bad thing here.
So are you ever going to fix this?
I think the 2 year timer is reset every time someone asks.
4 years later…
still not fixed.
This looks to be a general problem with any "extra" spells granted by class any features... and is still not fixed.
What do people hope for by going "not fixed yet"?
The Devs are working it, which has been confirmed. This will be resolved when they've overhauled the class features system - which they have confirmed is being worked on. No amount of "is it fixed yet" posts will change priority as that is factored by a whole host of other things.
Without you even posting, they will already be aware of the desire for this - which is why they are already working on it. The speed of implementation has nothing to do with post count.
Nagging somebody to do something they are already doing is more inclined to decrease productivity, if anything.
Everyone could have stopped posting years ago - and you'll end up getting it at the same time regardless.
Seriously why do people post "still not fixed"?
Wouldn't it be better to just edit subclass and swap manually - something even a newbie can do in like 3 minutes - and just move the fluff on? Seems a more productive use of your time.
When it is implemented, rejoice, but until then just do it manually. It's the tiniest of inconveniences and still considerably superior to pen & paper.
I don't understand, at all. O.o
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.
Its simple, the squeaky wheel gets the grease.
Why are you attacking users for continuing to show interest in a fix to an issue with a core book class?
It seems to me that you are implying that users are stupid for not having knowledge of development priorities.
Which after more than 4 years of promised fixes clearly this issue has not made it high enough on to any priority list to be fixed and published to users.
Can you show me a link to when they started on the fix, what phase of work or testing the bug is in, or what its timetable for release is?
It also seems to me that you are Implying that users are stupid for not having the speed and understanding to use the homebrew system to hack in their own fix for an unresolved issue that has been outstanding for years. Many, and my guess is most, users do not use this platform for its homebrew capabilities, nor do they have a DM who wants to spend hours to figure out how to modify something as complex as a subclass and then have to test that their changes did not break anything or cause unintended bugs in their players character sheets. I highly disagree that any newbie can (or would want to) home brew a subclass "in like 3 minutes".
Yes there is a script to follow to create homebrew workaround for this, but forcing players to spend hours hacking through or searching for workarounds is no excuse for a bugs continued existence.
Homebrew is very exacting, buggy, does not update in a timely fashion and in many cases is not allowed.
We are asking for a solution that works for everyone not just homebrew power users.
Nothing about my post is an attack. I asked a question out of confusion and curiosity.
Nothing about my post implies such a thing. This is your inference not my implication. Are you projecting some insecurity here? I don't understand your inference at all. I don't imply statements of stupidity - if I think you were stupid, I would state so. I did not, so I do not.
It's been less than 4 years. As was explained in multiple dev updates and posts they made regarding a previous fix that took years (life cleric features) implementing a fix is not as simple as many might assume. They have realised a failure in their base framework which needs to be adjusted. This is priority because all the other requested implementations will become much easier and possible. However, editing something that affects literally everything is a very delicate and time-consuming processing. Edit one thing, and something else gets affected. So the Class Features system they are working on will take time.
It's easy to say "we want this, look at how many, it must be high priority" - but in many cases this isn't how priority works. Prioritising things must also factor the difficulty of the task, how that task affects other planned things for the future, and juggled with other responsibilities like making new content available within the deadlines given to them. The rate that new content is being published by WotC takes a massive amount of time and effort to introduce into their sheet, searches, crosslinking and more. These must be prioritised - partially from contractual obligations but also with marketing as having your release days, or even weeks, behind your other competitors is going to seriously screw over your customer base and drive sales to the competitors.
And you then have to factor manpower because it isn't like you just have an army's worth of devs at your disposal - it's invariably just a few guys working hard.
I do appreciate not everyone is aware of how prioritisation works but it has already been proven numerous times that post count in a thread doesn't adjust the prioritisation at all. Most devs don't even look at the forum at all. One or two do, but not often.
Let's put it another way,
If you were making something and working as fast as you possibly can while trying to provide something high quality, that will have least amount of imperfections, and without the limits of the company requirements and other such. Point is, you're doing all you possibly can. Now imagine somebody coming to you and saying "work faster". There's only going to be 3 possible effects this is going to have.
1 - You're already at your best, so you can't do as requested. You just keep ploughing on and ignore the nagging.
2 - You try to do better but only end up stressing yourself, become unhealthy, and end up slower.
3 - You are magically gifted supernatural power to break beyond limits and provide the product faster.
Since we live in a real world that only realistically leaves 1 or 2. Neither results in anything beneficial.
I thought that this was obvious, really. But perhaps I was mistaken?
They have discussed they are working on it on this thread and in their dev updates. Multiples times in both. I don't need to provide links to either: they're already on the page you're viewing because you're already in the thread and the dev updates can be accessed using the above menu. Go find out yourself, the same as everyone.
As for "phase of work" or "timetable" these are not provided. Phase is simply "we're working on it" along with everything else they have to. Timetables are a bad idea because of how insanely complicated the Class Features Overhaul is and it is better to say "in progress" than give an estimated date they may end up failing to meet due to the huge amount of possible unforeseen circumstances.
They could explain the complexity - but most aren't going to understand even if they did and that's a lot of time to explain for very little point when they could instead be working on the issues. They already tried explaining before with the cleric issue - and so many didn't care and here we are with a lot of people still going "is it done yet". So, clearly taking the time to stop and explain is pointless.
Given what happened with that, their responses so far on this, its very clear they will be done, when they're done, and no amount of "is it fixed yet" will change that.
Again with the seeming/implying thing. This is a nasty habit you have. It's incredibly antagonistic. Please focus on the words I use, not the ones you make up. It's insulting.
-
The homebrew workaround isn't difficult.
Copy Subclass
Change Spell
Save
And you're done. If you are used to the homebrew interface it can take about 40 seconds. I can't comment on how easy it would be for me as a newbie as when I first started using D&D beyond I had a lot of programming and web development knowledge, plus in my 30s. I have, however, played with somebody who edited a wizard subclass to swap out the minor illusion cantrip to a different one - something that requires the same process - in under 2 minutes. First day using D&D beyond. They were 15.
The homebrew interface is daunting and clunky - but intuitive enough.
But perhaps my experience was a one-off and I'm blinded by that, if so I apologise. When I have more time, perhaps I will make a guide to show how to swap the spells manually. I'm pretty sure somebody has already done that somewhere, but I can't find it. If I remember I will make the guide later.
Anyway, my point is ultimately: "posting 'not fixed yet' doesn't do anything at all, why do it?" out of curiosity and confusion.
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.
As a professional software developer, this is utter nonsense. Having paying customers raising the same issue and adding to the tracker count absolutely has an effect on prioritization. If something is so minor no actual customer complains, then it might stagnate in the backlog for years. You are correct that often times an overhaul is required and preferable to some hacky fix that will just cause other regressions.
Except this forum is not used as a tracker count.
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.
If
If they choose not to acknowledge or to otherwise engage with their customers making a very reasonable and very long lasting issue, that is a choice.
Basically, every time someone posts here, it's a chance for Dndbeyond to do the smart thing, the right thing, and actually communicate about the issue.
And every time that they choose not to, they follow the soulless, corporate approach that treats their customers and inhuman lumps and fears openness integrity, or really even basic respect.
Thing is, they have communicated. They do advise you they are working on it. They explain and advise in the multiple forum threads and in their dev updates. Making them stop what they're doing to come into the forums and repeat themselves over and over isn't helping them or you or anybody - it's time they could be working, instead.
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.
For anyone wondering how to get this on your character sheet as a workaround, while you wait for D&D Beyond to implement this, I made a video showing how. It's bad quality with a really shitty mic - this is not something I normally do. But who knows, maybe it will still help somebody.
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.
In February, I'll have been playing a Divine Soul Sorcerer for 4 years. Still hoping for a fix to this issue.
Thanks for the workaround video. I actually just customized Cure Wounds by renaming it to Healing Word and adding 60' and 1d4+4 to the description instead.
It would be nice to be able to update this in the "Class Features" section where you already indicate your alignment anyway.
As a workaround for this I find it most efficacious to add a 6th option to the Divine Soul’s Divine Magic feature (so it always works correctly RAW from 1st level to 20th):
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting