or: “what games story can learn from Stephen Moffat”

So Braid finally came out. I was in shock when I saw the release date; wonderful as it was, I was never sure I was going to get a chance to play it. I shouldn’t have worried. It’s out, I’ve got it, and so far, it’s been very, very special.

And it’s had me thinking, because with all the coverage of Braid in the past few weeks – not to mention Jonathan Blow’s excellent keynote at Games:EDU last week – I’ve been thinking about games, and stories, and narrative, and writing (which is a special interest of mine if only because it’s one of the few things I know about that I actually studied). To understand what stories that can only be told in games look like, you need to know what stories that can only be told in other mediums look like. And that was when I realised I had some really good, mainstream examples to hand, and that I should explain this on the internet.

Now, to do that, I’m going to have to talk about Doctor Who.

Stephen Moffat wrote easily the best episode of new Who, Blink (from Season 3), and probably the best episodes of the most recent season – Silence in the Library and Forest of the Dead.

His episodes have received critical praise (ie: praise from adults); at the same time, they haven’t deviated from the core premise of the show: exciting sci-fi adventure aimed at the family market, which is basically 8-12-year-olds. This is a good thing. I’m very much with Mark Kermode when he points out that there’s far too much of an onus right now for entertainment targeting children to have “something for adults too”. If it’s good, it should appeal to everybody.

Stephen Moffat’s episodes are classic family entertainment; at the same time, they demonstrate very clearly that he understands the medium he’s working in – TV – explicitly, and he’s capable of writing stories that can only be told in TV and film.

Moffat’s episodes are designed around mechanics of fear. Specifically, the very things that most children are afraid of, or have been afraid of at some point in their life.

Blink is about creepy statues (which turn out to be aliens) that only move when you’re not looking at them. It taps into a fear of the uncanny, the ancient, and the inexplicable.

Silence in the Library and Forest of the Dead are about many things, but at the core of them is the primal fear of the dark. In it, shadows turn out not to be an effect of light, but creatures – the Vashta Nerada, vast clouds of tiny creatures that eat people.

Who hasn’t been afraid of the dark?

Both are great plot devices. Neither requires much in the way of complex effects. But the most important thing about them – certainly in terms of this article – is that they are plot devices that are entirely native to television and film.

Blink is an entire drama made possible by the fact that whilst TV is a linear medium, the audience understands editing. Editing as an artform has evolved over time; it was developed after the initial invention of film, and it was only a reasonable period after film’s creation that it was understood not only as a technique, but also as an art in its own right. (For a great example, look at the first five minutes of Nic Roeg’s Don’t Look Now – a very important sequence in that film, where it’s important that the editing shows how the characters are perceiving events as much as how they’re happening).

Anyhow, Blink and editing. The audience understands (even implicitly) that the statues aren’t moving in a blink of our eye; they’re moving in a blink of the characters’ eyes. This means they move in that simplest of scary-movie techniques, the jump-cut.

Because this jump-cut takes us by surprise, the creatures scare us like they scare the characters – even if we know that they’re not really moving when we don’t look. This particular kind of delivery of shocks isn’t possible (or at least as effective) in, eg, written fiction, because there is no possibility for edits, for jumpcuts. Prose flows in a linear manner forward, and whilst the writing may contain careful pacing, the act of reading is paced fairly consistantly.

The two-part story in Silence in the Library and Forest of the Dead is a drama all about light and dark. The Vashta Nerada, as mentioned, are clouds of creatures that look exactly like shadows – and are, of course, represented as shadows on screen. There are a few important effects shots where characters are seen to have multiple shadows, but most of the time, there’s no need for trickery.

All the “magic” is in set and lighting design, and script: dark corners, nooks and crannies, and the characters telling us they’re afraid of the dark. When the Doctor says “stay out of the shadows,” he reminds the audience that they too were afraid of the dark once. And, of course, as a child, when you say you’re afraid of the dark, an adult tells you there’s nothing there. The Doctor has told us to be afraid of the dark because the dark really is a monster. He’s contradicted our parents and made us even more afraid. It’s terrifying.

We need to find stories that we can only tell in games. We need to find play mechanics that tell us things about the world.

Both of these stories are natively filmic: a story that can only be told when you understand editing; a story built around the visual representation of light. These are, of course, not the only things the story is about – far from it; their richness and brilliance is the real reason Moffat has been so admired. But it’s important to appreciate that these two storylines stem from an individual technique or aesthetic that’s uniquely represented by the medium (TV/film).

Or, to put it more simply (and I think more effectively):

something everyone is afraid of when they’re eight + a plot device that can be satisfactorily represented on television/film without being too expensive or convoluted.

So what has this got to do with games?

The notion of telling stories appropriate to a medium is one response to what Braid developer Jonathan Blow is getting at in his Games:EDU keynote. Rather than resolving the conflict between ludic and narrative elements by wrapping gameplay around the story, why not write stories that can only be told through gameplay?

Braid is a game about trying to reverse the past; its time-control mechanic is an important commentary on the central character’s predicament. Moffat’s Blink would make a poor videogame, simply because it’s unfair; the Weeping Angels essentially have a cheatcode to the world, and their movement patterns wouldn’t make for fun.

But a game built around shadows – genuine light and dark area – as a foe might work. It’s very gamelike – and it’s that that set me thinking on this whole endeavour. We have spent so much money on lighting technologies and graphics cards and we can now make beautiful light and dark – both realistic and expressive. Why can’t that be a game – or at least, the starting point for a game – in its own right? Just because at the moment it just a neat visual effect doesn’t mean we can’t put it front and centre. This is something that, for a while, James Cameron did very effectively. The Terminator, T2, The Abyss, even Titanic; these are all movies that require sophisticated visual effects to tell a key part of the story – the T-800, the T-1000, the underwater creature, the ship; without convincing, cutting edge effects technology, these movies fall apart. But Cameron is interested primarily in his characters: once he has his core, visual-effect oriented premise in place, he turns his camera to the characters. He wants to tell human stories; he just happens to have found stories about that need remarkable visual effects to play out.

We need to find stories that we can only tell in games. We need to find play mechanics that tell us things about the world. And if we’re stuck for inspiration, it’s worth considering how other mediums have approached this issue. Above, there are a few examples; there are many more, when it comes to literature, and film, and radio drama, and theatre (and especially those last two). But when it comes to games, there aren’t enough.

We need to start considering what they might look like. Stories about shadows and lighting. Stories about physical worlds told through physics engines. Stories about direct control, or the lack of it.

Some of these exist; more need to. That’s the challenge facing games right now. If you’re looking for an example, download Braid and savour it. It really does succeed at the things Blow hints at. It tells a story you need to experience, and you need to experience the mechanic at the core of it to appreciate the game’s message. It’s remarkable.

Iroquois Pliskin has an excellent blog post from a while back about the way Grand Theft Auto IV is torn in its characterisation. It’s a great post, and well worth a read. And it also made me think:

In GTAIV, Niko Bellic has the option to socialise with the friends and acquaintances he meets throughout the game. These have little bearing on the plot, but are entertaining minigames, with some fun dialogue trees: darts, bowling, pool, drinking, and dating girls. Being friendly to certain characters may also have benefits in the long run – neat little tools and tricks you can summon with a call from the in-game mobile.

These games are totally optional, of course; you can happily play the game without seeing too many of them. But Iroquois’ piece made me realise that these “friendship games” aren’t just there for entertainment value, or for the neat bonuses you can get later in the game.

They’re there for characterisation – and a very specific kind of characterisation.

Niko is violent, Niko does bad things. You have a choice: you can temper that, by saying “but my Niko is also a good man: he’s nice to the girls he dates, he hangs out with his friends, he’s a good cousin to Roman“. Or you can turn you back on your friends, and a healthy, sensible social life, and focus entirely on the life of crime.

To play the game as it’s meant to be played, you can’t avoid the life of crime. But the player has a choice as to how much they temper the life of crime, and their malevolant sandbox antics, with the social-simulation aspects. If Niko becomes, essentially, psychotic – only focused on completing mission objectives, and not living the life – then who’s to blame but the player? To quote Iroquois:

There are some advantages for cultivating these relationships, but in general you get the idea that they are put in the game in order to give you a better perspective on your character. The portait of Niko that emerges is very well-drawn, and he emerges as a violent but ultimately sympathetic figure, a decent man who has been drawn into a life of expert violence against his own best efforts.

I think Niko is much more likely to emerge as “ultimately sympathetic” if the player makes the effort to round out his character. The cut-scenes and plot points the player is railroaded into go someway to providing that characterisation, but they provide that characterisation in dialogue and narrative. When the player helps create that characterisation through behaviour and gameplay, then the effect on the player’s understanding of Niko is much more deeply embedded.

Developing characterisation not through narrative but patterns of gameplay elements. I like that.

(Also: I can heartily recommend Iroquois’ blog, Versus Clu Clu Land)

Killing Jeff: Epilogue

04 June 2008

It only seemed appropriate to post an update to my tale of morality in Liberty City, given that Jeff is now dead. It’s also appropriate, this time around, to talk slightly less in the first person.

Once again, the player bumps into Jeff on the street – a small blue icon on the map. Niko bumps into him; he’s staring through a pair of binoculars at a house across the road. Niko is really unenthusiastic about meeting Jeff again, which I was pleased about. One trend that emerges throughout GTAIV is that whilst Niko has no hesitation about doing dirty work, that’s all very dependent on the reasons behind it. He’s angry that Brucie made him kill people simply because Brucie was hopped up on steroids, for instance; he’s less angry about crimes that fit within his moral spectrum.

Niko is really angry with Jeff. This made me feel somewhat relieved, if only because it felt like this was going to pan out a bit better. It turns out that Jeff has remarried (an instance of GTA’s somewhat liquid attitude to time) and is sitting watching his wife meet her ex. Of course, he’s decided this is a bad thing, and he wants Niko to kill her.

Niko’s having none of it, and gets quite angry with Jeff. Jeff starts yelling; Niko is “just like all the others“, it seems, and Jeff crosses the road to do the deed himself.

At this point, I’m thinking: is this where I get to kill Jeff, right? This is where Niko gets to demonstrate a wider spectrum of his morals.

And then a supercar piles down the street and runs Jeff over. He bumps over the windscreen, scattering the contents of his wallets, and lies splayed on the pavement. A lawyer-type leaps out of the car, gets on the phone, starts telling the police he’s had an accident. Jeff is still, splayed in the road.

Jeff has been killed in an accident appears, as a legend at the bottom of the screen.

I’m glad; I’m disappointed; I’m chastised. I’m glad he’s dead. I’m disappointed I didn’t get to kill him. I’m chastised for thinking about murdering a civilian.


The Jeff arc is a tiny, optional, three-mission plot in GTAIV, and I’m sure many players won’t experience it. I’m not sure it does much for the game’s misogynist reputation, which is something I am still sitting on the fence about – I have issues with some of its characterisation, for sure, but am not convinced of all the criticism thrown at the game. At the same time, it addresses an interesting issue that hasn’t really come up in the series (even in San Andreas, where it might have been an obvious fit): namely, the gap between criminals and civilians, and also more objective viewpoints of “good” and “bad”. The game is so heavily based upon subjective morals that it’s a really interesting shift of perspective.

Whilst the Jeff missions were presented as a real arc, rather than a series of disparate events, I’m still totally frustrated by the lack of freedom offered in the second Jeff mission, which was really quite unpleasant and made me genuinely angry. Still, I’m glad I played through to the end of the arc. For what it’s worth, there was a sense of closure.

Killing Jeff

18 May 2008


Update: I mistakenly called Jeff “Phil”. No idea where that came from. My bad.

Jeff should be dead.

I met Jeff on the street. He was just a blue blip on my minimap, to begin with. I’d seen him around for a while, but I was now passing right by him, and I was on foot, so I thought I’d head over to see what the blip was all about. And then Jeff started talking, and he wouldn’t shut up.

Jittery, paranoid. Babbling about how his wife’s cheating on him. Kept calling her bad names – bitch, whore. Not cool. But I listen. Anyhow, Jeff wants me to follow her when she leaves the apartment one day, and see where she’s going. Seems like an easy buck, and if he’s wrong, he’ll be glad to know that, right?

So I pull up outside the apartment, and watch her leave. Red Feltzer coupé. Very nice. Tail her for a few blocks, and she pulls up at a café.

I head inside, see her talking to some guy. Smart, suit, smells like a lawyer or something. Anyhow, I keep my distance, a few blocks over, snap a few pictures on my phone. I mean, if Jeff knows the guy, this all might blow over, right? Can’t help but listen to them. And, sure enough, there’s nothing sinister – not yet, anyhow. Just her, talking to some guy she knows – work colleague, maybe – about how jittery and paranoid Jeff is. How it’s driving her nuts, she’s not sure what to do. No affair, no cheating. Just jittery, paranoid Jeff.

I message him the pics, and he flies off the handle and hangs up. Not exactly cool; let’s just hope it all blows over.


Jeff calls me in the night. I’ve just bought a suit for this interview I’ve got tomorrow, big-shot law firm. Need to look the part. Anyhow, I need some sleep, but Jeff’s just yelling at me, screaming, telling me he needs to see me. He’s in a parking garage near Roman’s new apartment.

Parking garages never bode well.

And there’s no option to say no. No conversation branch, no choice; I picked up the phone and I got landed with Jeff – much like when I wandered up to him and he threw me into a mission. Already, I’m sick of Jeff.

So I go to the garage, pull up inside, and there’s Jeff, jittering about, holding himself. Things aren’t good. “Jeff made a mistake,” he tells me, not realising that talking in the third person is a dead giveaway for crazy. Tells me his wife’s had an accident. What kind of accident, I say. Jeff shows me.

The body is in his nasty little hatchback.

I have met many bad people in Liberty City, but Jeff is the worst. Jeff is not a criminal. He doesn’t deal drugs, he doesn’t rob banks, he doesn’t traffic people. He’s your ordinary-decent-citizen. Jeff’s wife is blameless in all of this. And yet he killed an innocent, decent woman, for no apparent reason, and he keeps talking about her like that, and I can tell that Niko hates Jeff, and feels a bit sick, and I hate Jeff, and feel a bit sick.

Jeff gives me the car keys, and sits on the tarmac, crying. He wants me to dump the body.

I’ve never intentionally killed civilians. No joke. Maybe the odd auto accident, but no shooting. Everyone who’s died by my hand has been cop or crook – somebody who was shooting at me, or who would kill me later if I didn’t kill them now. Those are the rules, right?

Anyhow, Jeff is sitting on the pavement in front of me, and I’m thinking that I don’t want his phonecalls in the night, and I don’t want his guilt, and I don’t want him dragging ordinary, decent people into the kind of shit you shouldn’t even choose for yourself (and heaven knows I’ve tried not to), and I realise that a moral decision is presenting itself to me. And there’s only one moral decision I can make in Liberty City.

I pull out my piece and put three rounds into Jeff. He doesn’t even look up when I draw the gun, he’s too busy crying. Sure, he’s not well, but he’s also gone too far, and I don’t want to have anything more to do with this. He rolls back on the ground, must have hit him in head and torso. I hate, you Jeff.

A black-and-white lights up behind me; must have been prowling the parking garage. I leap into Jeff’s car and head for the river. Doesn’t take much ducking and diving to avoid the single patrol car and lose the heat. Now I’ve just got to dump this car and dump the body. He didn’t even put it in the boot; it’s lying around on the backseat, and I can’t avoid seeing it as I’m driving. Still gives me that lump in my throat.

Towards the river, must be barrelling along at about 40. I lurch off the road, head straight for it. It’s hard judging distance at speed, and I throw open the door a fraction too late, because rather than rolling out onto the grass, I end up leaping out above the water. The car goes headfirst into the river as I dunk myself in it.

New interview suit, soaked already.

Jeff’s dead. Jeff’s car’s in the river, along with Jeff’s wife’s corpse. Poor Jeff’s wife. Wish I’d never met him.

I clamber out of the river, and head for home; time to catch some sleep before the big interview.

My cellphone rings.

It’s Jeff.

Jeff should be dead. He was dead to me the second he showed me the corpse in the back of the Blista; he was deader when I shot him, watched him crumple. And now he’s on the phone to me again, like nothing’s happened. I can’t describe my anger; all at once, I’m furious.

And the city fades away and the game wells up over me and I want to scream at Jeff, and scream at Rockstar, and empty my pistol into Jeff, tugging on the joypad trigger again and again until the virtual gun clicks dry, so that he can never come back again, never hurt anyone again. I made a choice – a valid choice in the game world – and for the first time in this game it had no repercussions. I’d have taken any amount of heat just to put Jeff down. But the game wouldn’t let me. The game thought he deserved to live. Saddened, I turn the 360 off.


Grand Theft Auto IV is a wonderful game; it resists any tarnishing with terms such as “fetch quests” and “escort missions” by virtue of the solidity and coherence of world it presents. It rises above the stereotypes of previous games and attempts to create genuine characters, however simple or cartoonish. Few of them are truly evil, few of them can ever be redeemed; they all tread the awkward line between survival and violent death.

Jeff was different; Jeff was the first time that I’d met a character I (and, indeed, Niko – the player’s character) found distasteful. For the first time, the game gave me no choice but to take his missions the second I approached him or picked up the phone. I could have coped with Jeff if I felt like I’d had the opportunity to do something – anything – about him. The game gave me that opportunity, and took it away, and it shouldn’t have done that. Not if it wants me to take the “freedom” it offers me seriously.

I’m going to keep playing, but every time my phone rings, I’ll pray it’s not Jeff, and if it ever is Jeff, I’m going to remember what I want to do to him – and why I want to do that to him – before I hit “reject”.

Rebooting

12 April 2006

Exciting news of the day: I’m going to be speaking at the Reboot conference in Denmark this summer.

Looking forward to it lots, though obviously I need to start working on the talk soon. Still, following ETech, I don’t think I’m going to let myself get quite so stressed.

What follows is the rough pitch I outlined in an email (written, as ever, in conference-abstract-ese); final version may vary, obviously, but I think it conveys the gist of what I want to discuss:

“Telling stories – what social software can learn from Homer, Dickens, and Marvel Comics”
or: “Social software as serial narrative”

Social software is playful, and much ludic analysis has been made of it. But what of narrative analysis? After all, we use this software to tell the grand serial narrative of our lives – cataloguing them via Flickr, journalling them (in whatever form) via our blogs. And then consider the wealth of parallel narratives many people have – a delicious account, a Flickr account, multiple blogs, LiveJournals, MySpace accounts, some contradictory, some anonymous, some fictional, some fact. This isn’t a bug, it’s a feature; we should encourage parallel storytelling, encourage the formation of personas, and make the interaction between these different platforms as complete as it needs to be to support this.

We should design our software around these narrative impulses. In ten, twenty, thirty years time, for good or ill, we will want to look back at the stories we told – for they are part of our greater story. So as well as encouraging parallel narrative, we need to consider how best to support the long ongoing narrative that we weave.

So: let’s look at how, over history, serial narrative has been told, distributed, and retrospectively altered, and see what it tells us about the tools we build to tell our stories.