Skip to main content

Character vault for players and DMs

A character vault built for play, sharing, and DM prep.

The vault holds every character you build. Player characters and non-player characters share the same vault foundation and the same sharing controls, while the editor uses PC and NPC section layouts where the product needs them. Build once, connect the record to a campaign, and share only the sections the party should see.

The two panes below use a PC example: the full editor record on the left, and a section-selected share on the right.

Character record

PC

Irelen Vaska

Half-orc druid, coastwatch exile

  • RaceHalf-orc
  • ClassDruid, Circle of the Shore
  • BackgroundCoastwatch apprentice
  • CampaignThe Long Tideward

Identity

Pronouns
she / her.
Alignment
Chaotic good.
Signature item
A driftwood staff carved with the tide marks of the Low Reach.

Appearance

Appearance
Green-skinned, saltwater braid worn to the shoulder, a half-healed brand under the left ear. Carries a gull feather behind the staff strap.

Personality

Personality
Quick to cross a stranger, slow to leave a friend. Trusts what the weather tells her before what a city council does.
Bonds
Will not abandon the Low Reach shoreline while its villages still fish it.
Fears
Fire on open water. The exact color the sky goes before a red tide.

Backstory

Backstory
Apprenticed to the coastwatch at Merrow Spit. Exiled after she broke a ceasefire to pull a child out of a burning longboat. The coastwatch still writes her name out of its winter rolls.
Origin place
Merrow Spit, a timber-built fishing town on the Low Reach, where the coastwatch keeps a lantern lit for every ship it once lost.

Story Hooks

Goals
Bring proof of the red tides back to the coastwatch without being arrested for it.
Plot hooks
A sealed letter from Ansel, the coastwatch captain who exiled her, offering a conditional return. A debt owed to the smuggler Par for a safe passage at Kelp Point.
Open questions
Whether the red tides are seasonal or something older wearing a season as a mask.

People & Relationships

Important people
Ansel, coastwatch captain, complicated. Par, smuggler, friendly. The child she pulled from the longboat, now a courier in Stonemere, safe.

Writings

Latest writing
A letter to Ansel, unsent. Two short songs in the coastwatch meter. One shoreline sketch in the margin of a weather log.
DM Only on this recordDM only

Every character record carries a DM Only section in the editor: Secrets, DM notes, visibility, and session-tracking fields. Secrets can be shared deliberately; DM notes stay editor-side.

Secrets
The red tides are being seeded upriver by a cult that has already bought a coastwatch officer. Ansel does not yet know which one.
DM notes
Irelen will accept the conditional return when the cost is paid in something she can still recognize as herself. That is the pivot.
Visibility
DM only on this record.

Two ways to run it

Edit the record directly, or let the session feed it.

Both paths are valid. Most DMs use a mix: write the record by hand for the lines that matter most, and let the session rhythm carry the rest.

Path A

Edit the record directly.

Open the character in the editor and write into the sections you need. Save when you are ready. Nothing on the vault record is ever required to be filled in.

  1. 01Start with the section you care about

    Identity, Story Hooks, or Personality are common first stops. You can skip the rest for now.

  2. 02Write as much or as little as fits

    One sentence in Appearance is enough to start. Rich text, links, and mentions to other records in your campaign work in every prose field.

  3. 03Save and keep playing

    The record updates in place. Other campaigns this character is linked to see the same record.

Path B

The recommended rhythm after a session.

When session notes are flowing, let Multiloop help. Nothing writes without review, and you always keep the final edit.

  1. 01Write the DM session notes

    The DM writes the session notes that already happened. Players can add their own notes on a shared surface when the campaign wants that.

  2. 02Optionally paste in a backstory or sheet

    Character import reads a pasted document or a PDF and pre-fills the record for review. You pick what saves.

  3. 03Run Analysis on supported surfaces

    Analysis reads the character record, relationships, writings, play journal, and linked campaign context when available. It proposes suggestions for relationships, writings, summaries, and supported character fields.

  4. 04Review, approve, and share the right sections

    Approve the suggestions you want saved. Then share the character and pick which sections appear on the share; leave Secrets, Rumors, DM Q and A, and Open Questions off unless a specific reader should see them.

Sharing

How character sharing works.

A character share is its own record. You pick the sections that appear on the share, you optionally set a password, you optionally set an expiration, and you can revoke any link in one click.

Shared sections
Each section on the record gets a checkbox. Leave one unchecked to hide the whole section from the share. Section order is kept from the record.
Optional password
A minimum four-character password protects a link. Character details and images stay out of social previews on protected shares; open shares can show the normal preview.
Expiration
A share can expire on a specific date. Expired links stop working for readers and stop showing social unfurls. The record itself is never affected.
Revoke any time
Delete a link and it stops resolving. New links can be created with a different section mix for a different audience.
Copy for Discord or forums
Each active link has a one-click copy to drop a formatted card into Discord, or a forum-flavored block into a play-by-post thread.
QR code and view count
Each link carries a QR code for in-person play and a live count of how many times the share has been opened.

NoteSection visibility applies to whole sections. Multiloop does not mask individual fields inside a shared section.

DM only

DM-only material lives on every record.

Every character record carries a DM Only section in the editor with Secrets, DM notes, visibility, and session tracking. Secrets can be included on a share only when selected; DM notes stay in the editor.

On the record

Open the character in the editor. The DM Only section holds Secrets, DM notes, a visibility setting, Last Seen Location, and Last Session Appeared. Write freely; DM notes are not part of a public character share.

On a PC share

When you share a player character, Secrets render inside the Story Hooks area only when you include the Secrets section. Leave Secrets unchecked to hide that line on the share.

On an NPC share

When you share a non-player character, Secrets render as their own DM Secrets section only when you include the Secrets section. Leave Secrets unchecked to hide the section entirely.

Dedicated surfaces for table prep

Secrets, Rumors, DM Q and A, and Open Questions are off by default on a new share. Include them deliberately for a specific reader when a session needs them in someone else's hands.

What a record holds

The sections a vault record can use.

PCs and NPCs share the same vault foundation, then use different section layouts where the product needs them. PC records lean on Story Hooks. NPC records lean on Quick Reference, Background, Relationships, and a dedicated DM Secrets section on shares.

  • Identity

    Name, race, class, subclass, background, age, alignment, pronouns, deity. Appears on both PC and NPC records.

  • Appearance

    Two or three sentences you can read aloud at first meeting. Physical Details is its own subsection for height, hair, eyes, marks, voice, attire.

  • Personality

    Personality, Ideals, Bonds, Fears, Weaknesses, Mannerisms, Speech patterns, Motivations, Quotes, and Common phrases. The same section on PCs and NPCs.

  • Backstory

    On PC records, Backstory holds the main prose, Life phases, and Origin place. On NPC records, the shorter Background section covers the same ground.

  • Story Hooks

    PC records use Story Hooks for Goals, Plot hooks, Open questions, Secrets, and Story arcs. NPC records use Background plus the DM Secrets share section instead.

  • People & Relationships

    Named party members, NPCs met, and companions live on each record. Full relationship records, with types and perspectives, live on the campaign.

  • Writings

    In-character letters, journals, poetry, songs, and sketches. Each writing carries a type, a recipient, and an in-universe date when you want it.

  • Inventory

    PC inventory covers equipment, magic items, treasure, and quest items with rarity and magical flags. Signature items and possessions sit alongside the inventory list.

  • Gallery

    Portraits, scene art, and references. One image flags as the primary; captions and display order travel with the record.

  • Sessions

    A PC play journal per character: session number and date, summary, NPCs met, locations visited, loot, and thoughts for next session.

  • Tags and affiliations

    Vault tags give you a reading cut across characters. Faction memberships track standing, joined and left dates, and a primary-faction flag.

  • Campaign context

    PC campaign context: game system, external campaign name, DM name, party name, joined and retired sessions, and a pre-session hook for when they next sit at the table.

Play and travel

The record is the source of truth, across every campaign it joins.

A character lives in the vault. Campaigns link to the record and read the same state a DM would see on the editor. Writings, sessions, and relationships travel with the character.

Link into campaigns where the character is in play.

Bring the same character record into multiple campaigns that use it. Each sync link keeps the vault record as the source of truth; campaign-specific context sits in the record's Campaign section.

Play journal per character.

Session entries sit on the character: session number and date, a summary, who the character met, where they went, and thoughts for next session.

Writings travel with the character.

The letters, journals, and songs a character writes in one campaign stay on the record when the character is linked into another.

Share pages for the specific audience.

Create one share for the whole party, another for the DM of a guest campaign, another for a forum thread. Each share picks its own sections, password, and expiration.

How suggestions behave

What Smart suggestions actually do here.

Analysis is review-first. It reads the material the character already has and proposes changes; you approve what saves.

  • 01Analysis reads the character record, relationships, writings, play journal, and linked campaign context when available. It proposes suggestions for relationships, writings, summaries, and character fields where the apply path supports them.
  • 02Character import reads a pasted backstory, a character document, or a PDF and pre-fills the record for review. You see the filled record in the real editor and choose what saves.
  • 03Nothing writes without review. Suggestions sit in a queue on the character; you approve, edit, or reject each one.
  • 04Apply behavior per suggestion type matches what the apply path ships. Public copy does not promise silent background writes or edits the product does not make.

Common questions

Questions this page hears from DMs and players.

Do PCs and NPCs use identical sections?
They share the same vault foundation and many fields, but the editor and share surfaces are not identical. PCs lean on Story Hooks, Inventory, Campaign Info, Player Meta, and Sessions. NPCs lean on Quick Reference, Background, Relationships, and DM Secrets. Both can carry Identity, Appearance, Personality, Writings and Reference, Gallery, Connections, and DM Only material.
Can I keep individual fields private inside a shared section?
No. Sharing is section-level. Leave a whole section unchecked to hide it; Multiloop does not mask individual fields inside a shared section. Secrets, Rumors, DM Q and A, and Open Questions are off by default for that reason.
Can a share expire or be password-protected?
Yes to both. Passwords use at least four characters. Expiration is a date the link stops working. Either can be off, and either can be added or removed later by editing the link.
Does a character belong to one campaign?
No. A vault character can be connected to more than one campaign when those campaigns use that character. The record stays the source of truth; campaign-specific context lives on the record's Campaign section.
Does Analysis update records without asking?
No. Analysis proposes suggestions; you review and approve. Character import pre-fills a record from a document for review. Apply behavior per suggestion matches the current apply path.
Can a share be revoked after the fact?
Yes. Deleting a share link stops it from resolving for anyone. You can create a new link with a different section mix, password, and expiration at any time.

Get Early Access

Build a character record that stays useful in play.

One character record. Many campaigns. Share-safe sections for the party, DM-only material on the record, and a rhythm that keeps both in sync after the game.