I was directed by James to open a bug if this continued to be an issue.
I have an issue that is likely a bug.
Bit easier I think to just paste the code, explain what I think should
happen, and then let you make the determination.
ABILITY:Internal|AUTOMATIC|Race Stat ~ AGI|Race Stat ~ AGI|Race Stat ~ AGI
+1 AGI KEY:Race Stat ~ AGI CATEGORY:Internal TYPE:RaceStatOnly
ABILITY:Internal|AUTOMATIC|Stat Increase ~ AGI
CHOOSE:NOCHOICE MULT:YES STACK:YES
Increase Agility PREVARGTEQ:Experience,PurchaseAGI KEY:Stat
Increase ~ AGI COST:0 CATEGORY:Internal TYPE:StatSelect
BONUS:LOCKEDSTAT|AGI|1 CHOOSE:NOCHOICE MULT:YES STACK:YES
Notice that both are abilities are NOCHOICE choosers with MULT:YES and
What I expect to happen
Race Stat ~ AGI (x3) grants Stat Increase ~ AGI (x3)
What actually happens
Race Stat ~ AGI (x3) grants Stat Increase ~ AGI (x1)
Am I wrong in expecting a different result?
I think this is related to an existing code bug to do with stacking no choice abilities. However to be sure we would need to know what version of PCGen you are using. Tom is looking at this as part of his ability rework, which is currently scheduled to be completed for the 6.4 release.
PCGen Code SB
My version of pcgen is using the latest build with recent code commit. I will look forward to the fix then. Thanks mate!
Yes just saw Tom's massive check-in, looks fantastic. If this problem continues please open a code bug in jira.
– End dialog.
pcgen version build 6.03.00 using commit revision 24042
Note: This is more complicated, per my post to pcgen and pcgen_experimental. Please see here:
These more complex issues need to be addressed before a resolution to this question can be defined
James, can you chime in here? I can't call this a bug, and even a freq is not well defined enough to handle without new capability like FOREACH (see the _exp thread I linked)
How should we handle?
Certainly when I initially read the concern I missed the chaining. I'd expect we would need to clarify what is required and come up with some new syntax to drive it. As it stands this is working as expected and fixing the bug as reported would have devastating effects on existing data and characters.
So this should form a new tag proposal.
You can likely simulate the desired outcome using a count of the "+1 AGI" but that should be further discussed on the lst file help list.
Converted to FREQ