![where to load campaign data in fantasy grounds 2 where to load campaign data in fantasy grounds 2](https://i.ytimg.com/vi/TOEj2ha1vCk/maxresdefault.jpg)
If the child tag has the static attribute, then the database node corresponding to the child tag. The root tag or any other subchild of the root tag can have any number of child tags Only one player can own a record at a time, but the GM can always edit. If the owner attribute is set to "true", then the player is also marked as the owner of this record, and can make changes. The data will be sent to the client with the given name on connection to a campaign. Makes the parent tag accessible to a specific user denoted by the name attribute of this tag. Internal tag, should not be used in modules. The data will be sent to all player clients on connection to a campaign. Makes the parent tag public to all users. By default, the module name is assigned as a category to all uncategorized module data. This tag specifies that any children of this tag belong to a given category. There is no defined limit on the amount of tags which can be nested in a data file. A leaf node is a tag with a data type attribute, and can not have child tags.
![where to load campaign data in fantasy grounds 2 where to load campaign data in fantasy grounds 2](https://img.youtube.com/vi/DHRBeO6lUWo/0.jpg)
A subtree node is a tag with no data type attribute, and can have child tags. The root tag and any subtree child tags can have any number of additional child tags. Any links to the old module name will be redirected to this module, as long as the old module is not open.Īll data within Fantasy Grounds is stored as a tree structure, with a root node for the campaign and each module as the starting point. Specifies any module names which this module overrides.
![where to load campaign data in fantasy grounds 2 where to load campaign data in fantasy grounds 2](https://i.ytimg.com/vi/lhbLirrcLh0/maxresdefault.jpg)
If "Any" specified, then this module can be used in any ruleset. The rulesets for which this module can be used. The module author to display in the module activation interface. The module category to group this module under in the Library. If no display name specified, then the module name will be used. The module display name to show users in the module activation interface. As of v3.3.2, if no module name specified, then the file name will be used. This name is used in all links to module data. The module name used to uniquely identify the module data and tokens. The string matching the version number of the FG client version that uses this data format (Ex: "3.3") The main root node contains all the meta-data for module definition files. The definition.xml consists of the following tags:
#WHERE TO LOAD CAMPAIGN DATA IN FANTASY GROUNDS 2 MOD#
mod file to be displayed in the module activation interface. Finally, a thumbnail.png file can be placed in the root of the module folder or the root of the. Also, any image files included in a "tokens" subfolder within the module will be added to the GM token bag when loaded. Any images (handouts, maps) referenced by the XML data files will need to be included as well. If any data is included in the module, it will be included in a db.xml file (for GM data) or a client.xml (for player data). A failed database load will load an empty database, which will then be saved on exit for that campaign.Įvery module requires a definition.xml file in the root of the module folder or the root of the. Note: If you choose to edit the campaign db.xml files directly for any reason, we highly recommend you make a backup before editing to avoid data loss.