[Pcgen-trackers] [ pcgen-Feature Requests-1311107 ] AUTO:FEAT, AUTO:VFEAT tags with CHOOSE support

[SourceForge.net <no...@so...>]

Feature Requests item #1311107, was opened at 2005-10-02 14:56
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1311107&group_id=25576

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Eddy Anthony (eddyanthony)
Assigned to: Nobody/Anonymous (nobody)
Summary: AUTO:FEAT, AUTO:VFEAT tags with CHOOSE support

Initial Comment:
Moved from PCGenDM under:
Tag Creation and Modification Requests
[ 905513 ] AUTO:FEAT, AUTO:VFEAT tags with CHOOSE 
support
<http://sourceforge.net/tracker/index.php?
func=detail&aid=905513&group_id=36698&atid=450221>

Original request:
I'd like to request a pair of new tags to allow a lst to 
add either automatic or virtual nonremovable feats to a 
character, but with any applicable aspect determined by 
a CHOOSE tag. For instance, a class that grants an 
automatic Weapon Specialization feat, but only to the 
character's deity's favored weapon might use 
AUTO:FEAT|Weapon Specialization|%CHOICE <tab> 
CHOOSE:WEAPONPROF|1|DEITYWEAPON.

Similarly, an effect that grants a virtual feat to a 
variable aspect could use a similar syntax, substituting 
AUTO:VFEAT for AUTO:FEAT.

Tag Name: AUTO:FEAT|x,x|y

Variables Used (x): Text (<Feat Name>)
Variables Used (y): Text (<Aspect>)

What it does:

This is a | (pipe) delimited list of automatic feats that 
are granted to the character for free. 
The feats added are marked on the GUI just as 
AUTO:FEATs are (yellow) and can't be removed. 
A matching CHOOSE tag is required to determine the 
applicable aspect if the aspect is %CHOICE.
CAUTION:If you specify multiple feats, they will all be 
applied to the same aspect.

Examples:

AUTO:FEAT|Weapon Specialization|%CHOICE

The feat "Weapon Specialization" is granted as an 
automatic feat, and is applied to a weapon proficiency 
specificed by a matching CHOOSE tag.

AUTO:FEAT|Weapon Focus,Weapon 
Specialization,Improved Critical|%CHOICE

The feats "Weapon Focus," "Weapon 
Specialization," "Improved Critical" are all granted as 
automatic feats, and are all applied to a weapon 
proficiency specificed by a matching CHOOSE tag.

Comments:
Date: 2005-03-04 20:15
Sender: ericbeaudoin
Logged In: YES 
user_id=324612

I'm rereading this and I wonder why not use

AUTO:FEAT|Weapon Sepcialization (%CHOICE)

The reason why I would see the%CHOICE embedded is to 
alow for multiple CHOOSE tag with different place-holder 
variables (if we ever manage to make the CHOOSE rewrite 
happen...).
                                                        
Date: 2005-01-07 06:13
Sender: tir-gwaith
Logged In: YES 
user_id=208239

Yes, this is still part of the AUTO:FEAT idea, which keeps 
getting postponed.
                                                        
Date: 2004-10-06 16:29
Sender: kingpaul
Logged In: YES 
user_id=277877

Are these trackers still valid?
                                                        
Date: 2004-08-06 18:59
Sender: tir-gwaith
Logged In: YES 
user_id=208239

Hm.... Ok, let's keep this in mind as an enhancement for 
later.  I like the idea.  Once AUTO:FEAT and AUTO:VFEAT are 
in, we can work on adding this in.  With the code clean up in 
progress, I don't want to pile too much on them yet.
                                                        
Date: 2004-07-08 13:32
Sender: dmcmill
Logged In: YES 
user_id=705399

Eric,
  I was looking through SF for things forgotten. Since we
have been talking about AUTO I am going to assign this to
Tir and have him assign it back so he has this info and can
take it into account in the TAG design no reason not to
think this through as it could add to the TAG's usefulness

Tir,
  Take a look at this we where all talking about this and I
had forgotten all about this tracker
                                                        
Date: 2004-03-04 21:33
Sender: ericbeaudoin
Logged In: YES 
user_id=324612

For Doug:

I wold drop the convoluted [x] (inline PRExxx tags). At first I

thought it would be nice but in the end, it doesn't have
any 
real added value and it complecate the syntax. If defferent 
PRExxx must be use, it's easier and clearerto use multiple

AUTO:xxx tags.

Question: is the slot (z) parameter mandantory? If not, I 
would use SLOT=z to make it clearer.

So

"AUTO:EQUIP|" <equip list> { "|"
<slot> } { "|" <PRExxx 
tags> }

<equip list>:= <equipment name> { ","
<equip list> }
<slot> := "SLOT=" <slot identifier>
<slot identifier> := "Head" | "Armor"
| "Ring" | ...
                                                        
Date: 2004-03-04 00:40
Sender: creeperman
Logged In: YES 
user_id=985356

Is AUTO:FEAT even in use now?  As far as I know, everything 
still uses FEATAUTO.  But if it is an issue, the new tag could 
easily be renamed to retain backward compatibility.
                                                        
Date: 2004-03-03 22:27
Sender: dmcmill
Logged In: YES 
user_id=705399

Main thing I don't like about this is it will break the
existing 
AUTO:FEAT as it current use 
    AUTO:FEAT|x|x|x|x|PRExxx
Main thing I like is that pipes are changed to the standard 
usage and it adds to the flexibility of the TAG
    AUTO:FEAT|x,x,x,x|y|PRExxx
If we change any atuotags this way I think we will want to 
change all AUTO TAGs to this format for consitancy so this 
means changing
AUTO:EQUIP|x|x|x|x[PRExxx]
to something like
AUTO:EQUIP|x[y],x,x|z|PRExxx
where x is the item, y is the eqmod, z is the slot to be used
and AUTO:WEAPONPROF  and anu otheres I am not thinking of

Opinions Eric??

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1311107&group_id=25576