Files
ChaosiumCon26/scenario-library
timevans666 27c0ace199 Fix HP/SAN track label bleed — BRP v4 and Stormbringer v3
Same root cause as LTCI/NAT: box top was rendering above label baseline.

BRP v4 (build_brp_characters_v4.py):
  BOX=20 → BOX=14, GAP=4 → GAP=3
  y_start: top-20 → top-29  (bleed was 13pt — worst of all scripts)
  height:  20+rows*(B+G) → 29+rows*(B+G)
  Number font: 9pt → 8pt, vertical centre adjusted

Stormbringer v3 (build_character_pdf_v3.py):
  BOX kept at 15, y_start: top-18 → top-29  (bleed was 9pt)
  height: 18+rows*(B+G) → 29+rows*(B+G)
  Portrait paths updated: /mnt/user-data/uploads → repo art directory
  IMG_BASE cleared (paths now fully absolute)

Ringworld (apps/ringworld-character-sheets/build.py):
  CLEAN — uses fixed mm-sized anatomy diagram boxes, not flowable tracks.
  Labels sit inside each box at fixed mm offsets. No bleed risk.

All PDFs rebuild successfully at correct page counts:
  BRP Day One: 14 pages, Night Crawler: 13 pages, Stormbringer: 13 pages
2026-05-19 10:24:10 +00:00
..

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

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