Campaigns
Multiloop keeps the DM session notes, the NPCs, the quests, the locations, the timeline, and the player side of the world connected. You can edit every record by hand, or let the recommended rhythm carry most of the bookkeeping while you focus on the next session.
Same workflow for a single one shot and a three-year campaign. Use every module, or just the ones your table actually cares about.
Two ways to run it
Both paths use the same campaign, the same records, and the same share view. The recommended rhythm is faster after most sessions, but the manual path is always there for the scenes you want to shape by hand.
The rhythm
The fastest path through a session, start to share. Every step maps to a real product surface in Multiloop.
You write this
Date, a one line summary, the three beats that actually happened, and whatever prose you want to remember. Bullet points or full prose, your table's voice.
Optional
Switch the session to open when you want the party's perspective. Players with a character in the campaign can add their own recap. You can keep the session private or lock it later.
Analysis
Analysis reads DM notes, shared player notes, and the campaign context you already have. It proposes reviewable updates across supported records.
Your review
Proposed suggestions are grouped by record type with the source excerpt, a reasoning note, and a confidence marker. Approved suggestions can create records or update supported records. Unsupported field edits stay in the native editor.
Player side
The campaign share view updates as you approve Analysis suggestions and edit records by hand. Players open it by link, optionally behind a password. You pick which sections show.
The modules
Run a session note only campaign or lean into the full world. None of these modules is required, and every one of them feeds the same session notes, Analysis suggestions, and campaign share view.
Story and structure
The shared frame for the world: what the game is about, how the arcs fit together, and what the party is living through session by session.
Premise, tone, themes, setting, central conflict, and house rules. The campaign bible in one place.
Arcs and chapters that group sessions into the shape of the campaign so far.
A session record with date, summary, notes, arc, attending characters, and links to everything the session touched.
Chronological events with in world dates, session references, and major event flags for the moments that reshape the story.
People and places
The living record of who is in the story and where it happens. Known to the party, DM only, or somewhere in between.
Name, role, voice, last scene, goals, secrets, and player-view setting. NPCs live alongside party characters.
Organizations with type, status, known-to-party flag, headquarters, parent faction, key members, and DM only notes.
Parent chain, type, status, inhabitants, player view summary, and DM only notes and secrets.
How characters, NPCs, and factions connect. Seeded labels plus perspectives, status, and a known-to-party toggle.
Quests and play
The forward pressure of the game: promises to track, encounters to prep, and the loot the party is carrying.
Main quests, side quests, personal goals, faction missions, plot threads, and rumors. Status, next action, and session links.
Combat, social, puzzles, traps, and skill challenges with prep notes and scene assets.
Party loot and important items with rarity, holder, and currency tracking.
Campaign maps with named pins for locations, handouts, and other references the table needs.
Player facing
What a player can read between sessions without logging in, and the pieces the DM chooses to show.
House rules, recaps, handouts, and anything a player should be able to re read on their own.
Images, documents, and references the DM shares with the table one at a time.
Campaign art, NPC portraits, and scene imagery tied to the records they belong to.
A visual relationship layout for the cast of the campaign, shown when the share view exposes it.
Analysis
After a session, Analysis reads DM notes, shared player notes, and the campaign context you already have. It highlights the NPCs, places, quests, relationships, timeline moments, items, and character changes it can support. You review each suggestion. You approve the ones that belong. Nothing changes without your review.
Approved suggestions can create records or update supported records. Unsupported field edits stay in the native editor so you can write the prose yourself.
Campaign share view
The campaign share view lives at its own link. You can hand it to the table, protect it with a password, and choose which sections appear. Players do not need an account to read it, and the view reflects what you have approved and edited.
One URL per campaign, generated from the campaign. Share it with the whole table.
Gate the view behind a password when a campaign is sensitive or includes private lore.
Turn sections on or off: Campaign Bible, Player Guide, Session Zero, Guide, The Party, NPCs, Relationships, Story Structure, Quests, Sessions, Timeline, Locations, Factions, World References, Encounters, Items and Loot, Maps, Handouts, Gallery, and Character Canvas.
Shared records respect their player-view setting or known-to-party flag. DM-only material stays out unless a share section explicitly allows it.
Collaboration
Invite a co-DM or a player, and the session page shows who is typing and where their cursor is. Access controls cover the common cases, and each record carries its own player-view setting so a secret stays a secret even when a session is open for notes.
Character import
Paste or upload a character sheet, a backstory document, or a roster of NPCs. Character import reads it and prepares a draft of the characters — stats, backstory, image. You review each one in the real editor and approve what saves. Nothing is imported silently.
Step 1
Paste or upload
Step 2
Review the draft
Step 3
Approve what belongs
Every record is manually editable. You can run a campaign in Multiloop without ever opening Analysis. The rhythm is a recommendation, not a requirement.
Analysis reads DM notes, shared player notes, and the campaign context you already have, then proposes reviewable suggestions. Approved suggestions can create records such as NPCs, quests, locations, factions, timeline events, encounters, and relationships, and can update supported records such as character fields, relationships, item holders, combat status, and quest and session links. Unsupported field edits stay in the native editor.
No. The campaign share view opens by link and can be protected with a password. A Multiloop account only matters if a player wants to claim a character or add their own session notes when the DM opens the session for notes.
No. The share view is one page per campaign with a section rail for the parts of the world you want to expose. Individual records appear inside the relevant section with the details the DM has chosen to include.
Yes. Campaigns, adventures, and one shots share the same engine. A one shot can skip most modules and still keep its sessions, NPCs, and quests linked. Longer campaigns pick up maps, factions, timeline, and a share view as they grow.
No. Multiloop is the story layer between sessions. Keep using your preferred battlemap for play and your preferred character sheet app for stat blocks. Multiloop holds the notes, the world, and the connections that sit between sessions.
Get Early Access
Join the waitlist to be invited as we open seats.
