Guide sections

Fantasy Grounds export

Export a campaign as Fantasy Grounds material and understand what maps into a module package or db.xml.

This is the reverse of Fantasy Grounds import: import reads a Fantasy Grounds db.xml; export writes one.

What exports

The Fantasy Grounds export packages four kinds of creation from the open campaign, plus images when you include them:

Campaign Familiar CreationBecomesNotes
NPCsFantasy Grounds NPC recordsName, description, stats when present
LocationsFantasy Grounds recordsName, description
EncountersFantasy Grounds recordsName, description, creatures
ItemsFantasy Grounds recordsName, description, properties
ImagesReferenced in the exportWhen Include images is on

All of this is written into a Fantasy Grounds db.xml, optionally wrapped in a .mod package.

Export options

When you pick Fantasy Grounds, the wizard adds an options step:

  • Package format - choose one:
    • .mod package (ready to drop into Fantasy Grounds) - builds an installable module.
    • Plain db.xml only - writes just the raw campaign XML, no package.
  • Module name - the name for the .mod package. Leave it blank to default to the campaign name.
  • Include images - include image references from your creations.

Export steps

  1. Open the campaign you want to export.
  2. In the campaign’s left navigation, choose Export Campaign.
  3. Select Fantasy Grounds.
  4. Set your options - Package format, Module name, Include images.
  5. Click Browse… and choose a destination folder.
  6. Click Export and wait for the summary. The Saved to: line shows the folder you picked.

Where the files land

Everything is written into the destination folder you choose:

  • db.xml - the campaign data as Fantasy Grounds XML. This is written every time.
  • <module name>.mod - written only when you choose the .mod package option. It’s a package that bundles a definition.xml and the db.xml together.

Pick .mod when you want a module you can install directly in Fantasy Grounds. Pick plain db.xml only when you just want the raw campaign data (for example, to inspect it or drop it into an existing campaign folder yourself).

Troubleshooting

Nothing was written

  • Make sure you selected a destination folder in the Browse… step before clicking Export.
  • Check that you have write permission for the folder you chose.

Where does Fantasy Grounds expect the module?

  • Fantasy Grounds loads modules from its own modules directory. Copy the exported .mod file there (or export straight into it), then enable the module inside Fantasy Grounds.

The .mod file didn’t appear

  • The .mod package is only created when you choose the .mod package option. If you chose plain db.xml only, that’s expected - you’ll find just db.xml in the folder.