Gamasutra is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
October 22, 2020
arrowPress Releases

If you enjoy reading this site, you might also want to check out these UBM Tech sites:


Story Flowchart Diagrams

by Emanuel Montero on 11/06/09 07:01:00 am

3 comments Share on Twitter    RSS

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.


I was writinga story for a 2 player horror game, and I end up with something like this:

 Linear Story Example

Figure 1: Linear story example.

It’s only a fragment. But it’s still interesting. It follows the typical linear story structure. All characters are hard-coded. There’s no variation, no choice, no interaction. Basically it’s a movie.

Of course, I can do it better. First I assume that players choose which character they play: the boy or the girl? Players also choose which character drives. Then we can add some challenges, player choices or random choices. And it looks like this:

Interactive Story Example 

Figure 2: Interactive story example.

It seems more like a game story. Players can choose their story path and the story remains always under control.

Now let’s draw some interesting conclusions.

First, we can diagram stories using flowcharts. Flowcharts are simple to diagram and easy to understand. So you can draw flowcharts in your favorite editing program and show them to your development team as a story schema. Flowcharts are useful to visualize a game story structure, so you can precisely communicate your story to the development team. Also you can find errors in the story structure from early stages of development.

Additionally, we can obtain a story Domain-Specific Language (DSL) adapting flowcharts to storytelling. In a flowchart diagram there’re some basic types of nodes: start/end nodes, process nodes and decision nodes. In a story flowchart we have: story start/end nodes, story exposition nodes and story choices.

  1. Story start/end nodes represent the beginning or the end of a story.  
  2. Story exposition nodes represent any story fragment conveyed to the players.
  3. Story choices represent any story decision. they can be of three types:
    1. Challenges are story choices that are based on player performance overcoming a conflict. Challenge choices always transition to failure or success story exposition nodes.
    2. Player choices are story choices based on the player will. The player chooses what to do.
    3. Random choices are story choices based on randomness or luck. 

 Note that figure 2 tries to illustrate all story primitives using flowchart visual notation. So we can specify a game story structure with a very simple diagram. Isn't it great?

Related Jobs

Deep Silver Volition
Deep Silver Volition — Champaign, Illinois, United States

Narrative Designer
Insomniac Games
Insomniac Games — Burbank, California, United States

Lead Engine Programmer
Deep Silver Volition
Deep Silver Volition — Champaign, Illinois, United States

Junior Gameplay Programmer
Sucker Punch Productions
Sucker Punch Productions — Bellevue, Washington, United States

Narrative Writer

Loading Comments

loader image