PCGen Wiki - User contributions [en]

GITHUB and proper procedures

2014-12-13T20:30:24Z

Zaister: /* Linux */

==Intro==
GITHUB is a wonderful collaboration tool for developers. We at PCGen are migrating from the SVN repository we host of SF to the free hosting at GITHUB. Most people should be familiar with GIT and GITHUB, but we'll go over what our procedures are:

===Contributor Setup===
If you plan on being a developer and contributing follow these steps:

* 1) Sign in to github with your account. (You should have a SSH key)
* 2) Navigate to the pcgen project you wish to contribute too and click the FORK button. (See below for link)
* 3) Navigate to your FORK of the pcgen project and use the SHH link for cloning a local copy
* 4) Choose a local folder to house your local copy and clone the copy there.
* 5) Add a remote repository and link it to the main pcgen project (or upstream) -- OPTIONAL STEP: This allows fast update to your local copy from the main project.
* 6) Once your local copy is downloaded, do a git checkout and name your branch* (See Branch Naming practices below)
* 7) Once you have finished working on your feature/bug branch, do the git equivalent of 'add', 'commit', and then 'push' those changes to your remote repository. (See GIT Commit Summary Practices)
* 8) Do a PR (Pull Request) from your repository to the main pcgen repository, using the branch you pushed in - make an explanation summary or JIRA ID

===Just want a Copy of a project===
If you want to maintain an up-to-date copy of the pcgen project repository, but do not have plans to contribute in the near future, you may easily do the following:
* 1) Navigate to the pcgen project repository (See below for link)
* 2) Click the "Link" of your choice for cloning a local copy - SSH is superior, but you may opt for https.
* 3) Choose a local folder to house your local copy and clone the copy there.
* NOTE: This will allow you to grab updates from the project, but not push any changes.

Of course, you are always able to use the download, to get a snapshot of the project. This is the least recommended method of having access to the project.

===Feature/Bug Branch Naming Practices:===
* All Features or Bugs should have a corresponding JIRA ID, example: CODE-1234, or DATA-4321. Your Branch should be JIRA-ID_Title, example: DATA-1234_Fix_Bard_Skills

SSH Keys are useful and should be used whenever possible. For Windows, PuttyGen will allow you to create your own SSH Key.

===Git Commit Summary Practices===
* Each Commit you make should include the JIRA-ID for point of reference and JIRA integration tracking
* Each Commit you make should include enough detail to understand what you were working on

* Before PUSHING, you may do any number of things to clean up before you PUSH to the remote. Please review the options from reputable GIT information sites for proper usage.
* Ideally, you should squash your commits into one commit before pushing into your remote.

===PCGen Projects===
All Active PCGen Repositories are held under the Username "PCGen" which is our organization on github.com. You can find the repositories we host here: https://github.com/PCGen

* Our Main Development Program is "PCGen" (Planned active as of December 22nd, 2014)
* Our New Source Development is NewSources (Active Now)

===GIT TOOLS===
* Command line for GIT is by far the superior method. However, we have found tools that our developers like to use and recommend them as easier alternatives to the command line if you choose to do so.

====Windows====
* Atlassian's free SourceTree GUI program
* TortoiseGIT (Shell integration)

====Mac====
* ...Pending...

====Linux====
* RabbitVCS (Gnome only, integrates with Nautilus)

Meeting Time

2014-11-20T08:23:08Z

Zaister: /* Availability for London Time Meetings (locked at 10 PM London Time) */

{| align="right"
| __TOC__
|}

=Introduction=

The [[Board of Directors|BoD]] meetings are on approximately every fortnight.

=Timezones=

{| border="1"
! Name !! Current Timezone !! Offset from GMT
|-
| [[Martijn Verburg]] || GMT || 0
|-
| [[Chris Chandler]] || EST/EDT || -5/-4
|-
| [[Tom Parker]] || EDT || -4
|-
| [[James Dempsey]] || AEDT || +11
|-
| [[Eric C Smith]] || EST/EDT || -5/-4
|-
| [[LegacyKing|Andrew Maitland]] || PST/PDT || -8/-7
|-
| [[Paul W. King]] || EST/EDT || -5/-4
|-
| [[User:Nylanfs|Paul Grosse]] || EST/EDT || -5/-4
|-
| [[Anestis Kozakis]] || AEST/AEDST || +10/+11
|-
| [[David R. Bender]] || EST/EDT@ || -5/-4@
|-
| [[Distant Scholar|Doug Limmer]] || CST/CDT || -6/-5
|-
| [[Stefan Radermacher]] || CET/CEST || +1/+2
|}

@ Current East Coast USA time zone

=Availability for Eastern (US) Meetings (locked at 12 PM or 1PM Australian Eastern Time [USA ET slot shifts to accommodate])=

*This is currently UTC 2 AM (next day)
*This is currently London 2 AM (next day)
*This is currently Europe 3 AM (next day)
*This is currently 9 PM EST (USA) (same day)
*This is currently 6 PM PST (USA) (same day)
*This is currently 1 PM Canberra (next day)
*These currency statements are made as of Jan 22, 2011:
http://www.timeanddate.com/worldclock/fixedtime.html?day=7&month=2&year=2011&hour=21&min=0&sec=0&p1=179

{| border="1"
! Vote !! Team !! Name !! Mon (Tue UTC) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| 2nd || Tracker || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No (effective Jan 7th 2011)|| Yes || No || No || Yes || Yes || Yes
|-
| SB || Admin || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Yes || Yes || Mostly || No || No || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| 2nd || Release || [[James Dempsey]] || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| SB || Content || [[Chris Chandler]]^^^ || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || No || No || No || Yes
|-
| 2nd || OS || [[Stefan Radermacher]] || No || No || No || No || No || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || Yes || Yes || Yes || Yes || No || No || No
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || Mostly || Mostly || Mostly || Mostly || No || Mostly || Mostly
|-
| 2nd || Advert || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || For now || No || Yes || Yes || Yes
|}

^ = (8PM EST to 10PM EST and 4AM EST to 9AM EST) 
^^ = Evenings after 6 pm Mon-Fri, AEST or AEDST 
^^^ = Mornings/Afternoons 7AM EST to 1PM EST 
PST is GMT -8 
MST is GMT -7 
EST is GMT -5

=Availability for Australia East Meetings (locked at 10 PM Australian Eastern Time)=

*This is currently UTC 11 AM (same day)
*This is currently London 11 AM (same day)
*This is currently Europe 12 PM (same day)
*This is currently 6 AM EST (USA) (same day)
*This is currently 3 AM PST (USA) (same day)
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=57

{| border="1"
! Vote !! Team !! Name !! Mon !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No || No || No || No || No || No || No
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || With Notice || Sometimes || Sometimes || Mostly || Mostly || No || No
|-
| SB || Code || [[James Dempsey]]^ || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| 2nd || Release || [[James Dempsey]] || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| SB || Content || [[Chris Chandler]] || Yes || Yes || Yes || Yes || Yes || No || No
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || No || No || No || No || No || Sometimes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Stefan Radermacher]] || Mostly || Mostly || Mostly || Mostly || Mostly || Mostly || Mostly
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Douglas Limmer]] || Rarely || Rarely || Rarely || Rarely || Rarely || Rarely || No
|}

=Availability for London Time Meetings (locked at 10 PM London Time)=

*This is currently UTC 10 PM
*This is currently Europe 11 PM
*This is currently 2 PM PST (USA) (same day)
*This is currently 5 PM EST (USA) (same day)
*This is currently 9 AM the following day, Canberra
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=136

{| border="1"
! Vote !! Team !! Name !! Mon (Tue Canberra) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No|| Yes|| No || No|| Yes || Yes || Yes
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Mostly || Mostly || No || No || Possibly || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || No|| No || No || No || Yes || Yes || No
|-
| 2nd || Release || [[James Dempsey]] || No|| No || No || No || Yes || Yes || No
|-
| SB || Content || [[Chris Chandler]] || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Sometimes || Sometimes || Sometimes || Sometimes || Sometimes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Stefan Radermacher]] || No || Yes || No || No || Yes || Yes || Yes
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || No || Yes || Yes || Yes || Yes
|}

Meeting Time

2014-11-20T08:21:01Z

Zaister: /* Availability for Australia East Meetings (locked at 10 PM Australian Eastern Time) */

{| align="right"
| __TOC__
|}

=Introduction=

The [[Board of Directors|BoD]] meetings are on approximately every fortnight.

=Timezones=

{| border="1"
! Name !! Current Timezone !! Offset from GMT
|-
| [[Martijn Verburg]] || GMT || 0
|-
| [[Chris Chandler]] || EST/EDT || -5/-4
|-
| [[Tom Parker]] || EDT || -4
|-
| [[James Dempsey]] || AEDT || +11
|-
| [[Eric C Smith]] || EST/EDT || -5/-4
|-
| [[LegacyKing|Andrew Maitland]] || PST/PDT || -8/-7
|-
| [[Paul W. King]] || EST/EDT || -5/-4
|-
| [[User:Nylanfs|Paul Grosse]] || EST/EDT || -5/-4
|-
| [[Anestis Kozakis]] || AEST/AEDST || +10/+11
|-
| [[David R. Bender]] || EST/EDT@ || -5/-4@
|-
| [[Distant Scholar|Doug Limmer]] || CST/CDT || -6/-5
|-
| [[Stefan Radermacher]] || CET/CEST || +1/+2
|}

@ Current East Coast USA time zone

=Availability for Eastern (US) Meetings (locked at 12 PM or 1PM Australian Eastern Time [USA ET slot shifts to accommodate])=

*This is currently UTC 2 AM (next day)
*This is currently London 2 AM (next day)
*This is currently Europe 3 AM (next day)
*This is currently 9 PM EST (USA) (same day)
*This is currently 6 PM PST (USA) (same day)
*This is currently 1 PM Canberra (next day)
*These currency statements are made as of Jan 22, 2011:
http://www.timeanddate.com/worldclock/fixedtime.html?day=7&month=2&year=2011&hour=21&min=0&sec=0&p1=179

{| border="1"
! Vote !! Team !! Name !! Mon (Tue UTC) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| 2nd || Tracker || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No (effective Jan 7th 2011)|| Yes || No || No || Yes || Yes || Yes
|-
| SB || Admin || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Yes || Yes || Mostly || No || No || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| 2nd || Release || [[James Dempsey]] || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| SB || Content || [[Chris Chandler]]^^^ || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || No || No || No || Yes
|-
| 2nd || OS || [[Stefan Radermacher]] || No || No || No || No || No || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || Yes || Yes || Yes || Yes || No || No || No
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || Mostly || Mostly || Mostly || Mostly || No || Mostly || Mostly
|-
| 2nd || Advert || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || For now || No || Yes || Yes || Yes
|}

^ = (8PM EST to 10PM EST and 4AM EST to 9AM EST) 
^^ = Evenings after 6 pm Mon-Fri, AEST or AEDST 
^^^ = Mornings/Afternoons 7AM EST to 1PM EST 
PST is GMT -8 
MST is GMT -7 
EST is GMT -5

=Availability for Australia East Meetings (locked at 10 PM Australian Eastern Time)=

*This is currently UTC 11 AM (same day)
*This is currently London 11 AM (same day)
*This is currently Europe 12 PM (same day)
*This is currently 6 AM EST (USA) (same day)
*This is currently 3 AM PST (USA) (same day)
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=57

{| border="1"
! Vote !! Team !! Name !! Mon !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No || No || No || No || No || No || No
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || With Notice || Sometimes || Sometimes || Mostly || Mostly || No || No
|-
| SB || Code || [[James Dempsey]]^ || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| 2nd || Release || [[James Dempsey]] || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| SB || Content || [[Chris Chandler]] || Yes || Yes || Yes || Yes || Yes || No || No
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || No || No || No || No || No || Sometimes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Stefan Radermacher]] || Mostly || Mostly || Mostly || Mostly || Mostly || Mostly || Mostly
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Douglas Limmer]] || Rarely || Rarely || Rarely || Rarely || Rarely || Rarely || No
|}

=Availability for London Time Meetings (locked at 10 PM London Time)=

*This is currently UTC 10 PM
*This is currently 2 PM PST (USA) (same day)
*This is currently 5 PM EST (USA) (same day)
*This is currently 9 AM the following day, Canberra
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=136

{| border="1"
! Vote !! Team !! Name !! Mon (Tue Canberra) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No|| Yes|| No || No|| Yes || Yes || Yes
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Mostly || Mostly || No || No || Possibly || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || No|| No || No || No || Yes || Yes || No
|-
| 2nd || Release || [[James Dempsey]] || No|| No || No || No || Yes || Yes || No
|-
| SB || Content || [[Chris Chandler]] || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Sometimes || Sometimes || Sometimes || Sometimes || Sometimes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Chuck Pint]] || Mostly || Mostly || Mostly || Mostly || Mostly || Sometimes || Sometimes
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || No || Yes || Yes || Yes || Yes
|}

Meeting Time

2014-11-20T08:19:41Z

Zaister: /* Availability for Eastern (US) Meetings (locked at 12 PM or 1PM Australian Eastern Time [USA ET slot shifts to accommodate]) */

{| align="right"
| __TOC__
|}

=Introduction=

The [[Board of Directors|BoD]] meetings are on approximately every fortnight.

=Timezones=

{| border="1"
! Name !! Current Timezone !! Offset from GMT
|-
| [[Martijn Verburg]] || GMT || 0
|-
| [[Chris Chandler]] || EST/EDT || -5/-4
|-
| [[Tom Parker]] || EDT || -4
|-
| [[James Dempsey]] || AEDT || +11
|-
| [[Eric C Smith]] || EST/EDT || -5/-4
|-
| [[LegacyKing|Andrew Maitland]] || PST/PDT || -8/-7
|-
| [[Paul W. King]] || EST/EDT || -5/-4
|-
| [[User:Nylanfs|Paul Grosse]] || EST/EDT || -5/-4
|-
| [[Anestis Kozakis]] || AEST/AEDST || +10/+11
|-
| [[David R. Bender]] || EST/EDT@ || -5/-4@
|-
| [[Distant Scholar|Doug Limmer]] || CST/CDT || -6/-5
|-
| [[Stefan Radermacher]] || CET/CEST || +1/+2
|}

@ Current East Coast USA time zone

=Availability for Eastern (US) Meetings (locked at 12 PM or 1PM Australian Eastern Time [USA ET slot shifts to accommodate])=

*This is currently UTC 2 AM (next day)
*This is currently London 2 AM (next day)
*This is currently Europe 3 AM (next day)
*This is currently 9 PM EST (USA) (same day)
*This is currently 6 PM PST (USA) (same day)
*This is currently 1 PM Canberra (next day)
*These currency statements are made as of Jan 22, 2011:
http://www.timeanddate.com/worldclock/fixedtime.html?day=7&month=2&year=2011&hour=21&min=0&sec=0&p1=179

{| border="1"
! Vote !! Team !! Name !! Mon (Tue UTC) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| 2nd || Tracker || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No (effective Jan 7th 2011)|| Yes || No || No || Yes || Yes || Yes
|-
| SB || Admin || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Yes || Yes || Mostly || No || No || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| 2nd || Release || [[James Dempsey]] || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| SB || Content || [[Chris Chandler]]^^^ || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || No || No || No || Yes
|-
| 2nd || OS || [[Stefan Radermacher]] || No || No || No || No || No || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || Yes || Yes || Yes || Yes || No || No || No
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || Mostly || Mostly || Mostly || Mostly || No || Mostly || Mostly
|-
| 2nd || Advert || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || For now || No || Yes || Yes || Yes
|}

^ = (8PM EST to 10PM EST and 4AM EST to 9AM EST) 
^^ = Evenings after 6 pm Mon-Fri, AEST or AEDST 
^^^ = Mornings/Afternoons 7AM EST to 1PM EST 
PST is GMT -8 
MST is GMT -7 
EST is GMT -5

=Availability for Australia East Meetings (locked at 10 PM Australian Eastern Time)=

*This is currently UTC 11 AM (same day)
*This is currently London 11 AM (same day)
*This is currently 6 AM EST (USA) (same day)
*This is currently 3 AM PST (USA) (same day)
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=57

{| border="1"
! Vote !! Team !! Name !! Mon !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No || No || No || No || No || No || No
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || With Notice || Sometimes || Sometimes || Mostly || Mostly || No || No
|-
| SB || Code || [[James Dempsey]]^ || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| 2nd || Release || [[James Dempsey]] || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| SB || Content || [[Chris Chandler]] || Yes || Yes || Yes || Yes || Yes || No || No
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || No || No || No || No || No || Sometimes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Chuck Pint]] || No || No || No || No || No || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Douglas Limmer]] || Rarely || Rarely || Rarely || Rarely || Rarely || Rarely || No
|}

=Availability for London Time Meetings (locked at 10 PM London Time)=

*This is currently UTC 10 PM
*This is currently 2 PM PST (USA) (same day)
*This is currently 5 PM EST (USA) (same day)
*This is currently 9 AM the following day, Canberra
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=136

{| border="1"
! Vote !! Team !! Name !! Mon (Tue Canberra) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No|| Yes|| No || No|| Yes || Yes || Yes
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Mostly || Mostly || No || No || Possibly || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || No|| No || No || No || Yes || Yes || No
|-
| 2nd || Release || [[James Dempsey]] || No|| No || No || No || Yes || Yes || No
|-
| SB || Content || [[Chris Chandler]] || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Sometimes || Sometimes || Sometimes || Sometimes || Sometimes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Chuck Pint]] || Mostly || Mostly || Mostly || Mostly || Mostly || Sometimes || Sometimes
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || No || Yes || Yes || Yes || Yes
|}

Meeting Time

2014-11-20T08:18:14Z

Zaister: /* Timezones */

{| align="right"
| __TOC__
|}

=Introduction=

The [[Board of Directors|BoD]] meetings are on approximately every fortnight.

=Timezones=

{| border="1"
! Name !! Current Timezone !! Offset from GMT
|-
| [[Martijn Verburg]] || GMT || 0
|-
| [[Chris Chandler]] || EST/EDT || -5/-4
|-
| [[Tom Parker]] || EDT || -4
|-
| [[James Dempsey]] || AEDT || +11
|-
| [[Eric C Smith]] || EST/EDT || -5/-4
|-
| [[LegacyKing|Andrew Maitland]] || PST/PDT || -8/-7
|-
| [[Paul W. King]] || EST/EDT || -5/-4
|-
| [[User:Nylanfs|Paul Grosse]] || EST/EDT || -5/-4
|-
| [[Anestis Kozakis]] || AEST/AEDST || +10/+11
|-
| [[David R. Bender]] || EST/EDT@ || -5/-4@
|-
| [[Distant Scholar|Doug Limmer]] || CST/CDT || -6/-5
|-
| [[Stefan Radermacher]] || CET/CEST || +1/+2
|}

@ Current East Coast USA time zone

=Availability for Eastern (US) Meetings (locked at 12 PM or 1PM Australian Eastern Time [USA ET slot shifts to accommodate])=

*This is currently UTC 2 AM (next day)
*This is currently London 2 AM (next day)
*This is currently 9 PM EST (USA) (same day)
*This is currently 6 PM PST (USA) (same day)
*This is currently 1 PM Canberra (next day)
*These currency statements are made as of Jan 22, 2011:
http://www.timeanddate.com/worldclock/fixedtime.html?day=7&month=2&year=2011&hour=21&min=0&sec=0&p1=179

{| border="1"
! Vote !! Team !! Name !! Mon (Tue UTC) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| 2nd || Tracker || [[Martijn Verburg]] || No || No || No || No || No || No || No
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No (effective Jan 7th 2011)|| Yes || No || No || Yes || Yes || Yes
|-
| SB || Admin || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Yes || Yes || Mostly || No || No || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| 2nd || Release || [[James Dempsey]] || Mostly || Mostly || Mostly || Mostly || Yes || Mostly || Mostly
|-
| SB || Content || [[Chris Chandler]]^^^ || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || No || No || No || Yes
|-
| 2nd || OS || [[Chuck Pint]] || Yes || Mostly || Mostly || No || Mostly || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || Yes || Yes || Yes || Yes || No || No || No
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || Mostly || Mostly || Mostly || Mostly || No || Mostly || Mostly
|-
| 2nd || Advert || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || 9pm-Late, 10pm-Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || For now || No || Yes || Yes || Yes
|}

^ = (8PM EST to 10PM EST and 4AM EST to 9AM EST) 
^^ = Evenings after 6 pm Mon-Fri, AEST or AEDST 
^^^ = Mornings/Afternoons 7AM EST to 1PM EST 
PST is GMT -8 
MST is GMT -7 
EST is GMT -5

=Availability for Australia East Meetings (locked at 10 PM Australian Eastern Time)=

*This is currently UTC 11 AM (same day)
*This is currently London 11 AM (same day)
*This is currently 6 AM EST (USA) (same day)
*This is currently 3 AM PST (USA) (same day)
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=57

{| border="1"
! Vote !! Team !! Name !! Mon !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Yes || Mostly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No || No || No || No || No || No || No
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || With Notice || Sometimes || Sometimes || Mostly || Mostly || No || No
|-
| SB || Code || [[James Dempsey]]^ || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| 2nd || Release || [[James Dempsey]] || Yes || No || Yes || No || Mostly || Mostly || Yes
|-
| SB || Content || [[Chris Chandler]] || Yes || Yes || Yes || Yes || Yes || No || No
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || No || No || No || No || No || Sometimes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Chuck Pint]] || No || No || No || No || No || No || No
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Douglas Limmer]] || Rarely || Rarely || Rarely || Rarely || Rarely || Rarely || No
|}

=Availability for London Time Meetings (locked at 10 PM London Time)=

*This is currently UTC 10 PM
*This is currently 2 PM PST (USA) (same day)
*This is currently 5 PM EST (USA) (same day)
*This is currently 9 AM the following day, Canberra
*These currency statements are made as of Nov 22, 2010:
http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=22&year=2010&hour=22&min=0&sec=0&p1=136

{| border="1"
! Vote !! Team !! Name !! Mon (Tue Canberra) !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| Chair || Chair || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| 2nd || Tracker || [[Martijn Verburg]] || Yes || Yes || Yes || Yes || Possibly || Possibly || Mostly
|-
| Chair || Chair 2nd || [[LegacyKing|Andrew Maitland]] || No|| Yes|| No || No|| Yes || Yes || Yes
|-
| SB || Admin ||[[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| 2nd || Data || [[LegacyKing|Andrew Maitland]] || - || - || - || - || - || - || -
|-
| SB || Arch || [[Tom Parker]] || Mostly || Mostly || No || No || Possibly || No || With Notice
|-
| SB || Code || [[James Dempsey]]^ || No|| No || No || No || Yes || Yes || No
|-
| 2nd || Release || [[James Dempsey]] || No|| No || No || No || Yes || Yes || No
|-
| SB || Content || [[Chris Chandler]] || No || No || No || No || No || Possibly || Yes
|-
| SB || PR || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || Sometimes || Sometimes || Sometimes || Sometimes || Sometimes || Yes || Yes
|-
| 2nd || Docs || [[Eric C Smith]] || Mostly || Mostly || Mostly || Mostly || Mostly || No || No
|-
| 2nd || OS || [[Chuck Pint]] || Mostly || Mostly || Mostly || Mostly || Mostly || Sometimes || Sometimes
|-
| 2nd || License || [[User:Nylanfs|Paul Grosse]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || PL || [[Paul W. King]] (9PM EST+) || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Web || [[Anestis Kozakis]]^^ || ? || ? || ? || ? || ? || ? || ?
|-
| 2nd || Advert || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || PR || [[David R. Bender]] || Yes || Yes || Yes || Yes || Yes || Yes || Yes
|-
| 2nd || Arch || TBA || No || No || No || No || No || No || No
|-
| 2nd || Data || [[Distant Scholar|Doug Limmer]] || Yes || Yes || No || Yes || Yes || Yes || Yes
|}

Board of Directors

2014-11-20T08:14:40Z

Zaister:

{| align="right"
| __TOC__
|}
=Introduction=
The PCGen Board of Directors (BoD) governs the project. Each major team is represented by one [[Explanation_of_Teams#Silverback|Silverback]] (SB) and at least one [[Explanation_of_Teams#2nd|2nd]] for each team/sub team (in case of SB absence).

=Mission Statement=
To provide overall governance to PCGen to ensure that it continues to be a leader in RPG character Generation

=Resources=
* [[Meeting Time]]
* [[Meeting Logs]]
* [[Bylaws]]
* [[Policies]]
* [[Holidays]]

=Active Members=

===Chair Monkey===
[[Martijn Verburg]] - The day to day project chairperson

===Chair Monkey Backup===
[[LegacyKing|Andrew Maitland]] - Chairs meetings

===Silverbacks===
The Team leads
{| class="wikitable" border="1"
! Name !! Team
|-
| [[Tom Parker]] || [[Architecture]]
|-
| [[James Dempsey]] || [[Code]]
|-
| [[LegacyKing|Andrew Maitland]] || [[Content]]
|-
| Anestis Kozakis || [[Admin]]
|-
| [[Paul Grosse]] || [[Public Relations]]
|}

===Seconds===
{| class="wikitable" border="1"
! Name !! Team !! Subteam
|-
| TBA || [[Architecture]] ||
|-
| TBA || [[Code]] ||
|-
| Douglas Limmer || [[Content]] || [[Data]]
|-
| [[Eric C Smith]] || [[Content]] || [[Documentation]]
|-
| [[Stefan Radermacher]] || [[Content]] || [[Output Sheets]]
|-
| [[Paul W. King]] || [[Public Relations]] || [[Publisher Liaison]] ([[Publisher Liaison|PL]])
|-
| TBA || [[Public Relations]] || [[Data License]]
|-
| TBA || [[Public Relations]] || [[Advertising]]
|-
| [[James Dempsey]] || [[Admin]] || [[Release]]
|-
| [[Martijn Verburg]] || [[Admin]] || [[Tracker]]
|-
| TBA || [[Admin]] || [[Website]]
|}

=Inactive Members=

===Benevolent Dictator===
[[Bryan McRoberts]] - The Project Creator

===Chair Monkey Backup===
[[Eddy Anthony]] - Chairs meetings

===Silverback===
{| class="wikitable" border="1"
! Name !! Team
|-
| [[Frank Kliewe]] || [[Content]]
|-
| [[Eddy Anthony]] || [[Content]]
|}

===Seconds===
{| class="wikitable" border="1"
! Name !! Team !! Subteam
|-
| Devon Jones || [[Architecture]] ||
|-
| Devon Jones || [[Code]] ||
|}

Stefan Radermacher

2014-11-20T08:13:54Z

Zaister:

{| align="right"
| __TOC__
|}

=Teams I belong to=
{| border=1
|-
! Team !! Rank
|-
| [[Code]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Data]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Output Sheets]] || [[Explanation_of_Teams#Second|Second]]
|-
| [[Content]] - [[Documentation]] || [[Explanation_of_Teams#Gibbon|Gibbon]]
|}

=Contact Details=
{| border=1
|-
| Timezone || GMT+1
|-
| Email || pcgen AT zaister DOT de
|-
| AIM ID || -
|-
| MSN ID || -
|-
| Yahoo Chat ID || zaister
|-
| ICQ || 6510566
|-
| Jabber || zaister AT kdetalk DOT net
|-
| IRC || Zaister
|-
| Google Talk || -
|}

Output Sheets

2014-11-20T08:13:02Z

Zaister:

{| align="right"
| __TOC__
|}
=Introduction=

Welcome to the Wiki section of the Output Sheet team! The OS team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To create useful output formats for PCGen data for screen viewing, printing or import into other gaming utilities that meet the high standards of our community.

=Links=
* [[Sheet Groupings]] - A List of all of the Sheets and how they should be treated
* [[OS How-To]] - Barak's Beginners Guide to OS Templating
* [[OS Sheet Improvement Discussion]]

=Active Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation of Teams#Second|2nd]]===
* [[Stefan Radermacher]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]]
* [[Chuck Pint]] - Inactive

===[[Explanation of Teams#Gibbon|Gibbon]]===
* [[Martijn Verburg]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Eddy Anthony]] - Inactive

===[[Explanation of Teams#Lemur|Lemur]]===
* Fluxxdog - Inactive
* [[Paul W. King]] - Inactive
* [[Tir Gwaith]] - Inactive

=Inactive Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* gawaine42, Open RPG

===[[Explanation_of_Teams#Lemur|Lemur]]===
* [[Jason Horner]]
* Keith Ratliff
* [[User:Nylanfs|Paul Grosse]]
* Tony Lavalle

Stefan Radermacher

2014-11-19T09:10:59Z

Zaister:

{| align="right"
| __TOC__
|}

=Teams I belong to=
{| border=1
|-
! Team !! Rank
|-
| [[Code]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Data]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Output Sheets]] || [[Explanation_of_Teams#Chimp|Chimp]]
|-
| [[Content]] - [[Documentation]] || [[Explanation_of_Teams#Gibbon|Gibbon]]
|}

=Contact Details=
{| border=1
|-
| Timezone || GMT+1
|-
| Email || pcgen AT zaister DOT de
|-
| AIM ID || -
|-
| MSN ID || -
|-
| Yahoo Chat ID || zaister
|-
| ICQ || 6510566
|-
| Jabber || zaister AT kdetalk DOT net
|-
| IRC || Zaister
|-
| Google Talk || -
|}

Output Sheets

2014-10-08T05:47:13Z

Zaister:

{| align="right"
| __TOC__
|}
=Introduction=

Welcome to the Wiki section of the Output Sheet team! The OS team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To create useful output formats for PCGen data for screen viewing, printing or import into other gaming utilities that meet the high standards of our community.

=Links=
* [[Sheet Groupings]] - A List of all of the Sheets and how they should be treated
* [[OS How-To]] - Barak's Beginners Guide to OS Templating
* [[OS Sheet Improvement Discussion]]

=Active Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation of Teams#Second|2nd]]===
* [[Chuck Pint]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]]
* [[Chuck Pint]]
* [[Stefan Radermacher]]

===[[Explanation of Teams#Gibbon|Gibbon]]===
* [[Martijn Verburg]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Eddy Anthony]]

===[[Explanation of Teams#Lemur|Lemur]]===
* Fluxxdog
* [[Paul W. King]]
* [[Tir Gwaith]]
* [[LegacyKing|Andrew Maitland]]

=Inactive Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* gawaine42, Open RPG

===[[Explanation_of_Teams#Lemur|Lemur]]===
* [[Jason Horner]]
* Keith Ratliff
* [[User:Nylanfs|Paul Grosse]]
* Tony Lavalle

Code

2014-10-08T05:46:08Z

Zaister: /* Active Team Members */

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the Wiki section for the Code Monkey team!

=Mission Statement=
'''TBA'''

=Resources=
* [[Developers Meeting]]
* [[Dev Meeting Log 20090429]]
* [[Dev Meeting Log 20090815]]
* [[Dev Meeting Log 20090911]]
* [[Dev Meeting Log 20091017]]
* [[Dev Meeting Log 20091114]]
* [[Dev Meeting Log 20120309]]
* [[Dev Meeting Log 20120429]]
* [[Dev Meeting Log 20121103]]
* [[Dev Meeting Log 20140627]]

==For New Starters==
* [[Joining the Code Team]] General steps to take to prepare yourself
* [[Code Monkey Introduction]]

==Developer Environment==
* [[Basic Developer Setup]]
* [[Subversion Setup]]
* [[Merging]] with SVN
* [[Building PCGen]], also see [[Gradle]]
* [[Continuous Integration]]

==Coding==
* [[Coding Standards]]
* [[Deprecating a Token]]
* [[Explanation of the Code Base]]
* [[PCGen Code Exploration Almanac]]
* [[Graph Theory]]
* [[Logging in the Code Base]]
* [[Unit Testing]]
* [[Removing Libraries]]
* [[Unnecessary Code Detector]]

=Completed Sub Projects=
* [[Ability Object TODO List]]
* [[LST_Editor_Verification]]

=Open Sub Projects=
* [[Internationalization]]
* [[CDOM]]
* [[UI Overhaul]]
* [[LST_Editor]]
* [[Major Code Projects]]
* [[Template Engine]]

=Active Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[James Dempsey]]

===[[Explanation of Teams#Second|2nd]]===
* TBA

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Tom Parker]]
* [[Stefan Radermacher]]

===[[Explanation of Teams#Gibbon|Gibbon]]===
* Jayme Cox

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Andrew Wilson]]
* [[Martijn Verburg]]
* [[Connor Petty]]

===[[Explanation of Teams#Lemur|Lemur]]===
* [[Eddy Anthony]]
* Per Christian Henden
* Thomas Cooper
* [[Tod Milam]] - Mac Developer
* [[Kim Winz]]

===[[X-Terminator Mark II]]===
* [[Greg Bingleman]] - [http://www.codemonkeypublishing.com Code Monkey Publishing]

===Other===
* Brad Stiles, SVN advice
* Jason Buchanan, Advice on old code
* [[Jonas Karlson]], Advice on old code

=Passive Team Members=

* B. K. Oxley (Provides IntelliJ licenses)

=Inactive Team Members=

===[[Explanation_of_Teams#2nd|2nd]]===
* Devon Jones

===[[Explanation_of_Teams#Chimp|Chimp]]===
* Aaron Divinsky

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* Andriy Sen
* [[Kevin Fernandes]]
* [[Koen Van Daele]]
* [[Joe Frazier, Jr.]]
* Per Christian Henden

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Bill Neumann
* Dan Parks
* [[Eduard Martinescu]]
* Eric Jarman
* Jasper Spaans
* Julio Esslinger Viegas
* Peter Barker
* [[Rick Ryker]]
* Thomas Clegg
* Tony Lavalle
* Hades Lucifer [7/20/10]
* Josh Johnston [7/20/10]
* MotorViper [7/20/10]
* [[Steven West]] [7/20/10]
* [[Alec Ross]] [7/20/10]
* [[Tir Gwaith]] [7/20/10]

===Other===
* [[Andargor]], Suggestions
* [[Bryan McRoberts]], Advice on old code
* Kurt Wimmer, Suggestions
* Walter Duncan, Held the old pcgen_autobuild user

CR Calculation Overhaul Proposal

2013-05-11T09:33:49Z

Zaister: /* CLASS.x.CLASSTYPE */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return a zero CR which can then be converted to show up as en em-dash ("CR —") by the output sheet. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===MONSTERROLEDEFAULT (new)===
This tag defines which monster role is to be assumed if none is listed. In Pathfinder, many creatures with an Intelligence score of 2 or less are listed as "No Role", because these creatures cannot take any class levels. However, if they should acquire an Intelligence score of 3 or more in some way, they can take class levels, and a monster role of "Combat" should be assumed. In order not to have to assign the Combat role to all these "No Role" creatures, it is easier to leave off the ROLE tag (see below) altogether in their race line and default to the value of this tag in case they should acquire class levels, like this:

MONSTERROLEDEFAULT:Combat

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===CLASS (modified)===
====CLASS.x.CLASSTYPE====
The token expands to the name of the classtyppe of the class.

====CLASS.x.ISMONSTER====
The token expands Y or N depending on the setting of the ISMONSTER tag in the class's classtype.

===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-05-11T09:29:42Z

Zaister: /* Export tokens */ Added CLASS.x.CLASSTYPE

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return a zero CR which can then be converted to show up as en em-dash ("CR —") by the output sheet. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===MONSTERROLEDEFAULT (new)===
This tag defines which monster role is to be assumed if none is listed. In Pathfinder, many creatures with an Intelligence score of 2 or less are listed as "No Role", because these creatures cannot take any class levels. However, if they should acquire an Intelligence score of 3 or more in some way, they can take class levels, and a monster role of "Combat" should be assumed. In order not to have to assign the Combat role to all these "No Role" creatures, it is easier to leave off the ROLE tag (see below) altogether in their race line and default to the value of this tag in case they should acquire class levels, like this:

MONSTERROLEDEFAULT:Combat

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===CLASS (modified)===
====CLASS.x.CLASSTYPE====
The token expands to the name of the classtyppe of the class.

===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-30T10:45:33Z

Zaister: /* MONSTERROLEDEFAULT (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return a zero CR which can then be converted to show up as en em-dash ("CR —") by the output sheet. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===MONSTERROLEDEFAULT (new)===
This tag defines which monster role is to be assumed if none is listed. In Pathfinder, many creatures with an Intelligence score of 2 or less are listed as "No Role", because these creatures cannot take any class levels. However, if they should acquire an Intelligence score of 3 or more in some way, they can take class levels, and a monster role of "Combat" should be assumed. In order not to have to assign the Combat role to all these "No Role" creatures, it is easier to leave off the ROLE tag (see below) altogether in their race line and default to the value of this tag in case they should acquire class levels, like this:

MONSTERROLEDEFAULT:Combat

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-30T09:52:07Z

Zaister: /* MONSTERROLES (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return a zero CR which can then be converted to show up as en em-dash ("CR —") by the output sheet. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===MONSTERROLEDEFAULT (new)===
This tag defines which monster role is to be assumed if none is listed. In Pathfinder, many creatures with an Intelligence score of 2 or less are listed as "No Role", because these creatures cannot take any class levels. However, if they should acquire an Intelligence score of 3 or more in some way, the can take class levels, and a monster role of "Combat" should be assumed. In order not to have to assign the Combat role to all these "No Role" creatures, it is easier to leave of the ROLE tag (see below) altogether in their race line, and default to the value of this tag in case they should acquire class levels, like this:

MONSTERROLEDEFAULT:Combat

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T19:31:22Z

Zaister: /* CRFORMULA (update) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return a zero CR which can then be converted to show up as en em-dash ("CR —") by the output sheet. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T18:01:08Z

Zaister: /* CLASSTYPE (usage) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return an empty value which in turn will show up as en em-dash ("CR —") on output. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level. The same is true for CLASSTYPE:Prestige and CLASSTYPE:Advanced in the Modern gamemode.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T17:54:27Z

Zaister: /* CLASSTYPE:x (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return an empty value which in turn will show up as en em-dash ("CR —") on output. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T17:54:03Z

Zaister: /* CLASSTYPE (update) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

====CRFORMULA (update)====
This subtag will now take the value NONE, which will cause the CR calculation to return an empty value which in turn will show up as en em-dash ("CR —") on output. This can be used for creatures who do not have their own CR, such as animal companions or familiars.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T17:51:38Z

Zaister: /* CLASSTYPE (usage) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level.

A new CLASSTYPE:Companion will be added. This will be used as the CLASSTYPE for all animal companions, familiars, and the like. These creatures never have their own CR—they are included in the CR of their master.
This CLASSTYPE will use CRFORMULA:NONE to reflect this.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T17:47:24Z

Zaister: /* CLASSTYPE (update) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CLASSTYPE (usage)===
For the Pathfinder RPG gamemode, the CLASSTYPE:Prestige can be eliminated. For CR calculation purposes, it is identical to CLASSTYPE:PC. With the class type now using its own class file tag (see below), there is no more need for this separation at this level.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T14:43:15Z

Zaister: /* CRMODPRIORITY:x (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a character has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T14:42:29Z

Zaister: /* CRMOD:x (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:max(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a chracter has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T14:42:07Z

Zaister: /* CRMOD:x (new) */

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contains the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:mx(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a chracter has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

CR Calculation Overhaul Proposal

2013-03-29T14:39:39Z

Zaister: Created page with "This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems. =Problems with CR Calculation= ==Problem I== PCGen takes an e..."

This is a concise summary about the problems of CR calcuation in PCGen and a proposal how to fix these problems.

=Problems with CR Calculation=
==Problem I==
PCGen takes an easy road for CR calculation, stemming from the original D&D 3.0 days. CRs for classes are determined by class type. For 3e and 35e, this means that for a PC class, the CR is equal to the level, and
for an NPC class, the CR is equal to the level – 1. CRs for creatures are assigned to the race. CRs for prestige classes are zero (no idea why). In Pathfinder, however, the CR of a PC class character is level – 1, while an NPC class character is at CR = level – 2.

It's even more complicated for creatures with racial hit dice and class levels. Here. it's necessary to determine if the class in question is a "key" class for the creature, or not. (Pathfinder uses the term "key
class", while 3e/35e used "associated class". I will continue with "key".) Pathfinder defines a "monster role" for each race, and has a list of which classes are key classes for which role, while 3e/35e do not specify that explicitly. If a class is a key class, the creature's CR is increased by 1 per class level. If the class is not a key class, a certain number of levels only increase the creature's CR by 1/2 (i.e. +1 CR per two levels), and only class levels in excess of that certain number are added on a +1 CR per level basis. The number is the creature's original CR in Pathfinder, and the creature's racial hit dice in 3e/35e.

PCGen, however, just goes and adds up all CRs from the race ant the various classes. For most PCs this works fine in 3e/35e, but the method is fundamentally flawed for any character with more than one class in Pathfinder, or with a class and racial hit dice. The problem even occurs in 3e/35e gamemodes. For example, a warrior 4 is CR 3, an expert 4 is CR 4, and so is a warrior 2/expert 2, but PCGen shows CR 2 because it
applies the formula "CR = Level -1" for NPC classes to each class and then just adds them up.

==Problem II==
Another problem that figures into this issue has previously been raised by Tom Parker. PCGen determines the formula used to calculate CR for a certain type of a class by that class's TYPE tag, for instance, a class might have the tag TYPE:Base.PC, and so, the PC class formula is used, or it may have TYPE:Monster, and the monster formula is used. However, TYPEs are not exclusive, to in theory a class might even be designated as TYPE:PC.Monster. What then? I found this comment by Tom in the source code, addressing this problem:

TODO I don't like the fact that this method is accessing the
ClassTypes and using one of those to set one of its variables. In
theory, we should have a ClassType that triggers CR that is not a
TYPE, but a unique token. See this thread:
http://tech.groups.yahoo.com/group/pcgen_experimental/message/10778

The overhaul proposed in this posting will also include this issue.

==Problem III==
Another problem lies in the fact that PCGen currently sets fixed CRs for races with no racial hit dice, such as, e.g. the bases PC races. Some are set to 1/2, some to 1/3, probably according to the sample character listed in the Bestiary/Monster Manual (1/2 if it's a PC class sample character, 1/3 if NPC class). For Pathfinder, the base races have CR:1/2, and I have no idea where this might be taken from, there is no Bestiary entry for these races - probably these are holdovers from the original 35e files.

Setting these fixed CRs, however, leads to problems when calculating the CR for low level characters. For races with no racial hit dice, a level 1 PC class character, or a level 2 NPC class character should always be CR 1/2, and a level 1 NPC class character should always be CR 1/3. With fixed CRs in the race files this does not always work correctly.

PCGen cannot correctly evaluate the expression "decrease CR by x" if the resulting CR is below CR 1. Pathfinder specifies this rule: "If this reduction would reduce a creature's CR to below 1, its CR drops one step on the following progression for each step below 1 this reduction would make: 1/2, 1/3, 1/4, 1/6, 1/8." This rule also applies when a template reduces a creatures CR. (3e/35e do not have such a rule, but would probably follow the same pattern, however, the only place where I see it would apply in these gamemodes is for level 1 NPC class characters with no racial hit dice.)

==Problem IV==
Ancillary to this issue, but still slightly connected: Pathfinder uses fixed XP awards per CR and the XP award of a creature is part of the standard Pathfinder statblock. Currently PCGen has no way of determining
and outputting this data.

=Proposal=
==Gamemode tags==
===CLASSTYPE (update)===
This tag needs two new subtypes. Currently it has CRFORMULA which contains the full formula, including the "minus one" part that is erroneously applied multiple times if a character has multiple classes. Thus the "minus one" part needs to be separated from the formula. These new subtags can be used to fix Problem I.

====CRMOD:x (new)====
This subtag contais the CR reduction mandated by a certain class type. E.g., for Pathfinder, the entry for CLASSTYPE:PC would change from "CRFORMULA:mx(CL-1,0)" to "CRFORMULA:CR" and "CRMOD:-1". The value from
CRMOD is only added after all CRFORMULA values have been added up. This tag should be able to take a formula.

====CRMODPRIORITY:x (new)====
If a character has multiple classes with different class types (such as, for example, an aristocrat/fighter), this tag determines which CRMOD is applied. For Pathfinder, if a chracter has a PC class, the CRMOD is –1, but if he has ONLY NPC classes, the CRMOD is –2. Thus, the PC CRMOD takes priority. The CRMODPROIRITY tag determines the priority in a way that PCGen will choose the CRMOD with the lowest value of CRMODPROIRITY.

===CRSTEPS:x=y|x=y|... (new)===
This tag lists the "lower than CR 1" CRs in decreasing steps, so that PCGen can do correct CR reductions and return a string result as used in the rules, fixing Problem III. This tag would be listed in most
gamemodes as:

CRSTEPS:1/2|1/3|1/4|1/6|1/8

===MONSTERROLES (new)===
To implement the system that compares classes and monster races for the synergy of "key" classes to determine CR, and thus fix Problem II, this tag will be used in the gamemode to list all valid "roles". As the "Spell" role, as listed in the rules, only applies if a creature has a spellcasting abilty of the exact same type as the class in question, it is replaced by using the spellcasting classes as individual roles. For Pathfinder, the tag would be listed in miscinfo.lst as follows:

MONSTERROLES:None|Combat|Skill|Special|Cleric|Druid|Sorcerer|Wizard

===CRTHRESHOLD (new)===
This tag defines the threshold beyond which further class levels are counted as 1 CR per level for non-key classes. This tag takes a formula. For 3e/35e this would be CRTHRESHOLD:HD, for Pathfinder CRTHRESHOLD:BASECR. (using a new variable, see below).

===XPAWARD (new)===
A gamemode tag that pairs each CR with its fixed XP award to fix Problem IV, if that is applicable to the gamemode. If not, such as in 3e/35e, the tag can be left off. For Pathfinder, the tag would be listed in
miscinfo.lst as follows:

XPAWARD:1/8=50|1/6=65|1/4=100|1/3=135|1/2=200|1=400|2=600|3=800|4=1200|5=1600|6=2400|7=3200|8=4800|9=6400|10=9600|11=12800|12=19200|13=25600|14=38400|15=51200|16=76800|17=102400|18=153600|19=204800|20=307200|21=409600|22=614400|23=819200|24=1228800|25=1638400

It might be possible to define differently, and user a formula instead. All awards for CRs of 1 and higher can easily be calculated from a single forumla. The awards for CRs less than CR 1, however, need a different forumal, and some must rounded to multiples of 5.

==Race file tags==

===CR (usage change)===
To fix Problem III and calculate CRs for creatures with no racial hit dice correctly, I propose that the fixed CR tags are removed from all of these races. The CR for these races is normally a function of the class levels, and not of the race.

===CRMOD:x.x|y (new)===
This tag can overrule the general CRMOD for certain races. In Pathfinder, for example, the descripiton of the drow noble specifies that a drow noble character's CR is alway equal to his class levels, or that for a kobold that has only NPC classes, the CR is "level – 3". x is used to specify one or more class types for which this CRMOD applies, while y specifies the value of the CRMOD. This subtag would be used on the race's line as follows:

Drow Noble CRMOD:PC.NPC|0
Kobold CRMOD:NPC|-3

===ROLE:x.x (new)===
This tag specifies the monster role(s) of a race, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

Gnoll ROLE:Combat
Demon (Babau) ROLE:Combat.Skill
Nymph ROLE:Druid

==Class file tags==
===ROLE:x.x (new)===
This tag specifies for which monster role(s) a class counts as a "key" class, using values taken from the list defined in the gamemode by the MONSTERROLES tag. These are examples:

CLASS:Fighter ROLE:Combat.Skill
CLASS:Druid ROLE:Druid
CLASS:Paladin ROLE:None
CLASS:Rogue ROLE:Skill

===CLASSTYPE:x (new)===
To solve Problem II, this tag specifies the type of a class to be used from the list of CLASSTYPEs defined in the gamemode. (Note that this will mandate that ALL classes in all datasets are adapted to use this tag. For migration purposes, a fallback can be implemented to continue to use TYPE as long as CLASSTYPE is not present.) These are examples:

CLASS:Fighter CLASSTYPE:PC
CLASS:Warrior CLASSTYPE:PC
CLASS:Arcane Archer CLASSTYPE:Prestige

==Variables==
===BASECR (new)===
This variable returns the unmodified CR of the creature's race. This is needed to calculate the CR threshold for the Pathfinder gamemode.

==Export tokens==
===XPAWARD (new)===
This export token contains the formatted value (i.e. using a comma as a thousands separator) of the XP award appropriate to the CR of the creature. If fixed XP awards are not used, such as in 3e/35e, the token
should return an empty string.

Pathfinder RPG Data Standards for PCC Files

2012-10-25T12:53:34Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Campaign Setting" (includes the previous name of this line, "Pathfinder Chronicles")
*"Pathfinder Player Companion (includes the previous name of this line, "Pathfinder Companion")
*"Pathfinder Module" (includes the previous name of this line, "GameMastery Module"
*"Pathfinder RPG".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

STATUS:
* Set to RELEASE, BETA, or ALPHA, as appropriate.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:
* For Pathfinder RPG rulebooks, which are setting neutral, this should be set to "Pathfinder RPG". All other books get "Pathfinder Campaign Setting".

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set.
*If the dataset uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder PRG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
*If the dataset is an for an adventure and includes kits for NPC or creatures, it might be necessary to include this line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Bestiary

Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag. For Pathfinder RPG rulebooks, leave out the "Pathfinder RPG" here.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc. Add the prefix "PF" for Pathfinder RPG rulebooks (such as "PFCR" for the Pathfinder RPG Core Rulebook).

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2012-10-25T12:26:23Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Campaign Setting" (includes the previous name of this line, "Pathfinder Chronicles")
*"Pathfinder Player Companion (includes the previous name of this line, "Pathfinder Companion")
*"Pathfinder Module" (includes the previous name of this line, "GameMastery Module"
*"Pathfinder RPG".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

STATUS:
* Set to RELEASE, BETA, or ALPHA, as appropriate.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:
* For Pathfinder RPG rulebooks, which are setting neutral, this should be set to "Pathfinder RPG". All other books get "Pathfinder Campaign Setting".

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set.
*If the dataset uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder PRG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
*If the dataset is an for an adventure and includes kits for NPC or creatures, it might be necessary to include this line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Bestiary

Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag. For Pathfinder RPG rulebooks, leave out the "Pathfinder RPG" here.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2012-10-25T12:14:48Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Campaign Setting" (includes the previous name of this line, "Pathfinder Chronicles")
*"Pathfinder Player Companion (includes the previous name of this line, "Pathfinder Companion")
*"Pathfinder Module" (includes the previous name of this line, "GameMastery Module"
*"Pathfinder RPG".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:
* For Pathfinder RPG rulebooks, which are setting neutral, this should be set to "Pathfinder RPG". All other books get "Pathfinder Campaign Setting".

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set.
*If the dataset uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder PRG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
*If the dataset is an for an adventure and includes kits for NPC or creatures, it might be necessary to include this line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Bestiary

Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag. For Pathfinder RPG rulebooks, leave out the "Pathfinder RPG" here.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2012-10-25T12:14:16Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Campaign Setting" (includes the previous name of this line, "Pathfinder Chronicles")
*"Pathfinder Player Companion (includes the previous name of this line, "Pathfinder Companion")
*"Pathfinder Module" (includes the previous name of this line, "GameMastery Module"
*"Pathfinder RPG".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:Pathfinder Chronicles
* For Pathfinder RPG rulebooks, which are setting neutral, this should be set to "Pathfinder RPG". All other books get "Pathfinder Campaign Setting".

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set.
*If the dataset uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder PRG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
*If the dataset is an for an adventure and includes kits for NPC or creatures, it might be necessary to include this line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Bestiary

Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag. For Pathfinder RPG rulebooks, leave out the "Pathfinder RPG" here.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Data Meeting Availability

2010-10-13T22:24:55Z

Zaister:

{| align="right"
| __TOC__
|}

=Introduction=

The [[Data|Data Team]] meetings will happen as deemed necessary by the Silverback or the team itself.

=Timezones=

{| border="1"
! Name !! Current Timezone !! Offset from GMT
|-
| [[Chris Chandler]] || EST/EDT || -5/-4
|-
| [[David R. Bender]] || EST/EDT || -5/-4
|-
| [[LegacyKing|Andrew Maitland]] || PST/PDT || -8/-7
|-
| [[Stefan Radermacher]] || CET/CEST || +1/+2
|-
|}

=Availability=
{| border="1"
! Name !! Mon !! Tue !! Wed !! Thu !! Fri !! Sat !! Sun
|-
| [[Chris Chandler]]^ || No || Mostly || Mostly || Mostly || Mostly || Yes || Yes
|-
| [[David R. Bender]]^^ || No || Yes (except 3rd) || Yes || Yes || Yes || Yes || Yes
|-
| [[LegacyKing|Andrew Maitland]] || After 4pm || After 6pm || NO || Yes || Yes || Yes || After 4pm
|-
| [[Stefan Radermacher]] || NO || After 6pm || NO || NO || Yes (except Oct 16) || Yes || After 8pm
|-
|}

^ = Afternoon/Evenings 3PM EST to 9PM EST 
^^ = After 1600 ET

Pathfinder RPG Data Standards for PCC Files

2010-07-16T10:33:50Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set.
*If the dataset uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder Roleplaying Game Character Traits Web Enhancement,Paizo - Pathfinder Roleplaying Game Advanced Player's Guide
*If the dataset is an for an adventure and includes kits for NPC or creatures, it might be necessary to include this line too:
PRECAMPAIGN:1,Paizo - Pathfinder Roleplaying Game Bestiary

Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder Roleplaying Game Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-16T09:32:31Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder Roleplaying Game Character Traits Web Enhancement,Paizo - Pathfinder Roleplaying Game Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder Roleplaying Game Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'').
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'').

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-16T09:17:52Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", adventure path volumes and modules are "Adventure", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder Roleplaying Game Character Traits Web Enhancement,Paizo - Pathfinder Roleplaying Game Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder Roleplaying Game Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-15T10:11:41Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder Roleplaying Game Character Traits Web Enhancement,Paizo - Pathfinder Roleplaying Game Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder Roleplaying Game Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-15T10:11:14Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder Roleplaying Game by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder Roleplaying Game Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-15T09:33:46Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-15T09:23:05Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder Roleplaying Game" (e.g. "Pathfinder Roleplaying Game Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

''empty line''

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-15T09:16:36Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaign Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, in upper case, or lower case for words like "the", "to", "a", or "of", etc.

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension, i.e. the same abbreviation as used in SOURCESHORT, only in all lower case.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

''empty line''

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-13T11:52:23Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
**For Adventure Path books, append the Name of the adventure path, separated by another dot.
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaing Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, omitting words like "the", "a", or "of".

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

''empty line''

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-09T13:46:53Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaing Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, omitting words like "the", "a", or "of".

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace ''<url>'' with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

''empty line''

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG

2010-07-08T11:30:08Z

Zaister:

For now, this page collects links to individal pages regarding the ''Pathfinder Roleplaying Game'' data sets for PCGen.

== General Standards ==
*[[Pathfinder RPG Data Standards for PCC_Files|Standards for PCC files]]

== Pathfinder RPG Core Rulebook ==
*nothing yet

== Pathfinder RPG Bestiary ==
*[[Pathfinder RPG Bestiary LST Standards|LST Standards]]

Pathfinder RPG Data Standards for PCC Files

2010-07-08T11:21:45Z

Zaister:

This is how a PCC file for a data set for the Pathfinder RPG should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: ''<rev>'' $ $Author: ''<name>'' $ -- Sat Dec 8 13:05:34 2007 -- reformated by prettylst.pl v1.38 (build 4387)
This line is updated by subversion with details about the last commit

CAMPAIGN:
This line contains the name of the data source and should always be begin with "Paizo - ", followed by:
*If the book is a Pathfinder RPG book, prefix the book name with "Pathfinder RPG" (e.g. "Pathfinder RPG Core Rulebook")
*If the book is an Adventure Path, the second part should be "Name of Adventure Path, Chapter X: Name of Adventure". (e.g. "Rise of the Runelords, Chapter 1: Burnt Offerings")
*For Adventure Path player guides, use "Name of Adventure Path Player's Guide" (e.g. "Rise of the Runelords Player's Guide")
*In all other cases use only the name of the book, without the product line name.

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder RPG.

TYPE:
This line builds the tree in the advanced sources panel. The first part should always be "Paizo Publishing". The second part, separated by a dot, should be the product line. Current product lines are:
*"Pathfinder Adventure Path" (note the singular!)
*"Pathfinder Chronicles" (soon to be renamed "Pathfinder Campaign Setting")
*"Pathfinder Companion (soon to be renamed "Pathfinder Player Companion")
*"Pathfinder Module" (includes the previous name of this Line, "GameMastery Module"
*"Pathfinder Roleplaying Game".

RANK:
* This is easy. The core rules get rank 1, campaign setting books form Paizo get rank 2, everything else should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", campaign setting books are "Campaign Setting", everything else is a "Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
This line should be present in all data set. If the data set uses character traits, add the following line too:
PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
Dependencies on other data sets, like Campaing Settings and Adventure Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
This should be the name of the book, without the product line, similar to the second part of the CAMPAIGN tag.

SOURCESHORT:
This is an abbreviation of the book. Pathfinder Adventure Path issues should use PF''number'' (with ''number'' replaced by the issue number, e.g. "PF1"). In most other cases, this abbreviation should consist of the first letters of the words in the name, omitting words like "the", "a", or "of".

SOURCEWEB:
The product page of the product at paizo.com.

SOURCEDATE:
Publication date in format YYYY-MM

ISOGL:YES

''empty line''

COVER:
* This should refer to a JPG picture of the book cover, as shown on paizo.com, resized to a height of 150 pixels. The name of the picture file should be the same as the PCC file, only with ".jpg" as extension.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.
URL:Paizo Publishing|''<url>''|Get this publication from Paizo Publishing!
Replace <url> with the same URL as SOURCEURL.

DESC:
The description of the book, ideally copied from the product page at paizo.com.

''empty line''

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo Publishing, LLC, which are used under Paizo's Community Use Policy. We are expressly prohibited from charging you to use or access this content. This dataset is not published, endorsed, or specifically approved by Paizo Publishing. For more information about Paizo's Community Use Policy, please visit paizo.com/communityuse. For more information about Paizo Publishing and Paizo products, please visit paizo.com.
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line immediately ''before'' the previous INFOTEXT line:
INFOTEXT:This dataset implements rules from a book that was originally designed for the 3.5 ruleset. For this dataset, these rules have been updated to the rules of the Pathfinder RPG by the PCGen data team.

''empty line''

COPYRIGHT:
This contains all the lines from the book's OGL section 15, one tag per line. Replace all occurrences of the copyright sign and "(c)" with the word "Copyright".
*If the book was originally published for the 3.5 rules, and this data set is a Pathfinder RPG conversion, add the following line (replacing ''<year>'' with the current year and ''<name>'' with a list of all developers working on the rules conversion):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-''<year>'', PCGen Data Team (including, but not limited to, ''<name>'')
*Finally, add the following line (replacing ''<book>'' with the book name (see SOURCELONG), ''<pubyear>'' with the publication year of the book, ''<year>'' with the current year, and ''<name>'' with a list of all developers working on the data set. If both years are the same, just put it once):
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright ''<pubyear>''-''<year>'', PCGen Data Team (including, but not limited to ''<name>'')

''empty line''

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

''empty line''

# Data Files
Here follow the data file tags.

Pathfinder RPG Data Standards for PCC Files

2010-07-08T10:44:37Z

Zaister: Created page with 'This is how a PCC file for a data set for the Pathfinder RPB should look, with all the necessary tags present and in a well-defined order == PCC File == # CVS $Revision: <rev> $…'

This is how a PCC file for a data set for the Pathfinder RPB should look, with all the necessary tags present and in a well-defined order

== PCC File ==
# CVS $Revision: <rev> $ $Author: <name> $ -- Sat Dec 8 13:05:34 2007
-- reformated by prettylst.pl v1.38 (build 4387)
* This line is updated by subversion with details about the last commit

#CAMPAIGN:
* This line contains the name of the data source and should be
constructed from the following parts, separated by dashes:
* First, the short name of the publisher, i.e. "Paizo".
* If the book is a Pathfinder RPG book, prefix the name with
"Pathfinder RPG"
* If the book is an Adventure Path, the second part should be
"Name of Adventure Path, Chapter X: Name of Adventure".
* For Adventure Path player guides, use
"Name of Adventure Path Player's Guide".
* On other cases use only the name of the book, without the product
line name.
* If the book was originally published for the 3.5 rules, and this data
set is a Pathfinder RPG conversion, append "(Pathfinder Conversion)".

GAMEMODE:Pathfinder
* This is straightforward, the name of the game mode for the Pathfinder
RPG.

TYPE:
* This line builds the tree in the sources panel. The first part should
always be "Paizo Publishing". The second part should be the product
line. Current product lines are "Pathfinder Adventure Path" (note the
singular!), "Pathfinder Chronicles" (soon to be renamed "Pathfinder
Campaign Setting"), Pathfinder Companion (soon to be renamed
"Pathfinder Player Companion"), "Pathfinder Module", and "Pathfinder
Roleplaying Game". The first and second parts are separated be a dot.

RANK:
* This is easy. The core rules get rank 1, everything else from Paizo
should be rank 3.

GENRE:Fantasy

BOOKTYPE:Supplement
* Similar to rank. The core rules are "Core Rules", everything else is a
"Supplement".

SETTING:Pathfinder Chronicles

PRECAMPAIGN:1,BOOKTYPE=Core Rules
* This line should be present in all data set. If the data set uses
character traits, add the following line too:
* PRECAMPAIGN:1,Paizo - Pathfinder RPG Character Traits Web
Enhancement,Paizo - Pathfinder RPG Advanced Player's Guide
* Dependencies on other data sets, like Campaing Settings and Adventure
Path player guides are also possible.

PUBNAMELONG:Paizo Publishing
PUBNAMESHORT:Paizo
PUBNAMEWEB:http://paizo.com

SOURCELONG:
* This should be the name of the book, without the product line,
similar to the second part of the CAMPIGN tag.

SOURCESHORT:
* This is an abbreviation of the book. Pathfinder Adventure Path issues
should use PF## (with ## replaced by the issue number). In most other
cases, this abbreviation should consist of the first letters of the
Words in the name, omitting words like "the", "a", or "of".

SOURCEWEB:
* The web page of the product at paizo.com

SOURCEDATE:
* Publication date in format YYYY-MM

ISOGL:YES
ISLICENSED:NO

COPYRIGHT:
* This contains all the lines from the book's OGL section 15, one tag
per line. Replace all occurrences of the copyright sign and "(c)"
with the word "Copyright".
* If the book was originally published for the 3.5 rules, and this data
set is a Pathfinder RPG conversion, add the following line (with
<year> representing the current year, and <name> replaced by a list
of all developers working on the data set):
COPYRIGHT:Pathfinder RPG Conversion Copyright 2009-<year>, PCGen Data
Team (including, but not limited to, <name>)
* Finally, add the following line (replacing <book> with the book name
(see SOURCELONG), <pubyear> with the name of publication of the book,
and <year> with the current year. If both years are the same, just
put it once)
COPYRIGHT:PCGen dataset conversion for "<book>" Copyright
<pubyear>-<year>, PCGen Data Team (including, but not limited to <name>)

INFOTEXT:This dataset uses trademarks and/or copyrights owned by Paizo
Publishing, LLC, which are used under Paizo's Community Use Policy. We
are expressly prohibited from charging you to use or access this
content. This dataset is not published, endorsed, or specifically
approved by Paizo Publishing. For more information about Paizo's
Community Use Policy, please visit paizo.com/communityuse. For more
information about Paizo Publishing and Paizo products, please visit
paizo.com.

COVER:
* This should refer to a JPG picture of the book cover, as shown on
paizo.com, resized to a height of 150 pixels. The name of the picture
should be the same as the PCC file, only with ".jpg" as extension.

LOGO:@/publisher_logos/Paizo_Publishing.png
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing!
URL:WEBSITE|http://www.paizo.com/communityuse|Paizo's Community Use Policy.

URL:Paizo Publishing|<url>|Get this publication from Paizo Publishing!
* Replace <url> with the same URL as SOURCEURL

DESC:
* The description of the book, ideally copied from the product page at
paizo.com.

# Do not remove the EXTRAFILE comment.
#EXTRAFILE:OGL.txt

# Data Files
* Here follow the data file tags

Pathfinder RPG Bestiary LST Standards

2009-11-12T14:05:55Z

Zaister:

This page collects some standards for use in coding creatures for the ''Pathfinder RPG Bestiary.'' These standards should be implemented in all data sets detailing creatures for the Pathfinder RPG game mode.

== File Location for Creatures ==
All creature definitions should go into the file '''pathfinder_rpg_bestiary_races_*.lst''' appropriate to the first letter of the creature as named in the ''Bestiary'', with the following exceptions:

* Dragons go into '''pathfinder_rpg_bestiary_races_dragons.lst'''.

* Creatures with no racial hit dice - ususally associated with a "X as characters" paragraph - go into '''pathfinder_rpg_bestiary_races_base.lst'''.

* Template creatures go into '''pathfinder_rpg_bestiary_races_templates.lst'''.

Files for starting kits and unique creature abilities are named appropriately.

== Creature Naming ==

=== Creatures with Subspecies ===
These creatures are usually named something like ''Demon, Succucbus'' or ''Giant, Stone'' in the ''Bestiary''. For the names of these creatures, please use the main name plus the subspecies in parentheses and an OUTPUTNAME tag as appropriate, using [NAME]. In the corresponding starting kit, use the result of the OUTPUTNAME tag for the NAME tag. This also applies to creatures named like ''Centipede, Giant''.

==== Examples ====
*Demon (Succubus) <> OUTPUTNAME:[NAME]
*Giant (Stone) <> OUTPUTNAME:[NAME] Giant
*Centipede (Giant) <> OUTPUTNAME:[NAME] Centipede

=== Variant Creatures ===
Some creatures use variants, possibly for bigger or aquatic versions. For the names of these creatures, please use the name of the original creature plus the name of the variant creature in parentheses and add OUTPUTNAME tag as appropriate, using [NAME]. In the corresponding starting kit, use the result of the OUTPUTNAME tag for the NAME tag.

==== Examples ====
*Centipede (Great Forest) <> OUTPUTNAME:[NAME] Centipede
*Ghoul (Lacedon) <> OUTPUTNAME:[NAME]

== Ability Scores ==
In the races files, always use even ability score bonuses for BONUS:STAT tags. If a monster has an odd score in an ability, use the starting kit to set this value: ability scores with even values should be set to 10, those with odd values to 11. Usually a creature has three odd scores and three even scores. If a creature has the same bonus for several abilities, combine them like this: BONUS:STAT|xxx,yyy|z. BONUS tags are never necessary for ability scores of 10 or 11.

The exception to this rule is if a creature has an ability score of 1 - In this case use BONUS:STAT|xxx|-9 in the races file and xxx=10 in the starting kit file.

== Class Skills ==
In the ''Pathfinder RPG'', class skills for monsters are determined by their creature type. In PCGen, these are already defined in the monster type classes and ''need not'' be defined in the races file via MONCSKILL. The exception to this rule are outsiders, who have four individual class skills in addition to those defined by their creature type. Only these monsters need MONCSKILL.

== Starting Kits ==
For the sake of consistency, please use the following line order for all starting kits. Lines that are not appropriate for a certain kits should be left out.

*STARTPACK
** This line should contain the following tags, where XXX is the name of the creature as defined in the race file:
***STARTPACK:XXX Default
***TYPE:DefaultMonster.YYY (YYY is the creature type)
***VISIBLE:QUALIFY
***EQUIPBUY:0
***PREMULT:1,[!PRERACE:1,%],[PRERACE:1,XXX]
***SOURCEPAGE:p.ZZZ
*RACE
**This line should contain the following tags:
***RACE:XXX
***!PRERACE:1,%
*NAME
** This line should contain the friendly name, i.e. the result of OUTPUTNAME if present, otherwise it is the same as RACE.
*ALIGN
*STAT
** The stats should be listed in order: STR, DEX, CON, INT, WIS, CHA. For normal creatures they should be 11-11-11-10-10-10 (not necessarily in this order). Creatures with levels usually have 13-12-11-10-9-8, or even 15-14-13-12-10-8.
*CLASS
*SKILL
*FEAT
*GEAR

Pathfinder RPG Bestiary LST Standards

2009-11-12T11:41:32Z

Zaister:

Pathfinder RPG Bestiary LST Standards

2009-11-12T11:36:02Z

Zaister:

Pathfinder RPG Bestiary LST Standards

2009-11-11T12:12:33Z

Zaister: /* Examples */

Pathfinder RPG Bestiary LST Standards

2009-11-11T12:11:02Z

Zaister: Created page with 'This page collects some standards for use in coding creatures for the ''Pathfinder RPG Bestiary.'' These standards should be implemented in all data sets detailing creatures for ...'

Pathfinder RPG

2009-11-11T11:47:47Z

Zaister: Created page with 'For now, this page collects links to individal pages regarding the ''Pathfinder Roleplaying Game'' data sets for PCGen. == Pathfinder RPG Core Rulebook == *nothing yet == Pathf...'

For now, this page collects links to individal pages regarding the ''Pathfinder Roleplaying Game'' data sets for PCGen.

== Pathfinder RPG Core Rulebook ==
*nothing yet

== Pathfinder RPG Bestiary ==
*[[Pathfinder RPG Bestiary LST Standards|LST Standards]]

Data

2009-11-11T11:45:08Z

Zaister:

{| align="right"
| __TOC__
|}
=Introduction=

Welcome to the Wiki section of the Data team! The data team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
'''TBA'''

=Resources=

* [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/listfilepages/listfiledatadevelopment.html New Datasource Development] Steps to create a new dataset
* [[First Steps with Prettylst]] A small guide for the very beginner
* [[Testing new Data]] Some steps you can follow to test your work
* [[Board of Directors|BoD]] [[Policies]] which includes a section on permissions
* [[LST Syntax FREQ]] describing the process a FREQ will run through
* [[Internationalization]]
* [[Out of cycle dataset releases]]
* [[Data LST Standards]]
* [[Joining the Data Team]]

=Active Team Members=
Members of this team (and areas of specialty/responsibility) are:

===[[Explanation of Teams#Silverback|Silverback]]===
* TBA

===[[Explanation of Teams#Second|2nd]]===
* [[Tir Gwaith]]

===[[Explanation of Teams#Chimp|Chimp]]===
* [[Tir Gwaith]] - 3e, 3.5e, Races, Classes, Prettylst
* [[Chris Chandler]] - Tag design, consulting (CMP datasets)
* [[Paul Grosse]]
* [[LegacyKing|Andrew Maitland]]
* [[Stefan Radermacher]], [[Pathfinder RPG]]
* [[Eddy Anthony]]

===[[Explanation of Teams#Gibbon|Gibbon]]===
* [[Paul W. King|Paul King]]
* Phantom of Krankor
* [[Eric C Smith]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* [[Shelley Stephen]]

===[[Explanation of Teams#Lemur|Lemur]]===
* Arjan van Ginneken
* [[David R. Bender]]
* Fluxxdog
* [[Martijn Verburg]]
* [[Terry FitzSimons]]
* Thomas Cooper
* [[Tod Milam]]

===Special Titles===
{| border=1
|-
| [[Shelley Stephen]] || 1st flunky in charge of finding weird bugs
|-
| [[Tir Gwaith]] || [[Strange Monkey]]
|}

=Inactive Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===[[Explanation of Teams#Chimp|Chimp]]===
* Michael Gray (taluroniscandar) - 3e and 3.5e Psionics
* Aaron Divinsky, Default Monster Kits, [[Internationalization]]

===[[Explanation of Teams#Tamarin|Tamarin]]===
* Ratheof Blithwyn

===[[Explanation of Teams#Lemur|Lemur]]===
* [[Andargor]]
* David Saulnier
* Dennis Baker
* Eric Jarman
* [[Jason Horner]]
* Phillip Ryan - PrettyLst

===Special Titles===
{| border=1
|-
| [[Andargor]] || Amoeba
|}