Directing emergent narrative without losing the author

Hand a story engine enough freedom and it will happily improvise you straight out of your own plot. The promise of emergent narrative — a world that reshapes itself around the player — is also its failure mode: a thousand reactive moments that add up to nothing in particular.

Our working model treats the author less like a scriptwriter and more like a director with a thesis. You don’t pre-write every line. You define the spine that can’t bend, the questions the story exists to ask, and the boundaries past which improvisation stops being interesting and starts being noise.

The spine and the slack

In Ashfall, the act breaks are fixed. The ending is fixed. What floats is everything between — the order you meet people, the alliances you abandon, the world the director rebuilds around the choices you walked away from. The system has enormous slack, but the spine holds.

The system improvises. The author decides what the improvisation is about.

The hardest part is restraint. A generative director can always do more — add a twist, escalate, react. Most of the time it shouldn’t. A lot of our directing work is teaching the system when to sit still, because a quiet beat the player earned is worth more than a surprise the system invented.

We’re still wrong about a lot of this. The research log for Ashfall is mostly a record of climaxes the director flattened and tension it threw away. That’s fine. Knowing where authorship has to step back in is the finding.