Lst editing

My standards try to match the PCGen team standards, as I want my sets to be compatible with their 3rd party books.

Directory and Data Set Naming:

• pcgen/data//<publisher_name>//full_book_name

"full_book_name.pcc" prefixing the underscore "" keeps the pcc at the top of the directory for rapid finding and editing.

For the LST files - use the abbreviated book name, Full Book Name = fbn; don't worry about identical names from other books, as long as the names are unique in the folder, we're good. Example:

• fbn_filetype.lst

ABILITIES:

• Do use DESC
• Avoid using SAB and BENEFIT - outside of Feats, there is no reason to use BENEFIT.

Standards for Abilitie:

• Display Name is first (If it has any commas, always use a KEY)
• KEY:(grantor) ~ (Name) (subgroup)

For Names that change (Smite 1/day, Sacred Defense +2, etc.) use ASPECT:NAME Examples:

• ASPECT:NAME| %1/day|(VARIABLE)
• ASPECT:NAME| +%1|(VARIABLE)

CATEGORY should always be Special Ability for anything we wish to display. Non-Display choices should use CATEGORY:Internal.

Valid CATEGORY - Special Ability, Internal, others TBD as needed.

• TYPEs - SpecialQuality or SpecialAttack; for Class Abilities use 'ClassFeature.(Actual Name Of ClassClassFeature)', for Races 'RaceAbility.(Name Of RaceRaceAbility)'

Update - ClassFeature is the heading I've seen, so I'll use that where it seem appropriate.

SOURECEPAGE is a must, even if it's only a 'p.' that will let us know we need to get a sourcepage. Determining Sourcepage number is always the FIRST page you see the appearance of an ability/class/feat (Don't worry if it goes to another page or three, only the first instance is required)

KEY shall be used to make the ability unique placing a '(Granting Object) ~ (Name of Item)' SORTKEY can be used to make an ability show up in a specific order.

RACE:

• Display Name
• KEY:if required
• SORTKEY:if Display Name would place it out of the correct order

ABILITYCATEGORY:(Class Name) Class Feature

More to come later...