Screenwriting view – the best of both worlds

18/11/2026

Petteri Sulonen

Co-Founder, CEO & CTO

I really enjoy being a toolmaker. It's given me the opportunity to work with some incredibly cool people with wild ideas, and I've derived a great deal of happiness when I see that something I've made has let them make those ideas into a reality. One of my favourite parts of the job is working together with them, understanding where their frictions are and what they actually need, which isn't always what they say or think they need. A bit like making games, actually – players express a lot of opinions but the games they really love are often the ones they never knew to ask for.

During the years we've been working on narrative design and game writing tooling, we've discovered a split that goes pretty deep in the way writers think about game writing. Writers fall into one of two camps, with a third group that switches fluidly between them. We've dubbed them the "linear" and the "graph" camps. They're about how you conceptualise a narrative and work on it.

The Tarinoi graph view – good for structure.

Reactivity and Structure ​

Game narratives differ from screenplays or stories in a number of ways, but the most important one is that there is usually an element of reactivity to them. This can range from very simple to fiendishly complex: at one end of the scale, linear dialogues that are triggered at particular points in the game, at the other, thousands of variables tracking player choices and characteristics gating branches, with forks based on game mechanics or player decisions.

At the same time, players experience dialogue much like in a TV show or a movie. All the characteristics of good writing need to be there – characterisation, pacing, beats, rhythm, flow. This is equally true for a perfectly linear piece of dialogue as it is for a massively reactive one.

Linear is for flow, graph is for structure ​

Screenwriting has a well-established standard for screenplays. It is excellent when pacing, rhythm, and flow are the focus. One page of a screenplay is about one minute of screen time. It is easy to get into the flow of writing when the format is familiar and you can just keep typing. When reviewing or reading – silently or out loud –, the screenplay format removes distractions and let you focus on how it feels.

However, screenplays, being linear, are not good at representing structure: which parts of a dialogue are conditional or forking; how the player can jump around a structure, returning to previously discussed topics or moving to something different. The more reactivity your game has, the trickier it becomes to visualise that in screenplay format.

This is where the graph comes in. It's much easier to represent gated content, choices, jumps, links, and forks as a graph. Visualising game dialogue this way also nudges you to a different kind of writing, more reactive, more player-centred. Players tend to love this kind of thing: it lets them express themselves and shape the experience to make it uniquely theirs.

Several narrative writing tools that are fundamentally linear, screenplay-like, address this by projecting their dialogue source into a graph that visualises the links and relations between the lines, so writers and designers can add the structure they need. Yarn Spinner, for example, includes this kind of visualisation.

Tarinoi is at its core a node-based, graph tool. The stories the writers at ZA/UM were working on were probably the most complex anyone has attempted, and we became very familiar with the challenges related to delivering that kind of reactivity, and brought that familiarity over to Tarinoi when we started to work on it.

However, over the years, several writers and narrative designers have told us that it would really help to be able to see a flow as a screenplay and, even better, work on it in that mode. Screenplays are also extremely useful for voiceover sessions, and in previous work we did just that.

Screenwriting view shows you the dialogue as a screenplay.

Enter Screenwriting Mode ​

That's why we added screenwriting mode to Tarinoi by making a linear screenplay projection of the dialogue graph.

What this means in practice is that you can click a button to switch between the graph view and the screenplay view of your board. In screenplay view, you just write. You work with the standard screenplay format with scene headers, cues, lines, and action paragraphs, and Tarinoi interprets your intent. It'll create cards or modify them. You can add (CHOICE) after cue lines to make fans of sibling cards, and use some Tarinoi-specific markdown like {hub} :: ferryman to place a hub card, and => ferryman to do some light structural work.

All the detail is there if you need it.

The card you're working on is displayed in the right drawer if you have it open, so you can deep-dive into its properties right there, and when you need to do structural work, you can hop back into graph view with the toggle. Switching is instant so you can flip back and forth as much as you need.

We think this mode is going to be helpful for a whole number of scenarios – most of these explicitly described to us by writers:

  • Early drafts. Sometimes you'll want to get the critical, linear path of the dialogue down first, then expand sideways for reactivity and forking. This sets the mood, tone, and pace, and you're not yet worrying about structure, so screenwriting mode is the natural way to do it.
  • Creative review and editing. When you're reviewing your own or somebody else's work, looking at cards won't always cut it. In-line playback is super helpful for this especially if you want to see how it plays in different game states, but just reading the screenplay silently or out loud will often do it, and in screenwriting mode, you can make your edits as you go.
  • Relatively linear stories. Some games don't have that much reactivity or branching – if your writing is based on a simple hub-and-spoke design, you might even do most of your work in screenwriting mode, just occasionally peeking at the graph for sanity.
  • Bringing in stuff you drafted elsewhere. Maybe you already wrote a screenplay as a basis for your in-game dialogue. Copy-paste it in, and you're go.

¿Por qué no los dos? ​

Because the screenplay is a projection of the graph, you can switch between the two instantly, at any time. When you've written the spine of your dialogue in screenwriting mode, you can switch back to graph mode to rearrange the cards, add branches, work with conditions, and expand sideways, then switch back to screenwriting view to write out a branch. When you're in the final review phases, you can read your dialogues as screenplays and make edits, keeping the structure intact. You get the best of both worlds.

We also have big plans around this feature when we get to implementing VO recording support – voice actors will want screenplays to study and read, and we're going to give you that. It won't be exactly the same as what you see when working on a dialogue, but screenplay view is a solid foundation for that too. I look forward to writing about that when we get closer to that feature.

#features
#updates

You may also like...

Squaring A Circle – Game State Preview

Tarinoi is unopinionated: your game, your mechanics, your way to make it. At the same time, it's really useful to be able to preview your game state in the editor playback. Here's the compromise we landed on.

The New Complete Joy Of Devops

Devops is an area everybody encounters, but there's no turnkey solution for it. This is a discussion about how we organise ours.

What Tarinoi is Not

We've talked a lot about what Tarinoi is. Now that early users are exploring the platform, we want to clear up some misconceptions and talk about what it's not.