Campaigns are independent constructs that encapsulate all the rules, graphics, maps, creatures, items, and handouts. A typical campaign might contain a special ruleset, some particular maps relative to the world that it is being played in, along with some world specific creatures, items which are world/campaign specific, along with handouts that relate only to this campaign.
Campaigns help to reduce cluttering the various library menus to keep each of these as non-cluttered as possible. It will help them GM find specific items rather that searching through items which might not have any relevance at all. Think of a campaign as a folder, and indeed that's exactly what a Campaign is. A specific Campaign will live in the judges/campaigns folder with the name of the folder is the name of the campaign.
When you first start in Judge mode (GM) there will be a option to choose which Campaign you are using. To change a Campaign once d20Pro is already running, you must restart d20Pro.
The screenshot above is what you will see when you first log in to d20Pro as a GM. In order to create a new Campaign you will need to hit the "Advanced" button. You will then be taken to the Campaign Creation screen.
Go to the desired campaign that you wish to modify. Under that directory you will find the following folders:
The "res" directory will contain the following subfolders:
The CTR folder is for graphics that represent images for your players and their opponents. You might want to place icons specific to this campaign in that folder. The FLR folder will contain graphics for various maps that you wish to use for this specific campaign. The ITEM folder is for graphics that represent items that you characters might encounter in this campaign. Some examples are backpacks, weapons, etc. When you place new images in this folder they will be available for you to choose when you need graphics for creating items in your library.
When you create a new character for example, and you want to choose an image for that character, it will search the CTR folder, and all of its sub folders, for a new image. It is important to note that d20Pro only scans this folder when it first starts up. Changing the folders while d20Pro is running is not supported and also not recommended. It is best to shut d20Pro down, make your modifications, and then restart d20Pro so that it can see the newly placed graphics in that folder.
The Manually Specified folder is for changing the classes, feats, skills, spells, and stats that are allowed in this campaign. In order to change these you will need to edit the following files:
The classes.txt file is for describing the classes in your campaign. If you examine the classes.txt file from the default campaign it will give you an idea of how to update this file. For a newly created campaign it will be empty. It might be a good idea to copy the classes.txt file from the default created campaign and then modify it as needed.
The feats, skills, and spells text files are similar to the classes.txt file. You can copy those files from the default campaign and modify them if you desire to change them.
The last file is the stats.zip file. Don't unzip this file as it is read as a zip file. This file is for an HTML based display of your characters stats. You can modify this file in another temporary folder and then return the modified zip file to this directory should you wish to update it.
This zip file contains the following files:
If you look at the raw HTML files you will see that they contain tokens. An example of some of the tokens in the stats display (row1.html) are as follows:
There are more tokens that can be added to the display. Below is a list of those tokens:
These tokens can be added to any of those HTML files for a custom character display. As you can see, the new Campaign feature is very powerful and very customizable. There is however, one more powerful customization available: Freeform tokens. These tokens are created by the user.
In order to establish a freeform token, you must use the delimiter <>. You can specify a key value pair where the first space in the string is the delimiter. A token without a space, or with the first space as the last character is not a valid token and is ignored.
Here is an example of a valid freeform token:
Wherever that token, in this case wherever $cmb appears in the stats HTML, it will be replaced by the String value, in this case 22.
A freeform key that is the same as a built-in one will get first dibs and will override the built-in key. The convention is to start a key name with $.
Judging a Game >