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 .
×
May your rolls be chill this holiday season!
Create a free account

Calculations Bug

So, with fairly extensive testing (see a total of 8 hours spent trying to do a simple division calculation) I've found that division of pulled attribute values doesn't work, at all, and multiplication is excruciatingly unreliable (the same multiplication of *2 has only worked in one attribute calculation, but past that has needed to be coded at attr-y + attr-y to work around multiplying it by 2)  Doing slight tagging tweaks to the code to make it compatible in javascript testing sites yields the appropriate result.  This means it is a bug within roll20 it's self not allowing certain calculations at all within the sheets gm's code in.
1496947320
Lithl
Pro
Sheet Author
API Scripter
See my most recent post in your other thread. I'm pretty certain this is a misunderstanding of how autocalc fields work.
Yeah, I'd figured the api for roll20 it's self would auto flag that a composite attribute would be the value of that attribute, and responded as such in that thread.  It's odd though that it wouldn't pull the the value of the composites instead of what's added together and then messing up OoO with the other calculations.  It's still a bit odd that it wouldn't flag that the middle calc (for z, being based on x+y) and instead pulls the x+y*aa for the calculation.  Something that wasn't denoted at all in the wiki as a potential thing that could happen, which makes using a frankenstienian coding conglomerate like we are a bit.....lets say frustrating