Build worlds, not spreadsheets.
ScryMaster Stories is a deterministic D&D 5e (2024 SRD) campaign engine and creator platform. You author branching adventures from a small, validated vocabulary — scenes, choices, skill checks, real combat, loot, endings — and players run them free, solo or at a table. The dice are real and seeded; the same choices on the same seed always play out the same way.
A portable, single-file reference — keep it beside your work or feed it to your own AI.
Start here
- 🤖 Build with an AI agent (MCP) →The numbered path: connect a token, ground on the vocabulary, then create → save → validate → simulate → publish, end-to-end.
- Build your first story →Scenes, choices, checks, a fight, and an ending.
- Scenes & the Scene Editor →A 2D builder: layers, real buttons, snap & groups, motion, clickable objects, conditional layers & variants, Test Interactions.
- Triggers & actions →The Event-Condition-Action rule system and the full vocabulary.
- Bindings & the data tree →Reactive prose: {{character.hp}}, {{event.lastDamage.type}}, and conditional text.
- Build with your AI →Use Claude, Gemini, or ChatGPT to draft a whole adventure — what an MCP is, in plain English.
- Publishing & saves →The store, the depth score, dry publish, in-run updates, and how versioned saves never break.
- API & MCP reference →Tokens, endpoints, the MCP connector setup, the authoring contract, and troubleshooting.
The two ways to build
Open the Story Studio and you get four workspaces over the same adventure: Beats (edit one node at a time), Graph (a flowchart you drag to connect), Cast & Content (your monsters, items, spells, and variables), and Listing (your store presence). The JSON tab is the raw escape hatch.
Prefer to build with your own AI? Point it at the live action vocabulary — the closed, validated list of everything the engine can do. Because it’s default-deny, a model literally can’t invent a verb the server would reject, so AI-authored adventures stay valid. (The full Model Context Protocol connector is live — draft, validate, simulate, and publish end-to-end — alongside the grounding endpoint and OpenAPI spec.)
The rules you don’t have to write
The engine already enforces 5e (2024 SRD): to-hit vs AC, saving throws, advantage/disadvantage, conditions, concentration, death saves, initiative, resistances. You author which encounter happens and what a success or failure means — the engine handles how the dice resolve. Every check returns one of five outcome bands (critical fail · fail · success · strong success · critical success), and you write distinct prose and consequences per band.