AMBA
The GM’s adventure workspace
AMBA is where the GM builds the adventure behind the scenes: notes, scenes, encounters, creatures, and player-safe handouts. GMs may find this the most interesting part of the warmup. Players do not need to use AMBA to play, but it can be fun to watch how the table pieces come together before they show up in WG, Owlbear, and the player handout link.
For the warmup, the GM can screen-share AMBA so everyone can see the prep flow in motion. The private setup stays with the GM: AMBA login, WG API key, and export settings do not go in Discord or on this site. Players just need the links shared during the call. Curious players are welcome to follow along; future GMs especially may want to see what AMBA is doing.
What the GM sets up
Start by creating a small empty module or adventure in AMBA. Think of it as a named shell for the warmup. Once the group chooses characters, import the public characters from their WG links, or use uploaded WG JSON files for any private characters.
Later, when it is time to connect WG, open AMBA settings and add the Wanderer’s Guide API details from the GM’s WG account. After the WG campaign is created, share the WG join key in Discord. That join key is for players; the API key stays private.
Player handouts
AMBA can also make a player-only link for revealed adventure material. This is not the GM’s full prep tree. It is more like a living handout packet: the GM chooses which nodes are visible, players bookmark the link, and they refresh it when new material is revealed.
For the warmup, start small: an overview, a no-spoiler handout, maybe an Act 1 intro or map. Later scenes and GM-only notes can stay hidden until the table reaches them.
What players need
Most players do not need AMBA to play. They make or import characters in WG, share public sheet links, join Discord, and open the player handout link when the GM shares it. If someone wants to keep a character private, they can use Uploads for that character’s WG JSON file.
That said, AMBA may be interesting if you like seeing how a session gets built. If someone wants to follow along more closely during the warmup, the GM can use AMBA module sharing. That is optional. Screen-share is enough for everyone else.
What we are noticing
During the warmup, we are mostly watching whether the pieces line up cleanly: WG character import, campaign join key, Party bench, Owlbear export, and the player handout link. We are also noticing whether AMBA feels useful and understandable from the GM side. If something feels smooth, confusing, or worth changing before the real session, drop a note on feedback and keep playing.