AMBA – Adventure Maker for Tabletop RPGs

Exports to Wanderer's Guide and Owlbear

Draft anywhere → assemble in AMBA → publish or run elsewhere

More structure than editor

An adventure as connected parts, not just a long document

AMBA treats an adventure as a structured collection of connected parts. Each act, scene, and encounter is a typed object with known relationships — not merely a heading in a document. Maps, handouts, monsters, and GM notes stay attached to the right place in the module tree.

That makes it practical to reorder whole branches, find every encounter in an act, export selected scenes, and prepare player-facing output without exposing GM-only material.

ActsCampaign-scale chapters

ScenesStory beats with attached material

EncountersMaps, monsters, treasure, handouts

Assemble

Bring mature drafts from Docs, Obsidian, Word, or notes into the module.
Organize material into acts, scenes, subscenes, and encounters.
Keep maps, NPCs, treasure, and handouts in context as the adventure grows.

Structure

Work with typed adventure nodes instead of freeform link webs.
Navigate a module tree from outline to encounter detail.
Use Pathfinder 2E tools alongside broader TTRPG authoring workflows.

Deliver

Register redeem codes so buyers load purchased modules for free.
Customers get the same WG, Pathbuilder, and Owlbear exports you built in.
Syndicate readable web pages and generate PDF output.
Validate incomplete sections before you publish or run.

Publish an encounter, run it faster

Combat, characters, VTT, and player links — without rebuilding the encounter in every tool

Once an encounter is structured in AMBA, export it in a few clicks. Maps, creatures, tokens, and narrative travel as structured data — so you are not rebuilding stat blocks, placing every token by hand, or copying narrative into separate apps.

Combat (WG)

Right-click a scene, subscene, or encounter and choose Export to WG.
AMBA resolves PF2e creatures against the ruleset and creates a WG encounter with proper enemy combatants, counts, and stats.
Link a module campaign once; players join with their own characters for live combat tracking.
Encounter narrative can land on a matching WG Notes page alongside the combatants.

Characters

Export PF2e PCs and NPCs to Wanderer's Guide for live sheet management.
Export Pathbuilder-compatible JSON snapshots from character sheets.
Import updated characters from WG back into the module.
Combat Simulator export for quick one-off monster-block tests.

VTT

Owlbear Rodeo — push maps, numbered monster tokens, stat cards, and optional PC tokens into the open scene.
Grid calibration stored on the map artifact travels with the export.
Foundry VTT — planned path for scenes, actors, and installable adventure modules.
Re-import updates the same scene items instead of stacking duplicates.

Syndicate & share

Publish a single encounter, scene, or selected branch as a read-only public link.
Share player-safe HTML without exposing GM-only material elsewhere in the module.
Generate PDF packets when you need a printable table reference.
Register redeem codes so buyers load purchased modules and get the same exports.

Assemble once in AMBA → export to WG and Owlbear → run at the table

Not where you write every word

AMBA is where the pieces become an adventure. Publishers assemble and ship for free. Customers redeem and play for free — with exports to the tools they already use at the table.

Free for publishers. Free for players.

AMBA is free.

Open Adventure Maker View feature map