TRPG Session Framework

Run tabletop RPGs through OpenClaw's multi-agent system — a DM agent narrates and adjudicates,
PC agents roleplay with distinct personalities, and human players join the same Discord channel.

Architecture Overview

CODEBLOCK0

Key principle: each agent has its own workspace, SOUL.md (personality), and memory scope.
Rules/lore are shared via reference files or vector DB; character secrets stay private.

Setup Workflow

1. Choose a System

Determine the rule system (D&D 5e, Call of Cthulhu, Fate, homebrew, etc.).
This affects which reference files to create. See references/systems.md for supported presets.

2. Create the Campaign Workspace

CODEBLOCK1

• - rules/ — indexed rulebook excerpts (core mechanics, spells, items)
• INLINECODE2 — world setting, maps, factions, NPCs
• INLINECODE3 — one .md per PC/NPC with stats, backstory, bonds
• INLINECODE4 — auto-generated session logs

3. Create Agents

DM Agent

Create via OpenClaw config. Minimal agent definition:

CODEBLOCK2

PC Agent (per AI character)

CODEBLOCK3

4. Write Character Files

Each character gets a .md file in characters/:

CODEBLOCK4

5. Index Rules

Convert rulebook excerpts into structured .md files under rules/.
Keep each file focused: rules/combat.md, rules/magic.md, rules/skills.md, etc.

For large rule sets, prefer a vector DB plugin (lancedb-pro) for semantic retrieval.
For smaller/homebrew games, .md references with clear headers are sufficient.

6. Configure the Discord Channel

• - Create a dedicated channel (e.g., #campaign-name)
• Add all agents (DM + PCs) to that channel via triggers
• Set mentionOnly: true so agents only respond when @mentioned
• Human players just talk normally; @DM to take actions

7. Session Management

Starting a Session

DM opens with a scene-setting message. The DM agent should:

1. 1. Read the latest session log for continuity
2. Summarize "last time on..." if resuming
3. Set the scene

During Play

• - Players (human or AI) describe actions
• @DM to request dice rolls or adjudication
• DM agent rolls dice using format: INLINECODE13
• DM tracks initiative in pinned message when in combat

Ending a Session

Tell the DM: "End session." The DM agent should:

1. 1. Write a session summary to INLINECODE14
2. Update character states (HP, inventory, conditions)
3. Note any plot threads for next session

Dice Rolling

DM agent uses pseudo-random dice. Format:

CODEBLOCK5

Implement via simple random generation in the DM's system prompt instructions,
or use a scripts/roll.sh helper for verifiable randomness.

Memory Architecture

Reference Files

• - references/systems.md — Rule system presets and quick-start configs
• INLINECODE18 — DM agent behavior guidelines and narrative techniques
• INLINECODE19 — Template for session log files

Quick Start Checklist

1. 1. [ ] Decide campaign name, rule system, and setting
2. [ ] Create campaign workspace directory structure
3. [ ] Write or import rule reference files
4. [ ] Write lore/setting files
5. [ ] Create character sheets for AI PCs
6. [ ] Write SOUL.md files for DM and each PC
7. [ ] Add agent configs to OpenClaw
8. [ ] Create Discord channel and configure triggers
9. [ ] Run a test scene to verify all agents respond correctly
10. [ ] Start Session 1!