Parties
The player characters at your table — assembled by importing JSON exports from each player's app.
What a party is
A party is a named roster slot inside your campaign: which player characters you're running with tonight. The live sheets stay on the players' devices; you keep a reference copy for initiative, damage, and GM rolls in Play.
Players export; you import. The app is the postal service, not the spy network.
The party list
On Edit campaign, expand Parties. Each row shows name, member count, and Edit / Delete. Footer: Add party.
There is no roster-level party export on the GM side — players send you JSON; you don't push parties back through the app.
The party editor
Add party or Edit opens:
- Identity — Name and Description (table nickname, scheduling notes, etc.).
- Players — table of imported characters (Character, Player, Size, Skills) with remove per row.
Toolbar in the Players section: Import (clipboard) — reads a player's party export JSON. You can combine multiple imports before the session; only one party is active during Play.
Footer: Save party or Discard. Saving persists the party and the campaign (and writes per-character storage for imported PCs).
Import collisions
Party import is not the same bulk overwrite dialog as NPCs. When a character collides with one already in the party (same key, or same name with a different key), they land on an approval queue:
- Overwrite — replace the existing roster entry with the imported sheet.
- Skip — leave the existing entry alone.
A warning chip shows how many characters are pending until you decide. Success snackbar: "Party imported. Total characters: N." (or a warning if approvals remain).
What players do on their side: Player Guide » Sharing the party with your GM. Remind them to Save Campaign before export so the JSON isn't stale.
Common mistakes
- Importing before the player saved. Export uses saved state on the player device.
- Leaving the approval queue hanging. Resolve Overwrite/Skip or you'll wonder why the roster count is wrong.
- Expecting two parties active in Play. Pick one party in session setup; swap by returning to setup, not by magic.
- Empty party name. Save validates — name the party something you'll recognise in the Play dropdown.
- Importing a caster without reading their powers. Skim powers in the import preview or have the player walk you through each one before session one. See the Powers guide.
See also
- At the table — pick the party in Play setup.
- How it works — clipboard hand-off.
- Player Guide » Campaigns — player export workflow.