Skip to content

Lst editing

Bahamut edited this page Jun 16, 2013 · 8 revisions

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/d20/publisher_name/category/full_book_name

a_full_book_name.pcc prefixing the "a_" keeps the pcc at the top of the directory for rapid finding

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.

Display Name is the start, KEY:Name (extra) is second.

CATEGORY should be Special Ability unless this is a simple chooser or selection that we don't want being displayed to the player on the character sheet.

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

TYPEs - SpecialQuality or SpecialAttack; for Class Abilities use 'ClassAbility.NameOfClassClassAbility', for Races 'RaceAbility.NameOfRaceRaceAbility'

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 is always the FIRST appearance of an ability (Don't worry if it goes to another page)

KEY shall be used to make the ability unique appending a ' ~ GrantingRaceOrClass' 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

More to come later...

Books (Test)

Clone this wiki locally