A simple way to make spell scrolls have a specific spell on them would be great, without having to homebrew a magic item for each specific scroll.
Even just the ability for Tooltips to function in the character sheet so you could type it into the custom name box of the scroll would work perfectly fine
Another thing would be to be able to add spells to magic items. There are even some missing on existing items. I just had to create a copy of Figurine of Wondrous Power (Silver Raven) that can cast animal messenger because that wasn't included in the item (it didn't appear on list of spells and PC doesn't have that spell on their class spell list). Being able to quickly add a spell or effect to an item as part of the "Customize" would be great.
With the Expert Classes UA, it can be hard to sort through every spell that is or isn't allowed by the new classes.
If we can't get homebrewed classes, can we get homebrewed Spell Lists? Like creating an Arcane Spell List, and then using that in a homebrewed subclass or item's Spell List feature? That way you could quickly add the Arcane List to a new homebrew and then add the additional restrict of School or the like.
Barring that, can we at least have the option on character sheets to filter by School of Magic?
Rollback Post to RevisionRollBack
Reality is more amazing than we are often led to believe.
This probably won't have a lot of interest, but I would love to see a public facing API for developers to integrate D&D beyond character sheets into their applications. I've got a project a client ordered I could repurpose into a simple VTT afterwards with a bit of work, and would love to hook into your character sheets.
Also, support for the TCE sorcerer subclasses (aberrant mind, clockwork soul) swapping out spells from their expanded spell lists as listed in the feature would be nice too.
please give us a way to opt out of one dnd because i already see problems with the spell list and changes to feats that will motivate me to just stick to 5th edition and maybe take some rules from one dnd
Is there an analytics option in the works that could be used to show a player how often they cast each spell? For character creation and selecting both known spells and prepared spells, I just think it would be helpful.
Is there an analytics option in the works that could be used to show a player how often they cast each spell? For character creation and selecting both known spells and prepared spells, I just think it would be helpful.
As a stats guy, I'd LOVE this option! And as someone who always WANTS to try different spells, play a variety of tactics, I'd LOVE this option!
I know, playing as my Cleric in one campaign, that I usually use the same spells over and over... As my Artificer in another campaign I try to be more varied and creative whenever I can... I'd love to be able to look at my Cleric Spell List after each Long Rest and say, "huh, I've never used _______, I'll prepare it now and see what happens"
Now that the sources section is expanding, I would love a possibility to pin the Adventure I am DM'ing at the moment so I don't have to click around as much. (I think this would help on the mobile version on the site as well as there is no view all option there so I can't go to the adventure at all, and yes, I have the app and that works great, I just forget to use it sometimes.)
If it hasn't been requested yet: Using an adventure's pre-gen characters in the associated adventures without having to recreate the characters for those adventures. Not quite what was requested below as I think it would be best to use them associated with the adventure in which they appear and let people recreate them if they wish to use them elsewhere.
I recently bought Stormwreck Isle and it includes PDFs of the pre-gen characters but for the life of me I cannot seem to see if there is a way to add the characters straight to you dnd characters list in DnD beyond other than going through each step of the character builder? Is this correct?
Rollback Post to RevisionRollBack
Human. Male. Possibly. Don't be a divider. My characters' backgrounds are written like instruction manuals rather than stories. My opinion and preferences don't mean you're wrong. I am 99.7603% convinced that the digital dice are messing with me. I roll high when nobody's looking and low when anyone else can see.🎲 “It's a bit early to be thinking about an epitaph. No?” will be my epitaph.
Monsters need reviewed to make sure correct monster tags are used. For example why would a wizard like the enchanter not have the wizard tag? This would make the monster type filter in the encounter builder more applicable/practical to find what you need.
Also, all tags should be included. Why isn't NPC there?
It would be cool if we could exclude certain monster types in the encounter tool once they have been updated
Monsters need reviewed to make sure correct monster tags are used. For example why would a wizard like the enchanter not have the wizard tag? This would make the monster type filter in the encounter builder more applicable/practical to find what you need.
Also, all tags should be included. Why isn't NPC there?
It would be cool if we could exclude certain monster types in the encounter tool once they have been updated
Tags are a deprecated piece of metadata from the early days of D&D. They're not actual rules information and were added to help the site listings function back when DDB first launched. Now they've been largely abandoned
Tags are a deprecated piece of metadata from the early days of D&D. They're not actual rules information and were added to help the site listings function back when DDB first launched. Now they've been largely abandoned
Thank you for the clarification.
This is exactly the kind of thing that makes DDB harder to use than it should be. If tags are no longer supported they should be removed. As a developer I must say that nothing is worse than unsupported functionality. It makes the application confusing and and difficult to use.
Personally, I like tags and would like to see them updated and supported again. There are so many ways they could be leveraged; I don't understand why DDB would abandon them.
Tags are a deprecated piece of metadata from the early days of D&D. They're not actual rules information and were added to help the site listings function back when DDB first launched. Now they've been largely abandoned
Thank you for the clarification.
This is exactly the kind of thing that makes DDB harder to use than it should be. If tags are no longer supported they should be removed. As a developer I must say that nothing is worse than unsupported functionality. It makes the application confusing and and difficult to use.
Personally, I like tags and would like to see them updated and supported again. There are so many ways they could be leveraged; I don't understand why DDB would abandon them.
Tags are a deprecated piece of metadata from the early days of D&D. They're not actual rules information and were added to help the site listings function back when DDB first launched. Now they've been largely abandoned
Thank you for the clarification.
This is exactly the kind of thing that makes DDB harder to use than it should be. If tags are no longer supported they should be removed. As a developer I must say that nothing is worse than unsupported functionality. It makes the application confusing and and difficult to use.
Personally, I like tags and would like to see them updated and supported again. There are so many ways they could be leveraged; I don't understand why DDB would abandon them.
DDB didn’t abandon them, WotC did.
I think there's some confusion here, and I can see why
What D&D Beyond calls subtypes, Wizards of the Coast calls tags. However, when D&D Beyond first launched the system didn't support tags/subtypes on stat blocks. However, D&D Beyond did use it's own version of tags, which is what the person is referring to. These do not exist in D&D rules and were a "D&D Beyondism", something to make the system work. These have since been deprecated.
However, DDB eventually updated the monster listing to support subtypes (aka actual tags) which WotC doesn't just continue to use, but has actually expanded their use of more proactively.
tl;dr Tags mean two different things, one official (which DDB calls subtype and is still used) and one unofficial (which DDB no longer uses)
I really wish I could help DnDBeyond, D&D, and Hasbro with the pace of feature release for this site and the mobile apps. But this is not an open source project where I can create issues or contribute code changes (pull requests). The majority of my day job is in coaching & leading Agile software teams, in spreading know-how to colleagues and client, and advising companies in their digital strategies. I work in a global IT consultancy, and see many of same successes and concerns across many business domains.
Based on that experience, I see these credits & concerns with DnDBeyond:
The good: - User feedback is strong. You're built a community (through forums and other means). More companies should do this: feedback is a virtuous cycle - Many bugs get fixed relatively quickly. "Quick" is in the eye of the holder, so I expect you may get pushback from the community. Within 1-2 days is best practice depending on how good your "path to production" pipeline is - The website and phone apps are quite reliable. I have almost never seen downtime. Kudos to your devops teams! This is perhaps challenge #1 for consumer-facing software
The less good: - Feature improvements are slow to publish. New homebrew features are perhaps the slowest (excepting the next point which is even slower) - Support of UA lags well behind Crawford & crew publishing. Your Product Owner should consider giving these more priority in the team backlogs. Especially with the April buyout by WotC, I would expect one consumer benefit is closer timing between product & DnDBeyond production releases. Your strategy folks likely have a lot to say about this: listen to them - Website & app reliability at the top levels are high, less so for particular areas like searching. Thankfully you have a friendly, sensible page for backend failures, and retrying nearly always works (again, go buy your dev & devops teams pizza for this). Note I've noticed improvements on this throughout the year: clearly you are addressing reliability
Were DnDBeyond a client, I'd love to see and walk through your backlog, and find out more on "how the sausage is made" with your teams. Alas, I'm just another player
Capturing and realizing how D&D works is an incredibly complex business domain full of "general, then specific, then exception". I get funny looks from colleagues when holding up D&D as an example of complexity, but I think it merits some tech whitepapers. And I've tried my hand in personal projects at this -- not simple!
A simple way to make spell scrolls have a specific spell on them would be great, without having to homebrew a magic item for each specific scroll.
Even just the ability for Tooltips to function in the character sheet so you could type it into the custom name box of the scroll would work perfectly fine
Another thing would be to be able to add spells to magic items. There are even some missing on existing items. I just had to create a copy of Figurine of Wondrous Power (Silver Raven) that can cast animal messenger because that wasn't included in the item (it didn't appear on list of spells and PC doesn't have that spell on their class spell list). Being able to quickly add a spell or effect to an item as part of the "Customize" would be great.
With the Expert Classes UA, it can be hard to sort through every spell that is or isn't allowed by the new classes.
If we can't get homebrewed classes, can we get homebrewed Spell Lists? Like creating an Arcane Spell List, and then using that in a homebrewed subclass or item's Spell List feature? That way you could quickly add the Arcane List to a new homebrew and then add the additional restrict of School or the like.
Barring that, can we at least have the option on character sheets to filter by School of Magic?
Reality is more amazing than we are often led to believe.
|| How to add tooltips || How to use snippet codes ||
This probably won't have a lot of interest, but I would love to see a public facing API for developers to integrate D&D beyond character sheets into their applications. I've got a project a client ordered I could repurpose into a simple VTT afterwards with a bit of work, and would love to hook into your character sheets.
Also, support for the TCE sorcerer subclasses (aberrant mind, clockwork soul) swapping out spells from their expanded spell lists as listed in the feature would be nice too.
Honestly, I want the Hadozee portraits back. It's annoying having to upload a picture when I'm trying to play one of my favorite races
please give us a way to opt out of one dnd because i already see problems with the spell list and changes to feats that will motivate me to just stick to 5th edition and maybe take some rules from one dnd
Is there an analytics option in the works that could be used to show a player how often they cast each spell? For character creation and selecting both known spells and prepared spells, I just think it would be helpful.
As a stats guy, I'd LOVE this option! And as someone who always WANTS to try different spells, play a variety of tactics, I'd LOVE this option!
I know, playing as my Cleric in one campaign, that I usually use the same spells over and over... As my Artificer in another campaign I try to be more varied and creative whenever I can... I'd love to be able to look at my Cleric Spell List after each Long Rest and say, "huh, I've never used _______, I'll prepare it now and see what happens"
Now that the sources section is expanding, I would love a possibility to pin the Adventure I am DM'ing at the moment so I don't have to click around as much. (I think this would help on the mobile version on the site as well as there is no view all option there so I can't go to the adventure at all, and yes, I have the app and that works great, I just forget to use it sometimes.)
If it hasn't been requested yet: Using an adventure's pre-gen characters in the associated adventures without having to recreate the characters for those adventures. Not quite what was requested below as I think it would be best to use them associated with the adventure in which they appear and let people recreate them if they wish to use them elsewhere.
Human. Male. Possibly. Don't be a divider.
My characters' backgrounds are written like instruction manuals rather than stories. My opinion and preferences don't mean you're wrong.
I am 99.7603% convinced that the digital dice are messing with me. I roll high when nobody's looking and low when anyone else can see.🎲
“It's a bit early to be thinking about an epitaph. No?” will be my epitaph.
Monsters need reviewed to make sure correct monster tags are used. For example why would a wizard like the enchanter not have the wizard tag? This would make the monster type filter in the encounter builder more applicable/practical to find what you need.
Also, all tags should be included. Why isn't NPC there?
It would be cool if we could exclude certain monster types in the encounter tool once they have been updated
Tags are a deprecated piece of metadata from the early days of D&D. They're not actual rules information and were added to help the site listings function back when DDB first launched. Now they've been largely abandoned
Find my D&D Beyond articles here
Thank you for the clarification.
This is exactly the kind of thing that makes DDB harder to use than it should be. If tags are no longer supported they should be removed. As a developer I must say that nothing is worse than unsupported functionality. It makes the application confusing and and difficult to use.
Personally, I like tags and would like to see them updated and supported again. There are so many ways they could be leveraged; I don't understand why DDB would abandon them.
DDB didn’t abandon them, WotC did.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I see, thank you for the correction.
Even still, I believe they need to be removed from DDB if they are no longer supported.
I think there's some confusion here, and I can see why
What D&D Beyond calls subtypes, Wizards of the Coast calls tags. However, when D&D Beyond first launched the system didn't support tags/subtypes on stat blocks. However, D&D Beyond did use it's own version of tags, which is what the person is referring to. These do not exist in D&D rules and were a "D&D Beyondism", something to make the system work. These have since been deprecated.
However, DDB eventually updated the monster listing to support subtypes (aka actual tags) which WotC doesn't just continue to use, but has actually expanded their use of more proactively.
tl;dr Tags mean two different things, one official (which DDB calls subtype and is still used) and one unofficial (which DDB no longer uses)
Find my D&D Beyond articles here
There is a lot of 'legacy clean up' to be done on D&D Beyond, tis the nature of a site such as this one.
Find my D&D Beyond articles here
I feel a lot of confusion might have been averted had DDB respected WotC’s naming conventions.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I really wish I could help DnDBeyond, D&D, and Hasbro with the pace of feature release for this site and the mobile apps. But this is not an open source project where I can create issues or contribute code changes (pull requests).
The majority of my day job is in coaching & leading Agile software teams, in spreading know-how to colleagues and client, and advising companies in their digital strategies. I work in a global IT consultancy, and see many of same successes and concerns across many business domains.
Based on that experience, I see these credits & concerns with DnDBeyond:
The good:
- User feedback is strong. You're built a community (through forums and other means). More companies should do this: feedback is a virtuous cycle
- Many bugs get fixed relatively quickly. "Quick" is in the eye of the holder, so I expect you may get pushback from the community. Within 1-2 days is best practice depending on how good your "path to production" pipeline is
- The website and phone apps are quite reliable. I have almost never seen downtime. Kudos to your devops teams! This is perhaps challenge #1 for consumer-facing software
The less good:
- Feature improvements are slow to publish. New homebrew features are perhaps the slowest (excepting the next point which is even slower)
- Support of UA lags well behind Crawford & crew publishing. Your Product Owner should consider giving these more priority in the team backlogs. Especially with the April buyout by WotC, I would expect one consumer benefit is closer timing between product & DnDBeyond production releases. Your strategy folks likely have a lot to say about this: listen to them
- Website & app reliability at the top levels are high, less so for particular areas like searching. Thankfully you have a friendly, sensible page for backend failures, and retrying nearly always works (again, go buy your dev & devops teams pizza for this). Note I've noticed improvements on this throughout the year: clearly you are addressing reliability
Were DnDBeyond a client, I'd love to see and walk through your backlog, and find out more on "how the sausage is made" with your teams. Alas, I'm just another player
Capturing and realizing how D&D works is an incredibly complex business domain full of "general, then specific, then exception". I get funny looks from colleagues when holding up D&D as an example of complexity, but I think it merits some tech whitepapers. And I've tried my hand in personal projects at this -- not simple!
Warm regards, and 20 on d20 to you all