Next CHOOSE issue:
Documentation or bug, not sure.
Per reading of the docs this should be legal, it gives incorrect results per the user (Jon).
If changed to:
He gets the desired results, but adds that the AUTO:FEAT component is not updating to the correct results.
Need more info here, can we get some specifics of what is used when and all present tokens so we can validate the exact issue?
Also, is this one issue or two? Seems there is a problem in what is displayed and how it is applied, which is two issues and should be opened separately.
I'm playing middleman here.
I've asked Jon to sign up and answer the question directly.
Andrew asked me to answer these so I'll relay the circumstances. I'm working on a class for Pathfinder that's a 3rd party publisher, but is OGL. One of it's abilities allows you to select a Combat feat that the character qualifies for. The code, as implemented at this time is:
Basics Feat Choice Talented Monk ~ Basics Feat Choice CATEGORY:Special Ability TYPE:TalentedMonkBasicsFeat VISIBLEISPLAY PREVARGTEQ:MonkLVL,1 CHOOSE:FEATSELECTION|QUALIFIED[TYPE=Combat] MULT:YES STACK:NO AUTO:FEAT|%LIST
As Andrew indicated, when the CHOOSE is set to CHOOSE:FEATSELECTION|!PC,QUALIFIED[TYPE=Combat], the ability fails to function, in that it never adds to the "Selected abilities" side of the UI, the CHOOSE dialog does not come up, an it fails to decrement the ability pool.
The other problem encountered while coding this ability is that the Feats, when added by AUTO:FEAT|%LIST, then do not remove from the character if the choices are changed or removed. In comparison, a different ability uses AUTO:FEAT as well, but adds a specific feat instead of a list, and when that ability is removed, the automatically attached feat is also removed. I don't know if this behavior of not removing the feat is tied into CHOOSE or the %LIST Wildcard, so when i reported it to Andrew, as both parts were experienced while designing the single ability, I reported them at the same time. These may be two separate issues and may require a second, separate JIRA opened. Let me know if so and I'll log a separate one for the AUTO:FEAT portion of this.
The first issue (!PC,QUALIFIED not providing any choices) has been fixed
Committed revision 24366.
Probably good to re-evaluate if the second problem still exists post this revision
As I'm not really that good with SVN, I'll pull down the Autobuild once it's caught up to at least REV24366 and test these issues. Will advise if there are still problems present. Thanks Tom!