[Pcgen-trackers] [ pcgen-Feature Requests-989026 ] [5.8] AUTO:FEAT / AUTO:VFEAT

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

Feature Requests item #989026, was opened at 2004-07-11 15:35
Message generated for change (Comment added) made by ericbeaudoin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=989026&group_id=25576

Category: Feat Support
Group: None
Status: Open
Resolution: None
Priority: 7
Submitted By: Andrew McDougall (tir-gwaith)
Assigned to: Devon Jones (soulcatcher)
Summary: [5.8] AUTO:FEAT / AUTO:VFEAT

Initial Comment:
Request for Global tags to replace all instances of FEAT, 
FEATAUTO, and VFEAT throughout the different files.  
Deprecation of all FEAT, FEATAUTO, and VFEAT tags, 
with LST Converter to AUTO:FEAT syntax.

Syntax can either go AUTO:FEAT with a PARAM:Virtual 
or PARAM:Automatic, or using AUTO:FEAT and 
AUTO:VFEAT without the optional PARAM tag.  
Whichever way is easier for the Code Monkey.

AUTO:VFEAT|<name of feat>,<name of feat2>,<name 
of mulitple feat(Choice)>|<PRExxx>|<PRExxx>

Since the AUTO:FEAT tag is not designed for a 
CHOOSEr, the <name of mulitple feat(Choice)> would 
need to list an exact choice to be applied, like Weapon 
Focus(Longsword)

At some point in the future it would be nice to have %
LIST capability for use with a CHOOSEr in another 
object, but that is out of the scope for now.

So, for example, the 3.0 Ranger TWF abilities would now 
be coded 
AUTO:VFEAT|Ambidexterity,Two-Weapon 
Fighting|PREVARLT:COUNT
[EQTYPE.ARMOR.EQUIPPED.IS.HEAVY],1,COUNT
[EQTYPE.ARMOR.EQUIPPED.IS.MEDIUM],1

That same one with the optional PARAMeter method 
would be:

AUTO:FEAT|PARAM:Virtual|Ambidexterity,Two-Weapon 
Fighting|PREVARLT:COUNT
[EQTYPE.ARMOR.EQUIPPED.IS.HEAVY],1,COUNT
[EQTYPE.ARMOR.EQUIPPED.IS.MEDIUM],1

PARAMeters would have to start with PARAM: and then 
be comma deliminated (not that we are doing more than 
one parameter here, since Automatic and Virtual are 
mutually exclusive.

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

>Comment By: Eric Beaudoin (ericbeaudoin)
Date: 2004-09-13 18:59

Message:
Logged In: YES 
user_id=324612

I remember we chosed PARAM to indicate the options but I 
think OPTION: would work better.

Other options that are needed:

MONSTER
REMOVEBLE (FEATAUTO feat cannot be removed by the user 
but ADD:FEAT() can. Let's have this opionnal).
PREREQ=YES|NO (only the feats that for witch the prereq are 
met get added)

The default if normal FEAT in no other option is present 
(VIRTUAL, MONSTER, REMOVEBLE).

The default for PREREQ is NO.

The option section is optionnal (ironic) but if present must be 
the first parameter (to the left). Multiple options are possible 
and must be separated by coma.

ADD:FEAT|OPTION:VITURAL,PREREQ=YES|TYPE=Fighter

This would add all the fighter feats for which the PC meet the 
requirement. The feats would be displayed as VIRTUAL i.e. in 
the purple colour and it would not be possible for the user to 
remove them.

OPTION might be a bit long. I think we should also accept 
OPT:. 

That would make:

ADD:FEAT|OPT:VIRTUAL|Alertness

Since we already have three category of feats and may have 
more in the future, I would like to have AUTO:FEAT with 
options rather then AUTO:FEAT, AUTO:VFEAT, AUTO:MFEAT, 
AUTO:RFEAT.

Let's go Devon, get cracking :-).

P.S. the PREREQ option is a nice to have for now. It is not 
needed for 5.8. Same thing for REMOVABLE although this one 
would be very useful.


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

Comment By: Andrew McDougall (tir-gwaith)
Date: 2004-09-13 15:29

Message:
Logged In: YES 
user_id=208239

Back on the 5.8 list.  VFEAT PRExxx stuff isn't working, and 
this is needed to get the 3.5 Ranger working smoothly.

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

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