Sessions and recaps

A session in PostRoll is the link between a real-world play-day and the in-world events that happened. Sessions are world-anchored (they belong to a specific world’s timeline), have separate player and GM recap fields, and serve as the anchor for the Reveal-in-session workflow.

Where sessions live

Sessions exist independent of the timeline workspace — they’re created and run from the Rooms system. What the timeline adds is a way to anchor a session to a world and use it as a timestamp / reveal anchor for events.

Two paths to a world-anchored session

1. Automatic — sessions whose room has an active scene that belongs to a world get anchored to that world for you. Most sessions you’ve already run probably qualify.
2. Manual — set the session’s world from the session detail page. Sessions still without a world are listed but don’t appear on any timeline.

The session list at /app/worlds/<your world>/sessions shows every session anchored to that world.

The session detail page

Each session has a detail page at /app/worlds/<your world>/sessions/<session-id>. From here:

• Edit session number — a per-world ordering number (1, 2, 3…). Drives Chronicle session-group sorting.
• Edit campaign day — the in-world day count, if your campaign uses one (campaign-day mode).
• Edit summary — a one-line description.
• Edit player recap — visible to players. Appears at the top of the session’s group on the Chronicle.
• Edit GM recap — editor-only. Hidden from player-safe views.
• List of tagged events — every event discovered in this session.

The recap workflow

1. Run your session.

2. After the session, open /app/worlds/<world>/sessions/<session-id> and write the Player recap — what your players experienced, in their voice, ready to send out. 100-300 words is a good target.

3. Optionally write a GM recap with the behind-the-scenes — what the players don’t know, NPC moves you teed up for next session, whatever.

4. Set the session number if it isn’t already (1 for first session, 2 for second, etc.).

5. Click Save recap.

The Chronicle tab now groups every event tagged to this session under a heading with both recaps. In Player-safe mode, only the Player recap shows; in Full view (and the GM-only Markdown export), both appear.

Reveal events in this session

The Inspector’s Reveal in session… button works hand-in-hand with the session — clicking it records the session it was discovered in as the one you pick, moving the event into the session’s group on the Chronicle. See The reveal workflow.

Connecting sessions to events

Beyond the explicit reveal button, the Chronicle automatically groups events whose position on the master timeline falls inside the session’s start-to-end window — so events that happened “during the session” show up alongside events that were “discovered in the session”, even if no one explicitly revealed them.

A session can also be linked from any event as a session link — useful for tagging “this combat happened in this session” without marking it as discovered there.

Tip

A session’s player recap is the most useful single field in the whole system. Write it in your players’ voice, with character names, in-world dates from the primary calendar, and references to prior sessions. The Markdown player-safe export collates them into a campaign log automatically — your players get a perpetual recap document for free.

Related

• The reveal workflow — Reveal-in-session button
• The Chronicle tab — where recaps appear
• Previously on… — the player-recap workflow end-to-end