Undefined means no die was defined - it's a set number.
It does apply the +1 damage, which is why it's 5, not 4 (normal blowgun does 4 damage).
No bug here.
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.
shouldn't blowguns only do 1 piercing and not 4? so it should 2 flat piercing damage. also if you look at the picture, it says UNDEFINED. so yes, blowgun +1 is bugged.
shouldn't blowguns only do 1 piercing and not 4? so it should 2 flat piercing damage. also if you look at the picture, it says UNDEFINED. so yes, blowgun +1 is bugged.
1 + Dex Mod 3 (which both my char and your char has) = 4.
It's a range weapon, so you add your Dex Mod to the attack and damage rolls.
As for the "undefined", I already explained that. No it isn't a bug.
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.
As for the "undefined", I already explained that. No it isn't a bug.
It is, but it's only a display bug. The reporting system should better handle "no die was rolled".
An intended outcome is not a bug. A bug is when the code does something unintended.
No die was defined for the roll so the output "undefined" (something the dev would have to specifically type out as the outcome when coding this) is fitting in every way and deliberate.
You might have a preference for what it should say, and you are welcome to put that in the Feedback forum, but a deliberately coded outcome occurring for the instance it was deliberately coded for is not a bug.
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.
As for the "undefined", I already explained that. No it isn't a bug.
It is, but it's only a display bug. The reporting system should better handle "no die was rolled".
An intended outcome is not a bug. A bug is when the code does something unintended.
No die was defined for the roll so the output "undefined" (something the dev would have to specifically type out as the outcome when coding this) is fitting in every way and deliberate.
You might have a preference for what it should say, and you are welcome to put that in the Feedback forum, but a deliberately coded outcome occurring for the instance it was deliberately coded for is not a bug.
"undefined" is a Javascript type. If you print it, you get the string "undefined".
If they were deliberately printing something for this situation, it'd be "1+4" (or, if the system has to encode the fixed damage as a damage bonus, "0+5"). The presence of undefined here is a clear indicator of a function that doesn't expect to get that, but due to JS's "make do and muddle along" design, it more-or-less works.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
https://imgur.com/a/7tAWMhq
undefine when rolling damage, does not apply +1 to damage
Undefined means no die was defined - it's a set number.
It does apply the +1 damage, which is why it's 5, not 4 (normal blowgun does 4 damage).
No bug here.
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.
https://www.dndbeyond.com/equipment/35-blowgun
shouldn't blowguns only do 1 piercing and not 4? so it should 2 flat piercing damage. also if you look at the picture, it says UNDEFINED. so yes, blowgun +1 is bugged.
1 + Dex Mod 3 (which both my char and your char has) = 4.
It's a range weapon, so you add your Dex Mod to the attack and damage rolls.
As for the "undefined", I already explained that. No it isn't a bug.
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.
It is, but it's only a display bug. The reporting system should better handle "no die was rolled".
An intended outcome is not a bug. A bug is when the code does something unintended.
No die was defined for the roll so the output "undefined" (something the dev would have to specifically type out as the outcome when coding this) is fitting in every way and deliberate.
You might have a preference for what it should say, and you are welcome to put that in the Feedback forum, but a deliberately coded outcome occurring for the instance it was deliberately coded for is not a bug.
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.
"undefined" is a Javascript type. If you print it, you get the string "undefined".
If they were deliberately printing something for this situation, it'd be "1+4" (or, if the system has to encode the fixed damage as a damage bonus, "0+5"). The presence of undefined here is a clear indicator of a function that doesn't expect to get that, but due to JS's "make do and muddle along" design, it more-or-less works.