I've been messing around with the dice roller added to the player app, and think I've found a bug.
While trying out rolling with an attack, I rolled a natural 20, which caused the damage box to light up blue as normal for the site, and caused it to roll double dice. All good there. Only problem is that from that point on I can't roll anything other than double damage; every weapon or effect I roll is rolled as if it were a critical hit, requiring the app to be closed before it will reset to normal behaviour again.
Is this the correct place to report this? Bugs seems more appropriate but doesn't have a specific section for the app.
Rollback Post to RevisionRollBack
Former D&D Beyond Customer of six years: With the axing of piecemeal purchasing, lack of meaningful development, and toxic moderation the site isn't worth paying for anymore. I remain a free user only until my groups are done migrating from DDB, and if necessary D&D, after which I'm done. There are better systems owned by better companies out there.
I have unsubscribed from all topics and will not reply to messages. My homebrew is now 100% unsupported.
Hmm, it doesn't seem to be consistent (not easy to test when it can take so long to roll a crit on purpose 😝). This time the first three crits didn't trigger it, then on a fourth it did; damage rolls became locked as crits (long press and choose to roll normally also affected). I was rolling with advantage to make a crit more likely in case that might have something to do with (I'm afraid I don't remember if I did the first time this happened).
I'm running on a Blackview BV5500 Pro, it's a budget brand but it runs a full version of Android 9.0, fully patched.
Rollback Post to RevisionRollBack
Former D&D Beyond Customer of six years: With the axing of piecemeal purchasing, lack of meaningful development, and toxic moderation the site isn't worth paying for anymore. I remain a free user only until my groups are done migrating from DDB, and if necessary D&D, after which I'm done. There are better systems owned by better companies out there.
I have unsubscribed from all topics and will not reply to messages. My homebrew is now 100% unsupported.
I've been messing around with the dice roller added to the player app, and think I've found a bug.
While trying out rolling with an attack, I rolled a natural 20, which caused the damage box to light up blue as normal for the site, and caused it to roll double dice. All good there. Only problem is that from that point on I can't roll anything other than double damage; every weapon or effect I roll is rolled as if it were a critical hit, requiring the app to be closed before it will reset to normal behaviour again.
Is this the correct place to report this? Bugs seems more appropriate but doesn't have a specific section for the app.
Former D&D Beyond Customer of six years: With the axing of piecemeal purchasing, lack of meaningful development, and toxic moderation the site isn't worth paying for anymore. I remain a free user only until my groups are done migrating from DDB, and if necessary D&D, after which I'm done. There are better systems owned by better companies out there.
I have unsubscribed from all topics and will not reply to messages. My homebrew is now 100% unsupported.
Thank you for this report but we need some more info:
Hmm, it doesn't seem to be consistent (not easy to test when it can take so long to roll a crit on purpose 😝). This time the first three crits didn't trigger it, then on a fourth it did; damage rolls became locked as crits (long press and choose to roll normally also affected). I was rolling with advantage to make a crit more likely in case that might have something to do with (I'm afraid I don't remember if I did the first time this happened).
I'm running on a Blackview BV5500 Pro, it's a budget brand but it runs a full version of Android 9.0, fully patched.
Former D&D Beyond Customer of six years: With the axing of piecemeal purchasing, lack of meaningful development, and toxic moderation the site isn't worth paying for anymore. I remain a free user only until my groups are done migrating from DDB, and if necessary D&D, after which I'm done. There are better systems owned by better companies out there.
I have unsubscribed from all topics and will not reply to messages. My homebrew is now 100% unsupported.
Thank you!
So far we haven't heard about the issue from other users so it can be device-specific but we'll be monitoring the issue.