Re: troubleshooting.htm.ftl questions
toggle quoted messageShow quoted text
So the issue really is whether the property call to get the result (to hit, damage, etc.) in the OS has, in addition to its final result value, a property as an array of arrays for the effective applied bonuses.
In the case of Pathfinder it would be an array of bonus types each containing a subtotal and an array of abilities and bonuses that contribute to that subtotal, with stacking rules applied. (i.e. showing the Armor Bonus to AC subtotal type might be shown as “+4 [Armor Bonus: +2 (Leather Armor), +4 (Mage Armor)]” revealing that the two components of the +4 armor bonus were the leather armor’s armor bonus and mage armor’s armor bonus). Thus revealing all sources of armor bonus and the stacking rules applied.
If an array of arrays of the bonuses is exportable then it should only be a matter of the OS recursively iterating through that results property and displaying them without the OS needing to specifically call for each bonus type by name. This would then be ultimately supportable without frequent need to change the OS for some new bonus type that suddenly exists, or the inability to display a custom bonus type in a homebrew.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Andrew Maitland via Groups.Io
Sent: Sunday, December 23, 2018 8:00 PM
To: email@example.com; Tom Parker <thpr@...>
Subject: Re: [pcgenexperimental] troubleshooting.htm.ftl questions
The simple answer is YES.
The more difficult answer is Only If we code it to do that.
Every number is tracked, and it knows where the bonuses and penalties come from. However, figuring out how to make sure those values are captured is harder. Unless Tom has already considered this and has a better a solution than I know of.
Let's take a mock example from what you have:
To Hit: +19
Assuming Level 9 Fighter +9
ï¿½ï¿½ï¿½ MODIFY:ToHit_Enhancement|MAX|2 (From EQMOD)
ï¿½ï¿½ï¿½ MODIFY:DAMAGE_Enhancement|MAX|2 (From EQMOD)
ï¿½ï¿½ï¿½ MODIFYOTHER:EQUIPMENT.PART|CHOICESELECTION|ToHit_Bonus|ADD|1 (Weapon Focus Feat)
MODIFYOTHER:EQUIPMENT.PART|CHOICESELECTION|ToHit_Bonus|ADD|1 (Weapon Specialization Feat)
MODIFYOTHER:EQUIPMENT.PART|CHOICESELECTION|Damage_Bonus|ADD|1 (Overhand Chop Feat)
MODIFYOTHER:EQUIPMENT.PART|CHOICESELECTION|Damage_Bonus|ADD|2 (Backswing Feat)
That's easier on the Data team, but then we have to make sure each source of the bonuses are being populated on export for a breakdown. Otherwise, we need to differentiate the bonuses, and make specific calls to them from the sheet, not as expandable and more work for the data team.
On 12/23/2018 5:33 PM, markjmeans wrote: