tag:blogger.com,1999:blog-60825332398751813372024-03-13T08:31:57.539-07:00Truth, Love, and Courage: Games as StoriesDedicated to the study of interactive storytelling and narrative design in video games, from the perspective of a writer and former game critic turned game designer.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.comBlogger23125tag:blogger.com,1999:blog-6082533239875181337.post-5774177710533926202014-12-30T13:38:00.001-08:002014-12-30T13:38:17.042-08:00In ConclusionIt's been a year and a day since I posted anything here, so I figured I'd post something to put a bookend on whatever this blog has meant to me since I started it in 2010.<br />
<br />
A year ago <b>Transistor</b> had just hit alpha, so in a lot of ways some of the hardest work was over. I had already been working long days for some time getting my part of the game to that point. Last year was tough but this year proved even tougher overall. The lead-up to Transistor's launch was physically taxing, and the aftermath was emotionally draining, as game launches tend to be -- but for me, more so than usual. While there are a bunch of reasons for that, the simplest is I've never worked on anything for as long as I worked on Transistor. It wasn't in development for a huge amount of time in the grand scheme of things (about 2-and-a-half years), but that's a while for me, especially given my background of web publishing and its very compressed deadlines. I like when things move fast.<br />
<br />
I've now had plenty of time to reflect, and can say the experience of having worked on that game changed me both physically and psychologically if not spiritually. It's reinforced to me core truths about myself, about what I'm capable of despite all my self-doubt, and about games. It's caused me to shed about 40 pounds and counting (through a combination of exercise, giving up eating anything I like, and giving up drinking except in situations where it's socially awkward not to). It's filled me with a mix of hope and fear for the future, a good set of feelings overall. Like many people, I attempt to apply narrative tidiness to make sense of life's meaningless turns, and through that lens I feel like I have some closure on a finished chapter.<br />
<br />
I also became aware I almost never posted here during Transistor's development. That's less for lack of material and more for lack of conclusions, and I suppose a sense of fear that anything I wrote before the game was out would just make trouble. As the point of this was to be a free-form environment in which I could write whatever I wanted at whim, I realized I had to find another outlet.<br />
<br />
Besides, I feel there are more great narrative games now than in years past. The Independent Games Festival now recognizes excellence in narrative among other craft categories. I think game players are discerning about good writing -- they know it when they hear or read it. This year alone there were games like <b>The Banner Saga</b>, <b>80 Days</b>, <b>Kentucky Route Zero Episode III</b>, <b>The Fall</b>, <b>Wolfenstein: The New Order</b>, and Telltale Games' entire line-up to name a few. While debate continues, and I think will always continue, over whether narrative is necessary or even relevant to games, I think the evidence stands that for a number of games each year, their use of interactive narrative is essential to the lasting positive impressions they create for many players.<br />
<br />
<div style="text-align: center;">
* * *</div>
<br />
I got into game development because I was interested in speaking through my actions, having spent a long time speaking mostly through words in my previous line of work. It turns out I need the balance. It's important to me to keep writing as part of what I do. Writing for me is a form of exorcism. It's a way of heeding the voice that's never steered me wrong. And now that voice is telling me I ought to wrap this up. Don't be a stranger,<br />
<br />
GregGreg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com0tag:blogger.com,1999:blog-6082533239875181337.post-68760304236630483652013-12-29T22:56:00.002-08:002013-12-29T23:08:17.446-08:00Specificity and PrivacyThe expression "there is nothing new under the sun" is so old, it's from the Bible. It's something I happen to believe; the expression I mean. Having worked on games for a number of years now I'm surprised-but-not-really how often the Quest for Originality rears its head in everything from design discussions to publisher evaluations to marketing meetings and so on. I think this quest is as pointless as Don Quixote's tilting at windmills.<br />
<br />
Here is a formula for originality: To make something original,<br />
1) Choose a concept at random.<br />
2) Repeat step 1 and mix, or stop.<br />
<br />
That's it. Try it! as a fun thought experiment almost guaranteeing a "not been done before" result, fast. Puzzle game about a love triangle between triangles? Shooter about extraterrestrial dolphins harpooning humans? Why not? Original ideas are as easy as Mad Libs, and like Mad Libs they can be funny. But like anything that can be reduced to a formula (not even chemicals, as <i>Breaking Bad</i> attests), this type of originality feels cheap. It is original in the negative sense -- gimmicky, novel for its own sake, contrived, and so on.<br />
<br />
I think when we speak of originality what we're really searching for, what we really want, is specificity. Specificity is a form of depth, and all games want depth. Specificity is depth of subject matter. A game that explores a particular subject in detail comes across as original in the positive sense. Rich, imaginative, a labor of love, and so on.<br />
<br />
<div style="text-align: center;">
* * *</div>
Specificity is inherently challenging because it means you have to explore a topic to a level of detail that is not obvious, and it's difficult to know more about a topic than anybody else.<br />
<br />
I just finished reading <i>Journey to the Centre of the Earth</i> to one of my kids and was struck by the specificity of the story. Towns and mountains in Iceland, ancient scientists, types of rocks and minerals, all named and described in detail, lending the book an air of authority as well as its distinct tone. The science may be total nonsense, but you wouldn't know it just from reading, and it doesn't even matter either way because it's a work of fiction. Unless you're Neil deGrass Tyson or whatever you're probably not going to have trouble suspending your disbelief as you read, because the specificity of the work is thorough and convincing.<br />
<br />
I think this year's critically acclaimed <b>Gone Home</b> is successful
in a similar way, by telling a specific story in a specific time and place. The
details are well-grounded, giving the game a sense of richness, and making the
environment feel convincing. If you played it I bet you spent a while scanning the VHS tape library as I did. Specific names of things are so valuable! Everything needs a name and a little story. Gone Home is arguably not an original game in the
conventional sense, in that the core play experience -- everything from the
setting (an old house) to what you do in the game (walk around examining things from a first-person viewpoint) are not out of the ordinary. However,
the degree to which the game is invested in its specific ideas is unusual, so
even though there are dozens of first-person games with terrific exploration
sequences, Gone Home is one of very few where that is the entire focus.<br />
<br />
To give a real-world example, an old friend of mine knows in intricate detail the history and all the routes of the MUNI bus system in San Francisco. It's a set of knowledge that seems very bland on the surface but I envy it because it's so specific. If Teddy made games he could probably make an amazing game about managing a municipal bus system (he and I played tons of <b>SimCity </b>and <b>Aerobiz</b> back in the day, besides). A game about managing a municipal bus system sounds pretty awful at face value, but then, so does a game about being a customs officer stamping passports, and yet <b>Papers, Please</b> was one of the best, most interesting games of this past year.<br />
<br />
Games made by fewer people I think can have a higher chance of being more specific because there are fewer people on the team to challenge the specificity, to rationalize it out of existence. I'm talking about the little things like <i>Journey to the Centre of the Earth</i>'s Icelandic locales. What if the reader doesn't know how to pronounce Snæfellsjökull...? Jules Verne decided to give his reader the benefit of the doubt on dealing with that one. But on larger teams, or teams of any size where this there's creative conflict, there's always going to be the temptation to omit, to compromise, to concede, when it comes to the specific details, to file down all those sharp edges. This may be better for a smooth and pleasant development process but it may be worse for the sake of the game's specificity, and therefore for the sake of the game.<br />
<br />
Specificity typically requires research, the more the better (and preferably not limited to Wikipedia because everyone uses Wikipedia). The research can be of a real-world subject or in service of a fictional one. <i>Game of Thrones</i> is a work of fantasy fiction, but its level of detail, from superficial things like clothes and food to subdermal things like character motivations, makes it feel fresh and distinct. It takes place in its own made-up world yet it feels very well researched.<br />
<br />
The only other good source of specificity is personal experience. To me the emphasis here is on the personal, or in other words, the private. There are some rare cases like the game <b>Papo and Yo</b>, in which a team can rally around one individual's personal experience and make an interesting game about it. But I also think some of the most interesting aspects of personal experience are unrelatable and truly private, and that this is often why art gets made. If I were to just tell you about the most meaningful experiences of my life, or if I tried to make a game unambiguously and autobiographically about it, it would be the worst, just the most banal cliché bullshit, and you would rightfully think less of me as a person for it. My personal experience is not more significant than yours, and does not warrant sharing.<br />
<br />
At the same time, that personal experience is all I have. I remember moments from it constantly despite having almost never documented them and almost never told any of them to anyone including my closest family, friends, and colleagues. I channel those moments in the games I work on, channel them so much and so consciously like you wouldn't believe, and you'd never know it because none of the games I've ever worked on seem to have anything to do with me. The key for me is that I keep it to myself. The only way I can make my work personal is to keep private what's personal about it. We relinquish so much privacy these days that I think there is a sense of strength to be gained from consciously holding onto some, only ever hinting at it. Put another way, the less you know about me, the more interesting I am, the more interesting my stories. This of course is not true of everyone. There is no formula, and this is not advice.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com2tag:blogger.com,1999:blog-6082533239875181337.post-69512779235693675652013-09-21T14:46:00.001-07:002013-09-21T15:01:52.510-07:00The Stitching ProcessWouldn't it be nice if all games formed around some strong, clear, inspired thematic core -- a Vision, with a capital V! -- and the great ideas kept sprouting from that seed. I think there's a misconception among some game players that games are made this way. I think they rarely are, not even the good ones.<br />
<br />
Game development feels more to me like an archeological dig where all you've got to go on is a hunch. You start digging and maybe you find something, but you probably won't, not at first. You start to second-guess what it is you're even looking for. Maybe you find something exciting along the way, but it's only exciting to you, and you're part of a team looking for something else. Maybe you're hell bent on finding this one specific thing to the detriment of other valuable discoveries along the way. In time, what you find down there probably isn't as perfect as the image you had in your head, but it's something.<br />
<br />
Games, I think, are often put together from a bunch of dusty old pieces, not all of which fit. You probably find too many pieces in your search. Apart from all the skill and craft involved in unearthing the pieces without ruining them, there is art in identifying which pieces are the ones that can form a whole, and in connecting them with care.<br />
<br />
Part of the reason an archaeological analogy works for me is I don't believe in new ideas. Everything has been done, done well, better than I (at least) could ever do it. Thankfully, though, memories are short and tastes change with time. Synthesize some good old ideas at the right time and people call you original. The paradox is that in uncovering old things, you discover new things.<br />
<br />
When I work on a game I always think I know what I'm looking for. Accepting that what I'm looking for may not be the right thing, may not be what we find, may not even be what we end up looking for, is a nonstop process.<br />
<br />
In time, if you're lucky, you get to the point where you've unearthed most of the pieces and what remains is putting them together. Finally, you're getting somewhere. The work is cut out and just needs to get done. But it's here, relatively late in development, when some of the most important creative decisions get made, through synthesis, through omission, and through connection.<br />
<br />
To convolute my archeological analogy: You're not just unearthing something, you're not just piecing it together. You're bringing it to life. It's a Frankenstein's Monster type of process. So then, once the pieces are splayed out, there's still a need for some good stitching to tie it all together into something recognizable as a distinct entity, preferably one that isn't an abomination but rather something that seems like it ought to belong in this world.<br />
<br />
I find that writing provides one of the lowest-cost, highest-efficiency forms of stitching together disparate game elements.<br />
<br />
In a simple mathematical model, you can form a line between any two points in space. In real-world situations, writing I think is the key to linking any two otherwise-unrelated things. I practiced this in college. Taking English lit classes, I faced the same challenge as every other student: What could I possibly say about this book that my professor (rather, the teacher's assistant) hadn't heard before a thousand times? A solution I eventually discovered consists of three steps:<br />
<br />
<ol>
<li>Open assigned reading to one page at random, and note the first passage that catches your eye.</li>
<li>Open assigned reading to another page at random, and note the next such passage.</li>
<li>Write essay arguing there exists a meaningful connection between those two passages.</li>
</ol>
<br />
I tried this several times as an experiment when I was concerned that I had no original ideas about what to write. I felt cynical and like a total hack when I did it, all the more so when the work inevitably yielded better grades than essays I put a lot more thought and effort into. But then I thought about it more.<br />
<br />
Meaning does not inherently exist. Meaning is manufactured, produced, contrived, any number of ugly words. There are nicer words. Meaning is felt, experienced, inferred. But deep down at the heart of it that shit is made up. Fiction. Narrative. In the case of media, the meaning of a work may initially be created by the author, but in the end it is shaped by the audience. As audiences, we have a strong capacity to sense when a work is cohesive and when a meaning can be found in it, and we like to experience that discovery through passive participation in the work if not through active exploration. Our brains do their pattern-matching thing and we take pleasure from finding hidden connections, from realizing the greater scheme of the work, the grander more intricate design. Meaningful work is impressive work.<br />
<br />
So to tie this back to game development: To me it is often not sufficient for a game mechanic to be fun or interesting in itself. It needs to be meaningful somehow -- I want to be able to find meaning in it, to connect it to some aspect of my own life experience (or someone else's), to see why it exists as an abstraction of some deeper truth, and to really understand why it's part of the game I'm playing. And so, when dealing with a bunch of disparate mechanics or ideas, all of which are no doubt cool yet not all of which are cohesively connected or inherently meaningful, I believe there's still a chance to integrate them meaningfully -- to stitch them together -- using words, if only as a starting point.<br />
<br />
To give you an example from <b>Bastion</b>, that game has a system called the Shrine, in which you can modify the game difficulty to suit your preference. This system was not the Shrine until rather late in development (for a long time it was the Bestiary) but the underlying idea was always that we wanted a difficulty system that didn't put a blind choice before the player at the start of the game, and instead let you tune the game's challenge in a granular way, beyond the opaque and judgmental easy/normal/hard choice given by many games. So, after much wracking of minds, from a writing perspective we found that a promising angle on it was to structure it around religion. After all, the difficulty effects were global, somewhat magical, and somewhat strange. To engage with our difficulty system was to test one's faith in one's abilities, so a religious metaphor just made sense. What's more, it served to deepen an aspect of the world's backstory (involving a cultural dispute between neighboring nations), which in turn deepened the plot.<br />
<br />
I think everyone on the team was happy with how this system came together, and it's one of the best specific examples we have to show for when our collaborative process goes well. More personally, I like what the Shrine system did for the game, and not just mechanically. I like how we were able to make it fit. And I appreciate that, if not for the Shrine system, Bastion would not have broached the subject of religion at all, which I know was a meaningful part of the game for some people (at least some of whom have written to me or talked to me about it). The desire to include a difficulty system created an opportunity to instill meaning into the system, by stitching it onto the rest of the game.<br />
<br />
<center>
* * *</center>
<br />
You're probably familiar with the term "to retcon". It's a pejorative term, frowned on by audiences, referring to the act of retroactively creating continuity where none existed. We see retconning as a sort of public embarrassment, a collapse of the fourth fall, as with the infamous midichlorians example from the <i>Star Wars</i> prequel. However, much like how I came to accept that my college English tactics were effective, I've come to accept retconning as an important part of game development. As much as I'd love for all meaning in a work to flourish from some pure and artful place, from some never-changing point of origin, I'll take it where I can get it. That means always searching for opportunities to create continuity where none exists, or strengthen continuity where a hint of it is detected if only by coincidence.<br />
<br />
Ideally all this is done behind a curtain, so that when the finished work is presented, it feels like it has Vision. There is no hint of retconning from the audience's point of view, and indeed, no retconning could have possibly occurred with Vision such as this! So, I'm all about retconning, because I want everything to fit and that's only possible once all the pieces are there, late in development. Retconning is a way of executing on ideas, and early on in a project when all you have are ideas, they can be more frustrating than anything else. All throughout development I like looking for those vestigial little pieces of game, whether it's a conspicuous art asset or a design contrivance or a limitation of the engine or a story trope or anything really, and I'll try to connect them to the game's center of gravity, so that in the end, the finished work gives the impression that it knew what it wanted to be all along.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com3tag:blogger.com,1999:blog-6082533239875181337.post-7667143616000335352013-02-02T20:56:00.003-08:002013-02-02T21:12:01.760-08:00Discovery and MasteryIt's been more than a year since I posted here. Here are some of the reasons:<br />
- I was busy<br />
- I was lazy<br />
- I was between projects<br />
- I was playing a lot of <b>Dota 2</b> in my spare time (see above)<br />
- The more time went by the more I felt I needed to say something profound if I posted again<br />
<br />
Two things have changed:<br />
- I'm playing less Dota 2 as too many other games need playing<br />
- My guilt at neglecting this space superseded the imperative to say something profound<br />
<br />
So here we are.<br />
<br />
Exposition is something I feel I've talked about a lot because, if you look past its colloquial definition as "the part of a story where plot details are explained", it's a lens through which you can look at the entire start-to-finish structure of a game.<br />
<br />
Exposition is a tool used for reconciling the mechanical, systemic, and narrative components of a game, as it's the method through which these components may be sequenced in some interesting, appropriate fashion for the player.<br />
<br />
When used properly, exposition creates motivation in the player. Interesting details expose themselves, raising questions about other interesting details, creating for the player an unspoken promise that the revelations will continue. One way of looking at the game designer's responsibility is, he or she must extend this expository sequence for as long as appropriate and no longer. The result is a game that is engaging from start to finish and leaves the player with a sense of satisfaction at the end.<br />
<div>
<br /></div>
<div>
All games are played to the point at which the player loses interest. An ending is just an invitation for the player to lose interest at what's likely an appropriate time.</div>
<div>
<br />
Not all games need to be finite and it seems to me the vast majority are not. If a game is to be endless for some reason then I think it's important for the player's sense of mastery over the game to also feel unreachable. If it could be measured over time, mastery ought to look like the geometric concept of an asymptote – it should be possible to approach mastery, but never quite reach it. The reason I played Dota 2 all last year, the reason I played fighting games for years and years, is because they do this.<br />
<br />
Mastery is not the goal of all games. Some games are experiential, contemplative. They don't offer challenge in a traditional sense. I admire games that do this well, such as the recently released <b>Proteus </b>or last year's <b>Journey</b>. These games tend to focus on creating a sense of discovery. In the absence of mechanical complexity or challenges, they need to compel the player through some other thing, through discovering the limits of the world or discovering interesting intersections between different game systems. Even <b>The Walking Dead</b> is a form of this – it's about the emotional experience of making difficult moral decisions and moving forward with the consequences of those decisions.<br />
<br />
So then: either a game compels its player to fully master it, or fully discover it, or possibly both. My absolute favorite games, and the kinds of games I want to work on, do both.<br />
<br />
From a certain point of view the terms are somewhat interchangeable. When I feel as though I've seen everything there is to see in Proteus, it could be said that I've "mastered" the game. When I feel I've reached the limits of my reflexes and mental capacity playing Dota 2, when I think I know all there is to know about it even though I may be wrong, I think I've "discovered" everything there is to discover about Dota 2.<br />
<br />
That said, I think "mastery" tends to be applied to mechanical and goal-oriented aspects of play, to competitive games or games with goals and challenges, while "discovery" tends to be applied to experiential, narrative aspects. Going forward I will use these terms to denote these respective meanings.<br />
<br />
I think it's fair to think that if a player fully masters a game before it's finished then the player is more likely to get bored and quit if that mastery occurs before the game has ended, if it has an ending.<br />
<br />
A player may also quit early if the gap between overcoming the challenges at stake exceeds his or her curiosity at what lies beyond those challenges.</div>
<div>
<br />
In such cases there is no real exposition left in the mechanics or systems. The player "gets it" and there's nothing left to learn. Maybe the game should have ended before the player reached this point, or more likely, the mechanics and systems themselves were underdeveloped in some way or the game wasn't tuned appropriately and the player was unable to find sufficient challenge there.<br />
<br />
I think depth is secretly desired by everyone who plays games no matter their interest level, because depth and engagement are very closely linked.<br />
<br />
Say a player has become bored of a game's mechanics and systems, having seen all there is to see, or at least believing this to be the case. One way the player may remain engaged in spite of this failure on the game's part is through the narrative. To me this is the main reason narrative belongs in games, as a sort of safety net for the gameplay, because it's very difficult for gameplay to be perfectly tuned and engaging for all players at all times. When the gameplay falters at its job, the narrative can be there to compel the player onward: "Well I just want to see what happens next."<br />
<br />
The narrative of course also can fail, just as easily and just as hard as the gameplay.<br />
<br />
This is why thinking of a game's structure as a single expository track I think is useful. Concepts of all kinds can be separated and ordered, ensuring that something interesting continually happens on some recurring yet slightly unpredictable interval. Applied properly, this method can be used to create a strong sense of discovery from start to finish and leave the player satisfied yet wanting more, because the experience was a good one. <b>Dark Souls</b> and its predecessor <b>Demon's Souls</b> are good examples of this. Those games are one big enigma, maddening intricate puzzles begging to be cracked.<br />
<br />
Exposition is its own worst enemy. The stigma that comes with the term comes from how often exposition is abused. Exposition can be abused in mechanics, systems, and narrative. Often this abuse occurs as the consequence of didactic design or on-the-nose writing.<br />
<br />
When a game explicitly tries to teach you everything about how to play it, through forced or heavy-handed tutorials and other interruptions, it is denying you the opportunity to discover what's interesting about the play experience on your own. Ever play a game and think "just let me play" when it's all cutscenes and pop-ups reiterating over and over? The game is being condescending to you and wasting your time. It's a disappointing feeling.<br />
<br />
It would be nice if all games were fully discoverable. At least when it comes to today's console and PC games and their dozens of possible inputs, that simply isn't possible sometimes, and some amount of teaching is necessary. Following the rules of appropriate exposition, the best way to teach is to teach as quickly and concisely as possible, and teach only those things fundamental to the player's ability to make progress, at the time when those things must be understood. No sooner, no later. Getting this right is hard.<br />
<br />
Knowing that teaching and discovery stand in direct opposition, and that discovery is a much more desirable sensation than "being taught something", can be useful as a means of forcing yourself to reduce teaching to an absolute minimum and leave as much as possible to the player.<br />
<br />
The last point I want to make here is that when you think of exposition holistically, as the player's path through the entire experience, then you discover opportunities for using exposition in interesting, unconventional ways.<br />
<br />
Maybe when there's a bit of necessary teaching to be done, you figure out a way to give it narrative context, as with <b>World of Goo</b>'s excellent Sign Painter signs – tutorials written from the perspective of a mysterious character.</div>
<div>
<br />
Maybe there's a really interesting but advanced play mechanic you're dying for the player to know about. Rather than just spell it out in a forced tutorial where the mechanic is plainly shown but can't really be appreciated, maybe you can provide more situations in which that mechanic stands a chance of being discovered naturally, thus providing the player the satisfaction of having figured it out.<br />
<br />
We live in a time when achieving a sense of discovery or mastery seems virtually impossible. Our personal accomplishments are inconsequential in comparison to those of many other people who have worked much harder for much longer to achieve similar things a long time ago. Our discovery of things is often coupled with a sense of ignorance at having not discovered them sooner. The best some people can hope for in these regards is writing "first" on a comment thread on a news story on the Internet – that's the modern-day equivalent of a frontier. As such, I and many others look to games to provide us with some of these feelings. Games might as well do the job.</div>
Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com5tag:blogger.com,1999:blog-6082533239875181337.post-67242013462727315942011-12-31T22:38:00.000-08:002013-02-02T08:56:36.068-08:00Developing Themes in GamesI don't know how people come up with their stories but I can tell you how I come up with mine. I don't start with scenes or characters or settings or genres. I start with a tone and a theme, because those two things provide the guiding light as I try and uncover everything else.<br />
<br />
When applied responsibly, a theme can give a work of fiction its center of gravity, and can make the experience feel meaningful and open to interpretation in a pleasing or thought-provoking way. When applied irresponsibly, a theme can make a work of fiction feel condescending or didactic, like you got tricked into taking a call from a telemarketer.<br />
<br />
A theme ought to be omnipresent but subtle. If the audience can identify the theme easily then it's too over-the-top. If there's unanimous consensus about the theme then it's also over-the-top. A theme is like the body language of the work. It should give a strong impression to those paying close attention while operating on a subconscious level in most cases.<br />
<br />
A theme is not a moral. It's an open question, not a conclusion. It needs to be an open question because an entire work of fiction needs to be created in its service. In thinking about new stories, I like to think of themes in a journalistic way. My responsibility as the writer is to fully explore a given theme, to provide the audience with a wide breadth of relevant information which can be used to draw various conclusions.<br />
<br />
The tone of the work may inform the theme, or vice versa. The combination of the two create the identity of the work, a subject I'll explore in more detail in <a href="http://www.gdconf.com/conference/design.html">my upcoming GDC 2012 talk</a> about creating atmosphere in games. (EDIT: The slides for this talk are <a href="http://dl.dropbox.com/u/10130879/Kasavin_Greg_CreatingAtmosphere.pptx">available here</a>.)<br />
<br />
The story I wanted to write for <b>Bastion </b>was intended to explore the theme of overcoming regret. The tone I wanted for it was bittersweet but not sentimental, cautiously optimistic and ultimately hopeful but still melancholy at times, something that felt real rather than sappy but still could be suitable for almost all ages. The characters, events, places, and various little details all came about in support of these ideas. The theme ended up serving as my map. The tone served as the directions from the starting point on that map to the end point. I knew the starting point and end point early on. Plotting the course is what took the longest amount of time, mainly because I didn't write any in-game content before we had playable levels that needed to be written.<br />
<br />
I don't like spelling out the theme like this but the game's been out long enough, and besides, it's a broad enough theme to where spelling it out doesn't really matter. The theme in and of itself is too broad to be susceptible to judgment. I think that's the mark of a theme worth exploring.<br />
<br />
You'll notice that the theme I chose is simply "overcoming regret", just two words, as opposed to something like "in life we all need to learn how to let go." One is a theme, the other is asinine. Because I'm not Aesop, I will never, so long as I'm blessed with the opportunity to continue to create games, ever inflict my morals on you. I have my kids for that. Besides, if the theme I chose could be reduced to a fortune cookie sentiment then it isn't strong enough to bear the weight of a story worth telling.<br />
<br />
The theme of a game's story ought to be the theme of the entire work, or vice versa, however it all comes together. If a game's story has a theme that's not supported by the play experience itself, the game threatens to feel disjointed and leave a sour taste with the player. In Bastion's case, the game was always going to be about building the world around you, an aesthetic idea and a design idea that naturally extended to a theme. The idea of building gave rise to the idea of rebuilding, which gave rise to the idea of overcoming regret and this post-disaster story about a few survivors (and other creatures) dealing with what happened in their own way.<br />
<br />
All of the different game systems ideally should support the theme. With this in mind, in Bastion we tried to solve for some problems that can induce a sense of regret in other role-playing games, such as when you get the sinking feeling that you chose poorly when developing your character. In many RPGs, you're asked to make half-blind choices about character class or perks and stats. Halfway through the game you find yourself wishing that you chose differently. This can create incentive to replay the game but it can come from a negative place. In Bastion, we offer the player complete freedom to customize their character all the way through. Our difficulty system, via the Shrine, works in a similar way. We don't make you choose the game's difficulty before you've had a chance to play it and get a feel for it.<br />
<br />
There are other smaller examples. When you run out of health and get defeated, you have the opportunity to "carry on", get back up at least one time and keep fighting. It's just a system of extra lives, superficially no different from the convention used by countless old games, but in Bastion I think it takes on a different connotation for some players as they see the protagonist character struggling through one situation after another.<br />
<br />
Then, when we present players with the game's climactic, expressive choices, those are the only moments where there's no turning back. I think this is self-evident in the choices themselves, and thankfully we got a lot of good feedback from players saying they gave pause in those situations for quite a while, deciding what to do. I'd like to think that almost everybody who reaches those moments in the game ultimately makes a firm decision, not the wishy-washy I-don't-know kind but the kind that feels satisfying and cathartic even if not exactly good.<br />
<br />
So, why would I want to write a story about an unpleasant subject like regret anyway, especially for a game that seems to have the trappings of a hack-and-slash action RPG romp? One reason is because I don't want to waste people's time with meaningless game experiences. Another reason is that this theme is important to me for a bunch of reasons I could only articulate through the story itself. I think regret is a universal feeling experienced by almost everyone from a young age. The depths of that regret vary from one individual to the next in a profound way, but on some level there is a shared experience, even among those who've suffered no real losses, who've had it pretty good overall. Me, I'm the sort of person who's spent (or wasted, depending on how you look at it) a lot of time re-playing various scenes from my life in my head, wondering about alternative outcomes. This is typical but I think I have an acute case of it. Setting aside whether it's healthy or not, I accept that it's a part of me, and it's the reason Bastion's story is what it is.<br />
<br />
Thanks for reading, and may things turn out all right for all of us in the new year.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com6tag:blogger.com,1999:blog-6082533239875181337.post-16087630467154643722011-08-22T23:56:00.000-07:002011-08-23T00:21:24.925-07:00Unveiling the Possibility SpaceRevealing the scope of a game should be, I think, a seductive act by the game for the player. Not that I know anything about seduction, but I think I've seen it done properly in movies at least, and read a thing or two about it. Seduction means leaving a lot to the imagination while drip-feeding reality in tantalizing doses. There is a sexuality there usually but it doesn't need to be there. A car can be seductive. So can a game. Even an E-rated game, get your mind out of the gutter.<br />
<br />
The game I've been working on is now out there, most of the reviews are in, the first-week sales have happened, all that. I can talk about it freely, though if you haven't played it yet, please don't read on unless you're OK with having aspects of it spoiled. Thankfully the game got a generally good response from players, and I'd like to talk here about one of the major reasons why I think it worked for those people. Sure, we worked to craft the discrete elements of the game to a good level of quality, everything from the tuning of the game systems to the art and music and writing and so forth. But I think the essential structure of <strong>Bastion</strong> is very important to its potential to have an impact on the player.<br />
<br />
We said during development that we wanted for the game to present to the player an ever-growing series of gameplay-expanding choices. Part of this involved keeping the player in the dark about the extents of the scope of those choices, culminating in a series of climactic narrative choices designed to feed back on the entirety of the player's experience up to that point. We had to not only continue introducing new elements of play from beginning to end, we also had to do it at slightly irregular intervals such that the structure itself resisted becoming predictable in a negative way. The desired effect is for the player to feel a sense of wonder and intrigue. When you fully understand something, you cannot wonder about it or feel intrigued by it any longer.<br />
<br />
Concluding the game with a pair of purely expressive choices, whose gameplay impact was implicit but not overt, was to me the ultimate way of subverting – in a hopefully interesting way – all the gameplay choices that had come before. Up until that point, you'd been deciding what to build, which Spirits to drink, which weapons to use, which upgrades to buy, whether to invoke any of the Shrine idols, and so on. Hopefully, then, the last thing you'd come to expect at the end of the game – especially in a game that appeared to be driving toward one specific outcome – is to have to make an expressive choice about what to do with the world you've been playing in. It's a world you've either grown attached to or haven't grown attached to, and the choices at stake are meant to encompass that entire range of experience.<br />
<br />
Bastion is built on this idea of the gameworld slowly unraveling. Every aspect of it. The world unravels almost literally. The story unravels. The game systems come online one by one. There's no telling how many game systems there are in total when you begin play, and in fact, we deliberately mislead you several times about the extent of the game's scope. We make you think you're almost done with the story after several hours, then we introduce another system around upgrading. And when you're almost done with that, we introduce the endgame act. Only when you're about to reach the endgame do we explicitly tell you that, yes, you're about to go into the final area. But even there, the final area is substantially larger than previous areas and has several new kinds of gameplay beats in store. To top it off, once you've finished the game, then we unlock a whole second play-through with more new content. We structured the game this way to keep the experience feeling fresh within the constraints of our scope.<br />
<br />
While I think this type of slow-and-steady-burn worked for us, I'm not about to suggest it's beyond reproach. A game needs to prove to its player as quickly as possible why it's worth playing. One way to go about this is to reveal great depth straightaway, such as by rapidly exposing complex game systems. A classic example of this is the character creation screen in a role-playing game. In <strong>Icewind Dale</strong>, an excellent old computer RPG, I spent probably a good two hours just making my party of characters before ever beginning play. The character creation system was just so rich with possibility. These days I think it's more fashionable to keep stuff hidden and not scare away the player with too much information up front. That's fine, but finding the right pace at which to reveal new elements of play becomes all the more important in those cases. I'm not sure that proper pacing can be taught, because it's resistant by its own nature to being reduced to a formula.<br />
<br />
So then, if you're a game, keeping some of your best ideas hidden away for your later stages is arguably a risky proposition. In fact, by doing so you are implicitly accepting that some probably rather large percentage of your players will never see that content. In Bastion's case, we invested heavily in the ending, by scheduling a bunch of time for a bunch of unscheduled stuff, because we wanted to do everything possible to make sure players who finished the game felt rewarded for their time and effort. From a clinical production perspective maybe this was a bad decision. One could argue that we should have disproportionately focused on only the early levels in this fashion, because more players would see them. The reason this mindset is wrong, to me, is because it ignores who the game's audience really is.<br />
<br />
Say you're an author writing a novel. The idea that you'd short-change the ending because not many readers would get that far is deplorable. You need to have faith that your readers will get there, ought to be focused on providing every reason for them to get there. Then you save the best for last for these people, because you owe them. They're the ones you're writing for. As for the ones who don't make it, sure it's probably your fault they gave up, but you can't just go in assuming they won't stay interested because that would make you a hack.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com5tag:blogger.com,1999:blog-6082533239875181337.post-64566840725179374962011-06-26T21:18:00.000-07:002011-06-26T21:33:54.814-07:00Power Fantasies and Their ProblemsFor a short time in college I considered enlisting in the military but you have to understand my mind was in a very dark place then. I got over it, though I still find shooters and military-themed games fascinating. What boggles my mind, though, is how wrong most of them are about why I want to play them. It's as if they think I think being a soldier is this thrilling and glorious experience. At least <strong>Modern Warfare</strong> got it right when it killed me in a nuclear blast.<br />
<br />
This isn't one of those complaints about there being too many shooters, though. Instead I bring up shooters to make an observation about games that are power fantasies, and some of the problems inherent to that style of play.<br />
<br />
For the most part, a power fantasy is what it sounds like. It's the idea that if only you were a better more capable person. Games allow us to play as characters with abilities far superior to our own. <strong>God of War</strong>, <strong>Halo</strong>, <strong>Ninja Gaiden</strong>, <strong>Gears of War</strong>, <strong>Batman: Arkham Asylum</strong>, <strong>Devil May Cry</strong>, <strong>Assassin's Creed</strong>, <strong>Mass Effect</strong>, and <strong>The Witcher</strong> are all examples of power fantasies in games. Such games naturally fall into the action adventure, shooter, and role-playing genres, because power fantasies tend to revolve around dominating one's opponents, and these genres revolve around combat.<br />
<br />
<strong>Identifying a Power-Fantasy Game: Themes vs. Systems</strong><br />
I think power-fantasy games are characterized at least as much by their thematic and fictional content as by their gameplay systems and player interactions. For example, take the old laserdisc arcade game <a href="http://www.youtube.com/watch?v=HuQ8vhK_-Jg"><strong>Space Ace</strong></a>, which is by all means a power fantasy about being a sci-fi action hero. The gameplay itself consists of reflexive button presses and memorization. Just dial in the proper button sequence, and you get to watch a cool cartoon unfold. Games like this are where quick-time events came from. The same format could just as soon be used for a game based on <em>Schindler's List</em>. So then you'd have two games with identical gameplay, but only one would be seen as a power fantasy. Not sure what people would make of the other.<br />
<br />
<strong>Spy Party</strong> designer Chris Hecker offers <a href="http://chrishecker.com/Power_Fantasy">a succinct argument against power fantasies</a> on his blog that got me thinking about this themes-vs.-systems distinction. In <strong>Bastion</strong>, the game I've been working on, I wanted to avoid creating the tone of a power fantasy. For example, the protagonist character is someone the player is intended to feel for rather than envy. On the other hand, aspects of Bastion's game systems can be likened to those found in power-fantasy games -- it's a combat-oriented game in the action role-playing genre. Does that mean it's a power fantasy in spite of my intentions? Of course not. The narrative and thematic substance of a game sooner defines its character as being a power-fantasy or not, rather than the genre or the gameplay systems.<br />
<br />
To illustrate my point, take <strong>ICO</strong> and <strong>Shadow of the Colossus</strong>. These games<strong> </strong>revolve around conventional gameplay challenges, including relatively straightforward platforming and combat systems. You run, jump, and kill things in those games in a manner that's comparable to games like God of War or Assassin's Creed. However, I don't think many would consider ICO or Shadow of the Colossus to be power fantasies. The emotional content of those games gives the experience of overcoming their challenges a nuanced and contemplative feel.<br />
<br />
<strong>Problems With Power Fantasies</strong><br />
I don't want to make power-fantasy games for a variety of reasons that have little to do with how common they are. Rather, it's because I think power-fantasy games have three inherent, thorny problems I would like to avoid:<br />
<br />
<strong>Problem 1: Risk of creating emotional disconnect or sense of inadequacy in the player</strong><br />
In the typical power-fantasy game, the player's skills will initially not be aligned with those of his character. You're controlling a character who is far superior to you.<br />
<br />
This can make the crucial first experience with the game feel dissonant or off-putting. In <strong>Uncharted 2: Among Thieves</strong>, which I think is a stunning and well crafted game overall, if you don't know how to sneak around as well as Nathan Drake knows how to sneak around, then there's a good chance you'll get flustered in one of the opening sequences. There's no explaining why Nathan Drake is suddenly incompetent in what should be a routine mission -- immersion is broken and you're reminded that you're just a poor schlub playing Uncharted 2 and failing at it. In <strong>The Witcher 2</strong>, my favorite game so far this year, the outstanding exposition and beautiful world can likewise come grinding to a halt as soon as the actual gameplay starts and you realize just how lethal the world of the game really is, and how lousy of a swordsman you are in spite of how proficient your character is supposed to be. You lose empathy for your character because you never experience having to go through what he went through in order to be good at his job.<br />
<br />
Some games get around this type of problem through smart use of exposition or flashbacks. I thought the first hour of <strong>Assassin's Creed 2</strong> wasn't as exciting as the rest of the game but at least it let you work your way up to earning the ninja-like skills of the protagonist. Most of the time, though, if a game is inviting you to be the badass then it's going to have an awkward learning curve, either nakedly easy or too hard.<br />
<br />
<strong>Problem 2: Design limitations of an inherently powerful protagonist</strong><br />
If you're playing a game in which your character is very powerful and versatile, then not only is the game going to be harder to learn than it probably needs to be, with tons of front-loaded tutorial, it also won't leave much room for growth. Or it'll be some kind of nongame where you give minimal input, like Space Ace. Ironically, all this undermines the basic appeal of a power fantasy, which is to have a growing sense of superiority.<br />
<br />
In <strong>Grand Theft Auto IV</strong> or almost any of the games derived from that series' template, you start with the power to wreak all kinds of havoc inside that sandbox world. You might work your way up to faster cars and deadlier guns than what you have access to right from the start, but in spite of the open-world scope, the sense of character progression is naturally limited. This is especially true of games set in the real world. In games like God of War, you start off extremely powerful but there's still a sense of progression as you move from superhuman to godlike powers. But in a military shooter, where you're a man with a gun, you don't expect to gain new abilities, and in 99 out of 100 such games, you don't. Realism.<br />
<br />
Role-playing games have a traditional solution to these problems, by making the player start off as a nobody and gradually letting him grow his powers while his notoriety in the gameworld grows through the fiction. Even still, RPGs are notorious for their complexity, often front-loading far more game systems than the player ought to be concerned with at first. And most RPGs still are power fantasies from a fictional point of view.<br />
<br />
If you're not making a power-fantasy game then you have far more latitude when defining your protagonist character. The player doesn't always want to be the badass, does he?<br />
<br />
<strong>Problem 3: Limited emotional range</strong><br />
When a game is a power fantasy then it occupies a narrow and limiting emotional range. Power-fantasy games can be about justice, revenge... and, that's about it.<br />
<br />
Look at the long list of games I've cited above and try and point to ones that aren't about justice or revenge.<br />
<br />
Justice and revenge are age-old themes, deeply ingrained in human nature. The emotional range associated with these, I'd say, tends toward the aggressive and the negative. Some of the best works of fiction in the history of fiction have concerned justice or revenge. But these themes aren't everything.<br />
<br />
Of course there's a whole slew of other themes and corresponding emotions that games can explore. It's an oversimplification but ICO and Shadow of the Colossus are games about love more so than they are about justice or revenge. By successfully applying an alternate thematic spin on conventional action adventure tropes, these games stood out as unique and provided unique and memorable experiences.<br />
<br />
<div style="text-align: center;">. . .</div><br />
Power-fantasy games have a lot of things going for them. That's why so many of them are made. Games that attempt to solve the problems I've listed here have plenty of their own problems, including, I suppose, having a potentially more-limited appeal than power-fantasy games do. Even still, when thinking about the kinds of games I want to make, I'd much rather take my chances with exploring relatively untapped thematic territory than trying to attack head-on some hundreds of different games I hold in very high regard. I've tried that before and didn't like it as much.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com10tag:blogger.com,1999:blog-6082533239875181337.post-3855073213582782452011-05-10T20:47:00.000-07:002011-05-10T21:25:41.257-07:00One Thing at a TimeHey, I'm back. My writing work for <strong><a href="http://www.buildthebastion.com/">Bastion</a> </strong>is complete and the game is nearly finished. How well it finally turned out will be for the public to decide, though what I can say is that it's very much the game I wanted it to be. Everyone on the team is feeling good about where we ended up. Now that I have a bit of hindsight on the process, I'd like to comment on three principles that helped me construct the narrative. There won't be any story spoilers here, but approach with caution anyway if you're looking to play the game with no preconceptions.<br />
<br />
It was important to me that Bastion have a rich and interesting story for the sake of players who (like me) care about story, while at the same time making concessions for players who don't care about story. This was not a matter of trying to make everyone happy. It was a matter of trying to create a good story for a game, by approaching it from the perspective of "no one cares about your stupid story," which I feel should be the baseline assumption if you're not a famous author or working with a famous property. People really cared about what the story was going to be in <strong>The Matrix Reloaded</strong>, but they had no expectations for the story in the original <strong>Matrix </strong>film. The original Matrix needed to work hard to get people to care, which is part of the reason why it's so much better than its sequels. In games, people are liable to care even less about story since there's a lot more to a game than its story.<br />
<br />
This "assume no one cares" approach was manifest in several principles that I tried to stick to, which I'll explain in more detail below. They are:<br />
<ol><li><strong>Structure the story around a clear, consistent goal</strong>.</li>
<li><strong>Avoid attempts to engage the player about things not happening onscreen in that moment</strong>.</li>
<li><strong>Suggest the emotional range of the story early on</strong>.</li>
</ol>Let me explain each of these a bit.<br />
<br />
<strong>Goal-driven story</strong>: An interesting story often is a complex or nuanced story. I wanted to strike a good balance with Bastion's story and layer the complexity so that it's there for people who care to see it, while the surface story remains simple and clear. Players have a lot they need to keep track of – not just story but also the game's systems and mechanics, which are in constant demand of attention. I didn't want the story to feel indulgent or like a comprehension test. I'm sure you've played games where you lose track of what's happening in the story and never get on board again. One such game happens to be my favorite game so far this year, called <strong>Tactics Ogre: Let Us Cling Together </strong>for the PSP. It's a beautiful and complicated game, with a huge cast of characters and an elaborate plot, but as engaged in it as I am, I have trouble keeping all of the factions and political maneuverings straight. I'm approaching the end of the game now and couldn't summarize the details of the story to save my life. I still enjoy it a lot for its tone and world but I wish key parts of it were presented more clearly.<br />
<br />
One of the ways in which Bastion's story is kept simple is that the cast of characters is not enormous, and the player goal is specific and persistent. I used to work on real-time strategy games, where each mission tended to have unique objectives, sometimes multiple objectives. I also used to play a lot of massively multiplayer games, whose quests tended to have their own fictional conceits. I found in both cases that many players of these games tended to tune out the story reasons for these missions or quests and just wanted the game to "bottom-line" what needed to be done. This wasn't because they were lazy, and wasn't even necessarily because the stories of these games were bad. It just got difficult to keep a complicated story straight while also having to parse new gameplay objectives.<br />
<br />
Maintaining a constant "object of desire" for the player to pursue doesn't have to over-simplify the story of a game. Instead I think it can create a strong framework on which to layer a rich narrative. One of my favorite examples is the original <strong>Metal Gear Solid</strong>, which has the best story of all the games in that series. The plot, on the surface, is simple: Solid Snake, a secret agent, must infiltrate a military complex in order to rescue the head of a weapons research firm and discover whether the terrorists occupying the complex have nuclear capability.<br />
<br />
That's it. It sounds like a totally straightforward premise for a spy thriller. But if you've played Metal Gear Solid, then you know the story takes an almost ridiculous number of unexpected turns. What helps drive you forward as you face off against cyborg ninjas, one-handed pistol-wielding sadists, and minigun-wielding tank-driving shamans? The goal remains the same. No matter what insane situation you're in, you're still after the same thing, and the game's briefer characters do a good job of reminding you of this.<br />
<br />
<strong>God of War </strong>is another one of my favorite examples. You're trying to kill the God of War. The story has much more to it than that, but you don't have the moment in God of War where you wonder, "Wait, what am I even supposed to be doing?" Unless you're stuck on a puzzle, but that's a subject for another day.<br />
<br />
<strong>Immediacy in storytelling</strong>: One of the reasons exposition has such a bad reputation is that it's often used to describe things that are disconnected from the matter at hand. You end up feeling like you're waiting for the story to get out of the way. Yes, Star Wars has license to open with a text crawl explaining what's happening in the world. This type of technique is best avoided in most cases, yet games do the equivalent of it all the time. Characters have long conversations about characters who aren't there. Cutscenes tell you why you should care instead of letting the gameplay make you care. You're given mission briefings about how important certain things are and how you must not let this or that happen. It's all just talk. None of this has an impact on you, and you see right through it, especially when you're playing a massively multiplayer game and you know it's just window dressing for another bit of quest loot.<br />
<br />
To avoid this problem, story in games should concern things that matter to the player, rather than matter to the story. In <strong>Halo</strong>, you crash-land on the Halo and need to find a way out before you're hunted down and killed. Though there's a backstory around trying to defeat the Covenant and save the Earth, none of that matters to you in the original Halo, and besides, these are things that no human being can relate to. In Halo, you're just trying to get out of a bad situation. <strong>BioShock </strong>is set up in much the same way. <strong>Out of this World </strong>and <strong>LIMBO </strong>are<strong> </strong>set up in much the same way. Being stranded in strange worlds not only makes you feel empathy for the protagonists of these games, it compels you to press forward and find a way out.<br />
<br />
In the case of Bastion, the story deliberately raises some key questions about the state of the world right from the beginning: Why is it shattered, why is the land reconstituting as you walk around, why are you being attacked by things called Squirts and Gasfellas, why is a narrator telling the story as you move through the game, and so on. Thanks to the game's narration technique, these questions come up right in the moment the issues begin to affect the player, rather than before they're of any concern or too long after. I don't tell you that there are strange creatures who want to hurt you before you face them. I don't tell you about the state of the land before you see how it looks for yourself. By not explaining away these things before the fact, I stand the best chance of piquing your curiosity and using exposition as it's meant to be used, rather than bombarding you with detail that's important to me as a writer but maybe not so important to you as a player.<br />
<br />
<strong>Revealing the emotional range of the story</strong>: This is an idea derived from Robert McKee's story seminar, in which he points out that it's a good practice for the author to show the emotional palette of his story early on. This may sound like terrible advice on the surface. What if you have some amazing plot twist all planned out, why would you want to give that away?? But this advice has no bearing on something like that. All it's saying is to avoid jarring emotional manipulation of the audience, not even for the audience's sake but for your own story's sake. To paraphrase McKee, if, for example, you have some sort of serious drama and then try to deliver some comic relief in the final act, what's likely to happen? The audience won't laugh – the story hasn't trained them to expect to laugh, and any attempts at humor will likely feel awkward and out of place. On the other hand, if there were humor in the story early on, later attempts at comic relief would be more likely to succeed.<br />
<br />
In other words, if the story gives evidence to the breadth of its emotional content early on, the audience will have an easier job of following along as the story unfolds. This does not need to come at a cost to the story's richness or complexity. One of my favorite movies, <strong>Fight Club</strong>, I think can't be accused of simplicity yet does a masterful job of defining its emotional palette quickly. The self-depracting humor and raw darkness of that story are all present from the start. The story moves into shocking and unexpected territory, but when you look back on it you realize that the groundwork was there. Maybe Fight Club isn't the best example of this since that third act really is crazy. Perfectly good examples are movies like <strong>Iron Man </strong>and the original <strong>Pirates of the Caribbean</strong>, each of which I think did a great job of creating a specific tone and sticking to it. Maintaining tone does not mean being monotonous if you have a rich tone.<br />
<br />
In Bastion, it was very important to me to establish the emotional palette of the story quickly, especially considering the story is delivered in large part through the use of voiceover narration. I needed to define the narrator's character in addition to defining the gameworld itself, and I do this using a range of emotional content that should ultimately feel consistent to the narrator and therefore to the game. If I did my job properly then you should get the impression that the narrator's telling of this story is important at least to him. You should quickly gain a sense for the depth of the character and, hopefully, find him intriguing enough to want to keep listening as well as keep playing. Each thing the narrator says near the beginning of the game is in service of informing you both about the state of the world and, indirectly, about what kind of man he is. And by virtue of that, you get a feel for the game as a whole, from its tone to its story themes. The narrator's character grows from there, and my responsibility from that point becomes fully delivering on this first impression.<br />
<br />
<div style="text-align: center;">. . .</div><br />
In conclusion, I kept in mind these three foundational techniques so that I stood the best chance of making Bastion's story something hopefully-worthwhile, without confusing players who just want to know what's going on and why they should care. I wanted to waste none of the player's time in coming to grips with what was interesting about the story. If I could do this well, I figured maybe the story would convert some of the players in the don't-care category into players who do.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com6tag:blogger.com,1999:blog-6082533239875181337.post-43134301881150744512011-03-24T02:12:00.000-07:002011-03-24T02:12:43.175-07:00Not Dead YetI've been working on Bastion all this year. I'm only taking a break now because I'm building a bunch more audio, but at this point we think we can see the light at the end of the tunnel. Our path is set and we've been in execution mode these past months. For me personally it's involved a good deal of level design work and a lot of writing. It's been the most rewarding work I've done since I got started working in the game industry.<br />
<br />
That said I don't want to say too much more about what I've been up to with the game since it's close to being finished and I don't want to give anything else away at this point. If people find the result of the work to be interesting then I'd love to talk more about the goals and process behind it after it's had a little time to settle.<br />
<br />
One thing's for sure -- the response the game's been getting based on the 20-minute prologue has been everything I could have hoped for and more. The game is a summation of many key elements and the integral contributions of each individual on the team, though given the narrative focus of this blog and my own focus on that work, it's been great seeing the positive reactions to how we approach story, exposition, and writing in games.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com6tag:blogger.com,1999:blog-6082533239875181337.post-46098723308707543792010-12-23T23:10:00.000-08:002010-12-23T23:43:03.030-08:00Death and GamesVideo games weren't always dominated by power fantasies. In fact I think the rise of the male wish-fulfillment Hollywood blockbuster of the 1980s, in movies like <em>Rambo II</em> and <em>Commando</em>, is what led video games down a similar path with stuff like <strong>Rush 'n Attack</strong> and, well, <strong>Commando</strong>. But even before this shift, games were still concerned with death, a trope that players young and old could always identify with. In <strong>Space Invaders</strong> you die. In <strong>Pac-Man</strong> you die. In <strong>Donkey Kong</strong> you die. In <strong>Pole Position</strong> you don't just lose the race, your shit fucking explodes and you die.<br />
<br />
The noted screenwriting instructor Robert McKee says that stories are a metaphor for life, when he explains why people are innately drawn to stories. I think games are a metaphor for life. This is the reason games don't need stories to be interesting, because in essence it's all the same.<br />
<br />
Many games are literal and so they depict death. The player fails by causing his player character to die in some fashion. Yet, for the vast majority of games, death is handled in a lazy, conventional fashion. It's strange when you think about it – something as serious as death, treated with such disregard as game death. What's the last game you played that handled death in an interesting way, that didn't act like the last 20 games you played by giving you a gameplay hint and respawing you at the last checkpoint? Death in games is nothing but a bit of inconvenience. Or when games neglect to put checkpoints close enough, it's a source of frustration, a poor design choice. It's almost never something profound, something complicated, something scary -- you know, like death.<br />
<br />
Most games don't even deliver on the promise of immortality. You have unlimited lives in military shooters just because whatever. Just like Afghanistan in real-life. <strong>Super Meat Boy</strong>, a ridiculous and funny and awesome game, has a more thoughtful approach to player death than virtually all the self-important AAA games this year by having a late-game cutscene where the villain gets frustrated by Meat Boy's propensity to keep respawning whenever he's killed. Meat Boy just kind of shrugs, almost apologetic for his immortality. He can't help being the way he is.<br />
<br />
Why should death even exist in games? Death used to exist in games because games needed a mechanism to punish failure. Today more and more games are becoming more and more lenient about failure, because they want more players and want to eliminate frustration and only keep pleasure. It's to the point at which failure becomes almost impossible in certain games, and yet as a player you're still expected to believe that your character is in mortal danger. What's the point?<br />
<br />
My main point is this: I think if a game is going to have death in it, then death in the game deserves careful consideration as part of the design. I am not OK with games thoughtlessly borrowing the auto-respawn-at-last-checkpoint design one after another. I want games to treat death with dignity, or disrespect, to make me fear it or laugh at it, to make me think about it or even want it, but I'm sick of games thinking it's something I don't care about as a player. If you don't think I care about it then don't put it in the game, or if you're going to put it in the game then do something interesting with it.<br />
<br />
Here is a short list of games that have done interesting things with death.<br />
<br />
- In the <strong>Fire Emblem</strong> series, which I love dearly, death comes swiftly and permanently. These are character-driven strategy games in a fantasy setting, but death isn't just an inconvenience in that setting as it is in most fantasy games. A character who dies in the game is gone forever after speaking his or her often-tragic dying words, and you'll be left to wonder how his or her story might have resolved. Players end up restarting entire missions to prevent character deaths, but at least it's a choice. Few games make me value staying alive quite like Fire Emblem. Other strategy games like X-COM and Jagged Alliance have done similar things, I just think Fire Emblem does it even better by building up its characters so well through its rich storytelling.<br />
<br />
- In the <strong>Soul Reaver</strong> series, you are the immortal vampire-wraith Raziel. Your body can be destroyed but not your spirit. When you "die" in the game, you sink into an alternate version of the world, a spirit realm filled with pathetic lost souls you must consume in order to regain your corporeal self. Some of the game's puzzles involved having to traverse both instances of the world to reach new places. Raziel is a tragic character who would like nothing better than to rest in piece, so the game subverts expectations around video game death on multiple levels.<br />
<br />
- In the arcade games <strong>Ninja Gaiden</strong> and <strong>Final Fight</strong>, both featured rather graphic "continue" screens showing your character bound and, respectively, about to be eviscerated by a spinning razor or blown to pieces by a bomb. You have 10 seconds to insert another coin to continue playing and prevent this fate. It was a cheap but effective play on the player's emotions. There was something base and manipulative about it, and for that reason I should hate it, but something about it was so playful that it worked well for these games. I'm sure it helped them earn a bunch more quarters, and as cheap emotional plays for player's time and money go, it was way cooler than FarmVille telling me to adopt a homeless orphaned crippled baby seal or whatever.<br />
<br />
- <strong>Braid</strong> is a game about what if you could move forward with the knowledge gained from failing while erasing the failure itself, so its handling of death is very interesting.<br />
<br />
- The officially-old massively multiplayer game <strong>EverQuest</strong> placed severe consequences on player death, often representing hours of lost time or even worse. In a worst-case scenario players could die in such a way that their corpses, which held all their belongings (representing potentially hundreds of hours' worth of questing), were impossible to recover. As a result, I imagine that fear of death in EverQuest probably approximated a real-life fear of death for some of its players more than any other game. MMOs have since repeatedly loosened the reigns on death penalties in order to reduce frustration / heartache and make themselves accessible to wider audiences, but EverQuest achieved something special in its time.<br />
<br />
- <strong>ZHP: The Unlosing Ranger vs. Darkdeath Evilman</strong>... look I'm sorry it's Japanese OK? I haven't played this game yet but it's on my short list in no small part because of its fascinating, funny, upbeat take on player death. It's a game about the inevitability of disgraceful death at the hands of a hopelessly powerful enemy, yet your character has the ability to reincarnate and begin anew with greater potential for advancement than his past self.<br />
<br />
- Last year's <strong>Demon's Souls </strong>reminded me a lot of EverQuest's corpse runs. Death came swiftly and often, and carried a heavy price of essentially all your money and experience, though the game gave you one chance to try and recover the lost goods... and did that ever make you take things slow and steady, take the time to learn the environments and the encounters. The best part was seeing apparitions of other players dying and seeing messages left by other players, warning you of impending dangers. The sense of a solitary-yet-shared experience was amazing in that game, like being trapped in a dungeon with other survivors and naturally joining forces to try and survive.<br />
<br />
- In <strong>Diablo II</strong> and its hardcore mode, death was permanent. Hit a lag spike going into Duriel's lair in Act II and that character you'd been building up for the last two weeks would be gone. Similar feelings to Fire Emblem – you felt a healthy respect for the possibility of death, an appreciation for how it could come at any time, would have to make peace with the shocking reality of it. I loved hardcore more.<br />
<br />
- In <strong>Prince of Persia: The Sands of Time</strong>, the character has a Braid-like ability to reverse time (in fairness the game came out well before Braid), and in addition to that there's a narrative layer in which the character is recounting his own story. When the player character dies, the narrator says things like "That's not how it happened," justifying why a respawn mechanic exists in that game, justifying why the game was pretty easy but nonetheless exciting because you wanted to know how it all worked out in the end. It was excellent. <br />
<br />
- In <strong>Counter-Strike</strong>, death was often shocking and meaningful. Here was a shooter where you couldn't just respawn. When you died you sat out the rest of the round. You were failing your whole team and all you could do was watch as the rest of your boys probably get killed because they were down a man. Death has never felt more meaningful to me in a shooter as it did in that game, so much so that I was never much of a Counter-Strike player. Of course most shooters trend away from this type of consequence, and yet Counter-Strike continues to be extremely popular, because it gives people reasons like this to become invested.<br />
<div style="text-align: center;"><br />
. . . .</div><br />
In the game I'm working on, we don't want you to die, but I want you to know it's possible to fail if you play in a careless fashion, if you ignore danger. If you do run out of health, you'll have at least one more chance to carry on from where you left off in any given sequence, which we think encourages players to push forward more carefully if they started getting a bit lazy or sloppy in their play. It works as a literal wake-up call. Our reactive narrator will also have different things to say about the player character getting knocked out in each of the game's sequences, and will say different things depending on whether or not you fail, so we at least acknowledge the possibility of death in this fashion – we keep track of it and respond to it.<br />
<br />
We struggled for a while with what to do about player death in the game, and were tempted by systems that would eliminate any penalty whatsoever because we didn't want to force people to repeat lots of content if they didn't want to. I think what we decided on is a good solution for our game, and I'm glad we arrived at it through thoughtful exploration and iteration rather than just taking the existing conventional checkpoint solution and calling it a day. I also like that our solution maps to the aesthetic of our game. In Bastion's world, death may be an inconvenience that can be prevented. At the very least, the narrator of the story does not seem to take death very seriously, as you can infer from the trailer. Part of the reason for that is, as you can see, that I don't think game players take death very seriously either.<br />
<br />
Let me know what are some of your favorite examples of games that treated death in interesting ways.<br />
<br />
<div style="text-align: center;">. . . .</div><div style="text-align: center;"></div><br />
I also wanted to take a moment to thank you for reading. Since I started this blog in March, I've succeeded in making the types of preoccupations expressed here into a key part of my job. I love what I get to do everyday and look forward to creating a game next year that's going to deliver on some of the ideas I've expressed here over the months. Happy holidays and here's to a good year for games in 2011.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com13tag:blogger.com,1999:blog-6082533239875181337.post-64619674845347234792010-11-23T22:57:00.000-08:002010-11-23T23:16:27.636-08:00Closed Narratives in Open WorldsI liked open-world games a lot better back when they were just called role-playing games. Maybe I couldn't mow down pedestrians with a car in <strong>Fallout</strong> or <strong>Ultima VII</strong>, but I still could go wherever I damn well pleased and do whatever I wanted, even if it meant breaking the rather strict laws of the respective gameworlds. The thing is, I felt like those games fully supported my actions no matter what I did. Such games fed back on the entire breadth of my gameplay choices. Ultima VII was not a game about being good or evil quite like <strong>Knights of the Old Republic</strong>, but it always let you do evil just so you knew it was there as an alternative, just so the temptation and the option for it were always there. You didn't have to be good, you chose to be, and that gave weight to your actions in the game.<br />
<br />
My problem with today's open-world games – and by this I really mean the Rockstar Games genre, because as a collective of studios, Rockstar really has single-handedly defined this genre in recent years – is that their narrative content is increasingly conflicting with their gameplay. Their gameplay says "do whatever you want when you're not playing a story mission" while their narrative says "watch this character's story unfold." From a narrative standpoint, these games have become the Western equivalent of the glory days of the Japanese RPG, the days of games like <strong>Final Fantasy VII</strong>. Except those games have long since fallen out of vogue.<br />
<br />
In those days, your reward for overcoming a gameplay challenge of some sort was a bit of noninteractive story. This was a wonderful structure as just about anyone can attest who played one of the well-regarded Final Fantasy games back in their heyday. You became attached these ensemble casts of crisply defined, empathetic, interesting characters and through your actions as some disembodied turn-based combat specialist you were able to help them reach the end of the line of their respective stories. I'll never forget some of those characters. Their stories benefited from the linearity of the structure and the lack of player control during story scenes. If I had control over the Dragoon Kain's choices in <strong>Final Fantasy II</strong>, I wouldn't have turned traitor against Cecil in the first place, and I would have inadvertently negated one of the game's more interesting subplots. Or if I had a real choice as to whether to remain a Dark Knight or become a Paladin as Cecil, well... I had no complaints about being something called a Dark Knight at a time when RPGs almost always cast me as a pure and noble hero.<br />
<br />
Today's open-world games such as <strong>Red Dead Redemption</strong> and <strong>Grand Theft Auto IV</strong> are presenting these increasingly lavish tales with huge casts of characters. I like what they're trying to do with their stories. I finished this year's Red Dead Redemption on the promise of a deeply satisfying ending, and in the end it totally delivered. However, the strength of these games' characterizations is adversely affecting the way I play. I <em>don't like </em>the freedom of choice that the gameplay offers me because most of the choice runs counter to what my character would actually do. Red Dead's John Marston is a good-natured man with a dark past. That the game lets me wantonly slaughter people in the streets in exchange for some petty cash and a slap on the wrist just feels all wrong, and I find only the absence of entertainment in it – not because I have a distaste for violent videogames (if I could drink videogame blood I would), but because I don't like when games give me lots of ways to break my own suspension of disbelief, especially when they do an excellent job of getting me to suspend my disbelief in the first place.<br />
<br />
Along these lines I just couldn't bring myself to rampage through GTA IV's Liberty City like I could in <strong>Grand Theft Auto III </strong>back in 2001. It's not that the novelty was gone, because it was absolutely there. GTA IV seemed like such a great playground in which to be some horrible, horrible crook. But Niko Bellic isn't that guy. He's a guy who's trying to help his Mom and find his cousin a nice girl. He doesn't mow people down on the sidewalk.<br />
<br />
I played and enjoyed both of these games and the lengths they took both to create vividly detailed clockwork worlds and relatively serious, relatively thoughtful stories. I'm just saying that the two halves of the games – the story part and the open-world structure – didn't mesh for me, so in both cases I found myself actively trying to ignore the peripheral content and beelining through the story missions with a feeling of "I hope I don't break anything" along the way. In effect, I made myself play these games as linearly as possible.<br />
<br />
I'm not suggesting these games should have been strictly linear, as the reception to the recent <strong>Mafia II</strong> is a good indicator of how a not-insigificant number of players do expect open-world gameplay systems from a game with any superficial resemblance to other open-world games. (There are also exceptional cases like <strong>Batman: Arkham Asylum</strong>, which supports a broad range of actions from the player, pretty much all of which seem internally consistent to the game and its famous starring character.) But I do find it strange how the open-world genre has evolved, when older examples like GTA III didn't have the same problems. GTA III and its silent protagonist let me decide what sort of man I was, whether I was the sort to drive on the sidewalk on a busy intersection or take care to only shoot the bad guys, or somewhere in between. In that game I truly felt like I was in an open world. Today's open worlds may be bigger and more detailed but they feel a lot more restricted to me, because I can't bring myself to ignore their stories.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com14tag:blogger.com,1999:blog-6082533239875181337.post-52855673445842467152010-10-23T10:04:00.000-07:002013-02-02T08:55:11.945-08:00Writing BastionOn September 2, I officially joined the small team at <a href="http://www.supergiantgames.com/">Supergiant Games</a> as their creative director, and together we showed our game <strong>Bastion</strong> for the first time at PAX in Seattle. The response was almost overwhelming, and on a personal level it was one of the most rewarding moments of my professional career. Part of the reason for this is that Bastion is a pure expression of many ideas that are close to my heart – ideas about games, stories, and other things that matter to me – so the enthusiastic response really meant a lot. In the game you'll find a lot of the stuff I've been writing about on this blog put into practice. Granted, my contributions to the project are only just beginning in earnest, but because I was involved in developing the original concept back when my colleagues and I parted ways with Electronic Arts in August of last year, I feel much closer to this game than any other thing I've worked on. Moving forward, I'd like to use this space from time to time to talk more about my thought process while developing Bastion, and to begin with I wanted to explain how we're approaching the game's use of storytelling through narration. But first...<br />
<br />
<strong>GDC Online Lecture: Delivering Exposition in Games</strong><br />
All this is tangentially related to my GDC Online presentation I gave on Tuesday, October 5. I've posted the slides here and invite you to take a look: <a href="http://dl.dropbox.com/u/10130879/Kasavin_Greg_Delivering_Exposition_In_Games.ppt">I Don't Want to Know: Delivering Exposition in Games</a>. The slides are fully annotated so just by flipping through the slides you'll get a feel for the substance of the talk. If you have a chance to look it over, let me know what you think.<br />
<br />
<strong>Narration in Bastion</strong><br />
In film, narration is one of the most misused and mood-killing techniques out there, for its unique ability to eliminate the type of ambiguity that adds richness to scenes and characters. While I've often fantasized about being able to read people's minds as a superpower, if movies have taught me anything it's that knowing people's inner monologue would make life far less interesting for someone as neurotic as me.<br />
<br />
Nevertheless, Bastion uses real-time narration extensively. Its purpose is to deliver story and exposition, and to build atmosphere, investment, and immersion in close partnership with the gameplay. The narration wasn't part of the original game concept. It was born in a flash of inspiration (through a development process that enables such happy accidents to occur), stemming from a couple of self-imposed constraints. The first constraint was to never interrupt the play experience for the sake of story or for any reason, which meant no cutscenes, no dialogue trees, no pressing the A button to advance through dialogue, and none of the other such trappings that tended to slow the pace of other RPGs. I love many games that do these things, but Bastion just isn't this kind of game. One of the things I miss about games in general is that sense of immediacy that console games used to have (before disc-based media ushered in a new era of loading times and cutscenes), where you'd hit Start and, indeed, start the game. Bastion is meant to be that kind of game. Text-based dialogue wasn't going to work. The team's suspicions about how it would negatively affect the pace of the game turned out to be accurate.<br />
<br />
From the outset, before the company was even formed, I wanted to work on a game with some narrative substance and emotional depth, to create an original world with its own characters. We would have these long late-night conversations about how to deliver story in ways only possible through the medium of gaming, because why not? Games should aspire to be games. Cinematics interrupt the play experience no matter how well crafted they are. And as much as I love stepping through dialogue in games like <strong>Fire Emblem </strong>or <strong>Torment</strong>, I had to agree that reading lots of text in a game usually isn't a good feeling. All the theorizing needed to be grounded in reality due to the would-be team's small size and limited bandwidth in art and animation. This other constraint meant no elaborate scripted scenes or silent emotive storytelling as in games like <strong>Ico </strong>or <strong>Limbo</strong>, where nuanced animation is essential to mood-setting and atmosphere.<br />
<br />
Eventually through prototyping and experimentation all this led to the idea of real-time narration, having a narrator who responds to the player's input. From the outset I was interested in having the story begin with a young man rising as if from sleep or from death, to discover a world changed around him in some profound way. The story would start on a mysterious but emotionally low point and expand from there. The intent was to provoke questions for the player immediately, and allow the game to reveal two worlds in parallel: the way things are, and the way things used to be. At any rate, in that waking-up moment, it turns out that just by adding the spoken line "He rose" to coincide with the player's input, it got a lot stronger. (This later changed to the current "He gets up" after further exploration of the narrative style.) This was one of an initial set of lines that our studio co-founder Amir recorded with our audio director Darren and their childhood friend Logan, a theatrical actor who provides the narrator's voice, after Amir suspected that adding narration may bring something positive to the experience. I remember when I first heard it, not knowing what quality it would have, never even having heard Logan's voice before. It felt powerful even inside a low-fidelity prototype. Players don't normally expect this type of output from a game, so it immediately speaks to some of the qualities that are specific to Bastion. The narrator's voice alone says a lot about the game.<br />
<br />
The other reason, probably the main reason, Bastion is using narration is because of Logan. In addition to being perfect for the part, Logan offers us one other great advantage: We have access to him. Some people mistook his voice for Ron Perlman's. Let's say we could afford Ron Perlman, lost our minds, and decided he'd be better than Logan for the part. We'd have maybe two or three recording sessions with him for the lifetime of the game. With Logan we can iterate rapidly, and we need to in order to get the narration in the game to feel as closely connected as possible to the moment-to-moment play.<br />
<br />
Logan's natural speaking voice is quite different from that of the narrator, though we were always interested in a fantasy-frontier aesthetic, something with some the beautiful-melancholy tone of some of Cormac McCarthy's novels. I also take inspiration from the late William Gaddis, whose novels have characters with such distinctive voices. And so we developed a character who embodies the tone we were interested in. And Logan nailed it.<br />
<br />
Bastion's narrator is designed to support our game on a fundamental level. He's a man of few words not only for fictional reasons but also, conveniently, to support a design constraint that we simply can't have him talking a lot during gameplay. Bastion has a very fast feel to it, closer to an action game than a typical action role-playing game. Our narrator needs to be very concise to keep up with the pace.<br />
<br />
<strong>Five Rules for Writing Bastion</strong><br />
Logan can probably make the stupidest combination of words sound awesome. Even still I'm attempting to write good material for him, in the spirit of not wasting the player's time with bloated unnecessary prose. By exploring the character and which types of narration work best for the game, we gain a low-level understanding of the narration in addition to our high-level goals for it. As such, here are the factors I bear in mind when writing for the game:<br />
<br />
<strong>1. Dialogue is for subtext. </strong>The player's actions in the game are the "text", the surface-level things that happen. When the player explores, builds things, attacks things, or acquires items, these are all clear and affordant actions. There was initially a temptation and a novelty in having the narrator declare these actions along the way. But this would mean missing the point of why we have the narrator in the game. This would have resulted in that brand of movie-style narration I dislike so much.<br />
<br />
Our narrator deepens the player's interactions by saying something about them that the player could not have known. He provides character intent, subplot, and backstory through his comments. The ultimate goal with every line is for it to tell you something about the player character, the narrator, the way the world is, and the way the world used to be. For example, the first item you find in the game is a large sledgehammer, to which the narrator says, "Kid finds his lifelong friend." You can see that it's a hammer so you don't need the narrator to point that out, but through the narration you can deduce that the protagonist has history with this hammer and that the narrator knows it. Further, through the narrator's particular delivery you sense that this history has had its ups and downs. Using this type of narration, we gradually build the backstory in the context of the player's immediate actions and surroundings – I would never expect you to care about something that wasn't onscreen. Following the points in my GDC presentation, I mean to deliver on the major questions raised in the game, but moment-to-moment this type of narration should give a sense of a detailed world that existed before you started playing the game.<br />
<br />
<strong>2. Keep it short.</strong> Our narrator is a storyteller but a terse man. Unlike me he doesn't waste his breath, and that's fortunate because our environments are packed with detail and leave no room for long speeches. In order to achieve the moment-to-moment reactive feel we want from the narration, the lines have to be short. Our narrator has a flair for the dramatic and speaks in a low flat voice, so tonally the lines tend to fit well together even if there's a lot of silence in between statements. These were factors in the character design.<br />
<br />
<strong>3. No breaking the fourth wall.</strong> One of the most exciting aspects of having a narrator in our game are all the opportunities to break from player expectations, and raise a lot of interesting questions over time. A temptation in all this is to have the narrator address the player directly or step out of the story and break into metafiction, maybe tutorialize the game by telling you when to press and hold the X button and so forth. But it didn't take long to realize this wasn't going to work. As mentioned earlier on, our high-level goals include building immersion and investment. If the narrator were to break the fourth wall, we might get a momentary gag out of it but we'd be undermining the experience we want to achieve by violating the player's expectations around the game's own logic. We have a cleaner way of training players, and as with everything else, the narrator is there to reinforce those moments without stepping on them.<br />
<br />
<strong>4. Reward experimentation and playing with finesse. </strong>Our narrator provides a great reward system, provided players like what he does for the game. I want players to develop a relationship with him as a character and to feel like they can provoke certain types of comments out of him. This happens to be well in line with the type of play experience we want to deliver, one where players feel like they can do whatever they want in the world, experiment with all the different systems and weapons, explore a bit off the beaten path, and so on. Having the narrator specifically acknowledge these moments tends to provide positive reinforcement in a natural way. We realized the closest thing to what we were going for were some of our favorite announcers in games from completely different genres, from the announcer screaming "BOOM-SHAKALAKA" after an awesome dunk in <strong>NBA JAM</strong> to Shao Khan saying "Excellent" after a ferocious uppercut in <strong>Mortal Kombat </strong>(both games were done by Midway in their glory days). The key difference is our narrator isn't quipping, he's telling a contiguous story for the most part. Having him sneak in a few incidental remarks based on the player's choices or performance helps make the whole thing feel personal and specific.<br />
<br />
<strong>5. No repeats. </strong>When done properly, our real-time narration starts to take on the quality of a story unfolding, and starts to get at those high-level goals we want to achieve. But nothing sucks the momentum out of the game's narrative like a repeated line. Almost every game uses repetitious dialogue even if it's got tens of thousands of lines of dialogue in it; combat encounters will repurpose enemy battle chatter and so on. With Bastion we realized that the moment any line repeated itself – for example, our narrator has different things to say if the player falls off a ledge – immersion is broken. You realize in that moment that you're playing a game where the narrator might loop through a host of different lines after a specific event, as in a real-time strategy game where your units will cycle through several responses whenever you issue an order. So we drew a line in the sand: No repeats in the game, not unless you replay the game from the start or restart a scenario from scratch (and even then we mix up the narration). This posed certain design challenges, such as what happens if a player revisits certain areas, but we're happily taking those on in the spirit of maintaining the feel we're going for.<br />
<br />
<strong>Conclusion</strong><br />
If there's one main underlying point in all this, it's that everything we're doing with the narration in Bastion is there only to support the specific type of play experience we're making. Everything from how the narrator character sounds and how he talks came about purposefully as part of the exploration around gameplay concepts and game themes. Bastion is hardly the first game to use narration to deliver story, so we never set out to pursue the idea of having a narrator purely for the sake of being different. Instead, we're pursuing it because we realized it worked well for the game we wanted to make and for the process we're using to make it.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com3tag:blogger.com,1999:blog-6082533239875181337.post-57195496910348482562010-08-29T23:17:00.000-07:002010-08-30T15:50:51.433-07:00A New ChapterThis is an uncharacteristic post but it's time I updated with some personal news I wanted to share. Normally I'm opposed to using this space for personal information -- I can barely find the words to talk about my life to my closest friends -- but in this case it's directly related to the larger topic of this blog.<br />
<br />
Two days after my previous post, my son Isaac was born. Then after I took two weeks for paternity leave, I returned to work and resigned from my job. This coming week after my last day with my employer, I'm going to get in a van with four other guys with whom I'll be working from now on, and make the 14-or-so-hour drive to Seattle for PAX Prime. There I'll be giving a talk titled "Memoirs of a Triple Agent" about my experiences having worked in gaming media, development, and publishing, and lessons for contending with each of these factions. I'll also be announcing my new venture, which will allow me to get much more hands-on with design and writing for games (among many other responsibilities), in addition to having a somewhat more flexible schedule to accomodate the changes in my family life.<br />
<br />
I'm giving up a lot, something I try not to think about too much. I was treated very well at my job and was given a lot of responsibility and latitude to do things my own way, and for that I'm deeply grateful. I wish all the best to the development team I've been working with as well as to the publishing team that took me in and supported me. But this new thing, this is something I have to do and this may be the only chance I'll ever get to do it. Life's too short to let any such chances slip away. I only hope my colleagues will forgive me for what must have seemed like a sudden change of heart.<br />
<br />
I started my professional career working independently. I co-published a gaming fanzine out of high school. I started doing freelance work for gaming magazines. I cofounded a gaming web site. And then I joined GameSpot, what was then one of the largest independent gaming publications around. There I stayed for 10 years and through two corporate acquisitions; what started as a disruptive force in gaming media had become an entrenched part of the establishment by the end of my stint. Following that, I joined Electronic Arts as a producer because I needed to get on with realizing my dreams of making games, and then last year I joined 2K Games as a producer on the publishing side -- both of these are large but very different companies that can achieve whatever they focus on. And now things are coming full circle, as I'll at last be leaving the corporate world behind for the trials and tribulations of independent game development. I have no delusions about this change. But I welcome the challenge and I relish the work itself. While I'll no longer be working on the sorts of multimillion dollar projects I often write about here, independent games have a purity of vision (and increasingly a high quality of execution) that's incredibly alluring to me. So in this new capacity, I expect to be able to apply what I know and what I think in a pure way that's manifested in original games designed for people who love games as I do.<br />
<br />
All I want is to pour everything I've got into making a game people can love. It will be something I want to look back on and say, this truly was a part of me -- it's not just something I sank a bunch of time and effort into out of principle. And if it's a game I could one day play with my son or daughter, so much the better.<br />
<br />
I have no plans to make a habit of hijacking this space for self-promotion like this, but as you can see, the last month's held a slew of changes that I wanted to share (especially since they've preoccupied me from coming up with anything more relevant to write about right now). In the spirit of getting it all out of the way in one swoop, I'd also like to mention I'll be giving another talk in October at GDC Online in Austin, titled "<a href="https://www.cmpevents.com/GDAU10/a.asp?option=C&V=11&SessID=11488">I Don't Want to Know: Delivering Exposition in Games</a>". Unlike my PAX talk, this one will be close in spirit to the type of subjects I've been writing about here. I haven't done any speaking functions in some time but am really looking forward to getting back out there and sharing everything I think I know about my favorite subjects.<br />
<br />
I'll need a lot of luck where I'm going so if you have any to share I'd be much obliged.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com12tag:blogger.com,1999:blog-6082533239875181337.post-53310418162281892352010-08-02T23:50:00.000-07:002010-08-03T14:27:06.000-07:00Infernal Logic<strong>Limbo</strong> is the arresting puzzle-platformer released in July for Xbox Live Arcade, and I wanted to talk a bit about this fascinating game through the lens of narrative design. So if you haven't played and finished it already, I highly recommend you do so before reading -- or even instead of reading. After all, beautifully crafted and artful games like this don't come around very often, though I'm not writing about Limbo here just because it's great.<br />
<br />
In some respects, there's not much to say about Limbo's use of narrative. The game doesn't have a single spoken word in it and barely has any written words in it either. I believe "Hotel" is literally the only word that appears as part of the game itself (discounting menu text and credits). Like the rest of the narrative, I think this word ultimately is a red herring, something that probably inspires a lot of speculation about its meaning when players run into it, yet there's really not much there -- it's art for art's sake. Which is fine. This is how Limbo works.<br />
<br />
Limbo has no real story as such. But you go through the game consciously or subconsciously looking for one, expecting one, because Limbo does such an excellent job of creating atmosphere and giving exposition, using methods that are as minimal as they are effective. Thus you expect the opening exposition to be expanded on, because of how our brains parse things shaped like stories. The game has one of the most intensely concentrated and compelling openings I've played in some years. It makes you think there's a story, and fills your head with dozens of interesting questions: who am I? where am I? why am I here? what am I looking for? who else is here besides me? am I even alive? The game's presentation is so strong that you in turn play through with the confidence that the authors of the game, and the game itself, must hold the answers. These types of questions are enough to keep you going through some extremely challenging puzzles that you'd sooner give up on if not for the game's narrative drive.<br />
<br />
If you've finished the game, then you've unlocked all the stages in the Chapters menu. If Limbo were a typical puzzle game, that Chapters menu would have structured the experience. You would have selected puzzles from that screen, finished them or maybe not, then dropped back to that screen to pick the next one. As a result, the game would have been a pale shadow of itself. One of the things that makes Limbo so special among puzzle games and among platformers is that it offers a completely seamless, contiguous experience -- it's like one long level. You become completely immersed in it due to the flawlessly executed art style, audio ambience, and physics simulation, all delivered without interruption. At the same time, little story vignettes imply a greater meaning to the events that take place, a meaning you continue to search for until the game is over. The game breaks your immersion only when it gets too hard, which happened to me a couple of times early on then a couple of more times towards the end. But not so often that I wasn't fascinated to keep playing, to see where the whole thing was going.<br />
<br />
It ends up going who-knows-where. The theme of the game gives it an "out" from a narrative perspective, in that a game about the place between life and death doesn't need to make sense (and probably shouldn't), and it doesn't need to provide clear answers (and probably shouldn't). Even still, Limbo's narrative felt incomplete to me in a way that wasn't entirely satisfying. I loved the starkness of the ending, the smash cut to the credits. I didn't love that things that seemed so intriguing in the game never came back into play. It struck me that the most interesting scenes were front-loaded. The game was at its most interesting when other living beings were afoot. Shadows of savage humanoids lurking in the darkness. Strange tortured souls hanging in the background. Flies swarming rotten chunks of meat. A man-made spider contraption. These sinister images are the game's most memorable. Later when it takes a shift to giant clockwork machinery and sketchy film noir neon signs, I realized that what was pushing me forward was my search for continuity, to see those dark shapes from the forest in the beginning come back and reassert themselves. And of course I wanted to see what happened at the end. It's a puzzle game and I was trying to piece together the biggest puzzle it had put in front of me. But it's the one puzzle that can't be solved. In the end, the game ends close to where it started, in the forest where the game is at its strongest. Limbo is a game about what it feels like to take a wrong turn.<br />
<br />
I had this feeling that there's no continuity to the game in part because there was no good way to create continuity among the puzzles the design team chose to include and polish to perfection, probably from among many hundreds or thousands that they cut during the iteration process. I found myself wondering what content was left on the cutting room floor.<br />
<br />
In the description paragraph you can read before you download the game, you're told that it's about a boy trying to find his sister. This is a surprisingly specific detail for a game that revels in unanswered questions. In <strong>Shadow of the Colossus</strong>, the ambiguity around the protagonist's relationship to the girl he seems to be trying to save works in the game's favor, to build intrigue. You're left to wonder about their relationship and what would drive the protagonist to do what he's doing for her sake. Even if it's love it takes a special love and a special woman to motivate a young man to hunt giant monsters for a woman's sake. In Limbo, you see an apparition of what looks like a girl on a couple of occasions before you finally encounter her right at the end. It's easy enough to interpret the plot of the game as something similar to Shadow of the Colossus from these scenes, yet being told precisely what the protagonist's relationship is to the girl he appears to be searching for feels unnecessary to a game that gives nothing else away. I wonder if the creators of the game had much of a part in writing that description.<br />
<br />
I don't think most people went into Limbo expecting much of a story, and neither did I. But having a story isn't the only way to build narrative depth into a game, as Limbo demonstrates. The game may have no meaning, but man, does it ever make you search for one. At least that's how it worked on me, and I like it when games leave me with a lingering feeling, especially if they're going to be short. Did you take something different away from it than I did?Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com10tag:blogger.com,1999:blog-6082533239875181337.post-41100512344903566832010-07-10T13:20:00.000-07:002010-07-10T13:58:46.613-07:00Justifying SystemsWhen I hear people describe something as "gamey", usually they're not paying a compliment. It's an odd way to bag on a game when you think about it, and I can't think of an analogy in any other medium, except maybe comics. Sometimes, such as in the upcoming <strong>Bulletstorm</strong> or last year's <strong>Borderlands</strong>, gamey qualities are designed into the experience. These are games where brightly colored messanges, numbers, or loot drops burst forth from enemy corpses, like a violent <strong>Peggle</strong>, in a manner that has no bearing on realism and is only comparable to what's been seen before in other games including slot machines and such. Hence, "gamey". These effects are there to heighten the sensory pleasures resulting from the basic actions available to the player.<br />
<br />
In most cases, though, games described as "gamey" in the negative sense are the ones where insufficient effort went into integrating certain game systems with the aesthetics and fiction of the gameworld. When a game expects the player to blindly accept why something works a certain way, simply because that's how the thing works in other previous games, I think the game threatens to become gamey-in-a-bad-way. Something about the experience of such games feels grating on the senses, as for every instant you begin to feel immersed while playing, something about the design shoves you back from the brink and reminds you that you're just sitting there on your couch playing a game. I think one of the responsibilities of narrative design as a discipline is to find meaningful ways of justifying game systems within the gameworld, in order to avoid that gamey feeling where it's not supposed to belong, and I'd like to talk more about that here.<br />
<br />
In <strong>Mass Effect 2</strong>, still my favorite game so far this year (next to <strong>Super Street Fighter IV</strong>), the game goes to extremely elaborate lengths to justify why you get to do the things you get to do at the beginning of pretty much every Western role-playing game, such as defining your character's appearance and proficiencies. The game opens with this completely wild and apocalyptic sci-fi explanation of how come a character introduced in the previous game now has to start over from scratch. It's the BioWare equivalent of the scene at the beginning of every <strong>Metroid </strong>game where Samus inevitably loses all her power-ups, or when Death shows up five minutes into a <strong>Castlevania </strong>to shake down the foppish hero for his cloak and rapier (I guess to fill us with latent righteous rage from all those times the big kids stole our lunch money and knocked the binders from our hands). But you know what? That opening scene in Mass Effect 2 worked really well overall. It showed you the people behind this game weren't asleep at the wheel, that they'd thought of a way to meet your expectations for story continuity as well as your expectations going into a new sci-fi role-playing game. They didn't just throw the conventional character-creation screen at you without any reason. Compare this with the approach taken by <strong>White Knight Chronicles 2</strong>, a Japanese role-playing game whose solution to story continuity is to <a href="http://www.destructoid.com/white-knight-chronicles-2-requires-clear-file-from-wkc1-175552.phtml">prevent you from playing unless you've finished the previous game</a>. Imagine if they checked for your past Harry Potter ticket stubs when standing in line to see the latest one.<br />
<br />
Games sometimes go too far to justify everything about them. A friend and I would often debate whether <strong>Assassin's Creed</strong> was guilty of this, as an example. The heads-up display, interface, and even the loading screens of that game were heavily explained away in the sci-fi metastory of a guy stuck in an evil MRI device that tapped into latent memories of his dark-ages ancestors. I told him I liked what they were going for, while he felt the game was trying way too hard, to the point where aspects of the user interface became highly distracting to him while he was playing, because they felt so contrived. According to my friend, the game didn't need to justify why button prompt tips appeared onscreen or why you had a map -- these are things we as game players accept without question. And he's probably right. Even still, I felt Assassin's Creed had its heart in the right place trying to marry these types of interface conventions in a game set a thousand years ago. If the sci-fi elements of the story were handled more gracefully, for instance as a big metaworld reveal later in the game foreshadowed only by the interface, I think it could have all come together in an amazing way. We would have experienced the revelation that certain conventions we just accepted as game players were in fact connected to the story in a meaningful way. Instead, the game frontloads exposition about why you have a health bar and a map, which sags the pace of the story and distracts from what was interesting about the game -- namely, the cities you could run around in.<br />
<br />
A game is not responsible to justify every little system or gameplay contrivance to the player, because as players we're willing to accept a lot of things at face value without any explanation. At the same time, I think we appreciate it when game systems are gracefully explained and justified. So, the narrative design process involves looking for opportunities to integrate aspects of game systems design into the gameworld in a way that makes sense and is interesting to the player without being disruptive.<br />
<br />
A classic example of justifying game interface conventions is the original <strong>Command & Conquer</strong>, with its wonderful installation sequence on down to its robotic female battlefield announcer. Like any PC game of the time, you had to install this one to your hard drive before you could play. But you didn't merely install that game -- due to its <a href="http://www.youtube.com/watch?v=cioyLQ2O6yc">amazing animated install sequence</a>, you felt like you were tapping into a sophisticated battle control interface, like something out of the movie <em>War Games</em>. I always felt that Command & Conquer was a first-person game, where you happen to be looking through your character's eyes at his battle interface, and as a fan I was disappointed in how the series seemed to drift further and further away from this direction rather than embracing it.<br />
<br />
Another of my favorite cases of this is from <strong>Super Mario 64</strong>. As the entire concept of controlling a character from a third-person perspective in 3D, plus having to control the camera, was quite new at this point, the game went out of its way to show you that the "camera" was in fact a little flying cameraman character trailing behind Mario the entire time. I think games that go to such lengths to be internally consistent have a tendency to be great.<br />
<br />
The real downfall of this type of thinking is when it leads to the destruction of conventions that exist with good reason. When the fiction of the game trumps the <em>game</em> of the game, the result are some of those games that try to do such things as eliminate all interface at the expense of your ability to play. The most surprising example I can think of is <strong>The Getaway</strong>, a GTA-inspired PS2 game, which has no onscreen heads-up display whatsoever in the name of cinematic realism in spite of being structured like an open-world game. So, in order to navigate the city during your missions, you have to follow your vehicle's turn signals, since there's no minimap much less any sort of GPS. Problem is, your turn signals can be shattered during the game's numerous chase scenes, leaving you completely blind unless you happen to know your way around London for real. I'm pretty sure even the people who live in London don't know their way around that city. At any rate, when the fiction or presentation of a game starts to get in the way of basic usability, they've probably gone too far. The only HUD-free game I've ever played that handled it pretty well was <strong>Call of Cthulhu: Dark Corners of the Earth</strong>.<br />
<br />
There's no formula to this stuff. It needs to be handled artfully on a case by case basis that suits the particular game. I'll continue to defend the original <strong>Halo </strong>as another outstanding example -- I've met a bunch of people who seem to resent the game's popularity and write Halo off as having merely been in the right place at the right time, but as far as I'm concerned it's probably the most influential game of the last 10 years. The <strong>Call of Duty </strong>series and just about every other shooter owes a debt to Halo for such common ideas as regenerating health and limited capacity for carrying weapons. These ideas in Halo were so well-thought-out that they felt like completely natural parts of the fiction. Much like Gordon Freeman's HEV suit in <strong>Half-Life</strong>, which was the reason you as a player felt capable of surviving through an insane situation that was killing everyone else around you, in Halo those recharging energy shields of yours are the ultimate key to your success. They're explained early on as an integral component of your one-of-a-kind armor through an excellent <em>Robocop</em>-style first-person diagnostics sequence that even fictionalizes the decision of whether to invert the controls for looking up and down. Five minutes into Halo, I felt completely absorbed in that world. When a game's tutorial can do that, it's off to a good start.<br />
<br />
People don't naturally expect for game mechanics to be justified by the fiction and often don't notice or mind when this isn't done, unless it sticks out. Military shooters have appropriated Halo's regenerative health system but applied it to flesh-and-blood characters who we'd expect to die from one or two bullets, and yet nobody seems to mind too much. Regenerating health may not fit the aesthetics of modern military combat, but a a game mechanic, it works, so most of us think nothing of it. But I think there's a danger of stacking too many inexplicable conventions into a game, which causes the game to begin to lose its identity and feel like a bunch of patchwork ideas. Conversely, I think there's a great benefit to artfully ingraining the mechanics, systems, and feedback of the game into the fiction of what's going on in it. In <strong>Oddworld Stranger's Wrath</strong>, there's this fantastic crossbow weapon that supports different ammo types. Each ammo type is in fact a different little creature (live ammunition, get it?) with its own weird personality that affords what the ammo type does.<br />
<br />
What are some of your own favorite or least favorite examples of games justifying their game systems through the fiction? Can you think of other cases where a game was either trying too hard to root its gameplay in the fiction, or didn't try hard enough?Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com10tag:blogger.com,1999:blog-6082533239875181337.post-81039637247728629362010-06-23T23:10:00.000-07:002010-06-23T23:38:00.956-07:00You Don't Have to Say ItI felt very fortunate to have attended the Electronic Entertainment Expo last week, same as I've felt every single other year at the show since it started in 1995. The main difference in my experience this year was that I really only saw just the one game I came there to demonstrate, so I spent mornings and nights catching up online on everything I missed. And looking back on all those many great-looking games that were shown, the one I wish I could have seen if I could pick just one is <strong><a href="http://thatgamecompany.com/games/journey/">Journey</a></strong>, from the makers of <strong>Flower </strong>-- primarily because that game is pursuing a goal I happen to care about very much, which, as creative director Jenova Chen puts it, is to "tell a story without using any language" (<a href="http://www.shacknews.com/onearticle.x/64463">source</a>). Wordless storytelling is a minimal and powerful technique that's well explored and understood in other media, ranging from all-ages movies like <em>WALL-E</em> to blood-soaked manga like <em>Lone Wolf and Cub</em>, yet in mainstream games it's gone out of vogue due to our industry's focus on technology and content storage. After all, why would we remove words from our games when our storage media let us cram in more words than ever? Jenova Chen and team at least recognize that this isn't a rhetorical question. Wordless storytelling won't be a first for Journey (Chen's already done it very well with Flower), so I'd like to talk about other cases where this has worked well in the past, and why. I'm not advocating for it as a path most games should take, but then again if more games would just shut up, it wouldn't be the worst thing.<br />
<br />
When I think of great wordless stories in games, the first example I think of is the 1987 arcade classic, <strong>Double Dragon</strong>. On the surface its story seems like the worst kind of gaming cliché: a pretty girl is kidnapped, so her boyfriend takes matters into his own hands by beating to blink-away-death everyone who stands between him and her (<a href="http://www.youtube.com/watch?v=xb9P0YTeq5Y">video</a>). The difference with Double Dragon, as in all great things, is in the details: One of the thugs in the opening scene is wearing a yellow jump suit and carrying a machine gun; there's a tricked-out Trans Am in the protagonist's garage, and the building he emerges from bears the name "English Tear". These details gave the world a sense of depth for its time, inviting interesting questions. Double Dragon is one of many games where you're supposed to save the girl. But it's the first such game that made me wonder why she got kidnapped in the first place. It's the first action game I ever read anything into. These guys didn't kidnap this girl because she was pretty. They did it to get back at you for something.<br />
<br />
There's more to Double Dragon. You can play the game simultaneously with another player, and if the two of you survive to the end, the grand twist is that the two of you must end up fighting each other to win the heart of the girl you were working together to rescue. There are no words used to express any of this (except a poorly translated you-win screen at the very end), yet it conveyed a complex relationship -- a good old fashioned love triangle, in an action game whose story was delivered without any language. The mechanics of Double Dragon were incredibly satisfying to me in their day, but it was the story, with its perfect expository scene and great endgame sequence, that makes the experience of it unforgettable for me. I've appreciated the power of wordless storytelling in games ever since then.<br />
<br />
Other games even before Double Dragon's time were doing similar stuff. Several years prior, <strong>Prince of Persia </strong>creator <a href="http://jordanmechner.com/">Jordan Mechner</a> created an amazing computer game in <strong>Karateka</strong>, considered the first game with cutscenes in it. Karateka has a similar rescue-the-girl premise as Double Dragon, and likewise went to surprising lengths at building up its characters in what was a relatively simple game. The difference for me was that Double Dragon's story connected the player to the inciting incident of the story -- we see a girl take a hard hit and get hauled off moments before our character emerges, whereas in Karateka, our hero shows up in a separate scene after we see the fair princess get locked up in a cell. We don't empathize with the Karateka protagonist as quickly as we do in Double Dragon because there's less of an implied connection between the player character and the girl, and less of a sense of urgency to get her before something terrible happens. Nevertheless, Karateka and Double Dragon were the '80s equivalent of blockbuster action games, and they pushed the envelope in terms of cinematic storytelling in the medium. The reason they didn't rely on words, I guess, must be at least partly due to the technical constraint that there was no easy way they could have. But by having to give exposition and establish a setting and a mission without being able to use any words, these games delivered story in a far more elegant way than most modern games do. I think those techniques absolutely are extensible to today's games and could be used to tell the sorts of deeper, longer stories that today's players expect.<br />
<br />
Elegant storytelling is conservative storytelling. Scenes should be enriched with as much subtextual meaning as possible before words are used to give any of it away. The more space and time needed to establish characters, places, and motives, the more the story runs the risk of becoming bloated and getting in the way of the gameplay. I don't mean to overgeneralize, mind you, since some of my favorite narrative experiences in games -- from <strong>Ultima V</strong> to <strong>Metal Gear Solid</strong> to <strong>Planescape: Torment</strong> to <strong>Fire Emblem</strong> -- happen to be very, very wordy. But I have a deep respect for games that can immerse me into the experience without having to talk me into why I should care.<br />
<br />
For example, that game Journey evidently takes inspiration from <strong>Shadow of the Colossus</strong>, which is a relatively more recent example of a game that delivered most of its story, including its own very strong expository scene, using very little language at all (<a href="http://www.youtube.com/watch?v=1sS_rHO6Vjc&feature=related">video</a>). And somewhere in between these two cases was <strong>Super Metroid</strong>, one of my favorite 16-bit games, which features an amazing endgame sequence that's rich with action and emotion yet goes over without so much as a word (<a href="http://www.youtube.com/watch?v=83C216WsYmc">video</a>).<br />
<br />
I happen to think players generally deserve more credit than most games give them, both in their capacity to learn and use complex overlapping systems and in their capacity to infer meaning. Occasionally there's a game like <strong>Braid </strong>or like <strong>Myst </strong>that invites players to explore with barely a word of explanation, and such games have a way of capturing fiercely loyal audiences. Because absolutely everyone, young and old, likes to feel smart. Conversely, absolutely no one, young or old, likes feeling condescended to. And so, games that express silent confidence in the player's ability to pull details out of the scene pay their players a great compliment by giving them the benefit of the doubt that they'll understand what's going on even though there isn't on-the-nose dialogue there to explain everything away.<br />
<br />
Of my written work that's been published, most has been published online, with too little regard for length. Having hard constraints -- whether it's for an author working in print or a game developer limited by time or technology -- can bring about good practices that come undone when those same constraints disappear. Then it takes years for games like Journey to come around to reintroduce old ideas for a new generation. But you know? Works for me.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com3tag:blogger.com,1999:blog-6082533239875181337.post-81485101574083826572010-06-08T22:36:00.000-07:002010-06-08T23:15:18.493-07:00Knowing vs. Growing ProtagonistsIn recent years more and more games have made me feel like an actor who doesn't know his lines in the middle of a performance. The set dressing changes but the experience is the same: For a while, everything is happening according to the script, until we reach the point where I start screwing up my part. Pregnant pauses and awkwardness ensue. Failure in highly scripted games feels almost embarrassing, like failing to solve a simple puzzle, because the star's performance as the hero/soldier in these games isn't even intended to be challenging.<br />
<br />
I think all this is a byproduct of what happens when games are chiefly designed to fulfill a particular power fantasy for the largest number of players, even at the expense of giving those players the ability to relate to the situation. There's an inherent dissonance to playing a realistic-looking game as a highly experienced character of some sort -- a spy or a supersoldier or whoever -- when you yourself don't know how to perform actions that should be second nature for the protagonist character. And judging by the trends, mainstream retail gaming's answer is to reduce difficulty, automate, and front-load lots of contrived training in order to ease you in. This feels like formula. So what does it take to provide a genuinely different and affecting experience in a mainstream game at this point? I think the answer is closely linked to the design of the protagonist character, and his or her persona, abilities, and relationship to the world of the game.<br />
<br />
It used to be more common for games to ramp the player's abilities. Classic games like <strong>Metroid</strong> and <strong>The Legend of Zelda </strong>demonstrated how compelling it is to start off as a character with great potential but limited ability and gradually gain access to a wider variety of powerful moves. This achieves a few things: It gives the player incentives to continue exploring, knowing that the next cool ability may be right around the next corner; it allows for intricate level designs that make the much-maligned concept of backtracking seem palatable if the player is later able to traverse areas in surprising new ways and faster than before; and it provides a natural ramp for a game's challenge and difficulty, by allowing early encounters to be simple and later encounters to be tougher and more complex. I love games that have these qualities, whether they're <strong>Castlevania: Symphony of the Night</strong> or <strong>Metroid Prime </strong>or <strong>Batman: Arkham Asylum</strong>. But it seems to me they're less common now than they used to be. I don't think this is because this type of structure became unpopular. I think it's because the pursuit of realism in games (or rather the idea of "superficial authenticity") became relatively more popular.<br />
<br />
If you're a supersoldier or a spy, you're what I'd call a "knowing protagonist", someone who's been training your whole life for this mission of a lifetime you're about to go on. The world of that mission does not support the idea that you'd somehow gain an incredible new ability during the mission, since you're already at the height of your prowess. You might find an experimental weapon or some cool new gadgets, and you might ride on vehicles or have to go through a level without killing anybody or something. But the pressure's squarely on the level design and possibly the story rather than on the ramp-up of player abilities to keep you engrossed. On the other hand, if you're somebody like Link, a kid with humble origins but a lot of potential, you start off with nowhere to go but up and you're what I'd call a "growing protagonist". As well, having a gameworld that's more imaginative than real opens up opportunities for Link or others like him to grow in power in a dramatic way.<br />
<br />
A protagonist character with humble beginnings doesn't have the natural, superficial appeal of an already-experienced character such as a tough-as-nails supersoldier or an unstoppable assassin. But by starting out strong, these types of characters naturally and severely constrain the internal logic of the gameworlds they inhabit, forcing designers to front-load play mechanics and put all the pressure on level designs and story to keep things interesting. Max Payne, Master Chief, Markus Fenix, and Soap MacTavish all start with the same exact abilities they end with -- the guns change, the scenery changes, the story changes, but the moment-to-moment gameplay basically stays the same the whole time. I love the games these guys are from, too. But their games have influenced two whole generations of similar stuff that seemed to muscle out many of the Links and the Alucards and the Samuses, in favor of more true-to-life and arguably less interesting characters and worlds.<br />
<br />
Reality-based games may be a big draw for mainstream developers or publishers, but reality imposes some really awful constraints on games. For instance, how do you teach a player the basic rules when you're also trying to make him believe that he's that badass supersoldier looking tough on the box art? The two goals are almost contradictory and yet almost every action or adventure game faces the challenge of building immersion while teaching the player how to navigate the environment.<br />
<br />
Some games manage very clever solutions. I loved playing as a Russian grunt at the beginning of <strong>Call of Duty 2</strong>, learning to throw potatoes like grenades because grenades were too costly for the Soviets to train with. What a fantastic bit of exposition. Running the training course as the new guy at the beginning of <strong>Modern Warfare</strong>, while an obvious solution on some level, also worked well to draw players into the experience while making them empathize with the protagonist character -- even a silent protagonist like Soap MacTavish. After all, Soap was going through exactly the same thing as the player -- learning, training, trying to fit in. By the time <strong>Modern Warfare 2 </strong>came around, Soap was no longer wet behind the ears, so developer Infinity Ward did something brilliant by making him a nonplayer helper character (at least when we first meet him) and once again cast you as someone still learning the ropes.<br />
<br />
Batman: Arkham Asylum also did a fantastic job of justifying the player's learning. Batman is a perfect example of a character who should be at the height of his power at the beginning of a story, unless it's his origin story. But in Arkham Asylum, developer Rocksteady Games justifies making him a "growing protagonist" by telling a story of a routine Batman mission that happens to go pretty badly wrong... leading to Batman being physically unprepared for what's to come and having to scrounge up additional tools from the Batmobile, his secret Bat Cave, and so on. Batman's growth is further expressed by his suit becoming more and more tattered over time -- he physically appears more experienced by the end. The moments where Batman gains new powers in the game feel pretty forced from a story perspective, but they enable the open-ended structure and that immensely satisfying feeling of having escalating powers and abilities.<br />
<br />
A protagonist character's status in his world at the beginning of a game is the foundation for the internal logic that structures the player's progress. If you start off as a supersoldier, there's not a lot of room to grow. You might succeed against all odds, but no one's going to promote you if you're already Master Chief. Or if two hours into the experience you already have your own team, your own spaceship, and carte blanche to do pretty much whatever in the galaxy as in <strong>Mass Effect</strong>, then no wonder you're going to wind up feeling a bit let down by the shallow systems governing character progress -- there's no real room to grow, not within the constraints of a "hard science" world where you start out on top. On the other hand, in BioWare's own <strong>Knights of the Old Republic</strong>, your character dramatically gained power, becoming a Jedi and gaining all its perks at record speed... something that felt almost suspiciously too good to be true until the game's big reveal that completely justified your character's remarkable ability to grow in power. Of course, the role-playing genre tends to heavily revolve around the concept of character progression, but almost any kind of game can use fiction to justify and support progression of the player's abilities and a smooth ramp of the complexity of the game rules.<br />
<br />
So, coming back to the question posed at the beginning: How to satisfy the mainstream power fantasy while avoiding the dissonance of having the player's lack of experience with a game collide with the protagonist character's strength and know-how? There's no formulaic answer, of course. But games that work hard at this problem I think tend have tighter internal logic, more empathetic protagonists, and a stronger structure than games that just assume you want to be a supersoldier and that you're OK with a few minutes of obligatory tutorial at the beginning even if it has nothing to do with the plot. <strong>Assassin's Creed II</strong> is a good recent example, a game that had a ton of natural appeal through its fantasy of becoming a cool-as-ice assassin stalking through the back alleys of rennaissance Italy -- but you had to earn your way into that role, learning the ropes as you went along. I didn't like the first couple of hours of that game as much as the rest (I'll come back to this when I write more about exposition), but I think playing through the "origin story" of Ezio made the brunt of the experience of that game all the more rewarding.<br />
<br />
In short, I think it's a good thing for a gameworld to justify the protagonist character's ability to change during the course of the game. If I could make whatever game I wanted, I'd make one with a protagonist character who has a significant capacity to grow throughout the game, as a reflection of the player's own growing familiarity with the game rules.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com5tag:blogger.com,1999:blog-6082533239875181337.post-80508202855590307902010-05-12T21:44:00.000-07:002010-05-16T15:10:01.127-07:00Three Dimensions of World DesignOne of the greatest, most influential game companies of all time is Origin Systems, which faded into obscurity during the second half of the '90s. But for a while there, Origin was at the forefront of the medium, specifically with the <b>Ultima</b> and <b>Wing Commander</b> series. I think it was in <b>Ultima VI</b>, the latest in a streak of outstanding games, when I noticed Origin using a succinct and fitting slogan: "We create worlds." They weren't kidding. To this day, Ultima and Wing Commander are among the most fully realized and, for me at least, memorable videogame worlds. These settings supported any number of games and other extensions ranging from novels to feature films. Unfortunately, someone failed to defend the integrity and quality of these worlds somewhere along the road to fortune. However, the string of failures leading to these franchises' demise ought not to diminish what they succeeded in doing in the past. Especially since the total number of memorable, unique gameworlds is relatively small.<br />
<br />
I want there to be more, whether I make them or you do.<br />
<br />
Think of your favorite gameworlds as I thought of Ultima and Wing Commander: What do they have in common? In my case, on the surface it seems as though the medieval fantasy world of Ultima has little in common with the futuristic-yet-modern-feeling world of Wing Commander, and to be sure, the best games in these series didn't come out of a formulaic process. But I do think these and all other successful, original gameworlds share a certain structure in common, and here I'm going to illustrate its triangular shape.<br />
<br />
I think anything that qualifies as a successful, original gameworld can be expressed in exactly three dimensions. Two dimensions is too few, and four is generally too many for a gameworld intended to be enjoyed by a large number of people. When I say dimensions, I mean specific overarching traits -- these are not genre statements like "science fiction", but are broad-stroke characteristic statements, such as "on a space station at the beginning of the 21st century." In other words, each of these dimensions must be a valid, reasonable answer to the question, "what are the essential properties of this gameworld?" Moreover, the gameworld must make good on each of these dimensions, by developing it in an artful way and to a sufficient degree, to the point where the author could, if he so chose, answer any player's questions about how the world works. The version of the gameworld that we experience as players ought to be the tip of the iceberg.<br />
<br />
Let's walk through some examples of what I'm talking about, starting with the game series I already mentioned.<br />
<br />
<strong>Ultima -- </strong>Ultima's world of Britannia has the following dimensions:<br />
<ol><li>Set in a medieval low-fantasy world based on the European dark ages</li>
<li>Teleportation-style travel is possible between this world and ours, as well as within this world</li>
<li>The world is governed by a strict and ancient moral code</li>
</ol>I think when people who remember Britannia think of Britannia, they mostly think of the first dimension I listed here, because that's the world's main characteristic. However, I think the second and third dimensions are the ones that gave the world its depth, accessibility, and originality -- they're the traits that take Britannia far beyond the boundaries of cliché. If you've never played one of the good Ultimas before, the world may sound generic to you, because its secondary and tertiary dimensions aren't as prominent or may not sound that cool when you just read about them. But those dimensions do reveal themselves very quickly in the context of any of the classic games in the series. For such long games, they all have very strong openings that grab you and pull you in. And there you stay, for two decades and counting in my case.<br />
<br />
Now let's have a look at Wing Commander before moving on to more modern examples so I stop sounding so dated.<br />
<br />
<strong>Wing Commander -- </strong>The world of Wing Commander is:<br />
<ol><li>Set in the Milky Way galaxy in the relative near future when spaceflight is common</li>
<li>About a war between humankind and a race of cat creatures (not as embarrassing as it sounds)</li>
<li>The war is waged by pilots whose personal lives intertwine with their battles</li>
</ol>On the surface, the world of Wing Commander maybe sounds less interesting than the world of Ultima, given these dimensions. And indeed, it isn't as interesting -- not the world itself. Because, the most essential dimension that lends Wing Commander its aesthetic quality is the third one, the one about the characters. Interesting characters, like interesting worlds, require multiple dimensions in and of themselves, which is a topic I'll cover next time. For now, the fact that Wing Commander pays special attention to its characters and their personal lives is -- while not the primary characteristic of the gameworld -- essential to the integrity of the world.<br />
<br />
Gameworlds can change form over time, though the evolution process is dangerous. Later Wing Commander games attempted to replace the second trait about humans fighting cats, by introducing a new antagonist faction. These attempts were not very successful, so deeply ingrained were the Kilrathi in the world design. The same thing happened to Star Wars when they expected you to care about the Trade Federation in <i>Episode I</i>. It's not Star Wars, because Star Wars is essentially about a rebellion versus an empire, and the world loses something important when that dimension is replaced by some other dimension.<br />
<br />
Once in a while you get a truly inspired gameworld out of a shooter. The go-to example is:<br />
<br />
<strong>BioShock -- </strong>Its world of Rapture is:<br />
<ol><li>A fallen underwater city</li>
<li>A place where genetic mutation is done purposely and has druglike properties</li>
<li>Set around 1960 in the not-too-distant past</li>
</ol>I think some would argue that the philosophy of BioShock, the Ayn Rand-inspired objectivist themes expressed in the setting and some of the main characters, are essential to BioShock as a gameworld. To me they're the game's fourth dimension, something that added a great deal more depth for certain players but was not fundamentally important to what made the world of the game so interesting and popular. The use of philosophy in BioShock reminded me of the use of philosophy in <i>The Matrix</i>; it shaped certain key characters, made people in the audience who "got" it feel smart, and it worked best as an easily ignored undercurrent. When the Matrix sequels dialed up the philosophizing, people tuned it out. They wanted more more quasi-modern dystopian mayhem, more kung fu, and more visions of humanity struggling against its robot oppressors. No one wanted naked raves, at least not before those other essential requirements were met.<br />
<br />
Now let's speedrun through a few others:<br />
<br />
<b>Halo</b> --<br />
<ol><li>Distant future setting beyond the reaches of the known galaxy</li>
<li>War between humankind and a fanatical high-tech alien collective</li>
<li>Mysterious ring-worlds that are ancient weapons</li>
</ol>If the Halo games were about space combat instead of surface combat, then the world of Halo would be very similar to that of Wing Commander. But Halo and Wing Commander couldn't be further apart as games. It bears mentioning that the core systems of a game heavily influence the sensation given by its world.<br />
<br />
<b>Fallout --</b><br />
<ol><li>Post-apocalyptic America in the near future</li>
<li>The culture of the world was "locked" in the not-too-distant past in an ironic way</li>
<li>Morality is subjective in a society without law</li>
</ol>If BioShock reminded you of Fallout, it's because the worlds have similar characteristics.<br />
<br />
<b>Starcraft</b> --<br />
<ol><li>Distant future beyond the reaches of the known galaxy</li>
<li>War between humankind, a fanatical high-tech alien collective, and a voracious alien hive</li>
<li>The war is waged by soldiers whose personal lives intertwine with their battles</li>
</ol>Starcraft has similar properties to Halo and Wing Commander, far beyond just being in the sci-fi genre. Yet to fans of these games, they all feel very different. You need only change one dimension of a given world design to alter the essence of that world.<br />
<br />
<b>S.T.A.L.K.E.R.</b> --<br />
<ol><li>Post-nuclear-meltdown Chernobyl set in the near future</li>
<li>Radiation has created horrific mutants and strange anomalies</li>
<li>Opportunists and others with little to lose explore the region for its riches</li>
</ol>Let it be known that we Russians love Fallout. S.T.A.L.K.E.R. takes some influences from Fallout beyond just the post-nuclear setting -- it too is a gameworld concerned with the American dream, in a way.<br />
<br />
<strong>Super Mario Bros.</strong> --<br />
<ol><li>Surreal and whimsical world where human characters don't fit in</li>
<li>Comedy-violent interactions in which no one ever really gets hurt</li>
<li>Lots of anthropomorphic inanimate objects, such as clouds with eyes</li>
</ol>When Super Mario got away from dimension #3 in <b>Super Mario Sunshine</b>, the result was an uncomfortable departure from the expected-and-wanted Super Mario experience. Could there be a great Mario game without Mario as the star...?<br />
<br />
<b>Demon's Souls</b> --<br />
<ol><li>Dark gothic medieval setting following a societal collapse</li>
<li>Ancient gods and legendary warriors are reborn with newfound powers</li>
<li>A prevailing sense of purgatory in which there is no release for the dead</li>
</ol>As seems to be the case with a number of these, the third dimension of Demon's Souls is what makes the gameworld very interesting. Demon's Souls also does a good job of fully developing its world along all three of these axes, not just from a fiction perspective but from a systems design perspective as well.<br />
<br />
<div style="text-align: center;">* * *</div>This type of deconstruction is tougher for certain gameworlds, sometimes because they have so much going on in them. The world of <strong>EverQuest </strong>was a hodgepodge of every fantasy trope. It worked great for a while, but EverQuest started losing people when it started expecting people to care about the fiction -- none of the EverQuest spin-off games were particularly successful because the world lacked cohesion. <b>Kingdom Hearts</b> scored a lot of points by featuring recognizable Disney and <b>Final Fantasy</b> characters, but again, the world itself was difficult to describe. The world depended on its audience's preestablished familiarity with its supporting cast of characters, like a videogame version of Who <i>Framed Roger Rabbit</i>.<br />
<br />
Most gameworlds are bland. Typically they have only one or two dimensions. <b>Ninja Gaiden</b> is one of my favorite Xbox games but the world of the game makes no sense -- it's a modern or near-future world filled with ninjas and demons and ancient lore, and that's pretty much it. Being a relatively open-ended game that encouraged some degree of exploration, it could have benefited from a more well-defined world, such as the <strong>Legacy of Kain</strong> series' ancient and troubled land of Nosgoth. (But then, Ninja Gaiden is so good as an action game that this barely even matters.)<br />
<br />
There are also those games that seem to have memorable gameworlds, when they only have memorable characters. <b>God of War</b>. <b>Tomb Raider</b>. <strong>The Legend of Zelda</strong>. These gameworlds defy the kind of deconstruction I've explained here by lacking a sufficient number of specific, defining traits. It's because their real defining trait is their protagonist character -- which, as with Wing Commander's ensemble cast of pilots, can count as one of the gameworld's three dimensions. But if you remove the character from these games, the world loses any distinction. You can't have a Tomb Raider without Lara Croft. You can't have a Zelda game without Link. And you can't have a <strong>Half-Life</strong> game with a wise-cracking protagonist rather than a silent one -- then you'd have <strong>Duke Nukem</strong>. As for my earlier examples, with the possible exceptions of Halo and Super Mario, those are worlds that are arguably defined by their own characteristics, rather than by the characteristics of their protagonists. The upcoming <strong>Halo: Reach</strong> has practically proven already that Halo is bigger than Master Chief. And the world of Super Mario Bros. is so iconic at this point that it can even withstand not having Mario in the spotlight, as we saw in last year's <strong>Bowser's Inside Story</strong>.<br />
<br />
The point being: Unique gameworlds must be created intentionally, as a cornerstone of game projects that merit such an effort, in the service of game experiences in which the world itself is intended to be a major attraction.<br />
<br />
I'm not advocating for all new games to try and create bold new worlds. If exploring and interacting with environments and their inhabitants are not integral parts of the game experience, then the game experience likely does not need to take place in some sort of unique world. A unique world may even be somewhat of a distraction, as in <b>Zeno Clash</b>, an awesome and inspired game whose world design is so out there that I feel as though it might have pushed away some players who really would have liked bashing in bird brains, which is really what the game boils down to. A more-traditional fighting game such as <strong>Super Street Fighter IV</strong> invests heavily in its characters and backstory, but not in the world itself -- the characters may be memorable but the backdrop matters less. A modern military shooter like <b>Battlefield: Bad Company 2</b> likewise invests in its characters because the world itself is the modern world, and the game benefits from bringing players the familiarities of that world, from the weapons to the destructible environments. But certain game genres do benefit from or arguably require original gameworlds, and their creators bear the responsibility of crafting these worlds with the same care and attention as they put into their graphics and game systems.<br />
<br />
What I've described here is not a formula, it's the form of the result. It's creatively bankrupt to attempt to create a gameworld by deriving or mixing and matching three different properties. But do think that one way to gauge a potentially promising world design is to identify its three primary dimensions, and then to make sure that each of these dimensions is fully explored in the context of the world and its stories. This thought process and the associated writing work has been useful to me at least, in my own attempts at outlining various gameworlds I'd want to build or be in.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com10tag:blogger.com,1999:blog-6082533239875181337.post-67171938354003841702010-04-20T23:14:00.000-07:002010-04-21T00:10:01.757-07:00Narrative RecognitionThe narrative of a game should exist only to make the act of playing feel more meaningful, by giving context to the game's systems and scenarios. Even a simple narrative implementation can make a game feel more significant. The simplest and best example I can think of is <b>Space Invaders</b>, the iconic 1978 arcade game whose entire narrative is so conservative, it's limited to the two words of its title. The high concept of defending Earth from evil aliens combined with those expressive-yet-abstract shapes encroaching toward the bottom of the screen to create what's probably the world's first "epic" videogame. But if you took Space Invaders and changed only the name, maybe to something more literal like "Shoot the Sprites", the high stakes wouldn't have been there and players' imaginations wouldn't have run wild from it. The mechanics would have still been great for their time, but I think the narrative is what brought them to life. Space Invaders isn't a typical example of a game narrative, though there's at least some fictional context there, whereas a lot of games have none. It's OK for a game to have little to no narrative, it just better have some truly outstanding mechanics. <b>Tetris</b> might not have needed narrative, but <b>Myst</b> and <b>Puzzle Quest</b> did.<br />
<br />
For these and other games that choose to provide the player with a fictional context, one of the best techniques they can use to draw the player into the experience in a profound and memorable way is to anticipate the player's emotions and expectations about the play experience itself, and recognize them at appropriate times through narrative feedback. 'Narrative recognition' is the shortest term I could come up with to describe this simple and practical technique. It does require some daring on a writer's and designer's part, though like everything else we do to avoid mediocrity, it's worth chancing. Today, as many games have grown more literal in their presentations, the minimum requirement for the player's imagination has diminished. However, for anyone responsible for crafting game content, the ability to imagine what's going on inside the player's head at any given time, and use this to spark the player's own imagination, continues to be key. Autoaim systems and other adaptive-difficulty tricks can make up for players' skill differentials, but I'm referring to the skill of interpreting a player's feelings beyond those of pleasure or frustration, which cannot be gauged as easily as how many health packs he's used or how many headshots he's scored. This is a skill that can only be cultivated from playing a lot of games, observing a lot of players playing games, or preferably both. And I think it's essential to crafting well paced experiences in a certain tone, especially if wit or humor is integral to that tone.<br />
<br />
Think of a game that felt deeply personal to you. I bet you're either thinking of an incredibly time-consuming or competitive game with social elements like <b>World of Warcraft</b> or <b>Counter-Strike</b>, or the sort of game I'm writing about here -- the kind that recognized your expectations as a player and fed them back to you in a surprising, insightful way. The feeling you get from this is the videogame equivalent of meeting someone with the same favorite band as you.<br />
<br />
Sometimes you're lucky to get this feeling early on in a game, such as in <b>Half-Life 2</b>, when in the opening scene, a professor is hammering you with exposition, leaving you free to explore his office... where you'll more than likely knock over one of his computer monitors, causing him to interrupt his speech and chew you out for not paying attention. It's a great little moment. The designers knew you were gonna screw around in there, and placed that little trap for you. In almost every shooter before Half-Life 2, you can bunnyhop like a moron in the middle of even the gravest of monologues. But in Half-Life 2, this opening scene informs you that you have a real presence in this world beyond just the presence of your guns. The rest of the game didn't have such moments in it but the placement of this very first one was important to quickly immersing the player in a world rich with detail, and setting an expectation for bits of comic relief amid all the sci-fi seriousness.<br />
<br />
There are dozens of other examples, though on some level it's surprising there aren't more. In <b>Uncharted 2</b>, relatively early on there's a sequence in which you're introduced to the grenade-throwing mechanics. Nate Drake is well-positioned behind cover as a bunch of thugs bear down on him. Fortunately, a box of grenades happens to be in arm's reach. So of course Drake, speaking for the player, quips something like "well isn't this convenient", referring to the unlimited grenade box while acknowledging the cliché, subverting it, and turning it into one of the game's great self-referential moments. Without that little bit of nudging-and-winking dialogue, the scene would have been just another grenade-throwing tutorial.<br />
<br />
Minor cases like that can be surprisingly poignant. In the classic SNES role-playing game <b>Chrono Trigger</b>, someone at some point makes the joke about how the protagonist doesn't talk much, a profound moment that for the first time points the spotlight at the silent-protagonist trope common to so many games. This same joke then appeared seemingly in almost every other game with a silent protagonist (including Half-Life 2), so it lost its impact after the umpteenth time, but the first few times it was great.<br />
<br />
On the other hand, <b>Saints Row</b> does a brilliant job of subverting the silent protagonist cliché by having the protagonist blurt out some sort of ultra-offensive Silent Bob-style one-liner when you least expect it, just when the story has convinced you to start taking it seriously. It's legitimately funny stuff.<br />
<br />
Then there's <b>Max Payne</b>, in which the hero once dreams he's a killer inside a videogame, in one of the game's most surreal and memorable moments. This too became a tired idea as more and more games fed you the line about how "this isn't a game", hoping you'd never heard it before. <b>No More Heroes</b> gets it right, by breaking the fourth wall on several occasions towards the end, conceding its own ridiculousness in moments that drive the game's self-effacing charm through the roof. 'This <i>is</i> a game' is No More Heroes' message, delivered playfully and perversely, at the height of the player's investment in the story.<br />
<br />
Narrative recognition doesn't require breaking the fourth wall. Another one of my favorite examples is in <b>The Elder Scrolls IV: Oblivion</b>, in the excellent Dark Brotherhood quest line, where you've decided to become a contract killer and work among a surly bunch of assassins who don't take kindly to newcomers. Just as you finally grow to like them and earn their respect, you receive a secret mission to kill them all. It's timed perfectly. You kill scores of things in this game but none are tougher to put down than those guys in the assassin's guild, because the designers made you work for their affection, made you feel attached to them, and only then asked that you turn on them -- a move that's made less despicable knowing that you're all following the same strict code of conduct.<br />
<br />
There are simpler and cleaner examples than this. In the original Halo, the option to invert the controls for looking up and down is couched as part of a diagnostics test at the beginning of the game, when you're learning about your special armor. A lesser game would have thrown this option into a menu and not integrated it into the narrative. But the makers of <b>Halo</b> figured correctly that the last thing a guy like me would expect was a fictional justification for inverting the Y-axis on my controller. All I expected was to be bored by a tutorial.<br />
<br />
What do all these games have in common? They have in common these crafted moments designed to anticipate exactly what the audience is feeling <i>about the game</i> at a particular time, and feed back on those feelings, sometimes merely by acknowledging them. I know you're frustrated. I know you've done this before. I know you don't think you care about these characters. These types of concessions can have a real impact. Narrative reversals are integral to storytelling -- I'm referring specifically to when the game narrative is used to reference the act of playing, not the story itself. Such acts of recognition are at the center of effective game narrative. They're among the most meaningful ways for a game to communicate with a player. One of the best feelings in life is getting what you want without having to ask -- at a restaurant, at work, in a relationship, you name it. Games have the ability to provide this exhilarating feeling using narrative techniques.<br />
<br />
Characters and gameworlds that tend to correctly guess at the player's feelings and feed back on them are the best kinds. They're typically bound to games that don't break when you push at their boundaries, as when you knock over that monitor in Half-Life 2, realizing you can knock over all sorts of shit throughout the entire game. Games like that let you explore the upper limits of the constraints of their rules. In last year's <b>Demon's Souls</b>, one of the first characters you meet in that oppressive and bleak gameworld is a cynical ghost of a man who's given up trying to escape. He more or less calls you a fool for attempting to do better. It's straight-up reverse psychology, and it's fantastic. Here's a game that knows it's challenging. Why shouldn't the world have characters in it who've become frustrated by those challenges? Not only does it fit the fiction, it affirms the player's own first impressions about the game. That ghost is a pretty sympathetic character. But then, if you want to kill him for being such a noob, you can go right ahead and do that too, says Demon's Souls. That game covers its bases, which is partly why its audience likes it so much. Those who gave it a chance tend to make a deep connection with it, because its designers knew you were going to have to fight for every inch in that game, and anticipated and fed back on the range of emotions you'd feel along the way.<br />
<br />
Most games with a narrative component can and should have moments like the ones I've mentioned here, because their designers ought to be concerned with what gives their game its distinct tone, as well as the likeliest emotional dispositions with which their players will approach any given scenario. This happens when designers think of players as individuals rather than as groups. When games speak to you on a personal level, when you experience one of those rare but great moments of recognition and reflection while playing, that's not coming from some guy following up on data from a focus test or gunning for the sci-fi shooter market. Instead, it's coming from someone trying to reach you, with the confidence -- the presumptuous authorial arrogance -- that he knows what you must be thinking at a certain time. How dare he? And yet he really is speaking to you in that moment, through his game.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com10tag:blogger.com,1999:blog-6082533239875181337.post-73239063572005504922010-04-06T22:43:00.000-07:002010-04-07T12:12:20.406-07:00Proper VillainyConsidering how many games exist for the promise of bringing you exciting action and adventure, it's a shame how few of them have memorable villains. Like a good story in general, a proper villain can help motivate a player to push his way through a game, past the difficulty spikes and through the inevitable rough patches, by adding meaning and context to the game mechanics as well as the promise of more variety and surprises. There are a few reasons why villains are hard to do in games, but games like <b>Portal</b>, <b>Legacy of Kain: Soul Reaver</b>, <b>Final Fantasy VII</b>, <b>System Shock II</b>, or even <b>Super Mario Bros.</b> and <b>Mike Tyson's Punch-Out!!</b> are evidence of why investing in a proper villain is worth it.<br />
<br />
One reason there are so few proper villains in games is implied by the word itself: The concept of villainy is kind of dumb. It's not how the world works. In reality, what happens is that when two people want opposite and mutually-exclusive things, they enter into an antagonistic relationship. Villainy is just an extreme form of antagonism where, most often, either the antagonist's motives are not rational or simply not well-developed. Videogames' misguided attempts at villains usually hinge on grandiose schemes such as destroying the world or other sadistic, evil acts. They're bad guys who overcompensate for their flat desires with huge lifebars. But it's impossible to relate to their motivations so these villains are doomed to obscurity. Instead, a proper antagonist gets under your skin and makes things personal in a way you could understand, even appreciate. Portal's GlaDos, despite being a machine, has the attitude of a spurned lover taking passive-aggressive revenge on a relationship that's slipped from her grasp. In Super Mario Bros., Bowser wants the Princess just as much as you. It's ironic that inhuman characters such as these turn out to be much easier to empathize with than the dime-a-dozen megalomaniacs waiting for you at the end of most games. But that's the key -- if the antagonist is impossible to empathize with, then he's just another villain, and more than likely doesn't have the substance to be memorable as a character.<br />
<br />
There's a more-practical reason why it's tough to have a proper antagonist in a game, which is that most games in the action or action adventure genres are designed around kill-or-be-killed scenarios, leaving little room for character development. When they present you with an antagonist character and a combat situation, one of you needs to be defeated and it's not going to be you if you keep trying. So then, either the antagonist is knocked out of the game or you get the cliché of the antagonist escaping just in the nick of time, or even worse, the one where he beats you up in a cutscene after you kick his ass in-game. What many games do to counteract this is they present you with a hodgepodge of disposable antagonists, in the form of different boss characters and such. But the narrative consequence is that the forces of antagonism in the game are diluted. Unless it's <b>Metal Gear Solid</b>, the story likely doesn't make time to develop most of these characters, and the artists and combat designers have to carry the burden of making them interesting when the fiction should be holding up its end of the bargain.<br />
<br />
Conversely, the reason why games like Portal, System Shock II, <b>BioShock</b>, <b>Batman: Arkham Asylum</b>, and even Punch-Out!! succeed with their antagonists is that their stories are structured around an ever-present-but-physically-inaccessible antagonist, someone you're always aware of but can't get to until the climax of the game.<br />
<br />
If a gameworld cannot support the idea of an ever-present but physically-inaccessible antagonist, then the burden is on the enemy faction to be empathetic, assuming this is compatible with the aesthetic of the gameworld. The enemy faction or factions you're fighting -- the various goons that populate the gameworld and are the predicates of the gameplay -- might as well be interesting. There's really no downside. And giving them empathetic qualities is a good way to make them interesting in most cases. In <b>Geometry Wars</b>, the evasive little green shapes are the best, most memorable enemies in the game because they have an empathetic sense of self-preservation. In <b>Halo</b>, the little Grunts freak out when you kill one of the Elites leading them into battle. In <b>Panzer Dragoon Orta</b>, the hordes of enemies forcing you to dodge a hailstorm of bullets panic as you gun them down, making you think about what it must be like to be on the bad guys' side in a shoot-'em-up. In <b>Plants vs. Zombies</b>, the zombies are sincerely hungry for brains -- you'd want to give them your brains if you didn't need them. Since most traditional games revolve around violent conflict, in these games, the forces of antagonism ought to express empathetic behaviors, even in the strict confines of a combat encounter. It's totally doable and relatively inexpensive in many cases, just the cost of writing and audio in many cases (plus a high premium in scripting, animation, and artificial intelligence for all the shooters out there). Even <b>F.E.A.R.</b>'s genetically cloned supersoldiers in their full body armor show a shred of humanity in their final moments simply by saying "Oh, shit...!" as you strafe around the corner in slow motion with your shotgun drawn.<br />
<br />
While memorable antagonists are rare, antagonists are some of the most memorable characters in games. That's because they often present far greater opportunities for character development than protagonists do. Look at games like BioShock and Portal, whose protagonists primarily serve as vessels for the player to immerse themselves into the experience, yet whose antagonists are extremely well-crafted, remarkable characters. Part of why the combination of invisible-protagonist and ever-present-antagonist works so well in these games is that, when the climactic moments of the story crop up, the antagonists' escalating actions feel very personal. And when these highly motivating personal affronts are coming from characters whose own motives you can empathize with on some level -- characters for whom the old "we're not so different, you and I" speech goes without saying -- you're more likely to be playing a game that's going to stick with you after you're finished playing it. Which are the kinds of games I most like and most want to make.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com23tag:blogger.com,1999:blog-6082533239875181337.post-37579763418752244952010-03-29T22:47:00.000-07:002010-03-29T23:27:20.851-07:00The Three -MationsI consider a game's story to be the subset of narrative content authored for that game, which the player interprets to have some coherent meaning. The meaning does not necessarily need to be placed there purposely by the game's creators, it just needs to be perceived by the player through the intuitive pattern-matching we conduct as we go about trying to find meaning in all things. Story is just one of many types of feedback games can employ in response to the player's input. Thinking of story as another form of feedback, I think, is the key to tapping its potential in games -- as well as the key to integrating it into the design process in an appropriate way, while mitigating risk of the story derailing or constraining the design.<br />
<br />
Game feedback, in general, provides information, confirmation, and affirmation. Story is no exception; I can draw an analogy between story and user interface design. In <b>God of War III</b>, a big spinning "O" button next to a prone enemy carries a specific, almost Pavlovian connotation: Here lies an enemy that you can savagely murder if you get close to it and press the corresponding button. The UI prompt is a reward, affirming your combat skills; it confirms the availability of a unique set of killing moves; and it informs you of the input required to access those moves. Good interface design in games is contextual and just feels right, in this fashion, because it's closely linked to player input and the affordances of the interface match the aesthetics of the game in general or the input in particular. Think of "You Are Dead", the game-over screen in <b>Resident Evil</b>. It works like a consolation prize, not a punishment. It's a pretty good screen.<br />
<br />
Linear noninteractive game narrative tends to be ineffective because it's disconnected from the player's actions. However, there are numerous games with lots of noninteractive cutscenes that are still considered to have outstanding stories in them. These games range from <b>Grim Fandango</b> to <b>Metal Gear Solid</b> to <b>Mass Effect</b>. How is it that these examples break from the popular player-elitist idea that linear story is a bad thing for a game? The answer is that, in addition to having these lengthy story sequences in them, these games do the important small stuff too: inform, confirm, affirm through the story.<br />
<br />
In Grim Fandango you can share your balloon animal shaped like Robert Frost with various characters, leading to unexpected comedy. In Metal Gear Solid, a character called Psycho Mantis looks for saved data for Castlevania: Symphony of the Night on your memory card, breaking the fourth wall as he points out your gaming preferences. In Mass Effect, you can shoot one of your party members dead if you don't like the way he's acting. By affirming the player's actions in these types of cases, these games inform the player of a wider-than-expected possibility space of interactions, which the player later confirms (or does not confirm) through additional interactions along the periphery of that space. These are examples of story working at its best. It's supported by a rich linear narrative in all three cases, which cushions these smaller, more-important story moments in deeper meaning. The result is three very different yet rewarding experiences that share in common a story-driven structure, where the player's input is acknowledged via story mechanisms and not just interface prompts as in God of War III. Nor are these games' stories simply playing out without respect for the player's actions, as is the case with many games reviled for their flashy noninteractive stories.<br />
<br />
<b>Animal Crossing</b> is another excellent game that uses these types of techniques but does not have story in the traditional sense, because (following my first statement) it has no coherent meaning behind what happens in the story -- except for the thinnest possible premise of "Tom Nook gives you a home loan and eventually you pay him back." The game has the perfect amount of story for something whose underlying meaning concerns the simple pleasures of life. But even though Animal Crossing would never be considered a game story on par with Grim Fandango, or Metal Gear Solid, or Mass Effect, it is just as effective in its application of game-story principles. One of my favorite examples of this is in the game's clothes-making mechanic, where you can "paint" clothing patterns and put them on display in the local clothes store. This type of player expression is very common in games, which routinely let you change your character's hairstyle, paint your car, and so on. However, Animal Crossing takes these types of systems a step further by affirming your efforts, as when you find one of your town's animal residents wearing that shirt you made and complimenting you for your artwork.<br />
<br />
Games rarely go to the trouble of confirming, let alone affirming, this type of player expression, as though we're all so confident in our ability to express ourselves that we don't want the world to judge or acknowledge our efforts. But, if you'll forgive another one of my analogies I've been meaning to commit to writing, think for a second about what happens the day after you get a new haircut. Either you're fishing for (or at the very least you're open to) compliments on your new look, or, if by some chance you're someone who knows her hair looks excellent, I figure you at least expect people (even just certain people) to notice the change. Conversely, you'd feel bad if no one noticed or seemed to notice. Doesn't mean you want to be fawned over in the way certain games vomit praise on you for your basest actions, like a mother indulging a spoiled child. You're sharp enough to observe subtle cues, as when someone who never once paid you a second glance does a quick double-take. And what a rush that is. Story in games should serve this end. All it really needs to do is acknowledge the player's input in a way that seems to give meaning to the player's actions, by being personal or specific or both. It also doesn't need to use a lot of words or cutscenes to accomplish this.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com5tag:blogger.com,1999:blog-6082533239875181337.post-14212176006512160012010-03-28T19:42:00.000-07:002010-03-29T19:47:49.771-07:00The Gift of TormentReleased with no fanfare in December 1999, <a href="http://www.gamespot.com/pc/rpg/planescapetorment/index.html"><strong>Planescape: Torment</strong></a> was one of the best games of the year largely on the strength of its one-of-a-kind story about immortality and human nature. Even though it wasn't a commercial success, I believe it's one of the most influential role-playing games of the last decade and ideas it pioneered have since found their way into much better-known games (mostly from BioWare), such as <strong>Star Wars: Knights of the Old Republic</strong> and <strong>Dragon Age: Origins</strong>. Apart from the overall quality, size, and depth of the game's ambitious story, on the surface Torment was basically just another Infinity Engine game, a "total conversion" of Baldur's Gate with a weird cast of characters and <a href="http://www.imdb.com/title/tt0187405/">an awesome voice cast</a>. But even though Torment relied on the conventional mechanics of the time, I believe it introduced a radical idea that's had a profound influence on story in Western RPGs: player dialogue with subtext.<br />
<br />
<a href="http://2.bp.blogspot.com/_KMcEkwHzrOw/S7AcJHvfzrI/AAAAAAAAAAw/9X6kmvD6PWc/s1600/187975_pc.jpg"><img style="float:right; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 116px; height: 144px;" src="http://2.bp.blogspot.com/_KMcEkwHzrOw/S7AcJHvfzrI/AAAAAAAAAAw/9X6kmvD6PWc/s320/187975_pc.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5453890091768336050" /></a>In other words, Torment is the first RPG to introduce player intent into dialogue, which may be contradictory to the substance of the dialogue -- it's a game in which you can say one thing and mean another, and use this to deliberately lie at times, by means of the authored choices presented to you.<br />
<br />
In a typical RPG, you might be asked by a character to retrieve an item, and tell that person "Yes, I'll do it" even if you as a player don't really know if you're going to do it or not -- probably you just want the quest logged in case you stumble upon it. You don't think about these types of interactions, and, as evidenced by the completely disposable text content for quests in games like World of Warcraft, they do little to build a meaningful connection between you, your character, or the gameworld. But in this same type of situation, Torment typically would give you at least two options: "Yes, I'll do it" (Truth) and "Yes, I'll do it" (Lie). And it would fully support these choices -- lying would affect your character's moral alignment, leading to other changes in gameplay. But even when it didn't really matter whether you told the truth or not, the game made you stop and think about what you were saying.<br />
<br />
I remember encountering this type of choice in the game for the first time and feeling frozen in my seat -- never before had I considered my options so carefully around a straightforward dialogue choice. Some previous RPGs, such as Fallout, might have let me play as a smartass, who might make a sarcastic quip instead of answering a question directly. But no game prior to Torment made me feel like I could, if I so chose, look another person in the eye and lie to him with a straight face.<br />
<br />
Plenty of RPGs before and after let you play as morally evil characters, letting you randomly kill people if you want, usually just after saying something terrible to them. But this type of psychopathic villainy, while potentially exciting for a little while, tends to feel hollow because your ability to empathize with your character rapidly breaks down as you start massacring entire towns and looting people's corpses for their boots and gold. It's out-of-character and not the "right" way to play, even if it doesn't outright break the game. On the other hand, in Torment you could do some really deceptive, scheming stuff simply through talking to people -- and it made you feel connected and close to that evil, because everyone knows what it feels like to lie, and in Torment you have reasons not to be up front with everyone you meet. As well, the option of lying made the default act of telling the truth feel more consequential. By letting you get inside your character's head as well as your own head, Torment created such a strong connection with players like me.<br />
<br />
It took years for anyone to improve on Torment's basic idea of letting you determine your character's intent and not just the content of his speech, but the <strong>Mass Effect</strong> games finally took this a step further through their system of subtext-driven dialogue. In those games, it's genuinely exciting to see the protagonist act out your dialogue choices, because you don't know exactly what Shepard is going to say or do -- you tend to just pick the emotion or intent behind the outcome you want, and your reward is seeing Shepard act it out faithfully, in most cases. The basic consequence of this is that dialogue sequences tend to be worth watching and listening to, something that's rather important for a game that's bothering to have tons of story content.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com11tag:blogger.com,1999:blog-6082533239875181337.post-41499286937518851482010-03-28T16:10:00.000-07:002010-03-29T19:48:44.894-07:00The Story So FarI have a lot to say about games. But I started bottling it up a few years ago when I left my position as Editor-in-Chief of GameSpot to become a producer at Electronic Arts. At the time, I felt I had given up my right and authority as a critic of the game industry, because I'd accepted a job at one of the biggest publishers in the business, and -- on the surface at least -- that meant I had a vested interest in the success of my new employer. In August 2009, I left Electronic Arts behind, moved back home to the Bay Area, and took a job in the publishing division of 2K Games. For whatever reason, I'm less concerned now than I used to be that my words may be misconstrued. So I've resolved to use this space to write about the subject that interests me most, irrespective of my current job. That subject is the idea of games as stories.<br />
<br />
As a producer on the <strong>Command & Conquer</strong> series, I started keeping a blog under pseudonym, which served as a sort of diary of my journey into game development. I maintained it for about two years but deleted it shortly after finishing my first full project, Command & Conquer Red Alert 3. I'd grown sick of the sound of my own voice in that blog, which threatened to become a list of predictable disappointments -- self-indulgent Internet tripe. The difference this time is that I have the guts to use my own name and have the focus to meditate on a specific topic and its far-reaching implications. This is a topic I like so much that there's no room for complaint.<br />
<br />
There are a lot of very smart people writing about game narrative. This made me reluctant to weigh in, especially since many of them have achieved much more than I have. However, I've decided that I have a unique-enough perspective on the subject that my thoughts and views on games-as-story may not be so redundant or unnecessary, that they may be worth writing and sharing. You can be the judge of that, but either way, the act of writing critically on this subject helps me to better understand it on my slow pursuit of mastery over it -- a journey that, thankfully, I'll never get to the end of, for if I did, I'd surely find a great emptiness waiting for me there.<br />
<br />
What makes me think I have something worth saying about game storytelling or narrative? This was a scary question. But I decided I have some legitimate qualifications, not the least of which is my background as the chief editor of a popular gaming publication that contributed to collective consciousness about what constitutes a good game story in the first place. There I presided over our reviews of games in general and authored many hundreds of them myself. I reviewed many kinds of games but my specialty was around narrative-driven games, including Western and Japanese role-playing games, action adventure games, certain shooters, and so on. In addition to my background as an editor and game critic, I studied English literature in college while working at GameSpot. And prior to getting into game development, I wrote game stories extracurricularly, while studying story structure and the way narrative works. I've since done uncredited game writing on a number of projects, especially <strong>Red Alert 3</strong> where I designed many of the characters and unit personalities in that game, and wrote much of their dialogue. So I've had a chance to apply some of my thinking and the results were encouraging and enlightening.<br />
<br />
The name of this blog is a reference to the classic <strong>Ultima</strong> series of role-playing games, and its three core moral principles, which are central to the stories of the best games in that series. <strong>Ultima IV</strong> and <strong>V</strong> are two of the most important games I've ever played, and that series is fundamental to my understanding of the potential of game narrative, so it's only fitting that I refer to it here. Besides, I think those three principles are essential to crafting any game narrative of sufficient quality.<br />
<br />
I will always be a student of games. I'm just old enough now to where I feel embarrassed at not trying to share some of what I think I might know. Thanks for reading and I look forward to our conversation.Greg Kasavinhttp://www.blogger.com/profile/06022059960212889807noreply@blogger.com5