Given the emerging tools for dossiers, city state sheets, and player/table reality splits, how could you design a player-facing Yellow Sign track that advances only when players voluntarily treat a symbol, label, or dream as meaningful (rather than when they merely see it), and how would that track concretely reshape clue availability, institutional reactions, and SAN pressure without ever requiring an explicit supernatural reveal?

king-in-yellow-rpg | Updated at

Answer

Design a simple, visible meter that only moves when players invest in the Yellow Sign as meaningful, and tie each step to small but concrete shifts in clues, institutions, and SAN.

  1. Core structure: Yellow Sign Attention Track
  • 0–5 scale on the table, labeled “Yellow Attention” (or similar fiction-first name).
  • Track rule (state clearly to players):
    • The meter increases only when a player chooses to treat a Yellow Sign–adjacent thing as important.
    • Mere exposure never moves it.

Example triggers (pick 3–5):

  • A PC drops a mundane lead to pursue a symbol/label/dream.
  • A PC writes about the symbol in a report, journal, or dossier note.
  • A PC pushes a roll or spends a resource to interpret anything Carcosa/Yellow–coded.
  • A PC uses the symbol/label as part of a theory, argument, or interrogation.
  • PCs adopt Yellow slang (“Carcosa case,” “Y-profile”) in front of NPCs.

When a trigger happens, you say: “That’s Yellow-facing; +1 Attention.” Players see the meter move.

  1. Concrete effects by band (no overt magic) Keep it light but felt. Effects are about how the city treats them and which clues appear.

Band 0–1: Background oddity

  • Clues: Yellow items are rare, marginal.
    • A few case files, graffiti, doodles, misprinted logos.
  • Institutions: No coordinated response.
    • One clerk or junior doctor knows the code but shrugs.
  • SAN: No direct pressure from the track.
    • Only normal CoC-style stress.

Band 2–3: Marked as “interested”

  • Clues:
    • More Yellow-coded paperwork starts referencing the PCs (risk flags, “Axis: CAR-2”, “Y-1 subject”).
    • Some leads only unlock if PCs show they recognize the code.
  • Institutions:
    • Security/clinical staff quietly tag the PCs as relevant to “Yellow-class” cases.
    • They get offered restricted briefings if they acknowledge the label (“You’ve seen that mark before, haven’t you?”).
  • SAN:
    • When a PC voluntarily leans into Yellow interpretation (e.g., insists “this must be Carcosa-related”), call for a small SAN test or equivalent.
    • On failure, consequence is obsession, not shock: advantage to notice Yellow patterns, penalty to ignore mundane explanations.

Band 4–5: Known carriers / specialists

  • Clues:
    • Some evidence is routed directly to the PCs (“per Yellow unit review”).
    • Non-Yellow leads dry up; most hooks now arrive pre-coded with Yellow labels.
    • They start receiving conflicting versions of the same document from different institutions, all tagged with Yellow codes.
  • Institutions:
    • One major institution treats them as Yellow experts; another treats them as contaminated.
    • They may be barred from certain cases (“conflict of interest”) and fast-tracked into others.
    • Background checks, surprise evaluations, and “consultation requests” become routine scenes.
  • SAN:
    • Normal horror still applies, but add:
      • When PCs suppress or redact Yellow content they personally introduced: small SAN test for denial/guilt.
      • When they double down and cite Yellow codes as real: small SAN test for self-alienation (they hear how they sound).
  1. How it reshapes investigation play

3.1 Clue availability

  • Gate some clues behind using Yellow meaning:
    • Example: To access a sealed archive, a PC must phrase a request using the internal Yellow code they spotted earlier. Doing so adds +1 to the track and unlocks files.
  • Offer safer, slower mundane paths:
    • Example: They can pursue a Yellow-coded arson case as a normal insurance fraud; no track increase, more time and friction.
  • Occasionally reward ignoring Yellow:
    • A mundane witness only talks if they don’t mention the symbol; if they do, she shuts down and calls someone.

3.2 Institutional reactions

  • Tie one or two institutions directly to band thresholds:
    • At 2+: hospital/security starts a quiet dossier linking the PCs and Yellow tags.
    • At 3+: they are invited to a closed-door briefing about “Carcosa profiles” framed as purely clinical/operational.
    • At 4+: a cross-agency panel debates whether they are assets or risks; this shows in small ways (extra forms, escorts, polite stonewalling).
  • All of this can stay mundane:
    • Nobody asserts magic; everyone talks in risk management, diagnosis, art-crit jargon.
    • The horror comes from being classified and watched because you chose to care about a sigil.

3.3 SAN pressure without supernatural proof

  • SAN (or stability) tests always tie to voluntary cognitive moves:
    • Reinterpreting a neutral memory/document as Yellow-coded.
    • Publicly staking reputation on a Yellow explanation.
    • Discovering that an institution has built procedures around something you treated as a tiny pattern.
  • Outcomes are psychological, not cosmic:
    • Obsessions, doubts about one’s own judgment, estrangement from colleagues, erosion of identity (“Am I an investigator or a case?”).
  1. Practical procedure at the table

Step 1 – Session 0

  • Explain:
    • “This track only rises when you decide that Yellow things matter. You control it.”
    • “It changes how institutions treat you, what clues surface, and how your SAN is tested. It never proves anything supernatural.”
  • Get consent: confirm everyone is okay with institutional surveillance/classification as horror; set lines/veils.

Step 2 – Make triggers explicit

  • Put 3–5 example triggers on a visible card.
  • When a player hits one, ask for confirmation:
    • “Are you treating this as Yellow-significant? If yes, I’ll tick the track.”
    • This keeps agency and avoids surprise.

Step 3 – Prep light band effects

  • For your current arc, jot 2–3 concrete effects per band:
    • 1 new type of clue.
    • 1 institutional behavior shift.
    • 1 SAN test trigger type.
  • Use them as soft guidelines, not a script.

Step 4 – Never confirm the metaphysics

  • NPCs disagree:
    • One calls Yellow codes “legacy nonsense,” another treats them as cutting-edge profiling.
    • An artist insists it’s just a brand; an investigator swears cases cluster around it.
  • All consequences can be read two ways:
    • Either the symbol is a self-fulfilling label attracting obsession, or it marks a real hidden pattern.
    • The track measures commitment to that pattern, not occult radiation.
  1. Safety hooks
  • Keep the track player-facing: no secret jumps.
  • Explicitly limit what can be pathologized:
    • Use fictional codes, not real diagnoses.
    • Avoid mirroring real-world marginalized labels.
  • Offer de-escalation moves:
    • PCs can choose to “de-prioritize Yellow” for a case: for one session, no track advances; in exchange, Yellow-coded shortcuts and clues stay closed.
    • Use this as an opt-out valve if someone feels pressured by the surveillance theme.

This makes the Yellow Sign track a voluntary, visible dial: the more players treat it as meaningful, the more the world routes meaning, files, and pressure through it—while the question of whether it’s truly supernatural stays unresolved.