So, right now, you have a dice collection, and to change what dice you use, you have to go to the "My Dice" tab and change them, and that changes them for all your characters.
However, I propose a change: Let the dice be Character spesific, like how Underdark mode or backgrounds are for the character sheets.
This way players can change what dice are used without having to go to a separate page, and if you're, say, playing a Cryomancer with The Everlasting Rime Dice in one campaign, and want to play a bloodhunter with the Sanguine Dice in another, you won't have to keep switching back and forth, because the dice are tied to the character.
+1, definitely would make for an increased quality of life update in the Character Sheet.
Rollback Post to RevisionRollBack
#Open D&D
Have the Physical Books? Confused as to why you're not allowed to redeem them for free on D&D Beyond? Questions answered here at the Hardcover Books, D&D Beyond and You FAQ
Looking to add mouse-over triggered tooltips to such things like magic items, monsters or combat actions? Then dash over to the How to Add Tooltips thread.
Necroing in 2024 cause how is this still not a thing? I am both a player and a DM and would like to use certain dice for certain creatures and instances. It is incredibly tedious to switch between them while in game but I want my big bad to have cooler looking dice then their henchmen.
I'm not a D&D Beyond developer nor am I privy to the specifics of how the various systems work, but I do work in a sector very adjacent to the services DDB provides so I think I could likely speculate a plausible reason why it hasn't been implemented; high disruption risk for a low reward (low Risk/Reward ratio).
If I had to guess, the following services are at play:
Entitlements to determine what dice you should have available
Dice to handle dice rolling and displaying your dice collection
Profile to store the currently selected set
Character to call a dice roll
My working theory would be that the dice service calls the entitlement service to list out your dice and the profile service to know which dice is selected. Then when you roll from your sheet, the character service just sends a call to the dice service and the dice service handles the rest.
To implement per-character dice, you'd need to move the storage of current set from the profile service (which is generally a fairly low volatility service) to the character service as part of character metadata. This is a big (like, site breaking big) change that could disrupt every single character on the site, including everyone who doesn't use digital dice. So here we have risk 1. There's also the addition of a new UI element for selecting the dice and worse yet, you need to add a two-way service call between the character service and the dice service. The character sheet needs to ask your dice collection what dice you have and then pull the selected dice into the new variable. Risk 2. Okay, so hopefully now things are okay, right? You've got the character service pulling in data from the dice service and storing the selected dice, and the dice service configured to look at the character service for the selected dice. Everything now works like before; roll is called and the dice service takes over. All good?
Nope.
Because now we have the best problem; character transfer. What happens when you transfer a character from one account to the other and the recipient account doesn't have the corresponding dice entitlements? Risk 3. You'd presumably need some fallback operation, probably to one of the default sets. However, I don't even know if this problem could be solved under how the entitlements system works. It would all depend on if entitlement licenses are two element User + SKU entitlements, or a single entitlement code generated as a function of user and sku. If it's the former, you'd probably be able to handle character handover and preserve selected dice if it's in the recipients collection and fallback to a free set if not. However, if it's the latter, then it'd be impossible to seamlessly hand-over and preserve dice. Not the end of the world if dice default back every time you transfer a character, but not elegant. However, I think the real concern would be the possible failure/bug states that result from this.
Again, I don't have any knowledge of how the guts of DDB works, but this is just my day-job based speculation. In other words, a lot of scary work for not a huge amount of return.
I am curious about character transferring between accounts. How does DDB handle this with sourcebooks? Like say, a character was created as an owlin but the account you're transferring it to doesn't have that race unlocked. Does it force them to choose a new race? I'm not expecting an actual answer, but with what they do for sourcebooks, could they implement the same coding for dice?
I am curious about character transferring between accounts. How does DDB handle this with sourcebooks? Like say, a character was created as an owlin but the account you're transferring it to doesn't have that race unlocked. Does it force them to choose a new race? I'm not expecting an actual answer, but with what they do for sourcebooks, could they implement the same coding for dice?
I don't know how it's handled "behind the scenes", but the content remains accessible until you remove it. It's effectively 'carried' with the character
However, if I had to speculate, this is likely possible due to the content sharing services that already exist in the backend. Dice however are part of a group of site elements (sheet cosmetics) that are not part of the sharing service, which is why I suspect it wouldn't function as elegantly.
I should caveat all this by saying that per-character dice is something I have personally championed for ages as a veritable dice goblin, both digital and physical. I don't think it's impossible, but I do think it'd be risky and involved. My 'day job' is high up in a software QA team and one of my day-to-days is looking at proposed changes and figuring out how much of a risk there is, and how much testing would be involved to be confident none of those risks come to fruition. This change is something I would personally categorise as a Wide - Medium - Low
Range of possible bugs - Wide (as opposed to Narrow or Medium) Average risk posed by any give bug - Medium (might break something catastrophically but shouldn't explode anything majorly) Return on work invested - Low (this is a nice to have feature, but it wouldn't really add much in terms of functionality or QoL)
I would like to see this implemented, especially with the new "one dice set per class" coming with the preorder of the 2024 players handbook. Being able to actually select the dice for that given class would be a nice feature, especially for those of us on the PbP forum who might be switching characters fairly frequently in a short time, rather than sticking with one for a whole game session.
I do get the points being made about risk, but the transfer mentioned with regards to race sticking and content sharing doesn't apply to frames and backgrounds which also stick until changed, but can't be shared via content sharing. I am fully aware that this is (almost certainly) not an easy change but if it is possible to implement, I will be very happy.
So, right now, you have a dice collection, and to change what dice you use, you have to go to the "My Dice" tab and change them, and that changes them for all your characters.
However, I propose a change: Let the dice be Character spesific, like how Underdark mode or backgrounds are for the character sheets.
This way players can change what dice are used without having to go to a separate page, and if you're, say, playing a Cryomancer with The Everlasting Rime Dice in one campaign, and want to play a bloodhunter with the Sanguine Dice in another, you won't have to keep switching back and forth, because the dice are tied to the character.
Love it!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So, right now, you have a dice collection, and to change what dice you use, you have to go to the "My Dice" tab and change them, and that changes them for all your characters.
However, I propose a change: Let the dice be Character spesific, like how Underdark mode or backgrounds are for the character sheets.
This way players can change what dice are used without having to go to a separate page, and if you're, say, playing a Cryomancer with The Everlasting Rime Dice in one campaign, and want to play a bloodhunter with the Sanguine Dice in another, you won't have to keep switching back and forth, because the dice are tied to the character.
Yes! Please.
+1 from me
How to: Replace DEX in your AC | Jump & Suffocation stats | Build a (Spell & class effect buff system | Wild Shape effect system) | Tool Proficiencies as Custom Skills | Spells at higher levels explained | Superior Fighting/Martial Adept Fix | Snippet Codes Explored - Subclasses | Snippet Math Theory | Homebrew Weapons Explained
Check out my: FEATS | MAGIC ITEMS | MONSTERS | SUBCLASSES Artificer Specialist: Weaveblade
Dndbeyond images not loading A PERMANENT WORKAROUND!!! (thank you Jay_Lane)
+1, definitely would make for an increased quality of life update in the Character Sheet.
#Open D&D
Have the Physical Books? Confused as to why you're not allowed to redeem them for free on D&D Beyond? Questions answered here at the Hardcover Books, D&D Beyond and You FAQ
Looking to add mouse-over triggered tooltips to such things like magic items, monsters or combat actions? Then dash over to the How to Add Tooltips thread.
Please make this quality of life change.
Carnival King
Adding this feature could potentially increase Digital Dice sales too, while making players happy!
Necroing in 2024 cause how is this still not a thing? I am both a player and a DM and would like to use certain dice for certain creatures and instances. It is incredibly tedious to switch between them while in game but I want my big bad to have cooler looking dice then their henchmen.
+1 Because I'm upset that this still isn't a thing and want to put dice for a specific character...
Kinda wild that it isn't. It seems like a win/win. Incentivizes digital dice hoarding AND makes the players happy.
I'm not a D&D Beyond developer nor am I privy to the specifics of how the various systems work, but I do work in a sector very adjacent to the services DDB provides so I think I could likely speculate a plausible reason why it hasn't been implemented; high disruption risk for a low reward (low Risk/Reward ratio).
If I had to guess, the following services are at play:
My working theory would be that the dice service calls the entitlement service to list out your dice and the profile service to know which dice is selected. Then when you roll from your sheet, the character service just sends a call to the dice service and the dice service handles the rest.
To implement per-character dice, you'd need to move the storage of current set from the profile service (which is generally a fairly low volatility service) to the character service as part of character metadata. This is a big (like, site breaking big) change that could disrupt every single character on the site, including everyone who doesn't use digital dice. So here we have risk 1. There's also the addition of a new UI element for selecting the dice and worse yet, you need to add a two-way service call between the character service and the dice service. The character sheet needs to ask your dice collection what dice you have and then pull the selected dice into the new variable. Risk 2. Okay, so hopefully now things are okay, right? You've got the character service pulling in data from the dice service and storing the selected dice, and the dice service configured to look at the character service for the selected dice. Everything now works like before; roll is called and the dice service takes over. All good?
Nope.
Because now we have the best problem; character transfer. What happens when you transfer a character from one account to the other and the recipient account doesn't have the corresponding dice entitlements? Risk 3. You'd presumably need some fallback operation, probably to one of the default sets. However, I don't even know if this problem could be solved under how the entitlements system works. It would all depend on if entitlement licenses are two element User + SKU entitlements, or a single entitlement code generated as a function of user and sku. If it's the former, you'd probably be able to handle character handover and preserve selected dice if it's in the recipients collection and fallback to a free set if not. However, if it's the latter, then it'd be impossible to seamlessly hand-over and preserve dice. Not the end of the world if dice default back every time you transfer a character, but not elegant. However, I think the real concern would be the possible failure/bug states that result from this.
Again, I don't have any knowledge of how the guts of DDB works, but this is just my day-job based speculation. In other words, a lot of scary work for not a huge amount of return.
Find my D&D Beyond articles here
You bring up a lot of good points so I thank you.
I am curious about character transferring between accounts. How does DDB handle this with sourcebooks? Like say, a character was created as an owlin but the account you're transferring it to doesn't have that race unlocked. Does it force them to choose a new race? I'm not expecting an actual answer, but with what they do for sourcebooks, could they implement the same coding for dice?
I don't know how it's handled "behind the scenes", but the content remains accessible until you remove it. It's effectively 'carried' with the character
However, if I had to speculate, this is likely possible due to the content sharing services that already exist in the backend. Dice however are part of a group of site elements (sheet cosmetics) that are not part of the sharing service, which is why I suspect it wouldn't function as elegantly.
I should caveat all this by saying that per-character dice is something I have personally championed for ages as a veritable dice goblin, both digital and physical. I don't think it's impossible, but I do think it'd be risky and involved. My 'day job' is high up in a software QA team and one of my day-to-days is looking at proposed changes and figuring out how much of a risk there is, and how much testing would be involved to be confident none of those risks come to fruition. This change is something I would personally categorise as a Wide - Medium - Low
Range of possible bugs - Wide (as opposed to Narrow or Medium)
Average risk posed by any give bug - Medium (might break something catastrophically but shouldn't explode anything majorly)
Return on work invested - Low (this is a nice to have feature, but it wouldn't really add much in terms of functionality or QoL)
Find my D&D Beyond articles here
I would like to see this implemented, especially with the new "one dice set per class" coming with the preorder of the 2024 players handbook. Being able to actually select the dice for that given class would be a nice feature, especially for those of us on the PbP forum who might be switching characters fairly frequently in a short time, rather than sticking with one for a whole game session.
I do get the points being made about risk, but the transfer mentioned with regards to race sticking and content sharing doesn't apply to frames and backgrounds which also stick until changed, but can't be shared via content sharing. I am fully aware that this is (almost certainly) not an easy change but if it is possible to implement, I will be very happy.
After joining more my signature got out of hand so I am now a proud member of the extended signature club!! :)
I have nothing to add to that. I understand all the problems and what not, but yeah, it would certainly be a nice QoL feature.
commenting to boost this suggestion. I think about this a lot and it would be huge if I could do this for my characters.
do you know how to get more dice colors
You purchase them here: https://marketplace.dndbeyond.com/digi-dice
pronouns: he/she/they
I'd like this feature, it's how I used to play at the table. Each character or campaign had different dice.
+1, im playing both a artificer and a barberian and i would love to have two diffrent dice for each charcter
Love it!