Adds 12 new prompts (BR19-EX-01 through BR19-EX-12) — each one the in-fiction case-file dressing for one of the existing blueprint maps. Format: tan-paper folder background with the blueprint reproduced at center, four annotated polaroid photographs paper-clipped at the corners (each with handwritten red-ink captions on masking-tape labels), black redaction blocks across portions of the margin text, a chain-of- custody box at the bottom with three signatures filled in, faint LAPD REP-DETECT shield watermark, CASE 037-2037-11473 DIR-019 EVIDENCE EXHIBIT stamp top right, handwritten exhibit-letter tag. Each prompt names four specific polaroids that ground the exhibit to the scenario: - EX-01 (Voss penthouse): mirror DIR-019, kitchen bootprint, Voss-in-bathtub, panic-room door - EX-02 (Morgue): Voss slab, Ostrow tattoo, paralytic ampoule, Ostrow effects bag with pocket watch - EX-03 (Lin Ai's noodle bar): surveillance still, seized notebook, Fairfax overpass exterior, Persian Quarter DIR-019 graffito - EX-04 (Volkov clinic): body on procedure table, the pen at reception, humming autoclave, the fake federal credential - EX-05 (Pham marina): body at kitchen table, handwritten confession, wet bootprint size 9, Wren's H02-B note - EX-06 (Saltgrove warehouse): memorial beam photographs, acid-burn floor, ledger page H02-A, approach road mile 22 - EX-07 (Parking structure): sound-grenade residue, Sera profile, 9mm wall damage, B-negative blood trace - EX-08 (Sandoval 88th): Cortez podium press photo, green-room badge, service-corridor pry damage, guest manifest page - EX-09 (Sandoval roof): relay terminal, broadcast-file audio fragment, ladder access pry marks, HVAC wiring tap - EX-10 (The terrace): wet stone handhold abrasion, surgical blade fragment, oilcloth fibre, BODY NOT RECOVERED notation - EX-11 (Salt flats regional): estate gate, warehouse 7 exterior, approach road mile 14 tracks, 2027 satellite overhead - EX-12 (Central LA overview): Bradbury at night, Sandoval entry, Volkov clinic street view, LAPD precinct fleet Shared evidence-exhibit style suffix at top of section keeps the twelve exhibits visually consistent. Section also includes notes on the Midjourney challenges (text rendering, redaction blocks, polaroid placement) and a usage guide: plain blueprint variants for quick scene navigation, exhibit variants when a PC explicitly pulls a file — e.g. Iris's [BR: Connect] roll to pull the Voss file should produce EXHIBIT A, not the plain map. File now 867 lines, 50 total prompts.
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.mdas starting point for the main file - Add a row to the index table above
- Update the system folder README
- Push to GitHub