...
The campaign database is the location where all the campaign information about characters, adventures, monsters and other NPCs is stored. The data base is saved when a session is closed and loaded when a session is started. Each campaign has its own database. The data is physically stored in XML form in the file "db.xml" in the campaign folder.
File Structure
See the Module Data File Overview topic for more details on the file structure.
...
To differentiate between the campaign database and module databases, a special database path string syntax is used. First, database path strings for modules are formed exactly as above (specifying the path within the module database). Then, the path is prefixed with the at character ('@') and following with the complete name of the module.
Examples
Path | Description |
|---|---|
charsheet.id-00005.inventorylist.id-00001.name | Absolute Path. Used as an API reference path. Points to a name of an item in the inventory of a PC sheet. |
ac.totals.general | Relative Path. Used as a number control source. Points to the general AC total score from a PC sheet database node. |
.inventorylist | Absolute Path, with relative override. Used as a window list control source.Points to the inventory database node from a PC sheet database node. |
...spellset.set1.levels.level0.dc | Relative Path. Used as a number control source. Given the current database node, traverse up two levels, then follow the "spellset.set1.levels.level0.dc" subpath. |
reference.classes.fighter@3.5E Basic Rules | Absolute Module Path. Used as a window database path. Points to a class record within the "3.5E Basic Rules" module. |