hypercross
77ed233f8c
Serves as the reference implementation of the game package contract: rules, spark tables, character backgrounds, and an example command.
1.5 KiB
1.5 KiB
Generic d6 Oracle
System-agnostic solo play. No stats are required: the fiction and the d6 carry the game. Use this as a base for a setting, or as the reference for how a game package is structured.
Resolution
Ask the oracle one yes/no question at a time:
journal oracle "Is the bridge still standing?" --campaign <name>
| d6 | Result | Meaning |
|---|---|---|
| 6 | Yes, and… | It works, with a fortunate extra. |
| 5 | Yes | It works, plainly. |
| 4 | Yes, but… | It works, at a cost. |
| 3 | No, but… | It fails, with an opening. |
| 2 | No | It fails, plainly. |
| 1 | No, and… | It fails, and something gets worse. |
On and/but results, pass --complicate to fold in a twist.
The PC
Keep a minimal sheet: name, background, inventory, and any lasting conditions.
stats and tracks may stay empty. If a stat grows out of play, record its
shape in the campaign's house-rules.md so it stays consistent.
Character creation
- Roll a background:
journal background --campaign <name> - Give the PC a name and one relationship to the world.
- Write a starting situation into
campaign.md.
Pacing
End a scene when the situation changes or the player's intent resolves. Append scenes; never rewrite them.
Content
tables/sparks.csv— general content prompts.tables/complication-themes.csv— twists onand/butresults.characters/backgrounds.csv— rollable starting backgrounds.