Given the emerging ‘reality tracks’ and three-logic node designs, how could you specify a minimal, reusable node template (fields, examples, and GM prompts) that lets a busy Call of Cthulhu Keeper prep a full King in Yellow mystery in under two hours while still (a) supporting institutional/artistic/Carcosan resolutions, (b) updating the shared city sheet, and (c) keeping clue paths legible for players at the table?

king-in-yellow-rpg | Updated at

Answer

Minimal node template: 1 page per node, same fields every time, optimized for 3-logics + city sheet.

  1. Node fields (keeper-facing)
  1. Node header
  • Node ID / title
  • Function: intro / mid / climax / fallout
  • Location / institution tag
  • Reality focus tags: Inst / Art / Carcosa (circle main one)
  1. Situation hook (2–3 lines)
  • What is this place/event?
  • Why do PCs come here now?
  1. Core question (1 line)
  • "What are the PCs really trying to learn/decide here?"
  1. Evidence bundle (3–5 bullets)
  • Physical: things in scene
  • People: 1–3 key NPCs
  • Records / media: files, photos, scripts, etc. (Write only what’s needed to feel concrete.)
  1. Three resolutions (institutional / artistic / Carcosan) For each logic, keep three micro-fields:
  • Answer (1–2 sentences, plain)
  • How it looks (1–2 sensory beats)
  • Push (what this makes PCs do next)

Example structure for each logic:

  • INSTITUTIONAL
    • Answer: mundane explanation in terms of policy, crime, diagnosis.
    • How it looks: uniforms, forms, procedures, jargon.
    • Push: points to a person, office, or file.
  • ARTISTIC
    • Answer: motive framed as art, persona, scene, gossip.
    • How it looks: décor, audience, style, quotes.
    • Push: points to a show, gallery, patron, or scene.
  • CARCOSAN
    • Answer: layered reality, memory drift, Yellow Sign pattern.
    • How it looks: odd doubles, time slips, motifs, dreams.
    • Push: points to a symbol, dream-site, or distorted memory.
  1. Method cues (how players “choose” a logic)
  • 3 short cues, one per logic: “fires when PCs …”
    • Inst: ask for official records; threaten legal action; lean on rank.
    • Art: ask about meaning, style, relationships; attend rehearsals.
    • Carcosa: follow symbols/dreams; accept coincidences; read the play. (These are soft rules; keeper interprets.)
  1. City sheet hooks (1 line per logic) For each logic, pre-write a tiny update to reuse with the campaign state sheet from 57394cba-b594-4dcf-9e0e-ada79b564772:
  • Reality track bump: which track +1 (Inst / Art / Carcosa / Player-recorded).
  • Scar / label: 1 short note. Format:
  • Inst: "+1 Institutional; Clinic scar: ‘new intake form asks about KiY exposure.’"
  • Art: "+1 Artistic; Theatre scar: ‘Yellow Sign appears in set dressing.’"
  • Carcosa: "+1 Carcosa; Label added: ‘Axis: CAR-2’ used by security." (Keeper just copies to city sheet when that logic resolves the node.)
  1. Clue path notes (legibility)
  • Up to 3 bullets:
    • Entry: how PCs usually find this node.
    • Outgoing: which 1–2 nodes this one points to, regardless of logic.
    • Fail-soft: what partial info they get if they bungle approach. Use simple arrows: “From A → this → often leads to Node D or E.”
  1. Table prompts (GM)
  • 1 safety prompt:
    • “What content here touches madness/identity? How to frame with lines/veils?”
  • 1 player-facing prompt per logic to keep horror in view:
    • Inst: “Who seems smaller or more trapped after you see the file?”
    • Art: “What part of you wants to join this scene?”
    • Carcosa: “What detail convinces you reality just slipped?” (Keeper asks these as quick reflection beats or internal narration.)
  1. Tiny example node (sketch)

Node: The Closed Rehearsal

  • Function: mid
  • Location: fringe theatre (Art tag)
  • Situation: PCs get invited / sneak into a rehearsal of a strange new play.
  • Core question: “Why is this troupe so committed to staging this text?”
  • Evidence:
    • Script pages with odd yellow annotations.
    • Director, lead actor, nervous stagehand.
    • Locked filing cabinet with grant letters.

Institutional

  • Answer: The play is a front to launder arts funds; director is pressured by a security agency.
  • How it looks: grant codes, risk categories on letters, a plainclothes observer.
  • Push: follow the money (Node: Funding Office).
  • Method cue: logic fires if PCs talk to the observer, demand contracts, cite law.
  • City sheet: +1 Institutional; Arts Board scar: “secret ‘Y-3’ risk label for experimental work.”

Artistic

  • Answer: Director is obsessed; the play is their magnum opus; troupe is complicit out of ambition.
  • How it looks: intense rehearsals, dramaturgical jargon, gossip about critics.
  • Push: attend opening night / chase a rival troupe (Node: Premiere or Rival Company).
  • Method cue: fires if PCs watch the rehearsal, ask about meaning, mingle with actors.
  • City sheet: +1 Artistic; Theatre scar: “Yellow Sign motif in posters downtown.”

Carcosan

  • Answer: Rehearsal space is a thin place; cast burns lines into reality; some scenes are déjà vu from PC dreams.
  • How it looks: double-cast roles, moments where time jumps, glimpses of Carcosa skyline through flies.
  • Push: dream-journey / investigate prior productions (Node: Old Playbills, Dream Hotel).
  • Method cue: fires if PCs read from the script, follow odd symbols, or reference prior dreams.
  • City sheet: +1 Carcosa; Label: “CAR-Stage-1” created as backstage slang and clinic note.

Clue path

  • Entry: flyer found at earlier crime scene or invitation from NPC.
  • Outgoing: always mentions Funding Office (Inst), Premiere (Art), or Dream Hotel (Carcosa).
  • Fail-soft: even if they get thrown out, they still see one key prop or symbol → pointer to next node.
  1. Use in a 2-hour prep loop

Prep steps for a full mystery (4–6 nodes):

  1. List 4–6 situations (crime scene, clinic, theatre, archive, dream site, street rumor).
  2. For each, fill:
    • Hook, core question, evidence (10–15 minutes per node max).
  3. Then, per node, do ultra-short 3-logics:
    • 1–2 sentences answer per logic.
    • 1 line city-sheet hook per logic.
    • 1–2 method cues. (5–8 minutes per node.)
  4. Last, draw simple arrows for node connections and note at least 1 safe-ish clue route from start to end.

At table:

  • Use method cues to choose which logic fires first.
  • Mark chosen logic; apply its city-sheet update.
  • Keep clue arrows visible on a simple index card so players always see where they can go next.

This keeps prep bounded, supports all three resolutions, updates the city sheet via tiny pre-written hooks, and gives players clear paths without exposing the meta-structure.