[Pcgen-trackers] [ pcgen-Feature Requests-1789856 ] Qualify tag

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

Feature Requests item #1789856, was opened at 2007-09-07 00:14
Message generated for change (Settings changed) made by jfrazierjr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1789856&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: Code Related (Add/Del/Improve)
Group: For 5.14
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: LegacyKing (amaitland)
>Assigned to: Joe Frazier, Jr. (jfrazierjr)
Summary: Qualify tag 

Initial Comment:
I appologize if this has come up before.

What I am proposing here is similar to the existing
QUALIFY tag but instead of specifically qualifying
certain objects it specifically will "bypass" a given
prereq anywhere it is found.

This is very powerful especially for homebrew type set
so you don't have to mod every object that contains
the PRE to include your qualifying options.

For example, lets say I create an ability that works
similarly to Sneak Attack and I call it Sneakier
Attack.  I want any character that has the Sneakier
Attack ability to qualify for anything that a
character with Sneak Attack would qualify for.  To do
this currently I have to find all the PRE tags that
reference Sneak Attack and .MOD those objects to say:
PREFEAT:1,Sneak Attack,Sneakier Attack.

Instead I would like to be able to have my Sneakier
Attack define something like BYPASS:FEAT|Sneak Attack.
 This looks alot like the QUALIFY syntax but a
QUALIFY:FEAT|Sneak Attack would make the character
eligible to possess Sneak Attack and BYPASS would make
it so any PREFEAT:Sneak Attack would return a match.

I think the tag names are actually backwards but since
QUALIFY exists I assume we are stuck with it.

-Aaron

----------------
Aaron Divinsky
PCGen Data Chimp, Code Chimp, Doc Tamarin

Please check out 1410718 and 1377067, both scheduled for 6.2+ if I
remember correctly.

Having said that, I would much prefer this be of the form:

PSEUDO:FEAT:Sneak Attack

...or something to that effect (though I'd rather defer the discussion
for a good year or so, in order to focus _experimental's attention on
the open items for 5.14).

By doing this, we can do any token with PSEUDO: including movement,
BONUSES, etc.  If we limit this to PObjects, we cook half the problem,
and then have to create a new syntax for the other stuff.  I'd rather
have one concept that can be reused.

TP.
I wasn't limiting it to PObjects.  I guess I didn't
make it clear.  I was suggesting that any PRExxx could
have a BYPASS:xxx token.

-Aaron

----------------
Aaron Divinsky
PCGen Data Chimp, Code Chimp, Doc Tamarin

Perhaps I'm misunderstanding again, but I'd rather keep the syntax
matching the current input tokens, not the PRExxx tokens.... 

Either way, there are plenty of issues with the entire PRExxx system
that this opens up, but that's best kept for a time when it's
appropriate to address these FREQs.

TP.


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

Comment By: Eddy Anthony (eddyanthony)
Date: 2008-02-05 11:00

Message:
Logged In: YES 
user_id=886893
Originator: NO

Adding to the 5.14 group per BoD meeting 2/4/08

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

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