I will be releasing a new version of the Druid Wild Shapes Implementor extension (DWSI) in the next couple days. I have submitted it to the Forge. As soon as it’s approved I’ll post it.
Finally I have a fix for the issue originally reported by Niwi, see posts #360-368, where DWSI was displaying an incorrect AC value in the player’s instance of Fantasy Grounds.
After much work, I can only believe that the problem is a result of timing issues. As the extension changes the Druid’s stats to those of the Wild Shape beast, many fields have to be manipulated. Some of the fields are composites, calculated, using various other fields. For the Armor Class, AC, there are about 1/2 dozen contributing fields (armor, shield, dexterity modifier, etc.) as those field values are manipulated, the user interface is asynchronously updated, meaning, for example, DWSI might change the armor value, followed by the shield value, followed by the dexterity value, … However because of asynchronicity, the change of the dex, might be reflected in the user interface before the others. It’s an uncontrolled situation that in this case can cause the final displayed value to be incorrect.
What this version does is, after all of the stats have been modified, and the extension’s Wild Shape routines are about to end, the “most important” stat, in this case the ability scores, are “tickled”. They're bumped up by 2 points, then decremented by 2 points. (The number 2 was chosen to ensure the ability bonus was affected.) Changes to the ability scores in this manner trickles down to many of the other affected stats, like AC and the Skills, refreshing each of their displayed values. For the user, the “tickling” of the ability scores, and their display, occurs so quickly, that they should be unnoticeable. Unless the display is wrong, as Niwi reported. In that case the correction of the user interface is observable as a cycling from the wrong value to the correct value.
A note to myself: while chasing down an effective, though somewhat unpalatable, fix for this problem, I noticed, just once or twice, a similar, incorrectly displayed value for the Perception Skill. The methodology developed to fix the AC, should also fix the Perception problem as well.