Storyline Planning

The storyline module is an ST-only tool for coordinating storylines across the chronicle. It provides a shared workspace where STs can plan, track, and review storylines, solving the problem of STs working in silos without visibility into each other's work.

Access it from Admin > Storylines or go directly to the admin storylines page.

The Chronicle Ticker

The landing page is the Chronicle Ticker, a live feed of everything happening in the chronicle. It shows two kinds of entries:

• Freeform posts: quick notes from STs about scenes they ran, things that happened, or anything the other STs should know. Post from the text box at the top of the ticker, or use !log in IRC.
• Storyline events: automatic entries when storyline steps are completed, statuses change, or log entries are added. These link back to the storyline they came from.

The ticker is the daily pulse check. Open it after a session to see what other STs ran.

Posting from IRC

Use !log in any channel (admin only):

!log Ran the mine scouting scene, players found corporate equipment
!log Kalipeda debriefed with Luca at the monitoring station

The bot confirms with Logged: "your message". Entries appear immediately on the ticker.

Pipeline and Chapter Views

The nav bar at the top switches between three views:

• Feed: the ticker (default landing page)
• Pipeline: storylines grouped by status: Draft, Active, Complete
• Chapters: storylines grouped by chapter for pacing

The Pipeline view flags any active storyline with no links to other storylines. This is a signal that something may be running in isolation.

Creating a Storyline

Click + New Storyline from the nav bar. Fill in:

Status Workflow

Each storyline moves through four statuses:

Draft -> Active -> Complete

• Draft: being written, not ready for review
• Active: currently running in-game
• Complete: finished, kept for reference

Change status from the dropdown on the storyline view page.

Running Scenes

After running a scene, go to the storyline's view page and use the Add Log Entry form:

1. Write what happened in the text box
2. Optionally select a step to complete from the dropdown
3. Optionally tag an NPC who was involved
4. Click Add Entry

This does three things at once:

• Appends the log entry to the storyline body
• Marks the step as done (if selected)
• Posts to the chronicle ticker so other STs see it

You can also toggle steps and objectives directly by clicking their checkboxes on the view page. Each toggle posts to the ticker automatically.

Linking Storylines

Links connect storylines and explain why they're connected. Add them in the edit form:

old-wounds | Markus first appeared here; his agenda continues
the-long-hunt | consequence, Elder Yusra's position weakened

The note field preserves the reason for the connection, not just the fact of it. Links show up on both the view page and the chapter view.

NPC Notes

NPCs have optional private notes visible only on the storyline view page:

Markus | Feeding false info to PCs, will reveal location in Scene 3
Elder Yusra | Doesn't know about the betrayal yet

NPC names (without notes) appear as tags on the dashboard for cross-referencing. Click an NPC name to see all storylines involving that character.

Themes

Themes are freeform tags. Click a theme on any storyline to see all storylines sharing that theme. Useful for tracking recurring motifs across the chronicle.

Tips

• Post to the ticker after every scene. Even a one-line note helps other STs stay in sync.
• Link storylines early. The pipeline view flags active storylines with no links as a warning.
• Use steps for scenes, objectives for conditions. Steps are ordered (Scene 1, Scene 2). Objectives are unordered (players learn X, NPC reveals Y).
• Keep the body as a living document. The log section at the bottom of each storyline body is append-only. Use it for session-by-session notes.