- sla-power-failure.md: full scenario file (premise, BPN brief, 6-scene structure, resolution options, clue table, NPC index, GM notes, adaptations) - sla-power-failure-gm.md: GM companion with full NPC secrets, encounter pacing, handout text, entity guidance, and ending philosophy - 3x SVG floor plans: ground level exterior, sub-level 1 (control/dormitories), sub-levels 2-3 (research wing + generator hall + rupture chamber) - Updated scenario-library/README.md with scenario index - Updated other-games/README.md with SLA Industries entry System: SLA Industries 1st edition. No game stats — narrative content only.
1.9 KiB
1.9 KiB
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
└── 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 |
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