Files

T

timevans666 0e8c13567a Add Blade Runner RPG system to scenario-library with Directive 19

New system folder: scenario-library/blade-runner-rpg/

Scenario: Directive 19 — LA 2037, six Blade Runners, 3.5hr
- Pure-investigation Act One (no combat)
- Action Act Two (Halden, Wren passes through, Sera ambush, salt flats)
- Tower showdown Act Three with structural Wren escape on the terrace
- 8 NPCs with stat blocks: Greer, Lin Ai, Marisol Yu, Halden, Wren, Sera,
  Hara, Cortez
- 6 pre-gens with personal hooks: Iris/Marc/Saoirse/Dmitri/Talia/Cole
  (3 human, 2 Nexus-9 replicant, 1 ambiguous senior)
- Full clue trail (8 essential + 3 optional + 1 special + 6 fallbacks)
- 6 handouts written: crime scene report, Lin Ai's list of nine,
  Voss bank statement, salt-flats ledger, Wren's note, the broadcast
- The Tangent: Marc's stolen memory of Hashem Lin (Saoirse's father),
  Halden surviving for campaign follow-up
- Full GM Notes covering tone, restraint on Halden, the terrace scene

GM HTML app: scenario-library/blade-runner-rpg/apps/directive-19/index.html
- Single-file, offline, tablet-friendly (2062 lines)
- Dark blue-black + amber/cyan/magenta palette
- Sidebar nav: Home / Acts / NPCs / Clues / Handouts / Players / Reference
- Timer with hard-checkpoint alerts at 0:15, 1:00, 1:15, 1:40, 2:00,
  2:20, 2:45, 3:15, 3:30
- Clue tracker (pending/found/missed cycle) with progress bar
- Handout modal with 5 paper styles (terminal/aged/handwritten/bank/broadcast)
- NPC cards with REVEAL GM NOTES classified-eyes-only sections
- PC cards with replicant/human visual distinction
- BR RPG reference: core mechanic, skill mapping, stress dice triggers,
  V-K use, combat quick ref, Promotion vs Humanity table
- localStorage persistence across sessions (clues, classified, timer)

Updated top-level README and scenario-library README to include the
new system folder.

2026-05-21 22:49:27 +00:00

2.1 KiB

Raw Blame History

Scenario Library

A personal archive of RPG scenarios written and run by timevans666 across all games and conventions over time.

This is separate from specific convention events. It exists so there is a permanent, searchable record of every scenario — what it was, when it was run, what worked, and what can be revisited or adapted.

Organisation

Scenarios are filed by game system. Each system folder contains individual scenario files, plus a system-level reference sheet.

scenario-library/
├── call-of-cthulhu/       # CoC 7e scenarios (any era)
├── brp/                   # Generic BRP scenarios
├── ringworld/             # Ringworld RPG scenarios
├── stormbringer/          # Stormbringer / Elric scenarios
├── blade-runner-rpg/      # Blade Runner RPG (Free League) — LA 2037 default
└── other-games/           # Any other system

Scenario Index

Title	System	Era / Setting	First Run	Status
Power Failure	SLA Industries	Mort, Downtown District 2	not yet run	ready
Directive 19	Blade Runner RPG	Los Angeles, 2037	not yet run	ready

Scenario Status Key

Status	Meaning
`draft`	Early development, not yet run
`ready`	Fully written, ready to run
`run`	Has been run at least once
`retired`	Not intended to run again
`adaptable`	Can be reused / reskinned for other events

File Structure Per Scenario

Each scenario has:

[system]-[title].md — main scenario file (players may see premise/structure)
[system]-[title]-gm.md — GM companion (NPC secrets, encounter notes, handout text)
art/[system]-[title]/ — maps and artwork (SVG floor plans, handouts)

Adding a New Scenario

Choose the correct system folder
Create files using the naming convention above
Use SCENARIO-LIBRARY-TEMPLATE.md as starting point for the main file
Add a row to the index table above
Update the system folder README
Push to GitHub

2.1 KiB Raw Blame History