Importing workshop prep and bundles

Bringing maps, monsters, NPCs, encounters, lore, tables, storyboards, shops, house rules and pregens from a workshop or a shared bundle into a campaign, and what happens to name collisions.

Desktop appAndroid appBrowser

Prep made in a , or received from another table as a , comes into a campaign through one import. The import is a plan first and a copy second: it previews what would be overwritten, lets you tick what to take, and renumbers anything whose name collides with something already there. Importing the same prep a second time keeps what the first import brought instead of adding numbered duplicates.

From a workshop

  1. At campaign creation, or from the lobby's Import, choose a you own.
  2. The planner lists every kind it found: maps, , , monsters, , , , shops, , , , and a world. Tick what you want.
  3. The preview shows collisions (a lore entry with the same title already in the campaign, say) and how they will be renamed.
  4. Import. The rows are copied into the campaign inside one transaction, with every link between them kept (a fight's map, a place's map and sound, an NPC's voice, the 's paths and labels); the workshop is untouched.

A storyboard imported into an AI campaign becomes 's plan; the Dungeon Master follows its beats. At an AI table the storyteller sees the prepared fights and can run one, and the prep's private notes reach its prompt. Prepared encounters deploy from the console or when the Dungeon Master calls them. A Market shop arrives with its place, keeper, shelf and policy, and starts its restock cycle on the campaign's clock. Pregens land in the campaign's party list for players to pick.

From a bundle

A 's Share tool exports a .odm-workshop.json with its pictures inside: map backdrops, portraits, monster art. Importing a bundle offers every kind as a tick, included, so a lead who wants only the monsters takes only the monsters. A bundle carries the links between its pieces, the draft and the document, and a 's bundle names the shared prep it depends on. in a bundle arrive as sheets checked by the character builder's own rules on both sides. A bundle imported into a workshop seats the person importing it as that workshop's Dungeon Master.

The workshop's Share tool: what the bundle will carry listed by kind with counts, and the export button
The Share tool lists what a bundle carries before it is written.

World packs

A is not prep; it is a reskin of the rules. It is chosen at campaign creation from the packs installed on the server, and a 's Plugin tool builds one. See Content pack and world packs.

Prepared worlds

The of community packs can also list whole prepared worlds; installing one from the plugin browser creates a with its maps, cast and ready to import.

Cloning instead

To reuse an entire campaign's setup for a new party, clone the campaign from the home screen. Prep, and settings travel; the and the seats do not.

Checked against desktop and Android app 0.17.2 and server 0.26.2 on 2026-10-11. Something wrong or missing? Open an issue.

Download · v0.17.2
Server app · v0.26.2

Optional. Runs the table for a whole group on one machine that stays on. Everyone else just installs the app.

Free & open source · MIT licensed · served from GitHub releases