Fixed
Details
Assignee
Andrew MaitlandAndrew MaitlandReporter
chadnicchadnicLabels
Source Books
Pathfinder (Specify)Pending User Input
NoComponents
Fix versions
Affects versions
Priority
Minor
Details
Details
Assignee
Andrew Maitland
Andrew MaitlandReporter
chadnic
chadnicLabels
Source Books
Pathfinder (Specify)
Pending User Input
No
Components
Fix versions
Affects versions
Priority
Created January 27, 2024 at 9:35 AM
Updated August 18, 2024 at 5:18 PM
Resolved August 18, 2024 at 5:18 PM
Unchained Monk’s Bonus AC is broken and it is causing double and triple and quadruple calculations of the Wisdom portion of the AC bonus that all monks get.
The issue stems from a clash between cr_abilities_class.lst and how it implements the bonus variables and then the AC bonus, and pu_abilities_class.lst and how it tries to calculate the bonus and implement it.
cr_abilities_class.lst has two steps to calculate the AC Bonus:
Line 1088
and line 1091
Because line 1088 use a Class|Monk.MOD, this is not removed when going to Pathfinder Unchained version of the Monk which is built as an Archtype actually. So line 1091 is removed as part of removing skills and replacing them with Unchained versions, but line 1088 is not. This causes the carry over that causes Monk AC to miscalculated because that MOD is on top of what is in line 460 of pu_abilities_class.lst
The easiest way to fix it is to simplify the pu_abilities_class.lst to match the way Monk normally does it because the AC progression and bonus stats etc are no different between the regular version of the monk and the Unchained version from what I can tell.
FIX: Replace line 460 in pu_abilities_class.lst with the following:
Alternatively you could fix Monk in the cr_abilities_class.lst and create the AC Bonus in one Special Ability alone without using the MOD and then that special ability will be removed in its entirety and replaced in its entirety with what is in pu_abilities_class.lst, however, I have not tested it this way because I don’t know if something else relies on that MOD so altering pu_abilities_class.lst was the safest way to handle things with the least chance of downstream issues however the cleanest way would be to fix cr_abilities_class.lst permanently and then deal with other possible side effects as they arise.