PCGen Wiki - User contributions [en]

Documentation

2015-04-13T16:04:52Z

Maredudd:

{| align="right"
| __TOC__
|}
=Introduction=
Welcome to the Wiki section of the Documentation team! The Documentation team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To provide effective, accurate, clear and easy to use documentation for PCGen that will allow the user to use the program and supplied data to the fullest effect, whether creating and playing characters or creating their own data sets.

=Resources=
* [[Joining the Docs Team]]
* [[Basic Developer Setup]] - This resource is aimed specifically at new Code Monkeys but can be used by new Doc Monkeys as well, at least for help in setting up an IDE to access the Repository.
* [[Subversion Setup]] - Like the previous page, this page is aimed specifically at Code Monkeys but new Doc Monkeys can use it to help get setup with Subversion.
* [http://pcgen.org/autobuilds/pcgen-docs/standards.html LST File Documentation Standard]
* [[Documentation Update Process]]

===Projects===
* [[PCGen Documentation Restructuring]]
* [[Variable Documentation Project]]

=Active Team Members=

===[[Explanation_of_Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#2nd|2nd]]===
* [[Eric C Smith]]

===[[Explanation_of_Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#Gibbon|Gibbon]]===
* [[Martijn Verburg]]
* [[Stefan Radermacher]]

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Matt Chambers

===Other===
* Matt Thompson

=Inactive Team Members=

===Chimp===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===Gibbon===
* Aaron Divinsky
* Sigurdur H. Olafsson
* [[Terry FitzSimons]]
* [[Tir Gwaith]]

===Lemur===
* David Lim
* Michael Durant
* Fluxxdog
* Dave Cheever

===Other===
* [[Charles Burkett]]
* deltadave
* Miriam Sexton

=Major Initiatives=
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]] Development Project
* [[PCGen Tag Dictionary Conversion to XML]]
* [[PCGen Documentation DTP Initiative]]

Data Team Resource Page

2015-04-13T16:00:54Z

Maredudd:

These are resources for the data team

* [http://pcgen.org/autobuilds/pcgen-docs/listfilepages/listfiledatadevelopment.html New Datasource Development] Steps to creating a new dataset

* [[New Recruits Training]]
* [[Data Team Tips and Tricks]] - Here's where new tips and tricks should be placed for others to learn.

Code

2015-04-13T15:53:54Z

Maredudd: /* Developer Environment */

{| 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]]
* [[Git 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

Code

2015-04-13T15:41:49Z

Maredudd: /* Developer Environment */

{| 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]]
* [[GitHub 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

PCGen Data Tag and OS Token XML Dictionaries Concept of Operations

2014-12-14T13:18:20Z

Maredudd:

{| align="right"
| __TOC__
|}

=Scope=
==Identification==
This is the Concept of Operations document for the XML Based PCGen Data Tag and OS Token Dictionaries.

==Document Overview==
This document will identify the operational goals and needs for the XML based Data Tag and OS Token Dictionaries being developed for PCGen. This is intended to be an informal document and therefore will not include a number of elements found in formal ConOps.

This is a document in development and therefore the outline included below will change as development proceeds.

==System Overview==

=Referenced Documents=
The only document referenced within this ConOps is the current Tag and Token Dictionaries, both of which can be found here.

=Concept for the Proposed System=
==Background, Objectives, and Scope==
==Description of the Proposed System==
==Modes of Operation==
==End-user Classes, other Involved Personnel==
==Support Environment==

=Operational Scenarios=
==User Goal Use Case Diagram==
==User Goal Use Case Descriptions==
==Data Flow Diagrams (?)==

PCGen Data Tag and OS Token XML Dictionaries Concept of Operations

2014-12-14T12:54:01Z

Maredudd:

{| align="right"
| __TOC__
|}

=Scope=
==Identification==
This is the Concept of Operations document for the XML Based PCGen Data Tag and OS Token Dictionaries.

==Document Overview==
This document will identify the operational goals and needs for the XML based Data Tag and OS Token Dictionaries being developed for PCGen. This is intended to be an informal document and therefore will not include a number of elements found in formal ConOps.

This is a document in development and therefore the outline included below will change as development proceeds.

==System Overview==

=Referenced Documents=
The only document referenced within this ConOps is the current Tag and Token Dictionaries, both of which can be found here.

=Current System=
==Background, Objectives, and Scope==
==Operational Policies and Constraints==
==Description of the Current System==
==Modes of Operation for Current System==
==End-user classes and Other Involved Personnel==
==Support Environment==

=Concepts for the Proposed System=
==Background, Objectives, and Scope==
==Operational Policies and Constraints==
==Description of the Proposed System==
==Modes of Operation==
==End-user Classes, other Involved Personnel==
==Support Environment==

=Operational Scenarios=
==User Goal Use Case Diagram==
==User Goal Use Case Descriptions==
==Data Flow Diagrams (?)==

PCGen Tag Dictionary Conversion to XML

2014-12-14T12:42:49Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the LST Tag Dictionary Conversion Initiative page!

==Purpose==
The purpose of this effort is to convert the current LST Tag Dictionary from the HTML based format to an XML format more suitable to regular maintenance and automated processing in support of the DTP Initiative.

The Tag Dictionary itself will be developed for three purposes:
* LST Tag Dictionary for LST Monkeys
* OS Token Dictionary for OS Monkeys
* LST/OS Token Dictionary for PCGen Developers

==Proposed (Eventual) Products==
* XML Based LST Tag Dictionary File(s)
* XML Based OS Token Dictionary File(s)
* Java Based LST Tag/OS Token Dictionary Entry Editor

==Roadmap==
The LST Tag/OS Token Dictionary to XML Project Roadmap is under development:

* Develop [[PCGen Data Tag and OS Token XML Dictionaries Concept of Operations | Concept of Operations (In-work)]] for the Tag/Token XML Dictionaries
* Develop Tag/Token Dictionary Specification
* XML Schema for Tag/Token Dictionary
* Develop Java based Tag/Token Editor
* Convert Existing HTML Based Dictionary to XML

=Resources=
==Related Efforts==
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]]
* [[PCGen Documentation DTP Initiative]]

==Tools==
Tools to be used in this effort will be added as they are identified.

==Prior Discussion==
* [[http://tech.groups.yahoo.com/group/pcgen_experimental/message/9667| PCGen Experimental]]

=Tasks and Status=
No tasks have been identified at this time.

{| border=1
|-
! Task Description !! Tracker Number !! Doc Monkey !! Status
|-
| || || ||
|-
| || || ||
|}

=Specifications and Requirements=

==LST Tag Elements==

{| border=1
|-
! Doc Element !! Data Example || Data Type || Data Description
|-
| Tag Status || New/Updated/Deprecated || ||
|-
| LST Tag Syntax || <lst tag>:<parameter list> || ||
|-
| Variables Used || || ||
|-
| Tag Description || || ||
|-
| Example LST Code || || ||
|-
| .MOD Consolidation || || ||
|-
| .MOD Example From || || ||
|-
| .MOD Example To || || ||
|-
| Deprecated Syntax || || ||
|-
| Where Used || || ||
|}

PCGen Data Tag and OS Token XML Dictionaries Concept of Operations

2014-12-14T12:41:38Z

Maredudd: Created page with "{| align="right" | __TOC__ |} =Scope= ==Identification== ==Document Overview== ==System Overview== =Referenced Documents= The only document referenced within this ConOps..."

{| align="right"
| __TOC__
|}

=Scope=
==Identification==
==Document Overview==
==System Overview==

=Referenced Documents=
The only document referenced within this ConOps is the current Tag and Token Dictionaries, both of which can be found here.

=Current System=
==Background, Objectives, and Scope==
==Operational Policies and Constraints==
==Description of the Current System==
==Modes of Operation for Current System==
==End-user classes and Other Involved Personnel==
==Support Environment==

=Concepts for the Proposed System=
==Background, Objectives, and Scope==
==Operational Policies and Constraints==
==Description of the Proposed System==
==Modes of Operation==
==End-user Classes, other Involved Personnel==
==Support Environment==

=Operational Scenarios=
==User Goal Use Case Diagram==
==User Goal Use Case Descriptions==
==Data Flow Diagrams (?)==

PCGen Tag Dictionary Conversion to XML

2014-12-14T12:31:30Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the LST Tag Dictionary Conversion Initiative page!

==Purpose==
The purpose of this effort is to convert the current LST Tag Dictionary from the HTML based format to an XML format more suitable to regular maintenance and automated processing in support of the DTP Initiative.

The Tag Dictionary itself will be developed for three purposes:
* LST Tag Dictionary for LST Monkeys
* OS Token Dictionary for OS Monkeys
* LST/OS Token Dictionary for PCGen Developers

==Proposed (Eventual) Products==
* XML Based LST Tag Dictionary File(s)
* XML Based OS Token Dictionary File(s)
* Java Based LST Tag/OS Token Dictionary Entry Editor

==Roadmap==
The LST Tag/OS Token Dictionary to XML Project Roadmap is under development:

* Develop [[PCGen Data Tag and OS Token XML Dictionaries Concept of Operations | Concept of Operations]] for the Tag/Token XML Dictionaries
* Develop Tag/Token Dictionary Specification
* XML Schema for Tag/Token Dictionary
* Develop Java based Tag/Token Editor
* Convert Existing HTML Based Dictionary to XML

=Resources=
==Related Efforts==
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]]
* [[PCGen Documentation DTP Initiative]]

==Tools==
Tools to be used in this effort will be added as they are identified.

==Prior Discussion==
* [[http://tech.groups.yahoo.com/group/pcgen_experimental/message/9667| PCGen Experimental]]

=Tasks and Status=
No tasks have been identified at this time.

{| border=1
|-
! Task Description !! Tracker Number !! Doc Monkey !! Status
|-
| || || ||
|-
| || || ||
|}

=Specifications and Requirements=

==LST Tag Elements==

{| border=1
|-
! Doc Element !! Data Example || Data Type || Data Description
|-
| Tag Status || New/Updated/Deprecated || ||
|-
| LST Tag Syntax || <lst tag>:<parameter list> || ||
|-
| Variables Used || || ||
|-
| Tag Description || || ||
|-
| Example LST Code || || ||
|-
| .MOD Consolidation || || ||
|-
| .MOD Example From || || ||
|-
| .MOD Example To || || ||
|-
| Deprecated Syntax || || ||
|-
| Where Used || || ||
|}

PCGen Tag Dictionary Conversion to XML

2014-12-14T03:36:15Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the LST Tag Dictionary Conversion Initiative page!

==Purpose==
The purpose of this effort is to convert the current LST Tag Dictionary from the HTML based format to an XML format more suitable to regular maintenance and automated processing in support of the DTP Initiative.

The Tag Dictionary itself will be developed for three purposes:
* LST Tag Dictionary for LST Monkeys
* OS Token Dictionary for OS Monkeys
* LST/OS Token Dictionary for PCGen Developers

==Proposed (Eventual) Products==
* XML Based LST Tag Dictionary File(s)
* XML Based OS Token Dictionary File(s)
* Java Based LST Tag/OS Token Dictionary Entry Editor

==Roadmap==
The LST Tag/OS Token Dictionary to XML Project Roadmap is under development:

* Develop [[PCGen Data Tag and OS Token XML Dictionaries ConOps | Concept of Operations]] for the Tag/Token XML Dictionaries
* Develop Tag/Token Dictionary Specification
* XML Schema for Tag/Token Dictionary
* Develop Java based Tag/Token Editor
* Convert Existing HTML Based Dictionary to XML

=Resources=
==Related Efforts==
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]]
* [[PCGen Documentation DTP Initiative]]

==Tools==
Tools to be used in this effort will be added as they are identified.

==Prior Discussion==
* [[http://tech.groups.yahoo.com/group/pcgen_experimental/message/9667| PCGen Experimental]]

=Tasks and Status=
No tasks have been identified at this time.

{| border=1
|-
! Task Description !! Tracker Number !! Doc Monkey !! Status
|-
| || || ||
|-
| || || ||
|}

=Specifications and Requirements=

==LST Tag Elements==

{| border=1
|-
! Doc Element !! Data Example || Data Type || Data Description
|-
| Tag Status || New/Updated/Deprecated || ||
|-
| LST Tag Syntax || <lst tag>:<parameter list> || ||
|-
| Variables Used || || ||
|-
| Tag Description || || ||
|-
| Example LST Code || || ||
|-
| .MOD Consolidation || || ||
|-
| .MOD Example From || || ||
|-
| .MOD Example To || || ||
|-
| Deprecated Syntax || || ||
|-
| Where Used || || ||
|}

PCGen Tag Dictionary Conversion to XML

2014-12-14T03:30:47Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the LST Tag Dictionary Conversion Initiative page!

==Purpose==
The purpose of this effort is to convert the current LST Tag Dictionary from the HTML based format to an XML format more suitable to regular maintenance and automated processing in support of the DTP Initiative.

The Tag Dictionary itself will be developed for three purposes:
* LST Tag Dictionary for LST Monkeys
* OS Token Dictionary for OS Monkeys
* LST/OS Token Dictionary for PCGen Developers

==Proposed (Eventual) Products==
* XML Based LST Tag Dictionary File(s)
* XML Based OS Token Dictionary File(s)
* Java Based LST Tag/OS Token Dictionary Entry Editor

==Roadmap==
The LST Tag/OS Token Dictionary to XML Project Roadmap is under development:

* Develop [[Tag/Token XML Conversion ConOps | Concept of Operations]] for the Tag/Token XML Dictionaries
* Develop Tag/Token Dictionary Specification
* XML Schema for Tag/Token Dictionary
* Develop Java based Tag/Token Editor
* Convert Existing HTML Based Dictionary to XML

=Resources=
==Related Efforts==
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]]
* [[PCGen Documentation DTP Initiative]]

==Tools==
Tools to be used in this effort will be added as they are identified.

==Prior Discussion==
* [[http://tech.groups.yahoo.com/group/pcgen_experimental/message/9667| PCGen Experimental]]

=Tasks and Status=
No tasks have been identified at this time.

{| border=1
|-
! Task Description !! Tracker Number !! Doc Monkey !! Status
|-
| || || ||
|-
| || || ||
|}

=Specifications and Requirements=

==LST Tag Elements==

{| border=1
|-
! Doc Element !! Data Example || Data Type || Data Description
|-
| Tag Status || New/Updated/Deprecated || ||
|-
| LST Tag Syntax || <lst tag>:<parameter list> || ||
|-
| Variables Used || || ||
|-
| Tag Description || || ||
|-
| Example LST Code || || ||
|-
| .MOD Consolidation || || ||
|-
| .MOD Example From || || ||
|-
| .MOD Example To || || ||
|-
| Deprecated Syntax || || ||
|-
| Where Used || || ||
|}

PCGen Tag Dictionary Conversion to XML

2014-12-14T03:28:51Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
Welcome to the LST Tag Dictionary Conversion Initiative page!

==Purpose==
The purpose of this effort is to convert the current LST Tag Dictionary from the HTML based format to an XML format more suitable to regular maintenance and automated processing in support of the DTP Initiative.

The Tag Dictionary itself will be developed for three purposes:
* LST Tag Dictionary for LST Monkeys
* OS Token Dictionary for OS Monkeys
* LST/OS Token Dictionary for PCGen Developers

==Proposed (Eventual) Products==
* XML Based LST Tag Dictionary File(s)
* XML Based OS Token Dictionary File(s)
* Java Based LST Tag/OS Token Dictionary Entry Editor

==Roadmap==
The LST Tag/OS Token Dictionary to XML Project Roadmap is under development:

* Develop Concept of Operations for the Tag/Token XML Dictionaries
* Develop Tag/Token Dictionary Specification
* XML Schema for Tag/Token Dictionary
* Develop Java based Tag/Token Editor
* Convert Existing HTML Based Dictionary to XML

=Resources=
==Related Efforts==
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]]
* [[PCGen Documentation DTP Initiative]]

==Tools==
Tools to be used in this effort will be added as they are identified.

==Prior Discussion==
* [[http://tech.groups.yahoo.com/group/pcgen_experimental/message/9667| PCGen Experimental]]

=Tasks and Status=
No tasks have been identified at this time.

{| border=1
|-
! Task Description !! Tracker Number !! Doc Monkey !! Status
|-
| || || ||
|-
| || || ||
|}

=Specifications and Requirements=

==LST Tag Elements==

{| border=1
|-
! Doc Element !! Data Example || Data Type || Data Description
|-
| Tag Status || New/Updated/Deprecated || ||
|-
| LST Tag Syntax || <lst tag>:<parameter list> || ||
|-
| Variables Used || || ||
|-
| Tag Description || || ||
|-
| Example LST Code || || ||
|-
| .MOD Consolidation || || ||
|-
| .MOD Example From || || ||
|-
| .MOD Example To || || ||
|-
| Deprecated Syntax || || ||
|-
| Where Used || || ||
|}

Eric C Smith

2014-10-08T23:35:06Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=

Eric C Smith, aka Maredudd, aka Tenacious Monkey, has been a member of the PCGen team since Sept/Oct of '06.

=Teams=
{| class="wikitable" border="1"
|-
| Team || Rank
|-
| [[Admin]] - [[Release]] || [[Explanation of Teams#Chimp|Chimp]] (Mac and OOC Releases)
|-
| [[Admin]] - [[Tracker]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Admin]] - [[Website]] || [[Explanation of Teams#Lemur|Tamarin]]
|-
| [[Content]] - [[Documentation]]|| [[Explanation of Teams#Second|2nd]]
|-
| [[Content]] - [[Data]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Publisher Liaison]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Data License]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Advertising]] || [[Explanation of Teams#Chimp|Chimp]]
|}

=Contact Details=
{| class="wikitable" border="1"
|-
| Timezone || GMT -5 (US EST)
|-
| Email || maredudd@blackroot.org
|-
| AIM ID || Maredudd
|-
| Yahoo Chat ID || maredudd800
|-
| SF ID || maredudd800
|-
| Web Site || http://www.blackroot.org
|}

=Trackers=
* Documentation Trackers
* New Tag Trackers
* Data Trackers
* New Source Trackers

=General Tasks=
* General Doc 2nd duties
* Performing OGL reviews on new data sets.
* Work documentation issues.

=Specific Documentation Tasks=
* [[PCGen Tag Dictionary Conversion to XML]]
* [[PCGen Documentation Style Guide]].
: * [[Documentation Style Review Status]] page.

=Specific Data Tasks=
* [[PCGen Support for Savage Worlds|Developing Savage Worlds GameMode and Data Set]]

PCGen Documentation Restructuring

2014-07-26T02:09:34Z

Maredudd:

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

=Status=

=Scope=

=Background=

=Proposed Restructuring=

PCGen Documentation Restructuring

2014-07-26T02:08:17Z

Maredudd:

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

=Status=

=Scope=

=Background=

=Proposal=

PCGen Documentation Restructuring

2014-07-26T02:06:00Z

Maredudd: Created page with "{| align="right" | __TOC__ |} = Introduction ="

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

Documentation

2014-07-26T02:05:47Z

Maredudd:

{| align="right"
| __TOC__
|}
=Introduction=
Welcome to the Wiki section of the Documentation team! The Documentation team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To provide effective, accurate, clear and easy to use documentation for PCGen that will allow the user to use the program and supplied data to the fullest effect, whether creating and playing characters or creating their own data sets.

=Resources=
* [[Joining the Docs Team]]
* [[Basic Developer Setup]] - This resource is aimed specifically at new Code Monkeys but can be used by new Doc Monkeys as well, at least for help in setting up an IDE to access the Repository.
* [[Subversion Setup]] - Like the previous page, this page is aimed specifically at Code Monkeys but new Doc Monkeys can use it to help get setup with Subversion.
* [http://pcgen.svn.sourceforge.net/viewvc/*checkout*/pcgen/Trunk/pcgen/docs/standards.html LST File Documentation Standard]
* [[Documentation Update Process]]

===Projects===
* [[PCGen Documentation Restructuring]]
* [[Variable Documentation Project]]

=Active Team Members=

===[[Explanation_of_Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#2nd|2nd]]===
* [[Eric C Smith]]

===[[Explanation_of_Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#Gibbon|Gibbon]]===
* [[Martijn Verburg]]
* [[Stefan Radermacher]]

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Matt Chambers

===Other===
* Matt Thompson

=Inactive Team Members=

===Chimp===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===Gibbon===
* Aaron Divinsky
* Sigurdur H. Olafsson
* [[Terry FitzSimons]]
* [[Tir Gwaith]]

===Lemur===
* David Lim
* Michael Durant
* Fluxxdog
* Dave Cheever

===Other===
* [[Charles Burkett]]
* deltadave
* Miriam Sexton

=Major Initiatives=
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]] Development Project
* [[PCGen Tag Dictionary Conversion to XML]]
* [[PCGen Documentation DTP Initiative]]

PCGen Documentation Restructuring Proposal

2014-07-26T02:05:14Z

Maredudd: Blanked the page

PCGen Documentation Restructuring Proposal

2014-07-26T02:03:48Z

Maredudd: Created page with "{| align="right" | __TOC__ |} = Introduction ="

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

Documentation

2014-07-26T02:02:27Z

Maredudd:

{| align="right"
| __TOC__
|}
=Introduction=
Welcome to the Wiki section of the Documentation team! The Documentation team is a sub team under the umbrella of the [[Content]] team.

=Mission Statement=
To provide effective, accurate, clear and easy to use documentation for PCGen that will allow the user to use the program and supplied data to the fullest effect, whether creating and playing characters or creating their own data sets.

=Resources=
* [[Joining the Docs Team]]
* [[Basic Developer Setup]] - This resource is aimed specifically at new Code Monkeys but can be used by new Doc Monkeys as well, at least for help in setting up an IDE to access the Repository.
* [[Subversion Setup]] - Like the previous page, this page is aimed specifically at Code Monkeys but new Doc Monkeys can use it to help get setup with Subversion.
* [http://pcgen.svn.sourceforge.net/viewvc/*checkout*/pcgen/Trunk/pcgen/docs/standards.html LST File Documentation Standard]
* [[Documentation Update Process]]

===Sub Projects===
* [[PCGen Documentation Restructuring Proposal]]
* [[Variable Documentation Project]]

=Active Team Members=

===[[Explanation_of_Teams#Silverback|Silverback]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#2nd|2nd]]===
* [[Eric C Smith]]

===[[Explanation_of_Teams#Chimp|Chimp]]===
* [[Chris Chandler|Barak]]

===[[Explanation_of_Teams#Gibbon|Gibbon]]===
* [[Martijn Verburg]]
* [[Stefan Radermacher]]

===[[Explanation_of_Teams#Tamarin|Tamarin]]===
* [[LegacyKing|Andrew Maitland]]

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Matt Chambers

===Other===
* Matt Thompson

=Inactive Team Members=

===Chimp===
* [[Eddy Anthony]]
* [[Frank Kliewe]]

===Gibbon===
* Aaron Divinsky
* Sigurdur H. Olafsson
* [[Terry FitzSimons]]
* [[Tir Gwaith]]

===Lemur===
* David Lim
* Michael Durant
* Fluxxdog
* Dave Cheever

===Other===
* [[Charles Burkett]]
* deltadave
* Miriam Sexton

=Major Initiatives=
* [[PCGen Documentation HTML Compliance Project]]
* [[PCGen Documentation Style Guide]] Development Project
* [[PCGen Tag Dictionary Conversion to XML]]
* [[PCGen Documentation DTP Initiative]]

Data LST Standards

2014-05-18T03:25:49Z

Maredudd:

===General Object Naming Standards===

These are general rules for the naming of classes, feats, races and other objects.

Characters approved for use in object names are: upper and lower case letters, numbers, single spaces in between multiple words (never before or after) and the following glyphs: underscore (_), dash (-), apostrophe ('), parentheses (), slash (/), and a tilde (~).

The following alpha characters shall not be used in object names: Comma (,), Pipe (|), Backslashe (\), Colon (:), Semicolon (;), Period (.), Bracket ([]), Percent (%), Asterisk (*) and Equals (=).

Two words separated by a dash should both be capitalized. (Example: Low-Light Vision)

Within these limits the name should be as close as possible to the published source.

EXCEPTION to the Naming Convention, if you use a KEY name, the Name acts as OUTPUTNAME and may use commas. The KEY MUST ADHERE to the General rules for the naming of all objects at ALL times. If the name has a Comma (,) the section after shall use Parenthesis in the KEY. Example: Beast Totem, Greater becomes Beast Totem (Greater).

Ability Naming Standard:

PublisherAbilityName <TAB> KEY:Granting Object ~ NameOfAbility

Example: Barbarian Class has 'Rage' as a Class Feature we would do it as such -

Rage <TAB> KEY:Barbarian ~ Rage

Objects Belonging to a Group of Selections should use the Originating Ability Name as the Granting Object to follow this pattern. Example: Rage Powers from Barbarian would be done 'Barbarian ~ Rage Powers' and then the powers themselves would be 'Rage Powers ~ Name of Power'

Rage Powers ~ Beast Totem (Greater)
Rage Powers ~ Beast Totem (Lesser)
Rage Powers ~ Brawler

===Additional Restrictions===

* No object may be named a valid number (even 0x45 or 1e20 could be a problem) as items with optional count can fail.
* No object may be called "ANY" or "ALL" or "LIST".
* No Class may be called "HIGHESTLEVELCLASS".
* No Equipment may be called "Total".
* No Weaponprof may be called "DEITYWEAPON".
* No equipment (or eqmod ITYPE) may use the types "ADD" or "REMOVE". Further restrictions discovered: 'THROWN', 'RANGED', 'WEAPON'. << Need to clarify with code if we can override this.

===General Variable Naming Standards===

Variables syntax should start with a letter and should be composed of only letters, underscores (_) and numbers. Do not use Hyphens, Dashes or Emdashs (-) as the program will think the Variable is a formula 'XYZ-ABC'. Our standard is to use only letters, and capitalizing individual words for readability.

Examples:
''''SneakAttackDice''''
''''UncannyDodgeFlankingLVL''''
''''AnimalCompanionLVL''''
''''PoisonDC''''

Variables should be Full Words and end in what they are doing. Listed below are the standard Ends for our Variable Names. Each one indicates a certain function:
'''LVL''' <-- Short for Level (Used with Classes and Progressions)
'''Dice''' <-- Number of Dice in a '''x'''dy format, with Dice being the '''X'''.
'''DieSize''' <-- Die Size in a xd'''y''' format, with DieSize being the '''Y'''.
'''Bonus''' <-- Used for '+x' formats, class features that have "Ability +1"
'''Count''' <-- This means counting involved, used for Feat Pools, or Selections. Example: How many Fighter Feats do you have.
'''DC''' <-- Used for items that have a 'DC x' format.
'''Times''' <-- Used for items that use 'x/day' style format
'''Duration''' <-- Used for items that have a Duration

Examples of this naming:
ClassNameLVL
SneakAttackDice
SneakAttackDieSize
FighterBonusFeatCount
AssassinSaveBonus
DeathAttackDC

There should be at least one, 'DEFINE' per variable and the DEFINE should be set at 0. All adjustments of the Variable will then use a BONUS:VAR statement. Per Code Silverback (James Dempsey): Define is evaluated once in the code, therefore using DEFINE to any value other than 0 can cause issues for characters. The exception we make is CLASS LINE - As this re-evaluates at each level change.

Only SYSTEM hard-coded variable names are all capitals. Any Data Team created variables are restricted to Mixed Case only.

Variables should ''always'' have the DEFINE set within the originating object where it is first used or encountered.

It is good practice to leave comments within the data sets LST code explaining what variables have been used in the set, what their purpose is and how they are to be used. UPDATE: Hopefully, moving to using consistent naming patterns the documentation won't be as necessary.

Our old Standard was to do variables for Classes in the class file. This is no longer optimal for the existing sets. All Classes that need to use 'CL' will replace 'CL' with '<ClassNameLVL>' and then move the Variable formula to the Ability it applies too.

===General EQMOD Naming Standards===

EQMOD keys 'KEY:EQMOD_NAME' are to be in all capital letters and may only contain letters, numbers and underscores ("_").

Each word should be separated by an underscore character for ease in reading.

For purposes of abbreviation the letter limit on the first and second sections of the Key name is 8 and 7.

EQMODs for different item types (Weapon vs. Armor for example) will be done as separate EQMODs.

Materials which list different pricing for different item types or sub types (Light Armor vs. Medium Armor for example) will be done as separate EQMODs for each price type.

Special Naming for EQMOD Keys:
ARMR <-- Armor
LT <-- Light
MED <-- Medium
HVY <-- Heavy
SHLD <-- Shield
WEAP <-- Weapon

===Special Usages===

KEY use should follow the following format

* For EQMODS
** ALL UPPERCASE
** Spaces will be underscores '_'

===Commenting In .lst Files Standard===

In an effort to make our use of comments in .lst files more uniform (and hopefully more useful), the following standard has been adopted regarding what comments should be in the file and how they should be done.

At the top of the file the original author should enter the following (this should be in every file from the date of adoption of this standard forward):

<nowiki>#</nowiki> ORIGINAL ENTRY: <name, handle, etc.> 
<nowiki>#</nowiki> ORIGINAL ENTRY DATE: <####/##/## date of original entry>

Note that the date should be in the format of YEAR/MONTH/DAY

The rest of these recommendations are to be used on an as needed basis. These types of entries should appear immediately above the item/feat/object they are referring to. For ease of reading, please restrict each line to one screen width, using multiple lines (all with the appropriate comment heading in front) if necessary. As a further aid to reading the comments and identifying what they apply to, a blank line should be left above the first of these comment lines and there should also be a blank line below the object line the comment(s) refer to (see examples below).

<nowiki>#</nowiki> NEEDS CODE WORK: <explanation of code work needed, tracker # if there is one> 
<nowiki>#</nowiki> NEEDS DATA WORK: <explanation of data work needed> 
<nowiki>#</nowiki> WORKAROUND: <explanation of workaround being used> 
<nowiki>#</nowiki> PARTIAL WORKAROUND: <explanation of partial workaround and what is supposed to be happening but isn't> 
<nowiki>#</nowiki> COMMENT: <elaboration on a difficult concept/implementation that the creator feels needs explanation (like all the barbarian rage vars)> 

More than one of these could be used in concert if there were a workaround in place but a better solution was expected from code, you might have a NEEDS CODE WORK and a WORKAROUND for example.

''Examples as they should appear in a .lst file'':

<nowiki>#</nowiki> ORIGINAL ENTRY: Barak 
<nowiki>#</nowiki># ORIGINAL ENTRY DATE: 2011/06/23

Feat 1 
Feat 2 
Feat 3 

<nowiki>#</nowiki> NEEDS CODE WORK: Cannot track *when* feat was taken, so adding +1 hp per level after is impossible - CDOM should fix this 
<nowiki>#</nowiki> WORKAROUND: Will implement the +1 hp - but it won't be correct. Basing calculation on fighter levels TL-6 
Feat 4 
Feat 5 
Feat 6 

<nowiki>#</nowiki> NEEDS CODE WORK: Need a way to tally total ranks in type.knowledge where you must have at least 3 different knowledge skills. 
<nowiki>#</nowiki> NEEDS CODE WORK: Current tag can get 20, but not the three part. 
<nowiki>#</nowiki> PARTIAL WORKAROUND: Coding to test for the total ranks, DM will have to monitor the total of three knowledge skills required 
Feat 7 
Feat 8 
Feat 9 
Feat 10 
Feat 11 
Feat 12

<nowiki>#</nowiki> COMMENT: The ExtShokQual variable will override the normal PREREQs for those classes that 
<nowiki>#</nowiki> COMMENT: gain this as a class ability without having to meet the prereqs. 
Feat 13

===File Naming and Folder Names===
* Submitted Oct 15th, 2010

* All titles and folders will adhere to lower case and spaces will be replaced by '_' underscores.
* Publisher > All books are identified by Primary Publisher or one holding current License if known
* Book Type > Core / Supplemental Title Group
* Book Name
* Files shall follow short name of book using short pub name and book name. Adhere to 3 to 5 letter book abbreviation by publisher if known. The PCC master file will be the full name of the book.
* Underscore (_) before the pcc file name will keep the file at the top of the list.

* Example:
** paizo
** pathfinder_rpg
** core_rulebook
** _core_rulebook.pcc
** cr_abilities.lst
** etc.

===File Reference===
* Submitted May 28th, 2012

For Conversion Folders - when referencing a folder above the conversion folder ALWAYS use RELATIVE file paths, not absolutes, otherwise your paths will be broken and you'll be forcing fixes as the files transition between NFD, to ALPHA, To the full release folder. The only case this is not PLAUSIBLE is reference to other source books OUTSIDE the sourcebook folder, i.e. you need to reference material in another source book.

One Folder Up:
../<filename>.lst

Folder below:
<folder_name>/<filename>.xxx

===PCC Stuff===
CAMPAIGN:>book name< or 'My Pathfinder Campaign' (home brew name) or 'Pathfinder Society' 
<nowiki>#</nowiki> EXAMPLE - CAMPAIGN:Advanced Players Guide 
<nowiki>#</nowiki> EXAMPLE - CAMPAIGN:Curse of the Crimson Throne, Chapter 1: Edge of Anarchy 
<nowiki>#</nowiki> EXAMPLE - CAMPAIGN:Inner Sea World Guide 
KEY:>PCGen Key Rules Apply< Instead of Parenthesis, we use dash (-) instead of Commas as PRECAMPAIGN will not work with Commas!
<nowiki>#</nowiki> EXAMPLE - KEY:Curse of the Crimson Throne - Chapter 1 

RANK:1-9 
<nowiki>#</nowiki> NOTE - Follow these rules - 1 (Core Rulebook), 2 (capaign settings), 3 (supplements), 4 (web/blog), 5 (3rd party campaign settings), 6(3rd party supplements), 7(3rd party web/blog), 8 & 9 (Homebrew) 
<nowiki>#</nowiki> EXAMPLE - RANK:3 
<nowiki>#</nowiki> EXAMPLE - RANK:3 
<nowiki>#</nowiki> EXAMPLE - RANK:2 
TYPE:Paizo Publishing.>Type of book = Core Rulebook, Player Companion, Campaign Setting, Adventure Path, Web Enhancement, Paizo Blog, >Homebrew<.>campaign setting name/adventure path name< 
<nowiki>#</nowiki> NOTE - Max of 3 type's only, last type is optional 
<nowiki>#</nowiki> EXAMPLE - TYPE:Paizo Publishing.Supplement 
<nowiki>#</nowiki> EXAMPLE - TYPE:Paizo Publishing.Adventure Path.Curse of the Crimson Throne 
<nowiki>#</nowiki> EXAMPLE - TYPE:Paizo Publishing.Campaign Setting 
STATUS:TESTONLY, ALPHA, BETA, RELEASE 
<nowiki>#</nowiki> EXAMPLE - STATUS:RELEASE 
<nowiki>#</nowiki> EXAMPLE - STATUS:BETA 
<nowiki>#</nowiki> EXAMPLE - STATUS:ALPHA 
BOOKTYPE:Core Rules, Supplement, Adventure, Campaign Setting, Homebrew 
<nowiki>#</nowiki> EXAMPLE - BOOKTYPE:Supplement 
<nowiki>#</nowiki> EXAMPLE - BOOKTYPE:Adventure 
<nowiki>#</nowiki> EXAMPLE - BOOKTYPE:Campaign Setting 
SETTING:Pathfinder and/or >overall setting name< and/or >setting regional name< and/or >specific location name< or Pathfinder Society or Homebrew or >campaign setting name< 
<nowiki>#</nowiki> NOTE - SETTING is pipe delimited 
<nowiki>#</nowiki> EXAMPLE - Pathfinder 
<nowiki>#</nowiki> EXAMPLE - Pathfinder|Golarion 
<nowiki>#</nowiki> EXAMPLE - Pathfinder|Golarion|Inner Sea 
PRECAMPAIGN:#,BOOKTYPE=>BOOKTYPE name< 
!PRECAMPAIGN:#,BOOKTYPE=>BOOKTYPE name< 
<nowiki>#</nowiki> NOTE - PREMULT works in these files - ignore the prettylst message 
<nowiki>#</nowiki> EXAMPLE - PRECAMPAIGN:1,BOOKTYPE=Core Rules 
<nowiki>#</nowiki> EXAMPLE - !PRECAMPAIGN:1,Character Traits Web Enhancement,BOOKTYPE=Complete Core 
<nowiki>#</nowiki> EXAMPLE - PREMULT:2,[PRECAMPAIGN:1,BOOKTYPE=Core Rules],[!PRECAMPAIGN:1,Character Traits Web Enhancement,BOOKTYPE=Complete Core] 
PUBNAMELONG:Paizo Publishing, LLC 
PUBNAMESHORT:Paizo 
PUBNAMEWEB:http://paizo.com 
SOURCELONG:>full book name< 
<nowiki>#</nowiki> EXAMPLE - SOURCELONG:Advanced Player's Guide 
<nowiki>#</nowiki> EXAMPLE - SOURCELONG:Curse of the Crimson Throne, Chapter 1: Edge of Anarchy 
<nowiki>#</nowiki> EXAMPLE - SOURCELONG:Inner Sea World Guide 
SOURCESHORT:>short book name< 
<nowiki>#</nowiki> EXAMPLE - SOURCESHORT:APG 
<nowiki>#</nowiki> EXAMPLE - SOURCESHORT:EOA 
<nowiki>#</nowiki> EXAMPLE - SOURCESHORT:ISWG 
SOURCEWEB:>url link to exact store location< 
<nowiki>#</nowiki> EXAMPLE - SOURCEWEB:http://paizo.com/store/downloads/pathfinder/pathfinderRPG/v5748btpy8fo1 
<nowiki>#</nowiki> EXAMPLE - SOURCEWEB:http://paizo.com/pathfinder/adventurePath/curseOfTheCrimsonThrone/v5748btpy81xw 
<nowiki>#</nowiki> EXAMPLE - SOURCEWEB:http://paizo.com/store/games/roleplayingGames/p/pathfinderRPG/paizo/pathfinderChronicles/v5748btpy8ief 
SOURCEDATE:>release date as 4 digit year dash 2 digit month (2008-08) 
<nowiki>#</nowiki> EXAMPLE - SOURCEDATE:2010-08 
<nowiki>#</nowiki> EXAMPLE - SOURCEDATE:2008-03 
<nowiki>#</nowiki> EXAMPLE - SOURCEDATE:2011-03 
ISOGL:YES 

<nowiki>#</nowiki> Place errata version/applied dates here (multi-lines as need be) 
<nowiki>#</nowiki> EXAMPLE - Errata: December 4, 2012 "Monkeying Around" Article - http://paizo.com/paizo/blog/v5748dyo5le61?Monkeying-Around (Andrew Maitland) 
<nowiki>#</nowiki> EXAMPLE - Errata: January 35, 2250 "274th errata update" - >weblink< - (>name of updater<) 

COVER:>book cover<.jpg 
LOGO:@/publisher_logos/Paizo_Publishing.png 
URL:WEBSITE|http://www.paizo.com/|Visit Paizo Publishing! 

INFOTEXT:>text< 
COPYRIGHT:>text< 
 
<nowiki>#</nowiki> Do Not Remove Comment 
<nowiki>#</nowiki> EXTRAFILE:OGL.txt 
 
<nowiki>#</nowiki> Data Files 
ABILITY:>source short name<_abilities.lst 
ABILITY:>source short name<_abilities_classes.lst 
ABILITY:>source short name<_abilities_companion.lst 
ABILITY:>source short name<_abilities_equipment.lst 
ABILITY:>source short name<_abilities_race.lst 
ABILITY:>source short name<_abilities_template.lst 
ABILITYCATEGORY:>source short name<_abilitycategories.lst 
BIOSET>source short name<_biosettings.lst 
CLASS:>source short name<_classes.lst 
CLASS:>source short name<_classes_race.lst 
COMPANIONMOD:>source short name<_companionmods.lst 
DEITY:>source short name<_deities.lst 
DOMAIN:>source short name<_domains.lst 
EQUIPMOD:>source short name<_equipmods.lst 
EQUIPMENT:>source short name<_equip_general.lst 
EQUIPMENT:>source short name<_equip_magic_items.lst 
EQUIPMENT:>source short name<_equip_arms_armor.lst 
FEAT:>source short name<_feats.lst 
KIT:>source short name<_kits.lst 
KIT:>source short name<_kits_race.lst 
KIT:>source short name<_kits_companion.lst 
LANGUAGE:>source short name<_languages.lst 
RACE:>source short name<_races.lst 
RACE:>source short name<_races_companion.lst 
SKILL:>source short name<_skills.lst 
SPELL:>source short name<_spells.lst 
TEMPLATE:>source short name<_templates.lst 
ARMORPROF:>source short name<_profs_armor.lst 
SHIELDPROF:>source short name<_profs_shield.lst 
WEAPONPROF:>source short name<_profs_weapon.lst 
 

===Pathfinder Specific===

[[Pathfinder RPG]]

Eric C Smith

2014-04-27T14:03:13Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=

Eric C Smith, aka Maredudd, aka Tenacious Monkey, has been a member of the PCGen team since Sept/Oct of '06.

=Teams=
{| class="wikitable" border="1"
|-
| Team || Rank
|-
| [[Admin]] - [[Release]] || [[Explanation of Teams#Gibbon|Gibbon]] (Mac and OOC Releases)
|-
| [[Admin]] - [[Tracker]] || [[Explanation of Teams#Gibbon|Gibbon]]
|-
| [[Admin]] - [[Website]] || [[Explanation of Teams#Lemur|Tamarin]]
|-
| [[Content]] - [[Documentation]]|| [[Explanation of Teams#Second|2nd]]
|-
| [[Content]] - [[Data]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Publisher Liaison]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Data License]] || [[Explanation of Teams#Chimp|Chimp]]
|-
| [[Public Relations|PR]] - [[Advertising]] || [[Explanation of Teams#Chimp|Chimp]]
|}

=Contact Details=
{| class="wikitable" border="1"
|-
| Timezone || GMT -5 (US EST)
|-
| Email || maredudd@blackroot.org
|-
| AIM ID || Maredudd
|-
| Yahoo Chat ID || maredudd800
|-
| SF ID || maredudd800
|-
| Web Site || http://www.blackroot.org
|}

=Trackers=
* Documentation Trackers
* New Tag Trackers
* Data Trackers
* New Source Trackers

=General Tasks=
* General Doc 2nd duties
* Performing OGL reviews on new data sets.
* Work documentation issues.

=Specific Documentation Tasks=
* [[PCGen Tag Dictionary Conversion to XML]]
* [[PCGen Documentation Style Guide]].
: * [[Documentation Style Review Status]] page.

=Specific Data Tasks=
* [[PCGen Support for Savage Worlds|Developing Savage Worlds GameMode and Data Set]]

Main Page

2014-04-04T15:44:31Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Main Page

2014-04-04T15:43:30Z

Maredudd: Reverted edits by Maredudd (talk) to last revision by Nylanfs

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[PCGen_6.02.00_Released!]]'''

'''[[PCGen_6.02.00RC2_Released!]]'''

'''[[PCGen 6.01.05 (Alpha) Released!]]'''

'''[[PCGen 6.00.1 Released!]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Main Page

2014-04-04T15:42:36Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[Advertising]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Main Page

2014-04-04T15:40:59Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[Advertising|Older press releases can be found here.]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Main Page

2014-04-04T15:39:01Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[Advertising]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising|Older press releases can be found here.]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Main Page

2014-04-04T15:36:37Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[Advertising]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Advertising

2014-04-04T15:35:00Z

Maredudd:

{| align="right"
| __TOC__
|}
=Introduction=
Welcome to the page for the [[Advertising]] Team page, a subteam of the [[Public Relations|PR Team]]!

=Mission=
To increase and maintain PCGen's mindshare among the RPG and Open Source Java communities.

=Advertisers=
* None

= Press Releases =

'''[[PCGen_6.02.01_Released!]]'''

'''[[PCGen_6.02.00_Released!]]'''

'''[[PCGen 6.02.00RC2 Released!]]'''

'''[[PCGen 6.01.05 (Alpha) Released!]]'''

'''[[PCGen 6.01.4 (Alpha) Released!]]'''

'''[[PCGen 6.00.1 Released!]]'''

=Articles=
* None

=Press Release Instructions=
* [http://sourceforge.net/news/?group_id=25576 PCGen News Archive]
* A Guide to Writing Press Releases (TBD)
* PCGen News Release Channels:
: * [http://games.groups.yahoo.com/group/pcgen/ pcgen @ Yahoo!Groups]
: * [http://forums.gleemax.com/forumdisplay.php?f=39 WotC Digital D&D]
: * [http://www.mortality.net/modules.php?op=modload&name=Submit_News&file=index Mortality.Net] Note: deceased website :(
: * [http://www.enworld.org/forumdisplay.php?f=6 ENWorld]
: * [http://www.rpg.net/press RPG Net]
: * [http://www.rpgnews.com/ RPGNews]
: * [http://paizo.com/paizo/messageboards/paizoPublishing/pathfinder/general Paizo's Pathfinder General Discusion Board] for Pathfinder data set releases.
: * [http://paizo.com/paizo/messageboards/community/gaming/dnd Paizo's D&D 3.5/d20/OGL Message Board] for general press releases.
: * [http://www.eruvian.com Eruvian]
* Other Channels:
: * [http://en.wikipedia.org/wiki/PCGen PCGen@Wikipedia]
: * [http://annex.wikia.com/wiki/PCGen PCGen@Annex]
: * [http://linux.softpedia.com/get/Utilities/PCGen-12365.shtml PCGen@Softpedia]
: * [http://freshmeat.net/projects/pcgen/ PCGen@FreshMeat]
* [[Press Release Templates]]:

=Active Team Members=
===[[Explanation of Teams#Silverback|Silverback]]===
* [[Paul Grosse]]

===[[Explanation of Teams#Second|2nd]]===
* [[Eric C Smith]]

===[[Explanation of Teams#Chimp|Chimp]]===

===[[Explanation of Teams#Gibbon|Gibbon]]===

===[[Explanation of Teams#Tamarin|Tamarin]]===

===[[Explanation of Teams#Lemur|Lemur]]===

=Inactive Team Members=

===[[Explanation of Teams#Second|2nd]]===
* [[David R. Bender]]

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Robert Ward
* [[Tir Gwaith]]

Main Page

2014-04-04T15:34:42Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[PCGen_6.02.00RC2_Released!]]'''

'''[[PCGen 6.00.1 Released!]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

Advertising

2014-04-04T15:34:08Z

Maredudd:

{| align="right"
| __TOC__
|}
=Introduction=
Welcome to the page for the [[Advertising]] Team page, a subteam of the [[Public Relations|PR Team]]!

=Mission=
To increase and maintain PCGen's mindshare among the RPG and Open Source Java communities.

=Advertisers=
* None

= Press Releases =

'''[[PCGen_6.02.01_Released!]]'''

'''[[PCGen_6.02.00_Released!]]'''

'''[[PCGen 6.02.00RC2 Released!]]'''

'''[[PCGen 6.01.4 (Alpha) Released!]]'''

'''[[PCGen 6.00.1 Released!]]'''

=Articles=
* None

=Press Release Instructions=
* [http://sourceforge.net/news/?group_id=25576 PCGen News Archive]
* A Guide to Writing Press Releases (TBD)
* PCGen News Release Channels:
: * [http://games.groups.yahoo.com/group/pcgen/ pcgen @ Yahoo!Groups]
: * [http://forums.gleemax.com/forumdisplay.php?f=39 WotC Digital D&D]
: * [http://www.mortality.net/modules.php?op=modload&name=Submit_News&file=index Mortality.Net] Note: deceased website :(
: * [http://www.enworld.org/forumdisplay.php?f=6 ENWorld]
: * [http://www.rpg.net/press RPG Net]
: * [http://www.rpgnews.com/ RPGNews]
: * [http://paizo.com/paizo/messageboards/paizoPublishing/pathfinder/general Paizo's Pathfinder General Discusion Board] for Pathfinder data set releases.
: * [http://paizo.com/paizo/messageboards/community/gaming/dnd Paizo's D&D 3.5/d20/OGL Message Board] for general press releases.
: * [http://www.eruvian.com Eruvian]
* Other Channels:
: * [http://en.wikipedia.org/wiki/PCGen PCGen@Wikipedia]
: * [http://annex.wikia.com/wiki/PCGen PCGen@Annex]
: * [http://linux.softpedia.com/get/Utilities/PCGen-12365.shtml PCGen@Softpedia]
: * [http://freshmeat.net/projects/pcgen/ PCGen@FreshMeat]
* [[Press Release Templates]]:

=Active Team Members=
===[[Explanation of Teams#Silverback|Silverback]]===
* [[Paul Grosse]]

===[[Explanation of Teams#Second|2nd]]===
* [[Eric C Smith]]

===[[Explanation of Teams#Chimp|Chimp]]===

===[[Explanation of Teams#Gibbon|Gibbon]]===

===[[Explanation of Teams#Tamarin|Tamarin]]===

===[[Explanation of Teams#Lemur|Lemur]]===

=Inactive Team Members=

===[[Explanation of Teams#Second|2nd]]===
* [[David R. Bender]]

===[[Explanation_of_Teams#Lemur|Lemur]]===
* Robert Ward
* [[Tir Gwaith]]

Main Page

2014-04-04T15:33:42Z

Maredudd:

{| align="right"
| __TOC__
|}

=Introduction=
PCGen is an Open Source '''FREE''' Java based character generator for d20 based Role-Playing games, it has many '''[[PCGen Features|Features]]''' and some '''[[PCGen Requirements|Requirements]]''' in order to run.

=Mission Statement=
To be the world's most flexible d20 character generation and maintenance software.

=Latest News!=

'''[[PCGen_6.02.01_Released!]]'''

'''[[PCGen_6.02.00RC2_Released!]]'''

'''[[PCGen 6.01.05 (Alpha) Released!]]'''

'''[[PCGen 6.00.1 Released!]]'''

=Community=
* [[Users]], (some who want to get straight to the [http://pcgen.sourceforge.net/autobuilds/pcgen-docs/index.html documentation]!)
* [http://pcgen.sourceforge.net/08_sponsors.php Sponsors]
* [[Publishers]]
* [http://pcgen.sourceforge.net/banners/ Our fantastic banners and images]
* [[Compatible 3rd Parties]]
* [[Conventions]]
* [[Mailing Lists and PCGen Links]]
* [http://jira.pcgen.org Issue Tracking] ('''Report Bugs and Feature Requests!''')
** [[JIRA Tracker List]]
* [[FAQ and Help]]
* [[Updating Homebrew Sets]]
* [[Beta Testers for Testing]]
* [[Open RPG Community Online Game]]

=Strategic Development=
* [[Roadmap]]
* [[Development Specs]]
* [[Future Development]]

=Team=
* [[Explanation of Teams]]
* [[Full Team Member Listing]] is a full listing of our current volunteers.

==Specific Teams==
* [[Board of Directors]] - (aka BoD), governs the project
* [[Architecture]]
* [[Code]] - (aka CM)
* [[Content]]
** [[Data]] (aka DM or LM)
** [[Output Sheets]] (aka OS)
** [[Documentation]]
* [[Admin]]
** [[Tracker]] (aka TM)
** [[Release]]
** [[Website]]
* [[Public Relations]]
** [[Publisher Liaison]] - (aka PL)
** [[Data License]]
** [[Advertising]]

= Licensing =
The core PCGen code is licensed under the [http://www.opensource.org/licenses/lgpl-2.1.php LGPL ver 2.1] open source license. Its various data sources are licensed under individual agreements, see the [[Data License]] team for details.

= Editing The Wiki =
To edit the wiki you'll need an account, contact the Wiki Admin (admin@pcgen.org) if you are joining the PCGen Community and wish to contribute to the actual wiki. Spammers need not apply.

PCGen Support for Savage Worlds

2013-09-23T02:29:14Z

Maredudd: /* Approach */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[Savage Worlds for PCGen - September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Space 1889: Red Sands
# Fantasy Companion
# Horror Companion and Ripper
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || In Place || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Functioning
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills), and Edges are in and selectable. Powers in work.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| armor_profs.lst || Complete || It looks like armor proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Armor" proficiency that every piece of armor will get.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || I needed to add a dummy feat to get PCGen to load a saved character but rather than create one on the FEAT file I created a FEAT in the racial ability file.
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| shield_profs.lst || Complete || It looks like shield proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Shield" proficiency that every shield will get.
|-
| skills.lst || In Work || Preliminary skills in place and working. Not sure what else needs to be done here.
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || Complete || It looks like weapon proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Weapon" proficiency that every weapon will get.
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T04:06:22Z

Maredudd: /* Status */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[Savage Worlds for PCGen - September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || In Place || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Functioning
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills), and Edges are in and selectable. Powers in work.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| armor_profs.lst || Complete || It looks like armor proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Armor" proficiency that every piece of armor will get.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || I needed to add a dummy feat to get PCGen to load a saved character but rather than create one on the FEAT file I created a FEAT in the racial ability file.
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| shield_profs.lst || Complete || It looks like shield proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Shield" proficiency that every shield will get.
|-
| skills.lst || In Work || Preliminary skills in place and working. Not sure what else needs to be done here.
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || Complete || It looks like weapon proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Weapon" proficiency that every weapon will get.
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T04:05:21Z

Maredudd: /* Status */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[Savage Worlds for PCGen - September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || In Place || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Functioning
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills), and Edges are in and selectable.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| armor_profs.lst || Complete || It looks like armor proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Armor" proficiency that every piece of armor will get.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || I needed to add a dummy feat to get PCGen to load a saved character but rather than create one on the FEAT file I created a FEAT in the racial ability file.
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| shield_profs.lst || Complete || It looks like shield proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Shield" proficiency that every shield will get.
|-
| skills.lst || In Work || Preliminary skills in place and working. Not sure what else needs to be done here.
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || Complete || It looks like weapon proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Weapon" proficiency that every weapon will get.
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T03:58:33Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[Savage Worlds for PCGen - September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || It looks like armor proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Armor" proficiency that every piece of armor will get.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || It looks like shield proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Shield" proficiency that every shield will get.
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || Complete || It looks like weapon proficiencies are not being used in SW but in order to enable equipment use I need to adapt PCGen proficiency system. To do this I have created a simple "Weapon" proficiency that every weapon will get.
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

Savage Worlds for PCGen - September 8, 2013 Update

2013-09-09T03:50:31Z

Maredudd:

= September 8, 2013, Savage Worlds on PCGen Update =

I thought is might be a good time to provide a status update on a side project I've been working, or not working depending on what else was going on in my life, for something like 5 years. That is building a Savage Worlds Data Set.

First, I have a page on our wiki where I have tried to document some of what I have done and a lot of what I'll mention here will eventually be placed on that page.

[[http://wiki.pcgen.org/PCGen_Support_for_Savage_Worlds Eric's Savage Worlds Project]]

But before I go into where I am technically speaking, let me briefly review where we stand permissions wise . . .

As we had at that time Full Permission for the Deadlands d20 material I figured we might be able to secure permission for the Savage Worlds material so in mid-2008 I sent a request for permission to Pinnacle Entertainment Group. It took a few months but I eventually got a reply from PEG granting permissions. With that in place I set out to build a gamemode. As it has been some time since the initial permissions were recieved, I plan on following up and confirming them.

Lots of time has now passed, which I will skim over as my effort varied in its efficacy depending on what else was going on in my life, but I have at this point made some good progress. This is where the Savage World data set currently stands:

= Savage Worlds GameMode =

The Savage Worlds GameMode is set and seems stable.

''equipmentslots.lst'' - I have not messed with this file yet as it is not clear to me yet which slots Savage Worlds uses. Armor can be placed on various body parts but at the core the torso is what counts. Additionally, current cannon, if there is such, for Savage Worlds is that a humanoid character with two hands and 5 fingers per hand can wear ten rings. One thing has become clear as I lurk on the PEGINC Forums . . . the GM has cart blanche when it comes to modifying the rules. I am just about to the point though were I will be ready to dig into the material to identify what slots are required by the core rules.

level.lst: This file is simple enough as level progression is clearly defined. 5 experience points grants a new level.

''load.lst'' - This file is a little more difficult. Load and encumbrance works differently in SW, as does size. The SIZEMULT and LOAD will need to be worked to finalize the gamemode. One item to note is that PCGen hardcodes the encumbrance designations and it would be very useful for Savage Worlds, and likely any other game system we might want to tackle one day, to decouple these designations. Have the encumbrance levels defined, by designation and level, in the gamemode.

''miscinfo.lst'' - Many of the tags in this file are likely going to be unnecessary for Savage Worlds, though it looks like I will need to include them with dummy information. One thing I will need eventually is to have the disabling of TABs enabled for the new GUI. SW does not use FEATS and I will not be using that tab. It will need to be disabled for the final SW solution.

I also note that the current SW gamemode posts errors relating to ACTYPEs. I haven't worked out how the ACTYPEs can be used for SW so I am not sure how any, if any, can be resolved as I move forward.

Something I may want to explore is to have gamemode specific CONTEXT Help pages, but I'll take a look at that later.

The BASEDICE tags are preliminary. I'll find out as I move forward if they are going to be useful and if so if they are set right.

Weapon Types seem like they will not be useful, though damage type might be.

Wield category does not seem to be used in SW. I'll know more as I move into the combat aspects of SW.

One big difference between d20 and SW is that the stats and skill ranks are identified as dice sizes. This is currently working in the gamemode and basic set so far, though it will require OS specific work arounds to carry the concept throughout. It is not clear if there is anything that could be done code wise to help here.

As of right now all ability categories are defined in the data set itself. This may not change.

I have created a preliminary troubleshooting OS to help while codiing. I might need help creating a full Preview OS, though I'll hold off for a bit before making any specific requests. (This might give me the opportunity to learn to build OSes.) I am also working on a summary sheet for the summary tab.

''paperinfo.lst'' - This file is unchanged

''pointbuymethods_system.lst'' - The content of this file has been commented out and does not seem to effect the operation of PCGen. This gamemode starts the character out with a "d4" dice, value of "1", with 5 points provided for stat increases. This is done through an ability pool.

''rules.ls'' -: All rules have been disabled for now. As I move forward I will assess which, if any, need to be re-enabled, or if any new rules need to be added.

''sizeadustment.lst'' - This file has been left alone for now but as I move forward and begin to activate AC and other aspects of the game system I will reassess. I do not know if this this file is criticale or if it can be disabled altogether.

''statsandchecks.lst'' - Five different stats are defined and working as expected for now.

''tips.lst'' - File left as is for now.

= Base Data Set: Savage Worlds Deluxe =

This set relies heavily on the ability object to make things work. As an example, I use the Skill object simply to track and display the skill ranks. Ranks are actually granted through abilities using the BONUS:SKILLRANK tag.

Proficiencies are not specifically used in SW so I have created a basic Armor, Shield, and Weapon proficiency. Equipment will have types that will be used as needed to implement combat bonuses or in support of other utilization effects. One problem I'll have to address is for weapon damage. In general damage is calculted by adding the STR bonus to the damage die roll, but not all weapons get the STR damage. SW standard practice is to identify the damage as such: Str+1d4. This will not work for the DAMAGE tag on equipment. I will explore using an EQMOD to identify when the STR is used and when it is not.

A note on EQMODS. Not sure yet if these will be used any differently than in d20 systems.

All Attribute (Stat), Skill, Hindrances, and Edge abilities have been created and can be added as required for the creation of an SW character. The crunch has not been added to the Hindrance and Edge abilities yet as that will require the combat and other miscelaneous rules crunch be in place.

At this time I do not plan on using the spell.lst file in the SW data set. As with stats and skills, spells will be implemented using the ability object. Is ther a way to differentiate between the various ability objects in te Temp Bonus display?

As of right now I have included only the "Human" race. I will be adding the core races after I get the core equipment input. After that I will be adding the Bestiary.

Finally, archetypes should be able to be set up using kits, and these will likely be one of the last things I set up.

Other Savage Worlds Sources

Once the core rules are up and running I will be working on the following sets, the order of which will depend upon what I feel like playing with at the time:

# Fantasy Companion
# Horror Companion
# Super Power Companion
# Necessary Evil
# The Savage World of Soloman Kane
# Space 1889
# Deadlands
# Rippers

One additional difficulty on the core set will be setting it up for genre support. As the SW Deluxe is laid out it supports fantasy, modern, pulp, horror, super-power, and many other genres. It might become easier once I start working on the companion books as well as the setting specific books, but I plan on creating specific campaign files for each genre specific data elements from the core set, as well as a campaign file for everything all at the same time, though I may wait until the companion books are done.

----
Eric C Smith, PCGen Doc 2nd 
PR/PL/Adv/Lic Chimp, Data/Doc Chimp 
Release/Tracker Gibbon, Web Tamarin 
aka. Maredudd, Tenacious Monkey

Savage Worlds for PCGen - September 8, 2013 Update

2013-09-09T03:47:06Z

Maredudd: Created page with "= September 8, 2013, Savage Worlds on PCGen Update = I thought is might be a good time to provide a status update on a side project I've been working, or not working dependin..."

= September 8, 2013, Savage Worlds on PCGen Update =

I thought is might be a good time to provide a status update on a side project I've been working, or not working depending on what else was going on in my life, for something like 5 years. That is building a Savage Worlds Data Set.

First, I have a page on our wiki where I have tried to document some of what I have done and a lot of what I'll mention here will eventually be placed on that page.

[[http://wiki.pcgen.org/PCGen_Support_for_Savage_Worlds Eric's Savage Worlds Project]]

But before I go into where I am technically speaking, let me briefly review where we stand permissions wise . . .

As we had at that time Full Permission for the Deadlands d20 material I figured we might be able to secure permission for the Savage Worlds material so in mid-2008 I sent a request for permission to Pinnacle Entertainment Group. It took a few months but I eventually got a reply from PEG granting permissions. With that in place I set out to build a gamemode. As it has been some time since the initial permissions were recieved, I plan on following up and confirming them.

Lots of time has now passed, which I will skim over as my effort varied in its efficacy depending on what else was going on in my life, but I have at this point made some good progress. This is where the Savage World data set currently stands:

= Savage Worlds GameMode =

The Savage Worlds GameMode is set and seems stable.

''equipmentslots.lst'' - I have not messed with this file yet as it is not clear to me yet which slots Savage Worlds uses. Armor can be placed on various body parts but at the core the torso is what counts. Additionally, current cannon, if there is such, for Savage Worlds is that a humanoid character with two hands and 5 fingers per hand can wear ten rings. One thing has become clear as I lurk on the PEGINC Forums . . . the GM has cart blanche when it comes to modifying the rules. I am just about to the point though were I will be ready to dig into the material to identify what slots are required by the core rules.

level.lst: This file is simple enough as level progression is clearly defined. 5 experience points grants a new level.

''load.lst'' - This file is a little more difficult. Load and encumbrance works differently in SW, as does size. The SIZEMULT and LOAD will need to be worked to finalize the gamemode. One item to note is that PCGen hardcodes the encumbrance designations and it would be very useful for Savage Worlds, and likely any other game system we might want to tackle one day, to decouple these designations. Have the encumbrance levels defined, by designation and level, in the gamemode.

''miscinfo.lst'' - Many of the tags in this file are likely going to be unnecessary for Savage Worlds, though it looks like I will need to include them with dummy information. One thing I will need eventually is to have the disabling of TABs enabled for the new GUI. SW does not use FEATS and I will not be using that tab. It will need to be disabled for the final SW solution.

I also note that the current SW gamemode posts errors relating to ACTYPEs. I haven't worked out how the ACTYPEs can be used for SW so I am not sure how any, if any, can be resolved as I move forward.

Something I may want to explore is to have gamemode specific CONTEXT Help pages, but I'll take a look at that later.

The BASEDICE tags are preliminary. I'll find out as I move forward if they are going to be useful and if so if they are set right.

Weapon Types seem like they will not be useful, though damage type might be.

Wield category does not seem to be used in SW. I'll know more as I move into the combat aspects of SW.

One big difference between d20 and SW is that the stats and skill ranks are identified as dice sizes. This is currently working in the gamemode and basic set so far, though it will require OS specific work arounds to carry the concept throughout. It is not clear if there is anything that could be done code wise to help here.

As of right now all ability categories are defined in the data set itself. This may not change.

I have created a preliminary troubleshooting OS to help while codiing. I might need help creating a full Preview OS, though I'll hold off for a bit before making any specific requests. (This might give me the opportunity to learn to build OSes.) I am also working on a summary sheet for the summary tab.

''paperinfo.lst'' - This file is unchanged

''pointbuymethods_system.lst'' - The content of this file has been commented out and does not seem to effect the operation of PCGen. This gamemode starts the character out with a "d4" dice, value of "1", with 5 points provided for stat increases. This is done through an ability pool.

''rules.ls'' -: All rules have been disabled for now. As I move forward I will assess which, if any, need to be re-enabled, or if any new rules need to be added.

''sizeadustment.lst'' - This file has been left alone for now but as I move forward and begin to activate AC and other aspects of the game system I will reassess. I do not know if this this file is criticale or if it can be disabled altogether.

''statsandchecks.lst'' - Five different stats are defined and working as expected for now.

''tips.lst'' - File left as is for now.

= Base Data Set: Savage Worlds Deluxe =

This set relies heavily on the ability object to make things work. As an example, I use the Skill object simply to track and display the skill ranks. Ranks are actually granted through abilities using the BONUS:SKILLRANK tag.

Proficiencies are not specifically used in SW so I have created a basic Armor, Shield, and Weapon proficiency. Equipment will have types that will be used as needed to implement combat bonuses or in support of other utilization effects. One problem I'll have to address is for weapon damage. In general damage is calculted by adding the STR bonus to the damage die roll, but not all weapons get the STR damage. SW standard practice is to identify the damage as such: Str+1d4. This will not work for the DAMAGE tag on equipment. I will explore using an EQMOD to identify when the STR is used and when it is not.

A note on EQMODS. Not sure yet if these will be used any differently than in d20 systems.

All Attribute (Stat), Skill, Hindrances, and Edge abilities have been created and can be added as required for the creation of an SW character. The crunch has not been added to the Hindrance and Edge abilities yet as that will require the combat and other miscelaneous rules crunch be in place.

At this time I do not plan on using the spell.lst file in the SW data set. As with stats and skills, spells will be implemented using the ability object. Is ther a way to differentiate between the various ability objects in te Temp Bonus display?

As of right now I have included only the "Human" race. I will be adding the core races after I get the core equipment input. After that I will be adding the Bestiary.

Finally, archetypes should be able to be set up using kits, and these will likely be one of the last things I set up.

Other Savage Worlds Sources

Once the core rules are up and running I will be working on the following sets, the order of which will depend upon what I feel like playing with:

# Fantasy Companion
# Horror Companion
# Super Power Companion
# Necessary Evil
# The Savage World of Soloman Kane
# Space 1889
# Deadlands
# Rippers

One additional difficulty on the core set will be setting it up for genre support. As the SW Deluxe is laid out it supports fantasy, modern, pulp, horror, super-power, and many other genres. It might become easier once I start working on the companion books as well as the setting specific books, but I plan on creating specific campaign files for each genre specific data elements from the core set, as well as a campaign file for everything all at the same time, though I may wait until the companion books are done.

----
Eric C Smith, PCGen Doc 2nd
PR/PL/Adv/Lic Chimp, Data/Doc Chimp
Release/Tracker Gibbon, Web Tamarin
aka. Maredudd, Tenacious Monkey

PCGen Support for Savage Worlds

2013-09-09T03:37:12Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[Savage Worlds for PCGen - September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T03:31:36Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [[September 8, 2013 Update]]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T03:31:00Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [September 8, 2013 Update]

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T03:30:46Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* [September 8, 2013 Update\

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-09T03:29:10Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Status Update =
* September 8, 2013 Update

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-05T04:13:11Z

Maredudd: /* Status */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the SW set to the point were I can create a simple SW character. Traits, hindrances, and edges are in and are accessible for character creation and advancement. The effects for the hindrances and edgs have not been activated yet.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-03T06:04:45Z

Maredudd: /* Specific Challenges */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet - troubleshooting preview sheet displays attributes and skills.
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-09-03T06:02:35Z

Maredudd: /* Status */

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Hindrances and Traits (attributes and skills) entered and selectable. Edges are in and selectable but cost needs to be worked out.
|-
| abilitycategory.lst || in Work || Preliminary categories done and working. Initial trait pools loaded here instead of in class file.
|-
| class.lst || In Work || Class works. (Initial trait loading moved to ability category file.)
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object.
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-08-19T21:13:50Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '''Necessary Evil''', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Preliminary Hindrances, Traits (attributes and skills) and most Edges in place
|-
| abilitycategory.lst || in Work || Preliminary categories done and working
|-
| class.lst || In Work || Class works and grants initial traits
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-08-19T21:12:19Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', '"Necessary Evil"', '''Dead Lands: Reloaded''', '''Rippers''', '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Preliminary Hindrances, Traits (attributes and skills) and most Edges in place
|-
| abilitycategory.lst || in Work || Preliminary categories done and working
|-
| class.lst || In Work || Class works and grants initial traits
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-08-14T07:47:10Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', "Necessary Evil", '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || Working || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || Working || Not sure how size works in Savage World
|-
| statsandchecks.lst || Working || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Preliminary Hindrances, Traits (attributes and skills) and most Edges in place
|-
| abilitycategory.lst || in Work || Preliminary categories done and working
|-
| class.lst || In Work || Class works and grants initial traits
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Had to include one language to squash log errors
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place and working mostly
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}

PCGen Support for Savage Worlds

2013-08-14T01:54:40Z

Maredudd:

{| align="right"
| __TOC__
|}

= Introduction =
Hi Folks! Maredudd here!

This project is a personal project I am taking on as an unofficial effort, yet with intent, to explore PCGen's flexibility when it comes to non-d20 gaming systems. The game system I have selected to work with is [http://www.peginc.com/ Pinnacle Entertainment Group's] Savage Worlds Game. I think it will be a great vehicle for proving PCGen's flexibility for supporting non-d20 systems, and PCGen has recently recieved [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/docs/acknowledgments/publishersandsources.html#PinnacleEnt permissions] for Pinnacle Ent. Group's '''Savage Worlds''' product line.

= Team =
{|
|-
! align="left" | Data Monkey
| [[Eric C Smith | Maredudd]]
|-
! align="left" | OS Monkey
| [[LegacyKing | Andrew Maitland]] for some stuff
|}

= Schedule =
There is currently no time frame in which this project is scheduled to be completed. In addition, PCGen's 5.16 and 6.0 developmental cycles are focusing on adding support for 4E/Pathfinder and the conversion to CDOM respectively. You can, on the other-hand, watch this space to see what kind of progress we are making. Please note though that no data sets will be provided for distribution until permission from Pinnacle has been granted.

= Approach =
The gameMode files and data files will be developed in parallel in support of the core rule set as described in '''Savage World Deluxe'''. The final steps in this project will be to develop LST files for at least one Savage World game setting. I currently own a copy of "The Savage World of Solomon Kane", '''Red Sands''', "Necessary Evil", '''Fantasy Companion''', '''Horror Companion''', and '''Super Powers Companion''', so it is likely that once the core rules are demonstrably working, I will start working on some of these game settings. The priority will be as follows:

# Red Sands
# Fantasy Companion
# Horror Companion
# Super Powers Companion and Necessary Evil
# The Savage World of Solomon Kane

'''Note:''' As of this update PEG is working on a SciFi Companion. When it comes out I plan on picking it up and will insert it into the implementation list just after Red Sands.

= Challenges =
A few challenges exist that will need to be tackled. (Others will be added as identified.)
== General Questions ==
* Is the character generation and maintenance effort required for Savage Worlds complex enough to warant adapting PCGen to the system?
: ''I have been told that SW is simple enough not to need a Char Gen but there are a number of PCGen's competitors that have implemented SW Char Gen, so I'm going to say:'' '''Yes'''.
* What new LST Tag/OS Token support is required?
* What GUI modifications are required?
== Specific Challenges ==
* Traits include both "Attributes" and "Skills":
** Traits are identified by a dice type, not by numerical value. (e.g. d4, d6, d8, etc.) PCGen is currently capable of doing this, though how this propagates through the rest of the program has yet to be seen.
** Attributes, or stats, include the following: Strength, Vigor, Agility, Smarts and Spirit.
** Derived attributes include Charisma, Pace, Parry, and Toughness.
** Skills will be implemented with a combination of the "skill" object to track the RANK and the "ability" object to handle advancement.
*** The cost of a Skill Rank increase depends upon the value of the attribute (stat) to which that skill is tied. (e.g. Increasing the rank of the "Fighting" skill from d6 to d8 costs 1 point if the "Agility" attribute is d8 or greater but costs two points if it is d6 or less.)
*** This is being implemented as a pair of "Trait Advances" (TA) with a PREVAR looking at the skill "RANK" and the relevant attribute. One TA will cost one point, the other will cost two.
* Hinderances and Edges (equivalent to feats/abilities) should be able to be implemented via PCGen's ability object.
* Savage Worlds is a classless system, at least the core is, so I will be creating a "Generic Class" that will form the foundation of all characters.
* Characters advance by level, gaining points for stats, skills, and edges, but few other calculations are based upon the character's level.
* Every five levels a character advances in 'rank', a text-based 'Level' designation, beginning with 'Novice' and moving up to 'Legendary'.
** Each rank increase advances an attribute/stat of the players choice. This can be implemented with a simple variable for tracking purposes, but I'll have to find a way to get a textual representation.
**This can be implemented as an additional derived attribute, i.e. CharacterRank, that is set equivalent to "CL/5+1" and using an "ability" that grants templates for each "Rank" at the appropriate levels.
*** Example: <code>TEMPLATE:Novice|PREVAREQ:lvlRank,1 <tab> TEMPLATE:Seasoned|PREVAREQ:lvlRank,2 <tab> TEMPLATE:Veteran|PREVAREQ|lvlRank,3 <tab> TEMPLATE:Heroic|PREVAREQ:lvlRank,4 <tab> TEMPLATE:Legendary|PREVAREQ|lvlRank,5</code>
* Output Sheets:
** Development/Test Sheet
** Character Sheet

= Status =
I have the gameMode files started but not tested yet and am starting on the Skills and Abilities LST files.

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''GameMode Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| equipmentslots.lst || || Not sure what will go here as Savage Worlds doesn't use equipment slots as an element of the rules
|-
| level.lst || Complete || Untested
|-
| load.lst || Complete || Untested
|-
| miscinfo.lst || In Work || Still working out what MUST be included to make a valid gamemode
|-
| paperInfo.lst || Complete || No Change Required
|-
| pointbuymethod.lst || Complete || Untested
|-
| sizeAdjustment.lst || In Work || Not sure how size works in Savage World
|-
| statsandchecks.lst || In Work || Lots more to do here to implement underpinnings of Traits/Hinderance/Edge system
|}

{| border="1" cellpadding="5" cellspacing="0"
|+ align="left" | '''Data Files'''
|-
! align="left" | LST File !! align="left" | Status !! align="left" | Comment
|-
| ability.lst || In Work || Preliminary Hindrances, Traits (skill) and most Edges in place
|-
| abilitycategory.lst || In Work || Preliminary categories done
|-
| class.lst || In Work || Lots to do, and figure out, here
|-
| companionmods.lst || N/A || At least for now
|-
| deities.lst || N/A || At least for now
|-
| domains.lst || N/A || At least for now
|-
| equipment.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| equipmods.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| feats.lst || N/A || All class features are being developed using the "ability" object
|-
| kits.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| languages.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| races.lst || In Work || Only one race will be developed for now. Other will be added after character development is working
|-
| skills.lst || In Work || Preliminary skills in place
|-
| spells.lst || On Hold || Not sure if this file will be required or if "spells" will be implemented with the "ability" object
|-
| templates.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| weaponprofs.lst || On Hold || Will implement after I get the core gamemode and character development working
|-
| savage_worlds.pcc || In Work || Preliminary PCC completed but will update as necessary
|}

= Roadmap =
This is the collection of trackers opened in support of this effort.

== Development Specs ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| || TBD ||
|}

== Feature Requests ==
{| border="1"
|-
! Link !! align="left" | Title !! Status
|-
| [https://sourceforge.net/tracker/index.php?func=detail&aid=1328300&group_id=25576&atid=384722 1328300] || Variables that can hold text || '''Open'''
|}