Where AMBA Fits

For most authors, the best workflow is probably to do the heavy drafting wherever they are most comfortable and bring material into AMBA once it is fairly mature.

Draft anywhere → assemble in AMBA → publish or run elsewhere

You might write a scene in Google Docs, develop lore in Obsidian, sketch an encounter in a notebook, generate a map in another application, and keep reference material scattered across several sources while an adventure is taking shape.

AMBA becomes useful when those pieces need to become one coherent adventure.

AMBA Is More Structure Than Editor

AMBA includes Markdown and HTML editors, but text editing is not its primary strength. A dedicated writing tool will generally provide a better environment for developing long passages of prose, revising dialogue, brainstorming ideas, and reorganizing paragraphs.

AMBA's strength starts at a different level. Instead of treating an adventure primarily as a document, AMBA treats it as a structured collection of connected parts.

A module can contain:

Module
 ├─ Act
 │   ├─ Scene
 │   │   ├─ Subscene
 │   │   └─ Encounter
 │   │       ├─ Map
 │   │       ├─ Monsters
 │   │       ├─ Treasure
 │   │       └─ Handouts
 │   └─ Scene
 └─ Act

Those are not simply headings in a document. They are actual objects with known types and known relationships. AMBA understands that a scene belongs to an act, that an encounter belongs somewhere inside the adventure, and that maps, handouts, monsters, treasure, hazards, and other artifacts can belong to particular parts of that structure.

That distinction becomes increasingly valuable as an adventure grows.

Structure Without an Everything-Links-to-Everything Graph

Many excellent campaign and worldbuilding tools are built around freeform linking. An NPC can link to a city, which links to a faction, which links to a session, which links to another location, which links back to the NPC.

That approach is extremely powerful, particularly for building worlds and maintaining long-running campaigns. It can also become complicated. The larger the project becomes, the more responsibility falls on the author to understand what every relationship means and to keep the resulting web of links understandable.

AMBA deliberately takes a more constrained approach:

• An Act contains Scenes.
• A Scene can contain Subscenes and Encounters.
• An Encounter can contain the material needed to run that encounter.

The structure itself communicates meaning. You generally do not create arbitrary links from Act 1, Scene 3 to Act 2, Scene 4. If those scenes are narratively connected, that connection still lives in the author's understanding and in the written adventure.

AMBA does not try to model every possible relationship in a fictional world. Instead, it focuses on modeling the structure of the adventure.

Why Typed Nodes Matter

Underneath the interface, an AMBA adventure is essentially a tree of typed nodes. That sounds technical, but the practical benefit is straightforward: the computer knows what each part of the adventure is.

A heading called "The Ruined Chapel" in a word processor is ultimately just text. In AMBA, "The Ruined Chapel" might specifically be:

Type: Scene
Parent: Act 2
Position: 3

Its encounter might be:

Type: Encounter
Parent: The Ruined Chapel
Position: 2

And that encounter might contain:

Map
Monster Block
Treasure
GM Notes
Player Handout

Because those relationships are explicit, the adventure can be manipulated as structure rather than merely as pages of text. That makes operations possible such as:

• Move a scene and everything inside it to another act.
• Reorder an entire branch of the adventure.
• Find every encounter in Act 3.
• Identify encounters that do not yet have maps.
• Count monsters, maps, handouts, or other artifacts.
• Calculate encounter or XP totals across a section.
• Export only selected acts or scenes.
• Produce player-facing material without exposing GM-only content.
• Validate whether particular parts of an adventure are incomplete.
• Clone or reuse sections while preserving their internal structure.

These are much harder to do reliably when the adventure exists only as one long document or as a loose collection of linked notes.

There is no reason one application needs to do all of these jobs well. Trying to turn AMBA into a better word processor than Google Docs, a better knowledge graph than Obsidian, and a better tabletop than Foundry would make it worse at the thing that makes it different.

             CREATE

 Google Docs
 Obsidian
 Word
 Maps
 Notes
 Existing material
       │
       │
       ▼
 ┌─────────────────┐
 │      AMBA       │
 │                 │
 │ Structure       │
 │ Assemble        │
 │ Organize        │
 │ Validate        │
 │ Manage assets   │
 │ Prepare output  │
 └────────┬────────┘
          │
          ▼

             USE

 PDF / Web
 Wanderer's Guide
 Owlbear Rodeo
 Other tabletop tools

The original writing does not have to begin in AMBA. In many cases, it probably should not. An author might develop a scene until it is 80–90% finished in Google Docs or Obsidian and then move it into its proper place in the module.

Once there, AMBA provides something the writing application does not: context inside the complete adventure. The text is no longer simply "a document called Scene 4." It is Scene 4 of Act 2, positioned after Scene 3, containing two encounters, three handouts, a map, an NPC, and a treasure artifact.

That is the layer AMBA is designed to manage.

AMBA is not only where adventures get organized. Once an encounter is structured — map attached, monster blocks in place, PCs defined for the module — you can publish or export that encounter in a few clicks instead of manually re-entering the same material in your combat tracker and virtual tabletop.

Because AMBA already knows what each piece is, the downstream tools receive maps, creatures, tokens, and narrative with far less prep on your side. You do not need to rebuild stat blocks in Wanderer's Guide, drag out a blank map in Owlbear, or hand-place a token for every goblin if AMBA can push the encounter as structured data.

You still run combat in Wanderer's Guide and the map layer in Owlbear (or another VTT). AMBA's job is to prepare and push structured encounter data — maps, tokens, creatures with ruleset-accurate stats, and player-facing pages — so session zero prep in those tools is mostly connection and review, not reconstruction.

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

If you sell adventures on DriveThruRPG, itch.io, Pathfinder Infinite, or similar storefronts, AMBA gives you publisher tooling at no cost: structure the module, attach maps and stat blocks, register a redemption code, and print that code in your PDF or download bundle.

Your customers get something equally valuable: a free tool they can use to play your content. They create a free AMBA account, redeem at /redeem, and the adventure lands in their library — ready to export to Wanderer's Guide for combat, Pathbuilder for characters, and Owlbear Rodeo for the map layer. You do not need to build or maintain a separate player app.

Each buyer receives a private copy cloned from your published release. Your master module stays on your account. The structured encounters, maps, and character data you built in AMBA travel with the redemption — so buyers are not rebuilding your prep by hand in three other applications.

From that redeemed copy, customers get the same play-at-the-table support you had while authoring:

• Character management — export to Wanderer's Guide or Pathbuilder.
• Combat — export encounters to Wanderer's Guide with ruleset-resolved creatures and stats.
• VTT — push to Owlbear Rodeo today; Foundry VTT support is planned.
• Read-only sharing — syndicate selected scenes or encounters as player-safe public links.

Publisher (free)                    Customer (free)
  │                                       │
  ├─ Assemble module in AMBA              ├─ Purchase PDF on storefront
  ├─ Register redeem code                 ├─ Sign up → /redeem → enter code
  ├─ Print code in download               ├─ Module appears in My modules
  └─ Ship structured adventure            └─ Play via WG, Pathbuilder, Owlbear

You publish once. Every legitimate buyer gets a free path from purchase to table — with maps, tokens, creatures, and exports already wired into the module structure.

Where This Could Go

A future integration with a tool such as Obsidian could make this division of responsibilities even stronger. Authors could continue working in a familiar writing environment while AMBA maintains the authoritative adventure structure.

Obsidian

Act 1/
  Scene 1.md
  Scene 2.md
  Scene 3.md

        ⇅

AMBA

Act 1
 ├─ Scene 1
 ├─ Scene 2
 └─ Scene 3

The goal would not be to replace Obsidian. It would be to let each tool do what it does best.