Your agent is the game master

A coding agent in a terminal prints its tool calls, permission prompts and JSON between the lines of your story. The Book takes the story out of the terminal. The agent runs headless behind it, its narration streams in as it writes, and what you read is prose.

• Your hero's skills speak up. Entering a scene rolls each one quietly, and only a success reaches the margin: SPOT HIDDEN [5] SUCCESS. You never learn what you missed.
• A torch burns down with game time, and dark places are dark.
• The codex keeps everyone you've met, with a face each, and blanks out what they want, fear and hide until you find out.
• Omens from hidden countdowns reach you as omens, never as numbers.
• When your hero dies, the Book closes on a gravestone with your last words, and Home keeps them in the Hall of the Fallen.

None of these is a mockup. They're screens from The Red Tusk Hall, the adventure that ships with oma-solorpg: the plugin's own QML, rendered offscreen against real engine state by the test harness in tests/qml. Click one to look closer.

On Omarchy the big moments leave the Book. Hyprland's window borders, a screen shader and hyprsunset land with the Book's dice to the millisecond, and each can be switched off under Desktop effects on the Table. Here CSS stands in for them, and the sounds are synthesised on the spot, the way the plugin makes its own with Python's standard library.

1 2 3 4Day 1, 00:15◆

solo deskclick one

DragonThe borders flash gold and gold light floods the screen. A chime. DemonThe borders turn red, the colour drains and the picture tears at its edges. A growl. A blowThe screen jolts. DyingThe borders stay dark red and a red rim closes in, further with every failed death roll. A heartbeat. DeathThe screen goes grey and cold for a while, and a bell tolls. OmenThe screen ripples and the omen arrives as a notification. CandlelightThe screen warms while the Book is open. A fight startsA war drum. solo desk restorePuts back exactly what it changed.

Questions nobody rolls for go down a fixed ladder: the adventure's text first, then a skill check, then the oracle, which takes its odds from what the campaign tracks. The agent never picks the answer. Every change is an event in events.jsonl, and the state is rebuilt from it at any time.

how a turn works

1. youwrite to the GM at the bottom of the Book
2. agentpicks one intent from what solo scene offers
3. enginesolo check sneaking: the dice and the rules, in code
4. agentreads the scene and proposes the consequence
5. enginesolo commit '{"facts": …}': validated, logged, clocks advance
6. agentnarrates what was committed

Fights, dying and advancement are rules the engine runs: initiative cards, weapon damage through armor, death rolls at zero HP, and skills marked by Dragons and Demons and rolled up at the end of a session.

solo check sneaking

{
  "summary": "Sneaking: 16 vs 5, failure",
  "push": {
    "cost": "take a condition",
    "choose_from": ["exhausted", "sickly", "dazed", "angry", "scared", "disheartened"]
  },
  …
}

solo commit '{"note": "the horn sounds", "facts": {"hall.alarm": true}}'

{
  "summary": "the horn sounds [for the GM: facts hall.alarm = true]",
  "then": [
    "The ritual below 1/6",
    "Omens of the ritual (3): A low chant rises from somewhere under your feet."
  ],
  …
}

solo ask "Is the gate barred from the inside?"

{ "summary": "asked \"Is the gate barred from the inside?\" (fortune, yes/no, rolled 2): No", … }

Real output from the engine, trimmed where it says …

playing alone, by the book

With Dragonbane's own solo rules built into your pack (they're in Alone in Deepfall Breach, in the core set), the engine runs the game the way the book means it to be played alone.

• Your hero starts with one more heroic ability. Army of One deals you two initiative cards in a fight; Sole Survivor lets you push a roll for willpower instead of a condition.
• Questions a GM would answer go to the book's fortune chart: yes or no, how many, how big, how strong, how fine, or how someone reacts. Open questions get words to read.
• Threats loom on a counter that climbs with every delay, and come for you when it fills.
• You can search an area and scavenge a nest. Foes the adventure never wrote fight as minions or bosses.
• At a rest you tend your own wounds. At zero HP you can rally yourself, or try to save your own life.

Without a solo rules book the oracle is the engine's own, a likelihood oracle that brings surprises: random events tied to the people and threads in play, and scenes that turn out altered, as often as a chaos factor says.

oma-solorpg ships Dragonbane's words and none of its rules. make dragonbane reads the books it knows from your PDFs, by their bookmarks and layout, with no agent. For a book it doesn't know, your agent reads it a chapter at a time and writes a pack the engine can run, every number citing the page it came from. The book never goes through a chat upload, however big it is, and nothing built from it lands in the repository.

what make rules does

1. solo extract turns the PDF into pages and chapters of text, with the running heads taken out and the printed page numbers read off the footers.
2. Any page that holds a roll table is also saved as a picture, because text extraction scrambles columns and the agent can look at the page instead. A page with no text on it is flagged as a scan.
3. solo inventory starts a checklist: an item for every section and table, every page cited.
4. Your agent works through it with the solo-rules-import skill: attributes, creation tables, weapons and armor, fear and mishap tables, a bestiary, the price lists, a rules page per topic.
5. solo audit fails on anything unaccounted for, either way, and on any table result, die, monster stat or price that isn't on the page it cites.

make rules BOOK=… SOLO_BOOK=… runs the mechanical steps and then opens your agent with the skill and a prompt. The pack lands in ~/Games/solo/systems, laid over the names the repository ships.

solo extract "Dragon Tests.pdf"

wrote ~/Games/solo/sources/dragon-tests

6 pages, 756 characters (about 189 tokens), 4 chapters from the outline, 1 table

The PDF has no page labels: the printed page numbers were read off the footers (manifest.json, labels).

solo inventory ~/Games/solo/systems/dragon-tests --extract ~/Games/solo/sources/dragon-tests

wrote 5 files in ~/Games/solo/systems/dragon-tests: inventory.toml, inventory/01-front.toml, inventory/02-equipment.toml, inventory/03-travel.toml, inventory/04-monsters.toml

Every page with text is cited by a todo item. Refine each chapter file, map every item, and run solo audit until it's clean.

solo import table ~/Games/solo/sources/dragon-tests/pages/0005.txt --out ~/Games/solo/systems/dragon-tests/tables/weather.toml

wrote ~/Games/solo/systems/dragon-tests/tables/weather.toml

# the agent maps the rest, a chapter at a time

solo audit --system dragon-tests

# Audit of dragon-tests against Dragon Tests

5 items: 4 mapped, 1 skipped.
The pack holds 9 things an item must claim.

Everything is accounted for.

## The book's pages
5 of 5 pages with text are cited (Dragon Tests.pdf, 6 pages).

## Mechanics only in rules pages (1)
The GM reads these; the engine doesn't run them.
- journeys: Journeys (p. 4)

Real output, on the six-page rulebook the test suite makes up for itself (tests/test_rules_import.py).

tables/p0005.pngcaptured by solo extract

name = "Weather"
formula = "1d6"
results = [
  { range = [1, 2], text = "Clear skies" },
  { range = [3, 4], text = "Rain, a bane on BUSHCRAFT" },
  { range = [5, 5], text = "Storm, no travel" },
  { range = [6, 6], text = "Fog, a bane on AWARENESS" },
]

The page as a picture for the agent to read, and the table solo import table made of it, dice worked out.

adventures, too

make adventure ID=my-adventure PDF=~/Books/dragonbane-adventures.pdf
make adventure ID=my-adventure FOUNDRY=~/Exports/my-adventure
make check-adventure ID=my-adventure

From a PDF, or from a Foundry VTT export (journals, actors and roll tables). The solo-import skill adds what the text only implies: factions, clocks, gates, branches, people with profiles and voices. It also says how to turn a published adventure's table rules into solo ones: a real-time limit becomes game time, pre-made replacement heroes wait for your death, a tournament's score is kept.

solo outline shows the whole adventure on one page for review (spoilers), and solo validate points out scenes nobody can reach. The adventure then shows up on the New adventure screen.

the Dragonbane quickstart's tournament adventure

The Sinking Tower

Every twenty years a drowned sorcerer's tower rises from the sea for two hours, a green light burning at its top. Seven floors of puzzles and monsters, and a tide that won't wait.

scenes

10

people & monsters

10

attack tables

6

rules pages

6

heroes

3

Play-tested with a real GM, scored 1 to 5 by a third agent on rules, adventure, state, secrecy, narration and agency. Archmaster Aodhan's full run went 33 turns across two dropped sessions with every clock, fact and condition intact: 5 5 5 5 4 4. With the solo rules, Ragna took two turns a round and killed the eel, the first run anyone lived through.

the solo campaign in the Dragonbane core set

Alone in Deepfall Breach

A wound in the world, struck by a demon lord's spear, plunges leagues into the earth. An old wolfkin demon hunter watches over it from a ruined chapel, and he has work for you: five missions into the Breach, one after another.

missions

5

waypoints

34

scenes

39

people & monsters

15

rules pages

4

In a real GM run the hero pocketed a smith's whetstone in Outskirt and told the tavern keeper about a sister lost in the Breach. Then the GM's session was dropped. The fresh one found it all again from the record, had the smith tell the store keeper while the hero was away, and, of its own accord, tied the lost sister to a ghost waiting in mission four.

The Sinking Tower and Alone in Deepfall Breach are Fria Ligan AB's. The author owns both books, and compiled these packs from them with the ingestion tools above; the screenshots are the engine playing those packs, rendered by the same harness as the rest of this page, with the GM's lines written for the occasion. The packs hold the books' text and tables, so they stay on the author's machine and are not in the repository. Build your own from the books you own.

A campaign can run for many sessions, and the GM may start any of them knowing nothing. The agent's session can be lost, compacted or replaced at any time, and the campaign holds the memory for it.

• What your hero does comes back. The GM writes down what will follow from a deed (the guard who took the bribe will brag, the cultist who fled will warn his master, the debt at the inn falls due in two days) and the engine tells it when the moment comes. You only see the world react.
• People remember what you did to them, and word spreads to their kin. Someone the GM made up keeps their name, face, voice and wants from one session to the next.
• A place you return to is the place you left: the forced gate still hangs open, and the GM is told how long you were away.
• Before it brings anything back, the GM searches everything ever said at the table (solo recall), so a name it gave you three sessions ago stays the same name.
• Close the Book whenever you like. It opens again exactly where you stopped, word for word.

make campaign ID=salt-and-ash TONE=grim MISSIONS=4 \
  PREMISE="a smuggler's coast where the dead keep the lighthouses"

solo new red-tusk --character ~/Games/solo/campaigns/sinking-tower-ragna