AMBA
GM builds a module or adventure here
AMBA is GM-only for editing—the adventure document and encounter list, not the player sheet. Think Foundry journal + bestiary, or the PDF you do not pass around. The GM writes a module or adventure, then exports it; in WG that object is a campaign. Players never log into AMBA. They do get a player-only syndication link as the GM reveals nodes.
Screen-share AMBA so the table can watch prep. Players never get an AMBA login and never get the API key. This signup site does not store that key. Export targets AMBA’s WG clone on the same server (original WGUI and AMBA’s newer UI both use that stack). Player handouts go out as a syndication bookmark, not an AMBA account.
What the GM does
Sign in to AMBA. Create an empty module or adventure first—a named stub. You cannot JSON-import PCs until that container exists. After Discord picks four of the eight, download those JSON files from Uploads and import them as PCs in the module. Do not design the act or export yet; that order is on Session. When you later export, open the avatar menu → Settings → Wanderer's Guide (second-to-last, above Redeem purchase code). Paste the API Key and Character Authorization URL from WG Account → Developer → API Clients. Pick Ours (amba.wandersguide.site). Never put those fields in Discord or this site. Create campaign in the module’s WG settings if needed. Copy the WG join key into Discord—not the API key. Players enter the key in WGUI. They should not appear under Characters. They should appear on the Party bench in encounters.
Player syndication (player-only link)
After the stub has an act, scene, and some player-safe nodes, the GM opens Settings → Player version → Create player version, then Copy player link into Discord. That URL is the module/adventure packet for players: no login, not the full GM tree. Manage publish tree is the checkbox tree: checked nodes are on the link; unchecked stay GM-only. Start with the initial set (overview, gazetteer, no-spoiler handouts, Act 1 intro). As the table reaches later scenes in the Session order, check newly reached maps and handouts and Save publish tree. Players refresh the bookmark. Do not send Full tree export to players.
What players do
Default: nothing in the AMBA editor. They log into WG, make two public characters, drop JSON here, and on the call enter the join key so they become available for the campaign. They should show on the Party bench, not under the GM’s Characters list. They also open the player syndication link from Discord and refresh it when the GM says nodes were revealed. Optional on the call: an AMBA account plus module sharing so they can follow encounter design (Shared dropdown, not a public clone). They still do not get the API key.
What we're curious about
Whether JSON-to-module PC import, API-key setup, and Create campaign feel obvious, whether joined players land on the Party bench (not the GM’s Characters list), whether the player syndication link stays spoiler-safe as the GM reveals scenes, and whether the WG campaign and Owlbear update when the GM acts from AMBA. If something is confusing, leave a note on feedback and keep playing.