PCGen Wiki - User contributions [en]

Key Terms

2009-10-27T00:29:43Z

Tir-Gwaith: /* Runtime */ fix broken link

{| align="right"
| __TOC__
|}

==Associations==

Associations are pieces of information about a CDOMObject that are only true within a specific context.
Examples of Associations include the specific Skill selected when the Feat Skill Focus is taken (example from
SRD 3.5)

==Category==

==CDOM List==

A CDOMList is a specific type of CDOM Object used as an identifier to store lists of CDOM Objects.
It is important to note that a CDOM List does not contain CDOM Objects, rather it is an index used
to identify a list of CDOM Objects stored within the [[Rules Data Store]] or Character Data Store.

==CDOM Object==

A CDOM Object is the base type of object used to store information. Languages, Abilities,
Stats, Races, Templates, and many other objects are specific implementations of (in programming
terms "extend") CDOMObject. The CDOM Object should only store information that is universally
true, meaning it is always applicable to the CDOM Object (to all Player Characters in all
circumstances). Transient or contextual information should not be stored in the CDOM Object.

==The Data Persistence Format==

The data persistence format is typically known to the data developers as "Game Mode", "PCC" or "LST" files. These vary slightly in syntax, but are generally tab-delimited text files. Generally "PCC" files are used to identify which "LST" files should be loaded, although there is also limited support for some Global tokens to be used in "PCC" files.

==Data Load==

Load is the set of events that occurs when data persistence files are loaded into PCGen. The Data Load process is intended to include full parsing of the data in the data persistence files (see [[Rules_Persistence_System#Catch Errors Early|Catch Errors Early]]) and not while Player Characters are being created.

==Deferred Objects==

==Derived Objects==

==File Loaders==

File Loaders are Classes that perform the specific actions necessary to load a specific LST file from the file system (or URI) and parse the file into
individual tags. The File Loaders then identify the appropriate Token and pass the value of the tag to the individual Token to be parsed.

For backwards compatibility in the transition from PCGen 5.14, the File Loaders are in the pcgen.persistence package.

==Key==

==Load Context==

The Load Context represents the translator of information loaded in File Loaders and Tokens. The translation is from the persistence data file format to the internal structure used by the Rules Data Store. The LoadContext provides various services; some are discussed in later sections.

Context Classes of the Rules Persistence System are found in the pcgen.rules package.

==Prerequisite==

Prerequisites are limitations placed onto CDOMObjects
in order to constrain the ability of a PlayerCharacter to use the CDOMObject (e.g. to limit
selection of a Feat to a minimum Character Level). There are a few key concepts
that should be recognized when dealing with Prerequisites:
#Prerequisite resolution must take place when a query for information is desired (Testing a Prerequisite is not a static calculation, due to temporary changes that may take place with a PlayerCharacter)
#CDOMObjects may have a Prerequisite as a stand-alone requirement
#CDOMObjects may have a Prerequisite only in a certain context (e.g. A Feat may have a certain Prerequisite only when it is granted by a specific PCClass)

Prerequisite resolution must take place when an object is added to a PlayerCharacter.

==Runtime==

Runtime processes and events are those that take place while a Player Character is being created. The [[Rules Persistence System]] is not responsible for Runtime behavior, although the [[Rules Persistence System]] is responsible for ensuring that the Data Load process produces entries in the [[Rules Data Store]] that minimizes the possible errors or unexpected conditions at Runtime.

==System Loader==

The System Loader is responsible for receiving a set of Campaigns that should be loaded during Data Load. These Campaigns are analyzed by the System Loader, and then the System Loader provides a list of Source Entries to each File Loader to indicate what files (or more generally, URIs) should be loaded.

For backwards compatibility in the transition from PCGen 5.14, the System Loader is in LstSystemLoader in the pcgen.persistence.lst package.

==Token Library==

The Token Library is the storage location for the Tokens, and is queried by the LoadContext once the key and value of a tag has been established by a File Loader. The Token Library is initialized by the Startup System when plugins are loaded by PCGen.

Tir Gwaith

2008-09-28T17:52:13Z

Tir-Gwaith: /* (Lesser used) */

{| align="right"
| __TOC__
|}

Andrew McDougall (aka Tir Gwaith) is a long serving member of the PCGen team. Any questions involving Data tags, or the history of the data structure, he can probably discuss in more detail than even he would like. He's the original monkey that went by "LST Chimp".

=Teams I belong to=

{| border="1"
|-
! Team !! Rank
|-
| [[Code]] || [[Explanation_of_Teams#Lemur|Lemur]]
|-
| [[Content]] - [[Data]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Documentation]] || [[Explanation_of_Teams#Gibbon|Gibbon]]
|-
| [[Tracker]] || [[Explanation_of_Teams#Lemur|Lemur]]
|-
| [[Public Relations]] - [[Data License]] || [[Explanation_of_Teams#Tamarin|Tamarin]]
|-
| [[Admin]] - [[Release]] || [[Explanation_of_Teams#Lemur|Lemur]] - prettylst.pl
|-
| [[Public Relations]] - [[Advertising]] || [[Explanation_of_Teams#Lemur|Lemur]]
|}

=Contact Details=
{| border="1"
|-
| Time Zone || GMT -6
|-
| Email || [mailto:tir.gwaith@gmail.com tir.gwaith@gmail.com]
|-
| IRC || TirGwaith (freenode)
|}

===(Lesser used)===
{| border="1"
|-
| AIM || Tir Gwaith
|-
| Yahoo || tir_gwaith
|-
| MSN || [mailto:tir_gwaith@hotmail.com tir_gwaith@hotmail.com] (spam email only)
|-
| ICQ || -
|-
| Google Talk || -
|}

=Other Tasks=
* UA OGC into LST format for PCGen release
* Trackers assigned to me
* Skill conditionals improvement Spec design and implementation
* Clear New Data Source Development trackers into /alpha or /d20ogl

Tir Gwaith

2008-09-28T17:51:23Z

Tir-Gwaith: /* Contact Details */

{| align="right"
| __TOC__
|}

Andrew McDougall (aka Tir Gwaith) is a long serving member of the PCGen team. Any questions involving Data tags, or the history of the data structure, he can probably discuss in more detail than even he would like. He's the original monkey that went by "LST Chimp".

=Teams I belong to=

{| border="1"
|-
! Team !! Rank
|-
| [[Code]] || [[Explanation_of_Teams#Lemur|Lemur]]
|-
| [[Content]] - [[Data]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Documentation]] || [[Explanation_of_Teams#Gibbon|Gibbon]]
|-
| [[Tracker]] || [[Explanation_of_Teams#Lemur|Lemur]]
|-
| [[Public Relations]] - [[Data License]] || [[Explanation_of_Teams#Tamarin|Tamarin]]
|-
| [[Admin]] - [[Release]] || [[Explanation_of_Teams#Lemur|Lemur]] - prettylst.pl
|-
| [[Public Relations]] - [[Advertising]] || [[Explanation_of_Teams#Lemur|Lemur]]
|}

=Contact Details=
{| border="1"
|-
| Time Zone || GMT -6
|-
| Email || [mailto:tir.gwaith@gmail.com tir.gwaith@gmail.com]
|-
| IRC || TirGwaith (freenode)
|}

==(Lesser used)==
{| border="1"
|-
| AIM || Tir Gwaith
|-
| Yahoo || tir_gwaith
|-
| MSN || [mailto:tir_gwaith@hotmail.com tir_gwaith@hotmail.com] (spam email only)
|-
| ICQ || -
|-
| Google Talk || -
|}

=Other Tasks=
* UA OGC into LST format for PCGen release
* Trackers assigned to me
* Skill conditionals improvement Spec design and implementation
* Clear New Data Source Development trackers into /alpha or /d20ogl

Skill Cost and CSKILL Overhaul

2008-09-27T22:39:04Z

Tir-Gwaith: /* SKILLCOST Global tag */ PARENTCLASS, and CLASSLIST= as alternate part of tag

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

== Current discussion notes ==

So I've thought about the ADDTOLEVEL issues, and I don't think that works well as proposed. The challenge in what was proposed is that CL has a specific meaning in formula, and we don't want to change that based on the context - meaning in this formula and not in others. That's very difficult to get correct... I ran through about 4 alternatives only to find they have some other problem, so it's
easiest to just define a new variable (I use CSL - that's open for discussion), and keep the concept of ADDTOLEVEL as Tir defined it.

This is an updated proposal based on the discussions - can we have someone wikify this, please? (Done, that is this page. :p - Tir)

Note there are still 4 open issues, some with "R1" "R2" (response 1,
response 2) showing the ongoing discussion that is not resolved. I
left "D" open due to the SpellList discussions that took place and
just wanted to double check on what this should be.

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

===Deprecations===
(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

===SKILLCOST Global tag===
(3c) Create SKILLCOST

<pre>Syntax:
SKILLCOST:x|[CLASSLIST=y|]z,z
SKILLCOST:.CLEARALL

Variables Used (x): Skill Cost from Game Mode File
(COST in Game Mode file for this Skill Cost must NOT be PROHIBITED)

Variables Used (y): CLASSLIST=ALL (Default)
Variables Used (y): CLASSLIST=Text (Class Name)
Variables Used (y): CLASSLIST=TYPE.Text (Class Type) (Alternate CLASSLIST=TYPE=Text)
Variables Used (y): CLASSLIST=CLASSLIST
(usable only in CLASS objects, for ease of .COPY, refers to containing class name)
Variables Used (y): CLASSLIST=PARENTCLASS
(usable only in Domain objects, adds to class that grants domain object)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL (all skills)
Variables Used (z): LIST (pulls from items selected in the CHOOSE: token in the object)

Examples:
SKILLCOST:CLASS|Spot,Listen
Add Spot and Listen to Class skills for all of character's classes
SKILLCOST:CROSSCLASS|CLASSLIST=Spy|Read Lips
Add Read Lips as a Cross Class from Exclusive for the "Spy" class.
SKILLCOST:CLASS|CLASSLIST=CLASSLIST|Use Magic Device
Add Use Magic Device to current Class object (in class.lst)
SKILLCOST:CLASS|CLASSLIST=PARENTCLASS|Knowledge (History)
Knowledge (History) becomes a class skill for class granting domain
</pre>

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.

Skill Cost and CSKILL Overhaul

2008-09-27T21:58:00Z

Tir-Gwaith: /* SKILLCOST Global tag */ layout for SKILLCOST syntax defintion

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

== Current discussion notes ==

So I've thought about the ADDTOLEVEL issues, and I don't think that works well as proposed. The challenge in what was proposed is that CL has a specific meaning in formula, and we don't want to change that based on the context - meaning in this formula and not in others. That's very difficult to get correct... I ran through about 4 alternatives only to find they have some other problem, so it's
easiest to just define a new variable (I use CSL - that's open for discussion), and keep the concept of ADDTOLEVEL as Tir defined it.

This is an updated proposal based on the discussions - can we have someone wikify this, please? (Done, that is this page. :p - Tir)

Note there are still 4 open issues, some with "R1" "R2" (response 1,
response 2) showing the ongoing discussion that is not resolved. I
left "D" open due to the SpellList discussions that took place and
just wanted to double check on what this should be.

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

===Deprecations===
(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

===SKILLCOST Global tag===
(3c) Create SKILLCOST
<pre>
Syntax:
SKILLCOST:x|y|z,z
SKILLCOST:.CLEAR

Variables Used (x): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (y): ALL
Variables Used (y): Text (Class Name)
Variables Used (y): TYPE=Text (Class Type)
Variables Used (y): CLASS (usable only in CLASS files, for ease of .COPY)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL
Variables Used (z): LIST (pulls from items selected in the CHOOSE:
token in the object)
</pre>

(3c1 - ISSUE C)

Make y something like like CLASS=ALL, CLASS=<classname>,
CLASS=TYPE.<class type> (there is that TYPE= vs. TYPE. thing again),
and a very funky CLASS=CLASS?

R1- Is this thinking out loud or a change you want in the syntax? If
it's actually a proposal change, then I'd prefer
CLASSLIST=<classname>. We may also want to use something like
CLASSLIST=<this> (literally using the "<this>" string) to improve
clarity vs. CLASSLIST=CLASS

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.

Skill Cost and CSKILL Overhaul

2008-09-27T21:52:10Z

Tir-Gwaith: /* Global LST changes */ break into subsections

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

== Current discussion notes ==

So I've thought about the ADDTOLEVEL issues, and I don't think that works well as proposed. The challenge in what was proposed is that CL has a specific meaning in formula, and we don't want to change that based on the context - meaning in this formula and not in others. That's very difficult to get correct... I ran through about 4 alternatives only to find they have some other problem, so it's
easiest to just define a new variable (I use CSL - that's open for discussion), and keep the concept of ADDTOLEVEL as Tir defined it.

This is an updated proposal based on the discussions - can we have someone wikify this, please? (Done, that is this page. :p - Tir)

Note there are still 4 open issues, some with "R1" "R2" (response 1,
response 2) showing the ongoing discussion that is not resolved. I
left "D" open due to the SpellList discussions that took place and
just wanted to double check on what this should be.

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

===Deprecations===
(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

===SKILLCOST Global tag===
(3c) Create SKILLCOST

Syntax:
SKILLCOST:x|y|z,z
SKILLCOST:.CLEAR

Variables Used (x): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (y): ALL
Variables Used (y): Text (Class Name)
Variables Used (y): TYPE=Text (Class Type)
Variables Used (y): CLASS (usable only in CLASS files, for ease of .COPY)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL
Variables Used (z): LIST (pulls from items selected in the CHOOSE:
token in the object)

(3c1 - ISSUE C)

Make y something like like CLASS=ALL, CLASS=<classname>,
CLASS=TYPE.<class type> (there is that TYPE= vs. TYPE. thing again),
and a very funky CLASS=CLASS?

R1- Is this thinking out loud or a change you want in the syntax? If
it's actually a proposal change, then I'd prefer
CLASSLIST=<classname>. We may also want to use something like
CLASSLIST=<this> (literally using the "<this>" string) to improve
clarity vs. CLASSLIST=CLASS

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.

Pathfinder feat progression

2008-08-12T14:59:26Z

Tir-Gwaith: LEVELSPERFEAT, not FEATSPERLEVEL. D'Oh!

This will be implemented under the following code FREQ: 
[http://sourceforge.net/tracker/index.php?func=detail&aid=2044260&group_id=25576&atid=384722 2044260 Pathfinder bonus feat progression]

This is a freq/proposal for the implementation of code to support the Pathfinder PRG.

Monsters and characters have different progressions for feats per level. While characters get a feat for each odd character level, feats for racial hit dice are still done as in D&D 3.5, i.e. one at 1 HD, and then one more for each 3 HD.

An example: Consider a 7th level fire giant barbarian. As a fire giant he has 15 racial hit dice. He gets feats at hit dice 1, 3, 6, 9, 12, and 15, just as in D&D 3.5. For his class levels, however, he gets feats at levels 1, 3, 5, and 7 (in D&D he would get two more, at hit dice 18 and 21).

== 5.16 proposal ==

=== LST Token change (Code) ===

class line: LEVELSPERFEAT tag

LEVELSPERFEAT:x|LEVELTYPE=y

x = formula / number, # of feats per class level of given class.
y = text, name of group.

Fractional numbers will be stacked together within LEVELTYPE, but not between groups.

=== Data structure change ===

3.0 / 3.5e Monster classes will need |LEVELTYPE=Monster to all LEVELSPERFEAT tags. This will fix a Bug in monsters with PC classes feats at wrong level bug.

Possibly a Scripted (PL) change.

== Post 5.16 (tabled discussion ) ==

The following discussion / proposal is currently tabled until after 5.16. The clean up in GameMode does need to happen, but tearing out that code will delay 5.16. Discussion should continue after 5.16, since this structure change will help ambiguity in the 6.0 code.

----

Tom's proposal to address this feature:

(1) Deprecate CLASSTYPE: in Misc Info files

(2) Deprecate BONUSFEATLEVELSTARTINTERVAL in Misc Info Files

(3) Add a comma delimited list token MONSTERCLASSTYPES in Misc Info Files. This is a list of Types (triggers off the TYPE token in a class) that produce Monsters, replaces ISMONSTER from CLASSTYPE

(4) Add a comma delimited list token IMMUNETOXPPENALTYCLASSTYPES in Misc Info Files. This is a list of Types (triggers off the TYPE token in a class) that do not get an XP Penalty. This replaces the XPPENALTY from CLASSTYPE

(5) Add a CLASSGROUP: in Misc Info files, which allows additional tokens on that line

(6) Add CR: as an additional token for CLASSGROUP: (replaces CR from CLASSTYPE)

(7) Add BONUSFEATLEVELSTARTINTERVAL as an additional token for CLASSGROUP:) (replaces BONUSFEATLEVELSTARTINTERVAL as a stand-alone token)

(8) Add a CLASSGROUP: token to Class LST files.

Note:
(3,4) can be auto-generated based on the CLASSTYPE lines.
(5,6,7) can be auto-generated from what remains of CLASSTYPE and the existing BONUSFEATLEVELSTARTINTERVAL
(8) can be auto-generated from the existing TYPE token based on what CLASSGROUPs were created.

Thus we can automatically convert existing game modes to this new syntax in the move to 5.16 (homebrews, et al.)

The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.

[http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022 See this post] for an in-depth explanation of the rational behind this proposal.

----

Example usage:

<tt>MONSTERCLASSTYPES:Monster 
IMMUNETOXPPENALTYCLASSTYPES:Prestige,Monster

CLASSGROUP:PC CR:CL <tab> BONUSFEATLEVELSTARTINTERVAL:3|3 
CLASSGROUP:NPC CR:max(CL-1,0) BONUSFEATLEVELSTARTINTERVAL:3|3 
CLASSGROUP:Monster CR:0 BONUSFEATLEVELSTARTINTERVAL:3|3</tt>

Pathfinder feat progression

2008-08-12T12:10:01Z

Tir-Gwaith: 5.16 proposal, and tabled post 5.16 spec on same page.

This will be implemented under the following code FREQ: 
[http://sourceforge.net/tracker/index.php?func=detail&aid=2044260&group_id=25576&atid=384722 2044260 Pathfinder bonus feat progression]

This is a freq/proposal for the implementation of code to support the Pathfinder PRG.

Monsters and characters have different progressions for feats per level. While characters get a feat for each odd character level, feats for racial hit dice are still done as in D&D 3.5, i.e. one at 1 HD, and then one more for each 3 HD.

An example: Consider a 7th level fire giant barbarian. As a fire giant he has 15 racial hit dice. He gets feats at hit dice 1, 3, 6, 9, 12, and 15, just as in D&D 3.5. For his class levels, however, he gets feats at levels 1, 3, 5, and 7 (in D&D he would get two more, at hit dice 18 and 21).

== 5.16 proposal ==

=== LST Token change (Code) ===

class line: FEATSPERLEVEL tag

FEATSPERLEVEL:x|LEVELTYPE=y

x = formula / number, # of feats per class level of given class.
y = text, name of group.

Fractional numbers will be stacked together within LEVELTYPE, but not between groups.

=== Data structure change ===

3.0 / 3.5e Monster classes will need |LEVELTYPE=Monster to all FEATSPERLEVEL tags. This will fix a Bug in monsters with PC classes feats at wrong level bug.

Possibly a Scripted (PL) change.

== Post 5.16 (tabled discussion ) ==

The following discussion / proposal is currently tabled until after 5.16. The clean up in GameMode does need to happen, but tearing out that code will delay 5.16. Discussion should continue after 5.16, since this structure change will help ambiguity in the 6.0 code.

----

Tom's proposal to address this feature:

(1) Deprecate CLASSTYPE: in Misc Info files

(2) Deprecate BONUSFEATLEVELSTARTINTERVAL in Misc Info Files

(3) Add a comma delimited list token MONSTERCLASSTYPES in Misc Info Files. This is a list of Types (triggers off the TYPE token in a class) that produce Monsters, replaces ISMONSTER from CLASSTYPE

(4) Add a comma delimited list token IMMUNETOXPPENALTYCLASSTYPES in Misc Info Files. This is a list of Types (triggers off the TYPE token in a class) that do not get an XP Penalty. This replaces the XPPENALTY from CLASSTYPE

(5) Add a CLASSGROUP: in Misc Info files, which allows additional tokens on that line

(6) Add CR: as an additional token for CLASSGROUP: (replaces CR from CLASSTYPE)

(7) Add BONUSFEATLEVELSTARTINTERVAL as an additional token for CLASSGROUP:) (replaces BONUSFEATLEVELSTARTINTERVAL as a stand-alone token)

(8) Add a CLASSGROUP: token to Class LST files.

Note:
(3,4) can be auto-generated based on the CLASSTYPE lines.
(5,6,7) can be auto-generated from what remains of CLASSTYPE and the existing BONUSFEATLEVELSTARTINTERVAL
(8) can be auto-generated from the existing TYPE token based on what CLASSGROUPs were created.

Thus we can automatically convert existing game modes to this new syntax in the move to 5.16 (homebrews, et al.)

The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.

[http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022 See this post] for an in-depth explanation of the rational behind this proposal.

----

Example usage:

<tt>MONSTERCLASSTYPES:Monster 
IMMUNETOXPPENALTYCLASSTYPES:Prestige,Monster

CLASSGROUP:PC CR:CL <tab> BONUSFEATLEVELSTARTINTERVAL:3|3 
CLASSGROUP:NPC CR:max(CL-1,0) BONUSFEATLEVELSTARTINTERVAL:3|3 
CLASSGROUP:Monster CR:0 BONUSFEATLEVELSTARTINTERVAL:3|3</tt>

Additional Weapon Damage

2008-08-05T10:38:14Z

Tir-Gwaith: /* WEAPON Token */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC. 
y = Var or formula, referenced by %1, %2, etc in (x) 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value> 

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z 
New (z) - ADDITIONALDAMAGE 

=== EQ Token ===
New Equipment tokens: 
EQ.%.ADDITIONALDAMAGE 
EQ.%.ALTADDITIONALDAMAGE 

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:12:57Z

Tir-Gwaith: /* New EQUIP / EQUIPMOD tag */ More hard returns

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC. 
y = Var or formula, referenced by %1, %2, etc in (x) 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value> 

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z 
New (z) - ADDITIONALDAMAGE 

Would we need an ALTADDITIOANLDAMAGE ??

=== EQ Token ===
New Equipment tokens: 
EQ.%.ADDITIONALDAMAGE 
EQ.%.ALTADDITIONALDAMAGE 

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:12:16Z

Tir-Gwaith: /* New EQUIP / EQUIPMOD tag */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.
y = Var or formula, referenced by %1, %2, etc in (x) 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE 
This tag takes PRExxx 
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value> 

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z 
New (z) - ADDITIONALDAMAGE 

Would we need an ALTADDITIOANLDAMAGE ??

=== EQ Token ===
New Equipment tokens: 
EQ.%.ADDITIONALDAMAGE 
EQ.%.ALTADDITIONALDAMAGE 

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:11:13Z

Tir-Gwaith: /* WEAPON Token */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.
y = Var or formula, referenced by %1, %2, etc in (x)
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z 
New (z) - ADDITIONALDAMAGE 

Would we need an ALTADDITIOANLDAMAGE ??

=== EQ Token ===
New Equipment tokens: 
EQ.%.ADDITIONALDAMAGE 
EQ.%.ALTADDITIONALDAMAGE 

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:10:53Z

Tir-Gwaith: /* EQ Token */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.
y = Var or formula, referenced by %1, %2, etc in (x)
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z
New (z) - ADDITIONALDAMAGE
Would we need an ALTADDITIOANLDAMAGE ??

=== EQ Token ===
New Equipment tokens: 
EQ.%.ADDITIONALDAMAGE 
EQ.%.ALTADDITIONALDAMAGE 

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:10:27Z

Tir-Gwaith: /* OS Token */ breakouts sub-sections

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.
y = Var or formula, referenced by %1, %2, etc in (x)
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

=== WEAPON Token ===
WEAPON.[q.][r.]s.z
New (z) - ADDITIONALDAMAGE
Would we need an ALTADDITIOANLDAMAGE ??

=== EQ Token ===
New Equipment tokens:
EQ.%.ADDITIONALDAMAGE
EQ.%.ALTADDITIONALDAMAGE

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T05:09:21Z

Tir-Gwaith: cleanup, and expanding specific examples in the Wiki to make Spec clearer.

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x|y|y
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.
y = Var or formula, referenced by %1, %2, etc in (x)
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x|y|y</tt>
Same syntax as ADDITIONALDAMAGE
This tag takes PRExxx
This tag can be used multiple times, and CLEARed in .MODs using .CLEARALL (everything) or .CLEAR.<specific (x) value>

Multiple instances from both Equip and Equipmods are joined together as a comma separated string for output just like multiple instances of SPROP is done.

'''NOTE''': +1d6 Fire +1d6 Cold looks a lot better than +1d6 Fire, +1d6 Cold, and so might want to be rethought. - Tir

=== .CLEAR / MODs ===

Clearing ADDITIONALDAMAGE tags can be done with the following syntax:

:<tt>ADDITIONALDAMAGE:.CLEAR.<exact text></tt> (to clear a specific instance)

:<tt>ADDITIONALDAMAGE:.CLEARALL</tt> (to clear all instances)

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

WEAPON.[q.][r.]s.z
New (z) - ADDITIONALDAMAGE
Would we need an ALTADDITIOANLDAMAGE ??

New Equipment tokens:
EQ.%.ADDITIONALDAMAGE
EQ.%.ALTADDITIONALDAMAGE

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T00:29:02Z

Tir-Gwaith:

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We may also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x</tt>

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

=== ISSUE ===
Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T00:27:40Z

Tir-Gwaith: /* Modification to NATURALATTACKS tag */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We may also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x</tt>

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

===ISSUE=== Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T00:26:54Z

Tir-Gwaith: /* Modification to NATURALATTACKS tag */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We may also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x</tt>

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

'''ISSUE:''' Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T00:22:42Z

Tir-Gwaith: /* Modification to NATURALATTACKS tag */

Here's something simple that PCGen can't currently handle, some weapons and monster attacks
deal additional damage beyond the standard damage roll. Flaming swords
do fire damage, many monsters attacks inject poison. This is displayed
in most stat blocks right inline with the normal damage, examples:

1d8 plus 1d6 fire 
1d6 plus poison

Currently we put this data in the equipments SPROP or an SAB tag if it's
a monster. I would like to see a way to do this in PCGen, we need
something in addition to SPROP as that tag is a dumping ground for many
things besides just additional damage. I think it can be a text string
as there are not many cases where there is something that modifies the
secondary damage value. In those rare cases where that may be needed we
could make the new tag accept variable substitution like SPROP and SAB do.

== New EQUIP / EQUIPMOD tag ==

ADDITIONALDAMAGE:x 
x = Text (Additional damage the weapon deals) 
This would be a short string (like "1d6 Acid damage") leaving any longer
descriptions and details to an SPROP or ability DESC.

Examples:

:<tt>ADDITIONALDAMAGE:Poison 
:ADDITIONALDAMAGE:1d6 Cold 
:ADDITIONALDAMAGE:%d4 Sonic|TL</tt>

We may also need a parallel tag for double weapons: 
:<tt>ALTADDITIONALDAMAGE:x</tt>

== Modification to NATURALATTACKS tag ==

Now we need a way to add this property to natural weapons, I propose we
add an additional optional variable to NATURALATTACKS at the end where
the text can be added, example:

:<tt>NATURALATTACKS:Claw,Weapon.Natural.Melee.Slashing,*2, 1d4,1d6 Acid</tt>

The new variable for NATURALATTACKS will accept a single entry and no variable substitution.

ISSUE: Adding to NATURALATTACKS tags needs either a) a cleanup on error reporting on badly formed NATURALATTACKS tags, or b) the last set of commas being optional (right now, the number of commas is NOT optional).

Adding another comma WITHOUT that will kill all NATURALATTACKS tags out there currently.

Possibily need to revamp / replace NATURALATTACKS, as it is a long and unwieldy tag currently.

== OS Token ==

Next we need a new sub token for the WEAPON OS token, ADDITIONALDAMAGE
which outputs the value of ADDITIONALDAMAGE for that weapon.

EQMOD's can have ADDITIONALDAMAGE tags to add these properties to weapons. ADDITIONALDAMAGE is additive in the same way that SPROP is (multiple tags are grouped into a single, comma separated string). This tag is pretty much identical to SPROP except for it's name and the additional ability to add this property to NATURALATTACKS.

----
See [https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1173470&group_id=25576 1173470 - BONUS: add DAMAGEDICE to WEAPON or WEAPONPROF] for the request for this feature.

Additional Weapon Damage

2008-08-05T00:20:16Z

Tir-Gwaith:

Additional Weapon Damage

2008-08-05T00:18:33Z

Tir-Gwaith:

Additional Weapon Damage

2008-08-05T00:17:50Z

Tir-Gwaith:

ASPECT tag for Abilities and Feats

2008-08-05T00:08:43Z

Tir-Gwaith:

This specifically addresses the need to model powers in 4e with ability objects. Powers use a format with a number of structured elements not unlike spells, such as Duration, Range, Attack, Hit, Miss, Sustain, etc.. The problem being that Ability Objects don't have tags to hold these stat values, other than maybe cramming them all in the DESC.

Rather than creating a number of specific tags for this purpose I propose we create one tag that has the versatility to hold all the stats. Basically all these stats need the same thing (hold a text string). This is conceptually similar to the QUALITY tag we made for use in equipment

== LST Token, Ability object ==

Tag Name: ASPECT:x|y|z|z

Variables Used (x): Text (Name of the aspect) 
Variables Used (y): Text (Value of the aspect) 
Variables Used (z): Number or formula (Optional, values to replace % in y)

What it does:

Determines that the feat or ability has the aspect and sets it's value in that feat or ability.
 Can be used multiple times within an ability but each time it should be a new aspect (name).
 The text in the y variable can use %z for replacing numerical values set by the z variable, %1 is replaced by the first z, %2 is replaced by the second z, etc..
 The y text can also use other special variables, also usable in the DESC tag:

:%CHOICE - Will replace the first associated choice in the object. 
:%LIST - Will substitute all choices comma separated into that parameter. 
:%NAME - The OUTPUTNAME or name of the object this DESC tag is in.

ASPECT tags can be modified by .MODing the feat or ability and inserting a
new ASPECT tag, Since each aspect name can hold only one value per ability
.MODing a new ASPECT tag will overwrite the only value of the aspect by that
name in the feat

Examples:

:<tt>ASPECT:Action Type|Standard Action 
:ASPECT:Attack Type|Melee weapon 
:ASPECT:Target|One creature 
:ASPECT:Attack|Strength vs. AC</tt>

And using variable substitution:

:<tt>ASPECT:Attack Type|Ranged %1|PowerRange 
:ASPECT:Effect|Double damage to %CHOICE creatures</tt>

Here's how the Lance of Faith cleric power could be modeled:

<tt>
:Lance of Faith 
:PREVARGTEQ:ClericLevel,1 
:DESC:A brilliant ray of light sears your foe with golden radiance 
:DEFINE:LanceofFaithDamageDie|1 
:DEFINE:LanceofFaithRange|5 
:BONUS:VAR|LanceofFaithDamageDie|1|PRELEVEL:MIN=21 
:CATEGORY:Power 
:TYPE:At-Will.Divine.Implement.Radiant 
:ASPECT:Action Type|Standard Action 
:ASPECT:Attack Type|Ranged %1|LanceofFaithRange 
:ASPECT:Target|One creature 
:ASPECT:Attack|Wisdom vs. Reflex 
:ASPECT:Hit|1%d8 + 2% radiant damage, and one ally you can see gains a +2 power bonus to his or her next attack roll against the target|LanceofFaithDamageDie|WIS</tt>

----

== OS Token ==

Output: In the GUI when selecting an ability all the aspects are displayed
in a string in the information pane. For example, here is how the first 4
examples above might appear in the info pane:

:Aspects: Action Type: Standard Action, Attack Type: Melee weapon, Target:
One creature, Attack: Strength vs. AC

On the OS we'll need some new tokens to support this tag. There are a number
of feat and ability tokens which use the same format but target different
groups of abilities. This is the list of tokens which will need to be revised:

:ABILITY 
:ABILITYALL 
:ABILITYAUTO 
:FEAT 
:FEATALL 
:FEATAUTO 
:VABILITY 
:VFEAT

These tokens all have DESC as a variable, the new variables will be used in the same location in the token that DESC is used. Each will have the following additions:

ASPECT - Will output a text string of all the aspects associated with the
ability in the same format as the GUI uses as described above.

ASPECT.<number> - Will output the name/value of the aspect of that number on
a 0 based index.

ASPECT.<text> - Will output the value of the named aspect.

ASPECTCOUNT - Outputs the total number of Aspects associated with the ability.

HASASPECT.<text> - Reports a Boolean result on the named aspect.

Examples using the Lance of Faith example from above:

:<tt>ABILITY.Power.0.ASPECT</tt> 
Outputs: "Action Type: Standard Action, Attack Type: Ranged 5, Target: One
creature, Attack: Wisdom vs. Reflex, Hit: 2d8 + 4 radiant damage, and one
ally you can see gains a +2 power bonus to his or her next attack roll
against the target"

:<tt>ABILITY.Power.0.ASPECT.0</tt> 
Outputs: "ActionType: Standard Action"

:<tt>ABILITY.Power.0.ASPECT.Attack Type</tt> 
Outputs: "Ranged 5"

:<tt>ABILITY.Power.0.ASPECTCOUNT</tt> 
Outputs: "5"

:<tt>ABILITY.Power.0.HASASPECT.Miss</tt> 
Outputs: "N"

Skill Cost and CSKILL Overhaul

2008-07-29T22:42:57Z

Tir-Gwaith: /* Current discussion notes */

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

== Current discussion notes ==

So I've thought about the ADDTOLEVEL issues, and I don't think that works well as proposed. The challenge in what was proposed is that CL has a specific meaning in formula, and we don't want to change that based on the context - meaning in this formula and not in others. That's very difficult to get correct... I ran through about 4 alternatives only to find they have some other problem, so it's
easiest to just define a new variable (I use CSL - that's open for discussion), and keep the concept of ADDTOLEVEL as Tir defined it.

This is an updated proposal based on the discussions - can we have someone wikify this, please? (Done, that is this page. :p - Tir)

Note there are still 4 open issues, some with "R1" "R2" (response 1,
response 2) showing the ongoing discussion that is not resolved. I
left "D" open due to the SpellList discussions that took place and
just wanted to double check on what this should be.

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

(3c) Create SKILLCOST

Syntax:
SKILLCOST:x|y|z,z
SKILLCOST:.CLEAR

Variables Used (x): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (y): ALL
Variables Used (y): Text (Class Name)
Variables Used (y): TYPE=Text (Class Type)
Variables Used (y): CLASS (usable only in CLASS files, for ease of .COPY)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL
Variables Used (z): LIST (pulls from items selected in the CHOOSE:
token in the object)

(3c1 - ISSUE C)

Make y something like like CLASS=ALL, CLASS=<classname>,
CLASS=TYPE.<class type> (there is that TYPE= vs. TYPE. thing again),
and a very funky CLASS=CLASS?

R1- Is this thinking out loud or a change you want in the syntax? If
it's actually a proposal change, then I'd prefer
CLASSLIST=<classname>. We may also want to use something like
CLASSLIST=<this> (literally using the "<this>" string) to improve
clarity vs. CLASSLIST=CLASS

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.

Skill Cost and CSKILL Overhaul

2008-07-29T22:42:19Z

Tir-Gwaith:

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

== Current discussion notes ==

So I've thought about the ADDTOLEVEL issues, and I don't think that works well as proposed. The challenge in what was proposed is that CL has a specific meaning in formula, and we don't want to change that based on the context - meaning in this formula and not in others. That's very difficult to get correct... I ran through about 4 alternatives only to find they have some other problem, so it's
easiest to just define a new variable (I use CSL - that's open for discussion), and keep the concept of ADDTOLEVEL as Tir defined it.

This is an updated proposal based on the discussions - can we have someone wikify this, please?

Note there are still 4 open issues, some with "R1" "R2" (response 1,
response 2) showing the ongoing discussion that is not resolved. I
left "D" open due to the SpellList discussions that took place and
just wanted to double check on what this should be.

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

(3c) Create SKILLCOST

Syntax:
SKILLCOST:x|y|z,z
SKILLCOST:.CLEAR

Variables Used (x): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (y): ALL
Variables Used (y): Text (Class Name)
Variables Used (y): TYPE=Text (Class Type)
Variables Used (y): CLASS (usable only in CLASS files, for ease of .COPY)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL
Variables Used (z): LIST (pulls from items selected in the CHOOSE:
token in the object)

(3c1 - ISSUE C)

Make y something like like CLASS=ALL, CLASS=<classname>,
CLASS=TYPE.<class type> (there is that TYPE= vs. TYPE. thing again),
and a very funky CLASS=CLASS?

R1- Is this thinking out loud or a change you want in the syntax? If
it's actually a proposal change, then I'd prefer
CLASSLIST=<classname>. We may also want to use something like
CLASSLIST=<this> (literally using the "<this>" string) to improve
clarity vs. CLASSLIST=CLASS

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.

Skill Cost and CSKILL Overhaul

2008-07-29T22:41:11Z

Tir-Gwaith: /* Introduction */

{| align="right"
| __TOC__
|}

==Introduction==

Pathfinder does not have the concept of "Cross-Class" skills, instead it has a Class skills and "Non Class" skills, with equal cost, but Class skills getting a bonus. Display name of Non Class skills is important, since the Cost of both Class and Non Class skills is the same.

In order to accomplish this, and remove hardcoding for future game systems, this is a proposal to move much of the back-bone framework of class skill lists into GameMode defined terms. The other major goal is to remove ambiguity, especially in the global vs. class-only tags "CSKILL" and "CCSKILL".

==Game Mode Level file changes==

# Deprecate CSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}
# Deprecate CCSKILLMAX {value placed into SKILLCOSTGROUP: MAXRANKBASE and MAXRANKINCREMENT, 2h, 2i}

==Game Mode Misc Info File changes==

(2a) Deprecate SKILLCOST_CLASS [default is 1 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2b) Deprecate SKILLCOST_CROSSCLASS [default is 2 if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2c) Deprecate SKILLCOST_EXCLUSIVE [default is 0 (illegal to "buy") if not used in Game Mode Misc Info file] {value placed into COST, 2f} 
(2d) Create a new line Tag SKILLCOSTGROUP: in Game Mode Misc Info 
(2e) Create a new token in SKILLCOSTGROUP: line, called DISPLAY, is display name 
(2f) Create a new token in SKILLCOSTGROUP: line, called COST, special value PROHIBITED (for SRD EXCLUSIVE cost), takes an integer 
(2g) Create a new variable called CSL (Class Skill Level), controlled by the ADDTOLEVEL item {see 2h}. This variable must be resolved in context to a ClassSkillList (if you don't understand what this means, it's a code thing {the source argument to getVariableValue}, not a data thing) 
(2h) Create a new token in SKILLCOSTGROUP: line, called ADDTOLEVEL, controls CSL variable 
(2i) Create a new token in SKILLCOSTGROUP: line, called MAXRANK, takes a Formula. 
(2j) Create a new token in SKILLCOSTGROUP: line, called MODIFIER, defines how the base formula for a skill is derived. (assists Pathfinder.) 
(2j1 - ISSUE A) MODIFIER cannot be used if COST is PROHIBITED?
R1- why not? I don't think it will do anything...
R2- Because if it doesn't perform a function, there isn't need to let
a user do it - leads to false expectations of behavior. 
(2k - ISSUE B) Looking at the docs, spotted a UI Change. Right now, there is Max Ranks for Class and Cross class skills. I think that will need to be dynamically set up from the GameMode defines? Would that require another tag in the SKILLCOSTGROUP line, or should we just show them all?
R1 - where is this in the UI? 
(2l) Create a new token in SKILLCOSTGROUP: line, called DEFAULTCOST: takes argument YES. Is allowed on one (and only one) SKILLCOSTGROUP line. 

Potential Examples of gamemode tags (3.5e doesn't have Exclusive, but you get the idea, separate lines in the LST file are separated by blank lines in this message) 

<gamemode 3.0/3.5>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL+3 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:CROSSCLASS DISPLAY:Cross Class COST:2 
ADDTOLEVEL:YES MAXRANK:(CSL+3)/2 MODIFIER:min(RANK,MAXRANK)+KEYSTAT

SKILLCOSTGROUP:EXCLUSIVE DISPLAY:Exclusive COST:PROHIBITED 
ADDTOLEVEL:NO MAXRANK:0 MODIFIER:KEYSTAT

<pathfinder>
SKILLCOSTGROUP:CLASS DISPLAY:Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT+if(RANK>=1,TrainedBonus,0)

SKILLCOSTGROUP:NONCLASS DISPLAY:Non-Class COST:1 
ADDTOLEVEL:YES MAXRANK:CSL MODIFIER:min(RANK,MAXRANK)+KEYSTAT

==Global LST changes==

(3a) Deprecate CSKILL, CCSKILL {replaced by SKILLCOST, 3c}

For CSKILL outside of CLASS LST files, just use SKILLCOST:
SKILLCOST:CLASS|ALL|Knowledge (Arcana)

NOTE: SKILLCOST does not behave differently in CLASS files, if you
want the effect of CSKILL in a Class LST file, you must use the Class
as an argument to SKILLCOST, see below.

(3b) Deprecate MONCSKILL, MONCCSKILL {replaced by SKILLCOST, 3c}

MONCSKILL changes to look like:
SKILLCOST:CLASS|TYPE=Monster|Knowledge (Arcana)

(3c) Create SKILLCOST

Syntax:
SKILLCOST:x|y|z,z
SKILLCOST:.CLEAR

Variables Used (x): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (y): ALL
Variables Used (y): Text (Class Name)
Variables Used (y): TYPE=Text (Class Type)
Variables Used (y): CLASS (usable only in CLASS files, for ease of .COPY)
Variables Used (z): Text (Skill name)
Variables Used (z): TYPE=Text (Skill type)
Variables Used (z): ALL
Variables Used (z): LIST (pulls from items selected in the CHOOSE:
token in the object)

(3c1 - ISSUE C)

Make y something like like CLASS=ALL, CLASS=<classname>,
CLASS=TYPE.<class type> (there is that TYPE= vs. TYPE. thing again),
and a very funky CLASS=CLASS?

R1- Is this thinking out loud or a change you want in the syntax? If
it's actually a proposal change, then I'd prefer
CLASSLIST=<classname>. We may also want to use something like
CLASSLIST=<this> (literally using the "<this>" string) to improve
clarity vs. CLASSLIST=CLASS

(3d - ISSUE D)

There are some interactions we need to resolve:

CLASS:Foo SKILLCOST:CLASS|CLASS|Sk1 SKILLCOST:CLASS|Foo|Sk2
SKILLCOST:CLASS|ANY|Sk3

CLASS:Bar=Foo.COPY SKILLLIST:1,Foo

So what does Bar's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:BooHoo SKILLLIST:1,Foo

So what does BooHoo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

CLASS:Goo=Foo.COPY SKILLLIST:1,Ranger

So what does Goo's Class Skill List look like? Does it contain Sk1,
Sk2, and/or Sk3?

The key questions center around whether CLASS in this case is a
"special" entry that places the item on to a "Class Skill List" (like
the CLASSES token in the Skill file does)... and whether other entries
that assign directly to the class from within the class perform the
same special function, etc.

Examples using Syntax option #2:

in class.lst, CSKILL goes to: SKILLCAT:CLASS|CLASS|<skill1>,<skill2>

in other object files, CSKILL goes to:
SKILLCAT:CLASS|ALL|<skill1>,<skill2>

CCSKILL in class goes to SKILLCAT:CROSSCLASS|CLASS|<skill1>,<skill2>

MONCSKILL goes to: SKILLCAT:CLASS|TYPE=Monster|<skill1>,<skill2>

==Global CHOOSE changes==

(4a) Deprecate CHOOSE:CCSKILLLIST, CHOOSE:CSKILLS,
CHOOSE:NONCLASSSKILLLIST, CHOOSE:SKILLS, CHOOSE:SKILLSNAMED,
CHOOSE:SKILLSNAMEDTOCCSKILL, CHOOSE:SKILLSNAMEDTOCSKILL {replaced by a
combination of 3c [LIST] and 4b}

CHOOSE:SKILLS [currently has no args] would change to:

CHOOSE:SKILLS|USEUNTRAINED=YES|MINRANK=1

CHOOSE:SKILLSNAMEDTOCSKILL|CROSSCLASS would change to:

CHOOSE:SKILLS|SKILLCOST=CROSSCLASS
SKILLCOST:CLASS|LIST

others have similar changes

(4b) Rebuild CHOOSE:SKILLS similar to the CHOOSE:SPELLS in 5.14

Tag Name: CHOOSE:SKILLS|x,y|x|y
Variables Used (x): Text (Skill name)
Variables Used (x): Text% (Skill name pattern)
Variables Used (x): TYPE=Text (Skill type)
Variables Used (y): ALL
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): !SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): MINRANK=Number (Mininum Number of Ranks)
Variables Used (y): MAXRANK=Number (Maximum Number of Ranks)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")

, is AND
| is OR

CHOOSE:SKILLS|MINRANK=1,MAXRANK=4|TYPE=Knowledge,MAXRANK=4

List all skills where
- the PC has at least one rank and at most 4 ranks
OR
- the Skill is TYPE=Knowledge and the PC has <= 4 ranks

==Global ADD Changes==

(5a) Deprecate ADD:CLASSSKILLS
(5b) Build ADD:SKILLCOST

Tag Name: ADD:SKILLCOST:v|w|u|x,y
Variables Used (v): Skill Cost from Game Mode File (COST in Game Mode
file for this Skill Cost must NOT be PROHIBITED)
Variables Used (w): Number, Variable or Formula (Number of choices
granted. Optional)
Variables Used (x): Text (Name of skill)
Variables Used (x): TYPE=Text (Type of skill)
Variables Used (y): ANY
Variables Used (y): CLASSLIST=Text (Class name)
Variables Used (y): SKILLCOST=Text (Skill Cost from Game Mode File)
Variables Used (y): SKILLCOST!=Text (Skill Cost from Game Mode File)
Variables Used (y): USEUNTRAINED=Text ("YES" or "NO")
Variables Used (u): [OPTIONAL] AUTORANK=Number (Number of free ranks
granted to selections)

==Global PRExxx changes==

(6a) Deprecate PRECSKILL

(6b) Build PRESKILLCOST

Syntax:
PRESKILLCOST:x,y,z,z

x is a number
y is a Skill Cost from the Game Mode File
z is a skill or TYPE=Text

==Skill LST Changes==

(7a) Deprecate EXCLUSIVE:YES {replaced by 7b, DEFAULTSKILLCOST:EXCLUSIVE}

(7b) Create a new SKILL token, DEFAULTSKILLCOST, can take any SKILLCOSTGROUP as the argument

DEFAULTSKILLCOST:EXCLUSIVE replaces EXCLUSIVE:YES in Skills for those that start as "EXCLUSIVE" rather than CROSSCLASS.