[Pcgen-team-code] [JIRA] Commented: (NEWTAG-96) CHOOSE:FEATSELECTION

[JIRA (f. E. C. S. ) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/NEWTAG-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12476#action_12476 ] 

Eric C. Smith commented on NEWTAG-96:
-------------------------------------

Tom, the conversion example given in this tracker are for converting CHOOSE:FEAT. Are these examples the same for FEATSELECTION?

Also, I need an axample that demonstrates the internal drill-down done by the CHOOSE:FEATSELECTION tag.

> CHOOSE:FEATSELECTION
> --------------------
>
>                 Key: NEWTAG-96
>                 URL: http://jira.pcgen.org/browse/NEWTAG-96
>             Project: New Tag
>          Issue Type: Modify Token
>          Components: LST Tag
>            Reporter: Tom Parker
>            Assignee: Eric C. Smith
>
> CHOOSE:FEATSELECTION
> SUBTOKEN: FEATADD (deprecated)
> SUBTOKEN: FEATSELECTION (new)
> Syntax
> CHOOSE:FEATSELECTION|x|y|y[z]|y[z,z]|x,y,y[z],y[z,z]
> x is a Feat PRIMITIVE
> A PRIMITIVE is an identifier of objects, and may include any number of specifications. In the case of Feat objects, there are are the three global PRIMITIVES:
> x = an Feat (specified by key)
> x = TYPE=w (w is a TYPE identifier for a Feat)
> x = !TYPE=w (w is a TYPE identifier for a Feat that would be prohibited)
> x = ALL (allow the choice of any Feat)
> y is a QUALIFIER
> A QUALIFIER is a special keyword that identifies a subset of objects that should be returned. Valid qualifiers for Feat objects are any of the Global Qualifiers.
> A comma represents "AND", meaning multiple items are evaluated independently and then any item that appears in ALL of the items is added to the list.
> CHOOSE:FEATSELECTION|Dodge,Toughness
> will result in NO choices because no Feat is both Dodge and Toughness.
> CHOOSE:FEATSELECTION|TYPE=Foo,PC
> would test for any Feat that has the Foo type (as defined in the Feat LST file) which is ALSO already selected by the PlayerCharacter
> This could also be written (probably more clearly):
> CHOOSE:FEATSELECTION|PC[TYPE=Foo]
> A pipe represents "OR", meaning multiple items are evaluated independently and then any item that appears in any of the items is added to the list:
> CHOOSE:FEATSELECTION|Dodge|Toughness
> will result in a choice between Feat Dodge and Feat Toughness.
> All commas (ANDs) are evaluated before pipes (ORs), so something like:
> CHOOSE:FEATSELECTION|Dodge|TYPE=Foo,PC
> would include Dodge unconditionally, in addition to any Feat that has the Foo type (as defined in the Feat LST file) which is ALSO already selected by the PlayerCharacter.
> Note that this will FULLY RESOLVE any Feats, meaning it will not return Weapon Focus, but Weapon Focus (Longsword), etc.
> (this is different than CHOOSE:FEAT| as that will not resolve Feats)
> Conversion
> CHOOSE:FEATADD|Dodge|Toughness
> becomes
> CHOOSE:FEAT|Dodge|Toughness
> ADD:FEAT|%LIST 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira