West Marches breaks on continuity, not on scheduling

The format is designed so no single person has to be at every session. That is the whole point, and it is also the failure mode: after a few months nobody alive knows what happened in the world, including you.

The problem

A West Marches game has fifteen to thirty players, ad-hoc parties drawn from whoever is free, and a persistent world that everyone’s actions change. Continuity is not a convenience here, it is load-bearing — and the traditional fix, a wiki somebody volunteers to maintain, decays the moment that person gets busy.

The format’s known failure mode

Every write-up of running West Marches lands on the same problem: the shared record. Players who were not on last week’s expedition need to know what it found, parties need to not re-clear the same ruin, and a GM needs to know which faction the Tuesday group annoyed before the Saturday group walks into it.

The usual answer is a player-maintained wiki and session reports written by whoever volunteers. It works while enthusiasm holds. What it does not survive is a busy month, and a West Marches game that loses its record loses the thing that made the persistent world persistent.

A wiki nobody has to volunteer for

Recording each expedition produces the write-up automatically: what the party found, who they met, what they left unresolved. Entities extracted from every session accumulate into one campaign wiki, so the world’s record grows from play rather than from somebody’s free time.

The read-only shared wiki link is close to purpose-built for this format and is not framed that way anywhere else on this site: your whole roster can browse what has been revealed, with your GM notes stripped, and none of them need an account to do it. For a twenty-player game, "no account needed" is the difference between a resource people use and one they do not.

Multiple GMs, one continuity

Open tables often run with more than one GM, which multiplies the problem: two people now need to stay current on a world neither of them sees all of. A shared record built from every session, searchable with citations back to the expedition it came from, is the cheapest way to keep co-GMs in sync without a weekly handover meeting.

If your co-GMs need their own accounts, Guild Master links up to four others onto one plan, each with their own hours.

Play-by-post and text expeditions count too

Plenty of open tables run downtime, travel or whole expeditions in text on Discord or a forum. That content is already a transcript, so it can be imported directly — paste it in or upload a .txt — and it runs the same chain as recorded audio: entities into the wiki, relationships, a recap. It consumes no transcription hours, and every plan includes imports (two a month free, ten on Dungeon Master, unlimited on Guild Master).

For a format where half the world-changing decisions happen between sessions in a text channel, that is not a side feature.

The format is having a moment

Critical Role’s fourth campaign, which began in October 2025, splits thirteen players across three groups playing at separate tables in one shared world, with actions in one affecting the others. Coverage has connected it to West Marches directly. A format that used to need explaining now has the largest actual-play show in the hobby demonstrating it weekly — which is worth knowing if you are pitching an open table to your own group.

The numbers, with sources

WhatValueSource
Critical Role Campaign 4 — structureWest Marches style; 13 players split across three groups at separate tables in the shared world of Aramán, GMed by Brennan Lee Mulligan; began 2 October 2025sourceas of 2026-08-15
DM Scribe — transcript imports by planAdventurer 2/month; Dungeon Master 10/month; Guild Master unlimited — none consume transcription hourssourceas of 2026-08-15
DM Scribe — linked accountsGuild Master links up to 4 additional accounts, each with their own 30 monthly hourssourceas of 2026-08-15

This is not for you if…

Your open table already has a player who loves maintaining the wiki. Do not replace a working social arrangement with a subscription. A volunteer archivist who enjoys the job produces better, more opinionated write-ups than any model, and the fact that a player cares enough to do it is worth more to the game than the record itself.

Your expeditions are short and rarely recorded. A West Marches game running ninety-minute sessions on an ad-hoc basis may never accumulate enough audio for the wiki to reach the density where it starts being useful.

  • A player already maintains the wiki and enjoys it
  • Your sessions are short, ad-hoc and mostly unrecorded
  • You need scheduling or roster tools — this is not one
  • Your world is authored up front rather than discovered in play

Other ways people use this

  • Actual play and podcast crews

    Actual play crews already have clean multitrack audio. Turn it into show notes, a searchable archive and accessibility transcripts.

  • Professional and paid GMs

    Running paid games for several tables means the worst continuity problem in the hobby — and a business reason to solve it. How the notes help.

  • Daggerheart tables

    Nothing in the pipeline is rules-aware, so Daggerheart transcribes and extracts like any other game. The prompts say D&D. Here is what to do about it.