PCGen Wiki - User contributions [en]

Talk:LegacyKing and MertonMonk discuss specs for replacement app

2025-10-30T01:49:11Z

LegacyKing: Initial responses.

'''mertonmonk''' — 5:21 PM
My thoughts in partially random order:
The 'rules' and 'basic formulas' associated with a game-type can be contained in a default character that is associated with that game-type. This way you can associate the default ability scores and other base elements, including formulas for determining ac, hp, etc, to a default character. The PC's character has a reference to this default character, so the PC character really only contains character selections. For example, a dwarf cleric of level 1 would have a character object that contains links to the default pc, the dwarf object, cleric object, cleric-level-1 object, total-class-level 1 object, and links to whatever objects the character selected for being a dwarf and a level 1 cleric. I like your idea about uids.

The data files for a particular source could be split into multiple files (say, all the feats in one file, classes in another, etc.) or they could all be in one file. Since the object structure for all objects will be the same, having them all in one easily-shared file is a possibility. Having it in multiple files makes it easier for people to split up the work for crafting the data.

'''mertonmonk''' — 5:36 PM
Internally the code should contain all the data about a character in a map and stacking rules can be defined/applied to the map nodes. All values should be in the format main.sub1...subx..bonustype. For example, combat.ac.armor, would be a valid bonus key. Each value would also contain a link to the source of where it came from so debugging a value is easier.
We will need to discuss the syntax of formulas. There are free libraries that can be used to evaluate a math equation once all tokens have been replaced with numerics.

'''LegacyKing''' — 6:37 PM
Having multiple files allows for easier debugging - and easier organization. Some files are already thousands of lines long I don't imagine it'd be fun to try and find x.

I'm up for the discussion, let me know. The beauty of what Tom Parker built is it supports non-numerical formats. Replacing a string with another string, changing alignment (reversing alignment or gender due to a cursed item is possible).

LegacyKing and MertonMonk discuss specs for replacement app

2025-10-29T16:23:08Z

LegacyKing:

This page is to lay the groundwork for taking the best of existing PCGen and being unhindered with backwards compatible constraints to build a PCGen "Remastered".

== Design Philosophy: Data driven, code engine system agnostic ==

UI/UX - Every "blade" should be fully customizable and language friendly (Support for any language) - We should be able to define these by 'system'

PCGen built sets based on books, which is a nice structure to understand what is included. But the method of selecting compatible books was painful. A checkbox and tree view would be ideal. Also the idea of optional rules being selected here would make sense. (DISCUSSION TOPIC)

Legal - Systems Licenses should be displayed or available to view, and each content source should clearly delineate it's license.

Code will utilize a simplistic design to replicate to all objects.

OUTPUT/DISPLAY - Most groups use smaller devices at their tabletop, formats like html or pdf that can be viewed is nice. We don't expect the app to be used real-time, but if it is, the displays should work and present the up-to-date details (especially true for temporary bonuses).
* EXPORT: Do we retain the three formats, or move to a single format? FREEMARKER template engine is an impressive engine, it does have some drawbacks that the export needs to understand to function fully, but the engine has made vast improvements.

PDF - Has the most support and backend configuration (base.xml.ftl with the macros and templates > various blocks to allow for modular sheet building)
- Talks surrounding a unified platform that could alter the output to various formats (Honestly a single template with multiple exports would be ideal and cut down on the knowledge required to add/remove features).

== CODE / CONTENT ==

=== Re-use the code that shows promise: ===

Formula (Replacement for JEP)

Full Write up here - [http://pcgen.org/w/index.php/Setting_up_the_new_Formula_System Setting up the Formula System]

* MODIFY/MODIFYOTHER - Handles all variables
* - [http://pcgen.org/w/index.php/Dynamic_Scopes DYNAMIC Scopes]
* - [http://pcgen.org/w/index.php/Lookup_Table LOOKUP TABLES]
* - [http://pcgen.org/w/index.php/INFO/INFOVARS INFO/INFOVARS]

Not Coded:
* [http://pcgen.org/w/index.php/SELECTION_-_A_CHOOSE_Replacement SELECTION] (replace the CHOICE/CHOOSER)

== What are we solving for - aka Requirements ==

In most d20 systems a character must prequalify before taking something (feats, powers); conversely, during some situations, the qualifications may be lost causing the loss of an ability (required)

Examples:
* If a feat required Dex 13, and the character's dexterity is below 13 they lose access to the benefits of the feat.
* A spellcaster requires a minimum spellcasting score to cast any given level.

PRE/REQ

PRE: What it takes to take the object
REQ: What it takes to use the object

Spells/Power - This system while functional, is outdated and requires a major facelift.

Requirements -
Ability to group spells together in a hierarchy (Classification, List, Level, or class/level as required by the system)

Examples:
* 1e spells were grouped by category, schools, class and level
* 3e spells were grouped by category, class specific level (Also some had special subcategories of casting/ability such as Specialization for wizards, and Domains for clerics)
* 4e spells were called 'powers' and categorized by tiers and class
* 5e spells were grouped by category, level

Spells need to be selectable based upon criteria, assignable to specific class or category. And update in real-time (We've had issues where spell assignments never populated until application or character reload)

Additionally, the ability to add and remove things such as attachments or crystals to equipment (aka containers) is a necessary issue. Tom, Mark and myself had a discussion on how to make sure bonuses would apply when attachments are used here: [[Proposal_Attachment|Attachment Proposal]]

Character save files:
1) Limitations - The saved file lacks the photo assigned to it (Dimensions, etc.) meaning a GM sent the file cannot have a working copy. The filepaths are absolutes typically meaning companions are broken when shared.

Directory Structure should allow for a more unified experience.

Characters and associated companions should be saved as such:
* character_directory/game_system/characters <-- all characters
* character_directory/game_system/characters/companions <-- All support companions

Taking a best practice, we should encode a uid for every character and use that as the reference to the pairing for companions (if we can make these globally unique, great, otherwise, something randomly generated based off of date, time and a random salt created per installation)

I'll use an xml format for illustration purposes, I really don't care how the final file format is made... But some initial ideas

<character>
<name>Baldwin</name>
<uid>20251029_efffe34437389734</uid>
<linked_uids>
<uid_1>
<uid>20251029_fffejahdkjjkf</uid>
<reference_name>Baldwin's Familiar</reference_name>
<reference_relationship>companion</reference_relationship>
</uid_1>
<linked_uids>
</character>

<character>
<name>Baldwin's Familiar</name>
<uid>20251029_fffejahdkjjkf<uid>
<linked_uids>
<uid_1>
<uid>20251029_efffe34437389734</uid>
<reference_name>Baldwin</reference_name>
<reference_relationship>master</reference_relationship>
</uid_1>
<linked_uids>
</character>

NICE TO HAVE:
* - Customizer

SUBPAGES:

[[PCGen 2e - Token List]]

[[Pathfinder 2e - Remastered design]]

LegacyKing and MertonMonk discuss specs for replacement app

2025-10-29T06:28:52Z

LegacyKing: /* Re-use the code that shows promise: */

Pathfinder 2e - Remastered design

2025-10-28T23:11:28Z

LegacyKing: Created page with " Breakout (We need an ability to display Icons to represent actions and traits) ABILITY SCORE <-- Strength Dexterity Constitution Intelligence Wisdom Charisma Score is a..."

Breakout (We need an ability to display Icons to represent actions and traits)

ABILITY SCORE <--
Strength
Dexterity
Constitution
Intelligence
Wisdom
Charisma

Score is a value 1-30 typically.

System specific rules
Default method: All characters begin with a value of 10 in all ability scores, ability boosts add 2 to the score while ability flaws reduce by 2. However, if the score is 18 or higher, the boost benefit is reduced to 1. Furthermore, level 1 characters may not have a starting value over 18.

Alternatives - roll and assign.

Alignment (Moral and ethical attitude) (Standard nine Good, Neutral, Evil with Lawful, Neutral and Chaos axis)

Age has no mechanical bearing in 2e

Ancestries (aka Race or Species)
* Dwarf
* Elf
* Gnome
* Goblin
* Halfling
* Human

Heritage + Ancestry Feat

Backgrounds

Hit Points - No longer just from Class levels, but also dictated by Ancestry.

Classes (Levels 1-20) PF2e caps at level 20
* Alchemist
* Barbarian
* Bard
* champion
* Cleric
* Druid
* Fighter
* Monk
* Ranger
* Rogue
* Sorcerer
* Wizard

Skills

Feats

Equipment

Spells

MISC:

Rules
Conditions

Version LK has is OGL v1.0a

LegacyKing and MertonMonk discuss specs for replacement app

2025-10-28T22:47:57Z

LegacyKing:

LegacyKing and MertonMonk discuss specs for replacement app

2025-10-28T22:47:34Z

LegacyKing:

PCGen 2e - Token List

2025-10-28T22:46:44Z

LegacyKing: Initial page creation

What to use where...

The vast majority of tokens in PCGen today are game system specific for a base d20 game system. Some are characteristics that needed to be captured but can easily be handled with newer systems.

d20 uses AGE and has milestones associated with certain age categories. Infant, child, youth, adult, middle-aged, old, ancient. To make this even more nuisanced, every race or species has a different age threshold. Humans are vastly different to elves and dwarves. Certain characteristics players enjoy having randomizers:
Hair color, eye color, skin tone, height, weight, sex/gender, handed, even names. While some races these characteristics don't apply - Lizardfolk/Dragonkin don't have hair. We need a method to alter some fields and inputs to be morphed to handle the diversity of the species available to a player.

Additionally, newer game systems have completely altered the rules between a playable races and those that are controlled by a Game Master - requiring the ability to switch rules based on whether the character created is a player character or non-player character. See Sagaborn as an example of a complete separation between player generated characters, and GM generated characters.

While the intention is to support any game system, the focus initially will be around Pathfinder 'Remastered' as that is what is being used currently, and allows for a complete design shift for support.

As a general principle, all variables shall utilize the existing formula system Tom Parker created:

MODIFY and MODIFYOTHER
* MODIFY is a direct modification of the object it is on if a local scope, or a GLOBAL variable.
* MODIFYOTHER is a modification of a local scope from another object (Think Feat altered a weapon such a improving the value of the critical)

TABLE allows for things that can be referenced in a table or occur in a table. Some use cases - Encumbrance Load based upon the strength score (3e/35e/PF1e)

DISCUSSION LIST:

APPROVED LIST:

LegacyKing and MertonMonk discuss specs for replacement app

2025-10-28T22:24:08Z

LegacyKing: Created page with "This page is to lay the groundwork for taking the best of existing PCGen and being unhindered with backwards compatible constraints to build a PCGen "Remastered". == Design..."

Development Specs

2025-10-28T21:06:34Z

LegacyKing: Discussion regarding new app to replace the aging pcgen...

{| align="right"
| __TOC__
|}

=Introduction=

This section lists the various Data Driven specifications under development

[[LegacyKing and MertonMonk discuss specs for replacement app]]

== Specs currently under development ==

[[Critical Thinking - Altering how we do things]]

[[Limiting Known Spells from Domains]]

[[Skill Cost and CSKILL Overhaul]]

[[Spell Improvements]]

[[Advanced Spell Chooser]]

[[Prerequisites for Armor and Shield Proficiencies]]

[[DONOTADD Tag Proposal Updates]] < Handy for Eclipse, but not required >

[[Method to Grant Companions Benefits direct from Master's Selections]] < Definitely handy for Eclipse >

[[New Tag - Ability to Dynamically Handle HD/HP as a Var in a Single Class]] <Definitely Handy for Eclipse>

[[Ability to Alter Skill Points per Level in a Single Class Dynamically]] <Almost crucial to better support Eclipse>

[[The Ability to Add additional Skill Cost changes dynamically]] <Needed for Eclipse>

[[The Ability to Dynamically add spells to a Spell List]] <Multiple Sets can use this>

[[The Ability to Choose an Ability/Feat from a list and have it be assigned to a character]] <Handy for any set>

[[The Ability to Adjust the Cost of an Ability/Feat]] <Crucial for Eclipse Support>

[[We need a method to track when an ability was gained]] <Crucial for Practical Enchanter>

[[COMPANIONLIST Improvements]] Something that would be helpful for new sources support

[[Eclipse Master List]] Showing List of Issues for Eclipse

[[Conditional Skill Proposal]] Better design to handle conditional skills

[[BONUSTYPE to replace TYPE in assigning bonuses]]

== Finalized Specs which now have associated code FREQ trackers ==

[[Pathfinder bonus feat progression]]

[[Additional Weapon Damage]]

[[Equipment Variables]]

== Finalized Specs which are now closed ==

[[SORTKEY - The Ability to Sort Items other than default NAME alphabetical]] 5.17.4

[[Spells Tab Revamp]] in 5.14.0

[[ASPECT tag for Abilities and Feats]] in 5.15.3

[[Pathfinder feat progression]] in 5.15.4

[[Quick Source Loading Page]]

Lookup Table

2023-06-22T22:28:39Z

LegacyKing: Created page with "Now it's lookup(TABLE[x,y], x, COLUMN[y]) TABLE and COLUMN will be special types. Both are complicated types, meaning they will look something like: * TABLE[NUMBER,STRING] *..."

Now it's lookup(TABLE[x,y], x, COLUMN[y])

TABLE and COLUMN will be special types. Both are complicated types, meaning they will look something like:
* TABLE[NUMBER,STRING]
* or
* COLUMN[STRING]

Note that a MODIFY doesn't look any different. It's still:
* MODIFY:TABLENAME|SET|SomeTable

"SomeTable" is still a string to a naive reader, but what the system will do at that point is make sure that SomeTable can actually be interpreted as a TABLE[x,y]... rather than just treating it as a String. Similar for the column names.

In that way, the first variable will allow multiple tables to be swapped in, AS LONG AS they are the right format. If the format is not compatible, then all bets are off and you'll get an error. Note that a table that has formats like this:

* NUMBER,NUMBER,STRING

... will have multiple valid places it can be used, including:
* TABLE[NUMBER,NUMBER]
* TABLE[NUMBER,STRING]

This doesn't mean you can assign one TABLE format to another if the table happens to be compatible. I'm not even going to TRY to manage that one... and the use case is probably pretty narrow anyway.

Note that this still allows some runtime errors, but catches a lot of possible issues. It is still possible to do a lookup on a Table that doesn't contain a specific column of the given name. So if the third variable is COLUMN[NUMBER], we can check at load that the TABLEFORMAT has columns of FORMAT=NUMBER, but we can't guarantee the variable will resolve to a name actually in that table... that will have to wait for a runtime error. That's life, but it does allow us to know the formats at load time, so we do get a lot of error checking in the context of the usage, if not the exact table and column names.

Tom

* STARTTABLE:Carrying Capacity,
* Strength,Capacity
* NUMBER,NUMBER
* 1,10
* 2,20
* ...
* 29,1400
* ENDTABLE:Carrying Capacity,

Ignoring some of the diagnosis of bad inputs that will be necessary, this is the key logic:
* (1) This format of START and END allows more than one table per file (avoids sprawl)
* (2) Trailing commas are ignored (this allows the STARTTABLE and ENDTABLE lines to have blank cells where the rest are the table contents... we don't want to complain on minor things that may tools will do.)
* (3) Blank lines will be ignored. This includes lines with commas but without content. (allows tables to be separated by blank lines or lines of all commas)
* (4) The column names (Strength,Capacity) are always the first line of the table. The Formats are always the second line. The rest of the lines are content of the table
* (5) Attempts to use embedded line breaks or embedded quotes may or may not be supported by the parsing system, but certainly aren't supported for purposes of PCGen.
* Optionally:
* (6) Lines that have the first cell starting with "#" are considered comment lines and will be ignored. This will likely need to include if the first cell is escaped in quotes, just for protection from any tools that quote by default.

The dicestep then becomes more like:

* STARTTABLE:Dice Step,,,,,,,,,
* Dice,DOWN5,DOWN4,DOWN3,DOWN2,DOWN1,SELF,UP1,UP2,UP3,UP4,UP5,...
* DICE,DICE,DICE,DICE,DICE,DICE,DICE,DICE,DICE,DICE,DICE,DICE,...
* ...
* 1d3,-,-,0,1,1d2,1d3,1d4,1d6,1d8,2d6,3d6,...
* ...
* ENDTABLE:Dice Step,,,,,,,,,

Note that "self" here is clearly defined, and it's a matter of pulling out of the correct column. Since the CSV format ignores leading/trailing spaces, one can easily have a spaced out version that is a table in a text editor if folks don't want to edit in a spreadsheet. (Having someone write a "PrettyTable" ... a trivial perl or python program to do that for the data team seems fairly easy)

I haven't fleshed it out, but there are some nuances here about what is "invalid" vs "empty" vs something else. Lots of "-" used in various tables in rules and we'd need to decide what those mean so we don't just crash if it happens...

The second major issue is how to do the lookup in data. We can borrow some inspiration from things like Excel and Google Docs:

'''lookup(X,Y,Z)'''

* X is a table name. This must resolve in the formula system to a String that is a valid table name.
* Y is the lookup value in the table. It must match the format of the column in the table.
* Z is the target column name. This must resolve in the formula system to a String that is a valid table column name in the table named X
*
Thus max load calculation would be something like:
* lookup("Carrying Capacity",roundDown(StrScore),"Capacity")*SizeMult

In a formula - data controlled in a MODIFY.
(

This ignores the over 29 logic, as well as how SizeMult was initialized (presumably from the SIZE: object), but those are not difficult.)

To make the Dice Step example work, we would need something to find the correct column from the offset:
* STARTTABLE:Step Column,
* Steps,Name
* NUMBER,STRING
* -5,DOWN5
* -4,DOWN4
* ...
* 0,SELF
* 1,UP1
* ...
* ENDTABLE:Step Column,

The query would then look up the correct column name and use that column from Dice Step:

* lookup("Dice Step",BaseDamage,lookup("Step Column",CurrentSize-BaseSize,"Name"))

---

There are probably some nuances around things like range lookup (having it correctly deal with an input like 4.5 so the rounddown isn't necessary), but that is easy mechanics as part of the lookup function.

---

One neat item would be that we could alter the query above to extract the table name into the Global Modifier file:
* MODIFY:DiceStepTable|SET|"Dice Step"
* lookup(DiceStepTable,BaseDamage,lookup("Step Column",CurrentSize-BaseSize,"Name"))

Now, if someone needs different dice steps for some reason... they can override the DiceStepTable variable and it will look up in a different table... so expansions could truly be expansions and not have to reach back into core PCC files in order to change key behaviors.

Another neat item is identical cast/known tables could be shared - the numbers would only need to be typed in once... :) ... since they are external to the Class file at that point... or if a subclass alters the default, just create a new table rather than having to BONUS/MODIFY all the numbers with adding and subtracting...

SIDE COMMENT: This was regarding tables with no limits...

* [7:45 PM] Tom Parker: so the min one is fairly easy
* [7:45 PM] Tom Parker: if STR < 0, result is zero
* [7:45 PM] Tom Parker: that can be easily done with a MODIFY SET with a higher priority
* [7:45 PM] Tom Parker: the max one is trickier, but basically you can do something like:
* [7:46 PM] Tom Parker: mult = roundup ( (basestr - 29) % 10)
* [7:46 PM] Tom Parker: lookup then uses -> basestr - (mult * 10)

Dynamic Scopes

2023-06-22T22:24:25Z

LegacyKing: Created page with "On Vision (and movement for that matter) Since originally designing the variable system, I have long considered vision to be just another variable, with "vision" actually be..."

On Vision (and movement for that matter)

Since originally designing the variable system, I have long considered vision to be just another variable, with "vision" actually being a namespace. I have shown examples of such, with VISION=Darkvision as a namespace and variable. This has long been an interest to clean up because Vision is actually a rather weird object within PCGen. It's halfway to things like Template and Skill, but leaves a lot of its code unused. So it's a bit wasteful, but there is a recognition that it needs to have *some* level of "power".

That being said, my desire for a separate namespace has been built upon an assumption that I would eventually build a method of exposing all varibles of a certain namespace (to allow an output sheet to increment across all of the forms of vision). We didn't cover that in the data meeting simply because we ran out of time (after running for 3 hours!?!)

Unfortunately, using a mere variable this runs into two challenges.

The first is that there is data that "turns on and off" the vision based on the variables. This hadn't really worried me - doing a bit of "pushing" on the data team to find constructs that work in the new system is good, and if it's really a problem, we can figure something out once I understand the exact rules construct that doesn't seem to work easily.

However, in planning conversion there is an issue when looking at one of the types of vision:
Low-light Vision

This is a problem (and the second challenge). Obviously "-" is a prohibited character in a variable name. So is the space. So we would have to have LowLightVision as the variable and then figure out a way for that to get "Low-Light Vision" onto the Output Sheet. Preferably without hardcoding awareness of Low-Light vision into the output sheet. Could it be done? Yes. Does it make a lot of sense to introduce LowLightVision (no minue, no space) as another String to be dealt with? No.

Reality is this: We have a "string name" (Low-Light Vision) and a numeric Range (60). This fits better with the model of certain types of Vision also not having a range (but being present).

Trying to extract and carry together both a name and a number in a single variable is a bit crazy. I could easily define a new format, but then that format suffers from the same conversion issues I challenged Mark on with respect to OrderedPair a while ago. It's worse, actually. And I'm not sure it even solves the "how to increment across all variables of a type" problem, which is code I haven't written.

What we really need is the ability to define a "scope" on the fly, which creates a basically hollow, simple object. So the scope is "VISION", and we can then instantiate "Low-Light Vision" and give it a variable "Range":
* DYNAMICSCOPE:VISION
* VISION:Low-Light Vision
* LOCAL:VISION|NUMBER|Range

This can then be modified as:
* MODIFYOTHER:VISION|Low-Light Vision|Range|SET|60

Since Vision is then an object that is in our "object library" (ReferenceContext to the code folks), we can pull the entire list from there (that code has long been written). We can then expose the dynamic types in its own subvariable, and we then have a pretty easy way to increment across all vision objects:
* <#list ${pc.dynamic.vision} as vision>
* ${vision.name} ${vision.val.number.range}
* </#list>

(this ignores converting 60 to local units and all that, but you get the idea)

So the proposal is this:
1)

'''DYNAMICSCOPE:''' becomes a new data control variable.

Like other LST tokens, this is case insensitive, but usage in later tokens is always capitalized, so I suspect the data standard should be all CAPS.
Any argument to that then becomes a legal "subtoken" in FILE:

2)

'''DYNAMIC:''' becomes a new token legal in PCC files. It's format is:

'''DYNAMIC:x'''
* x is the file just as in tokens like DEITY or DOMAIN
* INCLUDE/EXCLUDE on the line are are legal.
* The prefix MUST appear on the line, e.g.:
* VISION:Darkvision
* VISION:Low-Light Vision

3)

A Dynamic can not contain any information (no tokens). It is NOT a full CDOMObject.

4)

For Variable Definition and usage in MODIFYOTHER, the appropriate argument "x" matches the DYNAMICSCOPE (e.g. VISION would sensibly be "x" below)

* LOCAL:x|VAR|Range
* MODIFYOTHER:x|Low-Light Vision|SET|Range|60

5)

We introduce a new token usable in LST files:
* '''GRANT:x|y'''
* x is a DYNAMICSCOPE
* y is the name of the dynamic object.

6)

A Dynamic object MUST be granted in order to have its local variables modified or to have its modifiers have an impact (just like any other object)

Conversion

2023-06-22T22:20:55Z

LegacyKing: Created page with "${pc.val.x} (again, where the "x" is the new variable now holding new FACE). 2 new tokens for the Data Control file: * FUNCTION:x * VALUE:x '''FUNCTION:x''' * Must appear..."

${pc.val.x}

(again, where the "x" is the new variable now holding new FACE).

2 new tokens for the Data Control file:
* FUNCTION:x
* VALUE:x

'''FUNCTION:x'''
* Must appear as the first item on the line in a data control file
* Takes one argument, a function name
* Must be a "legal" function name, meaning:
* - starts with a letter, e.g. A-Z, additional legal characters are 0-9
* and _ (none of those as the first character)
* - No spaces, no other special characters.
* - Are case insensitive (as many other things in LST files)
This defines the function name as it will be used in a formula in the
LST data files.

If a FUNCTION appears more than once, the other characteristics (currently VALUE) must be identical.
===
'''VALUE:x'''
Must appear as an additional token on the line of a FUNCTION: in the data control file

The provided value must be a value formula. This means it must have valid variable names, valid function names, matching parenthesis, etc. etc.

In addition to all of the build-in functions (e.g. if, ceil, round), two additional items can be used:

(1) the arg(n) function. The arg function is a "local" function to the VALUE: part of a FUNCTION (it can not generally be used in LST files).

The arg function takes one argument. It MUST be a Integer >= 0.

(2) Any previously defined FUNCTION. This MUST appear in the file before the current Function or in a file processed before the current file.

Meaning:
* FUNCTION:d20mod <> VALUE:floor((arg(0)-10)/2)
* FUNCTION:embed <> VALUE:d20mod(arg(0)*4
is legal, while:
* FUNCTION:embed <> VALUE:d20mod(arg(0)*4
* FUNCTION:d20mod <> VALUE:floor((arg(0)-10)/2)

...is not legal (since d20mod does not yet exist when embed is encountered)

When a function is used in LST data, it is called by the name provided
in the FUNCTION token. It requires a certain number of arguments. This
exactly matches the integer one greater than the highest number of the
arg(n) function provided in the VALUE part of a FUNCTION
(In computer science terms, the arg(n) function is zero-indexed)

The provided arguments can be any legal formula, so:
* d20Mod(INT)
* d20Mod(INT+4)
are both perfectly legal.

===
For example:
* FUNCTION:d20Mod <> VALUE:floor((arg(0)-10)/2)
* Note the arg(n) function here uses ZERO, not ONE.
This would then be used in LST data as:

d20Mod(n)

It will catch both d20Mod() and d20Mod(14,5) as errors (too few or too many args). It would also catch: d20Mod("mystring") as an error (wrong format - requires a Number, found a String).

The n is substituted where "arg(0)" appears in the "VALUE"... so a
statmod would be as easy as:

d20Mod(INT)

or some such...

Direct values can also be used, e.g. d20Mod(10) would return 0.

===
Some other notes:
* Note that the function actually has to be *used* (not just defined) for
* the errors to be caught (since it can't guess at overall context)
* An embedding example can be found here:
* https://groups.yahoo.com/neo/groups/pcgen_experimental/conversations/messages/19549

INFO/INFOVARS

2023-06-22T22:16:40Z

LegacyKing: Created page with "I wanted to start a development discussion on how we process items for output since we seem to have different methods... like other things it would be nice to get one powerful..."

I wanted to start a development discussion on how we process items for output since we seem to have different methods... like other things it would be nice to get one powerful, consistent method.

As always for architecture items on _dev:
- Only high-level syntax discussion (it's usually none, but this one really does have a syntax impact)
- Read for intent, this is not the time to nitpick token names
- There is no schedule, and no plan to define one
- Be specific with examples of where this wouldn't meet needs - with specific examples of objects/rules... no chasing phantoms.

Assumptions:
- For any given identification of output, we only need one thing
- The output is unconditional

Clarification of assumptions:
"One thing" is akin to TargetArea on a spell today, which is 1 thing (the token overwrites if provided again). This is different than the current "DESC" or "Components" on a spell which are "append", and thus can be multiple things. These multiple items use .CLEAR/.CLEARALL to clear the list. If multiple outputs with the same identification are required, I'd like to see the rules structure/output structure that requires such behavior.

Unconditional is relative... since this should be assumed to arrive after the new variable system, if the data/OS wants to gate output on a FLAG in the new variable system, more power to them... so a trailing PRExxx is unnecessary to get full function.

===

I'll skip over the methods we have of doing substitution and get into my thought: What if we were to allow definition of a MessageFormat?

INFO:InfoName|<message format>

Note that MessageFormat allows items that include | et al, so we can't tack on any extra items in that token. No PRE, no variables, etc.

That would require:

INFOVARS:InfoName|x|x

For the variables (x would be something valid in the new formula system)

InfoName doesn't need to be pre-defined, just needs to be recognized that it overwrites if it matches a previously defined item on that object.

Not 100% certain if we can catch if there is an INFO without the appropriate count of INFOVARS, though it looks like getFormats() can effectively help accomplish such a check at the end of LST load.

Seems this can replace OutputName, Desc, Aspect (for just about everything except 4E where PRExxx may be necessary? - not sure since I never played 4E), many of the spell tokens (e.g. TargetArea), and some others.

Sensible at all?

Any way to do it with another String formatting system that would allow it in one token like DESC is today? Is that tradeoff worth it vs being able to leverage java.text.MessageFormat (built into Java)

Note: One of my decision criteria here is avoiding indirection. I've long held that data like this:

NEWTOKEN:InfoName|message_ab_foo_1|x|y|z
...where message_ab_foo_1 has to be in a language file... is putting a huge burden on data because it forces indirection due to localization. I neither want to develop nor debug data like that, so really have no interest in writing tokens that behave like that....

Having said that, this format does lend itself to localization, as the MessageFormat is effectively in the one token (INFO) and the specific information is named (The InfoName would be Description, OutputName, whatever).

You can therefore "address" that MessageFormat... so imagine a separate file doing:
ABILITY:FEAT|Dodge|Description|<other language version of message format>

This allows the code to do the swap of the message format without making the original data indirect.

Thoughts?

TP.

This is a formalization of the proposal earlier put onto _dev to address a replacement for DESC. The _dev discussion can be found here: https://groups.yahoo.com/neo/groups/pcgen_developers/conversations/topics/4412

Note that the dev discussion contains some examples I have not repeated here.

This is a proposed replacement for DESC, ASPECT, BENEFIT, and likely a number of other tokens. Since those tokens will be replaced *over time* (this is not a deprecation of these older tokens), the full list is not currently defined (We will discover them as we go and I'm sure the data team will add to the list as they discover and use the flexibility provided here)

Specifically to these tokens, there are four main reasons to replace them:

First, they allow Prerequisites, which is a non-trivial endeavor in determining what to do in any given situation. This can be confusing to a reader of the data (in trying to hold the PRExxx in their head) as well as uses CPU time for the code to determine at any given time what DESCs are "on" or "off".

Second, they allow multiple tokens, so we have to keep track of a list, we have to allow clearing of that list, we have to do extra things because there can be more than one. In the case of Aspect we actually have to do things that violate the isolation assumptions that support the use of an LST editor (so writing editor code for Aspect would be tough to get correct). Reducing this to a one-to-one relationship helps simplify a number of things in the code (and I'd argue the data as well).

Third, it does not play well with any form of localization because the substitutions are hardcoded and the variables and strings are all mixed together.

Lastly, it is hardcoded to the existing formula system to do replacement. Trying to mix the old and new formula systems is pretty much a disaster, so DESC (and other tokens that do similar replacement) need to be swapped out in the conversion to the new formula system.

This is a proposal for a replacement for DESC and the other descriptive tokens. There are two key Assumptions in this proposal:
- For any given identification of output, we only need one thing
- The output is unconditional

Clarification of assumptions:
"One thing" is akin to TargetArea on a spell today, which is 1 thing (the token overwrites if provided again). This is different than the current "DESC" or "Components" on a spell which are "append", and thus can be multiple things. These multiple items use .CLEAR/.CLEARALL to clear the list.

If multiple outputs with the same identification are required, I'd like to see the rules structure/output structure that requires such behavior. (This has been posted to _dev and bumped, and so far everything that has come back doesn't require multiple items, just a mental model change in how to make the data)

'''The proposal involves two LST tokens:'''

* INFO:x|y
* x is an "info name". This is data defined
* y is the message format. It matches the format required by java.text.MessageFormat, which can be found, among many other places, here: http://docs.oracle.com/javase/7/docs/api/java/text/MessageFormat.html#getFormatsByArgumentIndex%28%29
* This token overwrites (if the "info name" matches)
 

* INFOVARS:x|y=z|y=z
* x is an "info name". This is data defined
* y is a scope from the new Formula System (e.g. AREA). The y= is optional if y is "VAR" (the default numeric variable scope)
* z is a variable from the new Formula System (e.g. Face)
* This token overwrites (if the "info name" matches)

'''Some notes:'''
* - The "info name" is dynamic. It is NOT under the control of something like the data control file (it is NOT like FACT names or Variables). It is more similar to today's Aspect names.
* - There are rules for the "info name" regarding use in INFO and INFOVARS. Specifically:
* --- If an info name is used in INFOVARS but never in INFO on that object, it is an LST load error
* --- If an info name is used in INFO and the Message Format requires variables and no INFOVARS is provided, it is an LST load error
* --- If an info name is used in INFO and the Message Format requires N variables and the number provided to INFOVARS does not match N, then it is an LST load error.
* ---The "info name" is only so flexible, but the code will not restrict it at this time. I would advise the data standard be all letters and numbers (no spaces, no special characters), and if we can get to a standard the data team wants strongly enforced, that can be done.

Output in the new Freemarker system is implied. Any INFO token will be available under *.info . For example:
* Race LST file
* Monkey <> INFO:Wildness|Monkeys are usually found in the wild
* can be accessed under the following:
* pc.race.info.wildness

Tom's Discussions with Andrew aka LegacyKing

2023-06-22T22:12:28Z

LegacyKing:

* [[INFO/INFOVARS]]
* [[Conversion]]
* [[Dynamic Scopes]]
* [[Lookup Table]]

Tom's Discussions with Andrew aka LegacyKing

2023-06-22T22:11:54Z

LegacyKing: Created page with " INFO/INFOVARS Conversion Dynamic Scopes Lookup Table"

[[INFO/INFOVARS]]
[[Conversion]]
[[Dynamic Scopes]]
[[Lookup Table]]

Architecture

2023-06-22T22:10:42Z

LegacyKing: /* Future */

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

Welcome to the Wiki section for the Architecture team!

This section of our wiki will explain the different portions of our code base, the current work underway to improve different sections for better performance and flexibility.

=Resources=

Before reading about the details of the PCGen architecture, it is likely helpful to understand our key [[Design Concepts for PCGen]] and [[Architecture Document Conventions]]

=Index of Architecture Documents=

There is an [[Index to Architecture Documents]] that provides a complete list and is in the recommended reading order for those who wish to read the complete set of relevant documentation.

=PCGen Subsystems=

This section lays out the primary sub-systems within PCGen

==Startup System==

The [[Startup System]] is responsible for the activities required to load PCGen to the state where a user can select an option from the Load UI. This includes:
* Discovery and loading of Plugins (the plugin.* packages)
* Loading the Game Modes (stored in the system directory)
* Discovering and loading the PCC files (from the data directory)
* Loading the Load UI (part of pcgen.gui2.*)

==Load UI==

The Load UI is responsible for presenting the user with the options of game systems and components available to be loaded. The LoadUI triggers a call to the Rules Persistence system when the user requests for specific data to be loaded, and to the Character Persistence system when the user requests for a Player Character to be loaded...

==Rules Persistence System==

The [[Rules Persistence System]] is one of the major components of PCGen. It is responsible for loading game system and component data from the persistence data file format and (in most cases) saving it back into that data file format. It is aware of the internal storage of information within PCGen only to the point it is required to store information in the Rules Data Store for use by the core of PCGen. The Rules Persistence System is not capable of interpreting much in the way of behavior of the values it is storing (strictly it will know the persistent text format, but doesn't understand what REACH actually means, only that it contains a number to be loaded into a specific location in the Rules Data Store).

We have a number of files in both the system (game mode) and data (effectively book content) directories that represent the data. Specific file "Loaders" load each of the different formats of file that we have, breaking it into lines.

These lines are then split up into the first token (indicating what the line means) and the other tokens. Tokens are separated by one or more tab characters.

Given the combination of Loader (file format) and Token, we can look up the appropriate plugin to process that specific token. This is called to parse the value of the token. This parse method is responsible for loading the information about the token into the Rules Data Store (generally into the object being loaded, but this is not universally true). Any failure means the entire contents of the token will be ignored (the contents of the token are a "transaction" in the sense that it fully succeeds or fully fails).

Those tokens may encounter various items including references to other objects, which we capture as [[CDOM References Concept Document|CDOMReferences]]. In addition, there may be groups of objects referred to as well, so you may want to learn about [[Referring to Groups in LST Data]].

This also includes the [[Load Commit Subsystem]]. Additional detail is provided in [[Full Load Order Detail]].

==Rules Data Store==

The [[Rules Data Store]] is the internal data structure used to store the game system and component information.

As a "Data Store", it is very much akin to a complicated database (it could be converted into an actual database with some effort). The Rules Data Store is not designed to have methods that interpret the contents of the Rules Data Store, nor is the Rules Data Store capable of storing the information it contains into a persistent state. The conversion to and from a persistent state is owned by the [[Rules Persistence System]].

Once items are in the [[Rules Data Store]], they must be retrieved by their Identity. For more information, see [[Identifying Objects]]

==Player Character UI==

The Player Character UI is responsible for presenting the user with the contents of the PC, including all of the PC's characteristics. Requests to modify a PC are sent to back to the core to be processed. Much of this is currently framed through Facade objects which attempt to isolate the UI from the core.

Note that some of the items on a PC can be conditional, so it's valuable to understand [[Prerequisites and Requirements]] to understand what can be chosen and how those items will be applied to a PC.

==Processing a PC==

When an item is added to a PC, those behaviors need to be processed by [[Calculating Items on the PC]]. To understand that in more detail, you probably want to learn about the [[Formula Systems]], including JEP and the new formula system.

=Other - to Be Edited=

** Character Persistence: The Character Persistence system is responsible for loading and saving PCs into the specified file format. The Character Persistence system is also responsible for creating and initializing a new Player Character.
** Character Output: The Character Output system is responsible for resolving the active objects on a PC, searching those objects to find specific information, and preparing that information for consumption by any of the systems that desire PC information.
** Event Controller: The Event Controller acts as a hub to communicate events (typically triggered by changes to a PC) to the UI and to any loaded Plugins.
** Character Data Store: The Character Data Store is the internal data structure used to store the PC.

* [[Explanation of the Code Base|Code Base]] - Key Concepts
** [[Key Terms]]
** [[Tags and Tokens]]
** [[FreeMarker Output]]
** [[CDOM References Concept Document]]
* [[CDOM Primitive Choice Set Concept Document]]
** [[CDOM Choice Actors Concept Document]]

* Walkthroughs
** [[User Selection Walkthrough]]

* Rules Data Store Concepts
** [[Ability Category|Ability Categories]]

=Open Sub Projects=

==Current==

* [[Formula System Conversion]]
* [[FreeMarker Facet Output]]
* [[Incompatible Change List v6]]
* [[Current Architecture Projects]] (personal scratchpad)
* [[LST Token Information]] (scratchpad - relates to facet design and abstracting behaviors)
* [[BONUS Tag conversion list]]
* [[SELECTION - A CHOOSE Replacement]]

==Future==

* [[Internationalization]]
* [[Data Cleanup Projects]]
* [[PREREQ Cleanup]]
* [[PCG Round Robin Work]] (Tom's scratchpad)
* [[Bonus Subsystem Thoughts]]
* [[Bonus Subsystem Design]]
* [[Tom's Discussions with Andrew aka LegacyKing]]

=Past Projects=

* [[FACT Token]], [[FACTSET Token]]
* [[Architecture Update 1Q2013]]
* [[Subsystem Isolation]] (out of date?)
* [[PObject - The Refactoring]] (effectively completed for most items - CDOMObject)
* [[Rebuild of the Token/Loader System]] (effectively completed for most items)
* [[Architecture Changes 5.17]] (completed as much as would be in 5.17)
* [[Things to Test]] (now uses TEST- trackers)

==Not used==

Things not really part of the current architecture, but for context
* [[Behavior Questions]]
* [[CDOM]]
* [[Tom's Arch "TO DO" List]]
* [[Character Data Store]]

=Active Team Members=

===[[Explanation of Teams#Silverback|Silverback]]===
* [[Tom Parker]]

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

===[[Explanation of Teams#Lemur|Lemur]]===
* [[Connor Petty]]
* [[James Dempsey]]

=Inactive Team Members=

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

Release Instructions

2018-11-12T23:54:22Z

LegacyKing: /* Create Release Notes */

{| align="right"
| __TOC__
|}

==Introduction==

Here are the steps to follow when making a release of PCGen. If it is your first time, please check the prereqs section at the bottom of this page.

==Prerequisites==
The first time you run a release you will have to make sure you have the following tools available:
===Release Notes===
* Text editor
* Web browser
* Perl interpreter
* Perl modules: readonly (installed on Windows via ActivePerl's Perl Package Manager)

===Release===
* Java SDK 1.8 (the one that includes the javac compiler) --FOR PCGEN 6.07.x
* Gradle 1.x
* git
* Perl interpreter
* [http://nsis.sourceforge.net/Download NSIS]

===Outstanding Issues===
You need to check JIRA for any outstanding issues to ensure the release meets our QA std.

* Alpha releases require no Blockers, allow Critical only with Code lead exception
* Beta releases require no Blockers or Criticals
* RCs/final releases require no Blockers, Criticals, or Majors

==Create Release Notes==

# Update your local copy of pcgen from github
# Copy the previous set of release notes to pcgen-release-notes-nnn.html where nnn is the version number.
# Do a global replace of the old version number to the new version number, both as n.nn.n and nnnn
# Open Jira and for each project open the release notes for the version.
# Copy the html to the changelog section, changing h2 tags to h3.
# Update the What's New section with any high profile changes.
# Update the Thanks section with the list of people who committed during the cycle. The search filter "is:pr is:closed is:merged updated:>2015-02-09" is useful for triming the list of pull request to those included in the release.
# Commit the new release notes and notify pcgen_bod so they can review it.
# Notify pcgen dev and experimental lists of upcoming release, asking for autobuilds to be tested. Best to give 24 hours notice.

== Release Notes Placeholder ==
* https://pcgenorg.atlassian.net/projects/CODE?orderField=RANK&selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased

==The Build==
# Using a clean directory with no changes to the pcgen files
# '''git pull master''' the PCGen repository (5 mins)
# Release manager edits '''pcgen/code/src/java/pcgen/resources/prop/PCGenProp.properties''' to set the release date, version number, contributors, etc. and commit the result (5 mins)
# If switching to or from RC mode, edit '''gradle.properties''' and adjust the version number to be in the correct format. e.g. '''6.04.00 RC1''' or '''6.04.00'''
# Execute '''gradle prepareRelease slowtest''' OR IF USING WINDOWS ('''gradle prepareRelease slowtest --project-cache-dir c:\gradle\cache''') in the pcgen directory and verify there are no failing Junit test. Also check if there are any "Unknown publisher" messages. If so you need to add new entries for the listed publishers to the '''gendatalist.pl''' script. (20 mins)
# Check Jira for any closed requests missing from the release notes. Steps 4 and 6 of 'Create Release Notes' section above can be used to assist here. (10 mins)
# Update the '''readme.md''' file with the what's new section of the release notes.
# Smoke test the newly built pcgen full zip or exe. (30 mins)
# Create a folder for the release under the [https://sourceforge.net/projects/pcgen/files/ File Manager]
# Upload the release notes using the File Manager to the release folder
# Run '''gradle pcgenRelease''' OR IF USING WINDOWS ('''gradle pcgenRelease --project-cache-dir c:\gradle\cache''') (which updates the gradlefiles and tags the SVN repository). (2 mins)
# Upload the release files to SourceForge. The quickest way is uploading via the web, the same way you uploaded the release notes etc. (10 mins)
# Update '''Readme.MD''' with the SHA256 checksums from target/SHA256-digests.txt. Upload the revised file and check-in. (5 mins)
# Notify PCGen_bod of the new release. (5 mins)
# PR Monkeys create a news item for the new release
# PR Monkeys send announcement to all pcgen mailing list for the new release

==Update JIRA==

For each of the projects, mark the version you are working on as released and create the next version if it doesn't already exist. When marking a version as released, please make sure the released date is set to today.

* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/CODE/versions Code Versions]
* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/DATA/versions Data Versions]
* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/DOCS/versions Documentation Versions]
* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/NEWSOURCE/versions New Source Versions]
* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/NEWTAG/versions New Tag Versions]
* [https://pcgenorg.atlassian.net/plugins/servlet/project-config/OS/versions Output Sheets Versions]

==Mac Installer==

See [http://pcgen.svn.sourceforge.net/viewvc/pcgen/Trunk/pcgen/installers/mac-installer/instructions.html Instructions]

==IMPORTANT==
For Production Cycle Autobuilds the file '''code\gradle\autobuild.gradle''' lines 16-18 needs to be set to:
destAutobuildDir = '/home/pcgen1/public_html/autobuilds-prod/'
} else {
destAutobuildDir = "${buildDir}/autobuilds-prod/"

==Signing Files with PGP==
'''Historical only''' We used to use the [[http://www.gnupg.org/ GnuPG for Windows]] to generate the signatures. You will need the private key, either your own, or the PCGen one (contact the PCGen BOD). Once GnuPG is installed and knows about the key you wish to use, it is just a matter fo right clicking on the files to be signed (multi-select is fine) and selecting GPGee > Sign and then making sure the PCGen key is selected, hitting OK and entering the passphrase for the key. This creates an .asc signature file for each selected file.

==Troubleshooting==
Yes, even the best installs of all the program amount to nothing if there is a hitch. These are basic notes from the current issues cropping up and resolutions. These notes are not prettified yet. The idea being we will get a full set of troubleshooting tips and tricks here in the near future.

Check your versions.
JDK1.8 is required with JAVA_HOME variable (see below)
My Computer > System > Advanced Settings:
For JAVA_HOME make sure it's a set System Variable and make sure it's using the correct path to your current installation base folder

===OLD===
SVN must be a true .exe install, TortoiseSVN will not meet this requirement
SVN exe can be found here [[http://subversion.tigris.org/files/documents/15/46531/Setup-Subversion-1.6.5.msi SVN]]

Meeting 2018 11 10

2018-11-10T15:14:20Z

LegacyKing: Created page with "==Attendance== * Chair/Content - Andrew * Code/Architecture - Tom * PR - Paul * Data 2nd - Gwen * OS 2nd - Stefan * '''Volunteers/Lurkers''' * David * Avilay * Brad G. * Jaco..."

==Attendance==
* Chair/Content - Andrew
* Code/Architecture - Tom
* PR - Paul
* Data 2nd - Gwen
* OS 2nd - Stefan

* '''Volunteers/Lurkers'''
* David
* Avilay
* Brad G.
* Jacob
* BT

==Summary==
* Production Release planned for December 1st
* Revised Documentation Hosting
* Revise Wiki for Code Entry into the new system
* Finish License Reviews of outstanding new sources

===Raw Log===
* LegacyKing Today at 6:02 AM
* Welcome everyone to our Public Board Meeting on November 11th 6am (-0800 UTC)
* AGENDA for November 10 - 0600 PST:
*
* 1) State of the Program and release update plans
*
* 2) Reports from Content, Code and PR
*
* 3) Additional Business (If any)
*
* 4) Public Q&A
* For those new to these meetings, the rules are simple. Please allow the main speaker to finish what they are discussing and hold questions till the end. We do reserve time at the end for Public Questions and Answers.
* Roll Call real quick - Andrew Maitland (aka LegacyKing) acting Chair, and Content Silverback
* Bryan McRoberts Today at 6:06 AM
* Bryan McRoberts - Benevolent Dictator
* Nylanfs (UTC-5) Today at 6:06 AM
* Paul Grosse (AKA Nylanfs) - PR Silverbck, Public Face :smiley:
* thpr Today at 6:06 AM
* Tom Parker (thpr) - Code/Architecture lead
* Gwen T. Today at 6:06 AM
* Gwen T. - Data Second
* bigrin42 Today at 6:07 AM
* Brad Grinstead (AKA bigrin42) - code monkey and resident lurker
* LegacyKing Today at 6:07 AM
* Stefan Radermacher aka Zaister - OS 2nd (Looks like he lost connection)
* Zaister Today at 6:08 AM
* Yeah it’s a bit flaky,I’m i on mobile
* LegacyKing Today at 6:08 AM
* No worries man. We've all been there.
* Teladorer Today at 6:08 AM
* Avilay - professional lurker, help with design
* Jacob Today at 6:09 AM
* Jacob R, code monkey, also on mobile
* BT Today at 6:09 AM
* BT - absentee data and support
* LegacyKing Today at 6:09 AM
* Okay, thanks all for checking in
* Agenda item 1) State of the Program and release update plans
* This one might need more than myself to chime in - Personally, I've lost the ability to run PCGen developer builds, but when it was working things were very stable and we're on track with the formula system replacement; main focus is correcting and getting the data tables and the lookup working. Release Schedule is off course currently from the Roadmap we put out earlier this year.
* We're still focused on JAVA and we've been updating things to work with the LTS release of Java 11.
* @thpr or @Bryan McRoberts any comments about the Program?
* or schedule?
* thpr Today at 6:14 AM
* I literally just submitted the last PR to fully bring us to Java 11
* 💯
* 1
* 💛
* 1
* 👌
* 1
* Nylanfs (UTC-5) Today at 6:15 AM
* There have been more and more people going straight for the Stable build and we keep refering them to the dev because of the age. Getting a new stable out would be good.
* Bryan McRoberts Today at 6:16 AM
* I am able to get PCGen to build in java 11 on my machine - what problems are you having with the developer builds?
* LegacyKing Today at 6:16 AM
* @Bryan McRoberts let's discuss after the meeting. It's complicated and would take too much time from the meeting.
* thpr Today at 6:17 AM
* Good, but let's get you back up & running
* Bryan McRoberts Today at 6:17 AM
* we can take the developer issue offline, but let's get a stable build out asap because, as Paul mentioned, the age of the last one.
* LegacyKing Today at 6:17 AM
* Oh, I agree, but after the meeting. This would be a Rabbit Hole and derail the meeting. :wink:
* thpr Today at 6:18 AM
* On the tables/lookup, I saw that you are still encountering the same issue from earlier in the week, I'm looking into that
* LegacyKing Today at 6:18 AM
* Tom - I believe that is related to my above problem, I'm not getting a build with your PRs
* Again, another Rabbit Hole. Shall we plan for a fairly aggressive Stable release by December?
* Content has been ready to release and has mainly been doing bug squashes, so we are ready to switch to Beta if Code is good to go
* Nylanfs (UTC-5) Today at 6:21 AM
* I'm okay with december(edited)
* Bryan McRoberts Today at 6:22 AM
* I think a stable by December would be excellent.
* The travis builds work, it works on my machine, so unless there are mission-critical bugs, the sooner we release the better.
* LegacyKing Today at 6:23 AM
* If we're good, and we can fix my build capability today, we can have a beta release out later today, another next week (17th) RC1 on the 24th, and a Production by the 1st.
* thpr Today at 6:23 AM
* I think that's reasonable - I have one or two nice to haves, but aren't strictly necessary for a stable
* Bryan McRoberts Today at 6:23 AM
* excellent. let's fix your build issues after the meeting.
* 👌
* 1
* LegacyKing Today at 6:24 AM
* Okay, let's Segway into Agenda item 2) Reports from Content, Code and PR
* Content has been pumping out newsources, bug fixes, and features. We're good to go for a release as planned.
* 😃
* 1
* Not much else to say other than I'll be HAPPY to work on the new system and clear out ancient bug reports.(edited)
* Gwen T. Today at 6:26 AM
* I need to clean up Adventurer's Guide a bit before it gets finalized, and I am moving apace on Horror Adventures.
* Teladorer Today at 6:26 AM
* what are the new sources to be including in new stable?
* LegacyKing Today at 6:27 AM
* Whatever ones the volunteers say are ready for review before we switch to Beta
* And pass License and Data review
* Nylanfs (UTC-5) Today at 6:27 AM
* I know there are three or four ready for me to do a license review
* Teladorer Today at 6:27 AM
* oki. :smiley:
* Bryan McRoberts Today at 6:28 AM
* A list of new sources will be part of the release message, right? Lots of people will want to be able to see a list.
* LegacyKing Today at 6:28 AM
* And the ones that don't make the deadline can be add-on downloads.
* 👌
* 1
* Bryan - Yes! :smiley:(edited)
* 💯
* 1
* Any other questions for Content?
* @Nylanfs (UTC-5) Anything to report from the PR team?
* Nylanfs (UTC-5) Today at 6:30 AM
* It looks like using Slack and Discord have been a success. :smiley:
* I started a groups.io to replace the Yahoo groups if we want to switch.
* Bryan McRoberts Today at 6:31 AM
* I'm still sore over switching from egroups to yahoo groups.... :smile:
* Nylanfs (UTC-5) Today at 6:32 AM
* Both Andrew and I are liking how that works, it's exactly what we were wanting when we originally started looking for other options when Verizon bought Yahoo
* 👌🏻
* 1
* Mailing list, replies via email, web interface etc.
* LegacyKing Today at 6:32 AM
* It can replace the Forums we host!
* Nylanfs (UTC-5) Today at 6:33 AM
* I have started a Patreon page for the project but haven't launched it yet, needs more polishing.
* There's some sources that need license review which should be able to get done tomorrow
* I think that's it from PR
* Any questions?
* LegacyKing Today at 6:34 AM
* Thanks Paul. He really took ownership of that groups.io I set up. Next thing I knew, he'd redecorated the place and mimic'd the Y! groups. :stuck_out_tongue:
* Bryan McRoberts Today at 6:35 AM
* Awesome!
* LegacyKing Today at 6:35 AM
* Nothing but compliments from those using on how easy it is. pcgen.groups.io if anyone wants to check it out.
* Nylanfs (UTC-5) Today at 6:36 AM
* We need to make an system announcement on the Yahoo groups and let people know about the switch so they can adjust their membership if they don't want to transition
* LegacyKing Today at 6:36 AM
* Yeah.
* Nylanfs (UTC-5) Today at 6:36 AM
* https://pcgen.groups.io/g/main
* main groups.io Group
* PCGen.org - This is a mailing list group replacement for the old Yahoo Groups
*
* LegacyKing Today at 6:37 AM
* Okay, @thpr what have you got for us from Architecture/Code?
* thpr Today at 6:38 AM
* Working to review the work / local branches I have on the formula system, make sure they are updated, etc. and evaluating urgency to be in the next release
* Mostly through that now, although there are a few that will probably require a full redo, since a rebase has a huge clash with some formatting changes done on the code
* Then mostly the testing I'm working with you on... I don't have major items I know need to be done...
* Bryan McRoberts Today at 6:41 AM
* Nice
* thpr Today at 6:41 AM
* As a broader scope, I'm unsure if the docs done earlier this year are of use in folks understanding how the system is structured
* So if anyone is coming up to speed on code or things of that nature, comments about the content on the wiki are welcomed
* PCGen is just inherently challenging since it's not just a push/get from a UI/database structure, there is a huge "solving engine" in the background that can make it a bit more challenging to get into
* Bryan McRoberts Today at 6:43 AM
* Very true!
* thpr Today at 6:43 AM
* Hence why we need a bit more on the doc front to be able to get folks into it
* BT Today at 6:43 AM
* Note: http://wiki.pcgen.org/PCGen_Documentation has a number of links that go nowhere
* PCGen Documentation
* LegacyKing Today at 6:44 AM
* @Jacob is our newest Code monkey, and probably a good barometer on project complexity and documentation.
* thpr Today at 6:44 AM
* So http://wiki.pcgen.org/Index_to_Architecture_Documents is the starting point for the docs I'm referring to
* Index to Architecture Documents
* We will look at what @BT raised though, as we should fix that as well
* Teladorer Today at 6:44 AM
* i say discord is a success. :smiley:
* Jacob Today at 6:45 AM
* I will be taking a look later today / tomorrow, and try to take notes :)
* Nylanfs (UTC-5) Today at 6:45 AM
* A Brad Fonseca is looking for programmers on G+, I pointed him in the wiki direction and Tom's way if he finds any
* thpr Today at 6:45 AM
* That would be great
* Zaister Today at 6:46 AM
* isnt G+ dead?
* Nylanfs (UTC-5) Today at 6:46 AM
* Next year :smiley:
* Zaister Today at 6:46 AM
* ah
* BT Today at 6:47 AM
* Actually the Wiki has a lot of outdated/broken links you might want to check out. This page as well in particular: http://wiki.pcgen.org/Users
* Users
* with yahoo no longer being relevant
* thpr Today at 6:47 AM
* There are a number of ... working projects ... that folks can also take on to help out.
* Meaning there is a set of things to do across a few dozen or more files that doesn't require deep knowledge of how PCGen works, but once complete, will allow us to take out some more complex items in the code and help out clarity
* So if anyone is looking for a project ...
* :wink:
* I think that's it for my report
* LegacyKing Today at 6:49 AM
* Thanks @thpr
* okay, agenda 3) Additional Business (If any)
* I believe it is time we migrated the documentation to not be tied to the releases. Many other projects host their documentation online.
* That's the one thing that always lags behind
* Bryan McRoberts Today at 6:51 AM
* Agreed
* Zaister Today at 6:52 AM
* Yes
* Nylanfs (UTC-5) Today at 6:52 AM
* Lewis Yip had a concept from Hip chat that was very interesting.
* way back when.
* LegacyKing Today at 6:52 AM
* Yes, but he hasn't been active. It was a nice approach.
* Nylanfs (UTC-5) Today at 6:54 AM
* We do need somebody focused to work on the documentation. :smiley:
* LegacyKing Today at 6:54 AM
* @Bryan McRoberts if we choose a wiki/website, will you be able to change the Document load function to search the webpage and not the local pages?
* Or grant Content the ability to control that pointer in case it has to change?
* Maybe a local redirect page or something?
* Bryan McRoberts Today at 6:55 AM
* The preference would have to be able to refer to a website - I don't think that should be hard.
* Teladorer Today at 6:55 AM
* me have to be off now. to a 20 year reunion. pc will remain on
* LegacyKing Today at 6:55 AM
* Okay, cool.
* Last item - 4) Open Forum / Public Q&A - This is where anyone may ask anything of the Board Members
* Zaister Today at 6:56 AM
* I can take a look at the Documentation thing
* Teladorer Today at 6:56 AM
* ps: remember release package should always contain documentation, just in case people end up playing games in cabins in the wilderness
* 👍
* 1
* Jacob Today at 6:57 AM
* What's the idea behind the coming Patreon page? Is there any extra service we can provide to patrons?
* BT Today at 6:57 AM
* if @thpr has an index of those projects mentioned, I have a lot more free time with my new gig and should be able to get my hands dirty again
* Jacob Today at 6:58 AM
* I would also be interested in those projects
* thpr Today at 6:58 AM
* @BT I'll create some pages on the Wiki to describe them
* BT Today at 6:58 AM
* :thumbsup:
* Nylanfs (UTC-5) Today at 6:59 AM
* @Jacob That's one of the reasons why we never launched one before. As a free project what can we offer any of the tiers? :smiley:
* BT Today at 7:01 AM
* custom files would be one option
* Gwen T. Today at 7:01 AM
* Other then their name on a supporters page, not a lot. I wish I could say custom content, but what would happen if they want something that's impossible?
* Nylanfs (UTC-5) Today at 7:01 AM
* There were some mentions of options, but I sure can't find it now. :smiley:
* LegacyKing Today at 7:01 AM
* I have 7am (-0800 UTC) thank you for everyone showing up. Meeting is adjourned! BANGS GAVEL

Meeting Logs

2018-11-10T15:09:53Z

LegacyKing: /* 2018 */

{| align="right"
| __TOC__
|}

This is a new section to hold the Meeting Logs.

=2018=
* [[Meeting 2018 11 10]] "Full Board"
* [[Meeting 2018 08 04]] "Data Team in the house"
* [[Meeting 2018 04 28]] "Board Light Beta"
* [[Meeting 2018 03 31]] "Board Light Beta"
* [[Meeting 2018 02 24]] "Roadmap to Production"
* [[Meeting 2018 01 13]] "Future of PCGen"

=2017=
* [[Meeting 2017 06 17]] "Team Reports"
* [[Meeting 2017 02 25]] "Team Reports"
* [[Meeting 2017 01 21]] "Team Reports"

=2016=
* [[Meeting 2016 11 12]] "Release Discussion 6.07.01, and hold up"
* [[Meeting 2016 10 01]] "Discussion for 7.00"
* [[Meeting 2016 07 02]] "Quorum - 6.06 release and 7.00 roadmap"
* [[Meeting 2016 05 28]] "Informal"
* [[Meeting 2016 02 27]] "Production Release Meeting"

=2015=
* [[Meeting 2015 11 14]] "Informal Monthly Meeting"
* [[Meeting 2015 09 12]] "Monthly Meeting"
* [[Meeting 2015 08 15]] "Monthly Meeting"
* [[Meeting 2015 05 09]] "Monthly Meeting"

* [[Meeting 2015 03 27]] "Team Discussion"
* [[Meeting 2015 02 13]] "TBD"
* [[Meeting 2015 01 30]] "TBD"
* [[Meeting_2015_01_16]] "Informal"
* [[Meeting_2015_01_02]] "Team Discussion"

=2014=
* [[Agenda_Next_Meeting_Deep_Dive]]
* [[Agenda_Next_Meeting]]

* [[Meeting_2014_12_19]] "Deep Dive"
* [[Meeting_2014_12_05]] "Team Discussion"
* [[Meeting_2014_11_21]] "Deep Dive"
* [[Meeting_2014_11_07]] "Team Discussion & Parser Conversation Post Meeting"
* [[Meeting_2014_10_24]] "Deep Dive"
* [[Meeting_2014_10_10]] "Team Discussion"
* [[Meeting_2014_09_26]] "Post Release Meeting & Deep Dive"

* [[Meeting_2014_09_12]] "Release Meeting" RC2 good to Go?
* [[Meeting_2014_08_29]] "Release Meeting" RC1 good?
* [[Meeting_2014_08_15]] "Team Discussion Meeting"
* [[Meeting_2014_07_18]] "Team Discussion Meeting"
* [[Meeting_2014_07_11]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement Part 2; Documentation Discussion
* [[Meeting_2014_06_20]] "Team Discussion Meeting"
* [[Meeting_2014_06_06]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement
* [[Meeting_2014_05_09]]
* [[Meeting_2014_04_29]]
* [[Meeting 2014_02_28]]
* [[Meeting_2014_01_03]]

=2013=
* [[Meeting_2013_12_06]] <-- Final 2013 Meeting
* [[Meeting_2013_11_22]]
* [[Meeting_2013_10_25]]
* [[Meeting_2013_08_30]]
* [[Meeting_2013_08_02]]
* [[Meeting_2013_06_22]]
* [[Meeting_2013_05_28]]
* [[Meeting_2013_05_10]]
* [[Meeting_2013_03_05]]
* [[Meeting_2013_02_01]]
* [[Meeting_2013_01_22]]
* [[Meeting_2013_01_04]]

=2012=
* [[Meeting_2012_12_11]]
* [[Meeting_2012_11_23]]
* [[Meeting_2012_11_09]]
* [[Meeting_2012_10_30]]
* [[Meeting_2012_10_12]]
* [[Meeting_2012_09_28]]
* [[Meeting_2012_09_18]]
* [[Meeting_2012_08_31]]
* [[Meeting_2012_08_17]]
* [[Meeting_2012_08_07]]
* [[Meeting_2012_06_26]]
* [[Meeting_2012_06_08]]
* [[Meeting_2012_05_25]]
* [[Meeting_2012_March_16]]

=2010=

* [[Meeting_2010_08_02]]
* [[Meeting_2010_07_19]]
* [[Meeting_2010_July_5]]
* [[Meeting_2010_June_7]]

Users

2018-11-10T14:48:56Z

LegacyKing:

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

Welcome to the Wiki section for the User Community!

=Online Resources=
* PCGen [http://pcgen.sourceforge.net website].
* Visit our [http://groups.yahoo.com/group/pcgen main community group/forum], please read the [[Posting Guidelines]] first
* Submit a Bug or Feature Request into our [https://pcgenorg.atlassian.net JIRA Tracking System]
** We need help! We have a [[PCGen Jira Guide]] on how to use this new tracking system.

=Wiki links=
* [[PCGen Features]]
* [[PCGen Requirements]]
* [[Updating Homebrew Sets]]
* The [[Roadmap]] for PCGen
* For our non English speakers we have a [[Internationalization]] section.
* The [[Data Wishlist]]
* [[4e Documentation Review]]
* The [[Output Sheet Wishlist]]
* An [[Explanation of Teams]] in PCGen

=Show your Support=
* You can [https://sourceforge.net/project/project_donations.php?group_id=25576 donate] to the project!

Meeting 2018 08 04

2018-08-04T13:58:14Z

LegacyKing: Created page with "'''Summary:''' Quick meeting, only data was represented. '''Raw Log:''' * [6:30 AM] Andrew Maitland: Welcome to the Board Meeting. The agenda for today is: * 1) Team Report..."

'''Summary:''' Quick meeting, only data was represented.

'''Raw Log:'''

* [6:30 AM] Andrew Maitland: Welcome to the Board Meeting. The agenda for today is:
* 1) Team Reports (10 minutes)
* 2) Tom's Roadblocks Update (35 minutes)
* 4) Public Q&A (5 minutes)
* [6:31 AM] Andrew Maitland: Tom appears to be absent, so we have a much shorter agenda this morning.
* [6:32 AM] Andrew Maitland: Team Reports - I see Data is present, so we'll cover that
* [6:33 AM] Andrew Maitland: We have had a few patches and submissions reviewed.
* [6:33 AM] Andrew Maitland: @DouglasLimmer has been working on a new source
* [6:33 AM] Andrew Maitland: Anything you want to add @DouglasLimmer or @GwenT ?
* [6:34 AM] Douglas Limmer: I've been a bit distracted, so my new source is coming along more slowly than I'd like.
* [6:35 AM] Gwen T: I hope to get working on UW archetypes, get them as close to finished as possible, once the kids are back in school. That will be a slow process, but I'd like to get it into release.
* [6:35 AM] Gwen T: @DouglasLimmer Which source?
* [6:36 AM] Douglas Limmer: Path of War Expanded
* [6:39 AM] Gwen T: I think that's the whole Data Team report....
* [6:40 AM] Andrew Maitland: We're still waiting on code to finalize the formula system so we can switch to beta releases and focus on bug fixes. But looks like real life threw a nasty curve ball on that one.
* [6:40 AM] Gwen T: Tom ok?
* [6:40 AM] Andrew Maitland: As far as I know. Just a busy guy.
* [6:41 AM] Andrew Maitland: We have no PR rep, but I saw Pathfinder 2 had a hiccup going out for the prerelease beta
* [6:42 AM] Andrew Maitland: Hopefully folks get their orders soon!
* [6:42 AM] Gwen T: Yeah. Amazon fulfillment can't move the product fast enough.
* [6:42 AM] Douglas Limmer: The PDFs are available for download. I have one.
* [6:42 AM] Gwen T: We have hardcopies, but ours came from Paizo
* [6:43 AM] Andrew Maitland: Anyways, since we lack the rest of the teams, we'll move onto Q&A.
* [6:43 AM] Andrew Maitland: Anyone is free to ask questions of the team.
* [6:43 AM] Andrew Maitland: (Obviously Code & PR questions might be deferred)...
* [6:44 AM] Douglas Limmer: What's the state of Starfinder material? Is there anyone specifically working on anything?
* [6:44 AM] Andrew Maitland: Core Rules is coded up, and working. Pact Worlds was submitted for License review in Newsources
* [6:45 AM] Douglas Limmer: I'm willing to code up the player-facing material in Alien Archive, but I should probably finish what I'm doing first.
* [6:45 AM] Andrew Maitland: My school schedule has kept me tied up, but that will change soon(tm).
* [6:48 AM] Andrew Maitland: Any other questions from our guests? @DavidGuest4 @SwiftbrookGuest ?
* [6:48 AM] David: Not me....
* [6:49 AM] Gwen T: It's been a rough summer for the PCGen team, it looks like!
* [6:50 AM] Andrew Maitland: Volunteers have lives outside of their *favorite* hobby, bound to happen.
* [6:51 AM] Andrew Maitland: Right, I have 6:50am. Thanks for everyone who made it. *Bangs Gavel* Meeting adjourned.

Meeting Logs

2018-08-04T13:57:10Z

LegacyKing: /* 2018 */

{| align="right"
| __TOC__
|}

This is a new section to hold the Meeting Logs.

=2018=
* [[Meeting 2018 08 04]] "Data Team in the house"
* [[Meeting 2018 04 28]] "Board Light Beta"
* [[Meeting 2018 03 31]] "Board Light Beta"
* [[Meeting 2018 02 24]] "Roadmap to Production"
* [[Meeting 2018 01 13]] "Future of PCGen"

=2017=
* [[Meeting 2017 06 17]] "Team Reports"
* [[Meeting 2017 02 25]] "Team Reports"
* [[Meeting 2017 01 21]] "Team Reports"

=2016=
* [[Meeting 2016 11 12]] "Release Discussion 6.07.01, and hold up"
* [[Meeting 2016 10 01]] "Discussion for 7.00"
* [[Meeting 2016 07 02]] "Quorum - 6.06 release and 7.00 roadmap"
* [[Meeting 2016 05 28]] "Informal"
* [[Meeting 2016 02 27]] "Production Release Meeting"

=2015=
* [[Meeting 2015 11 14]] "Informal Monthly Meeting"
* [[Meeting 2015 09 12]] "Monthly Meeting"
* [[Meeting 2015 08 15]] "Monthly Meeting"
* [[Meeting 2015 05 09]] "Monthly Meeting"

* [[Meeting 2015 03 27]] "Team Discussion"
* [[Meeting 2015 02 13]] "TBD"
* [[Meeting 2015 01 30]] "TBD"
* [[Meeting_2015_01_16]] "Informal"
* [[Meeting_2015_01_02]] "Team Discussion"

=2014=
* [[Agenda_Next_Meeting_Deep_Dive]]
* [[Agenda_Next_Meeting]]

* [[Meeting_2014_12_19]] "Deep Dive"
* [[Meeting_2014_12_05]] "Team Discussion"
* [[Meeting_2014_11_21]] "Deep Dive"
* [[Meeting_2014_11_07]] "Team Discussion & Parser Conversation Post Meeting"
* [[Meeting_2014_10_24]] "Deep Dive"
* [[Meeting_2014_10_10]] "Team Discussion"
* [[Meeting_2014_09_26]] "Post Release Meeting & Deep Dive"

* [[Meeting_2014_09_12]] "Release Meeting" RC2 good to Go?
* [[Meeting_2014_08_29]] "Release Meeting" RC1 good?
* [[Meeting_2014_08_15]] "Team Discussion Meeting"
* [[Meeting_2014_07_18]] "Team Discussion Meeting"
* [[Meeting_2014_07_11]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement Part 2; Documentation Discussion
* [[Meeting_2014_06_20]] "Team Discussion Meeting"
* [[Meeting_2014_06_06]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement
* [[Meeting_2014_05_09]]
* [[Meeting_2014_04_29]]
* [[Meeting 2014_02_28]]
* [[Meeting_2014_01_03]]

=2013=
* [[Meeting_2013_12_06]] <-- Final 2013 Meeting
* [[Meeting_2013_11_22]]
* [[Meeting_2013_10_25]]
* [[Meeting_2013_08_30]]
* [[Meeting_2013_08_02]]
* [[Meeting_2013_06_22]]
* [[Meeting_2013_05_28]]
* [[Meeting_2013_05_10]]
* [[Meeting_2013_03_05]]
* [[Meeting_2013_02_01]]
* [[Meeting_2013_01_22]]
* [[Meeting_2013_01_04]]

=2012=
* [[Meeting_2012_12_11]]
* [[Meeting_2012_11_23]]
* [[Meeting_2012_11_09]]
* [[Meeting_2012_10_30]]
* [[Meeting_2012_10_12]]
* [[Meeting_2012_09_28]]
* [[Meeting_2012_09_18]]
* [[Meeting_2012_08_31]]
* [[Meeting_2012_08_17]]
* [[Meeting_2012_08_07]]
* [[Meeting_2012_06_26]]
* [[Meeting_2012_06_08]]
* [[Meeting_2012_05_25]]
* [[Meeting_2012_March_16]]

=2010=

* [[Meeting_2010_08_02]]
* [[Meeting_2010_07_19]]
* [[Meeting_2010_July_5]]
* [[Meeting_2010_June_7]]

Meeting 2018 04 28

2018-04-28T13:57:27Z

LegacyKing: /* Log */

==Attendance==
* Andrew M.
* Paul G.
* Douglas L.
* Gwen T.
* Avilay
* William L.

==Summary==
* Beta gated by code requested PRs, no details from code
* Content working on bugs, but the core programmers are busy with real life (Slow progress)
* Ultimate Wilderness is in the final phase with just Archetypes waiting to be handled

==Log==
* [6:10 AM] Andrew Maitland: Welcome all to the pcgen board of director's meeting for April.
* [6:10 AM] Avilay: hello
* [6:11 AM] Andrew Maitland: Our planned agenda is 1: Team reports, 2: Beta status from Code, 3: Open forum
* [6:11 AM] Andrew Maitland: With nobody representing code #2 will not be possible
* [6:13 AM] Andrew Maitland: I'll kick this off for Content Team - We have had some bug fixes, and features by the team. My involvement will be less for the next 11 weeks as I finish up some advanced classes. Regan is assisting with a new OS for SagaBorn system. Otherwise, not too much activity this past month.
* [6:14 AM] Andrew Maitland: Paul - What's happening with the PR team?
* [6:17 AM] Paul Grosse: There's been a few requests for books, I've put them in Jira or pointed people at that to add them.
* [6:17 AM] Paul Grosse: I think everything ready for release has been cleared, will catch up tomorrow and make sure nothing has been marked for license review
* [6:18 AM] Paul Grosse: Other than that I think it's been kinda quiet on the PR front
* [6:19 AM] Andrew Maitland: Have we contacted any publishers for the Facebook inquiries we've had? I know one was for a Cthulhu system we assisted a user with...
* [6:21 AM] Paul Grosse: Hmm, I don't think I had, I'll review the FB messages this weekend for those.
* [6:21 AM] Andrew Maitland: Okay, thanks.
* [6:23 AM] Andrew Maitland: We're waiting on code to push in several PRs before they'll be ready to switch gears in a Beta mode. We planned on a month or so of Beta, then 2 Release Candidates, before 6.08.00 is pushed out. Then 6.09.00 would be focused on full conversion for the formula system. At present rate, we're looking at a July or August production release.
* [6:24 AM] Andrew Maitland: @TomParker has the exact information on how far out Code is.
* [6:25 AM] Andrew Maitland: I think the covers the official team agenda, I'll open the forum for any questions or comments from those present.
* [6:26 AM] Andrew Maitland: @here any questions or comments?
* [6:26 AM] Avilay: august release?
* [6:27 AM] Andrew Maitland: August release of 6.08.00 - the first production release
* [6:27 AM] Andrew Maitland: A version we deem is stable/safe for public consumption. Like the older 6.06.01 release most people use
* [6:27 AM] Avilay: oki
* [6:28 AM] Douglas Limmer: What books are people asking for? [Yes, I'm too lazy to look at JIRA.]
* [6:29 AM] Andrew Maitland: Our release follow a standard "Alpha (toss in new features), Beta (Fix introduced bugs), Release Candidate (Verify we fixed known issues), Production (We're happy to have the public use it)"
* [6:29 AM] Andrew Maitland: Horror Adventures is one
* [6:30 AM] Andrew Maitland: Curse of the Crimson Throne
* [6:31 AM] Andrew Maitland: In One's Blood
* [6:32 AM] Avilay: ultimate wilderness, gwen is working on it already
* [6:32 AM] Andrew Maitland: Those are the most recent requests, I know the Paths of Prestige has been requested recently on forums
* [6:32 AM] William L (WarStoke): has any one looked at spheres of power?
* [6:33 AM] Andrew Maitland: I worked on that for David, and he adapted it a bit. Not sure if it's release worthy
* [6:34 AM] Andrew Maitland: Morning Gwen. Folks are asking how Ultimate Wilderness is coming along
* [6:34 AM] Gwen T: Sorry. Life's been busy...
* [6:35 AM] Andrew Maitland: An all too common issue.
* [6:35 AM] Gwen T: US is 90% done. Mostly archetypes left. 40 or so IIRC.
* [6:35 AM] Avilay: hmmmm.... why that about life is so familiar. no hassle in time taken
* [6:36 AM] Gwen T: So it's farther along than Intrigue was when we put it out as an alpha...
* [6:38 AM] Andrew Maitland: Sounds good. Thanks for the update Gwen. Any other questions or comments before I end the meeting?
* [6:39 AM] Douglas Limmer: Not from me.
* [6:39 AM] Avilay: i can test shifter normal
* [6:40 AM] Avilay: have a shifter character
* [6:40 AM] William L (WarStoke): any luck with getting winter witches working again ?
* [6:40 AM] William L (WarStoke): havent seen any updates to the bug report
* [6:41 AM] Andrew Maitland: Like Gwen, I've been extremely busy with life. I have a Final due tomorrow, and then then next 14 weeks I'm in two advanced overlapping programming classes for the summer semester
* [6:42 AM] Gwen T: @Avilay My local game shop requested it. They've been testing it since late November. I've adjusted it based on their feedback. So if you test it, try to break it! It's pretty solid, I believe.
* [6:42 AM] Avilay: will do my best
* [6:42 AM] William L (WarStoke): @AndrewMaitland wow heavy load
* [6:43 AM] Andrew Maitland: My fall semester has one last heavy hitting 300 series class IIRC, and then two general ed classes, before I graduate.
* [6:44 AM] William L (WarStoke): hopefully not in two extreamly dissimilar lang's i made the mistake of taking french and spanish and latin freshman year of col as electives lol to get all 3 lang classes out of the way lol was brutal
* [6:44 AM] Andrew Maitland: Yeah, heavy load. I have 8 books between the next two classes to pound out.
* [6:44 AM] Andrew Maitland: Nope, no language classes, history and philosophy I think
* [6:46 AM] Andrew Maitland: Thanks for everyone showing up to participate. This concludes our Board meeting. *Bangs Gavel*

Meeting 2018 04 28

2018-04-28T13:56:26Z

LegacyKing: Created page with " ==Attendance== * Andrew M. * Paul G. * Douglas L. * Gwen T. * Avilay * William L. ==Summary== * Beta gated by code requested PRs, no details from code * Content working on b..."

==Attendance==
* Andrew M.
* Paul G.
* Douglas L.
* Gwen T.
* Avilay
* William L.

==Summary==
* Beta gated by code requested PRs, no details from code
* Content working on bugs, but the core programmers are busy with real life (Slow progress)
* Ultimate Wilderness is in the final phase with just Archetypes waiting to be handled

==Log==
[6:10 AM] Andrew Maitland: Welcome all to the pcgen board of director's meeting for April.
[6:10 AM] Avilay: hello
[6:11 AM] Andrew Maitland: Our planned agenda is 1: Team reports, 2: Beta status from Code, 3: Open forum
[6:11 AM] Andrew Maitland: With nobody representing code #2 will not be possible
[6:13 AM] Andrew Maitland: I'll kick this off for Content Team - We have had some bug fixes, and features by the team. My involvement will be less for the next 11 weeks as I finish up some advanced classes. Regan is assisting with a new OS for SagaBorn system. Otherwise, not too much activity this past month.
[6:14 AM] Andrew Maitland: Paul - What's happening with the PR team?
[6:17 AM] Paul Grosse: There's been a few requests for books, I've put them in Jira or pointed people at that to add them.
[6:17 AM] Paul Grosse: I think everything ready for release has been cleared, will catch up tomorrow and make sure nothing has been marked for license review
[6:18 AM] Paul Grosse: Other than that I think it's been kinda quiet on the PR front
[6:19 AM] Andrew Maitland: Have we contacted any publishers for the Facebook inquiries we've had? I know one was for a Cthulhu system we assisted a user with...
[6:21 AM] Paul Grosse: Hmm, I don't think I had, I'll review the FB messages this weekend for those.
[6:21 AM] Andrew Maitland: Okay, thanks.
[6:23 AM] Andrew Maitland: We're waiting on code to push in several PRs before they'll be ready to switch gears in a Beta mode. We planned on a month or so of Beta, then 2 Release Candidates, before 6.08.00 is pushed out. Then 6.09.00 would be focused on full conversion for the formula system. At present rate, we're looking at a July or August production release.
[6:24 AM] Andrew Maitland: @TomParker has the exact information on how far out Code is.
[6:25 AM] Andrew Maitland: I think the covers the official team agenda, I'll open the forum for any questions or comments from those present.
[6:26 AM] Andrew Maitland: @here any questions or comments?
[6:26 AM] Avilay: august release?
[6:27 AM] Andrew Maitland: August release of 6.08.00 - the first production release
[6:27 AM] Andrew Maitland: A version we deem is stable/safe for public consumption. Like the older 6.06.01 release most people use
[6:27 AM] Avilay: oki
[6:28 AM] Douglas Limmer: What books are people asking for? [Yes, I'm too lazy to look at JIRA.]
[6:29 AM] Andrew Maitland: Our release follow a standard "Alpha (toss in new features), Beta (Fix introduced bugs), Release Candidate (Verify we fixed known issues), Production (We're happy to have the public use it)"
[6:29 AM] Andrew Maitland: Horror Adventures is one
[6:30 AM] Andrew Maitland: Curse of the Crimson Throne
[6:31 AM] Andrew Maitland: In One's Blood
[6:32 AM] Avilay: ultimate wilderness, gwen is working on it already
[6:32 AM] Andrew Maitland: Those are the most recent requests, I know the Paths of Prestige has been requested recently on forums
[6:32 AM] William L (WarStoke): has any one looked at spheres of power?
Gwen T joined the room
[6:33 AM] Andrew Maitland: I worked on that for David, and he adapted it a bit. Not sure if it's release worthy
[6:34 AM] Andrew Maitland: Morning Gwen. Folks are asking how Ultimate Wilderness is coming along
[6:34 AM] Gwen T: Sorry. Life's been busy...
[6:35 AM] Andrew Maitland: An all too common issue.
[6:35 AM] Gwen T: US is 90% done. Mostly archetypes left. 40 or so IIRC.
[6:35 AM] Avilay: hmmmm.... why that about life is so familiar. no hassle in time taken
[6:36 AM] Gwen T: So it's farther along than Intrigue was when we put it out as an alpha...
[6:38 AM] Andrew Maitland: Sounds good. Thanks for the update Gwen. Any other questions or comments before I end the meeting?
[6:39 AM] Douglas Limmer: Not from me.
[6:39 AM] Avilay: i can test shifter normal
[6:40 AM] Avilay: have a shifter character
[6:40 AM] William L (WarStoke): any luck with getting winter witches working again ?
[6:40 AM] William L (WarStoke): havent seen any updates to the bug report
[6:41 AM] Andrew Maitland: Like Gwen, I've been extremely busy with life. I have a Final due tomorrow, and then then next 14 weeks I'm in two advanced overlapping programming classes for the summer semester
[6:42 AM] Gwen T: @Avilay My local game shop requested it. They've been testing it since late November. I've adjusted it based on their feedback. So if you test it, try to break it! It's pretty solid, I believe.
[6:42 AM] Avilay: will do my best
[6:42 AM] William L (WarStoke): @AndrewMaitland wow heavy load
[6:43 AM] Andrew Maitland: My fall semester has one last heavy hitting 300 series class IIRC, and then two general ed classes, before I graduate.
[6:44 AM] William L (WarStoke): hopefully not in two extreamly dissimilar lang's i made the mistake of taking french and spanish and latin freshman year of col as electives lol to get all 3 lang classes out of the way lol was brutal
[6:44 AM] Andrew Maitland: Yeah, heavy load. I have 8 books between the next two classes to pound out.
[6:44 AM] Andrew Maitland: Nope, no language classes, history and philosophy I think
[6:46 AM] Andrew Maitland: Thanks for everyone showing up to participate. This concludes our Board meeting. *Bangs Gavel*

Meeting Logs

2018-04-28T13:51:24Z

LegacyKing: /* 2018 */

{| align="right"
| __TOC__
|}

This is a new section to hold the Meeting Logs.

=2018=
* [[Meeting 2018 04 28]] "Board Light Beta"
* [[Meeting 2018 03 31]] "Board Light Beta"
* [[Meeting 2018 02 24]] "Roadmap to Production"
* [[Meeting 2018 01 13]] "Future of PCGen"

=2017=
* [[Meeting 2017 06 17]] "Team Reports"
* [[Meeting 2017 02 25]] "Team Reports"
* [[Meeting 2017 01 21]] "Team Reports"

=2016=
* [[Meeting 2016 11 12]] "Release Discussion 6.07.01, and hold up"
* [[Meeting 2016 10 01]] "Discussion for 7.00"
* [[Meeting 2016 07 02]] "Quorum - 6.06 release and 7.00 roadmap"
* [[Meeting 2016 05 28]] "Informal"
* [[Meeting 2016 02 27]] "Production Release Meeting"

=2015=
* [[Meeting 2015 11 14]] "Informal Monthly Meeting"
* [[Meeting 2015 09 12]] "Monthly Meeting"
* [[Meeting 2015 08 15]] "Monthly Meeting"
* [[Meeting 2015 05 09]] "Monthly Meeting"

* [[Meeting 2015 03 27]] "Team Discussion"
* [[Meeting 2015 02 13]] "TBD"
* [[Meeting 2015 01 30]] "TBD"
* [[Meeting_2015_01_16]] "Informal"
* [[Meeting_2015_01_02]] "Team Discussion"

=2014=
* [[Agenda_Next_Meeting_Deep_Dive]]
* [[Agenda_Next_Meeting]]

* [[Meeting_2014_12_19]] "Deep Dive"
* [[Meeting_2014_12_05]] "Team Discussion"
* [[Meeting_2014_11_21]] "Deep Dive"
* [[Meeting_2014_11_07]] "Team Discussion & Parser Conversation Post Meeting"
* [[Meeting_2014_10_24]] "Deep Dive"
* [[Meeting_2014_10_10]] "Team Discussion"
* [[Meeting_2014_09_26]] "Post Release Meeting & Deep Dive"

* [[Meeting_2014_09_12]] "Release Meeting" RC2 good to Go?
* [[Meeting_2014_08_29]] "Release Meeting" RC1 good?
* [[Meeting_2014_08_15]] "Team Discussion Meeting"
* [[Meeting_2014_07_18]] "Team Discussion Meeting"
* [[Meeting_2014_07_11]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement Part 2; Documentation Discussion
* [[Meeting_2014_06_20]] "Team Discussion Meeting"
* [[Meeting_2014_06_06]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement
* [[Meeting_2014_05_09]]
* [[Meeting_2014_04_29]]
* [[Meeting 2014_02_28]]
* [[Meeting_2014_01_03]]

=2013=
* [[Meeting_2013_12_06]] <-- Final 2013 Meeting
* [[Meeting_2013_11_22]]
* [[Meeting_2013_10_25]]
* [[Meeting_2013_08_30]]
* [[Meeting_2013_08_02]]
* [[Meeting_2013_06_22]]
* [[Meeting_2013_05_28]]
* [[Meeting_2013_05_10]]
* [[Meeting_2013_03_05]]
* [[Meeting_2013_02_01]]
* [[Meeting_2013_01_22]]
* [[Meeting_2013_01_04]]

=2012=
* [[Meeting_2012_12_11]]
* [[Meeting_2012_11_23]]
* [[Meeting_2012_11_09]]
* [[Meeting_2012_10_30]]
* [[Meeting_2012_10_12]]
* [[Meeting_2012_09_28]]
* [[Meeting_2012_09_18]]
* [[Meeting_2012_08_31]]
* [[Meeting_2012_08_17]]
* [[Meeting_2012_08_07]]
* [[Meeting_2012_06_26]]
* [[Meeting_2012_06_08]]
* [[Meeting_2012_05_25]]
* [[Meeting_2012_March_16]]

=2010=

* [[Meeting_2010_08_02]]
* [[Meeting_2010_07_19]]
* [[Meeting_2010_July_5]]
* [[Meeting_2010_June_7]]

Git Setup

2018-03-31T16:45:44Z

LegacyKing: Created page with " git is what the PCGen uses to track changes and move those changes to our git repository on github.com. For Linux and Mac users, you will need to download/install git for yo..."

git is what the PCGen uses to track changes and move those changes to our git repository on github.com.

For Linux and Mac users, you will need to download/install git for you operating system.

Windows machines:
* Download git and install it -- LINK: https://git-scm.com/downloads
* You can use command line, or a git client. However, the programs the team uses are [https://www.sourcetreeapp.com/ SourceTree] and the [https://tortoisegit.org/ TortoiseGit Windows Shell Interface]

We will want to create a SSH key. This can be accomplished using PuttyGen, which comes with TortoiseGit or is a standalone [https://www.ssh.com/ssh/putty/windows/puttygen download here]

Create the Key, you will move your mouse to seed randomness. Once that is done, the window will have a KEY. Save the Private key somewhere easy to remember, like Documents/keys. Copy the public portion (Entire window), we'll be using that in a moment.

Next, you will need a [https://github.com/ GitHub account].

Once you have an account, [https://github.com/settings/keys click here to go to your settings/keys]

Create a NEW SSH KEY

Paste the key, and name it, click okay/save.

After that, you will want to have a copy of the PCGen Project, [https://github.com/PCGen/pcgen#fork-destination-box click on this to FORK a copy of the PCGen development] and [https://github.com/PCGen/pcgen-newsources#fork-destination-box click here for the NewSource Development]

After you have Forked, the green Button Clone or Download will have a LINK. Example: git@github.com:PCGen/pcgen.git or if you desire git@github.com:<YourUserName>/pcgen.git

Copy that LINK.

Next, you'll want to clone that repository onto your computer. I recommend a folder set aside for these repos. Like c:\Projects\PCGen. If using tortoisegit, right click while inside the destination folder and select 'Git Clone here'. If you copied the Github Clone link, then tortoisegit has already placed that link for the URL.

[[FILE:Tgit-clone.PNG]]

Check the Load Putty Key and give it the path to your key you created. Verify the destination is correct, and then click okay. Repeat the Git clone process for every repo you want to have available.

===Contribute Work===

If you are going to edit and work on files for inclusion in the next release, then you need to become familiar with the terms used and the workflow.

* Branch - A named branch to edit files in. (Always do changes in a branch). PCGen standards are name branchs for the JIRA you are working on. Each feature or bug gets a separate branch.
* Switch/Checkout - Method to change branch
* Add - Adds files to the git stage
* Commit - Takes the 'added' files and takes a snapshot of the changes
* Push - Takes all the snapshots in the branch, and "pushes" those changes to a remote repository (In this case, your repository on github.com)
* Pull Request (PR) - How to get your branch and changes to be seen by the upstream repository (PCGen/pcgen or PCGen/pcgen-Newsource).
* Merged - What takes place when two branches combine into each other. Each branch needs to eventually merge into the master to be seen for the releases.

* Fetch - Used to grab the list of another remote repository branch list
* Pull - Pull changes from the selected repository into the current selected branch
* Rebase - Used during a Pull/Fetch to reorder the commits you have made, and place them after the existing commits.

ALL work takes place on your computer. You host a local repository on your computer. You add/commit to save those changes. PUSH and PULL REQUEST are the methods to move your changes into the internet and share your changes with the team.

File:Tgit-clone.PNG

2018-03-31T16:31:14Z

LegacyKing: Screenshot of tortoisegit clone dialog

Screenshot of tortoisegit clone dialog

Meeting 2018 03 31

2018-03-31T16:10:26Z

LegacyKing: Created page with "=Board Meeting 2018/03/31= ==Participants== * Andrew (Content / Acting Chair) * Paul (Public & Publisher Relations) * Douglas L. * William L. * David B. ==Summary== * PR has..."

=Board Meeting 2018/03/31=

==Participants==
* Andrew (Content / Acting Chair)
* Paul (Public & Publisher Relations)
* Douglas L.
* William L.
* David B.

==Summary==
* PR has flyers and swag if anyone wants to represent PCGen at any upcoming conventions
* 6.07.07 had an issue with the windows installer and pcgen.sh not being executable. Javier has been helping to address that.
* 6.07.08 should be released tonight
* Still Alpha. Code is gating the switch to Beta pending several code merges

===Raw log===
* [6:05 AM] Andrew Maitland: Welcome to the PCGen Board of Director's Meeting for March 31st 2018.
* [6:06 AM] Andrew Maitland: Agenda:1) Team Reports (10 minutes)
* 2) Tom's Roadblocks Update (35 minutes)
* 3) Public Q&A (5 minutes)
* [6:06 AM] Andrew Maitland: @PaulGrosse would you like to give an update for PR?
* [6:07 AM] Paul Grosse: Lets see, since the last meeting all sources that were deemed complete and submitted for license review were cleared. One book by Legendary Games was decided it needed more work.
* [6:08 AM] Paul Grosse: Andrew and I are continuing to keep up with the various media fronts for PCGen, FB, forums, reddit, twitter, etc.
* [6:09 AM] Paul Grosse: If anyone has any cons coming up that they want to represent PCGen at, or leave some flyers on a swag table let me know
* [6:10 AM] Paul Grosse: I think that's about it
* [6:10 AM] Paul Grosse: Any questions?
* [6:10 AM] Andrew Maitland: None from me, thanks Paul!
* [6:11 AM] Andrew Maitland: Okay, content report -
* [6:12 AM] Andrew Maitland: Been working on mainly bug fixes found in the newer releases that were put out in 6.07.07. Thanks to our community who catch issues and report them.
* [6:13 AM] Andrew Maitland: I've done a lot of conversion to the new formula system with Starfinder, as that is a nice new game system with minimal files to change.
* [6:14 AM] Andrew Maitland: I'll be including that for the upcoming 6.07.08 (Tonight if all goes well)
* [6:14 AM] Paul Grosse: Did the Windows installer get worked out?
* [6:14 AM] Andrew Maitland: Our last release had issues with the Windows Installer. I have been working with Javier to get that hammered out.
* [6:15 AM] Andrew Maitland: I'll be testing his efforts to see where we land. And get those included if they work properly (He also included the build testing for Mac, so we have two distinct build tests - Linux and Mac).
* [6:16 AM] Paul Grosse: Yea!
* [6:16 AM] Andrew Maitland: The end goal is to have our CI actually build the release so it is consistent every time.
* [6:17 AM] Andrew Maitland: We've discovered a "break PCGen" bug with temporary bonuses and the javascript in Eddy's Fantasy Character Sheet (Character Tab Only)
* [6:18 AM] Andrew Maitland: Due to that, I'm afraid I'll have to pull it, until we can fix the javascript (Handles Rolling Dice)
* [6:20 AM] Andrew Maitland: Questions for Content?
* [6:20 AM] Paul Grosse: Want me to see if Eddy wants to take a look at it?
* [6:20 AM] Andrew Maitland: Yes please.
* [6:22 AM] Andrew Maitland: For Code -
* [6:24 AM] Andrew Maitland: Tom has not indicated he is ready to go Beta, he indicated he had about 3 more PR's that had to be merged in a specific order and conflicts resolved before Code would be ready to switch.
* [6:25 AM] Andrew Maitland: Tonight's release will be an Alpha as a result, and then the next release after should be a Beta. Gated upon Code giving the green light.
* [6:26 AM] Andrew Maitland: Any questions for the release/code portion?
* [6:27 AM] Paul Grosse: Not from I
* [6:28 AM] Andrew Maitland: Okay, well, I've covered Agenda #1 and #2, so that leaves us with #3 Public Forums.
* [6:28 AM] Andrew Maitland: Open Discussion time - Any questions for the Board of Directors from anyone?
* [6:29 AM] Andrew Maitland: Doug, David, or William?
* [6:29 AM] Papa (aka David Bender): not from I
* [6:29 AM] William L: I for one just want to say thank you to you folks and every one involved
* [6:29 AM] Douglas Limmer: No questions here.
* [6:30 AM] Andrew Maitland: Thanks David
* [6:30 AM] Andrew Maitland: Thanks for the kind words William
* [6:30 AM] Andrew Maitland: Thanks Douglas
* [6:31 AM] Andrew Maitland: Okay, well if there is no other business to present to the Board of Directors, I declare this meeting is adjourned.
* Andrew Maitland bangs gavel

Meeting Logs

2018-03-31T13:37:00Z

LegacyKing: /* 2018 */

{| align="right"
| __TOC__
|}

This is a new section to hold the Meeting Logs.

=2018=
* [[Meeting 2018 03 31]] "Board Light Beta"
* [[Meeting 2018 02 24]] "Roadmap to Production"
* [[Meeting 2018 01 13]] "Future of PCGen"

=2017=
* [[Meeting 2017 06 17]] "Team Reports"
* [[Meeting 2017 02 25]] "Team Reports"
* [[Meeting 2017 01 21]] "Team Reports"

=2016=
* [[Meeting 2016 11 12]] "Release Discussion 6.07.01, and hold up"
* [[Meeting 2016 10 01]] "Discussion for 7.00"
* [[Meeting 2016 07 02]] "Quorum - 6.06 release and 7.00 roadmap"
* [[Meeting 2016 05 28]] "Informal"
* [[Meeting 2016 02 27]] "Production Release Meeting"

=2015=
* [[Meeting 2015 11 14]] "Informal Monthly Meeting"
* [[Meeting 2015 09 12]] "Monthly Meeting"
* [[Meeting 2015 08 15]] "Monthly Meeting"
* [[Meeting 2015 05 09]] "Monthly Meeting"

* [[Meeting 2015 03 27]] "Team Discussion"
* [[Meeting 2015 02 13]] "TBD"
* [[Meeting 2015 01 30]] "TBD"
* [[Meeting_2015_01_16]] "Informal"
* [[Meeting_2015_01_02]] "Team Discussion"

=2014=
* [[Agenda_Next_Meeting_Deep_Dive]]
* [[Agenda_Next_Meeting]]

* [[Meeting_2014_12_19]] "Deep Dive"
* [[Meeting_2014_12_05]] "Team Discussion"
* [[Meeting_2014_11_21]] "Deep Dive"
* [[Meeting_2014_11_07]] "Team Discussion & Parser Conversation Post Meeting"
* [[Meeting_2014_10_24]] "Deep Dive"
* [[Meeting_2014_10_10]] "Team Discussion"
* [[Meeting_2014_09_26]] "Post Release Meeting & Deep Dive"

* [[Meeting_2014_09_12]] "Release Meeting" RC2 good to Go?
* [[Meeting_2014_08_29]] "Release Meeting" RC1 good?
* [[Meeting_2014_08_15]] "Team Discussion Meeting"
* [[Meeting_2014_07_18]] "Team Discussion Meeting"
* [[Meeting_2014_07_11]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement Part 2; Documentation Discussion
* [[Meeting_2014_06_20]] "Team Discussion Meeting"
* [[Meeting_2014_06_06]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement
* [[Meeting_2014_05_09]]
* [[Meeting_2014_04_29]]
* [[Meeting 2014_02_28]]
* [[Meeting_2014_01_03]]

=2013=
* [[Meeting_2013_12_06]] <-- Final 2013 Meeting
* [[Meeting_2013_11_22]]
* [[Meeting_2013_10_25]]
* [[Meeting_2013_08_30]]
* [[Meeting_2013_08_02]]
* [[Meeting_2013_06_22]]
* [[Meeting_2013_05_28]]
* [[Meeting_2013_05_10]]
* [[Meeting_2013_03_05]]
* [[Meeting_2013_02_01]]
* [[Meeting_2013_01_22]]
* [[Meeting_2013_01_04]]

=2012=
* [[Meeting_2012_12_11]]
* [[Meeting_2012_11_23]]
* [[Meeting_2012_11_09]]
* [[Meeting_2012_10_30]]
* [[Meeting_2012_10_12]]
* [[Meeting_2012_09_28]]
* [[Meeting_2012_09_18]]
* [[Meeting_2012_08_31]]
* [[Meeting_2012_08_17]]
* [[Meeting_2012_08_07]]
* [[Meeting_2012_06_26]]
* [[Meeting_2012_06_08]]
* [[Meeting_2012_05_25]]
* [[Meeting_2012_March_16]]

=2010=

* [[Meeting_2010_08_02]]
* [[Meeting_2010_07_19]]
* [[Meeting_2010_July_5]]
* [[Meeting_2010_June_7]]

Mailing Lists and PCGen Links

2018-03-29T04:19:27Z

LegacyKing: /* I need Help, please! */

=I need Help, please!=
* [mailto:help@pcgen.org Email the Help Desk Help@PCGen.org]
* [https://www.hipchat.com/gmddByrFS I need to talk to a real person via Hipchat]

==Related Lists==
* [http://pcgen.sourceforge.net PCGen's Release Site (On Sourceforge)]
* [https://github.com/PCGen/pcgen PCGen's Development on GITHUB]
* [https://github.com/PCGen/pcgen-newsource PCGen's New Source Development on GITHUB]
* [http://www.pcgen.org PCGen's Main Site]
* [http://groups.pcgen.org PCGen Forums!]
* [https://www.facebook.com/PCGen/ PCGen Facebook Page]
* [https://www.facebook.com/groups/267698787055301/ Official Friends of PCGen Facebook group]
* [http://wiki.pcgen.org/ PCGen's Wiki]
* [https://pcgenorg.atlassian.net PCGen's Bug & New Feature Requests Tracker] (Users may submit bugs or requests for new features)
* [http://www.pcgen.org/index.php?title=Roadmap PCGen's Roadmap]

===Autobuilds===
* [http://www.pcgen.org/autobuilds/ PCGen's Trunk/Development nightly Autobuild]
* [http://www.pcgen.org/autobuilds-prod/ PCGen's Production nightly Autobuild]

==='''PCGen Yahoo Groups'''===
* [http://games.groups.yahoo.com/group/pcgen/ PCGen] (The main PCGen group for asking generic questions and reporting bugs. High Traffic)
* [http://tech.groups.yahoo.com/group/pcgen_developers/ PCGen Developers] (Where the Code and Architecture monkeys hang out to discuss code implementation)
* [http://games.groups.yahoo.com/group/PCGen_webteam/ PCGen Webteam] (The Website team gathers here to discuss implementation and maintenance of the future website for PCGen)
* [http://tech.groups.yahoo.com/group/pcgen_international/ PCGen International] (Where international standards and translations are discussed by our international users. LOW TRAFFIC)
* [http://tech.groups.yahoo.com/group/PCGenListFileHelp/ PCGen List File Help](for assistance in creating new homebrew or official list files)
* [http://tech.groups.yahoo.com/group/pcgen_experimental/ PCGen Experimental] (for new official data source development and cutting edge FREQs)

=== PCGen JIRA Mailing Lists ===

'''Team Project Tracker Groups'''

These are grouped tracker mailing lists

* [https://lists.sourceforge.net/mailman/listinfo/pcgen-team-code pcgen-team-code] - This encompasses all Code, New Tag and Support Requests
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-team-content pcgen-team-content] - This encompasses all Data, Docs and Outputsheet Trackers

'''GITHUB Commit List'''
* [https://lists.sourceforge.net/lists/listinfo/pcgen-github Github.com commits] - Only subscribe to this list if you want to see all the code and data changes added to the PCGen Repository

'''Main Tracker'''

This Tracker gets ALL the JIRA PCGen Project Traffic (HIGH TRAFFIC)

* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers pcgen-trackers] - This list will receive all the changes made to the PCGen trackers.

'''Individual Project Tracker Lists'''

Subscribe to individual Project Trackers

* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_code pcgen-trackers_code] - This mailing list will send out every change to Code related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_code pcgen-trackers_data] - This mailing list will send out every change in the Data related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_docs pcgen-trackers_docs] - This list will send out every change in the Documentation related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_new_source pcgen-trackers_new_source] - This mailing list will send out every New Source being worked on in PCGen
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_new_tag pcgen-trackers_new_tag] - This mailing list will send out every New Tag proposal related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_outputsheets pcgen-trackers_outputsheets] - This mailing list will send out every change in the OS related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_project_test_requests pcgen-trackers_project_test_requests] - This mailing list will send out every Project Test Request related trackers
* [https://lists.sourceforge.net/mailman/listinfo/pcgen-trackers_support_requests pcgen-trackers_support_requests] - This mailing list will send out every support request from the trackers

'''OBSOLETE: SVN Commit List'''

Only subscribe to this list if you want to see all the code and data changes added to the PCGen Repository

* [https://lists.sourceforge.net/mailman/listinfo/pcgen-commit-svn pcgen-commit-svn] - Subversion commits

=== PCGen Misc. Mailing Lists ===

* [https://lists.sourceforge.net/lists/listinfo/pcgen-wiki PCGen Wiki Mailing List] - This is a mailing list to keep tabs on the wiki maintained by PCGen.

Old links:
* PCGen's Autobuilds and Docs: http://pcgen-test.org/autobuilds/ (Where you can get up to date changes from the nightly build)
* Direct Link to PCGen's Online Docs: http://pcgen-test.org/autobuilds/pcgen-docs/index.html
* PCGen's Backup Autobuilds and Docs: http://pcgen.akozakis.id.au/autobuilds/download.html
* [http://games.groups.yahoo.com/group/LSTfileclass/ OBSOLETE: PCGen List File Class] (Where new documentation for class files are discussed. LOW TRAFFIC)

TEMPBONUS Replacement

2018-03-26T02:24:42Z

LegacyKing: Created page with "On the Temporary Bonus tab, we have the various Abilities, Spells, and Templates that can alter the character for a temporary time. This Tab is populated only when a specific..."

On the Temporary Bonus tab, we have the various Abilities, Spells, and Templates that can alter the character for a temporary time. This Tab is populated only when a specific tag is used "TEMPBONUS".

Furthermore, TEMPBONUS has three aspects to control when or what is impacted -
'PC'
If the character must have the object 'attached' to it to see this object in the list
'ANYPC'
This produces a list of any ability, spell or effect placed upon them from another caster or object (potion, wand, poison, etc.)
EQ (Equipment)
This is visible always, but only alters the equipment type(s) listed. Example of Power Attack has different effects based upon the Weapon Handedness.

Issue - TEMPBONUS is JEP. It is a derivative of the BONUS tag.

Question, what will we replace TEMPBONUS with, or will we reuse the MODIFY/MODIFYOTHER tags and use special tags inside to denote they are a Temp variety?

MODIFYOTHER:Foo|Bar|ADD|TEMP(Formula Or value)

TEMPBONUS has a special Number only chooser called TEMPVALUE which allows the selection of a Number range. Will TEMPVALUE interact with the new System, since often the Caster Level of the temporary effect must be determined?

Data Team Discussions for Replacements

2018-03-26T02:12:24Z

LegacyKing:

[[Archetype Swapping Concerns]]

[[Race Racial Trait Swapping]]

[[Animal Companion Sprawl]]

[[TEMPBONUS Replacement]]

Animal Companion Sprawl

2018-03-25T23:42:12Z

LegacyKing: Created page with "One of the conventional holdovers from the D&D 3.5e era was multiple categories of companions - Familiar, Animal Companion, and Special Mount. In Pathfinder, these categories..."

One of the conventional holdovers from the D&D 3.5e era was multiple categories of companions - Familiar, Animal Companion, and Special Mount. In Pathfinder, these categories were changed to Familiar, and Animal Companion, with Eidolon added later as a Summoner companion.

Pathfinder:

Paladin Special Mount is an Animal Companion, same as the Samurai Mount, and the Cavalier Mount.

For the Paladin, we have a the Bonded Mount, "This mount functions as a druid’s animal companion, using the paladin’s level as her effective druid level. Bonded mounts have an Intelligence of at least 6."

For the Cavalier & Samurai, we have the Mount, "This mount functions as a druid’s animal companion, using the cavalier’s level as his effective druid level. The creature must be one that he is capable of riding and is suitable as a mount."

According to these FAQ rules:

FAQ: http://paizo.com/paizo/faq/v5748nruor1fn#v5748eaic9qqn

Cavalier: Do animal companion levels from the druid class stack with cavalier mount levels?

If the animal is on the cavalier mount list and on the list of animal companions for your other class, your cavalier and druid levels stack to determine the animal's abilities. If the animal is not on the cavalier mount list, the druid levels do not stack and you must have different animals (one an animal companion, one a cavalier mount).
For example, if you are Medium druid and you choose a horse companion, levels in cavalier stack to determine the horse's abilities. If you are a Medium druid and you choose a bird companion, levels in cavalier do not stack to determine the bird's abilities, and you must choose a second creature to be your mount (or abandon the bird and select an animal companion you can use as a mount).
This same answer applies to multiclassed cavalier/rangers.
(Note that the design team discourages players from having more than one companion creature at a time, as those creatures tend to be much weaker than a single creature affected by these stacking rules, and add to the bookkeeping for playing that character.)

In order to properly support these rulings, we'll need to take the MOST permissive lists, and place them in a selection.

Solution 1:

Separate out every single Animal Companion, have it add to one or more "lists" - 'Nature Bond Animal Companion', 'Divine Bond Mount', 'Mount'

Pros: Very precise, easy to add/remove
Cons: Ability or templates become very numerous.

Solution 2:
Have grouped Abilities that added entire groups of valid companions (Similar to what we are doing to handle Druid Archetypes).

Ultimate Solution:

Formula System v3 - Using the Arrays and allow the Lists to be populated from the Arrays.

Data Team Discussions for Replacements

2018-03-25T21:11:21Z

LegacyKing:

[[Archetype Swapping Concerns]]

[[Race Racial Trait Swapping]]

[[Animal Companion Sprawl]]

Setting up the new Formula System

2018-03-09T09:35:20Z

LegacyKing: /* FORMATs */

{| align="right"
| __TOC__
|}

=The basics=

The new formula system is designed to do a few things relative to data:
* Validate formulas at LST load instead of runtime
* Dramatically increase flexibility
* It will replace many tokens, including all the BONUS tokens
* It allows a sensible location for global modifications (things generally related to rule book type modifications that impact all objects of a given type)

==Key concepts==

To use the new system a few key things need to be remembered:
* It is possible to have local variables
* All variables must be defined prior to use
* Variables are not only numbers, but can be Strings, Dice, etc.
** We call this the variable FORMAT

You will want to keep track of what these key terms mean as you learn the new formula system:
* FORMAT: The type of variable, e.g. NUMBER, BOOLEAN, ORDEREDPAIR.
* SCOPE: The part of the data in which a (local) variable is available
* MODIFIER: An argument to MODIFY* tokens, specifically the "command" of what the modification represents
* OPERATOR: A mathematical operator as you would see in a formula ("+", "-", etc.)
* GROUPING: A name for a set of objects in PCGen
* ASSOCIATION: An additional set of information attached to a MODIFY* token. This is a key-value pair of information, e.g. PRIORITY=100

=Creating and Using Variables=

==Required Setup==

Every format that needs to be used requires a default value. This value is shared throughout an entire system (it CANNOT be redefined to a different value). This is placed into a file referred to in a PCC file from the DATACONTROL: token.

===DATACONTROL (PCC File)===

DATACONTROL: is a new Campaign file token (for PCC files). It is treated "recursively" like other tokens, e.g. TEMPLATE.

DATACONTROL:x

* x is the file to be loaded as a DATACONTROL file
* Limitations: It does not support PRExxx or INCLUDE/EXCLUDE.

===DEFAULTVARIABLEVALUE (DATACONTROL LST)===

The Format is:
DEFAULTVARIABLEVALUE:X|Y
* X is the format name
* Y is the default value

Example:
DEFAULTVARIABLEVALUE:NUMBER|0

It is a best practice to always define a DEFAULTVARIABLEVALUE for every FORMAT regardless of whether the data uses that FORMAT. The internal parts of PCGen may use it, so a default value may be required.

Note: it IS safe to "redefine" a DEFAULTVARIABLEVALUE to the same value. So if multiple datasets are loaded and they all had DATACONTROL: and all defined the default value for NUMBER to be 0, they will all happily load as the system is capable of recognizing the defaults are the same

==How to define a variable==

===VARIABLE (PCC File)===

To define a variable, you need to add an LST file that is referred to in a PCC file from the VARIABLE: token. It is treated "recursively" like other tokens, e.g. TEMPLATE.

VARIABLE:x

* x is the file to be loaded as a DATACONTROL file
* Limitations: It does not support PRExxx or INCLUDE/EXCLUDE.

There are 2 basic tokens for the VARIABLE file: GLOBAL and LOCAL.

===GLOBAL (VARIABLE File)===

* GLOBAL defines a global variable, usable from anywhere within the PlayerCharacter.

The format is:
GLOBAL:X=Y
* X is the format name
* Y is the variable name

Example:
GLOBAL:ORDEREDPAIR=Face

A GLOBAL token can take additional token on the line called EXPLANATION, which it is advisable to use to communicate to other data monkeys (and it is likely any future editor will also draw on this information).

===LOCAL (VARIABLE File)===

* LOCAL defines a local variable, usable only within the object on which the variable exists (or its children)
** The place where a local variable is usable is called the SCOPE. This could include a STAT (such as the stat's SCORE or STATMOD) or EQUIPMENT. The scopes possible in PCGen are hard-coded (see below for more info)

The format is:
LOCAL:W|X=Y
* W is the SCOPE of the variable
* X is the format name
* Y is the variable name

Example:
LOCAL:STAT|NUMBER=Score

A LOCAL token can take additional token on the line called EXPLANATION, which it is advisable to use to communicate to other data monkeys (and it is likely any future editor will also draw on this information).

===EXPLANATION (VARIABLE File)===

EXPLANATION: is a free-text token (no parsing is really done) that is designed to describe why a variable exists

Format:
EXPLANATION:x

* x is the text of the Explanation
* Limitations: By Design: Must not appear as the first token on a line
* Behavior: Overwrites (as if someone would use it twice??)

===Defaults in the VARIABLE file===

A few notes about the VARIABLE files:
If you see an item without a leading token, e.g.:
ORDEREDPAIR=Face
...then the system is using the default (GLOBAL). For now, the data standard is to avoid using this shortcut (as far as I know)

If you see an item without a leading format ("X" in both GLOBAL and LOCAL above), e.g.:
LOCAL:STAT|Score
...then the format is a NUMBER. For now, the data standard is to avoid using this shortcut (as far as I know)

Note both defaults can be combined, so a variable name with no other information on that line is a Global NUMBER

===No Overlapping===

In most programming languages, it is legal to have local variable share the same name as the global variable and thus "override" it in that context (although it is considered less than ideal, and in some languages it will now produce a warning). It is not legal in PCGen.

If a Global variable called "Hands" exists, then NO local variable IN ANY SCOPE can be "Hands".

Similar restrictions exist for scopes and SubScopes. If "CritMult" is an EQUIPMENT variable, then "CritMult" can't be an EQUIPMENT.PART variable.

Non-overlapping (when the Scopes do not interact) is legal. "Score" can be a local STAT variable and a local CHECK variable, for example.

For clarity:
* This occurs regardless of the FORMAT of the variables - tokens will infer the format from the variable name, so you can't have overlapping variables even of different FORMAT.
* Two variables of the same name but different FORMAT in the same SCOPE will cause an error as well, because that is effectively overlapping, and those variables can't be distinguished in most circumstances.

===Identical Duplication Legal===

It is legal for a load to include one or more PCC files that have one or more VARIABLE: files that redefine the same variables. As long as they are the same format and scope, they are not considered an error. If either the scope or format differs, then the "No Overlapping" rules above are applied.

A difference in the "Explanation" text is not considered a difference in the variables significant enough to trigger an error. (In fact, the last loaded Explanation will "win" -> it is overwritten each time it is encountered for redefined but identical variables)

==Setting and Modifying a variable==

===MODIFY (LST files)===

The MODIFY token is used to set a variable that is accessible in the current SCOPE. (Note: It could be local to the current scope or any ancestor of the current scope... so modifying a global variable always just requires MODIFY)

The format of the token is:
MODIFY:V|W|X|Y=Z|Y=Z
* V is the Variable name for which the value will be modified
** This variable MUST be visible in the current scope. Therefore, it must be either a global variable or a local variable on the current object or its parents.
* W is the MODIFIER to be taken on the variable (e.g. SET)
** There can be multiple actions (more below), but SET will ALWAYS be available for any format.
* X is the value related to the action. If the action is set, the variable will be set to the value in this part of the token.
** Note: The value CAN be a formula. It is possible, for example, to SET a variable to OtherVar+4 ... the system will solve that formula. For legal OPERATORS (e.g. "+") , see below.
* Y is the name of an (optional) ASSOCIATION. For now, PRIORITY (more below) is the only available association.
* Z is the value of the association.

Note: If a PRIORITY is not set it is assumed to be ZERO.

Example: Give a Player Character 2 hands:
MODIFY:Hands|SET|2

===MODIFYOTHER (LST files)===

The MODIFYOTHER token is used to set a variable that is not accessible in the current SCOPE. Beyond what is necessary in MODIFY, this token also requires the "address" of where to go before it runs the modification. Think of it as the ability to remotely place a MODIFY on another object (but revoke that MODIFY if the current object is no longer granted to the PC)

The format of the token is:
MODIFYOTHER:T|U|V|W|X|Y=Z|Y=Z
* T is the FORMAT of the object on which the resulting MODIFY (as defined by V-Z) should occur
* U is the object or GROUPING of objects on which the MODIFY (as defined by V-Z) should occur
** Note that this does not and will not support TYPE.
* V is the Variable name for which the value will be modified
** This variable MUST be visible in the scope of the addressed object. Therefore, it is likely to be a local variable on the remote object or its parents.
** In rare cases, a remote modification of a global variable is useful. It effectively adds to that global variable only if both objects are granted to the PC.
* W is the MODIFIER to be taken on the variable (e.g. SET)
** There can be multiple actions (more below), but SET will ALWAYS be available for any format.
* X is the value related to the action. If the action is set, the variable will be set to the value in this part of the token.
** Note: The value CAN be a formula. It is possible, for example, to SET a variable to OtherVar+4 ... the system will solve that formula. For legal OPERATORS (e.g. "+") , see below.
* Y is the name of an (optional) ASSOCIATION. For now, PRIORITY (more below) is the only available association.
* Z is the value of the association.

Note: If a PRIORITY is not set it is assumed to be ZERO.

Example: Reduce the HandsRequired on all Weapons by 1:
MODIFYOTHER:EQUIPMENT|GROUP=Weapon|HandsRequired|ADD|-1

Note this assumes GROUP:Weapon is in the LST line of every Weapon... PCGen can't guess or derive what a weapon is :)

==Formulas==

SET as a MODIFIER allows the use of a formula for the value. This follows many mathematical systems of using parenthesis - "(" and ")" to be precise - to group (and thus prioritize parts of the calculation).
There are a number of build in OPERATORs (see below). The system can also use functions, which use parenthesis to contain their arguments. For example:
* min(this,that)
Would return the minimum of the two variables "this" and "that".

===Built in Functions===

The system also has a series of built-in functions that work with the NUMBER format:
* abs: calculates the absolute value of the one argument.
* ceil: calculates the next integer that is >= the value of the one argument.
* floor: calculates the next lower integer that is <= the value of the one argument
* if: conditionally performs an operation. The first argument must resolve to a BOOLEAN. If true, the second argument is evaluated; if false, the third argument is evaluated.
* max: calculates the maximum of the provided two or more comma-separated arguments
* min: calculates the minimum of the provided two or more comma-separated arguments
* round: calculates the closest integer to the value of the one argument. Exactly 0.5 is rounded up.
* value: returns the value of the calculation before the current modification was started (no arguments)

Additional functions specifically related to PCGen are available:
* get: This function takes two arguments. The first is a Object type (like "SKILL"), the second is the key of a CDOMObject (like a Skill) (also in quotes)
**Example: get("SKILL","Hide")
* getFact: This function returns the value of a FACT. The first two arguments are much like the two arguments of "get", the third argument is the name of the FACT to be returned

=Legal Values=

==FORMATs==

Currently, the following are built-in formats:
* NUMBER: This is a mathematical value. Note that integer arithmetic is done if possible, so if you have an integer 6 and an integer 3, 6/3 will be an integer 2. If the 6 or 3 is a decimal value (double), then integer arithmetic was not possible and thus rounding may occur.
* STRING: A String
* BOOLEAN: A True/False value
* ORDEREDPAIR: An ordered pair of numbers. This could be an X,Y point (or in a game system more like a FACE)
* DICE: A value that takes the form AdB+C. A is the number of rolls of the die, B is the number of sides on the die, and C is the value to be added afterwords
* ALIGNMENT: An alignment object (None is default typically)

==OPERATORs==

For NUMBER, the following modifiers are available:
* +: performs addition
* -: performs subtraction (or is the unary minus operator to make a value negative)
* *: performs multiplication
* /: performs division
* %: performs a remainder function
* ^: performs an exponential calculation
* ==: Checks for equality (NOTE: Returns a BOOLEAN, not a NUMBER)
* !=: Checks for inequality (NOTE: Returns a BOOLEAN, not a NUMBER)
* >: Checks for greater than (NOTE: Returns a BOOLEAN, not a NUMBER)
* <: Checks for less than (NOTE: Returns a BOOLEAN, not a NUMBER)
* >=: Checks for greater than or equal to (NOTE: Returns a BOOLEAN, not a NUMBER)
* <=: Checks for less than or equal to (NOTE: Returns a BOOLEAN, not a NUMBER)

For BOOLEAN, the following modifiers are available:
* ==: Checks for equality
* !=: Checks for inequality
* &&: Performs a logical AND
* ||: Performs a logical OR
* !: Negates the value

For other formats, the following operators are always available:
* ==: Checks for equality (NOTE: Returns a BOOLEAN, not the compared format)
* !=: Checks for inequality (NOTE: Returns a BOOLEAN, not the compared format)

==MODIFIERs==

For NUMBER, the following modifiers are available:
* SET: This sets the variable to the value provided in the "X" parameter
* ADD: This adds the current value of the variable to the value provided in the "X" parameter
* MAX: This takes the maximum value of the current value of the variable and the value provided in the "X" parameter (i.e. min(current value, "X"))
* MIN: This takes the minimum value of the current value of the variable and the value provided in the "X" parameter (i.e. max(current value, "X"))
* MULTIPLY: This multiplies the current value of the variable and the value provided in the "X" parameter
* DIVIDE: This divides the current value of the variable by the value provided in the "X" parameter

For other Formats, the SET modifier will always be available

==GROUPINGs==

At present, the second argument of MODIFYOTHER supports 3 possible values:
* ALL
** This means the MODIFYOTHER will impact ALL objects of that type. This is useful for setting a general default for that value (e.g. you could default "HandsRequired" on weapons to 1)
* GROUP=X
** This is set by the GROUP token in LST data
* A specific object KEY

More will be added over time.

==SCOPEs==

The following are the legal scopes (not including GLOBAL):
* EQUIPMENT: This is a variable local to equipment
** EQUIPMENT.PART: This is a variable local to an equipment PART (or in older terms, an Equipment HEAD). Note that due to double sided weapons, Damage, CritMult and other items are generally on an equipment PART, not on the Equipment itself. Note also that this is a SUBSCOPE of the EQUIPMENT scope (so all variables in the EQUIPMENT scope can also be seen in the EQUIPMENT.PART scope)
* SAVE: This is a variable local to Save (or if you prefer, Check)
* SIZE: This is a variable local to the Size of a PC
* SKILL: This is a variable local to a Skill
* STAT: This is a variable local to a Stat

More will be added over time.

DYNAMIC can also be used to create a Scope and Object Type (see below)

=Examples=

==Understanding SubScope in practice==

To understand how local variables work in SubScopes, consider the following (note this is not all the variables we will use but a critical set to define the scope):
GLOBAL:NUMBER=Hands
LOCAL:EQUIPMENT|NUMBER=HandsRequired
LOCAL:EQUIPMENT|BOOLEAN=Penalized
LOCAL:EQUIPMENT.PART|NUMBER=CritMult

The Equipment part is what the traditional system called a "head" (so a double headed axe has two "parts" in the new system - this was done since in some game systems, an item could have more than 2)

To understand how variables are available and how they get modified consider this:

Inside of a piece of equipment it could do something like:
MODIFY:Penalized|SET|HandsRequired>Hands

This would be "true" if HandsRequired on the Equipment were more than the Hands on the PC. The "Hands" variable is Global, so it is available anywhere. A Template of "Extra Hands" could do something like:
MODIFY:Hands|ADD|2
... and that adds to the Global variable "Hands".

Now consider an Equipment Modifier that was something like "Lighter Than Normal". Assume the game benefit was one less hand is required. This would look like:
Lighter Than Normal MODIFY:HandsRequired|ADD|-1
(This ignores for the moment any situation like "can't be reduced to below one".)

Note that the EquipmentModifier falls into EQUIPMENT.PART, so that it has access to the HandsRequired variable from the EQUIPMENT scope and can modify it. Note that this change could then impact the result of the BOOLEAN variable Penalized, since HandsRequired changed. Note also that "HandsRequired", when evaluated anywhere in that Equipment is now 1 less. Even if another EquipmentModifier evaluates HandsRequired, it is analyzing the variable from its parent scope, so that value on a variable from EQUIPMENT is the same in every EquipmentModifier (in the EQUIPMENT.PART scope) of that piece of Equipment.

==Understanding SubScope on Equipment==

Since variables like CritMult and Damage would be on an Equipment "part" it is important to understand how to get access to that "part" from the LST code. If a single-headed weapon wanted a larger CritMult, it would be silly to have to add a Dummy EquipmentModifier just to modify the CritMult on the part. (Much of the point of the new system is to make things more direct)

There is a token for Equipment called PART. This effectively takes 2 arguments: A number (today 1 for the primary head, 2 for the secondary head) and a full token otherwise valid on a plain object. MODIFY and MODIFYOTHER will both work in that situation, so for a piece of Equipment to set its own CritMult to 3 on its primary (and perhaps only) head, it would do:
PART:1|MODIFY:CritMult|SET|3

Note since the MODIFY is a "real" token call it uses ":" after the MODIFY which makes PART look slightly different to most tokens which use | as an internal separator. Since PART is effectively calling a "real" token, we need to use the inner ":" in order to have it pass through the same code/parsing system.

==Understanding SubScopes in relation to MODIFYOTHER==

* Note Jan 29 2018: There is a possibility of a solution for this issue that would allow MODIFYOTHER to do direct addressing of sub-objects under certain conditions

Normally MODIFYOTHER allows you to "address" another scope. For example:
MODIFYOTHER:EQUIPMENT|Bastard Sword|HandsRequired|ADD|-1

However, since items like Damage and CritMult are actually on the EQUIPMENT.PART, that is different. If you consider how you would have to "address" the first head on "Bastard Sword", you would need something like:
SOMEWEIRDTOKEN:EQUIPMENT|Bastard Sword|PART|1|CritMult|ADD|1

Note that this requires both a primary and secondary address. No token like this exists (at the moment). To alter items in a SubScope, you need to pass them down to the SubScope. An attempt to modify it at the Equipment level, such as:
MyAbility MODIFYOTHER:EQUIPMENT|ALL|CritMult|ADD|1
... will fail (at LST load) because CritMult was on EQUIPMENT.PART, so it is not visible to the EQUIPMENT scope. Said another way, you can't universally modify all EQUIPMENT.PART variables by attempting to use that variable at a higher scope.

A more appropriate method (since this is relevant to a Feat that might alter CritMult) is to add another variable at the EQUIPMENT level:
LOCAL:EQUIPMENT|NUMBER=CritMultAdder
If all the heads then get
MODIFY:CritMult|ADD|CritMultAdder
... you can have the Feat do a MODIFYOTHER to alter CritMultAdder and the MODIFY will "pull" that into each PART:
SomeFeat MODIFYOTHER:EQUIPMENT|ALL|CritMultAdd|ADD|1
So the data can be set up to only require one modification from a Feat and each Equipment Part can pull that modification down into the part. (A tangential note for those objecting that the known modifiers of CritMult select a specific weapon type: Yep, got it. That's not possible yet, so not documented yet. Suspend disbelief on the examples - Imagine a more powerful Feat for now)

==Understanding PRIORITY and processing of MODIFY and MODIFYOTHER==

When a PlayerCharacter has multiple items that attempt to modify a variable, they are sorted by two systems:
* First, they are sorted by their user priority. This is provided in the PRIORITY=Z association. Lower PRIORITY will be processed first.
* Second, they are sorted by their inherent priority. This is a built-in system that approximates mathematical priority rules. It ensures, for example, that a SET will occur before ADD if they both have a matching user priority.

Example:
Assume we had the following items:
MODIFY:Hands|MULTIPLY|2|PRIORITY=100
MODIFY:Hands|SET|2|PRIORITY=50
MODIFY:Hands|ADD|1|PRIORITY=50

The first thing is that we can tell from the PRIORITY items that the SET and ADD will both occur BEFORE the multiply (because 50 < 100). For the SET and ADD, we would need to know the inherent priority (For what it's worth, SET is 0, ADD is 3, MULTIPLY and DIVIDE are 1 and 2 since they are higher priority than ADD in traditional math). This means the SET will happen first. So the result is Hands is SET to 2, then ADD 1 to get 3, then MULTIPLY by 2 to get 6.

By controlling the PRIORITY, the data team can reorder any calculation and perform much more complicated calculations than was possible with BONUS (where movement, for example, had multiple different BONUS tokens to try to do adding before and after a multiply). This is much the same as using parenthesis in a formula in normal math, but this allows you trigger any required ordering even if the MODIFY statements are in different objects.

==Using the previous value in a more complex calculation==

Take a modification that, for example, wishes to perform a calculation such as: "Reduce the value by 1, but to no less than 1". We could write this as two MODIFY statements, but that is probably undesirable for a few reasons:
* If the book states it as one sentence, it would be preferable to write it as one MODIFY
* It makes the calculation a bit harder to follow as to what is going on
* If the items are different PRIORITY, there is a risk of another dataset attempting to (or accidentally) putting something in between those two steps, resulting in an incorrect calculation.

Therefore, we need a method of drawing on the current value in a formula. To do that we use the value() function. The calculation above then becomes:
max(value()-1,1)
...and we can use it in a MODIFY as such:
MODIFY:HandsRequired|SET|max(value()-1,1)

Note that we are using SET here - if a formula is used, it is likely to be best done as a SET, since that will be much more clear than calculating a formula and then immediately applying another MODIFICATION. Note that some modifications may also prohibit a formula depending on their underlying behavior.

=Global Modifier File=

There is a new file type that is defined in the PCC files with GLOBALMODIFIER.

This file allows for a centralized (and clear to the data user) location for global modifications (don't hide things on stats or elsewhere anymore). This supports MODIFY for global variables (if you want to start all PCs with 2 hands for example) or MODIFYOTHER for local variables.

==GLOBALMODIFIER (PCC File)==

Format:
GLOBALMODIFIER:x
* x is the file to be loaded as a GLOBALMODIFIER file
* Limitations: It does not support PRExxx or INCLUDE/EXCLUDE.

=Advanced Topics=

==Dynamic Objects and Scope==

This set of features allows the data to supplement the defined SCOPEs with new object types not originally comprehended in PCGen. Within a Dynamic Scope, the data can produce objects.

Warning: Attempts to define a SCOPE that overlaps with existing objects (e.g. LANGUAGE) will not produce a warning today but will get you in trouble long term. It won't work in the way you would like it to work (it won't attach a SCOPE to that object type), so just avoid those overlapping names. Basically if you can CHOOSE it, or use it with FACT, don't DYMAMICSCOPE it.

===DYNAMICSCOPE (DATACONTROL LST)===

The DYNAMICSCOPE token (used in files referred to by the DATACONTROL: token in PCC files) can define a Dynamic Scope.

DYNAMICSCOPE:x

*x is the new scope
**Any argument to DYNAMICSCOPE becomes a legal "scope" in LOCAL: in the variable definition file
**Limit of one new scope per line. (No delimiter on this token)
*Like other LST tokens, this is case insensitive, but usage in later tokens is always capitalized, so I suspect the data standard should be ALL CAPS

===DYNAMIC (PCC File)===

In order to create objects within the defined DYNAMICSCOPE, DYNAMIC: becomes a new token legal in PCC files. It's format is:

DYNAMIC:x

* x is the file just as in tokens like DEITY or DOMAIN
* INCLUDE/EXCLUDE on the line are are legal.

Within the Dynamic file, the Scope of the new objects being created MUST appear as a prefix token on the line. For example, if there was a DYNAMICSCOPE:VISION, then the following would be legal in a DYNAMIC file:
VISION:Darkvision
VISION:Low-Light Vision

* The "Token Name" (what appears before the ':') is the DYNAMICSCOPE name.
* These are created as basically hollow, simple objects.
* These objects CAN contain variables.
(It is the intent to allow these at some point to also have MODIFY* tokens, but that is not currently supported)

===GRANT (LST files)===

A Dynamic object MUST be granted in order to have its local variables modified or to have its modifiers have an impact (just like any other object)

GRANT:x|y

* x is a DYNAMICSCOPE
* y is the name of the dynamic object.

===Export===

Dynamic items can be exported in Freemarker using the

<#list pc.dynamic.x as y>

* x is the name of the DYNAMICSCOPE
* y is the local variable within the #list that the output team wants to use to access the dynamic object
* It is likely for ease of use by the output team, x and y will be identical

For a complete example using output, see below

===Example===

DATACONTROL: file:
DYNAMICSCOPE:VISION

DYNAMIC: file:
VISION:Normal
VISION:Darkvision
VISION:Low-Light Vision

VARIABLE: File:
LOCAL:VISION|NUMBER=Range

GLOBALMODIFIERFILE:
MODIFYOTHER:VISION|ALL|Range|Set|60

Sets a "default" range for any VISION, to avoid setting on each VISION object

RACE LST file:
Human <> GRANT:VISION|Normal

Export:

<#list pc.dynamic.vision as vision>
${vision.name} ${vision.val.range}
</#list>

(this ignores converting the range to local units and all that, but you get the idea)

==ARRAY Format==

In addition to the base formats, there is an ARRAY[x] format:
ARRAY[x]
* x is an existing valid Format
** x CANNOT be ARRAY (multi-dimensional arrays not supported
** Just to be precise, yes DYNAMIC formats are legal

(Note: This may get renamed - we need to decide on a few things for how this will work vs other types of collections)

===Modifiers===

There are two valid MODIFIERs for ARRAY:
* ADD: This adds a value to the ARRAY
** Mathematically, ARRAY acts as an ordered set of objects. Therefore, if you add an item to an array more than once it is ignored.
* SET: This sets the contents of the ARRAY

==Custom Functions==

Within certain game systems, there are calculations that are likely to be repeated. In order to simplify the calculation of these items, there is an ability to create custom functions.

A function can have zero or more arguments. The number is defined by what appears in the VALUE token (see below).

Note that the function actually has to be *used in the data* (not just defined) for most errors to be caught (since the system can't guess at overall context before a function is used and it would be possible to write a function that would work in more than one FORMAT).

===Function (DATACONTROL LST)===

FUNCTION:x
* This token must appear as the first token on a line in a DATACONTROL file.
* x is the name of the function. This name must starts with a letter, e.g. A-Z, additional legal characters are 0-9 and _ (none of those additional legal characters as the first character)
** x must not contain spaces, no other special characters.
** Function names are case insensitive (as many other things in LST files)

A Function MUST also contain a VALUE, which defines how the function is calculated.

If a FUNCTION appears more than once, the other characteristics (VALUE) must be identical.

===Value (DATACONTROL LST)===

VALUE:x
* Must appear as an additional token on the line of a FUNCTION: in the data control file
* x is a valid formula.
** This means it must have valid variable names, valid function names, matching parenthesis, etc.

In addition to all of the build-in functions (e.g. if, ceil, round), two additional items can be used:
* the arg(n) function (see below).
* Any previously defined FUNCTION. This MUST appear in the file before the current Function or in a file processed before the current file.

===arg (Function)===

The arg function is a "local" function to the VALUE: part of a FUNCTION (it can not generally be used in LST files). The arg function takes one argument. It MUST be a Integer >= 0.

arg(x)
* x is an integer number (zero-indexed)

When arg(x) is used in value, the function pulls from the arguments that were provided to the original function in the data.

===Using a Function===

When a function is used in LST data, it is called by the name provided in the FUNCTION token. It requires a certain number of arguments. This exactly matches the integer one greater than the highest number of the arg(n) function provided in the VALUE part of a FUNCTION (In computer science terms, the arg(n) function is zero-indexed). The provided arguments can be any legal formula, so:

d20Mod(INT)
d20Mod(INT+4)

...are both perfectly legal.

===Example===

The modification calculation in most d20 games is fairly easy to calculate, but is repeated very often. It basically takes (ability score - 10)/2.

Here is how we would define a new function d20Mod in the DATACONTROL file:
FUNCTION:d20Mod VALUE:floor((arg(0)-10)/2)

This would then be used in LST data as:

d20Mod(n)

The system will catch both of these as errors:

d20Mod()
d20Mod(14,5)

These have too few or too many arguments, respectively. It would also catch:

d20Mod("mystring")

...as an error (wrong format - requires a Number, found a String).

The n is substituted where "arg(0)" appears in the "VALUE"... so a statmod would be as easy as:

d20Mod(INT)

or some such... Direct values can also be used, e.g.:

d20Mod(10)

...would return 0.

==Performance Considerations==

It is possible to write two identical modifiers that perform the same net calculation on a PC. For example:
MODIFY:Age|ADD|2
MODIFY:Age|SET|value()+2

...perform the same calculation (adding 2 to Age).

Why have ADD at all? Answer: These are NOT AT ALL equivalent in memory use or speed/performance.

The ADD (Since it's adding an integer) occupies approximately 40 bytes of memory and is an extremely rapid calculation: If it took 200 nanoseconds I'd be surprised. This is because ADD is using a number. If it was a formula, even 1+2, it would load the formula parser. This special case on constants allows the modification system to modify a value without loading a much larger infrastructure, and this is valuable as a large majority of our calculations are simple modifications of values.

The SET shown above (since it has an operator) loads the formula system, and thus may occupy 500 (or more) bytes of memory (>10x), so it could take 100 times as long to process as the ADD (it also took longer during LST load).

Thus: When possible the data standards should be written to use numeric modifiers and no operator. (Think "static" modifiers ... that only use numbers) rather than a formula.

==Lookup and Tables==

For some situations, it makes more sense to have a lookup table rather than attempting to have a set of tokens or calculations perform processing. This also allows for much cleaner translation from books when the books are using tables to organize information.

The Table file format is designed to allow you to use a spreadsheet program to modify the tables and export the table in CSV format. While we don't strictly follow full CSV rules, as long as you avoid embedded quotes and embedded return carriage/line feed, it should be safe.

More than one table is allowed per file (to avoid sprawl and help simplify modification/management of tables).

===TABLE (PCC File)===

TABLE:x
* x is the file to be loaded as a TABLE file
* Limitations: It does not support PRExxx or INCLUDE/EXCLUDE.

====Table LST file format====

File formatting considerations:
* Trailing commas will not impact any TABLE, and will be ignored
* Blank lines will be ignored. This includes lines with commas but without content. (allows tables to be separated by blank lines or lines of all commas)
* Attempts to use embedded line breaks or embedded quotes may or may not be supported by the parsing system, but certainly aren't supported for purposes of PCGen.
* Lines that have the first cell starting with "#" are considered comment lines and will be ignored. This will likely need to include if the first cell is escaped in quotes, just for protection from any tools that quote by default.
* Since the CSV format ignores leading/trailing spaces, one can easily have a spaced out version that is a table in a text editor if folks don't want to edit in a spreadsheet. (Having someone write a "PrettyTable" ... a trivial perl or python program to do that for the data team seems fairly easy)

A TABLE starts with STARTTABLE:
STARTTABLE:x
* x is the name of the Table. Most characters are allowed, avoiding quotes is advisable.
* Allowing Trailing commas allows the STARTTABLE lines to have blank cells where the rest are the table contents... we don't want to complain on minor things that may tools will do.

If a STARTTABLE is encountered when another Table is active, an LST load error will occur.

A TABLE ends with ENDTABLE:
ENDTABLE:x
* x is the name of the Table. Most characters are allowed, avoiding quotes is advisable.
* Allowing Trailing commas allows the ENDTABLE lines to have blank cells where the rest are the table contents... we don't want to complain on minor things that may tools will do.

If an ENDTABLE is encountered without a STARTTABLE, an LST load error will occur.

A Table must have a minimum of 3 rows, NOT counting the STARTTABLE and ENDTABLE tokens.

The First row:
x,x
* x is the column name. These are always the first line of the table after STARTTABLE:

Any column which has data MUST have a name.

The Second row:
y,y
* y is the format for the column. Any column that was named must have a FORMAT.

Additional rows:
z,z
* z represents contents of the table. These must be in the FORMAT provided for the appropriate column.

====Example====

STARTTABLE:Carrying Capacity,
Strength,Capacity
NUMBER,NUMBER
1,10
2,20
...
29,1400
ENDTABLE:Carrying Capacity,

===TABLE[x] Format===

When a TABLE is created, it implicitly picks up a FORMAT based on the FORMAT of the first column of the Table.
Unlike basic FORMATs shown above, TABLE has a SUBFORMAT (in brackets).

TABLE[x]
* x is the SUB-FORMAT of the TABLE (this is the format of the first column of the Table)
** x must be an otherwise valid FORMAT, and it is advised to avoid any FORMAT that has a SUB-FORMAT
*** This limitation may be inconsistently enforced. It certainly is prohibited to create a TABLE[TABLE[x]], but other situations the behavior may not be prohibited by the code (but the behavior is also not guaranteed)

===COLUMN[x] Format===

When a Column needs to be referred to in the data, it has a special format as well:

Unlike basic FORMATs shown above, COLUMN has a SUBFORMAT (in brackets).
COLUMN[x]
* x is the SUB-FORMAT of the COLUMN (this is the format of the data that appears in that column in a Table)
** x must be an otherwise valid FORMAT, and it is advised to avoid any FORMAT that has a SUB-FORMAT
*** This limitation may be inconsistently enforced. Such behavior may not be prohibited by the code (but avoiding bad behavior is also not guaranteed in a situation where embedded brackets occur)

===Using Tables===

With MODIFY, a TABLE[x] variable doesn't look any different. It's still:
MODIFY:TableNameVar|SET|"SomeTable"

"SomeTable" is still a string to a naive reader, but what the system will do at that point is make sure that SomeTable can actually be interpreted as a TABLE[x]... rather than just treating it as a String. Similar for column names when they are encountered (see below).

In that way, the sub variable will allow multiple tables to be swapped in, AS LONG AS they are the right format. If the format is not compatible, then all bets are off and you'll get an error.

===lookup() Function===

The major consideration is how to do the lookup in data. We can borrow some inspiration from things like Excel and Google Docs:

lookup(X,Y,Z)

* X is a table. This must resolve in the formula system to a valid table. For now, a get(...) function may be required.
* Y is the lookup value in the table. It must match the format of the first column in the table. At this time, it does an EXACT match.
* Z is the target column. This must resolve in the formula system to a valid table column. It must appear in the table named by the contents of the first argument of lookup.

Example: Max load calculation would be something like:
lookup("Carrying Capacity",floor(StrScore),"Capacity")*SizeMult
We have to do the floor due to the exact name of the lookup

Note: The format of both TABLE "Carrying Capacity" and COLUMN "Capacity" can be derived by PCGen internally and thus are no longer required to have a get (current as of Jan 30, 2018)

Note that this function allows some runtime errors, but catches a lot of possible issues. It is still possible to do a lookup on a Table that doesn't contain a specific column of the given name or format, simply because those items can be variables resolved at runtime. For example, if the third variable is COLUMN[NUMBER], we can check at load that the TABLEFORMAT has columns of FORMAT=NUMBER, but we can't guarantee the variable will resolve to a name actually in that table... that will have to wait for a runtime error. That's life, but it does allow us to know the formats at load time, so we do get a lot of error checking in the context of the usage, if not the exact table and column names.

Note you can do some really dynamic behaviors to have folks override game mode behaviors. For example, one neat item would be that we could alter a query for dice steps to extract the table name into the Global Modifier file:
MODIFY:DiceStepTable|SET|"Dice Step"
lookup(get("TABLE[NUMBER]",DiceStepTable),BaseDamage,get("COLUMN[NUMBER]",lookup("Step Column",CurrentSize-BaseSize,"Name")))

Note: In both cases here, the "get" is shown for completeness. In the case of DiceStepTable - it MAY be required or prohibited - it depends on what the Format is of the "DiceStepTable" variable. If it's TABLE, then the get is not necessary (and is actually prohibited). The example shown above assumes DiceStepTable is a String. The better design would be for it to be a TABLE (specifically TABLE[NUMBER]). For the "get" after the lookup, that is required - the lookup value will return a STRING, and as such, will needs to be converted to a COLUMN.

Now, if someone needs different dice steps for some reason... they can override the DiceStepTable variable and it will look up in a different table... so expansions could truly be expansions and not have to reach back into core PCC files in order to change key behaviors.

Consider also that spell tables can be shared across classes, or if a subclass alters the default, just create a new table rather than having to BONUS/MODIFY all the numbers in a table with adding and subtracting...

==To be completed==
* dropIntoContext
* Channels

=Material Changes=

==lookup function simplification==

Effective January 30, 2018, tables and columns can be referred to directly in lookup(). This is actually a "broad" change to how strings are interpreted. The system - when possible - fully asserts a FORMAT, and first attempts to convert the given String per the rules of that FORMAT. This also means an assignment of an ALIGNMENT, by key, will not require a "get":
MODIFY:Alignment|SET|"LE"
...will be fully legal. (This assumes Alignment is FORMAT: of ALIGNMENT)

Archetype Swapping Concerns

2018-03-08T23:30:55Z

LegacyKing:

Class Archetypes - I think you covered the main class feature x is replaced by y nicely, however, in some instances a Class Feature is not replaced, but a portion of the feature is negated in order to gain another new feature.

Example:

Rogue gains Sneak Attack (Class Feature), which has level dependent gains.

Every odd level, the rogue gains an additional +1d6 to the Sneak Attack Damage.

Broken down:
1 = 1d6
3 = 2d6
5 = 3d6

However, we encounter this:

1 = 1d6
3 = New Class Feature
5 = 2d6

We need to manage several things:

1) When a new bonus is applied (We cannot remove/negate a bonus until the correct level is reached)

2) We cannot grant new features until the minimum level has been reached

3) And in odd cases, when features are granted, there can be level dependent bonuses on those as well...

Archetype Swapping Concerns

2018-03-08T22:59:28Z

LegacyKing: Created page with " Class Archetypes - I think you covered the main class feature x is replaced by y nicely, however, in some instances a Class Feature is not replaced, but a portion of the feat..."

Class Archetypes - I think you covered the main class feature x is replaced by y nicely, however, in some instances a Class Feature is not replaced, but a portion of the feature is negated in order to gain another new feature.

Example:

Rogue gains Sneak Attack (Class Feature), which has level dependent gains.

Every odd level, the rogue gains an additional +1d6 to the Sneak Attack Damage.

Broken down:
1 = 1d6
3 = 2d6
5 = 3d6

However, we encounter this:

1 = 1d6
3 = New Class Feature
5 = 2d6

We need to manage several things:

1) When a new bonus is applied (We cannot remove/negate a bonus until the correct level is reached)
2) We cannot grant new features until the minimum level has been reached

Race Racial Trait Swapping

2018-03-08T22:55:18Z

LegacyKing: Created page with "Concern: Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern: 1) "Race Package" where a race is granted specific non-default traits,..."

Concern:

Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern:

1) "Race Package" where a race is granted specific non-default traits, and/or a choice between two or more additional choices

2) Racial Trait that is chosen by the player actually removes 2 or more existing default traits

Data Team Discussions for Replacements

2018-03-08T22:53:31Z

LegacyKing: Created page with " Archetype Swapping Concerns Race Racial Trait Swapping"

[[Archetype Swapping Concerns]]

[[Race Racial Trait Swapping]]

6.08 Documentation

2018-03-08T22:52:54Z

LegacyKing:

==New Documentation Repository for 6.08==

[[Setting up the new Formula System]] - How to set up and use variables (MODIFY, MODIFYOTHER, DYMAMIC, GRANT, FUNCTION, VALUE)

[[Lookup & TABLE 6.08]] - Lookup is used with Table

[[INFO & INFOVARS 6.08]] - Dynamic Text Display (Replaces DESC, BENEFIT, ASPECT, QUALITY, SPROP)

[[DICE in Formula 6.08]] - New System for handling Dice Formats

[[CODE CONTROLS]] - Disable specific tags and replaces it with a FORMULA Version (For output sheets integration)

[[Replacing Archetype Controls]] - Some initial thoughts on how to use the formula system to make Archetypes easier

[[OUTPUT for 6.08]] - Formats for output into Freemarker

[[Data Team Discussions for Replacements]]

FAQ and Help

2018-02-26T00:12:23Z

LegacyKing: /* What systems does PCGen support today? */

This is just some tips to help along. It'll be a repository of Frequently Asked Questions and Help Tips that we've encountered a lot.

== What is PCGen? ==
PCGen is a JAVA Program that uses custom 'text' files (*.pcc and *.lst) to emulate books from table-top role-playing games, like Dungeons & Dragons 3rd edition, to help create and maintain system rules-legal characters for that game system. It allows you to print out character sheets, or export them into various formats for later use - such as a basic text sheet, xml for various forum play and software systems, htm for web browser enabled devices and pdf. PCGen is built to support the most popular d20 systems and has plans for future expansion into non-d20 based systems.

== What systems does PCGen support today? ==
Today PCGen (version 6.2) supports Dungeons and Dragons by Wizard of the Coast - the specific versions supported directly are: 3rd edition (Known as SRD), 3.5 edition (RSRD), d20 Modern (MSRD). Due to license issues, the program can support 4th edition and the upcoming 5th edition (known as D&D Next) but we cannot supply any pre-made books. Those will require custom sets that you can make yourself.

Our list of supported d20 systems with pre-made books:
* D&D 5.0 edition (Listed as SRD5)
* D&D 3.0 edition (Listed as SRD - System Resource Documents)
* D&D 3.5 edition (Listed as RSRD - Revised System Resource Documents)
* D&D Modern Edition (Listed as MSRD - Modern System Resource Documents)
* Deadlands by Pinnacle Entertainment
* Fantasy Craft by Crafty Games (Crafty Games is hosting the full core rule book, we only have a level 4 demo set)
* Gaslight 1st edition by Battlefield Press
* Legends of Excalibur
* Pathfinder by Paizo Publishing
* Sidewinder
* Spycraft
* Xcrawl
* Sagaborn (d20)
* Killshot (Non-d20 system) by Broken Ruler Games (This is ready to play but needs a Character Sheet to display)
* Starfinder
* Darwin's World II

Non-d20 Systems we're building support for:

* Cyberpunk
* Shadowrun

== Using Pathfinder in PCGen ==
* Unchained Classes - Q&A:
** '''QUESTION''': How can I created an Unchained x class?
** '''ANSWER''': First, you need to make sure you are loading the correct book(s). You will need to load ''Pathfinder Unchained'' to have access to the first four Unchained variant classes - Barbarian, Monk, Rogue, and Summoner. Select the base class, Rogue for Unchained Rogue as an example. Once you add the first level, go to the Feats & Abilities tab, under Class Features, there should be a CLASS SELECTION group. Select the Unchained Version from there. Congratulations, you now have an Unchained version of the Class.
** '''LIMITATIONS''': Warning - Due to how PCGen processes SPELL LISTS, an Unchained Summoner will require you to SAVE and RELOAD to have the correct spells populate your spell list.
** QUESTION: I'm very curious (from both a user's viewpoint and that of a designer) as to why you made the Unchained classes as options within the class (when the source is selected) instead of a separate class in their own right. I actually found that very confusing when making an unchained class as I couldn't select it from the class list as one would usually do when making a character. It was only when I went back to the summary screen after selecting the class that I realized I could make the Unchained version. That's a design decision that needs to be deliberated upon and possibly altered because as it stands, it is highly confusing and may lead a lot of people to believe that you can't make an Unchained class at all in PCGen.
** ANSWER: Since that was my decision, I'll be happy to explain the reasoning and how I arrived at that conclusion. If you do a comparison between the normal classes and the unchained versions, you will see (in most cases) the only differences was the class features - Monk had a HD boost, Summoner has a Spell List change, Barbarian only changes features, and Rogue added some new features. It seemed more economical to re-use the base framework which 90% of the classes were built upon. Reduce duplication in code (Each class loaded requires some memory, whereas the method I opted did not increase memory, merely which features to use). Unchained classes comes across as more a variant. Plus, you cannot have an unchained version and regular version of the class. Programming in "Cannot take this" does increase cpu cycles and additional code lines. Add in the fact they were treated just as the regular version in terms of meeting prerequisites for prestige classes, feats, and archetypes, etc. Looking at it big picture, it made more sense to simply use the base class and treat the unchained variant as a super archetype - swap out abilities. They were more the base class then not. The chance of breaking support was higher if they were coded separately - anything using the code classlevel("Summoner") would fail for an "Unchained Summoner" as an example, SERVESAS only does prexxx support. Reviewing everything related to the class - favored classes, archetype support, feats and the data hacks was a bit more time consuming. Plus, it gave me the excuse to test out a function of the program to try and support a prestige class that grants class features from other classes, which we could not support in the past. To combat the confusion, I did include the Summary TO DO to prompt the user to choose which version they want to use; most users use the summary screen to add classes to the character, which would mean they see the prompt right off. Under the hood, it defaults to the base version in case they never make that selection. An important fact for the Summoner - so it still gains spells. If it helps to know, I went back and forth several times, actually coding them up initially as classes. But the lack of time on my part limited what I was willing to undertake, so choosing the path that had the least chance to break any particular build was what I ended up doing. As I progressed, I learned a new tidbit that swung the pendulum toward the other method. I might have chosen differently knowing what I know today. Right or wrong, it is a bit late to change the decision (6.06.00 is now released). With our focus for the 6.08 dev cycle to rip out the JEP reliance tags - anything that starts with BONUS:x, anything that is touched by BONUS, such as LEGS, FACE, REACH, WEAPONPROF, etc. Implementing new support for global and local variable numbers, Booleans, strings and orderedpairs. Rip out every text output tag and replace it with INFO/INFOVARS. Redesign the output sheets to (1) use the freemarker template code properly, and (2) switch to grabbing the new output via fact, info and value. The end goal is a more lean and efficient code base and data processing. Hope that helps clear up the decision making process that led to variant vs. class. If you have any other questions, comments or otherwise, feel free to reach out to me. --Andrew Maitland (Content Silverback - PCGen Board of Director's)
** Reply back: Thanks for the explanation. Now I understand the process behind the decision a lot more. Might be something to add to the FAQs because other people may also get confused and I admittedly found the Unchained version by accident.

* Pathfinder vs Pathfinder Society:
** QUESTION: What is the difference between these and why should I care?
** ANSWER: Pathfinder Society is an actual real world international organization which publishes official rules of play for gamemasters and players alike. The games are run using official modules with completion items given out, special sheets to track rewards and of course a very different XP progression, which is capped well before 20th level. As mentioned before they publish rules each year to tell their members what is legal to use in their games. In essence Pathfinder Society (abbreviated PFS) is a structured event setting which determines what is legal in their games, allowing players from all over the world to have the same experiences and options. Many feats, spells, equipment and class options are restricted in the Pathfinder Society games. PCGen supports the various seasons of play as best we can. Many false bugs are raised due to people mistakenly thinking their favorite options are not working. Rule of thumb, unless you play in this actual society, do not use their rules.

== How Customizable is PCGen? ==
PCGen is designed with user customizations in mind. For the Books Side, we are looking to re-include an In-built LST Editor in the program for version 6.4.0. LST files are the main text files for holding the information that PCGen (JAVA Program) can read and execute. LST Files are plain text programing using a customized Language that is designed towards simple premise of Human-Readable and easily used.

PCGen has several methods to impart how to create your own custom files. First, we supply a sample folder including a full set of pcc and lst files for you to get started. We have extensive documentation in the program, and maintained on our website. Andrew Maitland has made several youtube videos explaining how to craft the files, and the common mistakes to avoid. Finally, we offer online support via our Yahoo Groups and direct help from our Support Desk Monkey - Help@PCGen.Org.

== Is there support for issues and recommendations? ==
Yes, PCGen is a volunteer project run by monkeys and humans. We all know monkeys are a laugh, and humans are fallible. Thus, we have a Ticket Support system that is monitored by the various projects that go towards supporting PCGen. Our ticket support system is called 'JIRA' and anyone can log into the system after creating an account, and report a problem "Bug" or make recommendations for improvements (Feature Requests). The system is located at http://jira.pcgen.org.

Wait, what do all those projects visible mean? I'm totally confused?!!?!
* Data - This is the Books. Chances are if it's incorrect the logical issue would be this project. Bug is something broken; Feature is new things to be added.
* Code - This is the heart of PCGen and encompasses the JAVA involved. They also handle the User Interface (UI for short).
* Docs - This is the Documentation that comes with PCGen. Bugs are typographical errors, or formatting problems. Features would be adding new "classes" or "how-to" to explain using PCGen in new ways.
* OS - This is the output sheets or the final product you see. This encompasses the Summary bottom Pane, the Preview Sheets found on "Character" tab of the program, and all of the export methods.
* Admin - This is non-pcgen issues, like the Website has mistakes.
* Support - This is the catch-all "Help, I'm lost and need guidance". When the program is causing issues, or you cannot figure out something, this is a good place to start.

What if I mess up and place it in the wrong area?
* Fear not, our Jira is monitored by experienced project volunteers, and can easily move your issue to the correct location at any time.

How should I submit an issue?
* Details are the key point. In order to address any issue we need facts. Please include the following in all reports:
** Summary of the issue (Single sentence to briefly give an idea of the issue)
** Version of PCGen (In most cases this is a requirement)
** Data You are loading (You can submit a character file (*.pcg) to the Ticket and that will help speed things along
** Description - What is wrong in your own words, and what is the correct result. Cite a source book if available. Since a person needs to verify the issue before making corrections.
** Environment - Your operating system, Java version and anything else you think will help us.

== Trouble Shooting Problems ==

===Mouse Over Issues for some users===
Solution: run Command Line, navigate to your PCGen installed files "cd c:\the\path\to\pcgen" and type in:
java "-Dsun.java2d.d3d=false" -jar .\pcgen.jar

===High Resolution Display===
I was able to workaround this issue by going into the compatibility properties of the PCGen shortcut and setting the "Override high DPI scaling behavior" to System. This was tested on Windows 10.

=== Java 7 for version 5.17.11 or lower ===
PCGen versions prior to 5.17.11 (including the current production version, 5.16.4) are not compatible with Java 7. This is now the default version Java installed for most system types. Open JDK 6 on Linux exhibits the same problems and the same fix applies.

==== Symptoms ====

When you start PCGen, all character tabs other than the summary tab are blank (i.e. the table outline is there but there is no table displayed and thus no races, classes, equipment etc. can be seen). The advanced sources tab is also empty.

==== Fix ====
There are two options to fix this:
# Install Java 6 and ensure PCGen uses that (may require downgrading
Java or using a batch file to start PCGen with Java 6)
# Use PCGen 5.17.11 or later. At the time of writing the current alpha version was 5.17.14. See [http://sourceforge.net/projects/pcgen/files/PCGen%20Unstable/ PCGen Alpha Downloads]

=== Windows Installations ===
* Vista & Win7 (32 & 64 versions) Install and Running
** If you are running 64-bit versions of Vista or Win7, the bat file may not find JAVA. You may have to hard-code the path to java.exe. To edit those either Right Click on my Computer -> Properties -> Advanced System Settings -> Environment Variables OR Control Panel -> System -> Advanced Syystem Settings -> Environment Variables.
** You can modify the PATH by adding your JAVA path to it.
** Example of a Direct Reference to Java:
** "C:\Program Files (x86)\Java\jre6\bin\java" -Dswing.aatext=true -Xms1024m -Xmx1024m -jar pcgen.jar
** Put that in your PCGen Bat File.
** If you're using the BAT, feel free to up the memory usage. I have mine set to 512 and 1028 (Just edit the bat file in a text editor). Set the memory to what your system can handle.
** Install in a NON-default directory (not c:\program files) Vista and Win7 seem to have directory permission issues at times. (Especially Win7) The UAC in both can cause problems in some cases.
** Setting the Permission of the FOLDER to the highest level can help
** 5.17.0 onward have an exe file that solves the JAVA issue.
** Make sure you have a current version of JAVA installed (Not normally an issue for Windows Users)

* 1) Create a pcgen.cmd file with the following in it:

** "C:\Program Files (x86)\Java\jre6\bin\java.exe" -Dswing.aatext=true -Xms256m -Xmx1024m -jar "C:\Program Files (x86)\PCGen\PCGen5161\pcgen.jar"

** 2) Put the pcgen.cmd file in your C:\program files (x86)\pcgen\pcgen5161\ directory.
** 3) Change your shortcut link to the pcgen.cmd file.

=== Mac Installation Issues ===
ISSUE: I have downloaded PCGen for the Mac and I cannot get it to run. If I try to open the application from within the disk image, I get this error message: " “PCGen 6.04.01” is damaged and can’t be opened. You should eject the disk image." If I move the application into the Applications folder on my hard drive, I get this error message: "You can’t open the application “PCGen 6.04.01” because it is not supported on this type of Mac."

SOLUTION: To prevent this error, go to System Preferences -> Security & Privacy. At the bottom of the window there is a section titled: "Allow apps downloaded from:" Then select "Anywhere". That will allow you to open PCGen.

ISSUE: Gatekeeper will not allow PCGen to run

SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.

UPDATE:

* Hold down "control" button
* Click on the app that is triggering the message about the security preferences
* Select "open" to override and install/open the application

This allows you to avoid changing the security setting to "anywhere."

=== Homebrew OS Sheet for working 5.17.16 and forward ===

As part of an improvement to Display all the Allowable Range Increments properly for Thrown and Ranged Weapons, some changes were made to the BASE.XML file and the reliant XSLT files. Sadly, this change '''will''' break home-brew OS sheets going forward.

You have two options going forward.

'''Option 1:'''
You'll need to make the following change to the section listed in your XSLT files that contains this:



Replace that entire Section with this new code.

[http://pastebin.com/2YAhrBSV PCGen Pastebin Link to Updated Ranges Template]

'''Option 2:'''

Replace the BASE.XML file shipped by us and using an older one (But this will mean you lose the newer functionality)

=== Changing a Character's Sources ===

Sometimes you may need to change the sources a character is associated with, you could be adding a new source book you have started using or removing a book that is unused. Here's how to do it:

# Turn off the "Load Sources with PC" option in Preferences > Sources
# Load the desired sources
# Load your character
# Save your character again (I'd recommend saving to a new file)
# Reactivate "Load Sources with PC" in preferences.

The saved character will now be registered against the new sources which will be checked each time you load the character.

Another option is to use a pre-saved source selection. This can then be used by a number of characters and just updated when you want to add books. You can create a pre-saved source selection using these steps

# Open Sources > Select Sources and switch to the Advanced tab
# Select the game you are using in the first drop-down.
# Select the sources you would like to use (using Add Selected)
# Once happy click the Save Source Selection button and enter a name for your source set.
# Select the new set on the Basic tab and load it.

Then when you want to update the sources used for those characters just repeat the process using the same name. You should select the original saved selection first before switching to the Advanced tab and then the old books you selected will be already selected.

FAQ and Help

2018-02-26T00:10:13Z

LegacyKing:

This is just some tips to help along. It'll be a repository of Frequently Asked Questions and Help Tips that we've encountered a lot.

== What is PCGen? ==
PCGen is a JAVA Program that uses custom 'text' files (*.pcc and *.lst) to emulate books from table-top role-playing games, like Dungeons & Dragons 3rd edition, to help create and maintain system rules-legal characters for that game system. It allows you to print out character sheets, or export them into various formats for later use - such as a basic text sheet, xml for various forum play and software systems, htm for web browser enabled devices and pdf. PCGen is built to support the most popular d20 systems and has plans for future expansion into non-d20 based systems.

== What systems does PCGen support today? ==
Today PCGen (version 6.2) supports Dungeons and Dragons by Wizard of the Coast - the specific versions supported directly are: 3rd edition (Known as SRD), 3.5 edition (RSRD), d20 Modern (MSRD). Due to license issues, the program can support 4th edition and the upcoming 5th edition (known as D&D Next) but we cannot supply any pre-made books. Those will require custom sets that you can make yourself.

Our list of supported d20 systems with pre-made books:
* D&D 5.0 edition (Listed as SRD5)
* D&D 3.0 edition (Listed as SRD - System Resource Documents)
* D&D 3.5 edition (Listed as RSRD - Revised System Resource Documents)
* D&D Modern Edition (Listed as MSRD - Modern System Resource Documents)
* Deadlands by Pinnacle Entertainment
* Fantasy Craft by Crafty Games (Crafty Games is hosting the full core rule book, we only have a level 4 demo set)
* Gaslight 1st edition by Battlefield Press
* Legends of Excalibur
* Pathfinder by Paizo Publishing
* Sidewinder
* Spycraft
* Xcrawl

Non-d20 Systems we're building support for:
* Killshot by Broken Ruler Games (This is ready to play but needs a Character Sheet to display)
* Cyberpunk
* Shadowrun

== Using Pathfinder in PCGen ==
* Unchained Classes - Q&A:
** '''QUESTION''': How can I created an Unchained x class?
** '''ANSWER''': First, you need to make sure you are loading the correct book(s). You will need to load ''Pathfinder Unchained'' to have access to the first four Unchained variant classes - Barbarian, Monk, Rogue, and Summoner. Select the base class, Rogue for Unchained Rogue as an example. Once you add the first level, go to the Feats & Abilities tab, under Class Features, there should be a CLASS SELECTION group. Select the Unchained Version from there. Congratulations, you now have an Unchained version of the Class.
** '''LIMITATIONS''': Warning - Due to how PCGen processes SPELL LISTS, an Unchained Summoner will require you to SAVE and RELOAD to have the correct spells populate your spell list.
** QUESTION: I'm very curious (from both a user's viewpoint and that of a designer) as to why you made the Unchained classes as options within the class (when the source is selected) instead of a separate class in their own right. I actually found that very confusing when making an unchained class as I couldn't select it from the class list as one would usually do when making a character. It was only when I went back to the summary screen after selecting the class that I realized I could make the Unchained version. That's a design decision that needs to be deliberated upon and possibly altered because as it stands, it is highly confusing and may lead a lot of people to believe that you can't make an Unchained class at all in PCGen.
** ANSWER: Since that was my decision, I'll be happy to explain the reasoning and how I arrived at that conclusion. If you do a comparison between the normal classes and the unchained versions, you will see (in most cases) the only differences was the class features - Monk had a HD boost, Summoner has a Spell List change, Barbarian only changes features, and Rogue added some new features. It seemed more economical to re-use the base framework which 90% of the classes were built upon. Reduce duplication in code (Each class loaded requires some memory, whereas the method I opted did not increase memory, merely which features to use). Unchained classes comes across as more a variant. Plus, you cannot have an unchained version and regular version of the class. Programming in "Cannot take this" does increase cpu cycles and additional code lines. Add in the fact they were treated just as the regular version in terms of meeting prerequisites for prestige classes, feats, and archetypes, etc. Looking at it big picture, it made more sense to simply use the base class and treat the unchained variant as a super archetype - swap out abilities. They were more the base class then not. The chance of breaking support was higher if they were coded separately - anything using the code classlevel("Summoner") would fail for an "Unchained Summoner" as an example, SERVESAS only does prexxx support. Reviewing everything related to the class - favored classes, archetype support, feats and the data hacks was a bit more time consuming. Plus, it gave me the excuse to test out a function of the program to try and support a prestige class that grants class features from other classes, which we could not support in the past. To combat the confusion, I did include the Summary TO DO to prompt the user to choose which version they want to use; most users use the summary screen to add classes to the character, which would mean they see the prompt right off. Under the hood, it defaults to the base version in case they never make that selection. An important fact for the Summoner - so it still gains spells. If it helps to know, I went back and forth several times, actually coding them up initially as classes. But the lack of time on my part limited what I was willing to undertake, so choosing the path that had the least chance to break any particular build was what I ended up doing. As I progressed, I learned a new tidbit that swung the pendulum toward the other method. I might have chosen differently knowing what I know today. Right or wrong, it is a bit late to change the decision (6.06.00 is now released). With our focus for the 6.08 dev cycle to rip out the JEP reliance tags - anything that starts with BONUS:x, anything that is touched by BONUS, such as LEGS, FACE, REACH, WEAPONPROF, etc. Implementing new support for global and local variable numbers, Booleans, strings and orderedpairs. Rip out every text output tag and replace it with INFO/INFOVARS. Redesign the output sheets to (1) use the freemarker template code properly, and (2) switch to grabbing the new output via fact, info and value. The end goal is a more lean and efficient code base and data processing. Hope that helps clear up the decision making process that led to variant vs. class. If you have any other questions, comments or otherwise, feel free to reach out to me. --Andrew Maitland (Content Silverback - PCGen Board of Director's)
** Reply back: Thanks for the explanation. Now I understand the process behind the decision a lot more. Might be something to add to the FAQs because other people may also get confused and I admittedly found the Unchained version by accident.

* Pathfinder vs Pathfinder Society:
** QUESTION: What is the difference between these and why should I care?
** ANSWER: Pathfinder Society is an actual real world international organization which publishes official rules of play for gamemasters and players alike. The games are run using official modules with completion items given out, special sheets to track rewards and of course a very different XP progression, which is capped well before 20th level. As mentioned before they publish rules each year to tell their members what is legal to use in their games. In essence Pathfinder Society (abbreviated PFS) is a structured event setting which determines what is legal in their games, allowing players from all over the world to have the same experiences and options. Many feats, spells, equipment and class options are restricted in the Pathfinder Society games. PCGen supports the various seasons of play as best we can. Many false bugs are raised due to people mistakenly thinking their favorite options are not working. Rule of thumb, unless you play in this actual society, do not use their rules.

== How Customizable is PCGen? ==
PCGen is designed with user customizations in mind. For the Books Side, we are looking to re-include an In-built LST Editor in the program for version 6.4.0. LST files are the main text files for holding the information that PCGen (JAVA Program) can read and execute. LST Files are plain text programing using a customized Language that is designed towards simple premise of Human-Readable and easily used.

PCGen has several methods to impart how to create your own custom files. First, we supply a sample folder including a full set of pcc and lst files for you to get started. We have extensive documentation in the program, and maintained on our website. Andrew Maitland has made several youtube videos explaining how to craft the files, and the common mistakes to avoid. Finally, we offer online support via our Yahoo Groups and direct help from our Support Desk Monkey - Help@PCGen.Org.

== Is there support for issues and recommendations? ==
Yes, PCGen is a volunteer project run by monkeys and humans. We all know monkeys are a laugh, and humans are fallible. Thus, we have a Ticket Support system that is monitored by the various projects that go towards supporting PCGen. Our ticket support system is called 'JIRA' and anyone can log into the system after creating an account, and report a problem "Bug" or make recommendations for improvements (Feature Requests). The system is located at http://jira.pcgen.org.

Wait, what do all those projects visible mean? I'm totally confused?!!?!
* Data - This is the Books. Chances are if it's incorrect the logical issue would be this project. Bug is something broken; Feature is new things to be added.
* Code - This is the heart of PCGen and encompasses the JAVA involved. They also handle the User Interface (UI for short).
* Docs - This is the Documentation that comes with PCGen. Bugs are typographical errors, or formatting problems. Features would be adding new "classes" or "how-to" to explain using PCGen in new ways.
* OS - This is the output sheets or the final product you see. This encompasses the Summary bottom Pane, the Preview Sheets found on "Character" tab of the program, and all of the export methods.
* Admin - This is non-pcgen issues, like the Website has mistakes.
* Support - This is the catch-all "Help, I'm lost and need guidance". When the program is causing issues, or you cannot figure out something, this is a good place to start.

What if I mess up and place it in the wrong area?
* Fear not, our Jira is monitored by experienced project volunteers, and can easily move your issue to the correct location at any time.

How should I submit an issue?
* Details are the key point. In order to address any issue we need facts. Please include the following in all reports:
** Summary of the issue (Single sentence to briefly give an idea of the issue)
** Version of PCGen (In most cases this is a requirement)
** Data You are loading (You can submit a character file (*.pcg) to the Ticket and that will help speed things along
** Description - What is wrong in your own words, and what is the correct result. Cite a source book if available. Since a person needs to verify the issue before making corrections.
** Environment - Your operating system, Java version and anything else you think will help us.

== Trouble Shooting Problems ==

===Mouse Over Issues for some users===
Solution: run Command Line, navigate to your PCGen installed files "cd c:\the\path\to\pcgen" and type in:
java "-Dsun.java2d.d3d=false" -jar .\pcgen.jar

===High Resolution Display===
I was able to workaround this issue by going into the compatibility properties of the PCGen shortcut and setting the "Override high DPI scaling behavior" to System. This was tested on Windows 10.

=== Java 7 for version 5.17.11 or lower ===
PCGen versions prior to 5.17.11 (including the current production version, 5.16.4) are not compatible with Java 7. This is now the default version Java installed for most system types. Open JDK 6 on Linux exhibits the same problems and the same fix applies.

==== Symptoms ====

When you start PCGen, all character tabs other than the summary tab are blank (i.e. the table outline is there but there is no table displayed and thus no races, classes, equipment etc. can be seen). The advanced sources tab is also empty.

==== Fix ====
There are two options to fix this:
# Install Java 6 and ensure PCGen uses that (may require downgrading
Java or using a batch file to start PCGen with Java 6)
# Use PCGen 5.17.11 or later. At the time of writing the current alpha version was 5.17.14. See [http://sourceforge.net/projects/pcgen/files/PCGen%20Unstable/ PCGen Alpha Downloads]

=== Windows Installations ===
* Vista & Win7 (32 & 64 versions) Install and Running
** If you are running 64-bit versions of Vista or Win7, the bat file may not find JAVA. You may have to hard-code the path to java.exe. To edit those either Right Click on my Computer -> Properties -> Advanced System Settings -> Environment Variables OR Control Panel -> System -> Advanced Syystem Settings -> Environment Variables.
** You can modify the PATH by adding your JAVA path to it.
** Example of a Direct Reference to Java:
** "C:\Program Files (x86)\Java\jre6\bin\java" -Dswing.aatext=true -Xms1024m -Xmx1024m -jar pcgen.jar
** Put that in your PCGen Bat File.
** If you're using the BAT, feel free to up the memory usage. I have mine set to 512 and 1028 (Just edit the bat file in a text editor). Set the memory to what your system can handle.
** Install in a NON-default directory (not c:\program files) Vista and Win7 seem to have directory permission issues at times. (Especially Win7) The UAC in both can cause problems in some cases.
** Setting the Permission of the FOLDER to the highest level can help
** 5.17.0 onward have an exe file that solves the JAVA issue.
** Make sure you have a current version of JAVA installed (Not normally an issue for Windows Users)

* 1) Create a pcgen.cmd file with the following in it:

** "C:\Program Files (x86)\Java\jre6\bin\java.exe" -Dswing.aatext=true -Xms256m -Xmx1024m -jar "C:\Program Files (x86)\PCGen\PCGen5161\pcgen.jar"

** 2) Put the pcgen.cmd file in your C:\program files (x86)\pcgen\pcgen5161\ directory.
** 3) Change your shortcut link to the pcgen.cmd file.

=== Mac Installation Issues ===
ISSUE: I have downloaded PCGen for the Mac and I cannot get it to run. If I try to open the application from within the disk image, I get this error message: " “PCGen 6.04.01” is damaged and can’t be opened. You should eject the disk image." If I move the application into the Applications folder on my hard drive, I get this error message: "You can’t open the application “PCGen 6.04.01” because it is not supported on this type of Mac."

SOLUTION: To prevent this error, go to System Preferences -> Security & Privacy. At the bottom of the window there is a section titled: "Allow apps downloaded from:" Then select "Anywhere". That will allow you to open PCGen.

ISSUE: Gatekeeper will not allow PCGen to run

SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.

UPDATE:

* Hold down "control" button
* Click on the app that is triggering the message about the security preferences
* Select "open" to override and install/open the application

This allows you to avoid changing the security setting to "anywhere."

=== Homebrew OS Sheet for working 5.17.16 and forward ===

As part of an improvement to Display all the Allowable Range Increments properly for Thrown and Ranged Weapons, some changes were made to the BASE.XML file and the reliant XSLT files. Sadly, this change '''will''' break home-brew OS sheets going forward.

You have two options going forward.

'''Option 1:'''
You'll need to make the following change to the section listed in your XSLT files that contains this:



Replace that entire Section with this new code.

[http://pastebin.com/2YAhrBSV PCGen Pastebin Link to Updated Ranges Template]

'''Option 2:'''

Replace the BASE.XML file shipped by us and using an older one (But this will mean you lose the newer functionality)

=== Changing a Character's Sources ===

Sometimes you may need to change the sources a character is associated with, you could be adding a new source book you have started using or removing a book that is unused. Here's how to do it:

# Turn off the "Load Sources with PC" option in Preferences > Sources
# Load the desired sources
# Load your character
# Save your character again (I'd recommend saving to a new file)
# Reactivate "Load Sources with PC" in preferences.

The saved character will now be registered against the new sources which will be checked each time you load the character.

Another option is to use a pre-saved source selection. This can then be used by a number of characters and just updated when you want to add books. You can create a pre-saved source selection using these steps

# Open Sources > Select Sources and switch to the Advanced tab
# Select the game you are using in the first drop-down.
# Select the sources you would like to use (using Add Selected)
# Once happy click the Save Source Selection button and enter a name for your source set.
# Select the new set on the Basic tab and load it.

Then when you want to update the sources used for those characters just repeat the process using the same name. You should select the original saved selection first before switching to the Advanced tab and then the old books you selected will be already selected.

Release 6.10.x

2018-02-24T17:38:40Z

LegacyKing: Created page with "{| align="right" | __TOC__ |} =Release dates= '''Alpha''' TBD '''Beta''' TBD '''RC''' TBD '''Production''' TBD =Team Goals= * Implement the Formula Parser Replaceme..."

{| align="right"
| __TOC__
|}

=Release dates=

'''Alpha'''
TBD

'''Beta'''
TBD

'''RC'''
TBD

'''Production'''
TBD

=Team Goals=

* Implement the Formula Parser Replacement
* Update OS to take advantage of the new FACT system, the Formula Parser and other improvements.

==[[Architecture]]==
* [[Formula_Parser_Equip_Vars_Proposal | Formula Parser replacement for JEP (Global and Local)]]
* Deprecate unnecessary BONUS tags being replaced by new Formula Parser System

==[[Code]]==
* [[LST Editor]] overhaul
* Correct Natural Attacks (Discussion)

==[[Data]]==
* Continue Data Improvements
* Work with Arch to Align Data to use new Formula Parser

==[[Output Sheets]]==
* Continue migration to Freemarker Output

==[[Documentation]]==
* Update to reflect Tag changes

==[[Publisher Liaison]]==
* No major projects, continuation of existing work

==[[Data License]]==
* No major projects, continuation of existing work

==[[Advertising]]==
* No major projects, continuation of existing work

Roadmap

2018-02-24T17:37:15Z

LegacyKing:

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

This page contains the PCGen Roadmap

=Releases=
* [[Release 6.10.x]] - Release 6.10.0 will implement Formula Parser improvements, deprecate the JEP code, and begin progress on both Output sheets and User Interface.

* [[Release 6.8.x]] - Release 6.08.0 will continue the pattern of improvements in the code base (migrating to a replacement formula parser) and OS.

==
* [[Release 5.6.x]] - There is no further active development on this branch
* [[Release 5.8.x]] - 5.8.1 was last production release of this branch, there is no further active development
* [[Release 5.10.x]] - 5.10.2 was the last production release of this branch, there is no further active development
* [[Release 5.12.x]] - 5.12.1 was the last production release of this branch, there is no further active development
* [[Release 5.14.x]] - 5.14.1 was the last production release of this branch, there is no further active development
* [[Release 5.16.x]] - 5.16.4 was the last production release of this branch, there is no further active development
* [[Release 6.0.x]] - 6.0.1 was the last production release of this branch, there is no further active development
* [[Release 6.2.x]] - Release 6.2.1 is the current production release
* [[Release 6.4.x]] - Release 6.4.0 is the next planned production release (No further active development)
* [[Release 6.6.x]] - Release 6.6.0 will contain various feature enhancements to PCGen

=Planning=
* [[Proposed FREQ Roadmap]]

Release 6.8.x

2018-02-24T17:35:12Z

LegacyKing:

{| align="right"
| __TOC__
|}

=Release dates=

'''Alpha'''
* 2017-01-14 -- 6.07.01
* 2017-06-11 -- 6.07.02
* 2017-08-13 -- 6.07.03
* 2017-10-15 -- 6.07.04
* 2017-11-22 -- 6.07.05
* 2018-01-29 -- 6.07.06
* 2018-03-04 -- 6.07.07
* 2018-03-18 -- 6.07.08

'''Beta'''
* 2018-04-01 -- 6.07.09
* 2018-04-08 -- 6.07.10
* 2018-04-15 -- 6.07.11
* 2018-04-22 -- 6.07.12

'''RC'''
* 2018-04-29 -- 6.08.00RC1
* 2018-05-06 -- 6.08.00RC2
* 2018-05-13 -- 6.08.00RC3

'''Production'''
* 2018-05-20 -- 6.08.00 (Production)

=Team Goals=

* Implement the Formula Parser Replacement
* Update OS to take advantage of the new FACT system, the Formula Parser and other improvements.

==[[Architecture]]==
* [[Formula_Parser_Equip_Vars_Proposal | Formula Parser replacement for JEP (Global and Local)]]
* Deprecate unnecessary BONUS tags being replaced by new Formula Parser System

==[[Code]]==
* [[LST Editor]] overhaul
* Correct Natural Attacks (Discussion)
* Update Java to use 8 as the base code, remove support for Java 7

==[[Data]]==
* Continue Data Improvements
* Work with Arch to Align Data to use new Formula Parser

==[[Output Sheets]]==
* Continue migration to Freemarker Output
* Take advantage of FACT/FACTSET capabilities when available

==[[Documentation]]==
* Update to reflect Tag changes

==[[Publisher Liaison]]==
* No major projects, continuation of existing work

==[[Data License]]==
* No major projects, continuation of existing work

==[[Advertising]]==
* No major projects, continuation of existing work

Meeting 2018 02 24

2018-02-24T17:06:04Z

LegacyKing:

==''Attendance:''==
* Benevolent Dictator - Bryan
* Chair - Kar
* Code - Tom
* Content - Andrew
* PR - Paul
* Data 2nd - Gwen
* Observer - Douglas
* Observer - David

==''Summary:''==
* PR - Willing to support local volunteers for Conventions for 2018
* PR - No GenCon for 2018 planned
* PR - Will review Data Books waiting on queue
* Content - Fixing bugs and making publishers happy
* Code - Several GATE issues prevent any Production Release
* Code - Issues are fixed, just in a queue to be PR and reviewed
* Code - Will improve WIKI to get new developers up and running
* Roadmap - Target is May/June for Production release 6.08.00

===Redacted Log===
* [6:00 AM] Andrew Maitland: Good morning all, welcome to the Board of Directors meeting
* [6:00 AM] Andrew Maitland: The agenda on the table for today is:
* [6:00 AM] Andrew Maitland: Agenda: 1) Team Reports (10 minutes) 2) Roadmap Progress / Release Planning (10 minutes) 3) Tom's Corner (35 minutes) 4) Public Q&A (5 minutes)
* [6:01 AM] Andrew Maitland: @PaulGrosse would you like to kick this off from the PR?
* [6:04 AM] Paul Grosse: Lets see, we've had some books cleared for release, theres a pile of them that I will be getting to next week while wife is on vacation. :)
* [6:05 AM] Paul Grosse: We've had a good response from the call for help, and there's been a trickle of volunteers coming in
* [6:06 AM] Paul Grosse: I need to update the news page on the 6.07.06 release while the ability to update the webpage was broken
* [6:06 AM] Paul Grosse: I think that's it for me
* [6:07 AM] Bryan McRoberts: Nice
* [6:07 AM] Andrew Maitland: Any plans for convention presence this year?
* [6:09 AM] Paul Grosse: GenCon is already out we would have had to sign up last year
* [6:10 AM] Andrew Maitland: Okay, when would we need to plan for 2019's convention then?
* [6:10 AM] Paul Grosse: We almost have the funds already though if we want to aim for next year. Other then that there some other ones we could aim at.
* [6:11 AM] Andrew Maitland: Cool. I think we should encourage local volunteers to hit up their local area conventions to get to a wider audience if possible. :)
* [6:11 AM] Paul Grosse: GaryCon, Origins, a couple others I can't remember ATM
* [6:11 AM] Andrew Maitland: No booth necessary, just pass out flyers.
* [6:11 AM] Andrew Maitland: (or run games using PCGen created sheets).
* [6:12 AM] Paul Grosse: We could even cover a booth if they had a team to cover it, most cons are around 40-150ish for a booth depending on size
* [6:12 AM] Andrew Maitland: Okay, for the Content Team -
* [6:12 AM] Andrew Maitland: @GwenT and the data volunteers have been pounding out a solid stream of books to keep @PaulGrosse fairly busy. :)
* [6:13 AM] Andrew Maitland: @ReganAnderson is working on revamping the Sorcerer Bloodlines
* [6:14 AM] Bryan McRoberts: When is the next production release?
* [6:14 AM] Andrew Maitland: We'll hit that in a moment Bryan.
* [6:14 AM] Andrew Maitland: We've discovered they were not coded up correctly, and in order to properly handling the various archetypes, a major overhaul was required (The existing system was broken, and un-maintainable).
* [6:14 AM] Bryan McRoberts: That's a big undertaking by Regan
* [6:15 AM] Andrew Maitland: It is, but I've been supporting him and letting him tackle this project at his pace.
* [6:15 AM] Andrew Maitland: However, since we took a rather large chunk of Usability out, I've delayed the next release until we can include that back in.
* [6:16 AM] Andrew Maitland: I updated our Saga Born data and connected Output sheets to the delight of one of our Publishers.
* [6:16 AM] Paul Grosse: :)
* [6:16 AM] Bryan McRoberts: Very cool!
* [6:17 AM] Andrew Maitland: Other than that, I've been handling bugs that are trickling in.
* [6:17 AM] Andrew Maitland: Any questions before we move on to Code team report from @TomParker ?
* [6:17 AM] Bryan McRoberts: Well done, data team! Paul - thanks for all your work with PR as well!
* [6:18 AM] Bryan McRoberts: What % done would you say the Sorcerer work is?
* [6:18 AM] Bryan McRoberts: Just ballpark
* [6:19 AM] Andrew Maitland: With APG, CR and UM pretty completed, supporting the Eldritch feats, and Crossblooded, leaving only the Wildblooded, I'd say 80-90% since I'm not the one doing the work.
* [6:20 AM] Bryan McRoberts: Excellent
* [6:20 AM] Gwen T: Sorry I'm late. Over slept
* [6:20 AM] Bryan McRoberts: GM Gwen
* [6:21 AM] Andrew Maitland: Morning Gwen
* [6:21 AM] Gwen T: Good Morning... or it will be when coffee finishes brewing. :p
* [6:21 AM] Andrew Maitland: Okay @TomParker code team is probably going to cover agenda #2 and #3 as well, so feel free to hit on all of those. :)
* [6:22 AM] Tom Parker: Continuing work to simplify the core infrastructure - a bunch of internal changes there that don't really appear externally
* [6:22 AM] Tom Parker: but have removed a lot of one-off cases in the code
* [6:23 AM] Bryan McRoberts: Nice
* [6:23 AM] Tom Parker: Have a bit of an issue at the moment that's preventing us from retiring the "built-in" default race
* [6:23 AM] Tom Parker: Effectively, FACT / FACTSET leak between loaded game modes/campaigns
* [6:24 AM] Tom Parker: which could cause issues if things are swapped in and out, especially if one of the campaigns causes a FACT to be required
* [6:25 AM] Tom Parker: That's going to gate other things on my end until I get it addressed, since the fix will likely be a bit invasive to a number of places in the code
* [6:25 AM] Tom Parker: The new formula system is doing work behind the scenes already, so we know it works to the first order
* [6:25 AM] Tom Parker: (FACE is currently done for all game modes, for example, even if it's not apparent to the data team)
* [6:25 AM] martijnverburg: Sorry I’m late - toddler battles!
* [6:26 AM] Bryan McRoberts: Martijn - lol
* [6:27 AM] Tom Parker: Speaking of which. ... Martijn has been suggesting some use of DI, but given that we are so heavily data driven, that is a huge challenge.... I rapidly hit the point where a DI framework is unusable or unruly... so could use a more detailed discussion with Martijn (and others who want to participate) at some point
* [6:27 AM] Bryan McRoberts: Tom - would the leak gate a production release? Or has this not been folded into the master branch yet?
* [6:27 AM] Tom Parker: The leak is in master
* [6:27 AM] Tom Parker: has been for a long time actually
* [6:27 AM] Tom Parker: It shouldn't gate another 6.7.x release
* [6:28 AM] Tom Parker: but should probably gate a 6.8
* [6:28 AM] Bryan McRoberts: Ok
* [6:28 AM] Tom Parker: On the bug front, have addressed some of those, and Marco (one of the new folks that has helped out) diagnosed a few of them to where it appeared to be a data issue
* [6:30 AM] martijnverburg: Yeah I need to understand the code better before making spurious suggestions
* [6:30 AM] Tom Parker: On the new volunteer front for code engagement and retention is a bit of an issue. There aren't a lot of "easy projects" around, and I can point people at some bugs to go look at to start to get familiar with things but that doesn't always lead to them actually looking
* [6:32 AM] Tom Parker: On the wider side of things, there are updated docs on the formula system on the wiki
* [6:32 AM] Tom Parker: As well as a proposal on the CHOOSE replacement (which will need to be tweaked a bit, but gives the general sense for now)
* [6:33 AM] Tom Parker: The new developer startup page is also updated, with a review and some feedback from folks as well
* [6:33 AM] Tom Parker: If anyone has other things to consider for how it might keep (or get) people engaged, let me know
* [6:34 AM] Andrew Maitland: Should we list out useful projects for people to look at?
* [6:35 AM] Andrew Maitland: Like a roadmap with the subtasks looking to accomplish perhaps?
* [6:35 AM] Gwen T: I'd like to see one of our "splash screens" that pop up while loading used for recruitment
* [6:36 AM] Tom Parker: I think the question is what level of detail is needed
* [6:36 AM] Tom Parker: not sure I know, so it needs to be more of a discussion with folks
* [6:37 AM] Tom Parker: otherwise I'm just writing tons of stuff down for no effect
* [6:37 AM] Tom Parker: As far as the splash screen, I'd be cautious about driving more recruitment if we can't retain - we should try to figure out how to retain the trickle we have now before we open a flood gate
* [6:37 AM] Tom Parker: Not sure I have anything else for today
* [6:38 AM] Bryan McRoberts: Is the new developer document on the wiki?
* [6:38 AM] Andrew Maitland: Based upon current code gates to the formula system, where do we see the next production release potentially happening?
* [6:38 AM] Avilay: is there a way to sort of tasks according to urgency?
* [6:39 AM] Andrew Maitland: Avilay - in Jira yes, on the wiki, it's however they are listed out.
* [6:39 AM] Tom Parker: http://wiki.pcgen.org/Basic_Developer_Setup
* [6:39 AM] Tom Parker: JIRA though it a LONG list of items
* [6:39 AM] Tom Parker: with lots of mixes of complexity
* [6:40 AM] Tom Parker: The problem being we don't know the skill set of devs coming in - we've dealt with all levels
* [6:40 AM] Bryan McRoberts: I don't see a link to that on the main wiki page
* [6:40 AM] Gwen T: @AndrewMaitland When we port to Stride, we should look at getting Trillo boards for that!
* [6:40 AM] Tom Parker: Someone who is new to Java probably can't take on a deep diagnosis
* [6:42 AM] Andrew Maitland: I think the retention is at least a two-fold problem
* [6:42 AM] Tom Parker: I'm not sure how to do that balancing without a conversation with those folks, but when I've tended to ask questions about skills et al, so I have a sense of where to start, that seems to drive some away, and at times it feels others go silent when I don't assume they know what they are doing (because they may be an experienced dev but I really don't know that)
* [6:43 AM] Andrew Maitland: Getting set up seems to be a big hurdle (I cannot get set up with the newest Eclipse) as an example. And then getting them plugged into an easy communication with the teams seems to be another part.
* [6:43 AM] martijnverburg: I think a basic tutorial could be written on getting a piece of data from a LST file through to the UI and exported to a character sheet
* [6:44 AM] Tom Parker: @MartijnVerburg Fair point. Part of the challenge being there are a few ways to do it today - one strategic, and some legacy
* [6:45 AM] Tom Parker: I will at least write up the two primary ones
* [6:45 AM] Bryan McRoberts: Martijn - great idea. Something that explains a bonus that has a prereq and how it gets to a character sheet and UI would take a dev through the main functions of the code.
* [6:45 AM] Bryan McRoberts: Same for the new formula code
* [6:45 AM] martijnverburg: Yeah I’ll admit I’m lost on the legacy way vs current way vs proposed future way
* [6:46 AM] Bryan McRoberts: As Andrew noted, making sure the new dev instructions gets someone up and running fairly quickly is paramount
* [6:46 AM] Tom Parker: All a great point. Barring some major issue, I will write that this week
* [6:47 AM] Bryan McRoberts: I'd be a good guinea pig. My build was working, I did an update and now it's broken and I haven't had/made time to figure it out.
* [6:47 AM] martijnverburg: I’ll happily review / try it out as well - happy to write some as well if that helps with the load
* [6:48 AM] Tom Parker: @BryanMcRoberts There are a few situations where an update can break things, and I think you joined when we did one of them
* [6:48 AM] Tom Parker: sorry, LOL not joined
* [6:48 AM] Tom Parker: brought up your dev environment :)
* [6:48 AM] Bryan McRoberts: right :)
* [6:48 AM] Tom Parker: So you may need to delete the project and re-import it as a new Gradle project to get Gradle to behave
* [6:49 AM] Tom Parker: (so delete from eclipse but not from the disk)
* [6:49 AM] Bryan McRoberts: ah
* [6:49 AM] martijnverburg: 👍
* [6:50 AM] Tom Parker: I removed a few key files from git that Gradle can now consistently build correctly, and that breaks you if you didn't realize the impact
* [6:50 AM] Tom Parker: Thankfully those types of rebuild events are rare
* [6:51 AM] Bryan McRoberts: cool
* [6:52 AM] Tom Parker: If it doesn't work for you let me know and we can try to find some time to walk through what is misbehaving
* [6:52 AM] Bryan McRoberts: ok - thanks
* [6:53 AM] Tom Parker: Any other questions or suggestions ?
* [6:53 AM] Andrew Maitland: Tom - on the Jira side, I enabled tasks for data, which allows for sub issues inside on main issue.
* [6:53 AM] Andrew Maitland: Would that be helpful for the code and new tag projects?
* [6:54 AM] Tom Parker: My sense if probably not, but I'll think about it. For the few times I've needed that I've just created a Mini-Project and linked the issues together
* [6:54 AM] Bryan McRoberts: Not from me - great work on the code, Tom. Hopefully Martijn, I and others can become more productive to lessen the load on you.
* [6:54 AM] Andrew Maitland: And the last question Bryan had that we don't have answer for - Production Release?
* [6:55 AM] Bryan McRoberts: Drum roll....
* [6:55 AM] Tom Parker: So my big gates
* [6:55 AM] Tom Parker: FACT / FACTSET needs fixing
* [6:56 AM] Tom Parker: GROUPING needs fixing, since it's a nasty inner class hack at the moment
* [6:56 AM] Tom Parker: I need to fix a Scope/Format issue that impacts what is currently dropIntoContext
* [6:57 AM] Tom Parker: and in the process of changing that convert to getOther instead (better semantics)
* [6:57 AM] Tom Parker: the latter two are needed so we don't end up with MODIFY/MODIFYOTHER statements that I immediately need to break -
* [6:57 AM] Tom Parker: that should all happen in one Alpha cycle
* [6:58 AM] Tom Parker: The GROUPING item is done, but about 4th in line on my local system for pushing
* [6:58 AM] Tom Parker: (I have a HUGE set of interacting PRs, one of which turns out is gated by the FACT fix)
* [6:59 AM] Tom Parker: The Scope/Format fix has had a bunch of the work done in the Formula Library; let me look at whether it is already integrated
* [7:00 AM] Tom Parker: So Scope/Format is partially in the formula library
* [7:01 AM] Tom Parker: I have a few other PRs to go in there, but I try to integrate things that are incompatible interface changes one at a time into the master of PCGen, so avoid confusing myself too much :)
* [7:01 AM] Tom Parker: The other items I need are built, just not Pushed
* [7:01 AM] Tom Parker: So once I get the FACT thing down, it's probably a few weeks to get the rest pushed through. 80% of the work is done and I just get to do a slew of conflict resolution to create valid PRs
* [7:02 AM] Tom Parker: So maybe target moving to Beta in April?
* [7:03 AM] Andrew Maitland: Wow, that's faster than I anticipated.
* [7:03 AM] Andrew Maitland: I guess the better question is what do we expect in the next production release.
* [7:03 AM] Tom Parker: That's a fair question, actually
* [7:04 AM] Tom Parker: The April statement is about as fast as I can do it
* [7:04 AM] Andrew Maitland: If we want single gamemode conversion, then I'm probably going to need a couple of months at least.
* [7:05 AM] Tom Parker: Yea, I'm not sure everything you need for that is April
* [7:05 AM] Tom Parker: I was answering "If you need to get stuff stable enough to be usable, what would it be"
* [7:05 AM] Tom Parker: Not "If PF conversion will be complete, what is the date"
* [7:06 AM] Tom Parker: At the same time, I'm not sure we should get a full conversion done
* [7:06 AM] Tom Parker: There are 2 or 3, perhaps 4 changes that are very likely to break PCs
* [7:06 AM] Andrew Maitland: Question to the group - Push out a stable 6.08 quickly, and focus on Code Formula completion and data conversion for a 6.10?
* [7:06 AM] Tom Parker: The problem being that PCGen today discards information based on how it stores PCs
* [7:07 AM] Tom Parker: A classic example is Domain is only loosely stored to the Class... but it's hard to do a dual class with two Domains
* [7:07 AM] Bryan McRoberts: It'd be nice to get a prod release out since it's been so long and a lot of data work has been done.
* [7:07 AM] Andrew Maitland: Agreed.
* [7:07 AM] Tom Parker: When we fix that, the PCG file format would need to change, and then we end up with a compatibility gap during load
* [7:07 AM] Tom Parker: The Domain one we probably just let break and people re-select the Domain - pretty innocent
* [7:07 AM] Tom Parker: But they become more invasive from there
* [7:08 AM] Bryan McRoberts: I don't think anyone would complain about a prod release soon-ish and another one in April/May.
* [7:08 AM] Tom Parker: I'm not prepared for one soon-ish
* [7:08 AM] Tom Parker: (under that definition of soon-ish)
* [7:08 AM] Bryan McRoberts: Ok - so there are current code issues gating a release from master?
* [7:09 AM] Tom Parker: The 3 I listed a bit ago
* [7:09 AM] Tom Parker: The "big gates"
* [7:09 AM] Andrew Maitland: We fix those 3, Push out a Production 6.08.00 May 15th, since we need at least 1 RC?
* [7:09 AM] Gwen T: I'd love to see a stable 6.8 as soon as reasonable. 2/3 of the issues I run across are because folks only like to use the "stable" versions. Currently, that's 6.06.01, released 2016-07-30
* [7:10 AM] Bryan McRoberts: Ok - I thought those were related to dev efforts aimed at an April release.
* [7:10 AM] Gwen T: We've killerd a lot of bugs since then!
* [7:10 AM] Tom Parker: Gwen has a good point
* [7:10 AM] Tom Parker: Andrew, I think it's better to call out early may for RC1
* [7:10 AM] Bryan McRoberts: Would it be work putting out just a data release?
* [7:10 AM] Tom Parker: and then go from there
* [7:11 AM] Andrew Maitland: Agreed, people don't touch the latest releases, and we get a lot of redundant reports.
* [7:11 AM] Tom Parker: We can't really do just a data release
* [7:11 AM] Tom Parker: the data is compatible with the current code, not the 6.6 code
* [7:11 AM] Bryan McRoberts: Ah
* [7:11 AM] Andrew Maitland: We can, but it gets sloppy... so a nice clean prod release
* [7:11 AM] Andrew Maitland: I'm still getting Starfinder 1.6 bug reports. :(
* [7:12 AM] Paul Grosse: And we are going to definitely want to have SF in the prod release. :)
* [7:12 AM] Andrew Maitland: Okay, Target May/June for 6.08.00 release.
* [7:12 AM] Bryan McRoberts: Sounds good
* [7:13 AM] Andrew Maitland: That means we drop Alpha and switch to Beta no later then end of April.
* [7:14 AM] Gwen T: That SHOULD allow for at least a couple RCs, if not a final version, in time for the summer conventions.
* [7:14 AM] Andrew Maitland: We've gone over time a bit, but any questions from anyone else before we close this up?
* [7:16 AM] Andrew Maitland: Thanks for coming everyone. Meeting adjourned - **Bangs Gavel**

Meeting 2018 02 24

2018-02-24T17:04:59Z

LegacyKing: Created page with "''Attendance:'' * Benevolent Dictator - Bryan * Chair - Kar * Code - Tom * Content - Andrew * PR - Paul * Data 2nd - Gwen * Observer - Douglas * Observer - David ''Summary:''..."

''Attendance:''
* Benevolent Dictator - Bryan
* Chair - Kar
* Code - Tom
* Content - Andrew
* PR - Paul
* Data 2nd - Gwen
* Observer - Douglas
* Observer - David

''Summary:''
* PR - Willing to support local volunteers for Conventions for 2018
* PR - No GenCon for 2018 planned
* PR - Will review Data Books waiting on queue
* Content - Fixing bugs and making publishers happy
* Code - Several GATE issues prevent any Production Release
* Code - Issues are fixed, just in a queue to be PR and reviewed
* Code - Will improve WIKI to get new developers up and running
* Roadmap - Target is May/June for Production release 6.08.00

===Redacted Log===
* [6:00 AM] Andrew Maitland: Good morning all, welcome to the Board of Directors meeting
* [6:00 AM] Andrew Maitland: The agenda on the table for today is:
* [6:00 AM] Andrew Maitland: Agenda: 1) Team Reports (10 minutes) 2) Roadmap Progress / Release Planning (10 minutes) 3) Tom's Corner (35 minutes) 4) Public Q&A (5 minutes)
* [6:01 AM] Andrew Maitland: @PaulGrosse would you like to kick this off from the PR?
* [6:04 AM] Paul Grosse: Lets see, we've had some books cleared for release, theres a pile of them that I will be getting to next week while wife is on vacation. :)
* [6:05 AM] Paul Grosse: We've had a good response from the call for help, and there's been a trickle of volunteers coming in
* [6:06 AM] Paul Grosse: I need to update the news page on the 6.07.06 release while the ability to update the webpage was broken
* [6:06 AM] Paul Grosse: I think that's it for me
* [6:07 AM] Bryan McRoberts: Nice
* [6:07 AM] Andrew Maitland: Any plans for convention presence this year?
* [6:09 AM] Paul Grosse: GenCon is already out we would have had to sign up last year
* [6:10 AM] Andrew Maitland: Okay, when would we need to plan for 2019's convention then?
* [6:10 AM] Paul Grosse: We almost have the funds already though if we want to aim for next year. Other then that there some other ones we could aim at.
* [6:11 AM] Andrew Maitland: Cool. I think we should encourage local volunteers to hit up their local area conventions to get to a wider audience if possible. :)
* [6:11 AM] Paul Grosse: GaryCon, Origins, a couple others I can't remember ATM
* [6:11 AM] Andrew Maitland: No booth necessary, just pass out flyers.
* [6:11 AM] Andrew Maitland: (or run games using PCGen created sheets).
* [6:12 AM] Paul Grosse: We could even cover a booth if they had a team to cover it, most cons are around 40-150ish for a booth depending on size
* [6:12 AM] Andrew Maitland: Okay, for the Content Team -
* [6:12 AM] Andrew Maitland: @GwenT and the data volunteers have been pounding out a solid stream of books to keep @PaulGrosse fairly busy. :)
* [6:13 AM] Andrew Maitland: @ReganAnderson is working on revamping the Sorcerer Bloodlines
* [6:14 AM] Bryan McRoberts: When is the next production release?
* [6:14 AM] Andrew Maitland: We'll hit that in a moment Bryan.
* [6:14 AM] Andrew Maitland: We've discovered they were not coded up correctly, and in order to properly handling the various archetypes, a major overhaul was required (The existing system was broken, and un-maintainable).
* [6:14 AM] Bryan McRoberts: That's a big undertaking by Regan
* [6:15 AM] Andrew Maitland: It is, but I've been supporting him and letting him tackle this project at his pace.
* [6:15 AM] Andrew Maitland: However, since we took a rather large chunk of Usability out, I've delayed the next release until we can include that back in.
* [6:16 AM] Andrew Maitland: I updated our Saga Born data and connected Output sheets to the delight of one of our Publishers.
* [6:16 AM] Paul Grosse: :)
* [6:16 AM] Bryan McRoberts: Very cool!
* [6:17 AM] Andrew Maitland: Other than that, I've been handling bugs that are trickling in.
* [6:17 AM] Andrew Maitland: Any questions before we move on to Code team report from @TomParker ?
* [6:17 AM] Bryan McRoberts: Well done, data team! Paul - thanks for all your work with PR as well!
* [6:18 AM] Bryan McRoberts: What % done would you say the Sorcerer work is?
* [6:18 AM] Bryan McRoberts: Just ballpark
* [6:19 AM] Andrew Maitland: With APG, CR and UM pretty completed, supporting the Eldritch feats, and Crossblooded, leaving only the Wildblooded, I'd say 80-90% since I'm not the one doing the work.
* [6:20 AM] Bryan McRoberts: Excellent
* [6:20 AM] Gwen T: Sorry I'm late. Over slept
* [6:20 AM] Bryan McRoberts: GM Gwen
* [6:21 AM] Andrew Maitland: Morning Gwen
* [6:21 AM] Gwen T: Good Morning... or it will be when coffee finishes brewing. :p
* [6:21 AM] Andrew Maitland: Okay @TomParker code team is probably going to cover agenda #2 and #3 as well, so feel free to hit on all of those. :)
* [6:22 AM] Tom Parker: Continuing work to simplify the core infrastructure - a bunch of internal changes there that don't really appear externally
* [6:22 AM] Tom Parker: but have removed a lot of one-off cases in the code
* [6:23 AM] Bryan McRoberts: Nice
* [6:23 AM] Tom Parker: Have a bit of an issue at the moment that's preventing us from retiring the "built-in" default race
* [6:23 AM] Tom Parker: Effectively, FACT / FACTSET leak between loaded game modes/campaigns
* [6:24 AM] Tom Parker: which could cause issues if things are swapped in and out, especially if one of the campaigns causes a FACT to be required
* [6:25 AM] Tom Parker: That's going to gate other things on my end until I get it addressed, since the fix will likely be a bit invasive to a number of places in the code
* [6:25 AM] Tom Parker: The new formula system is doing work behind the scenes already, so we know it works to the first order
* [6:25 AM] Tom Parker: (FACE is currently done for all game modes, for example, even if it's not apparent to the data team)
* [6:25 AM] martijnverburg: Sorry I’m late - toddler battles!
* [6:26 AM] Bryan McRoberts: Martijn - lol
* [6:27 AM] Tom Parker: Speaking of which. ... Martijn has been suggesting some use of DI, but given that we are so heavily data driven, that is a huge challenge.... I rapidly hit the point where a DI framework is unusable or unruly... so could use a more detailed discussion with Martijn (and others who want to participate) at some point
* [6:27 AM] Bryan McRoberts: Tom - would the leak gate a production release? Or has this not been folded into the master branch yet?
* [6:27 AM] Tom Parker: The leak is in master
* [6:27 AM] Tom Parker: has been for a long time actually
* [6:27 AM] Tom Parker: It shouldn't gate another 6.7.x release
* [6:28 AM] Tom Parker: but should probably gate a 6.8
* [6:28 AM] Bryan McRoberts: Ok
* [6:28 AM] Tom Parker: On the bug front, have addressed some of those, and Marco (one of the new folks that has helped out) diagnosed a few of them to where it appeared to be a data issue
* [6:30 AM] martijnverburg: Yeah I need to understand the code better before making spurious suggestions
* [6:30 AM] Tom Parker: On the new volunteer front for code engagement and retention is a bit of an issue. There aren't a lot of "easy projects" around, and I can point people at some bugs to go look at to start to get familiar with things but that doesn't always lead to them actually looking
* [6:32 AM] Tom Parker: On the wider side of things, there are updated docs on the formula system on the wiki
* [6:32 AM] Tom Parker: As well as a proposal on the CHOOSE replacement (which will need to be tweaked a bit, but gives the general sense for now)
* [6:33 AM] Tom Parker: The new developer startup page is also updated, with a review and some feedback from folks as well
* [6:33 AM] Tom Parker: If anyone has other things to consider for how it might keep (or get) people engaged, let me know
* [6:34 AM] Andrew Maitland: Should we list out useful projects for people to look at?
* [6:35 AM] Andrew Maitland: Like a roadmap with the subtasks looking to accomplish perhaps?
* [6:35 AM] Gwen T: I'd like to see one of our "splash screens" that pop up while loading used for recruitment
* [6:36 AM] Tom Parker: I think the question is what level of detail is needed
* [6:36 AM] Tom Parker: not sure I know, so it needs to be more of a discussion with folks
* [6:37 AM] Tom Parker: otherwise I'm just writing tons of stuff down for no effect
* [6:37 AM] Tom Parker: As far as the splash screen, I'd be cautious about driving more recruitment if we can't retain - we should try to figure out how to retain the trickle we have now before we open a flood gate
* [6:37 AM] Tom Parker: Not sure I have anything else for today
* [6:38 AM] Bryan McRoberts: Is the new developer document on the wiki?
* [6:38 AM] Andrew Maitland: Based upon current code gates to the formula system, where do we see the next production release potentially happening?
* [6:38 AM] Avilay: is there a way to sort of tasks according to urgency?
* [6:39 AM] Andrew Maitland: Avilay - in Jira yes, on the wiki, it's however they are listed out.
* [6:39 AM] Tom Parker: http://wiki.pcgen.org/Basic_Developer_Setup
* [6:39 AM] Tom Parker: JIRA though it a LONG list of items
* [6:39 AM] Tom Parker: with lots of mixes of complexity
* [6:40 AM] Tom Parker: The problem being we don't know the skill set of devs coming in - we've dealt with all levels
* [6:40 AM] Bryan McRoberts: I don't see a link to that on the main wiki page
* [6:40 AM] Gwen T: @AndrewMaitland When we port to Stride, we should look at getting Trillo boards for that!
* [6:40 AM] Tom Parker: Someone who is new to Java probably can't take on a deep diagnosis
* [6:42 AM] Andrew Maitland: I think the retention is at least a two-fold problem
* [6:42 AM] Tom Parker: I'm not sure how to do that balancing without a conversation with those folks, but when I've tended to ask questions about skills et al, so I have a sense of where to start, that seems to drive some away, and at times it feels others go silent when I don't assume they know what they are doing (because they may be an experienced dev but I really don't know that)
* [6:43 AM] Andrew Maitland: Getting set up seems to be a big hurdle (I cannot get set up with the newest Eclipse) as an example. And then getting them plugged into an easy communication with the teams seems to be another part.
* [6:43 AM] martijnverburg: I think a basic tutorial could be written on getting a piece of data from a LST file through to the UI and exported to a character sheet
* [6:44 AM] Tom Parker: @MartijnVerburg Fair point. Part of the challenge being there are a few ways to do it today - one strategic, and some legacy
* [6:45 AM] Tom Parker: I will at least write up the two primary ones
* [6:45 AM] Bryan McRoberts: Martijn - great idea. Something that explains a bonus that has a prereq and how it gets to a character sheet and UI would take a dev through the main functions of the code.
* [6:45 AM] Bryan McRoberts: Same for the new formula code
* [6:45 AM] martijnverburg: Yeah I’ll admit I’m lost on the legacy way vs current way vs proposed future way
* [6:46 AM] Bryan McRoberts: As Andrew noted, making sure the new dev instructions gets someone up and running fairly quickly is paramount
* [6:46 AM] Tom Parker: All a great point. Barring some major issue, I will write that this week
* [6:47 AM] Bryan McRoberts: I'd be a good guinea pig. My build was working, I did an update and now it's broken and I haven't had/made time to figure it out.
* [6:47 AM] martijnverburg: I’ll happily review / try it out as well - happy to write some as well if that helps with the load
* [6:48 AM] Tom Parker: @BryanMcRoberts There are a few situations where an update can break things, and I think you joined when we did one of them
* [6:48 AM] Tom Parker: sorry, LOL not joined
* [6:48 AM] Tom Parker: brought up your dev environment :)
* [6:48 AM] Bryan McRoberts: right :)
* [6:48 AM] Tom Parker: So you may need to delete the project and re-import it as a new Gradle project to get Gradle to behave
* [6:49 AM] Tom Parker: (so delete from eclipse but not from the disk)
* [6:49 AM] Bryan McRoberts: ah
* [6:49 AM] martijnverburg: 👍
* [6:50 AM] Tom Parker: I removed a few key files from git that Gradle can now consistently build correctly, and that breaks you if you didn't realize the impact
* [6:50 AM] Tom Parker: Thankfully those types of rebuild events are rare
* [6:51 AM] Bryan McRoberts: cool
* [6:52 AM] Tom Parker: If it doesn't work for you let me know and we can try to find some time to walk through what is misbehaving
* [6:52 AM] Bryan McRoberts: ok - thanks
* [6:53 AM] Tom Parker: Any other questions or suggestions ?
* [6:53 AM] Andrew Maitland: Tom - on the Jira side, I enabled tasks for data, which allows for sub issues inside on main issue.
* [6:53 AM] Andrew Maitland: Would that be helpful for the code and new tag projects?
* [6:54 AM] Tom Parker: My sense if probably not, but I'll think about it. For the few times I've needed that I've just created a Mini-Project and linked the issues together
* [6:54 AM] Bryan McRoberts: Not from me - great work on the code, Tom. Hopefully Martijn, I and others can become more productive to lessen the load on you.
* [6:54 AM] Andrew Maitland: And the last question Bryan had that we don't have answer for - Production Release?
* [6:55 AM] Bryan McRoberts: Drum roll....
* [6:55 AM] Tom Parker: So my big gates
* [6:55 AM] Tom Parker: FACT / FACTSET needs fixing
* [6:56 AM] Tom Parker: GROUPING needs fixing, since it's a nasty inner class hack at the moment
* [6:56 AM] Tom Parker: I need to fix a Scope/Format issue that impacts what is currently dropIntoContext
* [6:57 AM] Tom Parker: and in the process of changing that convert to getOther instead (better semantics)
* [6:57 AM] Tom Parker: the latter two are needed so we don't end up with MODIFY/MODIFYOTHER statements that I immediately need to break -
* [6:57 AM] Tom Parker: that should all happen in one Alpha cycle
* [6:58 AM] Tom Parker: The GROUPING item is done, but about 4th in line on my local system for pushing
* [6:58 AM] Tom Parker: (I have a HUGE set of interacting PRs, one of which turns out is gated by the FACT fix)
* [6:59 AM] Tom Parker: The Scope/Format fix has had a bunch of the work done in the Formula Library; let me look at whether it is already integrated
* [7:00 AM] Tom Parker: So Scope/Format is partially in the formula library
* [7:01 AM] Tom Parker: I have a few other PRs to go in there, but I try to integrate things that are incompatible interface changes one at a time into the master of PCGen, so avoid confusing myself too much :)
* [7:01 AM] Tom Parker: The other items I need are built, just not Pushed
* [7:01 AM] Tom Parker: So once I get the FACT thing down, it's probably a few weeks to get the rest pushed through. 80% of the work is done and I just get to do a slew of conflict resolution to create valid PRs
* [7:02 AM] Tom Parker: So maybe target moving to Beta in April?
* [7:03 AM] Andrew Maitland: Wow, that's faster than I anticipated.
* [7:03 AM] Andrew Maitland: I guess the better question is what do we expect in the next production release.
* [7:03 AM] Tom Parker: That's a fair question, actually
* [7:04 AM] Tom Parker: The April statement is about as fast as I can do it
* [7:04 AM] Andrew Maitland: If we want single gamemode conversion, then I'm probably going to need a couple of months at least.
* [7:05 AM] Tom Parker: Yea, I'm not sure everything you need for that is April
* [7:05 AM] Tom Parker: I was answering "If you need to get stuff stable enough to be usable, what would it be"
* [7:05 AM] Tom Parker: Not "If PF conversion will be complete, what is the date"
* [7:06 AM] Tom Parker: At the same time, I'm not sure we should get a full conversion done
* [7:06 AM] Tom Parker: There are 2 or 3, perhaps 4 changes that are very likely to break PCs
* [7:06 AM] Andrew Maitland: Question to the group - Push out a stable 6.08 quickly, and focus on Code Formula completion and data conversion for a 6.10?
* [7:06 AM] Tom Parker: The problem being that PCGen today discards information based on how it stores PCs
* [7:07 AM] Tom Parker: A classic example is Domain is only loosely stored to the Class... but it's hard to do a dual class with two Domains
* [7:07 AM] Bryan McRoberts: It'd be nice to get a prod release out since it's been so long and a lot of data work has been done.
* [7:07 AM] Andrew Maitland: Agreed.
* [7:07 AM] Tom Parker: When we fix that, the PCG file format would need to change, and then we end up with a compatibility gap during load
* [7:07 AM] Tom Parker: The Domain one we probably just let break and people re-select the Domain - pretty innocent
* [7:07 AM] Tom Parker: But they become more invasive from there
* [7:08 AM] Bryan McRoberts: I don't think anyone would complain about a prod release soon-ish and another one in April/May.
* [7:08 AM] Tom Parker: I'm not prepared for one soon-ish
* [7:08 AM] Tom Parker: (under that definition of soon-ish)
* [7:08 AM] Bryan McRoberts: Ok - so there are current code issues gating a release from master?
* [7:09 AM] Tom Parker: The 3 I listed a bit ago
* [7:09 AM] Tom Parker: The "big gates"
* [7:09 AM] Andrew Maitland: We fix those 3, Push out a Production 6.08.00 May 15th, since we need at least 1 RC?
* [7:09 AM] Gwen T: I'd love to see a stable 6.8 as soon as reasonable. 2/3 of the issues I run across are because folks only like to use the "stable" versions. Currently, that's 6.06.01, released 2016-07-30
* [7:10 AM] Bryan McRoberts: Ok - I thought those were related to dev efforts aimed at an April release.
* [7:10 AM] Gwen T: We've killerd a lot of bugs since then!
* [7:10 AM] Tom Parker: Gwen has a good point
* [7:10 AM] Tom Parker: Andrew, I think it's better to call out early may for RC1
* [7:10 AM] Bryan McRoberts: Would it be work putting out just a data release?
* [7:10 AM] Tom Parker: and then go from there
* [7:11 AM] Andrew Maitland: Agreed, people don't touch the latest releases, and we get a lot of redundant reports.
* [7:11 AM] Tom Parker: We can't really do just a data release
* [7:11 AM] Tom Parker: the data is compatible with the current code, not the 6.6 code
* [7:11 AM] Bryan McRoberts: Ah
* [7:11 AM] Andrew Maitland: We can, but it gets sloppy... so a nice clean prod release
* [7:11 AM] Andrew Maitland: I'm still getting Starfinder 1.6 bug reports. :(
* [7:12 AM] Paul Grosse: And we are going to definitely want to have SF in the prod release. :)
* [7:12 AM] Andrew Maitland: Okay, Target May/June for 6.08.00 release.
* [7:12 AM] Bryan McRoberts: Sounds good
* [7:13 AM] Andrew Maitland: That means we drop Alpha and switch to Beta no later then end of April.
* [7:14 AM] Gwen T: That SHOULD allow for at least a couple RCs, if not a final version, in time for the summer conventions.
* [7:14 AM] Andrew Maitland: We've gone over time a bit, but any questions from anyone else before we close this up?
* [7:16 AM] Andrew Maitland: Thanks for coming everyone. Meeting adjourned - **Bangs Gavel**

Meeting 2018 01 13

2018-02-24T16:56:42Z

LegacyKing: Created page with "''Attendance:'' * Chair - Bryan * Arch - Tom * Content - Gwen * PR - Paul * Observer - Several Team members and general users ''Summary:'' * PCGen is still an active project..."

''Attendance:''
* Chair - Bryan
* Arch - Tom
* Content - Gwen
* PR - Paul
* Observer - Several Team members and general users

''Summary:''
* PCGen is still an active project with an influx of old and new team members
* Java is still the prefered language because a re-write will take a large chunk of time
* Get Code team back up and running and implement Tom's Formula system
* Migrate server from Anestis to Stefan
* Start recruitment drive for Data, Code, Webmasters, Architecture, & Documentation
* Clean up and update documentation on contributing code and data, setting up dev environment

"Raw Log"
*[09:06] <Bryan> Yeah - let's get started
*[09:06] <Bryan> Let me grab the agenda from the meeting announcement
*[09:06] == Strato [535b3d8a@gateway/web/freenode/ip.83.91.61.138] has joined #pcgen
*[09:07] <Bryan> 1) Current PCGen Status - Are we still active or is it time to retire the project?
*[09:07] <Tom[Arch_SB]> df
*[09:07] <Gwen> I know the first issue we face is that there has been very little support of the project as a whole.
*[09:07] <Bryan> PCGen has been around for a long time.... 17+ years if my math is right.
*[09:08] <[OGL]Nylanfs> 20
*[09:08] <[OGL]Nylanfs> You first released in aug 1998 :)
*[09:08] <@Zaister> I'm sorry that I have been inactive recently - my job demand a lot more time than previously, but I still hope to keep contributing
*[09:08] <Bryan> Really??? Oh boy...
*[09:08] <Tom[Arch_SB]> :)
*[09:08] <Bryan> It's come a long way since I first posted it on ENWorld
*[09:08] == Strato_ [535b3d8a@gateway/web/freenode/ip.83.91.61.138] has joined #pcgen
*[09:09] <Bryan> A *lot* of people have contributed to it and made it *way* better than I could have ever on my own
*[09:09] <Bryan> I still use it for my own campaigns and clearly lots of other people do too
*[09:09] <karianna> I'm also constrained (as I foolishly took on the CEO role at my company), but have started a new D&D group with my Chief Scientist as a member and he's also willing to chip in a little.
*[09:09] <Gwen> Personally, I see our biggest need as recruitment of volunteers, both CODE and DATA.
*[09:10] <Bryan> To be active, we need people involved in each of the categories
*[09:10] <[OGL]Nylanfs> We got quite a bit of responses on the FB posts about it. Most were positive about keeping it running
*[09:10] <@Zaister> I can still work on both code and data
*[09:10] <Bryan> I think that having made the issue known that we need help, people have responded (myself included).
*[09:10] <Bryan> So it sounds like a resounding yes, let's remain active.
*[09:11] <karianna> There I can help for sure (Java recruitment), but we'll need to improve the CONTRIBUTING.md and wiki docs so that new coders know what parts of hte code base are legacy (don't touch) and what parts are new (along with a guide on how to contribute to that newness)
*[09:11] <Gwen> I'm happy to teach new data monkeys, if we can drum a few up who will last longer than a month ot so.
*[09:11] <@Zaister> I'M all for it
*[09:11] <Bryan> Karianna - very good points.
*[09:11] == Strato [535b3d8a@gateway/web/freenode/ip.83.91.61.138] has quit [Ping timeout: 260 seconds]
*[09:11] <Bryan> I just got reinvolved in the coding and it was a large hurdle to get to the point where I could debug/commit
*[09:11] <karianna> I'm willing to Pair with Tom and other coders to write those docs (I'm effectively a new developer to the project now)
*[09:11] <Bryan> That hurdle has to be lowered/removed.
*[09:12] <@Zaister> yeah it's difficult to get in
*[09:12] <Bryan> Karianna - Andrew was very helpful, so you might pair with him.
*[09:12] <Bryan> If you could do that, let's improve that documentation as a high priority.
*[09:12] <karianna> Right, and the complexity is mostly needed because we're doing some formal methods of computer science graph modelling here amongst other things.
*[09:12] <karianna> Oh and LST is a turing complete language :-O
*[09:12] <@Zaister> cool
*[09:12] <Avilay> i going to be rather busy too for next 3 years as i be doing a double phd. but on sunday's i can get some time to work on pcgen and my other project
*[09:13] <Bryan> All in favor of PCGen remaining active, say Aye
*[09:13] <karianna> Aye!
*[09:13] <@Zaister> Aye
*[09:13] <Gwen> Aye!
*[09:13] <rfinch> Aye!
*[09:13] <[OGL]Nylanfs> Aye
*[09:13] <Avilay> definitely a YES
*[09:13] <Bryan> All opposed say Nay
*[09:14] <Tom[Arch_SB]> I'm Aye as well, just didn't type fast enough :P
*[09:14] <Avilay> bryan wants to retire. :p
*[09:14] <Bryan> Congatulations, the Ayes have it, so PCGen will remain active. :)
*[09:14] <Avilay> though i c++ coder camp, definitely not java
*[09:14] <@Zaister> good
*[09:14] <Bryan> 2) If #1 is Active, then restructure discussions and recruiting coders (Java or next gen C++/C#) OR retire the project and restart with new Language and Open Source License (LPGL is a bit restrictive, and was thought to be only for libraries according to others)
*[09:15] <Bryan> So is there any appetite for re-writing the project in a different language? This would be a massive effort.
*[09:15] <Tom[Arch_SB]> I really don't think language is the issue
*[09:15] <@Zaister> Restarting would certainly be interesting and would bring in opportunities for cleanup we'd not have otherwise
*[09:15] <Bryan> Tom, I agree.
*[09:16] <@Zaister> Java has the platform mobility advantage
*[09:16] <[OGL]Nylanfs> Right, but with volunteers only this could take a LOG time
*[09:16] <Tom[Arch_SB]> @Zaister... not sure. If we really want a "hard fork" so to speak, we could just delete the code we don't like and fix what is then missing
*[09:16] <Tom[Arch_SB]> doesn't require dumping the language to do that
*[09:16] <@Zaister> however, Java keeps being problematic with HiDPI monitors
*[09:16] <Tom[Arch_SB]> (and I'm not advising that, just observing)
*[09:16] <karianna> That's all fixed in 9+
*[09:16] <karianna> That's all fixed in 9+ (monitor issues)
*[09:16] <Bryan> Restarting, even in the same language, would be a huge step back in functionality that would take a long time to catch up to where PCGen is now.
*[09:17] <@Zaister> oh, cool
*[09:17] <[OGL]Nylanfs> That's fixed if we redo the gui in JavaFX
*[09:17] <Tom[Arch_SB]> So that is one gap we have
*[09:17] <Gwen> Personally, I think a new language would be ideal, especially if it offers mobile options, BUT it should be a longer-term project. Fix what we have for now, while we develop in a newer language
*[09:17] <karianna> I've been involved in massive re-writes before and it almost never ends well
*[09:17] <Tom[Arch_SB]> UI design has never been an area I've coded
*[09:17] <Tom[Arch_SB]> Well, not well anyway ;)
*[09:17] <@Zaister> we could really use app suppport these days
*[09:17] <[OGL]Nylanfs> I think there's an issue with Swing and 9+
*[09:18] <@Zaister> put ypour csheet on your mobile device, active temp bonuses on the fly etc
*[09:18] <@Zaister> that would be awesome
*[09:18] <[OGL]Nylanfs> There's a couple of indepentant app's thar import pcgen files or output
*[09:18] <@Zaister> yeah but probably static
*[09:18] == Luigi [beeccb44@gateway/web/freenode/ip.190.236.203.68] has quit [Quit: Page closed]
*[09:18] <rfinch> They do not allow for applying temp bonuses however, you need to export a copy of the sheet with them on and switch, its cludgey
*[09:18] <karianna> So Swing is no longer supported by Oracle (e.g. they won't fix or enhance it). That said OpenFX / JavaFX is not necessarily well supported either (by a major vendor).
*[09:19] <Bryan> Zaister - that sounds like a separate app.
*[09:19] <@Zaister> yeah
*[09:19] <Tom[Arch_SB]> @Zaister - I think it's an open question whether there is enough need for overlap with the core code... yea, what Bryan just typed
*[09:19] <Bryan> I think PCGen itself needs to be focused on the PC
*[09:19] <@Zaister> so it would be advantageous to use a code base that couls be used for mobile devices somehow
*[09:19] <Bryan> And we can have someone who is interested write an app for that functionality
*[09:19] <karianna> One option is that if the API is well defined enough we can use a JSON Binding/Parsing Lib like Jackson and an embedded web server like Jetty/Tomcat and Voila we could build a browser based UI for PCGen that can run from a desktop
*[09:19] <@Zaister> ah good idea
*[09:19] <Bryan> Karianna - excellent idea
*[09:20] <Gwen> PC focus is what I'm planning for the next several source. LITE versions that only include the info for "official" PC races.
*[09:20] <karianna> Browser based will be an easier skill set to recruit for and we could then also HTML5 app it for mobile and run PCGen as a service
*[09:20] <karianna> grand ideas.
*[09:21] <Bryan> Does anyone have any questions or comments before we vote on whether or not to rewrite in another language?
*[09:21] <Avilay> concern: how to make ui for tiny screen, when we work with huge amount of information, and normally have pcgen window maxed at hd resolutions
*[09:21] <karianna> I think completing Tom's excellent work on formula and CDOM etc comes first though
*[09:21] <@Zaister> yes
*[09:21] <Gwen> Would the costs be higher for a browser-based version?
*[09:21] <Tom[Arch_SB]> define cost
*[09:21] <karianna> Avilay - progressive disclousre
*[09:22] <Bryan> Gwen, what costs are you referring to?
*[09:22] <Gwen> Bandwidth, server space, etc?
*[09:22] <Avilay> definitely have 2 sets of ui, one for mobile and one for hd screens
*[09:22] <Tom[Arch_SB]> probably more disk space
*[09:23] <[OGL]Nylanfs> Also if it were a service how would homebrew be handled?
*[09:23] <Tom[Arch_SB]> but I don't know enough to ballpark the difference
*[09:23] <Tom[Arch_SB]> Not sure this is a service as in online
*[09:23] <karianna> Nylanfs - upload your homebrew (with your user account)
*[09:23] <Bryan> This agenda item is 2-fold. Do we maintain/fix the existing code base (java) or rewrite (either in java or another language)
*[09:23] <Tom[Arch_SB]> I think karianna was proposing we use the browser but it targets a local web server
*[09:23] <Tom[Arch_SB]> Bryan, hold on one sec
*[09:23] <karianna> And Tom is correct, local user desktop browser first
*[09:24] <karianna> PCGen as a Service much later on
*[09:24] <Gwen> OR, are we talking about PCGen being a program that runs locally, but displays in a browser?
*[09:24] <karianna> Gwen - yes
*[09:24] <[OGL]Nylanfs> Ahh okay got it
*[09:24] <@Zaister> SAS would be problematic as we would have to offer it as a free service
*[09:24] <Gwen> Sorry, took me a second.
*[09:24] <karianna> No problem - I explained it poorly
*[09:25] == JOhn [4cd99f59@gateway/web/freenode/ip.76.217.159.89] has joined #pcgen
*[09:25] <Tom[Arch_SB]> ok, I think that clears it up enough, thanks for the pause Bryan
*[09:25] <@Zaister> ok
*[09:25] == JOhn has changed nick to Guest51542
*[09:25] <Avilay> homebrew on webserver based apps is going to be challenging
*[09:25] <Bryan> The question I'd like to pose is whether or not we want to maintain or abandon the current code-base.
*[09:25] <Bryan> In the short-term.
*[09:26] <karianna> It's a trick we use for jClarity. We write the server/core code in Java, define the API in Java and auto generate a Javascript API via Jackson and various Java EE or Spring annotations. Then the browser just thinks it's talkin to a Javascript backend
*[09:26] <Gwen> What benefits specifically would a local run/browser displayed version?
*[09:26] <Bryan> Long-term is a different animal.
*[09:26] <karianna> Bryan - I'd keep what we have
*[09:26] <@Zaister> I think so too
*[09:26] <karianna> Bryan - I'd keep what we have but document how to work in it and as Tom suggested on anotehr thread, start deleting the deprecated stuff
*[09:26] <karianna> There's 20 years of history in that code, very hard to reproduce that konwledge again
*[09:26] <Bryan> Ok - so all in favor of keeping our current code-base, say Aye
*[09:27] <Tom[Arch_SB]> same, but I'll need to learn from karianna here - outside my historical experience working with web UI
*[09:27] <@Zaister> migrating in place to newer stuff
*[09:27] <Tom[Arch_SB]> Aye
*[09:27] <[OGL]Nylanfs> Aye
*[09:27] <karianna> Aye
*[09:27] <Gwen> aye
*[09:27] <@Zaister> Aye
*[09:27] <Bryan> All opposed say Nay
*[09:27] <Bryan> Ok - so we keep the current code base, and Karianna's suggestion to delete deprecated code is excellent
*[09:28] <Tom[Arch_SB]> Can we delve into that for a minute?
*[09:28] <[OGL]Nylanfs> Yep, rip and fix what breaks. :)
*[09:28] <Bryan> Moving to a service based system can be on a future agenda
*[09:28] <karianna> If we move to Java 9 then we can use it's new deprecation system
*[09:28] <@Zaister> sounds good
*[09:28] <Tom[Arch_SB]> So on the deprecation, right now if we rip any of it out, things break
*[09:28] <karianna> Tom - yep, can you re outline what you said in the mail thread a few days ago?
*[09:29] <@Zaister> is there an openjdk for Java 9 yet?
*[09:29] <Tom[Arch_SB]> and we dont' always know what those things are (the deprecated code isn't 100% code coverage
*[09:29] <karianna> Zaister - yes
*[09:29] <@Zaister> good
*[09:29] <karianna> Zaister - I run the build farm for it :-)
*[09:29] <Tom[Arch_SB]> So any ripping involves replacing or we don't have working code
*[09:29] <@Zaister> ah :)
*[09:29] <@Zaister> karianna: I'm on Gentoo linux so I'll have to build it
*[09:29] <karianna> Tom - right, that's where the new deprecation system in Java 9 is super useful
*[09:30] <Tom[Arch_SB]> Up to this point, for the last probably 6 years anyway, we have kept one branch - always working code, no major fork with work
*[09:30] <Tom[Arch_SB]> So if that's going to change, it should be conscious
*[09:30] <karianna> you can annotate things as "We have a known good replacement", "This is obsolete", "This will be removed next release" so on and so forth
*[09:30] <@Zaister> cool
*[09:30] <karianna> Tom - I think we can still work on one branch
*[09:31] <karianna> Tom - I think we can still work on one pcgen canonical branch, as long as folks keep to the practice of brancjing locally and PR'ing from there
*[09:31] <Tom[Arch_SB]> @karianna okay, we'll have to talk on that, most of our stuff is replacement at a very high level - so will be interesting to learn how to tag stuff and how useful it would be
*[09:31] <Bryan> That's implementation details - let's stick to big picture items here
*[09:31] <@Zaister> yeah
*[09:31] <karianna> yep
*[09:31] <Tom[Arch_SB]> ok
*[09:31] <Bryan> I have to leave in 30 minutes, so I want to push things along :)
*[09:31] <Bryan> The next item Andrew had was team restructuring
*[09:32] <Bryan> Clearly the teams had become depleted, but the call for help has had some good success
*[09:32] <Bryan> So who are the data monkeys and their leadership?
*[09:32] <karianna> Gwen?
*[09:32] <@Zaister> I thing Doug is the leader
*[09:32] <Avilay> oki. so no migration from java
*[09:33] <Avilay> i continue lurker in the shadows watching :)
*[09:33] <Bryan> Avilay - correct, we're sticking with the current code base
*[09:33] <Gwen> I'm Data Second
*[09:33] <[OGL]Nylanfs> Andrew, Gwen, Regan, And a few others
*[09:34] <[OGL]Nylanfs> I'd have to check the data commits
*[09:34] <@Zaister> I do data too
*[09:34] <Bryan> It sounds like data is fairly active. Would you agree Gwen?
*[09:34] <Tom[Arch_SB]> I'm not sure I always know the real names vs the userids :)
*[09:34] <Gwen> Yes.
*[09:34] <Bryan> Tom - I sure don't know real names either!
*[09:35] <Bryan> Does anyone think the data team needs restructuring?
*[09:35] <Gwen> This week I finished Bestiary 4, Familiar Folio, and am almost done with a LITE version of Monster Codex
*[09:35] <Bryan> I'm impressed! Thanks for all your effort!
*[09:35] <@Zaister> cool
*[09:36] <[OGL]Nylanfs> The data team will always have the highest amount of turn over
*[09:36] <Gwen> I had 2 weeks off of work....
*[09:36] <Avilay> i wish with java coders the best in updating pcgen
*[09:37] <Bryan> How many people here can be active on data, even if its just intermittent?
*[09:37] <@Zaister> here
*[09:37] <[OGL]Nylanfs> So keeping Andrew and lead (telling the monkeys what's needed) and Gwen picking up the odd pieces and user support in Hipchat has worked really well
*[09:37] <@Zaister> sounds good
*[09:37] <[OGL]Nylanfs> I'm been having a hard time conceptually with data since we started using categories :(
*[09:37] <Bryan> We need more than Andrew and Gwen. Zaister can help. anyone else?
*[09:38] <Bryan> Sounds like a documentation issue, Nylanfs
*[09:38] <sethj11> i'd prefer to work on code, but i can learn data instead if that's needed
*[09:38] <Bryan> sethj11 - we'll circle back on that after we talk code team
*[09:39] <Tom[Arch_SB]> Bryan there are other data folks that just may not be here
*[09:39] <karianna> There seem to be a lot of data PR's - I'd argue it's pretty good progress
*[09:39] <Tom[Arch_SB]> What @karianna said
*[09:39] <Bryan> I'd like anyone who is willing to help with data to contact Andrew Maitland on HipChat/email/etc
*[09:39] <Gwen> I was wondering if we could add a recruitment ad to the download pages or to a PCGen loadscreen? We used it for years and didn't realize it was all volunteer until a couple years ago.
*[09:39] <karianna> The docs not being updated is a concern for me though - that LST documentation was a jewel in hte crown of PCGen
*[09:39] <Bryan> Lets talk documentation
*[09:39] <karianna> Gwen - great idea
*[09:40] <Bryan> As Karianna said, documentation is *very* important
*[09:40] <@Zaister> Sp we'd need to collect the changes and then update the docs. I could do that
*[09:40] <[OGL]Nylanfs> Yea Regan isn't here, there's at least two others that are fairly active that Ican't think of at the moment
*[09:40] <Bryan> And as Nylanfs indirectly said, it's important not just for users, but for coders and data monkeys as well
*[09:40] <Bryan> Do we have any formal documentation monkeys?
*[09:40] <Gwen> My 2 cents.... I use the LST Tag Index almost daily and it's a bit arcane and VERY out of date.
*[09:41] <@Zaister> I think Eric ist still lited as the doc monkey
*[09:41] <@Zaister> *listed
*[09:41] <Bryan> Any doc monkeys here?
*[09:41] <[OGL]Nylanfs> There isn't anybody actively working on docs
*[09:41] <@Zaister> I've done docs
*[09:41] <[OGL]Nylanfs> currently
*[09:41] <Bryan> Zaister - looks like you're nominated
*[09:41] <@Zaister> heh
*[09:42] <Bryan> Zaister - we need documentation for categories and update the out-of-date LST syntax
*[09:42] <Bryan> Gwen and data monkeys, please inform Zaister of any incorrect or incomplete LST documentation
*[09:42] <@Zaister> with categories you mean for ability objects?
*[09:42] <[OGL]Nylanfs> LiaungYip did have some good ideas on how to redo the documentation
*[09:42] <Bryan> Zaister - how do you prefer to be contacted?
*[09:42] <@Zaister> hipchat is probably easiest
*[09:42] <Bryan> Zaister - yeah categories on the ability objects
*[09:43] <Tom[Arch_SB]> Bryan - the data monkeys can do that, but there is another place to start
*[09:43] <karianna> I used to do docs, my issue is that I'm not familiar with the LST stuff anymore to update that side of things
*[09:43] <Tom[Arch_SB]> When we converted to JIRA, there is a specific workflow for creating tokens that impact data
*[09:43] <@Zaister> I'm usually online here too though
*[09:43] <Tom[Arch_SB]> Each of those has a state "documentation required" or some such... so any of the NEWTAG-X entries in that state mean doc updates are required
*[09:43] == Strato_ [535b3d8a@gateway/web/freenode/ip.83.91.61.138] has quit [Ping timeout: 260 seconds]
*[09:43] <Bryan> Ok - Zaister, do you have access to the PCGen JIRA?
*[09:43] <@Zaister> sure
*[09:44] <Bryan> Tickets can be created/tracked there.
*[09:44] <@Zaister> Bryan: I've been using that for years
*[09:44] <Bryan> Gwen and others - do you know how to create the tickets to track badly documented LST tokens?
*[09:44] <Gwen> So we use DOCUMENTATION in JIRA to alert @Zaister of LST doc issues?
*[09:44] <Gwen> Yes
*[09:44] <@Zaister> good
*[09:45] <Gwen> Well, I do. Not sure about others, but I can teach them if need be.
*[09:45] <Bryan> Okay - so Zaister is in charge of documentation. Thanks for your willingness to help!
*[09:45] <@Zaister> Gwen: if you can, put the teaching on the wiki
*[09:45] <Bryan> I can't understate how important and crucial documentation is!
*[09:45] <[OGL]Nylanfs> I remember the first documentation you made for PCGen. :)
*[09:45] <Bryan> Gwen and others, as we come across documentation needs, create a ticket so Zaister knows what needs to be done and it can be tracked.
*[09:46] <Gwen> OK. I can do that! I'll get together with Andrew and set up a section to teach.
*[09:46] <Bryan> Nylanfs - no one needs to be reminded of that... :D
*[09:46] <@Zaister> cool
*[09:46] <Bryan> Lets try to recruit help for Zaister so we don't burn out a single monkey.
*[09:46] <Bryan> On to the code team
*[09:47] <Bryan> Tom - you're Code SB, are you willing and able to remain in charge of code?
*[09:47] <Tom[Arch_SB]> y
*[09:47] <@Zaister> Code is now merged with Arch, right?
*[09:47] <karianna> I think it should be yes
*[09:47] <Tom[Arch_SB]> I think that would be a good change yes
*[09:48] <Tom[Arch_SB]> Arch can be a 2nd under Code just like Content has different 2nds
*[09:48] <@Zaister> yes
*[09:48] <Bryan> So we want a Code SB and an Arch SB?
*[09:48] <Tom[Arch_SB]> No
*[09:48] <Tom[Arch_SB]> Code SB
*[09:48] <Tom[Arch_SB]> Arch 2nd
*[09:48] <Tom[Arch_SB]> and Code 2nd
*[09:48] <Tom[Arch_SB]> or some such
*[09:48] <Bryan> Ah
*[09:48] <Tom[Arch_SB]> if we have enough folks to cover those
*[09:49] <Tom[Arch_SB]> which means my nick is wrong ... ;)
*[09:49] <Bryan> So do you want to be Code SB or Arch 2nd?
*[09:49] == Tom[Arch_SB] has changed nick to Tom[Code_SB]
*[09:49] <@Zaister> I'm still available for code
*[09:49] <Bryan> lol
*[09:49] <Tom[Code_SB]> Code SB
*[09:49] <Bryan> Okay - that answers that :)
*[09:49] <Bryan> Karianna - any chance you could be Arch 2nd?
*[09:50] <Bryan> Who all can help with coding? I'm getting involved there again.
*[09:50] <karianna> I assume we want developer guide documentation to be GitHub based?
*[09:50] <karianna> starting with CONTRiBUTING.md?
*[09:50] <Bryan> Karianna - yes
*[09:51] <@Zaister> we also have the wiki
*[09:51] <Tom[Code_SB]> Yea, there is stuff under Architecture and Code on the wiki
*[09:51] <Tom[Code_SB]> and reading the developer meeting logs would be useful for folks
*[09:51] <Tom[Code_SB]> I think a lot of where we are/where we are going is there and we need to decide if it's worth rewriting that or just pointing to the log
*[09:51] <@Zaister> I think we maintain the wiki and point there from GitHub
*[09:52] <Avilay> i can give input on design (non-java), which would be little it seems from the wiki content i read
*[09:52] <Bryan> we can get into the specifics of roles, but let's stick to who-is-on-what-team for now
*[09:53] <Bryan> I have to leave in about 8 minutes... so let's nail down who is on the code team
*[09:53] <Bryan> you guys can continue the discussions after I leave...
*[09:53] <@Zaister> I'd like to keep being on there
*[09:53] <sethj11> I'd like to be on code team, though by wiki standards I'm like sub-lemur. Plus I'm learning Java.
*[09:54] <Bryan> I have a former co-worker who is willing to help as well with coding
*[09:54] <Tom[Code_SB]> @Avilay a lot of the arch stuff is really not code specific
*[09:54] <Tom[Code_SB]> but it does require understanding the concepts of what we need to do
*[09:54] <karianna> hello?
*[09:54] <Bryan> sethj11 - I'd like us to get the code to a place where a new java coder can make sense of the code
*[09:54] <Tom[Code_SB]> so there is opportunity there as well that is independent of code
*[09:54] <Bryan> Hi Harianna
*[09:54] <Bryan> I mean, Karianna...
*[09:55] <[OGL]Nylanfs> Kar, you mean based around submitting and using Github, as opposed to keeping the guide IN github?
*[09:55] <Avilay> @tom, that is what i referring to. the non-coding content i can work with
*[09:56] <Tom[Code_SB]> okay, we can find time to talk - nice to have someone to bounce ideas/concerns off of
*[09:57] <Avilay> yep. i rather long time lurker in hipchat.
*[09:57] <Bryan> In any event, it seems that Andrew's concern was Tom was the only code monkey for quite some time.
*[09:57] <@Zaister> yeah as i said i war rather inactive for the last year
*[09:57] <@Zaister> *was
*[09:58] <Bryan> So the code team was in danger of becoming inactive, based solely on what time Tom had to offer (this is just volunteer effort!)
*[09:58] <Bryan> So now we have some new people who can help, which is great.
*[09:58] <[OGL]Nylanfs> Yes, with active code the data will largely sort itself out. :)
*[09:58] <Bryan> Karianna, if you could pair with Andrew and Tom to get new developer documentation put together, that would be tremendously important
*[09:58] == karianna [97e4f0e4@gateway/web/freenode/ip.151.228.240.228] has quit [Ping timeout: 260 seconds]
*[09:59] <Bryan> as we want to recruit more people and get them active without turning them off due to the difficulty of getting an env set up
*[09:59] <Bryan> We lost Karianna...
*[09:59] <@Zaister> Kar seem to have technical problems
*[09:59] <Bryan> Anyway - Tom, can you reach out to Karianna on the documentation for new developers? I had a lot of problems and Andrew was able to talk me through them.
*[10:00] <Tom[Code_SB]> yep
*[10:00] <Bryan> Other developers might have just given up, especially for a volunteer project.
*[10:00] <Bryan> Cool.
*[10:00] == karianna [~karianna@97e4f0e4.skybroadband.com] has joined #pcgen
*[10:00] <Bryan> That's all the time I have. Thanks again everyone for all your effort and interest in PCGen!
*[10:00] <[OGL]Nylanfs> We want the entry as easy as possible, just like a pitcher plant
*[10:01] <Avilay> wb karianna
*[10:01] <@Zaister> Thanks fo moderating!
*[10:01] <Bryan> Karianna - reach out to Tom and Andrew to help with the new-developer-documentation
*[10:01] <Gwen> It sounds like our biggest hurdle in ALL the teams is recruitment. @Nylanfs can you handle that and, if so, what support/assistance do you need?
*[10:01] <karianna> Hmm, I missed the last 6 mins :-/, is there an archive view?
*[10:01] <Bryan> And if we can find some doc monkeys to help Zaister, that would be awesome.
*[10:01] == distant-scholar [ac066da2@gateway/web/freenode/ip.172.6.109.162] has joined #pcgen
*[10:01] <[OGL]Nylanfs> I have the log
*[10:01] <Bryan> People can be on more than one team (for those who want to help with data and code and documentation or some combination)
*[10:02] <[OGL]Nylanfs> Hiya Doug
*[10:02] <Bryan> I just should not ever have anything to do with documentation.
*[10:02] <distant-scholar> Hello, each.
*[10:02] <[OGL]Nylanfs> heh
*[10:02] <@Zaister> Bryan I've been "full stack" on PCGen for several years :)
*[10:02] <Bryan> Thanks again everyone!
*[10:02] <Bryan> @Zaister - awesome! I'll stick to code only...
*[10:02] <@Zaister> :)
*[10:02] <karianna> Thanks all - nice to see the renewed interest and support
*[10:02] <Avilay> thanx for coming bryan
*[10:03] <Bryan> You can keep discussing but I need to bow out. bye!
*[10:03] == karianna [~karianna@97e4f0e4.skybroadband.com]
*[10:03] == realname : Martijn Verburg
*[10:03] == channels : #pcgen
*[10:03] == server : adams.freenode.net [Budapest, HU, EU]
*[10:03] == End of WHOIS
*[10:03] <Bryan> I'll leave myself logged in so I can read what was said...
*[10:03] <Bryan> afk
*[10:03] <[OGL]Nylanfs> So we need people for data, documentation, & code
*[10:04] <[OGL]Nylanfs> We also need to move the server.
*[10:04] <Avilay> <---- architecture/design stuff (no coding)
*[10:04] <Gwen> I'd also like some folks to help test what is being produced. No coding or programming experience needed!!
*[10:05] <Tom[Code_SB]> I think the server move needs to be high priority
*[10:05] <[OGL]Nylanfs> we have enough monthly donations come in that I think we can afford to pay for what we need
*[10:05] <Avilay> i always have the latest develop package
*[10:05] <[OGL]Nylanfs> Arch we need the people to already be familiar with the guts and not new volunteers
*[10:06] <Tom[Code_SB]> @Nylanfs not always
*[10:06] <[OGL]Nylanfs> at least that's how percieve it
*[10:06] <Tom[Code_SB]> "guts" is relative
*[10:06] <Tom[Code_SB]> Some of it is very conceptual software design work
*[10:06] <karianna> The server is on Anesitis’s hosting provider right?
*[10:06] <Tom[Code_SB]> I have these 16 requirements - which of the tradeoffs do we make architecturally
*[10:06] <Gwen> An aside.... Any donors that want data, like an ability, monster, etc... I'd be happy to hook them up. They support us, we should support them!
*[10:06] <Avilay> oki. no hassle then. remove me then
*[10:06] <Tom[Code_SB]> @karianna yes
*[10:07] <Tom[Code_SB]> Avilay, don't think you need to be removed
*[10:07] <Tom[Code_SB]> Let's talk before you make those decisions
*[10:07] <Tom[Code_SB]> so you can have a sense of what the issues are and what you need to know
*[10:08] <[OGL]Nylanfs> Mostly I was thinking that the arch person needs to be familiar with where we were and where we are going, which somebody new might not be familiar with
*[10:09] <Avilay> anyway. i busy with my own c++ pc manager project, just means i spend more time on it, and follow design concepts, etc of pcgen and use what can work for my project to solve my custom campaigns i play in
*[10:09] <Gwen> Oh! @Tom!! Andrew was discussing a move towards a more "agnostic" architechture.
*[10:09] == Rfinch-mob [2ed0086f@gateway/web/freenode/ip.46.208.8.111] has joined #pcgen
*[10:09] <Tom[Code_SB]> It can be really useful to have someone who doesn't know the guts and thus asks questions
*[10:09] <Tom[Code_SB]> since there is no assumption they can have about what it does today
*[10:10] <Tom[Code_SB]> @Gwen, not sure what that means...
*[10:10] <karianna> Zaister - were you volunteering to take over the server? I forget.
*[10:10] <@Zaister> Yes I was, but I'm not sure I can get it all to run on my own
*[10:10] <[OGL]Nylanfs> He was, but I think needed the requirements of the server from Anestis?
*[10:10] <Gwen> He was saying it shouldn't be d20 based. That it should be able to handle a wider assortment of games.
*[10:10] <@Zaister> The old server uses CPanel
*[10:10] <Tom[Code_SB]> Right
*[10:11] <Tom[Code_SB]> yes, I agree. I have systems I'd like to run in PCGen that I can't today
*[10:11] <Tom[Code_SB]> but it's "one step at a time"
*[10:11] <Tom[Code_SB]> @Zaister we can move one item at a time - did you get my instructions on what Jenkins needed?
*[10:11] <Gwen> I agree, but wanted to be sure that the Arch team is looking in that direction as they move forward.
*[10:11] <@Zaister> Tom: I think I have them somewhere, yes, but I haven't acted on them
*[10:12] <Tom[Code_SB]> @Gwen The new formula system gets pretty "agnostic" already...
*[10:12] <Tom[Code_SB]> The UI then becomes the constraint
*[10:12] <Tom[Code_SB]> Which is why a UI focus will be needed once we manage to rip out the old formula and export systems
*[10:12] <Tom[Code_SB]> I have ideas there, just held close to the vest so as to not set anyone's expectations it will come soon
*[10:13] <karianna> Zaister - what wuold you be hosting on? Hetzner?
*[10:13] <[OGL]Nylanfs> We get between $5-20ish USD per month, which could be increased if we put out more calls for donating
*[10:13] <Tom[Code_SB]> What @karianna has talked about with the web UI would help a lot, and ... let's just say it's likely to work really well along the direction I was thinking we needed to go
*[10:13] <Gwen> No problem. Just trying to give Andrew a voice here. I only JUST understand the "agnostic" engine concept.
*[10:13] <@Zaister> karianna yes that is my hoster
*[10:14] <karianna> OK, we use them at jClarity - I like them
*[10:14] <karianna> If you’re happy providing me ssh access then I could help you with various migrations?
*[10:14] <karianna> I’m a fan of pairing on these things
*[10:14] <PapaDRB> exit
*[10:14] <karianna> My Chief Scientist (john) is also a bit of a devops guru
*[10:14] == PapaDRB [~Papa-DRB@pool-100-40-193-73.pghkny.fios.verizon.net] has quit [Quit: ~ Trillian Astra - www.trillian.im ~]
*[10:14] <@Zaister> yes, why not
*[10:14] <karianna> so he cna likely help
*[10:15] == Grimthorpe [522eb8a2@gateway/web/freenode/ip.82.46.184.162] has quit [Ping timeout: 260 seconds]
*[10:15] <karianna> Cool - do you have a box already setup or do we need to get one provisioned?
*[10:16] <@Zaister> basically I have two servers thre, an older one a nd a newer one. I've moved most of the stuff, ecept mail to my newer server, and so the older one could be used for PCGen I thought
*[10:16] <karianna> Cool, what are the specs? And is it backed up :-D
*[10:16] <@Zaister> I can dig them out, and it's not yet backed up :)
*[10:18] <karianna> OK, let me know what the specs are and how much the backup will cost (IIRC Hetzner has a fairly crude facility for this, but we should enable it)
*[10:18] <karianna> You’re German timezone?
*[10:18] <@Zaister> yes
*[10:18] <sethj11> I need to bow out - where should I keep an eye out for any code monkey updates? I've got the wiki and the hipchat bookmarked already.
*[10:18] <Tom[Code_SB]> are you on the dev list?
*[10:19] <sethj11> not sure
*[10:19] <Tom[Code_SB]> That provides a level of persistence HipChat doesn't so things may end up there as well
*[10:19] <karianna> Zaister: Cool, I’m UK (although will be New Zealand for 3 weeks starting on the 18th), but perhaps we can start this week? Can you do during the day at all?
*[10:19] <Tom[Code_SB]> pcgen_developers Yahoo group
*[10:19] <sethj11> okay, i'll join before the end of the day and keep an eye out there
*[10:19] <@Zaister> karianna yes that shoudlnt be a problem
*[10:19] <@Zaister> the old server is a VQ12
*[10:20] <@Zaister> Single core, 1GB Ram, 40 GB disk
*[10:20] <karianna> Hmm, OK I’m afraid that’s going to struggle to host PCGen reqs
*[10:20] <@Zaister> yeah i was afraid that could be the case
*[10:20] <karianna> JIRA will eat that alive by itself!
*[10:20] <@Zaister> oh
*[10:20] <Tom[Code_SB]> we use JIRA hosted by Atlassian
*[10:21] <@Zaister> arenÄt we in the cloud with jira
*[10:21] <karianna> That’s good to know
*[10:21] <karianna> So what actually needs shifting?
*[10:21] <karianna> website?
*[10:21] <Tom[Code_SB]> Wiki
*[10:21] <Tom[Code_SB]> build
*[10:21] <Tom[Code_SB]> the build will suck up that 1 GB pretty quick
*[10:21] <karianna> Yah build will kill it
*[10:21] <@Zaister> Well I moved off that server because I host several mediawikis
*[10:22] <@Zaister> Ok then we'll need another solution
*[10:22] <karianna> Do we know what the current server is?
*[10:22] <karianna> I assume only Anestis knows
*[10:23] <karianna> I wonder if Hetzner takes Paypal as well
*[10:23] <sethj11> i'm trying to join the yahoo group, but there seems to be an issue getting some content? I'll have to figure it out later. I'm out - thanks all and see you later!
*[10:23] <@Zaister> karianna I think so
*[10:23] == sethj11 [4915e9f2@gateway/web/freenode/ip.73.21.233.242] has quit [Quit: Page closed]
*[10:24] <@Zaister> however you have to pay manually each month then
*[10:24] <karianna> OK, I’ll ping anestis and see what he’s currently running
*[10:25] <Tom[Code_SB]> For the moment, even if we could just get the libraries up and running on that VQ12 it would let me shut down my Amazon image
*[10:25] <Avilay> i impressed that small server has served well over the years :)
*[10:25] == Rfinch-mob [2ed0086f@gateway/web/freenode/ip.46.208.8.111] has quit [Ping timeout: 260 seconds]
*[10:25] <Tom[Code_SB]> it can support that, since I'm running on even less than that on the current VM
*[10:26] <@Zaister> I'll check your instructions to see if I can get that to run
*[10:26] <Tom[Code_SB]> cool
*[10:26] <Tom[Code_SB]> Okay, I'm going AFK as well... thanks all
*[10:27] <@Zaister> I'll use one of my parked domains for that for now
*[10:27] <@Zaister> have a nice weekend
*[10:28] <karianna> Tom - quickly before you go, why can’t those libs go to Maven Central?
*[10:28] <karianna> Sorry didn’t word that well but hopefully you get the gist :-)
*[10:29] <karianna> I’ll ping him later on thiat :-)
*[10:29] <@Zaister> ok
*[10:31] <[OGL]Nylanfs> So looks like we have everything discussed that we had planned? :)
*[10:31] <Gwen> I'd like to bring up something that my husband just reminded me of. Our web presence is a bit splintered. The wiki, forums, FB, download locations, etc.... They don't seem to have a lot of links to each other or are solidly in most user's awareness.
*[10:32] <@Zaister> that's true
*[10:32] <Gwen> If folks don't know about these resources, they can't use them.
*[10:32] <karianna> Cool, I’ll head off now as well - I’ve dropped tom a note on the developers list and anestis a note on the BoD list and Tom and I are going to try to resolve hte PND issue with Eitan in the next few days, then we can move to Java 9 (Tom and I will sort that) and then I can start the doc exercise with Tom (for developers)
*[10:32] <karianna> Gwen - you’re totally right
*[10:33] <karianna> Is that something you, your Husband and I can go through on a video call?
*[10:33] <Gwen> Can we look at recruiting a sort of webmaster to tighten this up??
*[10:33] <@Zaister> PND?
*[10:33] <karianna> I used to be that person, I can probably do that again
*[10:33] <karianna> Zaister - PMD
*[10:33] <@Zaister> ah
*[10:34] <karianna> I upgraded to 6.0.0 (needed for Java 9) but it’s a massive change and so it’s breaking hte build by default (we need to re do the ruleset)
*[10:34] <Gwen> Not at the moment. We're about to head to the movies. The local theater is running a Sensory Friendly showing, so kids with autism don't have to be still and quiet. We don't get those often, so we need to take advantage when we can.
*[10:34] <@Zaister> hm gettign Java 9 on my machine doesn't look too easy. I'll have to look into that
*[10:35] <@Zaister> Gwen that's awesome
*[10:35] <Gwen> But I think hubby would be happy to do that later. He's a "super-user" so his input might be more useful than mine. (all of his gaming groups use PCGen)
*[10:36] <karianna> Gwen - sorry I wasn’t thinking now :-), ping me on martijnverburg AT gmail DOT com and we can arrange a date / time that suits
*[10:36] <Gwen> Sounds good!
*[10:36] == rfinch [2ed0086f@gateway/web/freenode/ip.46.208.8.111] has quit [Quit: Page closed]
*[10:36] <Avilay> curious. is meeting finished?
*[10:36] <karianna> And that sounds awesome (movies)
*[10:36] <karianna> Avilay - I think so now yes
*[10:37] <Avilay> so i can return to lurking again :)

Meeting Logs

2018-02-24T16:56:21Z

LegacyKing: /* 2018 */

{| align="right"
| __TOC__
|}

This is a new section to hold the Meeting Logs.

=2018=
* [[Meeting 2018 02 24]] "Roadmap to Production"
* [[Meeting 2018 01 13]] "Future of PCGen"

=2017=
* [[Meeting 2017 06 17]] "Team Reports"
* [[Meeting 2017 02 25]] "Team Reports"
* [[Meeting 2017 01 21]] "Team Reports"

=2016=
* [[Meeting 2016 11 12]] "Release Discussion 6.07.01, and hold up"
* [[Meeting 2016 10 01]] "Discussion for 7.00"
* [[Meeting 2016 07 02]] "Quorum - 6.06 release and 7.00 roadmap"
* [[Meeting 2016 05 28]] "Informal"
* [[Meeting 2016 02 27]] "Production Release Meeting"

=2015=
* [[Meeting 2015 11 14]] "Informal Monthly Meeting"
* [[Meeting 2015 09 12]] "Monthly Meeting"
* [[Meeting 2015 08 15]] "Monthly Meeting"
* [[Meeting 2015 05 09]] "Monthly Meeting"

* [[Meeting 2015 03 27]] "Team Discussion"
* [[Meeting 2015 02 13]] "TBD"
* [[Meeting 2015 01 30]] "TBD"
* [[Meeting_2015_01_16]] "Informal"
* [[Meeting_2015_01_02]] "Team Discussion"

=2014=
* [[Agenda_Next_Meeting_Deep_Dive]]
* [[Agenda_Next_Meeting]]

* [[Meeting_2014_12_19]] "Deep Dive"
* [[Meeting_2014_12_05]] "Team Discussion"
* [[Meeting_2014_11_21]] "Deep Dive"
* [[Meeting_2014_11_07]] "Team Discussion & Parser Conversation Post Meeting"
* [[Meeting_2014_10_24]] "Deep Dive"
* [[Meeting_2014_10_10]] "Team Discussion"
* [[Meeting_2014_09_26]] "Post Release Meeting & Deep Dive"

* [[Meeting_2014_09_12]] "Release Meeting" RC2 good to Go?
* [[Meeting_2014_08_29]] "Release Meeting" RC1 good?
* [[Meeting_2014_08_15]] "Team Discussion Meeting"
* [[Meeting_2014_07_18]] "Team Discussion Meeting"
* [[Meeting_2014_07_11]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement Part 2; Documentation Discussion
* [[Meeting_2014_06_20]] "Team Discussion Meeting"
* [[Meeting_2014_06_06]] "Deep Dive Meeting - Formula Parser Compatibility System Replacement
* [[Meeting_2014_05_09]]
* [[Meeting_2014_04_29]]
* [[Meeting 2014_02_28]]
* [[Meeting_2014_01_03]]

=2013=
* [[Meeting_2013_12_06]] <-- Final 2013 Meeting
* [[Meeting_2013_11_22]]
* [[Meeting_2013_10_25]]
* [[Meeting_2013_08_30]]
* [[Meeting_2013_08_02]]
* [[Meeting_2013_06_22]]
* [[Meeting_2013_05_28]]
* [[Meeting_2013_05_10]]
* [[Meeting_2013_03_05]]
* [[Meeting_2013_02_01]]
* [[Meeting_2013_01_22]]
* [[Meeting_2013_01_04]]

=2012=
* [[Meeting_2012_12_11]]
* [[Meeting_2012_11_23]]
* [[Meeting_2012_11_09]]
* [[Meeting_2012_10_30]]
* [[Meeting_2012_10_12]]
* [[Meeting_2012_09_28]]
* [[Meeting_2012_09_18]]
* [[Meeting_2012_08_31]]
* [[Meeting_2012_08_17]]
* [[Meeting_2012_08_07]]
* [[Meeting_2012_06_26]]
* [[Meeting_2012_06_08]]
* [[Meeting_2012_05_25]]
* [[Meeting_2012_March_16]]

=2010=

* [[Meeting_2010_08_02]]
* [[Meeting_2010_07_19]]
* [[Meeting_2010_July_5]]
* [[Meeting_2010_June_7]]

FAQ and Help

2018-02-17T21:00:38Z

LegacyKing: /* Trouble Shooting Problems */

This is just some tips to help along. It'll be a repository of Frequently Asked Questions and Help Tips that we've encountered a lot.

== What is PCGen? ==
PCGen is a JAVA Program that uses custom 'text' files (*.pcc and *.lst) to emulate books from table-top role-playing games, like Dungeons & Dragons 3rd edition, to help create and maintain system rules-legal characters for that game system. It allows you to print out character sheets, or export them into various formats for later use - such as a basic text sheet, xml for various forum play and software systems, htm for web browser enabled devices and pdf. PCGen is built to support the most popular d20 systems and has plans for future expansion into non-d20 based systems.

== What systems does PCGen support today? ==
Today PCGen (version 6.2) supports Dungeons and Dragons by Wizard of the Coast - the specific versions supported directly are: 3rd edition (Known as SRD), 3.5 edition (RSRD), d20 Modern (MSRD). Due to license issues, the program can support 4th edition and the upcoming 5th edition (known as D&D Next) but we cannot supply any pre-made books. Those will require custom sets that you can make yourself.

Our list of supported d20 systems with pre-made books:
* D&D 5.0 edition (Listed as SRD5)
* D&D 3.0 edition (Listed as SRD - System Resource Documents)
* D&D 3.5 edition (Listed as RSRD - Revised System Resource Documents)
* D&D Modern Edition (Listed as MSRD - Modern System Resource Documents)
* Deadlands by Pinnacle Entertainment
* Fantasy Craft by Crafty Games (Crafty Games is hosting the full core rule book, we only have a level 4 demo set)
* Gaslight 1st edition by Battlefield Press
* Legends of Excalibur
* Pathfinder by Paizo Publishing
* Sidewinder
* Spycraft
* Xcrawl

Non-d20 Systems we're building support for:
* Killshot by Broken Ruler Games (This is ready to play but needs a Character Sheet to display)
* Cyberpunk
* Shadowrun

== Using Pathfinder in PCGen ==
* Unchained Classes - Q&A:
** '''QUESTION''': How can I created an Unchained x class?
** '''ANSWER''': First, you need to make sure you are loading the correct book(s). You will need to load ''Pathfinder Unchained'' to have access to the first four Unchained variant classes - Barbarian, Monk, Rogue, and Summoner. Select the base class, Rogue for Unchained Rogue as an example. Once you add the first level, go to the Feats & Abilities tab, under Class Features, there should be a CLASS SELECTION group. Select the Unchained Version from there. Congratulations, you now have an Unchained version of the Class.
** '''LIMITATIONS''': Warning - Due to how PCGen processes SPELL LISTS, an Unchained Summoner will require you to SAVE and RELOAD to have the correct spells populate your spell list.
** QUESTION: I'm very curious (from both a user's viewpoint and that of a designer) as to why you made the Unchained classes as options within the class (when the source is selected) instead of a separate class in their own right. I actually found that very confusing when making an unchained class as I couldn't select it from the class list as one would usually do when making a character. It was only when I went back to the summary screen after selecting the class that I realized I could make the Unchained version. That's a design decision that needs to be deliberated upon and possibly altered because as it stands, it is highly confusing and may lead a lot of people to believe that you can't make an Unchained class at all in PCGen.
** ANSWER: Since that was my decision, I'll be happy to explain the reasoning and how I arrived at that conclusion. If you do a comparison between the normal classes and the unchained versions, you will see (in most cases) the only differences was the class features - Monk had a HD boost, Summoner has a Spell List change, Barbarian only changes features, and Rogue added some new features. It seemed more economical to re-use the base framework which 90% of the classes were built upon. Reduce duplication in code (Each class loaded requires some memory, whereas the method I opted did not increase memory, merely which features to use). Unchained classes comes across as more a variant. Plus, you cannot have an unchained version and regular version of the class. Programming in "Cannot take this" does increase cpu cycles and additional code lines. Add in the fact they were treated just as the regular version in terms of meeting prerequisites for prestige classes, feats, and archetypes, etc. Looking at it big picture, it made more sense to simply use the base class and treat the unchained variant as a super archetype - swap out abilities. They were more the base class then not. The chance of breaking support was higher if they were coded separately - anything using the code classlevel("Summoner") would fail for an "Unchained Summoner" as an example, SERVESAS only does prexxx support. Reviewing everything related to the class - favored classes, archetype support, feats and the data hacks was a bit more time consuming. Plus, it gave me the excuse to test out a function of the program to try and support a prestige class that grants class features from other classes, which we could not support in the past. To combat the confusion, I did include the Summary TO DO to prompt the user to choose which version they want to use; most users use the summary screen to add classes to the character, which would mean they see the prompt right off. Under the hood, it defaults to the base version in case they never make that selection. An important fact for the Summoner - so it still gains spells. If it helps to know, I went back and forth several times, actually coding them up initially as classes. But the lack of time on my part limited what I was willing to undertake, so choosing the path that had the least chance to break any particular build was what I ended up doing. As I progressed, I learned a new tidbit that swung the pendulum toward the other method. I might have chosen differently knowing what I know today. Right or wrong, it is a bit late to change the decision (6.06.00 is now released). With our focus for the 6.08 dev cycle to rip out the JEP reliance tags - anything that starts with BONUS:x, anything that is touched by BONUS, such as LEGS, FACE, REACH, WEAPONPROF, etc. Implementing new support for global and local variable numbers, Booleans, strings and orderedpairs. Rip out every text output tag and replace it with INFO/INFOVARS. Redesign the output sheets to (1) use the freemarker template code properly, and (2) switch to grabbing the new output via fact, info and value. The end goal is a more lean and efficient code base and data processing. Hope that helps clear up the decision making process that led to variant vs. class. If you have any other questions, comments or otherwise, feel free to reach out to me. --Andrew Maitland (Content Silverback - PCGen Board of Director's)
** Reply back: Thanks for the explanation. Now I understand the process behind the decision a lot more. Might be something to add to the FAQs because other people may also get confused and I admittedly found the Unchained version by accident.

* Pathfinder vs Pathfinder Society:
** QUESTION: What is the difference between these and why should I care?
** ANSWER: Pathfinder Society is an actual real world international organization which publishes official rules of play for gamemasters and players alike. The games are run using official modules with completion items given out, special sheets to track rewards and of course a very different XP progression, which is capped well before 20th level. As mentioned before they publish rules each year to tell their members what is legal to use in their games. In essence Pathfinder Society (abbreviated PFS) is a structured event setting which determines what is legal in their games, allowing players from all over the world to have the same experiences and options. Many feats, spells, equipment and class options are restricted in the Pathfinder Society games. PCGen supports the various seasons of play as best we can. Many false bugs are raised due to people mistakenly thinking their favorite options are not working. Rule of thumb, unless you play in this actual society, do not use their rules.

== How Customizable is PCGen? ==
PCGen is designed with user customizations in mind. For the Books Side, we are looking to re-include an In-built LST Editor in the program for version 6.4.0. LST files are the main text files for holding the information that PCGen (JAVA Program) can read and execute. LST Files are plain text programing using a customized Language that is designed towards simple premise of Human-Readable and easily used.

PCGen has several methods to impart how to create your own custom files. First, we supply a sample folder including a full set of pcc and lst files for you to get started. We have extensive documentation in the program, and maintained on our website. Andrew Maitland has made several youtube videos explaining how to craft the files, and the common mistakes to avoid. Finally, we offer online support via our Yahoo Groups and direct help from our Support Desk Monkey - Help@PCGen.Org.

== Is there support for issues and recommendations? ==
Yes, PCGen is a volunteer project run by monkeys and humans. We all know monkeys are a laugh, and humans are fallible. Thus, we have a Ticket Support system that is monitored by the various projects that go towards supporting PCGen. Our ticket support system is called 'JIRA' and anyone can log into the system after creating an account, and report a problem "Bug" or make recommendations for improvements (Feature Requests). The system is located at http://jira.pcgen.org.

Wait, what do all those projects visible mean? I'm totally confused?!!?!
* Data - This is the Books. Chances are if it's incorrect the logical issue would be this project. Bug is something broken; Feature is new things to be added.
* Code - This is the heart of PCGen and encompasses the JAVA involved. They also handle the User Interface (UI for short).
* Docs - This is the Documentation that comes with PCGen. Bugs are typographical errors, or formatting problems. Features would be adding new "classes" or "how-to" to explain using PCGen in new ways.
* OS - This is the output sheets or the final product you see. This encompasses the Summary bottom Pane, the Preview Sheets found on "Character" tab of the program, and all of the export methods.
* Admin - This is non-pcgen issues, like the Website has mistakes.
* Support - This is the catch-all "Help, I'm lost and need guidance". When the program is causing issues, or you cannot figure out something, this is a good place to start.

What if I mess up and place it in the wrong area?
* Fear not, our Jira is monitored by experienced project volunteers, and can easily move your issue to the correct location at any time.

How should I submit an issue?
* Details are the key point. In order to address any issue we need facts. Please include the following in all reports:
** Summary of the issue (Single sentence to briefly give an idea of the issue)
** Version of PCGen (In most cases this is a requirement)
** Data You are loading (You can submit a character file (*.pcg) to the Ticket and that will help speed things along
** Description - What is wrong in your own words, and what is the correct result. Cite a source book if available. Since a person needs to verify the issue before making corrections.
** Environment - Your operating system, Java version and anything else you think will help us.

== Trouble Shooting Problems ==

===High Resolution Display===
I was able to workaround this issue by going into the compatibility properties of the PCGen shortcut and setting the "Override high DPI scaling behavior" to System. This was tested on Windows 10.

=== Java 7 for version 5.17.11 or lower ===
PCGen versions prior to 5.17.11 (including the current production version, 5.16.4) are not compatible with Java 7. This is now the default version Java installed for most system types. Open JDK 6 on Linux exhibits the same problems and the same fix applies.

==== Symptoms ====

When you start PCGen, all character tabs other than the summary tab are blank (i.e. the table outline is there but there is no table displayed and thus no races, classes, equipment etc. can be seen). The advanced sources tab is also empty.

==== Fix ====
There are two options to fix this:
# Install Java 6 and ensure PCGen uses that (may require downgrading
Java or using a batch file to start PCGen with Java 6)
# Use PCGen 5.17.11 or later. At the time of writing the current alpha version was 5.17.14. See [http://sourceforge.net/projects/pcgen/files/PCGen%20Unstable/ PCGen Alpha Downloads]

=== Windows Installations ===
* Vista & Win7 (32 & 64 versions) Install and Running
** If you are running 64-bit versions of Vista or Win7, the bat file may not find JAVA. You may have to hard-code the path to java.exe. To edit those either Right Click on my Computer -> Properties -> Advanced System Settings -> Environment Variables OR Control Panel -> System -> Advanced Syystem Settings -> Environment Variables.
** You can modify the PATH by adding your JAVA path to it.
** Example of a Direct Reference to Java:
** "C:\Program Files (x86)\Java\jre6\bin\java" -Dswing.aatext=true -Xms1024m -Xmx1024m -jar pcgen.jar
** Put that in your PCGen Bat File.
** If you're using the BAT, feel free to up the memory usage. I have mine set to 512 and 1028 (Just edit the bat file in a text editor). Set the memory to what your system can handle.
** Install in a NON-default directory (not c:\program files) Vista and Win7 seem to have directory permission issues at times. (Especially Win7) The UAC in both can cause problems in some cases.
** Setting the Permission of the FOLDER to the highest level can help
** 5.17.0 onward have an exe file that solves the JAVA issue.
** Make sure you have a current version of JAVA installed (Not normally an issue for Windows Users)

* 1) Create a pcgen.cmd file with the following in it:

** "C:\Program Files (x86)\Java\jre6\bin\java.exe" -Dswing.aatext=true -Xms256m -Xmx1024m -jar "C:\Program Files (x86)\PCGen\PCGen5161\pcgen.jar"

** 2) Put the pcgen.cmd file in your C:\program files (x86)\pcgen\pcgen5161\ directory.
** 3) Change your shortcut link to the pcgen.cmd file.

=== Mac Installation Issues ===
ISSUE: I have downloaded PCGen for the Mac and I cannot get it to run. If I try to open the application from within the disk image, I get this error message: " “PCGen 6.04.01” is damaged and can’t be opened. You should eject the disk image." If I move the application into the Applications folder on my hard drive, I get this error message: "You can’t open the application “PCGen 6.04.01” because it is not supported on this type of Mac."

SOLUTION: To prevent this error, go to System Preferences -> Security & Privacy. At the bottom of the window there is a section titled: "Allow apps downloaded from:" Then select "Anywhere". That will allow you to open PCGen.

ISSUE: Gatekeeper will not allow PCGen to run

SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.

UPDATE:

* Hold down "control" button
* Click on the app that is triggering the message about the security preferences
* Select "open" to override and install/open the application

This allows you to avoid changing the security setting to "anywhere."

=== Homebrew OS Sheet for working 5.17.16 and forward ===

As part of an improvement to Display all the Allowable Range Increments properly for Thrown and Ranged Weapons, some changes were made to the BASE.XML file and the reliant XSLT files. Sadly, this change '''will''' break home-brew OS sheets going forward.

You have two options going forward.

'''Option 1:'''
You'll need to make the following change to the section listed in your XSLT files that contains this:



Replace that entire Section with this new code.

[http://pastebin.com/2YAhrBSV PCGen Pastebin Link to Updated Ranges Template]

'''Option 2:'''

Replace the BASE.XML file shipped by us and using an older one (But this will mean you lose the newer functionality)

=== Changing a Character's Sources ===

Sometimes you may need to change the sources a character is associated with, you could be adding a new source book you have started using or removing a book that is unused. Here's how to do it:

# Turn off the "Load Sources with PC" option in Preferences > Sources
# Load the desired sources
# Load your character
# Save your character again (I'd recommend saving to a new file)
# Reactivate "Load Sources with PC" in preferences.

The saved character will now be registered against the new sources which will be checked each time you load the character.

Another option is to use a pre-saved source selection. This can then be used by a number of characters and just updated when you want to add books. You can create a pre-saved source selection using these steps

# Open Sources > Select Sources and switch to the Advanced tab
# Select the game you are using in the first drop-down.
# Select the sources you would like to use (using Add Selected)
# Once happy click the Save Source Selection button and enter a name for your source set.
# Select the new set on the Basic tab and load it.

Then when you want to update the sources used for those characters just repeat the process using the same name. You should select the original saved selection first before switching to the Advanced tab and then the old books you selected will be already selected.