Skip to content

Lst editing

BahamutDragon edited this page Nov 30, 2014 · 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/gamemode/publisher_name/group/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; do not worry about identical names from other books, as long as the names are unique in the folder, it will be fine. 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 Abilities:

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

For Names that change with levels (Smite 1/day, Sacred Defense +2, etc.) use ASPECT:NAME|Name of Ability Examples:

  • ASPECT:NAME|AbilityName %1/day|(VARIABLE)
  • ASPECT:NAME|AbilityName +%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 Features use 'Class Feature.Class Name Class Feature', for Races 'Race Trait.NAME Race Trait'

Update - ClassFeature is the heading I have seen for 3.5 sources, so I will use that where it seems appropriate.

SOURECEPAGE is a must, even if it's only a 'p.' that will let us know we need to get a source page from the source book. Determining Source page number is always the FIRST page you see the appearance of an ability/class/feat (Do not 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)'. Example: KEY:Fighter ~ Bonus Feat

SORTKEY can be used to make an ability show up in a specific order.

RACE:

  • Display Name

  • KEY: if required (Name (Group))

  • SORTKEY:Base Group (Individual) - if Display Name would place it out of the correct order

  • RACETYPE:(One of the Base Race Types)

  • RACESUBTYPE:(If appropriate)

  • TYPE:(Must match RACETYPE) + PC if a PC race.

  • STARTFEATS:1 (If Intelligent Race and gains feats)

  • HANDS:# (How many hands the race has)

  • LEGS:# (How many legs the race has, this is important for Size and weight carrying capacity)

  • SIZE:x (Abbreviation for Base Race Size, omit if special size is used, like dragons)

  • MONSTERCLASS:Racetype:# (If the creature has HD)

  • ABILITY:Internal|AUTOMATIC|Race Traits ~ RaceName

  • REACH:# (New methods are being introduced that makes this automatic)

  • FACE:x,x (New methods are being introduced that makes this automatic)

  • ADD:SPELLCASTER|x (If Race has spellcasting capabilities outside of class)

  • BONUS:PCLEVEL|x (If Race has spellcasting capabilities outside of class)

  • BONUS:VAR|DarkvisionRange|x|TYPE=Base (If Race has Darkvision)

  • BONUS:VAR|HasLowlightVision|1 (If Race has Low-Light Vision)

  • BONUS:VAR|RaceSizeIsLong|1 (If Race is considered LONG instead of TALL)

  • SOURCEPAGE:p.# (What page does the race first appear on)

New Designs are making AUTO:LANG and LANGBONUS granted by Ability > Template

  • AUTO:LANG|x|x (For automatically granted languages)
  • LANGBONUS:x,x (For Languages that the race can take if it has a high intelligence)

If you intend on Race Traits or Class Features displaying in the UI, then you need to take the extra steps outlined:

  1. Create ABILITYCATEGORY:xxx Class Feature or ABILITYCATEGORY:xxx Race Trait Best method is to Copy an existing version from PH, Barbarian Class Feature, or a Race Ability - Replace the Name with the Class or Race name. There are only two instances you need to replace in a single line.
  • ABILITYCATEGORY:Human Race Trait
  • VISIBLE:QUALIFY
  • EDITABLE:YES
  • EDITPOOL:NO
  • CATEGORY:Special Ability
  • TYPE:Human Race Trait.HumanRaceTrait
  • PLURAL:Human Race Traits
  • DISPLAYLOCATION:Race Traits

Next, you need to force the ability to be granted to the new ability category. Instead of

ABILITY:Special Ability|AUTOMATIC|xxx ~ yyy
you need to use 
ABILITY:xxx Class Feature|AUTOMATIC|xxx ~ yyy 
or 
ABILITY:xxx Race Trait|AUTOMATIC|xxx ~ yyy

Be sure to match the ability category you made though.

Examples:

  • ABILITY:Human Race Trait|AUTOMATIC|Human ~ Skill Bonus