WGUI
Players log into WG here. They never log into AMBA.
If you already build in Pathbuilder and fight on Foundry (or a Discord bot + a map), this is the same split: WG is the sheet, new UI is live combat, AMBA is GM-only prep. Build in old and/or new UI; combat on the call is new UI only. Two public characters, export JSON, drop files on Upload. We pick four of eight on Discord; the GM downloads those four from Upload.
Party
PCs so far
| Hero | Name | A/B/C | Level | Player |
|---|
No public sheet links yet.
Log in on this site to paste your two public WG sheet links. We fetch the read-only sheet at /sheet/… after you turn on Public Character.
Your public sheet links
Two links per player. Old UI: amba.wandersguide.site/sheet/…. New UI: wgui.wandersguide.site/sheet/…. Same public, read-only sheet. You can edit or delete a link later.
Old UI (original builder): amba.wandersguide.site. New UI: wgui.wandersguide.site. Same WG account on both—like Pathbuilder 2e desktop vs web, not two different characters. The GM keeps AMBA on the Discord share. Players do not need AMBA accounts: they use the player syndication link (Session step 6) for the adventure packet. Optional: an AMBA account plus module sharing to follow encounter design (Session step 5).
Public Character — old UI and new UI
Turn on Public Character for both PCs so anyone with the sheet link can open them—the equivalent of a public Pathbuilder share, not a locked Foundry actor. Same label in both UIs; different clicks to get there.
- Old UI: Open the character in the builder (
/builder/…). Use the Home step (house icon, first stepper step). Open the Options tab (last of Books, Homebrew, Variant Rules, Options). Switch on Public Character (after Organized Play, before Voluntary Flaw). - New UI: Open the character builder (sheet with
?view=builder, or Characters → that PC). Stay on the Home step (not Builder). Open the Options tab. Switch on Public Character.
Use old UI, new UI, or both for building. Do not skip the public switch.
Before the call
Sign in with your own WG account. Create two characters that are not twins. Make both public. Export each character’s WG JSON. Then drop both files on Uploads. Do not log into AMBA. Do not ask for the GM API key.
When the group meets
When we first meet on Discord, pick four of the eight to play. The GM then downloads those four from Uploads and imports them as PCs in the AMBA module, then creates the WG campaign and posts the join key. Enter the key in the new UI. That makes you available for the campaign. You should not appear under Characters on the GM’s WG account—that list is the GM’s characters if AMBA is linked. You should appear on the Party bench in encounters. The four leftover files stay unused for this run.
What the GM does (still in AMBA)
After Discord pick, download the four chosen JSON files from Uploads. Import them as module PCs. Link WG from the AMBA avatar menu (Settings → Wanderer's Guide), then Create campaign in the module’s WG settings and post the WG join key in Discord. Combat is designed and fired from AMBA. Players watch and click in the new UI only.
Combat and skill — new UI only
On the call, open the new UI (wgui.wandersguide.site). Leave the old builder. The table designs a moderate XP encounter and one skill in AMBA. Confirm the four chosen PCs on the Party bench. Combat notes stay in the new UI, not on the map.
If the bench is empty
Joined players may not show on the Party bench in every encounter, and the API may not update WG in real time. If they never show, mention it on feedback and continue to Owlbear with tokens placed by hand if needed.