Wanderer’s Guide
Bring characters for the party pool
WG is where player characters start. You can save up to six public WG characters here, and they will appear on the Signup page for the group to see. The GM sets how many characters from each player are considered for this run. Once the party is chosen, each player keeps one character in the party and removes their extras.
Party
My PCs
| Hero | Name | A/B/C | Level | Player |
|---|
No PCs yet.
Log in on this site to save your public WG sheet links. You can add a few options, and we will choose a good party mix together before the warmup.
Your character options
You can save up to six WG character options here. Public characters use a sheet link; private characters use a saved WG JSON archive and show up to the group as Private character. The old WG UI and new WG UI use the same account and character data, so use whichever builder feels better.
Saved characters show up on the Signup page. The GM can set how many characters per player are considered for the warmup. After the table picks the party, each player keeps the character they are playing and removes their other characters from the party list.
I have a private character
If this character is staying private, upload its WG JSON first, then choose that saved file here. The party list will show it as Private character.
Old UI: amba.wandersguide.site. New UI: wgui.wandersguide.site. Same WG account, same characters, two different ways to work with them. Players use WG for character sheets and the new combat view. AMBA stays mostly on the GM’s screen, unless someone is curious and the GM shares access.
Have a character on Pathbuilder?
Easy: bring it into WG with WG’s importer first. Once it is in WG, make it public and save the sheet link here. If you want to keep that character private, then export WG JSON and use Uploads instead.
- In Pathbuilder 2e, open the character, use the menu, and choose Export JSON. Pathbuilder can give you a JSON ID, and you can also save the exported JSON file.
- In the new UI, open Characters (wgui.wandersguide.site).
- Open the import menu next to Create Character (upload icon). Choose Import from Pathbuilder.
- Paste the JSON ID or upload the exported Pathbuilder JSON file. That creates a WG character on your account.
Once the character is in WG, treat it like any other WG PC: turn on Public Character and save the public sheet link here. Bringing a few different character options is welcome; the GM will set how many are considered for the run. Use Uploads only for characters that are staying private.
Public sheet links
Turn on Public Character for any PC you want the group to consider. This part is required: the site uses the public sheet link to show your character on Signup, and the group needs to be able to open the sheet before choosing the party.
It works like a shareable Pathbuilder link: people with the link can view the sheet, but they are not editing your private character. The setting has the same name in both WG UIs; the clicks are just a little different.
- 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. Just make sure the character is public before saving the sheet link here.
Before the call
Before the call, bring any WG characters you want considered, up to six. Make each one public and save the public sheet links here. More than one option is helpful, but everyone will only play one character once the party is chosen. If a character is staying private, export that one as WG JSON and put it on Uploads.
When the group meets
In Discord, we will look at the characters on Signup and pick a party that seems fun for the warmup. The GM controls how many characters from each player are in consideration. Once the party is picked, each player keeps one character in the party and removes their extras.
The GM imports selected public characters from their WG links, uses uploaded JSON for any private characters, creates the WG campaign, and shares the join key. Paste that key in the new WGUI so your character can appear on the Party bench for encounters.
What the GM connects
After the group chooses characters, the GM imports the selected public WG links into AMBA and downloads any private-character JSON files from Uploads. From there, the GM connects WG, creates the campaign, and shares the WG join key. Players use that key in the new WGUI; the GM keeps the API setup private.
Combat and challenges
On the call, we will use the new WGUI for combat and challenge screens. It may look a little different if you are used to the old builder, but the warmup only needs one round and one challenge moment. Enough to see where everything lives.
If the bench is empty
If joined characters do not show up on the Party bench right away, no panic. We will note what happened, keep going, and use Owlbear with manual tokens if needed. That is exactly the kind of thing the warmup is meant to uncover.