Re: [pcgen] Back to the beginning
- --- Chris Chandler <barak@...> wrote:
> Well, this is like deja-vu. I'm back to theWell I will volunteer if you like.
> beginning of when I came aboard
> on PCGen. :p
> I spent the evening trying to create the new
> statblock format that's used in
> the DMG II (got a pretty fair representation of it
> actually). In the course
> of this endeavor I discovered that the Output Tokens
> are horribly bollixed
> up (either in functionality or documentation or
> So, I'm thinking about diving in again (although in
> a somewhat more
> restrained manner than last time!). Kar, get that
> look outta your eye...
> You got my soul once already, so just stay on your
> seat over there.
> Devon/James, is there a codemonkey I can collar and
> coerce into helping me
> figure what Output Tokens are broken, mis-documented
> or just plain missing?
> And then get them to help me fix the docs (by
> telling me how it should work
> according to the code), or having them fix/add the
> code/functionality needed
> if it's missing?
> PCGen LST Chimp
> PCGen OS Chimp
> PCGen Doc Tamarin
PCGen Docs 2nd, Data Chimp, Code Gibbon, Doc Tamarin
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
- On 8/10/06 5:04 PM, "Terry FitzSimons" <fitzsimons@...> wrote:
> This message is being cross-posted to Experimental for code monkey supportWhat this token appears to be doing is building a list and the (!) means it
> from PcGen, when replying to this message strip off the
> email@example.com please.
> On Tue, 08 Aug 2006 14:40:11 -0400, you wrote:
>> On 8/8/06 3:18 PM, "Terry FitzSimons" <fitzsimons@...> wrote:
>>> As near as I can figure from the tag entry the following changes are
>> I know I would feel better if a code monkey could confirm that the token
>> indeed works the way I've found it to.
>> The only change I see is the second example, what I think the token does is
>> build a sub-list of feats of the specified type. With that in mind using a !
>> negative should build a list of all feats without the specified type.
>>> Displays the 2nd feat name if it is a metamagic feat.
>>> Should be:
>>> Displays the 2nd metamagic feat.
>>> Displays the 3rd feat description if it is a General feat.
>>> Should be:
>>> Suppresses the 3rd General feat description.
>> Should be:
>> Displays the 3rd non-TYPE=General feat description.
> I thought the (!) is a NOT so the display would have been suppressed, not
> just print the next third thing (ItemCreation, Fighter, Metamagic,
> SalientDivineAbility, Epic, SpellKnowledge, Divine, Wild, Psionic,
> EpicPsiCountFeat, Metapsionic)it finds.
will not include that feat type on it's list.
The listing for the Y variable as "the feats position in the character's
complete feat list" is incorrect, what it is referenceing is the feats
position in it's own list that it just created.
Also very confusing are the examples, they do not include the full syntax
specified above it. They do not show that there are two places where you can
spec a feat type
Here is a full example:
This would display the third feat which has TYPE:general but not
What it does NOT do is display the third feat IF it has TYPE:General but not
NOTE: the variable X position accepts a feat type but not in the TYPE=<text>
format, it just takes the text so you can NOT inverse it there.
NOTE: appearently you can have more than 1 Z variable, the !TYPE=Fighter and
the DESC shown above are both Z properties and that use works. It may just
be that that just works for TYPE= or that TYPE= is actually it's own
optional variable, I don't know.
Please preface this with the knowledge that this is just what I observed in
it's use, I have no idea what's the code does under the hood nor do I have a
clue about the Token designers original intent.
>>> Displays the type of the 4th feat if it is an Occupation feat.
>>> Should be:
>>> Displays the type of the 4th Occupation feat.
>> I'll see if I can squeeze some time in and test this theory.
> This in reference to [ pcgen-Documentation Bugs-1536512 ] COUNT
> FEATALL.HIDDEN.ClassAbility clarification.
> The Output Token in question
> Token Name: FEATALL.w.x.y.z
> Variables Used (w): Text (Visibility).
> VISIBLE - Filter the feats that are visible in the outputsheets (default
> HIDDEN - Filter the feats that are not visible in the outputsheets.
> ALL - Shows all feats.
> Variables Used (x): Text (Any Feat Type - default is ALL).
> Variables Used (y): Number (The feats position in the character's complete
> feat list - 0-based index).
> Variables Used (z): Text (Property)
> None - Displays the name of the feat in position x in the character's feat
> DESC - Displays the description of the feat in position x in the
> character's feat list.
> TYPE - Displays the type of the feat in position x in the character's feat
> TYPE=<type> - Filters for feats with the indicated TYPE tag.
> SOURCE - Displays the source of the feat in position x in the character's
> feat list.
> What it does:
> Displays information about the xth feat in the character's complete feat
> You may include more than one TYPE=type in the token.
> You may use "!" in front of a TYPE=type to exclude the particular type from
> the list.
> You may not have an inclusion and exclusion in the same token.
> You may still append .DESC or .TYPE after TYPE=type variables.
> Displays the first feat name.
> Displays the description of the first feat.
> Displays the 2nd feat name if it is a metamagic feat.
> Displays the 3rd feat description if it is a General feat.
> Displays the type of the 4th feat if it is an Occupation feat.
~ Eddy Anthony (MoSaT)
~ PCGen BoD, Data Content Second, Doc Chimp