One call, four tools

This round is for a trusted group that already plays PF2e (or close) with mixed tools—Pathbuilder plus Foundry, or Pathbuilder plus a Discord dice bot, or HeroLab plus a VTT. You do not need a new playstyle. We are swapping which window does which job. This site never stores AMBA, WG, Owlbear, Discord passwords, or the GM API key. The shared time grid shows handles, not emails.

Map it to a table you already run: Wanderer’s Guide is Pathbuilder (build the PC, export JSON). The new WG UI in combat is the live sheet and tracker—what you click in Foundry’s character sheet / combat tracker, not the map. AMBA is the GM’s module notes (the PDF, the Foundry journal, the stuff players never edit). Owlbear is the battle map only (Foundry canvas, Roll20 scene). Discord is still voice. In AMBA the GM builds a module or adventure; after export that is a campaign in WG—same table, two names. Old and new WG UI share one stack, so a join key works in either builder; combat on the call is new UI only.

1. Log into AMBA WG, make two public characters, export both

Before the call: sign in on AMBA’s WG clone. Build in old UI or new UI (try both if you can)—same job as Pathbuilder, two apps on one stack. Make two characters that differ a bit, and turn on Public Character on each (like a shareable Pathbuilder link, not a private draft). Where that switch lives is on the WG page. Export each as WG JSON and drop both files on Uploads. Four people × two files is eight characters. Combat on the call uses new UI only.

2. Discord

Everyone joins the same voice channel. Open the Discord page for the server widget, text channel, and voice toggle. When we first meet, pick four of the eight to play. Keep AMBA, Owlbear, and WGUI closed until the steps below call for them. The GM will screen-share; players watch unless a step says they click.

3. Empty AMBA module first, then JSON import the four PCs

You cannot import PCs until there is an empty module (or adventure) container. The GM screen-shares AMBA, signs in, and creates a blank module or adventure—a stub with a name and nothing in it yet. Only after that stub exists does the GM download the four chosen JSON files from Uploads and import them as module PCs. Do not Create campaign, do not design acts, and do not export yet. Link WG later if the export step needs it.

4. Owlbear: extensions, connect, PC tokens only

Switch to Owlbear. The GM screen-shares, loads the AMBA-related extensions, connects that room to the stub module, and runs import PCs and character sheets. Nothing else yet: no Watabou map, no monsters, no second export. Players join the room, take ownership of their own token, and practice moving it on the scene.

5. Back to AMBA: first act, scene, encounter

Screen-share AMBA again. Together, make the first act, then a scene, then an encounter. Optional: players who want to follow along can use an AMBA account plus module sharing (Shared, not their own copy). Screen-share still works if they skip that.

6. Player syndication link (player-only packet)

Players do not log into AMBA. They get a player-only syndication link for the module or adventure—read-only HTML, no account. In AMBA Settings, under Player version, create the player version, then Copy player link into Discord. Open Manage publish tree and leave only the initial nodes checked (overview, gazetteer, no-spoiler handouts, Act 1 intro—not later scenes, GM packets, or spoilers). Players bookmark that URL. As the table hits later scenes, the GM returns to the publish tree, checks the newly reached nodes, saves, and players refresh the bookmark. Unchecked nodes stay GM-only. This is not the full-tree or partial public syndicate; it is the player channel the GM exposes as they go.

7. Discord: Watabou map, then monsters, then export

On Discord, pick a map with Watabou. Then in AMBA make some monster blocks and pick creatures for the encounter. With a map and creatures in place, the GM exports to both WG and Owlbear. After that export, share the WG join key in Discord if players need to join the campaign in the new WGUI. Never share the API key. If the new map or encounter should be on the player packet, check those nodes on the publish tree and save; players refresh the syndication bookmark.

8. Sample combat

Together we make a medium XP encounter. Export that encounter to WG and import it from Owlbear. PCs leave the Party bench and join the encounter. Every enemy and ally should be represented. Combat starts with initiative in the new WGUI tracker. Talk out loud about who can click what. Reveal the combat map or aftermath nodes on the player publish tree if those belong on the packet.

9. Sample skill check

Use the new skill-check challenge screens and an encounter that contains challenges. Put one trap and one social challenge in the same encounter. Run both on the call so we see whether the new screens and the mixed encounter hold up. Publish player-safe challenge or handout nodes after they resolve; leave GM notes and unreached scenes unchecked.

10. Write it down

Drop notes on feedback whenever something clicks or stalls—during the call is fine. What worked, what blocked, whether a later sit-down should be longer or split. No need to wait until the end.