How it works

The app, your device, sharing with players, and how to move a campaign from your desk to the table without losing your mind.

Website, app, and your data

Same model as the player app: this site is the manual; the app at /app/ is where you build and run. Campaigns, NPC catalogs, zones, and imported characters live in this browser's local storage until you export them.

PWA install, offline cache, and the “clear data = gone” rules are covered once on Player Guide » How it works — it applies to GMs too.

Sharing with players

Receive from players button with wifi tether icon
Import (clipboard) button with clipboard icon
In the party editor Players panel — live receive is the outlined button; clipboard import is the filled button at the bottom.

Two paths for getting player characters into a campaign party:

  • Live party exchange (recommended): in the party editor, tap Receive from players, share the 5-character code, and Import each incoming submission. Players use Send to GM on their campaign row. Requires network and the same website. Details: Parties.
  • Clipboard (fallback): players use Export for GM, you use Import (clipboard) in the party editor. Same collision rules either way.

Zones can also move live between GM devices (Receive zone / Send zone on the Zones panel). NPCs and encounter templates still use clipboard when sharing catalogs — see below.

Clipboard hand-off (NPCs, zones, co-GMs)

For catalog content and offline co-GM sharing, export JSON to the clipboard and paste on the other side. Live zone transfer is preferred when both devices can reach the same RpgMeister host.

  • Sharing NPCs or zones with a co-GM: use Export all on the NPC list, per-row export on templates, or Export zone (clipboard) / live Send zone on the Zones panel. Zone exports bundle the zone, its encounter references, templates, and the NPCs they need.
  • Import on the other side: Import (clipboard) on NPCs, encounter templates, or zones — or Receive zone + Import for a live hand-off. Bulk overwrites ask for confirmation before replacing existing catalog entries.

Step-by-step: NPCs · Zones.

PC to tablet: moving a campaign to the table

Building on a widescreen is faster. Running on a tablet is nicer than squinting at a phone. Live zone exchange is the fastest path when both devices share the same RpgMeister host; clipboard remains the offline fallback.

  1. On your PC, open the campaign and finish the heavy lifting — NPC catalog, templates, zone graph. Hit Save campaign (and Save zone on each zone you've edited).
  2. On the tablet, open Edit campaignZones and tap Receive zone. Share the 5-character code (letters and digits).
  3. On the PC, tap Send zone, enter the code, pick the zone you'll run tonight, and send. Confirm overwrites on the tablet if prompted.
  4. Offline fallback: Export zone (clipboard) on the PC, paste into a note or chat, then Import zone (clipboard) on the tablet. Use Export all on the NPC list if you're travelling light on map data.
  5. Import the player party via Receive from players at the table, or Import (clipboard) if players sent JSON earlier. Tap Play on the campaign row when the players arrive.

You don't have to sync the entire world every session — one zone and tonight's encounter templates are often enough.

Build big, run lean

Not every note needs to live in the app. Index cards, a paper map, and a dramatic voice are still valid GM tools. What the app is good at:

  • Reusable NPC stat blocks and attack lines.
  • Encounter templates you can fire from Play with a tap.
  • Initiative, rounds, and damage during a fight.
  • Player character sheets imported for reference during combat.

Minimum viable campaign in the app: NPC catalog + templates + party. Zones are wonderful; they're also optional if you're narrating travel yourself.

Known limitations

  • No campaign duplicate button. Export zones and NPC lists, then paste into a new campaign — or use live zone transfer between devices you control.
  • No live sheet sync during play. Player rolls and edits stay on their devices; you keep reference copies. Live exchange only relays import JSON while a receive session is open (party, roster backup, or zone).
  • Mobile clipboard can need a long-press or a fresh copy before import (fallback path).

Symptom-by-symptom fixes: Troubleshooting.

Open the app

Open the Campaigns list

New here? Try the Quick start next.

← Back to Campaign Guide