Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data 4366 #7205

Merged
merged 3 commits into from
Nov 6, 2024
Merged

Data 4366 #7205

merged 3 commits into from
Nov 6, 2024

Conversation

AllenCohn
Copy link
Contributor

To start, I "fixed" an unexpected deviation in the implementation of the evoker's force missiles. As best I can tell all of the arcane school powers (of the number of uses = INT + 3 type) use the variable ArcaneSchoolPowerTimes to calculate the number of times they can be used...except for the evoker's force missiles. It uses

BONUS:VAR|EvocationForceMissileTimes|3+INT

instead of

BONUS:VAR|EvocationForceMissileTimes|ArcaneSchoolPowerTimes

I assumed this was a mistake and changed it to the latter in cr_abilities_class.lst.

Then in apg_abilities_race.lst I added a bonus to ArcaneSchoolPowerTimes in Favored Class Bonus ~ Arcane School Power Use.

Finally, the language of the alternate favored class bonus ("Select one arcane school power at 1st level that is normally usable a number of times per day equal to 3 + the wizard’s Intelligence modifier. The wizard adds +½ to the number of uses per day of that arcane school power.") suggests that there is a "selection" process involved...that there is more than one of these arcane school powers per character.

But as far as I could see there is only one such power per specialist wizard. So I skipped implementing any CHOOSE and just added to ArcaneSchoolPowerTimes directly (in apg_abilities_class.lst) assuming it would only affect one thing. But if I'm wrong and ArcaneSchoolPowerTimes affects more than one thing, then there's an edge-case error in my implementation.

@LegacyKing LegacyKing merged commit 5eee914 into PCGen:master Nov 6, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants