How to follow a story from its start to a threat¶
A season's work can start a story that comes later. A salamander drawn by Aurelia's fire spell hangs about her laboratory, and may want to become her familiar (a story event may come some time after the experiment, DE p. 276). The app keeps each one as an open Story Event until it's told, or grows into a threat.
- See where stories come from. An experiment's story event writes one in the covenant's Diary, concerning the magus. A Disaster's covenant story writes one concerning the covenant (DE p. 275), and Suggest a Story on a covenant's Hooks writes one when it's accepted.
- Add your own. In the covenant's Diary, add a Story Event, Open, with what it Concerns.
- Find them. The Region's Open Stories lists every open one of the troupe's covenants. A character's or laboratory's Connections lists its own.
- Take it up. Each time the troupe plays some of it, Take Up the Tale writes a chapter with the season, and what was done, met or avoided (see Take Up the Tale). The story's details list its chapters.
- Tell it. When the troupe plays it out, Edit it and mark it Resolved. The app asks for its last chapter, how it ended.
- Or let it grow. Left alone, it can become a threat of the Region. Grow into a Threat makes one from its words, and marks the story Grown.
- Give the threat its stages. Add them, and give it a clock if a place's trigger should move it (see How to set up a threat's clock).
- Take up the tale on the threat. From then on, its chapters go in the threat's Diary. Recording a stage's outcome can take one too, in What the troupe did.
See also: Diary, Grow into a Threat, A threat