Considering this bug was reported back in 2017, I doubt that's going to happen any time soon. Several workarounds have been posted in this thread. Someone even made a full video showing a workaround...
In all seriousness though, some type of update on this topic from staff would definitely be welcome. This was originally brought up in April of 2017, so it has been 6 years (not 50). Since the merger with D&D Beyond, is this still happening? Is it something that is still planned sometime in the future?
I know there are workarounds, but native integration for this would be nice.
Has anything really been addressed since the Hasbro machine has taken over and took complete control of DDB? This issue. The isue of not being able to link custom spells, monsters, items, or even non-SRD spells to items? This particular issue. Because who needs to easily create things for their games without asking players to do work arounds? And the earlier attitude of people who may or may not be in the loop? Just do it yourselves must be a great business model for this company to its fans. "Be happy you aren't in the pencil and paper era" is not a proper response to an issue. That's like Tesla saying its ok our cars blow up sometimes because at least you aren't in the age of the carriage, be happy. This is coming from a paying customer btw. I expect when I pay for something for problems with it to be addressed.
I guess the developers who be have more important things to do than to fix things for the users of their software.
This is coming from a paying customer btw. I expect when I pay for something for problems with it to be addressed.
This was one of the big drivers behind me ditching my paid subscription. I was giving them money every month, and the one issue I brought up as a legitimate bug that was impacting my campaign, and was shared by a ton of people on top of that, has yet to even get an official response after multiple years. Just doesn't inspire a lot of faith in them.
You know what they are working on? A VTT that nobody asked for (and probably wont even work)
The ONLY good thing to come from them making their own VTT is that Roll20 has finally started to step up their game improving that old ass site. Really felt like Roll20 was coasting the entire time I was paying for it.
At this point, I fear that this bug will never be fixed (yes it's a bug, not a feature request). In a lot of industries when a large takeover happens (e.g., Hasbro taking over D&D Beyond) the focus is shifted heavily to how they can make more money rather than making a great product. I agree with the posts above about having a certain expectation of quality for a paid product. It's a different story if it was a completely free service (only some aspects of D&D Beyond are free), but in this case, people pay quite a bit of money for the source material (e.g., the legendary bundle is almost $1k now!) and a monthly subscription on top of that. To have a very obvious bug that affects a very large number of people for many years seems to point to intentional negligence. Yes there are workarounds, but should that really be necessary for years on end? I can see it being a short term solution until a fix is implemented, but in this case, the workarounds have pretty much become the permanent solution...
I have enjoyed this product for many years and have paid money, but It's really sad to see things like this go unresolved for so long. I fear what will happen when the next version of D&D is released. Will this tool be abandoned completely and never be fixed? Will Hasbro lock all of the new content behind some new paywall for a similar service only to have more bugs that go unresolved for years? As someone who works in the IT/Software industry, I know it takes time and resources to resolve issues, but to have a bug linger for 6 years is quite disheartening. I mean no disrespect to the D&D beyond team and appreciate their work. This is meant to be constructive criticism. I only wish that more outstanding bugs were fixed rather than more dice skins.
completely off topic but has anyone noticed that a Barbarians rage bonus damage is the hardest ******* thing to find? like we have all these conditions for a player like charmed, stunned, prone, etc. but barbarians cant get a custom condition for Rage?
completely off topic but has anyone noticed that a Barbarians rage bonus damage is the hardest ******* thing to find? like we have all these conditions for a player like charmed, stunned, prone, etc. but barbarians cant get a custom condition for Rage?
Rage is right under Features & Traits with all the rest of the class features for your character, it even has a snippet to automatically calculate the current rate damage for you.
If you want it to display under attack, you can select longbow under weapon and then customize weight (to 0) on the character sheet. Looks good on the character I had to improvise with...
Just edit it on your sheet. I know it isn't as convenient as being able to share it, but at like only a few mins per "special ammo type" (which most games aren't going to have many of, and even then some characters won't ever need) it's not a big deal.
You can already give yourself custom ammo and the devs are busy with other things. Making an "ammo builder" is extremely low priority and will probably never get made (because, you can already do it).
It's still a bug because it still offers you the feature when you're creating the magic item, but then it errors out when you try to save it. It's not a "missing feature," it's a "bug report," and as someone who has been reporting this bug for YEARS all the while giving them money every month for their online features, I just don't see where their bug fix team is focusing their efforts. It's not like someone is not writing a new source book because they have to fix a bug. This is a billion dollar company that should have dedicated bug fix devs on their web team. It's not like we're getting all of this for free and complaining. WOTC has gotten hundreds of dollars from some people, not just for source books and adventures, but for the website membership where these kinds of features are added as a selling point.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Considering this bug was reported back in 2017, I doubt that's going to happen any time soon. Several workarounds have been posted in this thread. Someone even made a full video showing a workaround...
oh nice over half a century and still the same :D
What? O.o
My Homebrew: Races | Subclasses | Backgrounds | Spells | Magic Items | Feats
Need help with Homebrew? Check out this FAQ/Guide thread by IamSposta
See My Youtube Videos for Tips & Tricks using D&D Beyond
They are back from the future to let us know it doesn't get fixed in half a century.
Half a century is 50 years...
In all seriousness though, some type of update on this topic from staff would definitely be welcome. This was originally brought up in April of 2017, so it has been 6 years (not 50). Since the merger with D&D Beyond, is this still happening? Is it something that is still planned sometime in the future?
I know there are workarounds, but native integration for this would be nice.
Imagine if they just added ammunition and homebrew invocations before we all die
i never even thought about homebrew invocations! you could always use Feats to get the same effect tho
This is a big oversight that is unbelievably simple to fix. Bumping. If there is a better place to poke people, let's find it.
Has anything really been addressed since the Hasbro machine has taken over and took complete control of DDB?
This issue. The isue of not being able to link custom spells, monsters, items, or even non-SRD spells to items?
This particular issue. Because who needs to easily create things for their games without asking players to do work arounds?
And the earlier attitude of people who may or may not be in the loop? Just do it yourselves must be a great business model for this company to its fans.
"Be happy you aren't in the pencil and paper era" is not a proper response to an issue. That's like Tesla saying its ok our cars blow up sometimes because at least you aren't in the age of the carriage, be happy.
This is coming from a paying customer btw. I expect when I pay for something for problems with it to be addressed.
I guess the developers who be have more important things to do than to fix things for the users of their software.
This was one of the big drivers behind me ditching my paid subscription. I was giving them money every month, and the one issue I brought up as a legitimate bug that was impacting my campaign, and was shared by a ton of people on top of that, has yet to even get an official response after multiple years. Just doesn't inspire a lot of faith in them.
Every time I mention something like this in a thread, the mod/admins just send me a link to apply for jobs. Trash
You know what they are working on? A VTT that nobody asked for (and probably wont even work)
The ONLY good thing to come from them making their own VTT is that Roll20 has finally started to step up their game improving that old ass site. Really felt like Roll20 was coasting the entire time I was paying for it.
true that
At this point, I fear that this bug will never be fixed (yes it's a bug, not a feature request). In a lot of industries when a large takeover happens (e.g., Hasbro taking over D&D Beyond) the focus is shifted heavily to how they can make more money rather than making a great product. I agree with the posts above about having a certain expectation of quality for a paid product. It's a different story if it was a completely free service (only some aspects of D&D Beyond are free), but in this case, people pay quite a bit of money for the source material (e.g., the legendary bundle is almost $1k now!) and a monthly subscription on top of that. To have a very obvious bug that affects a very large number of people for many years seems to point to intentional negligence. Yes there are workarounds, but should that really be necessary for years on end? I can see it being a short term solution until a fix is implemented, but in this case, the workarounds have pretty much become the permanent solution...
I have enjoyed this product for many years and have paid money, but It's really sad to see things like this go unresolved for so long. I fear what will happen when the next version of D&D is released. Will this tool be abandoned completely and never be fixed? Will Hasbro lock all of the new content behind some new paywall for a similar service only to have more bugs that go unresolved for years? As someone who works in the IT/Software industry, I know it takes time and resources to resolve issues, but to have a bug linger for 6 years is quite disheartening. I mean no disrespect to the D&D beyond team and appreciate their work. This is meant to be constructive criticism. I only wish that more outstanding bugs were fixed rather than more dice skins.
completely off topic but has anyone noticed that a Barbarians rage bonus damage is the hardest ******* thing to find? like we have all these conditions for a player like charmed, stunned, prone, etc. but barbarians cant get a custom condition for Rage?
Rage is right under Features & Traits with all the rest of the class features for your character, it even has a snippet to automatically calculate the current rate damage for you.
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Epic Boons on DDB
If you want it to display under attack, you can select longbow under weapon and then customize weight (to 0) on the character sheet. Looks good on the character I had to improvise with...
~Stephanie
Still an issue. This is MADDENING
Just edit it on your sheet. I know it isn't as convenient as being able to share it, but at like only a few mins per "special ammo type" (which most games aren't going to have many of, and even then some characters won't ever need) it's not a big deal.
You can already give yourself custom ammo and the devs are busy with other things. Making an "ammo builder" is extremely low priority and will probably never get made (because, you can already do it).
My Homebrew: Races | Subclasses | Backgrounds | Spells | Magic Items | Feats
Need help with Homebrew? Check out this FAQ/Guide thread by IamSposta
See My Youtube Videos for Tips & Tricks using D&D Beyond
It's still a bug because it still offers you the feature when you're creating the magic item, but then it errors out when you try to save it. It's not a "missing feature," it's a "bug report," and as someone who has been reporting this bug for YEARS all the while giving them money every month for their online features, I just don't see where their bug fix team is focusing their efforts. It's not like someone is not writing a new source book because they have to fix a bug. This is a billion dollar company that should have dedicated bug fix devs on their web team. It's not like we're getting all of this for free and complaining. WOTC has gotten hundreds of dollars from some people, not just for source books and adventures, but for the website membership where these kinds of features are added as a selling point.