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
January 16, 2021
arrowPress Releases

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


What are we talking about when we talk about systemic narrative?

by Victor Sanchez on 08/15/18 07:03:00 pm   Featured Blogs

7 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.


There are a lot of approaches to narrative on games. The most usual one is linear narrative where the storyline always follow the same path and reach the same conclusion, but we can find games with branching narratives, where the storyline “splits” on certain points providing different conclusions; parallel narratives, same that previous one, but branches merge again to reach an unique conclusion; non-linear narrative, where the storyline is divided on small chunks that the player must see, but they have certain freedom to choose the order and finally dynamic narrative where no specific ending is defined and the chunks of story can be played and replayed on almost any order.

Systemic narrative is not a new approach to narrative but a new way to realize any of the previous approaches.

When we talk about systems on games we refer to elements that work following rules. These rules are met by the internal state of the element, and this state can be modified by inputs and can provide outputs. These inputs and outputs may be provided or consumed by other elements of the system, other systems or players/NPC actions.

Systems do not provide responses that we cannot script (given enough time) but a different way on how those responses may happen.

The usual example is fire. We can script that when the player character have a torch and the interact button is pressed within a distance to a certain object, that object is set on fire. If we are going to create a system that provide this kind of interaction we can define some elements as flammable with a couple of internal variables to represent current temperature and current structure integrity. We would define as an input the external temperature and as an output, the generated heat. Our rules for this element could be something like “if input temperature is higher than current temperature, increase the current temperature”, “if current temperature is higher than a certain limit, set element on fire, decrease the structure integrity and output current temperature to surrounding elements” and finally “if structure reaches 0, destroy element”

Obviously this only makes sense when our scale starts growing. If there is just one element on the game to be lit with the torch, the scripted interaction is more than enough but if we are going to provide the players with a variety of elements that can be burned and we want to be able to propagate the fire with any element already on fire instead of just using the torch all the times, a system can prove useful. Even more… because the rules are usually based on real world behavior, it will provide more believable results and as the outputs will continue interacting with other elements, players will face situations that are acting on their own, not just reacting to their actions.

So, when we talk about Systemic Narrative, we talk about creating a system that provide the rules on how the narrative unfolds. We are talking about having narrative elements that may have some inputs, that modify an internal state, that is used to apply a serie of rules, and may provide some outputs, and as a good system, these inputs and outputs can have its source on or be consumed by other elements of the system, other systems or players/NPCs

A systemic narrative will show its greatness if we stop creating “player focused” narratives and start creating “narratives where the players are immersed in”, providing not a storyline that unfold because of the players, but a storyline where the players can act to try to influence it to their own interests.

I find important to notice that this is not a black or white situation. It is not fully systemic versus non systemic at all. We can mix and match. Currently we can see examples of games, usually open world games, that use a systemic approach on how the side missions are given to the players while the main storyline is presented on a more traditional “press button to start mission” way. Sadly, on these cases, the rules seem to not go too far beyond of a generic interpretation of its scripted counterpart, being limited to player centric checks (Has the player reached this level? Do the player’s inventory contains this object? Has it been X seconds since last time player tried to do this?)

As in the fire system example, there are little advantages on create a system that control the narrative when the final result is so constrained that a simple script could provide easily the same experience, but if we are aiming to have a narrative that seems to happen not just because the player pressed the interact button but because everything that has been happening provide the appropriate conditions that make it happens, then we should consider creating some form of systemic narrative.

Related Jobs

Square Enix, Inc.
Square Enix, Inc. — El Segundo, California, United States

Senior Web Developer
Sucker Punch Productions
Sucker Punch Productions — Bellevue, Washington, United States

Jackbox Games, Inc.
Jackbox Games, Inc. — Chicago, Illinois, United States

Senior Gameplay Engineer
innogames — Hamburg, Germany

Senior Mobile Game Developer (C++) - Forge of Empires

Loading Comments

loader image