Toward a minimum viable combinatorial narrative machine

I’ve been looking at a lot of experiments in storytelling form lately, and I see three broad types:

  • Traditional linear narrative in which the narrator is control of the reader/viewer’s path
  • Choose Your Own Adventure, in which the reader/viewer chooses among a set of carefully preordained paths
  • Random access, in which the reader/viewer can skip back and forth among a lot of story material with a high degree of freedom, but without experiencing a single, cohesive plot (e.g., I Love Your Work, CLOUDS)

Deciding which form to use involves weighing author control and overall cohesiveness against reader control. But is that a necessary tradeoff?

Would it be possible, I wonder, to create a new structure, which has the sense of unity of traditional linear narrative but some of the flexibility of the others? So that, for example, each time you read/watch/play a story, you start by hitting a “shuffle” button and get the same characters and settings as the time before, but different plots, goals, and themes. Could each combination be a single, cohesive story?

I can’t imagine this being done with text. But I can imagine it being done visually, because it has been done — but only very simply, and only in Russia, and only around 1920. Soviet filmmaker Lev Kuleshov performed an experiment in which he juxtaposed the same footage of a man’s expressionless face with a bowl of soup, a girl in a coffin, and a pretty woman. Depending on the cut, the audience saw the man act hungry, sad, or lustful. In this case, the trade-off between cohesiveness and reader/viewer control was not necessary — in fact, it was the viewer’s participation, her tendency to make sense of events by interpreting them as a story, that made the two clips a meaningful unity in the first place.

So here’s my idea for Kuleshov 2.0: rather than introducing new clips every time to create new stories as Kuleshov did, start out with all the story elements you need and just rearrange each time. The relationship between the clips might have to be a little more ambiguous than in mainstream Hollywood cinema, but as Kuleshov proved, we are a story-seeking people, and given a little help we will fill in gaps where necessary in order to create a narrative.

The mechanics of this narrative machine wouldn’t be the challenge: a “shuffle” button is a simpler mechanic than the “random access” examples linked above. What would be hard is coming up with clips that are both rich and loose enough in their juxtapositions to accommodate story-making in any combination. And that gets progressively harder as you scale: If you two clips to shuffle, you have two possible stories. But if you have three clips, there are six possible stories. Four clips, twenty-four possible stories. It becomes unwieldy quickly.

That’s what I worry about when I read something like this:

The words “combinatorial explosion” have probably never come up in a video game storytelling talk as many times as they did with BioShock creator Ken Levine’s “Narrative Legos.” At the 2014 Game Developers Conference in San Francisco, Levine outlined an ambitious — if vague — idea for endlessly replayable, systems-based stories that he compares to a player-driven episode of Game of Thrones. When a slide deck offhandedly lists “build a web of nearly infinite relationship states” as a prerequisite, you’re in for something that’s at least compelling listening.

What the creator of BioShock is interested in is a game that is a lot more complicated from a mechanics standpoint than my “shuffle” button, but that’s not the thing I’m hung up on. He’s talking about a LOT of elements, resulting in “nearly infinite” relationship states.” Setting aside the question of whether each play-though is equally fun, how do you even ensure that each is sensical? How do you do narrative quality control as the number of story element combinations your machine spits out approaches infinity?

Better to start small, I should think. What’s the minimum viable implementation of a combinatorial narrative machine?

A multitude of drastic things

In an interview in The Dissolve, three filmmakers talk about what it’s like to create interactive films.

They asked us for a script, and we were like, “That’s really hard,” because we wanted it to develop organically. Somehow, we convinced them that was okay. We wrote a broad-strokes break-up scene that just hit beats we thought could be interpreted in different ways, like, “Let’s have her say, ‘I’m going to do something drastic.’ That way, a multitude of drastic things could start playing out onscreen.” —Daniel Scheinert

The script is the most generic version of a breakup you could ever think of. There’s no way you could apply what they’re saying to 60 different actions if it was very specific. —Daniel Kwan

When we were brainstorming ideas over the last few years, that was the one thing he came up with that has become our touchstone of, “Why the fuck am I making interactive movies?” We’ve come back again and again to, “It’s only worth it if we implicate the audience in the story.” If because they’re clicking, they’re more invested, then it’s worth this added distraction. —Daniel Scheinert