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

Saving Throws Not Adding Modifiers

After playing today briefly, my players and I have noticied that Saving Throws are not adding their respective modifiers. Skill/Ability checks are working fine, as are NPC saving throws, just not player saving throws. They come up showing that the modifier is 0 on the roll.

I've checked another game I own/run, as well as a game that I am a player in, but I get the issue in all of them.

Is this happening to anyone else at the moment?

June 23 (4 years ago)
David M.
Pro
API Scripter

Yes, it seems to be affecting other people, too. I am not affected, but folks on this thread are:

https://app.roll20.net/forum/post/8863918/saving-throws-not-adding-any-modifiers/?pageforid=8863981#post-8863981



June 23 (4 years ago)
GiGs
Pro
Sheet Author
API Scripter

Today's the day sheet's get their weekly update, so it sounds like this week;s update changed something.

indeed, both of our games are affected, saving throws yesterday were working correctly, today they add 0 modifier

June 23 (4 years ago)
keithcurtis
Forum Champion
Marketplace Creator
API Scripter

I have reported this in the official feedback thread for the D&D 5th Edition by Roll20 sheet, as well as other channels. Hopefully it will be reverted soon. They display properly on the sheet, but the roll templates are using the wrong modifier attribute.

June 23 (4 years ago)

Having the same problem. Glad it isn't just me. Hope they sort it soon...

June 24 (4 years ago)
Kenton
Forum Champion
Translator

Thanks for reporting this. A bug was introduced with the release this morning that caused Saving Throws to roll without modifiers. After the issue was reported here and other places, a fix was made and pushed. We've confirmed the solution resolved the issue. 

Thanks for the response and for everyone's help!