[BugFix] Repeating Section Default Attributes and Select Element Default Attributes

I'm doing some work to prep the API to be able to run Sheet Worker scripts, and as part of that I'm fixing a few outstanding bugs. I've just pushed a new API version to the Dev Server which should fix the issues with using getAttrByName() and getSheetDefaultValue() when used with select elements. In addition, now you can get the default values of repeating section elements by doing for example "repeating_skills_attributeone". The default values are the same for all repeating sections so you don't pass in the repeating section ID. Let me know if that broke anything for anyone :-)

Indeed. It's going to be opt-in somehow, probably based on the character sheet supporting it?  But at any rate, the idea is that for example if I'm using the 5E OGL sheet, as a player if I change the "Class" element, some of my attributes get automatically set up for me. Right now if the API were to make that same change (setting "Class" to something), class would change but the sheetworker code wouldn't run. So your only option currently would be to duplicate all of the code on in the API script that's also in the sheetworker, if you wanted to maintain that automatic logic. The new feature would basically allow the API script to "dumbly" just "set class", but then there would be another piece of the API that would come along afterward and go "oh, I notice you just updated Class! Well I have some sheetworker code over here that needs to happen when that happens, so I'll run it!" It basically allows the API to do anything a player can do in terms of a sheet and still have automated sheetworker logic happen.

Stephen L. said: Oh wait... perhaps I got a little too hopeful. Still getting "(10+@{perception_bonus}+@{passiveperceptionmod})" when I try to get a character's passive perception from the 5E OGL sheet with getAttrByName. :( Yeah this doesn't affect that, it only provides the default value. You can use sendChat() currently (with a callback function) to calculate what the calculated value of the formula should be for the current point-in-time. I might be able to add a simple "calcFormula()" function that can do the same thing but it would just be syntax sugar...

Stephen L. said: That's what I've been doing. Some of the select-type values for the calculated attributes have caused whole equations to not work in the API, although they work in macros just fine. For those, I've had to manually dissect some of the equations for calculated attributes. Perhaps this update fixes that though? I'll probably ruu it out later. Yes that should be fixed now with this.