Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Why Roll20 ad +0 to my roll?

Good morning I've noticed that roll20 adds a mysterious +0 to my NPC rolls, and I can't figure out why. It also happens to a friend of mine DM. What does that +0 represent? and how can i delete it?
It looks like you're using the 'D&D 5E by Roll20' character sheet.  That additional '+0' is a simply placeholder an additional modifier (I believe it's the Global Damage Modifer).  I'm pretty sure the sheet defaults to adding the +0 so that formulas don't break when it's absent.
Intriguing question, I'd never noticed that before, but I have it too. It's not a requirement of the NPC roll template to have three numbers in the damage spec (there's just one damage value), so whatever creates the dice roll from the sheet deliberately put the zero there. However, the 5E sheet in NPC form doesn't have global modifiers.  I tried switching to PC form, adding one, and switching back to NPC form, and the zero remained stubbornly a zero, so its not picking up the modifer formula.  And none of the fields on the NPC form I tried changing to add a plus (proficiency, strength mod) changed it either. I suspect Jarren is correct that it's some kind of placeholder "just in case", maybe someone who understands the arcana of sheet-building can say. But it doesn't seem to actually be used, so it's not going to change the roll, and it looks like we've all got it, so just ignoring it shouldn't be a problem.  It's certainly not anything you or your DM friend did wrong.
Ken S. said: Intriguing question, I'd never noticed that before, but I have it too. It's not a requirement of the NPC roll template to have three numbers in the damage spec (there's just one damage value), so whatever creates the dice roll from the sheet deliberately put the zero there. However, the 5E sheet in NPC form doesn't have global modifiers.  I tried switching to PC form, adding one, and switching back to NPC form, and the zero remained stubbornly a zero, so its not picking up the modifer formula.  And none of the fields on the NPC form I tried changing to add a plus (proficiency, strength mod) changed it either. I suspect Jarren is correct that it's some kind of placeholder "just in case", maybe someone who understands the arcana of sheet-building can say. But it doesn't seem to actually be used, so it's not going to change the roll, and it looks like we've all got it, so just ignoring it shouldn't be a problem.  It's certainly not anything you or your DM friend did wrong. well, nice to hear that haha At least it's not my mistake haha However, it still remains a mystery. I've tried making an npc called 42, with 42 in every possible place: stats, name, modifiers, attacks etc And anyway the modifier was still +0 and not +42 haha, I'm afraid we'll never find out the real cause of that +0 ahahah
1681220909
Kraynic
Pro
Sheet Author
Using inspect on the browser for an attack on the npc sheet reveals that the macro call for the attack is stored in an attribute labeled "rollbase". While it is quite old now, from before the code for the official sheets went proprietary, I looked up the old (html) code on github: <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy</a> The relevant parts for rollbase: &lt;input type="hidden" name="attr_rollbase"&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_dmg" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_crit" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{crit=1}} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}} {{crit1=[[@{attack_crit}+0]]}} {{crit2=[[@{attack_crit2}+0]]}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/div&gt; Basically, the +0 is hardcoded into the macro.&nbsp; It isn't an attribute reference, so there is no way to change it.&nbsp; Why is it there?&nbsp; Might need a time machine to get that answer...
Kraynic said: Using inspect on the browser for an attack on the npc sheet reveals that the macro call for the attack is stored in an attribute labeled "rollbase". While it is quite old now, from before the code for the official sheets went proprietary, I looked up the old (html) code on github: <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy</a> The relevant parts for rollbase: &lt;input type="hidden" name="attr_rollbase"&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_dmg" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_crit" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{crit=1}} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}} {{crit1=[[@{attack_crit}+0]]}} {{crit2=[[@{attack_crit2}+0]]}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/div&gt; Basically, the +0 is hardcoded into the macro.&nbsp; It isn't an attribute reference, so there is no way to change it.&nbsp; Why is it there?&nbsp; Might need a time machine to get that answer... Ooh haha The mystery thickens haha, who has a spare time machine? I lent mine to my cousin ahaha
Kraynic said: Using inspect on the browser for an attack on the npc sheet reveals that the macro call for the attack is stored in an attribute labeled "rollbase". While it is quite old now, from before the code for the official sheets went proprietary, I looked up the old (html) code on github: <a href="https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/tree/master/DD5thEditionLegacy</a> The relevant parts for rollbase: &lt;input type="hidden" name="attr_rollbase"&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_dmg" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;button type="roll" style="display: none;" name="roll_npc_crit" value="@{wtype}&amp;{template:npcdmg} @{damage_flag} {{crit=1}} {{dmg1=[[@{attack_damage}+0]]}} {{dmg1type=@{attack_damagetype}}} {{dmg2=[[@{attack_damage2}+0]]}} {{dmg2type=@{attack_damagetype2}}} {{crit1=[[@{attack_crit}+0]]}} {{crit2=[[@{attack_crit2}+0]]}}"&gt;&lt;/button&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/div&gt; Basically, the +0 is hardcoded into the macro.&nbsp; It isn't an attribute reference, so there is no way to change it.&nbsp; Why is it there?&nbsp; Might need a time machine to get that answer... Ah then I think that it's there so that if the field is left blank that it doesn't throw an error.&nbsp; If you leave the 'ON HIT:' field blank, then you'll get an empty damage roll; if you put a non-number character in there then you get nothing in chat. I think the better option would have been to code it like this : {{dmg1=[[0@{attack_damage}]]}}. But the base code for the 5E sheet is very old at this point!
I hope for One-D&amp;D it completely updates it
1681240418
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Lyt said: I hope for One-D&amp;D it completely updates it This is something I am strongly looking forward to. A lot has been learned since those very early sheets, and the&nbsp;D&amp;D 5th Edition by Roll20 Sheet has passed through soooo many hands.
1681263510
GiGs
Pro
Sheet Author
API Scripter
Lyt said: I hope for One-D&amp;D it completely updates it I believe One-D&amp;D has been abandoned, after the OGL fiasco. Now they are sticking with 5e.
and if One D&amp;D goes through, it aint with Roll20, since they wanna lock that up into their ecosystem on D&amp;D beyond.
As far as I know One D&amp;D is moving forward, and they even release material from time to time to test it out. The OGL fiasco doesn't seem to be impacting the project too much. As for D&amp;D beyond, I don't think they will prevent the other VTTs from using and creating cards for 5e, I don't think it would be convenient for them to lose so many fans (who maybe don't want to pay for the new D&amp;D beyond platform). But who knows, we'll only find out by living