Skip to main content

Known Limitations

Not supported​

  • Dual class - Foundry's Pathfinder 2e system has no dual class variant, so only the primary class is imported, with a warning. Add the second class's features by hand.
  • Companions, eidolons and constructs without PF2e Companion Compendia - companions, eidolons and constructs are only built when that module is active.
  • Kits - kits are skipped; add their contents by hand. The Adventurer's Pack is the exception in Pathfinder 2e: it comes across as a backpack holding its usual contents.
  • Signature spells - Pathbuilder's export does not say which spells are signature spells, so mark them on the character sheet. The import notes remind you, and later imports keep your choices.
  • Starfinder shields - see Starfinder 2e.

Things to check​

  • Names that differ - Pathbuilder and Foundry sometimes name things differently. Anything Pathmuncher cannot match is listed in the import notes. Please report any you find, ideally with a shared link to the Pathbuilder character or its JSON export.
  • Variant rules - if the world's Free Archetype or Gradual Ability Boosts settings do not match the build, archetype feats and boosts may not land where you expect. See Variant rule warnings.
  • Items kept on a re-import - an item you keep in Keep items added by hand? that is also in the build appears twice.
  • Older Pathbuilder exports - exports from older versions of Pathbuilder may not say which spells a prepared caster has prepared. Every known spell is then put in the spellbook, unprepared.
  • System updates - Pathmuncher uses parts of the Pathfinder 2e system to work out choices from a build. If a system update changes them, GMs see a warning when the world loads. Imports still work, but the system asks for more choices, until Pathmuncher is updated.

Common problems​

I can't see the Pathmuncher button. It only shows on player character sheets, for a user who owns the actor and has the Create New Actors permission. If the GM has turned on Restrict Import to trusted users?, the user must also be a Trusted Player. See Who can import.

"Unable to reach Pathbuilder". Check the export ID. If it is right, paste the JSON instead: in Pathbuilder's Export JSON window, choose View JSON and copy all of it.

"This does not look like a Pathbuilder export". Make sure you copied the whole export, from the first { to the last }.

My familiar wasn't created. Pathmuncher creates a Familiars folder for it, so the importing user needs permission to create folders. See Familiars.