If Games Were Like Game Stories...
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.
Not for a lack of trying. Game developers often look to other art forms (movies, books, TV) and try to model game stories after them. However, this leads to a disjointed feeling between gameplay and narrative, and why most games stick to the old model of "cutscene-gameplay-cutscene". How can we merge systems and stories, how can we create systemic stories?
While creating my short semi-autobiographical narrative game,Â Coming Out Simulator 2014, I learnt three ways we can make game stories more fluid, more natural.Â There's one place we should seek to model our games' stories after... and that's games themselves.
1) Kill the "branching" metaphor.
Most games have a continuous playing space. The game gives you countless options in how to move your character, or manage resources, or build a world. Not all the options lead to significantly different outcomes, nor are all of them good. But you still get a broad spectrum of choices.
In contrast, most game stories only give you a few "branching points" here and there, if they give you any influence over the plot at all. But here's the core problem of "branching": as you add more branches, your game's content grows exponentially. The most common solutions to this problem aren't much better: have lots of dead ends, have all branches re-combine, have branches only at the end, or have a very short game.
But "branching" is such a core assumption of game writing nowadays, we forget that there's an alternative right under our noses. Forget about branching. Let game stories have a continuous and ever-broadening possibility space.
Player choices should flavour the later story, instead of creating entirely separate branches.
Case Study: Papers, Please.
In Papers, Please, you play an immigration officer, deciding whether to approve or reject people for entry. Each "day"/level of the game, you process around 10 people. What you choose for each person affects both the gameplay and the story. But if each approve/deny decision created a new branch in the game, each day would result in 1024 branches. And there's 30 days in the game.
The game doesn't have 1024^30 endings, obviously.
Accidentally reject someone with legit paperwork, and it won't radically change the game. But it does subtly add more stress, resulting in later incorrect or unethical decisions. The game also has multiple sub-stories. Your choices add up over time, as the game/story shifts through a continuous space of possibility.
Telltale's The Walking Dead games have a more-or-less linear story, but the big and small details (your reputation, how Clementine sees you, who's still alive) are flavoured by your choices.
2) The little things matter.
In game design, there's the idea of "juice". It's the particles, sound effects, and secondary animation to make the game feel like it's really responding to you. And it's not just for big gameplay actions either. It's the footsteps and inertia of walking around. It's the highlight and sound effect of hovering over a button. It's the little things that matter.
Why not have the same in game stories? Instead of every decision being a Big Moral Choice, scatter your game with lots of small choices, and actually have those choices pop up again and again. Decisions in the past coming back to surprise the player, or to haunt the player.
Have small choices flavour the game's story.
Case Study: um... Papers, Please.
My favourite moment from Papers, Please was when someone gave me a banner for a sports team named the Arstotzka Arskickers. I had a choice of whether to put it up on my wall, or not.
Compared to all the other decisions... taking bribes, separating families, conspiring to take down the Arstotzkan government... this was a small and silly decision. I put it up on my wall, of course.
But the reason this is so memorable to me, is because the game actively acknowledged this small act! A few people commented on the banner, some remarking it's tacky, some cheering "Go Arskickers!" And then, of course, this decision bites me in the ass when the inspector comes by and tells me the decoration is against protocol, and fines me.
The game also acknowledges your other choices through dialogue, the newspaper segments, and recurring characters. The point is, if your game's story is so juicy, responsive, and alive... that even a sports banner has a story arc of its own? You've done good.
- Bastion. The narrator live-commenting on you attacking enemies, getting hurt, and other actions.
- The Walking Dead making you regret every single damn choice, ever. Even saying the word "shit" instead of "fertilizer".
- The Stanley Parable. The narrator reacts to your every action, or inaction, no matter how silly. (Did you get the broom closet ending?)
3) Game choices = Story choices
Imagine if a platformer game made you use the arrow keys to walk, the mouse to run, and voice recognition to jump. Great idea, if you want carpal tunnel and a sore throat. Otherwise, your game's controls should be consistent, and for a few exceptions, (like menu screens) not change drastically in-game.
So why do games suddenly switch from run-and-shoot to CHOOSE A OR B when they want to include story decisions?
Actions speak louder than words. Let the gameplay actions a player takes influence the story. How the player controls the game should be the same way the player controls the story.
Case Study: yeah, you guessed it... Papers, Please.
APPROVE, or REJECT. That's the choice you have to make every time a new person comes in with paperwork. Not only do story choices and game choices have the same controls, the story choices are the game choices.
There's another game mechanic in Papers Please that also serves as a story choice mechanism. At the end of each day, you choose how much of your day's salary to go to heat, food, and medicine for your family. On the surface, it's simple resource management. But what you choose, who starves or lives or dies, heavily impacts the story.
On top of all that, the game's mechanics reflect the mood of the story. The gameplay is routine, but stressful, and forces you to obey arbitrarily changing rules. This reflects the depressing, bureaucratic world your character is trapped in. Game mechanics can convey emotions all by themselves.
Okay, Fine, Have More Examples:
- Spec Ops: The Line. The core gameplay is shooting at things, and you make story choices the same way. (e.g. shoot at the the thief, or the murderer?... or the snipers, or the rope, or run away...)
- No-One Has To Die. An underappreciated gem of an indie game. This is a puzzle game, where each level has multiple solutions - and which solution you pick determines who lives or dies.
- Brothers: A Tale of Two Sons. You use the left and right thumbsticks to control two brothers separately, and they work together to solve puzzles. They're individual, but united. It's a great mechanical metaphor.
In The End...
If games were like game stories... they'd have lots of dead-end branches, feel unresponsive, and have wildly inconsistent controls.
Games are still a very young art form. We're all still figuring this stuff out, but the several recent examples I listed give me hope. (did I mention Papers Please?) Maybe these games will lead the way in helping us figure out how to do storytelling through gameplay. Systemic stories. And we can start by asking one question, asking a simple "if"...
"If game stories were like games..."
. . .