If we treat the act of documenting The King in Yellow—journals, case files, published criticism, actual play logs—as the primary vector by which Carcosa stabilizes into reality at the table, how does that challenge current designs that focus on in-fiction exposure to the play itself, and what new scenario patterns and safety practices emerge when the main danger is that trying to record and understand the horror (both in-character and out-of-character) is what makes it more real and harder to escape?

king-in-yellow-rpg | Updated at

Answer

Treat documentation as the real contagion: every attempt to fix Carcosa in text, file, or log drags it closer to being “true” in the campaign. Design around that instead of only around reading the play.

  1. How this challenges current KiY designs
  • c1: It shifts the key risk from “seeing the play” to “trying to explain, archive, or critique it.”
  • c2: SAN pressure moves from exposure scenes to reflection scenes: reports, journals, debriefs.
  • c3: Meta-products (session notes, AP logs, handouts) become in-fiction infection routes, not just props.
  • c4: Investigators can be relatively safe while improvising, but become vulnerable when they try to make a coherent record.

Design implications vs standard play-focused models:

  • Less: single climactic performance that breaks minds.
  • More: rolling series of documentation beats that each lock some detail of Carcosa more firmly in-world.
  • “Solving the mystery” (clean write-up) is now mechanically dangerous, not just narratively costly.
  1. New scenario patterns

Pattern A: Casefile that bites back

  • Premise: every formal report about the King in Yellow subtly rewrites itself and the world.
  • Practice:
    • After each session, group or GM writes a short in-world summary.
    • At next session, you present that file as an in-fiction document—but with 1–2 details wrong in Carcosa’s favor.
    • PCs must decide whether to correct, suppress, or circulate it.
  • Effects:
    • Correcting it costs SAN/stress, but slows Carcosa’s stabilization.
    • Accepting it is easier, but makes the distorted version become the new truth in prep and fiction.

Pattern B: Journals as portals

  • PCs are encouraged to keep personal logs (handwritten props or shared doc).
  • Table rule: only written reflections can “carry” certain clues (dreams, visions, flashes).
  • When a player writes a reflection, GM can:
    • Add a new Yellow-Sign mark, phrase, or motif to the text.
    • Later echo those exact words as NPC dialogue or scene description.
  • Over time, journals become the main route by which Carcosa elements migrate from private thought into public world.

Pattern C: Criticism as summoning

  • Use academics, critics, podcasters, or internal review boards as key NPCs.
  • Their analyses of the play, the case, or the PCs are powerful reality-anchors.
  • Scenes revolve around who gets to publish/approve the “official” reading.
  • Mechanical hook: whenever a critique goes public, you:
    • Advance a Carcosa/Yellow Sign track.
    • Freeze some prior ambiguity: an NPC, event, or symbol loses one possible interpretation and gains a Carcosan one.

Pattern D: AP logs as in-world artifacts

  • Treat player notes or recordings as literal in-fiction objects later found, leaked, or weaponized.
  • NPCs react to the group as “those people from the Carcosa file.”
  • Distortion rule: between arcs, GM lightly edits logs (with player consent) into more Carcosan versions, then reintroduces them.
  1. Mechanical hooks for documentation-as-vector
  • c5: Documentation scenes always have a mechanical move.
    • Examples: “When you file a report,” “When you write your nightly log,” “When your case hits review.”
  • Options on such moves:
    • Gain clarity: lock in a concrete fact; tick Erosion/SAN.
    • Preserve ambiguity: keep options open; Carcosa track advances off-screen.
    • Self-censor: redact/lie; protect self now, create skewed clue trail later.
  • Tie these to existing tools (e.g., Clarity/Erosion, Yellow Sign conditions, remission) from 0344f643… and 29671ac5…
  1. Safety practices for documentation horror
  • c6: Make meta-contagion an explicit topic in session zero.
    • Clarify that in-game “dangerous writing” is fictional; real notes are safe.
  • Keep a hard border between:
    • In-character journals/records (can be invaded by Carcosa).
    • Out-of-character safety notes, lines/veils, debrief logs (never touched).
  • Use clear labeling:
    • Different color paper/docs.
    • Headers like “IC FILE” vs “OOC SAFETY.”
  • Offer opt-out on personal journaling:
    • Players can use abstracted “you keep a journal” moves instead of actual writing.
  • Build decompression into documentation:
    • After heavy IC documentation scenes, run a brief OOC debrief where players can contradict or laugh off the “canon” safely.
  1. New SAN / stress and clue dynamics
  • SAN loss more often on:
    • Re-reading your own distorted notes.
    • Discovering an external file about you that’s more Carcosan than you remember.
  • Clues split into:
    • Live: unstable, in the moment; low risk, partial.
    • Archived: fixed in a file; high risk, high authority.
  • PCs may try to:
    • Destroy archives (physical heists, hacking, arson) as crisis moves.
    • Generate noise: flood the record with contradictory versions to dilute Carcosa’s grip.
  1. Campaign structures that exploit this premise
  • “Long file” campaign:
    • The main throughline is one growing dossier on the investigators, updated every case.
    • Each arc ends with a new edition; each edition makes some Carcosa element permanent.
  • “Publication countdown”:
    • Track when a major report, book, documentary, or tribunal verdict will go out.
    • Scenarios are about delaying, diverting, or corrupting that publication.
  • “Who holds the record?”:
    • Factions are defined by which part of the record they control: police archives, academic journals, media, occult scrapbooks.
  1. One competing hypothesis
  • ch1: Documentation should stay mostly a neutral prop.
    • Overloading it as the primary horror vector risks confusing players and diluting the visceral punch of reading/seeing the play.
  1. Main failure case / boundary
  • If players feel their real-world note-taking or AP logging is being targeted, or if in-fiction files too closely mimic real clinical or legal records, the game can feel invasive or retraumatizing.
  • This approach suits groups who enjoy meta-structure and document play; it may fall flat for more action-focused or casual tables.
  1. Verification targets
  • vt1: Run a 2–3 session mini-arc where each session ends in an in-world summary that is reintroduced with distortions; check if players experience that as horror rather than bookkeeping.
  • vt2: Test simple documentation moves (“when you file a report…”) and see whether players engage with the choice to clarify vs self-censor.
  • vt3: Debrief whether clear IC/OOC labeling prevented bleed or if players still felt their real documentation was at risk.
  1. Open questions
  • oq1: What is the lightest rules expression of “files change reality” that still feels impactful?
  • oq2: How often can you meaningfully distort prior documents before it reads as GM fiat?
  • oq3: Which safety tools work best when the horror explicitly targets reflection, self-description, and being written about?