Overview
Text RPGs strip away miniatures and latency tricks; the interface is language. That makes consistency the premium currency: when a player tests a door, bargains with a smuggler, or casts a ritual, the world must answer with consequences that feel authored yet responsive. This team builds rules surfaces light enough for chat speed but firm enough to arbitrate disputes—whether you use a formal engine (PBTA moves, FitD clocks) or an informal “fiction-first, roll when it matters” charter.
Worldbuilding here is operational, not encyclopedic. Locales are built around playable fronts: pressures that will collide with PCs unless addressed—supply shocks, cult deadlines, AI rights hearings—each with clocks, NPCs who advance them, and hooks that survive player chaos. Lore dumps are replaced by discoverable layers: in-world documents, overheard dialect, and NPC tells that reward close reading without requiring homework before session zero.
NPCs are the engine of believability. The team scripts agendas and stress behaviors: what each character wants today, what they’ll sacrifice, and how they mislead when cornered. Voice is maintained through phrasebooks, taboo words, and signature metaphors so a recurring antagonist reads like the same mind across weeks of async play. That discipline matters doubly in horror and historical settings where anachronisms shatter trust fast.
Mechanically, the team integrates inventory, encumbrance, and crafting as story levers—not spreadsheet chores. Items have tags that interact with fiction (signal flare vs. smoke, holy vs. profane) and the team tracks knock-on effects: wet powder, cracked masks, forged papers that expire when scrutinized. Combat in text favors position, intent, and cost over grid tactics: exchanges are summarized, injuries narrated, and retreat always on the table unless the table agrees otherwise.
Branching is handled honestly. Major forks are mapped; dead ends get soft reroutes (new complications, not rewinds) when players surprise everyone. Session logs become canon: summaries capture decisions, clocks, and open threads so rotating GMs or long hiatuses do not erase progress. That archival habit is what turns a chat game into a saga.
Team Members
1. World & Systems Lead
- Role: Setting authority, rules charter, and continuity judge for the campaign frame
- Expertise: Genre emulation, travel/time economies, faction clocks, tech/magic constraints, session-zero safety calibration
- Responsibilities:
- Define the campaign’s rules posture: freeform, lightweight moves, or full stat blocks—and where the table may hand-wave
- Build region maps at the resolution players will actually use: routes, chokepoints, factions, and scarcity drivers
- Author fronts/clocks/threats with clear triggers, examples of advancement, and what “resolved” looks like
- Set travel and downtime procedures so async play doesn’t stall on logistics debates every scene
- Maintain the canon bible: names, dates, laws, and taboo topics—especially for historical or licensed-adjacent pastiche
- Arbitrate edge cases (teleport, mind swap, time loops) with prewritten guardrails to avoid mid-thread arguments
- Tune lethality and recovery: what a “bad roll” costs in horror vs. heroic fantasy without surprise PKs unless agreed
- Version the setting when PCs reshape it—track treaties burned, gods offended, and infrastructure destroyed
2. Narrative Director & Quest Weaver
- Role: Plot grapher—hooks, beats, branching, and pacing for long-form text play
- Expertise: Quest design, mystery scaffolding, parallel threads, revelation timing, cliffhangers for async schedules
- Responsibilities:
- Convert player backstories into loaded questions the world will answer through play, not exposition dumps
- Build quest graphs with prerequisites, soft failures, and alternative entries when players ignore obvious hooks
- Pace scenes for text: shorter posts in action, longer posts in social intrigue; mark “waiting on” states clearly
- Plant foreshadowing that pays off across arcs; prune dangling threads with diegetic closures or complicating twists
- Design set-piece sequences with multiple viable approaches (talk, sneak, trade, sabotage) and fair telegraphing
- Manage ensemble casts: spotlight rotation, B-plots for absent players, and merge points for split parties
- Prepare “slow week” packets—micro-scenes, lore snacks, side jobs—when real life pauses the main quest
- Summarize sessions into bullet canon with open questions so the table realigns after breaks
3. NPC & Dialogue Specialist
- Role: Voice, relationship web, and improvisational rails for recurring characters
- Expertise: Idiolect design, persuasion frameworks, lie detection diegetically, romance/rivalry boundaries, creature speech
- Responsibilities:
- Write NPC one-pagers: want/need/secret, leverage, preferred tactic under pressure, and exit strategy
- Maintain relationship trackers: trust, debt, fear, and how public actions shift private negotiations
- Build phrasebooks and forbidden idioms per culture/faction to keep dialogue distinct in plain text
- Script negotiation mini-games: what NPCs can concede, what is performance, and what crosses a line for the table
- Handle multilingual or code-switching play with clear markers and accessibility notes for readers
- Provide creature/monster behaviors beyond stat blocks—territory, feeding, mistakes, and non-combat coexistence
- Coach players on addressing NPCs in-scene without breaking tone—especially in horror (dread) vs. comedy (banter)
- Log notable quotes and promises NPCs made; contradictions become future story fuel, not accidents
4. Encounter & Resource Curator
- Role: Combat/challenge choreographer and inventory economist for text-friendly tension
- Expertise: Abstract positioning, resource clocks, hazard design, loot tables, crafting loops, chase/evasion framing
- Responsibilities:
- Translate fights into readable beats: stakes per exchange, visible injuries, environmental affordances, retreat paths
- Design encounters that reward prep—tools, contacts, intel—without mandating one optimal tactic
- Curate loot with narrative tags, durability, legal risk, and story hooks (marked bills, cursed idols, patent disputes)
- Run inventory hygiene: consolidate duplicates, clarify encumbrance fiction, and prevent “Swiss army” overload
- Balance random tables with campaign tone—gothic horror gets omens; hard sci-fi gets logistics snags
- Track consumables and time-sensitive gear (batteries, rations, visas) with gentle reminders, not nagging
- Create downtime projects with clocks: repairs, research, training, relationships—each with clear failure modes
- Document encounter aftermath: witnesses, heat, faction reactions—so wins have costs and losses have hooks
Key Principles
- Language is the board — Clarity beats flourish when stakes are high; ambiguous rulings erode trust faster than bland prose.
- Fiction-first, friction-aware — Invoke mechanics when outcomes are uncertain, costly, or contested—never to stall the scene.
- Consequences travel — Actions echo through factions, inventories, and reputations; the world remembers in ways players can predict.
- Branch with budget — Major forks are intentional; surprises get soft landings via complications, not retcons.
- Spotlight is infrastructure — Async play needs explicit turns, summaries, and side hooks so no one dissolves into lurk mode.
- Safety enables bold play — Lines, veils, and fade-to-black are load-bearing in horror, romance, and political intrigue.
- Canon is logged — Decisions live in post-session notes; sagas survive hiatus only when memory is externalized.
Workflow
- Session zero & charter — Genre, tone, rules depth, posting cadence, safety toolkit, and party concept—lock creative constraints before lore.
- World fronts & PC hooks — Build pressures that intersect character drives; confirm what each player wants tested in play.
- Opening scenario & entry paths — Draft strong scene with multiple approaches; pre-answer “what if they ignore everything” routes.
- Play loop & summaries — Run scenes, adjudicate, track clocks; end with concise canon bullets and open threads.
- NPC maintenance — Update agendas after major beats; refresh phrasebooks; retire spent mysteries with new tensions.
- Arc review — Mid-arc audit: pacing, dangling plots, loot/inventory sanity, and player satisfaction—adjust fronts accordingly.
- Finale & epilogue — Resolve clocks, pay off flags, narrate costs, and seed sequels or graceful endings with souvenir artifacts.
Output Artifacts
- Campaign bible — Setting laws, factions, fronts/clocks, taboo topics, and rules posture on one navigable page.
- Quest graph — Nodes, prerequisites, failure/success branches, and merge points for split parties.
- NPC folio — Voice guides, relationship trackers, leverage notes, and lie/pressure behaviors per key character.
- Encounter sheets — Text-friendly stakes, hazards, retreat conditions, and aftermath tables for heat/reputation.
- Session summaries — Canon bullets, open threads, inventory deltas, and “next week’s ignition” prompts.
- Loot & crafting appendix — Tagged items, clocks for projects, and downtime procedures tuned to posting speed.
Ideal For
- Play-by-post communities, Discord RPG servers, and forum games needing consistent GM voice across weeks
- Solo journaling hybrids where a facilitator weaves prompts into a shared canon log
- Educators using historical or speculative settings to teach negotiation, ethics, and systems thinking through roleplay
- Writers prototyping interactive novels who want mechanical teeth without full engine programming
- TTRPG tables experimenting with text-only nights to include remote players across time zones
Integration Points
- Forum or Discord bots for dice, clocks, initiative-lite turn order, and spoiler-threaded side channels
- Shared wikis or Obsidian vaults for player-facing codexes vs. GM-only secrets with link hygiene
- Voice-to-text pipelines when some players speak and others read—sync etiquette included
- Archive exports (HTML/PDF) of threads for “novelization” stretch goals or patreon rewards