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

[Ex 2e] Exalted sheet bug.

I am not sure if this goes in here or in bug reports & technical issues, but my problem is very simple: I recently started playing Exalted, and I am using the sheet provided for 2nd edition. After the second game I started noticing that some of the stats that the sheet auto calculates were missing. It happened to some of the NPC sheets so i didn't care too much, but then it happend to a player too and I have no idea how to fix it. The missing stats are DV and  everything on the athcleticims section.
1441851484

Edited 1441851531
I just found the problem. After checking all the stats that factor into the movement of a character I noticed that the mobility penalty for armor makes all the stats that include said penalty, and are auto calculated, blank. Not sure if it only happend in my game or maybe it is a known bug with the sheet.
1441855647

Edited 1441856694
Lithl
Pro
Sheet Author
API Scripter
Looks like the Dodge DV and the movement distance calculations are all expecting a positive value for the armor's mobility penalty, but the mobility penalty input is designed to have a negative value when you use the spinners. You can still type in a positive value directly by ignoring the spinners, and the calculated fields should work properly. Go ahead and use that for a workaround until I get a fix pushed through. (So if you've got a -2 penalty armor, type 2 in the mobility penalty box.) Edit: Pull #1053 should fix this problem. Once the changes are merged into the live version of the sheet, it won't matter whether you list your mobility penalty as positive or negative, it will subtract correctly regardless. Until the changes are merged in, setting the value to a positive number should get you the correct results in all of the fields experiencing an error.
Thanks, Brian. Inputing a positive value directly works fine.