At some point, you might want to add additional classes, spells, or feats to your d20pro installation. Most custom content is easily added by modifying the text files located in the folder:

d20pro\\dm\res\ManuallySpecified

There you will find four text files (classes, skills, feats, spells). Before you make any modifications to these, make backups and store them somewhere, like in a folder called Originals, for example.

Custom Feats

Editing feats is pretty straightforward. Just type in the names of your new feats. There are a few things to keep in mind though:

• Prefixes & Suffixes: If you open the feats file, you will notice that most feats have the Generic| prefix before them. For any feats that do not modify initiative, it's recommended that you keep that prefix. Feats that affect Initiative have the InitModifier| prefix followed by a |# suffix where the # is a numerical modifier.
• Example: If you were to add the Thug feat from the Player's Guide to Forgotten Realms (which grants a +2 to intimidate & initiative), you would enter it as InitModifier|Thug|2 The only feats that currently have automated processes associated with them are those that affect Initiative
• List Order: Feats display in d20pro in the order listed, so if you don't add to the list in an alphabetical fashion, your feat list will be unorganized in the program. You can use this to your advantage, though. See examples.
• Naming Tips: These are just some of the naming conventions I use. Your mileage may vary.
  
• I use a minus before the names of any feats that are 1st level or regional feats, so they don't get confused with general feats. Such as: Generic|-Arcane Schooling
• I use an asterisk after any feat that is not core, just so I know that it's from another source. Example: Generic|Combat Tactician*
• You could also change the existing feats to reflect their role a bit more, such as adding Metamagic before appropriate feats. Example: Generic|Metamagic - Empower Spell

This can be the most complicated of the custom content, but only for spellcasting classes. Regardless of the order they appear in the txt file, classes will be listed in d20pro in alphabetical order. Things to consider:

• For the most part, you can look at the current classes to gain an understanding of syntax. Classes start with a capitalized entry of ## CLASS: <name>. That's to make them easier to find.
  
• Next we have CreatureClass=<name> The name listed here is what displays in the class list within the program. Creative naming conventions can control how your classes appear, such as using NPC_Adept and PRC_Blackguard to keep NPC an prestige classes grouped in the list.
• Next is AttackRate=<#> where the number indicated the rate of progression in Base Attack Bonus. There are only 3 rates in D&D 3.5. Note that you are not technically limited to the rates below, as d20pro accepts any numerical rate.
  
• Poor: used by wizards, sorcerers, and commoners. This advances at a 1/2 rate, or .5
  
• Moderate: used by clerics, rogues, monks, etc. This advances at 3/4 rate, or .75
• Good: used by fighters, paladins, barbarians, etc. This advances at 1/1 rate, or 1

• Right now, d20pro does not have support for base save progression, so the GoodSaves=<type> doesn't have a real function. Saving throws in D&D advance in two tiers - good and poor. Close attention to save progression for any class in the rulebooks reveals that it has only two possible values for saves. Clerics for example have good Fort and Will saves, and poor Reflex saves. This line denotes those saves that advance at a good rate. It's advised that you fill this out, in case future support is enabled.

Spellcasters
At this point, you are done unless your custom class is a spellcaster, at which you need to enter in additional blocks.

• Spellcaster= ............ This instructs d20pro to use a specific spellcaster template and ability modifier. To make this easier, copy & paste a caster type that matches your class.
• Example: If I wanted to enter information for the Duskblade class, I might look at the sorcerer, since both are spontaneous casters. However, I would modify the last part (the ability modifier) to be INT since duskblades use that ability modifier for bonus spells. My final entry would be:

SpellCaster=com.mindgene.d20.plugin.dnd.creature.SpellCasterTemplate_Sorceror|INT

• #SPELLS AVAILABLE and Spells<#>=<name> : This section starts the spell list. Each spell level is listed on a separate line and starts with Spells# where # is the spell level, then = then the spell names separated by pipe characters | (shift+backslash).
  
• IMPORTANT!! Spell names MUST match exactly with the names in the spells.txt file. So Blade of Blood will not appear if you have the spell listed as Blade of Blood* (with asterisk) in the spells.txt file. Also, keep in mind that spells from core books are listed with their SRD names, so if you add a class with Melf's Acid Arrow, you should rename it to Acid Arrow, since that's the name in the spells.txt file.
• This can be a tedious process, but once completed, it's done for good. If you are feeling helpful, please post your content here!
  
• #SPELLS PER DAY and PerDay<#>=<#>: This section starts the spells per day table. Simply follow the conventions for other classes. Separate numbers with the pipe character |
  
• For spontaneous classes, don't forget to add the third section, #SPELLS KNOWN. This controls how many spells the character knows at the appropriate level.
  

Custom Skills

You shouldn't have to add skills very often, but they are listed with the format of: Skill Name|ABILITY. See the text file for examples.