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

[5e OGL] Revisiting sneak attack macro issue once more

1516137878

Edited 1516138011
So you guys are probably tired of seeing me ask questions about this but, I have had a new issue arise since the update to the OGL sheet. I have found that the sneak attack macro and crit macro, along with the assassinate macro all work just fine, until I level up. Any time a modification is made to my character level, my sneak attack macro breaks and goes from this 1d6 + ?{Sneak Attack|No, 0|Yes, [[ ceil((@{base_level}) / 2) ]]d6 [Sneak Attack]} to only displaying this 1d6 + ?{Sneak Attack|No . what this does is makes it so the sneak attack query comes up but since it does not have a following value, it does not roll any dice. Has anyone else had any issues with inline queries, in attacks in the attacks and spellcasting block, where the macro would get cut off? Or, does anyone know if they added a limit to the number of characters allowed in the "Damage" fields of attacks? Normally, this wouldn't be a problem, but since I have multiple weapons and have started to get more unique finesse weapons, it would require me to re-input the macro on every weapon every time I level up, and that's just gonna get really annoying. Thanks for any help you guys can provide.  This is my first post, and  this is my second regarding all of the Sneak Attack macro nonsense.
1516141543

Edited 1516143014
Looks like the Sheet Workers are misparsing something. I'm looking into this further, but here is a workaround in the meanwhile: 1d6 + ?{Sneak Attack|0|[Sneak Attack] [[ceil((@{base_level}) / 2)]]d6}
Ah, that would explain it, I gave that a try, and seems to work perfectly. The asking yes or no versus 0 or formula isn't a big deal and still gets the job done. Thanks a lot.
You're very welcome. Thank you for reporting this issue; I've brought it to the attention of the Dev Team, here .
Oh dude, you are way better at reporting the issues and steps than I would have been, lol. Thanks again. Hopefully this gets addressed in the next update, as this is new to the most recent sheet update.