The Dungeon Master
Who Never Forgets

DMLog keeps your campaign world in PLATO — every NPC state, every session log, every world-shaping decision. Your campaign is a room. The room remembers everything.

🧙 Campaign Tracker 👥 NPC States 🗺️ Session Logs ⚔️ World-Building

Your Campaign Is a Room

PLATO's delta recording means you track what changed — not the whole world. Every session, only what happened.

👥 NPC State Tracking

Track every NPC's current disposition, known information, secret motivations, and relationship to the party. When the party "accidentally" bumps into a contact from Session 3, DMLog knows exactly where that contact left off.

📜 Session Logs

File what happened after every session. Not a full narrative — just the deltas. Who met whom. What was discovered. What was left unresolved. Future sessions pick up exactly where you left off.

🗺️ World Continuity

When your player asks "what did we do in that tavern in Session 7?" DMLog answers. Your world has memory. Not just the DM's memory — a verifiable, queryable record.

🔍 Cross-Reference

Ask DMLog: "Which NPCs have we met who know about the Crimson Guild?" PLATO searches your entire campaign history. Connections you forgot surface automatically.

🎲 Dice Log

File critical dice rolls with context. "Nat 20 to convince the guard — but the guard was secretly a changeling." The roll and the story around it, permanently linked.

📋 Quest Threads

Track active quests, who gave them, what's the deadline, what's been done. When a player asks "are there any open quest threads?" DMLog surfaces them from the accumulated campaign history.

Session-by-Session Intelligence

The campaign timeline — queryable, not just narratable.

📅 Recent Sessions

Session 14 Party confronted the Merchant Guildmaster. Rolan (NPC) revealed as doppelganger. Lost the Crimson Seal to the party.
Session 13 Found the hidden vault beneath the old temple. Took the Crimson Seal — but broke the ward stone. Guild alerted.
Session 12 Met Rolan at the market. Passed the Persuasion check (DC 18). Rolan agreed to a secret meeting. Party suspicious — didn't share full name.
Session 11 The Crimson Guild introduced — merchant front, real operations under the docks. Rolan identified as Guild quartermaster.

Why DMLog Instead of a Notebook?

Because a notebook doesn't answer questions. PLATO does.

🔍 Searchable

Notebooks are linear. DMLog isn't. Ask "show me every time the party interacted with the Crimson Guild" — not "flip through pages until you find it."

🔗 Linked

Every NPC, location, quest, and session is a tile. Tiles can reference each other. You build a knowledge graph of your campaign, not a narrative.

👥 Shareable

Other players can be added to the campaign room. They can file their own observations. The DM isn't the only one taking notes anymore.

🛡️ Backed Up

Your campaign lives in PLATO. It survives your laptop dying, your notebook getting lost, your dog eating the page with the final boss's HP on it.

🌱 Compounding

The longer you use DMLog, the smarter it gets. Patterns emerge across sessions. "Every time you introduced a morally gray NPC, the party tried to kill them." DMLog surfaces the meta.

⚔️ Prep-Focused

DMLog files what happened. What should happen next is your job. The tool serves the DM, not the other way around.

How DMLog Fits Your Workflow

1

End of session: file what happened. 2-5 minutes of delta-entry. That's it.

2

Pre-session: query the room. "What was left unresolved?" "Who did we last meet?" Instant context.

3

During session: NPCs gain state. New information filed. Quest threads updated. No stopping the flow — just quick entries.

4

Post-session: the room is smarter. Your future self thanks you.

Your Next Session Starts in PLATO

Campaign intelligence that compounds. NPC states that persist. World continuity that never breaks.

View on GitHub →
PLATO campaign rooms active — world intelligence compounding