Visibility & reveal
Timeline events have two independent controls for who sees what:
- Visibility controls whether someone can see the event at all.
- Reveal status controls how a visible event appears — full, redacted, foreshadowed, or hidden.
Use them together to encode “this prophecy exists in the world but the players haven’t found it yet” or “this NPC’s secret is locked behind GM-only” or “this event was revealed in Session 4”.
Visibility levels
Section titled “Visibility levels”| Level | Who can see it |
|---|---|
| GM only | Only the world owner and editors. It’s hidden from everyone else, and your GM notes stay attached. |
| World (default) | Everyone with access to the world — owner, editors, and viewers. GM notes are stripped for viewers. |
| Specific players | The owner, editors, and the individual players you list. Useful for per-player secrets in a shared world. |
| Public | Anyone, including signed-out visitors — but only if the world itself is public. Even then, each event reaches visitors only when you mark it Public; nothing is exposed by default. |
| Unlisted | World members can see it; signed-out visitors reach it only through a direct link or share. |
Visibility is a genuine access boundary, not just styling. A GM only event is truly hidden — a player with access to the world still won’t receive it.
Reveal statuses
Section titled “Reveal statuses”| Status | What players see |
|---|---|
| Revealed (default) | The full event. |
| Partially revealed | The Player summary replaces the full summary and body. Use it when players know some but not all. |
| Foreshadowed | A ghost-outlined placeholder (“Something happened here…”). For events you’ve planted in early sessions but haven’t surfaced yet. |
| Hidden | Doesn’t appear to players at all, even when visibility would allow it. Rare — usually you’d just set the event to GM only instead. |
How they combine
Section titled “How they combine”Most events are World + Revealed. Boring, correct.
Useful combinations:
- World + Foreshadowed — players can see the event, but its content is replaced by a placeholder. Switch it to Revealed when they learn what happened.
- GM only + Foreshadowed — even you see it as foreshadowed. Useful for “I haven’t decided what this event actually is yet”.
- World + Partially revealed with a Player summary filled in — players see the redacted version; you see everything.
- Public + Revealed with a Public summary filled in — readers of a public world see your hand-curated public summary instead of the full write-up.
The Reveal-in-session button
Section titled “The Reveal-in-session button”The Inspector has a one-click Reveal in session… button that:
- Sets the reveal status to Revealed.
- Records which session you pick from the dropdown as where it was discovered.
- Marks the moment it was revealed.
After Reveal, the event appears in the Chronicle’s session group for that session — a “Previously on…” recap is built automatically.
See The reveal workflow for the end-to-end flow.
GM notes stay private
Section titled “GM notes stay private”The GM notes on an event are held back from players at every point they’d otherwise be shown — on the event, in player-safe exports, and on any public share. You can write freely in GM notes knowing they never reach anyone but you and your editors.
Related
Section titled “Related”- Event fields
- The reveal workflow
- The Chronicle tab — Player-safe toggle preview
- Markdown export — Full vs Player-safe download