Over The Flagpole: Escape as Art

I got into a conversation the other day with a friend of mine, a comp lit grad student. Her familiarity with gaming being somewhat limited, and my love of pontificating being extreme, I gave her a quick re-hashing of the old Roger Ebert "Video Games Can Never Be Art" discussion (a conversation I usually shy away from, since Ebert is a) obviously wrong, and b) probably arguing in bad faith for his own amusement). That argument/conversation morphed into a more interesting one, which I'll try to summarize here.

For me, a game becomes art when its mechanics and interactivity - the things that define it as a game as opposed to a series of pictures or a movie or a novel - make a meaningful statement about reality. Jonathan Blow's Braid is the obvious example, with its themes of perfectionism and regret amplified by the game's time-manipulation mechanics. (More recently, Molleindustria and Jim Munroe's game, Unmanned, examined the disconnect between Americans and the consequences of their actions by forcing players to divide their attention between two screens, one displaying dialogue choices and the other arcade-like mini-games related to the life of an American drone pilot). It's obvious to me that games can be designed to be art.


But the question that nagged at me while thinking about the issue was this: Can games generate art (or at least, artistic moments) without designer intent? Not just in the sense of unintentional meanings being found in the design, but as an expression of player freedom (hypothetically one of the key tenets of game design?)

One of Ebert's major contentions against video games is that, by giving up control to the players, a game's designer can never express a singular artistic vision the way a director or an author can. What he doesn't understand is that game designers don't give up control - they incorporate it into the stories they tell. (Most) games are not designed to play themselves - they expect certain actions from players and respond in turn. The design of a game is not just the world the player moves through, but the actions the game allows the player to take. In fact, the whole point of much of game design is to constrain player actions to the ones the designers want. Going even further, pieces like The Stanley Parable* make the case that ANY freedom in a game is an illusion, since the world is entirely constrained by the designer's intent. The only choice is to play, or not to play.


Even open-world games, touted for their openness to player choice, exist as shallow ponds, surrounded on all sides by the inflexible nature of the rules that make up the system. Most games that talk about freedom are actually talking about adding more rules, more systems into the game. Oh, you can own your own property in this one! - Once we've defined what property is, how it's purchased, and what benefits and effects it conveys in game. The system either tightens - you can romance many of the cast in Bioware RPGS, each of whom requires extensive scripting, animating, and writing - or becomes painfully vague - you can romance almost anyone in Fable III, but only by making the process generic enough to be described with extremely flexible rules. In either case, all actions are still defined by the rules supplied by the designer, and all "art" is the product of the designer's intent. But can the interaction of the rules themselves, divorced from the artist's goals, produce art?

All this got me thinking about Langton's Ant.


The Ant is a very simple (hypothetical) mechanism that produces very odd results. Existing on a grid of black or white squares, the ant moves according to two rules: If it encounters a white square, it turns right, flips the square to black, and moves forward. If it encounters a black square, it turns left, flips the square to white, and moves forward.

As you might expect, for the first several thousand iterations of these rules, the Ant produces a chaos of black and white squares. But then... (And this happens regardless of the initial black-and-white makeup of the grid, although "obstructions" may delay the process), the Highway emerges. The Ant begins to build a long, diagonal pathway away from the central pattern, made up of identical 104-step loops. In the most basic version of the Ant, this occurs at around 10,000 steps. Which is to say that, coded in those two very simple rules is hidden information about the incredibly complex behavior that occurs in their 10,000th iteration.

Video games have a lot more than 2 rules.

Obvious news flash: Game designers don't physically build the games we play. Instead, they lay out rules that describe the world they've imagined. If the rules are well crafted, the world is constructed to the designer's specifications, and the player is "trapped" within that design. They can only have the experience the designer WANTS them to have - any art that occurs in that scenario has been dictated by the designer, with the player acting, essentially, as a prop. But, as we just learned, rules can be tricky... And, really, what's a bug? A rule that's not doing what it's meant to.

Sometimes a bug in a game is there because someone miswrote a rule - a variable was mis-set, a step was left out. But sometimes it's because the rules are interacting in strange ways, ways the designer never intended.** Rules related to how player movement works intersect with rules defining how surfaces behave at corners... and suddenly you're on the other side of the wall.


There are whole communities built around these glitches. Speedrunners, especially, delight in finding ways to "break" the game to improve their times. But it occurred to me that there's something artistically meaningful in these sudden bursts of freedom - perhaps the most meaningful message games can convey. The artist loses control of his or her art - or, maybe, the rules themselves become inadvertent artists, working in concert with the players.

The example that comes to mind, that maybe this whole discussion builds out of in the back of my mind, is from the first game I ever owned: Super Mario Brothers. Every non-castle level of SMB ends the same way: the player guides Mario to the end-of-level flagpole, touches it, slides down, and control is taken away until the start of the next level. The flagpole stands as the edge of the designer's intended play area.

Which makes for a disconcerting experience when you realize you can jump over it...

Now, there are very few areas in the game where this is possible without cheating (although, now that I think about it, the use of cheat devices like the Game Genie to alter gameplay is ALSO a way for players to defy or circumvent the designer's intent by interacting directly with the game's rules). The easiest is in World 3-3, where there is a player-movable platform directly before the goal (probably significant that this trick is only possible in one of the rare parts of SMB where the designer gives control of the environment to the player). With good timing and a proper running start, Mario can leap OVER the flagpole, escaping the intended bounds of the playable area. Moving past the castle, Mario can now run along a featureless brick wall, unable to backtrack... until time runs out and he dies. Technically, it's pretty non-climactic.

But, as a kid, it was an incredible moment. I had ESCAPED the level. I was free from the designer's plan. I had done what wasn't expected.



Now, I'm not trying to suggest that this is some horrid violation of the universe's physics that would make Shigeru Miyamoto rip out his hair in a dark rage. It's clear that Nintendo knew about this glitch, and added a placeholder area behind the flagpole so that the game wouldn't crash. But the rules of SMB are exceptionally clear: the flagpole is the edge of the world. You can't jump over it, you can't escape. In the language of the game's design, it's a solid brick wall.

But by colluding with the rules, I beat the design. Experienced a moment of authentic-feeling freedom in a world entirely bound by constraints.***

It felt like art to me.



*The Stanley Parable is an excellent freeware mod for Valve's Source Engine. You can download it here, and I strongly recommend it. I'll probably have a post about it up in the next few weeks, but it's a game that deserves to be played before you read about it.

**Interestingly, combos, the backbone of most competitive fighting games, stem from a glitch in Street Fighter II that allowed players to chain moves together. Glitches like these often end up becoming part of high-level gameplay in competitive games, basically allowing the interactions between the rules, and the player's ability to take advantage of them, to trump initial designer intent.

***One of the factors behind the success of Valve's game Portal (besides being excellent), is how well it simulates this feeling. The entire first two-thirds of the game function as a metaphor for the game player, being forced to complete ridiculous, arbitrary tasks by an inflexible machine. The moment where the player breaks free of GLaDOS's control, escapes the fire, and breaks into the "backstage" is an in-design attempt to recreate the same freedom I'm trying to convey in this post. Of course, it's fake freedom... But it talks to the same part of the gamer mind, I think.

Timed Hits Part 3: Gems, Tiles, and Beats

This is the third and final part of "He knows WAAAAAAAY too much about Timed Hits," a series of posts on how game developers have used and modified the mechanics of RPG combat over the years, and what it can tell us about the genre. Part One, dealing with the inclusion of action and timing elements, can be found here. Part Two, an in-depth look at how standard RPG combat is refined and enhanced by increasing player choice, here.

In this conclusion, I'd like to look at games that have approached the issue of RPG combat by avoiding it - by throwing out "standard" combat systems entirely in favor of more unorthodox choices. These aren't games like Call of Duty, where the progression mechanics of role-playing games are used to enhance an established genre. They're not even true hybrids, like the Shooter/RPG Mass Effect 2, which play like a deliberate cross-breeding of genre. These games, in my eyes, are still fundamentally RPGs*, but ones that have replaced their combat systems with a separate but equal alternative.


I want to examine these games, not because I'm dismissive of RPG combat as it stands (I think this series makes it clear that, on the contrary, I've thought FAR too deeply about it over the years), but because, by transposing new systems into the place of the old ones, we can figure out what makes this genre so compelling and long-lasting.

RPG combat is a metaphor, an abstraction meant to represent the hectic back-and-forth of a real battlefield. At the same time, it's meant to give the player a feeling of connection to their character's actions, with menus (or other combat control systems) representing the choices available to the characters. If games are about simulating experiences that the player couldn't have in real life, then the following games approach that old goal of simulation in new, innovative ways.


1) Puzzle Quest

Infinite Interactive's Puzzle Quest created a slight stir back in 2007 by adapting a Bejeweled-type Match 3 game as a battle system for an otherwise typical fantasy RPG. The player moves around a map, solving quests, searching for treasure, fighting monsters. And when it's time to fight... Out come the gems!

During combat, the player takes turns with the AI, moving pieces on a Match 3 board, trying to line up gems to fill their various mana bars or deal direct damage. Matches of four or five provide extra turns and bonus effects, and much of the strategy relies on making optimal moves for yourself while denying strong moves to your opponent.


The RPG elements come into play by allowing either side to vastly modify the play field. Both player and opponent are equipped with a wide variety of spells whose effects range from direct damage, to massively skewing the distribution of gems on the field to a particular color, to destroying certain gems for a big boost in power. At the same time, player equipment and stats modify the effects of matching gems (generally increasing mana earned or damage dealt per match).

One of the ways that I like to judge games like this is by seeing how they represent different enemy "types". In Puzzle Quest, a "fast" enemy will have low HP, but plenty of cheap, quickly recharging spells. A "mage" will have a few cheap abilities designed to funnel mana to him to fuel his expensive, devastating spells. A "warrior" will have straightforward spells and a bonus to his damage for matching skulls (the direct-damage gem type). Fights become a matter of learning how to control the battlefield and counter your enemy's specific tactics (for example, denying a fire-based enemy access to the red gems he'll need to cast his spells). These mechanics allow the player to get a sense of what it would be like to fight these creatures that is both separate from, and parallel to, the sense they'd get from battling such monsters in a more traditional RPG.


2) Bookworm Adventures

Of course, Infinite Interactive was following in Bejeweled creator PopCap's steps in more ways than one with Puzzle Quest - the puzzle-game-as-fighting thing had already been done a year earlier by the kings of gem destruction with Bookworm Adventures, an RPG spin-off of their popular Boggle clone Bookworm.

Compared to Puzzle Quest, the combat in Bookworm Adventures (and its sequel, released in 2009) is ridiculously simple. You have a grid of letters. You spell words with them. The longer the word you spell (and the more difficult the letters used), the more damage you do to the opponents who are bashing away at your health after every word spelled.

What BA lacks in complexity, though, it makes up for in charm, and in visceral thrills. Lex, the titular bookworm, is cute as hell, and his vocal clips and dim-witted taunts are often delightful (not to mention the always-hilarious descriptions of enemies, most of whom are parodies or direct lifts from fables, nursery rhymes, and works of literature).

But the real appeal of the game is the slow construction of perfect words, the thrill of tapping away at your enemies with "and" or "boat" or "car" as you wait for the final letter that will let you unleash "extraordinarily." The battle animations support the joy of it, ranging from a simple head-bop by Lex to an earth-shaking blast of vocabularial power. (Note: Do not try to use "vocabularial" in Bookworm Adventures, it is not a real word).

The RPG mechanics are limited - Lex levels up automatically as you play, slowly increasing his basic stats. And a new treasure is gained at the end of every level, two of which may be brought into the next to produce a bonus or defend against certain status effects. But to me, it's still a great RPG, because of the way it translates my mental struggles into in-game awesomeness. Blowing away the Monkey King with "devastated" felt as intense and real as blasting Sephiroth with Knights of Round did when I was 13.


3) Sequence

Confession time: When I started this series, two months ago (Ye gods, do I write slowly), it was initially as an EXTREMELY roundabout way of talking about a game that I felt had redefined RPG combat in an important, enjoyable new way, and which quickly became one of my favorite games of 2011. That game was Sequence.

The first game from the two-person team Iridium Studios (plus two musicians and a handful of voice actors), Sequence is one of the strongest gaming debuts I've played in a long time. The plot, which starts with a standard "guy-wakes-up-in-a-mysterious-place" premise, quickly expands to include warm, memorable characters, hilarious meta-musings on the nature of gaming, and, ultimately, strong questions on the nature and value of free will. I could write an essay on it (and probably will), but the focus of this article (and no one would blame you for forgetting, given how many parenthetical statements (including this one) I've been making), is on combat. And the combat in Sequence is sublime.

This is going to get a little complicated, so if my ramblings stop making sense, just skip this paragraph and watch the embedded video from Iridium's Jason Wishnov talking about the game (and even if you do understand, you should watch the video to see it in motion - plus, it's pretty funny). Combat in Sequence, to quote Wishnov, is a "mash-up between a rhythm game and a traditional RPG." When combat begins, a song starts playing. The player is presented with three small screens, each with a DDR-esque row of arrows at the bottom. One screen is for Defense - arrows that fall here represent enemy attacks, and must be blocked with well-timed player input or damage will be taken. Another screen is for casting spells - the only way of doing damage to opponents. The player chooses an equipped spell and activates it - causing a specific sequence of arrows to fall. Failure to input the sequence causes the spell to fail, doing nothing except wasting mana. The third screen is for re-charging the mana used to power spells - there's no consequence for missing notes here, but if you don't pay attention to it, you'll run dry and be unable to activate any of your attacks.



The tricky part here is that only one screen can be active at a time - necessitating a constant cycling as you deflect attacks, charge your mana, and execute the often-tricky sequences needed to unleash attacks. In essence, this means that your true enemy in these fights isn't the gorgeously drawn monster you're facing (which is really just a pool of hit points and an attack and defense stat to modify damage given and received), but the tempo and beat of the song currently playing. Timing becomes the most crucial consideration of every move - a powerful spell might be unfeasible if its steps are too complicated, or its sequence takes several seconds to input, seconds where you're either taking damage or frantically flipping between screens to block. The tension of dividing your attention, watching all the parts of the "battlefield", and waiting for a moment when your opponent's attacks flag to strike... It's as pure a sensation of "being in a fight" as any of the other combat abstractions I've encountered in more traditional RPGs.

When I finally tapped into that feeling, it made me realize that that's the element I seek out in games like this. The adrenaline rush of pitting my mind and hands against an opponent, of formulating desperate plans and executing them with my tongue clenched between my teeth. And Sequence made me realize that that feeling is core to the joys of the RPG, and that it transcends whatever metaphor a game uses to convey it - whether it be timed hits and Judgment Rings, or job systems and wordy menus, or deadly beats and falling arrows.

If there's a lesson to be taken away from all this, it's this: The battle is what matters, not the skin it wears.

At the risk of being a terrible shill, I'd like to point out, here at the end of this series, that Sequence is available on XBox Live Arcade and Steam for $5 (and it often goes on sale). If you love RPGs, and even only like rhythm games, you owe it to yourself to play it.



*If one of the points of this series was to consider what, exactly, "RPG" means, by excluding elements of narrative design and focusing solely on combat, I have to conclude that, in this regard at least, the series has failed. Having examined as many combat systems as my feeble memory could present me with, I've become a little flummoxed by the sheer diversity of the genre. The only similarity I can find (and even here I'm generalizing horribly) is the common sense of disconnect between the player and the action on the screen. Menus, swapping gems, even things like Shadow Hearts' Judgment Ring, all stand in between what the player experiences and what the character does. Even in games that give direct control to players, the character's stats still modify the effects of player action in a way that, say, the character in Modern Warfare does not. If Zelda's Link was meant to be a "link" between the game world and the real world, then perhaps an RPG character is defined in the way they don't link, in the way their existence stands between and modifies the difference between the player and the game.

Gunpoint: Where Player Freedom Becomes An Artform

Tom Francis is one of my favorite gaming writers. He works for PC Gamer UK, and has been responsible for some of my favorite features written on the ways players can explore and engage with the games they play.

You can always tell one of Tom's reviews by the glee with which he approaches the subject. They're full of breathless descriptions of bizarre or interesting situations the games let him get into, dumb, fun tricks he's logic'd himself into trying. For instance, take this example from his review of Deus Ex: Human Revolution:

He’s inside gang territory, trying to make it to a door at street level. He decides to use the surprising development of a vending machine falling out of the sky to distract the gangsters, so that he can drop down and get to the door without attracting attention. A sort of pepsi ex machina.

Jensen hurls the vending machine arbitrarily and tumbles off the building after it. His Icarus Landing System kicks in, floating him safely towards the street below in a dazzling ball of golden light. When the vending machine crashes to the ground, the armed gangsters nearby all look at it in surprise. Then they look at the dazzling ball of golden light floating down to land across the street, and they draw their guns.

Francis's critical perspective on games seems fueled not so much by the choices and scenarios that games force on people, but by the ones that they allow. His writing celebrates games like Deus Ex for allowing the player's own mad ideas to be a major factor in their success. As such, it's not surprising that when he decided to design his own game, it became something like an art studio for brilliant works of player creativity.

It works like this: Tom's game, Gunpoint, is a stealth platformer about breaking into buildings without being shot by some EXTREMELY trigger happy guards. The levels are full of interactive elements - light switches, door panels, cameras, alarms. On the surface, these are all on the side of the guards, systems in place to thwart your hero, Conway, from reaching his goal. Except Conway has an ace up his sleeve (also: springs in his pants, but that's neither here nor there): The Crosslinker.


Mousewheel up, and you enter Crosslink mode. All of the details of the level fade into darkness... Except the devices. Those light up like lights on a Christmas tree. And, like a child opening his presents on Christmas morning, you can start to play...

Drag a line from any device to any other to connect them. A light switch will now open a door. A guard walking through a motion sensor will call an elevator to his floor, distracting him. Re-wire a hand-scanner so that, instead of opening the door it's connected to, it activates the scanner on the other side, activating the door in the opposite direction, slamming into the guard and knocking him out. The Crosslinker turns every level into a playground for crazy Rube Goldberg machines and nasty pranks.

The brilliant, compelling thing about this design is how unnecessary most of these tricks are. Gunpoint is built so that brute force is almost always an option; guards can be pounced from behind and knocked unconscious; you can even buy a gun and shoot them dead - although, in keeping with the idea that this is a stealth game, gunshots will quickly summon difficult-to-avoid-snipers at the level exit (although even these can be avoided with enough upgrade points invested in a bullet-deflecting belt). Even when using the Crosslinker, there are a few simple moves (the aforementioned suicide-by-door trick, for instance) that can be used over and over to clear levels... efficiently. You could play it that way.

But most likely, you won't. Instead, you'll sweat, and puzzle, and play, until you've found a convoluted, beautiful solution to your problems. Because you can.

The motivating philosophy behind Gunpoint is, I think, that if you give players freedom, and have faith in them to use it, they will. You don't HAVE to set off a cascade of opening doors, moving elevators, blaring alarms, and darkened hallways that culminates in a man being electrocuted by a light switch. You do it because it is, objectively, awesome. And it is equally awesome that the game allows you to do it, with no scripting or forcing. The only motivating desire is the desire to do something great with the vast, flexible tools provided. It's the difference between "Man, that game just did some awesome stuff," and "Man, I just did some awesome stuff."

It's challenging, refreshing, rewarding. I expect videos of Gunpoint solutions to be a big hit on Youtube (and I'm quietly hoping Francis will implement some basic video-capture elements into the game to make sharing mad, inspired solutions that much easier). Because who doesn't love showing off just how crazy they can be, when someone gives them the chance?


In closing, please enjoy this: Three unscripted, me-designed moments from my most recent Gunpoint playthrough that had me laughing or feeling like a badass. These are, I guess, technically spoilers, but since the whole game is devising your own personal way around obstacles, I don't think it'll hurt to see my approaches.

1) I'm standing at the window of a building. Across a small alleyway stands another building, with a guard, above me, looking out. I'm safe now, but when I move my cursor into the space between the buildings, it turns red, telling me that I'll be seen as soon as I step (or leap) outside. He's in pouncing range, and I've upgraded my leap enough to propel me through the window, but there's no chance I'll cross the distance before he puts a bullet in me. I could shoot HIM, maybe, but I've still got objectives left in the level, and no time to clear them before the sniper shows up, blocking the exit.

I slip into Crosslink mode, look at my options. I'm in luck! The switch behind me is on the same circuit (devices on different circuits can't be linked together, usually) as the lights on his floor. I hook my switch to his lights, exit Crosslink, and flick it. Lights go out, he turns around to turn them back on, and as soon as his back is turned, I pounce, crashing through the window and slamming my fist into his face. Awesome.

2) Problem: I need to get through a door, and there are guards on either side of it. I can't open the door myself, and they'll shoot me on sight. What to do, what to do....

Solution: I've bought a new gadget in the between-mission store: the Longshot. It allows me to, with the expenditure of a power core, Crosslink a guard's gun. I laughed out loud when I saw that. I pull out the Crosslinker. A few tweaks later, and I set a tragedy in motion.

I flick a switch, and the lights on the floor go out. Guard A is the closest to the light switch, but it's on the other side of the door. So he activates the hand-scanner to go through. This activates the door... which activates Guard B's (standing guard further down the hallway on the other side) gun... Guard A crumples to the floor, shot. Guard B stands there, slapping at his gun, wondering why it misfired... as I come up behind him and pounce. Beautiful.

3) There's a Pro on the floor below me. Pros are special types of guards, clad in black suits like high-price bodyguards or Will Smith hunting aliens. Annoyingly, they're much harder to manipulate than their less-professional brethren. They won't follow noises. They won't freeze in place when you point a gun at them. They just shoot you, and then you're dead. Like I said, annoying.

I leap down, crashing through the hallway's plate-glass roof. Quick as lightning, the Pro unholsters his gun, points it at me, pulls the trigger... And the lights go out. The door behind him opens. And, grinning at his misfiring gun... I pounce. It is exceptionally Batman.

Thanks, Longshot.

Gunpoint is still in development. You can follow its progress and sign up to test (which I've been doing for the last nearly-2-years, and highly recommend) at www.gunpointgame.com and on Twitter at @GunpointGame. The game is up for the Audience Choice award at the Independent Games Festival this year, so if what you've read here (and on Tom's blog) sounds interesting, consider voting for it here: http://igf.com/audience.php
Voting ends Sunday 2/19.

The Necessary Information Awards: Best Use of Narration in a Video Game

It's the end of the year, and I have half-formed essays on a bunch of games from this year floating in my head, so I decided it was time to do what everyone always does with their half-formed thoughts at the end of the year: Hand out some awards! Whoo!

Our very first award in this, the inaugural Necessary Information Awards blogcast, is a very prestigious one: Best Use of Narration in a Video Game.

And the winner is....


BASTION!

There's a moment near the start of Bastion that I think I've seen mentioned in every review of the game. Your character, The Kid, has just received his first weapon, a hammer. And, if you're the standard gamer, you do what gamers do when given a smashing weapon and a destructible environment - you whale on everything in sight, seeing what pops out. But then...

"The kid just rages for a while..." That's Rucks, Bastion's narrator - or maybe more accurately, its storyteller - commenting on your actions and showing off the game's wonderful "dynamic narration" system.

There's nothing technologically impressive about dynamic narration - responding to player action is what games do, after all - but its use in Bastion allows the designers to tell an engaging story about the act of storytelling. Let's break down that first moment and try to understand why it's so affecting.

On the surface, it's simply clever - it's always fun when game designers anticipate common, or even bizarre, player action. It's also not especially groundbreaking - the TV Tropes article The Dev Team Thinks of Everything is full of fun examples of this sort of stuff. PC Gamer UK writer Tom Francis's in-development game Gunpoint, for instance, responds to players continuing to punch unconscious guards with a text pop-up reading "It, er, only takes one punch to knock them out." Hideo Kojima's games are as well-known for their responses to weird player behavior as they are for the sneaking action or bizarre metaplots.

So why is this moment special? Why does it stick in the mind? Because it allows you to feel empathy for the little guy you're controlling. Bastion is a story about the end of the world, and about the pain of surviving. You, you're just some schlub (or schlubette) holding a controller and smashing some boxes. But The Kid... Well, The Kid just watched his whole world get destroyed. Everyone he's ever known is dead. And when he picks up a hammer... The Kid just rages for a while.


Rucks's narration bridges the space between player action and character motivation, re-interpreting and providing in-universe meaning to the player's actions. You hit some buttons, and the game told you a story about it - again, you could argue that that sentence is what games fundamentally are, but, by addressing it directly, Bastion draws attention to the disconnect between you as a player and The Kid as a character - and invites you to empathize with the poor guy.

(The next paragraphs have spoilers for Bastion. If you haven't played it, I strongly recommend it - and it's on sale today on Steam, so... go! Fly, monkeys, fly. If you must read on, skip ahead until you see END OF SPOILERY BITS)

In Bastion, the world forms around The Kid as he moves, like a storybook being filled in with detail as the tale goes on. But the question is: Whose story?

Bastion is, essentially, a narrative told from two different perspectives to two different senses. Your eyes (and your hands) are playing the story as it's perceived by The Kid as he travels through Caelondia, slowly restoring it and searching for cores to repair the Bastion. At the same time, your ears are hearing Rucks's gravelly voice describe what's going on. These two stories almost always overlap and complement, but there are points of divergence.

The first comes when The Kid ventures into a poisonous swamp. The fumes force him into a dazed sleep, where the player must play through a demented nightmare that re-uses old areas in nonsensical ways, while Rucks's voice taunts and misdirects. Both senses are lying to the player, but it's a reminder that, for better or worse, the perspective that we, the players, are most attached to is that of The Kid's. Eyes and ears aside, The Kid is the one whose hands we control, the one whose choices we make.

And in the end, it is at another moment of choice that Rucks's control* of the narrative is potentially broken, where "his" story is shown to be just one perspective of many. In the end game, your "enemy" lies before you, abandoned and beaten by his own people for his crimes. There is no boss fight, no big speeches. Just a choice. Leave Zulf to his fate... or drop your weapons and carry him to safety. Pick the latter, pick the choice that the person telling the story wouldn't, and he'll go on talking... about how you must have left your foe behind. In that moment, Rucks's is wrong about what kind of story this is, and it's a wonderful moment of freedom, the feeling that you've broken an old narrative of revenge and fear in favor of something new.

And when you return to the Bastion, Rucks is no longer the only person with a voice. Now, your friend Zia can also talk (in all your previous descriptions, Rucks simply described what you said to each other), urging you not to follow Rucks's advice and use the Bastion to turn back time, but to move forward into a new story (and it's strongly implied that you should, that restoring Caelondia dooms the world to an endlessly repeating story of woe). By integrating its narration so fundamentally into the core of its gameplay, and then allowing the player to subvert and defy that narration, Bastion gave me one of the most enjoyable feelings of player freedom I've felt since the first time I told GLaDOS to go screw herself and escaped the fire pit at the end of Test Chamber 19.

*I'm kind of harsh to poor Rucks here - and it's one of Bastion's joys that our disembodied voice adviser doesn't inevitably turn evil like so many in the past. He just has a very particular perspective -one that makes him an active character instead of simply a narrator - and that allows him to be wrong at times.



**END SPOILERY BITS****


Finally, it's hard to say too many positive things about Logan Cunningham's work as Rucks. His voice is soothing, compelling, funny, warm. It incentivizes exploration and achievements, because you know you'll get a little more of Rucks to reward you for it. In a game that is inherently about story-telling and narration, it would be impossible to care about any of this nonsense without an incredible voice anchoring the character.

So, congratulations, Mr. Cunningham, (and writer Greg Kasavin, and everyone else who helped to make this one of my favorite games of the year) - enjoy your meaningless, fake award!

Best Taekwondo Head Kick Knockouts

As per a search result I got today, I present: The Five Best Taekwondo Head Kick Knockouts

(Note: this list was written before the publication of John Hodgman's That Is All, which features, briefly, a similar joke about a town of Shirley Jackson worshipers. Given that this list is a deliberate homage/pastiche/rip-off of Hodgman's distinctive style, that seems somehow appropriate).

#5: 11:30 PM, 08/23/1986 - Sante Fe, NM - 500 ft above where the Gold's Gym used to be on San Mateo Boulevard

Kicker: Ryan Appleburry, disgruntled gym patron

Kickee: Milos Sardos, disgruntled Gold's Gym night janitor

The Kick: Accidentally performed while jumping from a helicopter, piloted by kickee.

Surviors: None, except for a series of How-to manuals, including "How to Rob a Gym," "How to Rappel from a Helicopter Without Kicking Anyone," and "Kako pilot helikoptera bez uzimajući nogom u glavu," a Croatian edition of "How to Pilot a Helicopter Without Getting Kicked in the Head." Investigators at the scene determined that none of the books had ever been opened.



#4: 12:15 PM, 06/05/1960 - Berrywood, NH (Pop: 400)

Kicker: Berrywood, NH (Pop: 399)

Kickee: Mike Millsop (Pop: 1)

The Kick: Founded in a hidden valley in 1953 by a mixture of Korean monks and die-hard Shirley Jackson fans fearful of being swept up in Sen. Joe McCarthy's HUAC meetings, the town of Berrywood has long celebrated a quaint tradition. Every year, all of the residents gather in the Town Square and pass out copies of Jackson's famous story, "The Lottery." Whoever draws the copy of the story marked with a black dot is quickly seized, dragged onto a platform, and simultaneously Taekwondo Head Kicked by every other resident of the town. It is believed by the townspeople that this brutal sacrifice will ensure good harvests in the coming year, and also that it might convince Shirley Jackson to come visit some day, dispensing autographs and lyrical allegories for the evils of man. Tragically, it did. (See Best Taekwondo Head Kick Knockouts #2).

Survivors: These days, when HeadKick Day comes around, Berrywoodians wear foam shoes and cloud-spun socks, and kick effigies spun from the lightest gossamer, in the hopes that no one's feet might be indecently bruised. A local clown facepaints the children's cheeks with Shirley Jackson's grim visage. Much revelry, good-spirits, and laughter are had.

The corn harvests, needless to say, are terrible.

In Mike Millsop's day, you weren't considered a true Berrywood Bruiser unless you'd smelted the steel for your own steel-toed boots for HeadKick Day and brought laminated sheets to keep the blood off your new copy of The Lottery. I don't want to get into gross imagery, so I'll just say this: Mike Millsop popped like a pimple. And that's why he's #4.



#3: 2:30 PM, 03/18/1996 - The Set of the Movie "Space Jam"

Kicker: Beloved character actor and fifth-degree Black Belt Wayne Knight

Kickee: Michael Jordan

The Kick: It's a little known fact that, buried deep within one of his many mansions, Michael Jordan has a notebook. Inside it appear the words "I will not use the phrase 'Hey Newman, get me a beer, you fat little turd,'" repeated hundreds and hundreds of times, apparently under great duress.

Survivors: If you ask Jordan about the notebook, he'll look off into the distance for a moment, gently rubbing the back of his head. Then he'll ask if you want to see him dunk.

You will.



#2 12:15 PM - 6:30 PM, 06/05/1965 - Berrywood, NH (Pop. 397)

Kicker: Shirley Jackson

Kickee: Berrywood, NH (Pop. 397)

The Kick: From "The Haunting of High Kicks: How Shirley Jackson Kicked Us All In The Head," by Alex Millsop - "Perhaps it was some sleight of hand. Perhaps, as my grandad used to say, the Jackson woman was a Wordwitch, deadly in her wrath. Maybe the Lewis child, who handed out the books that day, had been playing with a pot of ink, supplied to him by sleight of hand, and brewed by a Wordwitch. I don't know.

In any case, every copy of The Lottery we handed out that day was marked with the Black Spot. All except Jackson's.

We lined up around the square, from oldest to youngest, and approached her as the wheat approaches the reaper [Ed. Note - like most Berrywood residents alive that day, Millsop suffered mild brain damage that plagued him until his death]. To each Berrywoodian, Jackson would bow, smile, and then dispatch with a perfect Taekwondo Head Kick Knockout. Unconscious bodies began to pile up on either side, but the woman was nothing if not determined. By the end of the afternoon, her foot had swollen to be the size of an egg that was the size of a loaf of bread! But she just kept kicking, kicking, kicking. Finally, she kicked the town's youngest resident, the aforementioned Ink-hand Lewis, and, with a smile, fell over, dead. We buried her in the quarry, then burnt the quarry down, and tried to forget any of this had ever happened. Frankly, I don't know why I'm writing this book. I should stop. Okay, I stopped."

Survivors: Jackson, whose literary style reflected a cynical disappointment in the follies of human nature that belied a hope that man might someday overcome his inhumanity to man, would never have willingly taken a life with her masterful Taekwondo skills. She was the only casualty of the day.



#1: ??/??/???? - Hypothetical Improbable Robot Testing Lab

Kicker: TAEKWONDO KICK BOT 3000

Kickee: GIANT FRAGILE HEAD BOT 2999

The Kick: Sublime. Perfection. An arrow is built to arc through the air as a bird in flight, striking true its target. A poet's quill, to solidify glory on the page. A head kicking-robot to kick a robot designed to be kicked in the head. Who can deny the beauty of a purpose fulfilled?

Survivors: Please visit my Kickstarter page, http://kickstarter.com/I-want-to-build-a-robot-to-kick-another-robot-in-the-head-and-maybe-it-explodes-i-don't-know-I'm-still-working-out-some-of-the-details-Oh-also-the-robot-knows-Taekwondo-the-kicking-robot-I-mean-not-the-other-one.html

Timed Hits Part 2: Fight, Magic, Item, Cycle All Your Stats and Powers Into One of Hundreds of Different Templates, Run

Note: This is Part Two of "He knows WAAAAAAAY too much about Timed Hits", a series on how to breathe life back into RPG combat systems. Part One is here, Part Three is here

So, the question remains: How do you break up the monotony of the FIGHT/MAGIC/ITEM/RUN paradigm of RPG combat? Last time we looked at the addition of timing elements, and complete conversion to action gameplay. This time we'll take a look at how you can increase player engagement from within the "classic" turn-based RPG system. This essay focuses on how to increase the available choices open to players, while the next one will be about crafting challenges for the player that force them to innovate within the space you've given them.

How do you overcome boredom in RPG combat? Give the player more to think about, more to do.

This one is so basic that you'd be excused for thinking I was padding my list by adding it. But it really can't be overstated - finding ways to increase player choice, and making those choices more meaningful, is the cornerstone that's kept interest in the turn-based RPG alive. Every designer looking to work in the genre must figure out how to approach these issues if they hope to make an engaging game.

Repeating: For combat in a turn-based RPG to be successful, the player must be presented with varied, interesting decisions that evolve and change as the game progresses.

(I know that RPGs have long been seen as the domain of "story," and, certainly, some of my very favorite video game stories have been told in this genre. But there is nothing inherent to the turn-based RPG that makes it an ideal vector for good storytelling beyond the willingness of the people making them to try telling one. As that willingness has spread to other genres, turn-based RPGs have remained, if not as culturally dominant as they once were, at least still relevant. So, there must be some aspect of the games, beyond their narratives, that keeps them interesting to players.)


Characters as Trees (And no, I'm not just talking about Exdeath)

In a turn-based game, battles are reduced to a series of discrete decisions. These individual choices are the core of the combat experience, and they MUST be interesting if the player is going to be engaged.

Once again, we're starting from that ur-RPG, that basic building block from which so much innovation has been constructed: Dragon Warrior.

In Dragon Warrior, there's only one tree that choices are being pulled from, and it's very simple - the one representing the player character's combat actions. In any situation, you choose either Fight, Magic, Item, or Run. Magic and Item have sub-choices, but those choices carry the cost of using up resources (MP or the items themselves). This tree expands when new items or spells are obtained, and the values for some of the decisions can be altered by new equipment, but this is the basic structure through which the player responds to every challenge in the game. Further, each choice is an optimal response to a particular situation - Fight is ideal for dispatching weak opponents, Magic is needed to destroy strong opponents quickly, Item for emergency healing or the occasional rare buff, and Run when survival is uncertain. The strategic element of Dragon Warrior, then, is not one of devising real plans, but one of assessing the danger level from turn to turn and choosing which of the four basic responses is most appropriate.

Once you begin to add other party members, things become more interesting. Every active character in an RPG party is a separate decision tree, sometimes only distinguished by the odds and numerical effects of their basic commands (Bob's Fight command does more damage but hits less often than Mary's, say), but usually also featuring unique commands that allow them to fulfill specific battle roles. A typical "White Mage" character, for instance, will have a tree featuring a fairly weak Fight command, but will compensate for this by having a much more complex Magic sub-tree, allowing the player to make more nuanced decisions about what type of healing or support they want to give their party via this decision.

By presenting the player with not one single decision tree, but multiple trees being cycled as character turns come up, we vary the gameplay experience (Hopefully. Early RPGs often fell into the trap of giving "Fighter" classes an extremely simplistic tree in exchange for a reduced need for healing and an increase in the power of the "Fight" command. Useful in-game, but not tactically very interesting. Later games often give the Fighter a selection of different types of strikes to use, each with different costs and effects). In a static party, though, even these multiple trees can only get you so far. To keep things interesting on the player side, we need to vary the trees/characters available.

The easiest way to vary the trees available to the player is to switch characters out of the party as the plot demands. After all, in the context of the whole game, a character isn't just the sum of the choices they allow in battle, but a hopefully well-realized person with their own motivations (Final Fantasy V gives us an interesting inversion of this, where a new character replaces a party member, but keeps the former character's abilities and, consequently, their decision tree). At the same time, new mandatory party configurations force the player to adopt new strategies to take advantage of the shifts in the decisions available to them (This can be used for narrative weight, too. For example, the sequence in Final Fantasy IV in which the Dark Knight Cecil escorts fragile-but-powerful wizards Palom, Porom, and, later, Tellah, up Mt. Ordeals is both an interesting gameplay challenge - keeping your "Glass Cannons" safe until they can take out your enemies with their spells- and reflects on Cecil's journey from invading general to stalwart protector).

Still, by assigning specific decision trees/characters to the player, an avenue for player choice is removed, possibly hampering engagement. To redress this, we have to take a step back from the battles we've been focusing on so far, and look to party composition and character (tree) customization.


Uh...If we bring more than three people into the dungeon, it'll.... explode. Yeah. - Party Composition

By choosing the members of your party, you're making a choice about which decision trees are being presented to you in battle. It's now up to you to figure out which sets of choices dovetail, intersect, and overlap in ways that allow you to win battles with the lowest amount of resources expended. Some games do this by allowing you to choose character classes at the outset (based on various decision-impacting features, such as the class's cost to operate and the "bushiness" of their decision tree) and letting the character trees develop as a natural outgrowth of the class (the first Final Fantasy game, for instance).

Others give you a certain pre-set number of characters and ask you to form a viable party from these ingredients. This can vary from a small group of potential characters (Final Fantasy VIII's three-person teams formed out of six total party members) to a staggeringly large one (Shin Megami Tensei: Strange Journey, which has three party slots that may be filled by any of the game's 300+ recruitable demons). The key to generating interest here is to create a variety of trees that are distinct from each other, but which interact in useful ways. A large roster of playable characters means nothing if it doesn't reflect an increase in interesting choices available to the player. In terms of combat, distinct characters are less important than the distinct decision trees they represent.

It's at this point that meaningful strategies can begin to develop, allowing a player to tune their party to individual strengths or to countering a particular challenge. The player ceases to reactively pick one of the choices presented by the game, but to begin creating their own.


Get a Job System! - Character Customization

Beyond choosing which decision trees to include in the battle, most games also allow the player to customize their characters; that is, use in-game systems to edit the decision tree each character represents. This can and has been done in a vast multitude of ways, but one pitfall that needs to be avoided is one of homogeneity. This relates to something I call "the problem of the optimal," something one of my favorite game writers, PC Gamer UK's Tom Francis, discussed recently in the context of his stealth game Gunpoint. To wit, if there is a clearly optimal solution to a problem, most rational players will choose it. Any choice presented to the player between an optimal option and something else is a false choice, and player freedom isn't really being expanded. In RPGs with extensive customization, this can be seen in character decision trees that narrow down and become extremely similar to each other (Final Fantasy 7 is the example that leaps to mind, where endgame characters essentially act as holders for the modular Materia that represent actual player choice in battle). If there is a "correct" character build, one that overcomes in-game obstacles most efficiently, most players will choose it.

The obvious solution is to establish game challenges in such a way that there is no single "optimal" build (more on this later). But it's also possible to constrain character customization in ways that still allow the player significant choice in their available combat options. Anyone who's spent any time with World of Warcraft or similar games will be familiar with the multitudes of ways designers have tried over the years to inject variety into the standard Tank/DPS/Healer paradigm (although competitive environments like MMORPGs are usually extremely aggressive in working out mathematically "optimal" character builds and punishing players who do not follow them - again, limiting player choice). In single player games, the Etrian Odyssey series on the DS stands out for including a larger-than-average set of distinct classes, each of which contains multiple specialized sub-classes based on which skills the player chooses to invest points in. In essence, you end up with a party of five hand-tailored decision trees, each focused on a different aspect of combat, each reflecting a conscious, engaged choice on the part of the player.

I firmly believe that enjoyable gameplay derives from a sense of player accomplishment, a feeling that I, as the player, was victorious because of the choices I made. By expanding those choices (while, possibly, quietly guiding players toward more useful options), the designer allows me to feel responsible for my victories in a way that a more game-controlled system wouldn't allow.

Of course, all the choices in the world are meaningless if the obstacles I'm overcoming with them aren't interesting and challenging. Next time, we'll talk about how the other side lives - how enemies and bosses in turn-based RPGs drive player innovation and engagement.

He knows WAAAAAAAY too much about Timed Hits, or, How to keep your console RPG combat system interesting: Part One!

This is Part One of a Three-Part series examining innovations in RPG combat. Part Two can be found here, and Part Three, here.

Once upon a time, long before the dystopia we live in now, where every Gun Shoot City or Modern Fightknife is filled to the brim with progress bars, unlockable perks, and precious, precious XP, the role-playing elements in video games were the sole province of the nerdiest of nerds. Unlike other video games, which prized reflexes, or luck, or knowing the rules of sports, all you needed to succeed at the RPGs of yesteryear were patience... and a love of reading.

The major challenge facing your silent, indistinct hero in those classic RPGs (besides eyestrain and your mom's threats to throw the Nintendo in the trash if you didn't let her have the TV back, right now, and no, she does NOT care that you haven't saved in an hour) was combat with the various static pictures of monsters that constantly popped up to assault him.


As you can see, the tactical options open to our hero (named BUTT, in honor of the fact that I was six when I first played Dragon Warrior) are somewhat limited. In fact, it's easy to see this combat as a predecessor to casual Facebook games like Farmville. No, seriously, let's break the gameplay of, say, Dragon Warrior down into its basic gameplay loop.

1)The player has a goal, accomplished by exploring a dungeon.
2)Every dungeon requires a certain number of steps to fully explore, and monsters attack periodically at certain step-intervals.
3)Every combat turn, the player trades some of their health (and sometimes a less-easily replenished but more powerful resource, MP) in exchange for damaging the monster.
4)Bonuses to your stats, gained by increasing your level or buying better equipment, reduce the amount of health that must be paid to defeat any given monster.
5)If the player has sufficient resources to defeat all of the opponents they encounter without spending all of their health by the time they've accomplished the dungeon goal, they win, and begin looking for another dungeon.
6)Repeat until game is finished.

Which isn't to say there isn't tension there - especially since the random number generator being used for the combats can cause the "health paid to defeat monster" cost to vary wildly - but the only player skills required are planning, and the patience to acquire the stats and items needed to execute those (pretty simplistic) plans.

What it translates to, in gameplay terms, is mashing the A button a lot, clicking Fight as fast as you can, and speeding through the combat text. And it's not like this is a problem only afflicting the residents of 1990, either; although Square's Active Time Battle system, in which choices must be made in real-time while the monsters continue to attack, added a bit more pressure to turn-based combat, this basic system is still at the heart of the vast majority of role-playing games.

So, what's an RPG designer to do? How do you liven up this most basic of gameplay loops?


Ask me what my job is, and then ask me the hardest part - Timing

One trick for injecting some extra excitement into your game's battles is to add a timing component. Sick of mashing 'A' constantly? Good news! Now you can mash 'A' selectively instead!

The idea here is that, by adding a small amount of skill-reliant player input into every action your character performs, the player becomes a more active participant in the battle. The question isn't just whether Ignacio Steel XII, Elf Spaceking, has a high enough ATK stat. It's whether Jerry, Dorito Eater, K-Mart Employee, and Gamer, has the skill to input the commands that power up Ignacio's Spacehorsesword, Sparklemune and let him ridestab all his enemies to death.

Why it's good: The added element of risk adds a lot of excitement to a game, especially if the game lets you play with that danger - increasing penalties or making the timing more difficult - in order to enhance the rewards.

Why it's bad: Sometimes it's nice to be able to grind through some random battles without having to watch for the half-second where one of your character's eyes glows slightly redder than normal. And some people, sad to say, suuuuuuuuuck at timing. Poor, Guitar-Hero-loathing weirdos.


Who did it early: Super Mario RPG (1996). This game is so strongly associated with this mechanic that I had to make a supreme act of will not to just put "Timed Hits!" for this whole section and move on. SMRPG used Timed Hits for everything; attacking, defending, special moves, items.

The best use was undoubtedly for the unfortunately named Scan move 'Psychopath." Get the timing right with it, and you'd not only see the enemy's health, but also THEIR VERY THOUGHTS! These could range from the saucy "MAGIC! DEAL with it!," to the heart-wrenching "Don't pity me, Mario!," to the conscientious "Gotta mow the lawn soon!"

They only really had one thing in common: being completely useless to the player. Fun, though!


Who did it best: All of the Mario-based RPGs (of which there have been, if I'm counting right, 6) have some elements of timing, but the handheld games (Mario & Luigi: Superstar Saga, Mario & Luigi: Partners in Time, and Mario & Luigi: Bowser's Inside Story) push these to the extreme. Of special note is that every attack in these games can be entirely negated with good timing (and most harder battles assume that your relatively fragile plumbers will be dodging everything thrown at them flawlessly). These games, especially the excellent Partners in Time, push the Timed Hits paradigm to the point that every battle becomes a small-scale platforming segment, and they're fantastic, engaging fun.

Honorable Mention: The Shadow Hearts games, which incorporate the timing-based "Judgment Ring" not just into battles, but into winning the lottery, haggling with shopkeepers, even operating a treadmill-powered teleporter to the moon!

Who did it... not so best: Loath as I am to speak ill of the cult favorite Mother/Earthbound series, the third game (never released in the US, but a translated version is not at all difficult to find online, if your conscience will let you play it) features an ill-conceived "rhythm element" that adds needless annoyance and frustration to battles. By tapping along to the beat of the music (which can be near-impossible to discern), the player can combo their attacks, increasing damage. While the feature is almost entirely optional, the game mentions it often enough to make players feel like they're missing something by not taking advantage of this obtuse enhancement.

Which Final Fantasty game used it: Not only was Final Fantasy VIII's Gunblade the coolest gun-sword-chainsaw hybrid my 15-year-old eyes had ever seen, it also gave the player unprecedented control over the flow of battle by... letting you hit R1 at the right time to do a little extra damage. FF8 also countered complaints that the previous games' summon animations were too long and boring by adding a rapid-tapping "Boost" system to the game's Guardian Forces. Meaning that instead of being bored during the animation, you were frustrated, your thumb hurt... and you were bored.


"Wow, we're a lot more mobile here than we are on the map screen..." - Action Instances

One of the biggest problems with the standard turn-based battle system is that it almost entirely divorces the player's experience from the character's. You click "Fight," he leaps twenty feat into the air and rends an eldritch abomination in twain. You press "Cast Gravity," she marshals her mystical might to manipulate the fundamental forces of the universe. If the goal of gaming is to let players do things they otherwise couldn't, this isn't particularly effective as a simulation.

Some games get around this by giving the player significantly more control over the character during battle than at any other point. Usually this involves switching from the standard moving-around-the-map environment to a highly detailed battlefield, and putting the player in direct control of one member of the party.

(I'm distinguishing, for largely arbitrary reasons, this style from games like Secret of Mana or Dark Cloud, where combat occurs in the same world/viewpoint/screen as normal gameplay. For some reason, I've always viewed those games less as RPGs and more like Zelda-with-stats (although, more on that further down)).

Sometimes this battlefield will be a 2D plane; more recent games using this model (the later Star Ocean and Tales games, for instance), use pseudo-3D or real 3D battlefields.

Why it's great: First and foremost, it's just a lot more exciting to physically guide your character's moves. At the same time, a good system won't sacrifice your access to advanced techniques, or to controlling your other party members. It can give you the sense of being both a powerful warrior and a general, truly, viscerally responsible for your party's success in battle.

Why it's bad: I'll let the Penny Arcade guys cover this one:

Which is to say: Most RPGs feature multiple-character parties. A system that forces you to control only one of those party members, leaving the others to the tender ministrations of the AI, can lead to some... unsavory... scenarios.

Who did it early: Oddly enough, given my earlier comments, Zelda. Specifically, 1988's Zelda 2: The Adventure of Link. Zelda 2 gets mentioned all the time for being an odd game out (in a series with a LOT of strange outliers), and one of the ways it deviates most strongly from the Zelda pattern is in being an RPG, complete with random encounters. Walk off the path on the overworld and you'll quickly start seeing monster icons. Bump into one, or enter a dungeon, and you'll switch from a top-down map view to a side-scrolling battle.

Zelda 2's clunky controls (and often confusing translation) stop it from being as well-regarded as its brethren, but it's interesting to note that this system isn't that different from the ones seen in SNES games like Tales of Phantasia and Star Ocean.


Who did it best: The people at Namco have spent a LOT of time refining the combat in their Tales games. My favorite of the lot is Tales of Symphonia (2004), easily the best of the Nintendo Gamecube's not-particularly-crowded pack of RPGs. Symphonia's combat is fast and challenging, without sacrificing control over your overall party. Plus, I'm a sucker for any game where combat performance is graded and rewarded (as it is with ToS's GRADE system, which trades battlefield performance for bonuses in a second playthrough).

Honorable Mentions: Valkyrie Profile 2: Silmeria, developed by Star Ocean creators Tri-Ace, had a battle system utilizing the conceit that in-game time on the 3D battlefield only flowed when the player was moving, allowing for increased time for planning and executing strategies.


The Summon Night: Swordcraft Story series on the GBA has an in-depth crafting mode and a fun battle system reminiscent of the 2D Tales games. The interesting added quirk here is the ability to break a boss's weapon in combat, earning the recipe to craft it yourself.

Who did it... not so best: I never played much of Star Ocean: Till the End of Time, the game referenced in the above Penny Arcade cartoon, but what I played of it seemed to bear out Gabe and Tycho's accusations.

Still, though, this is a hard "genre" for me to criticize. It's just... FUN to run around the battlefield, executing simplistic combos on your foes. As long as the character I'm controlling moves fluidly, and the game isn't viciously punishing me for my lack of attention to my other characters, I'm going to enjoy myself.

Which Final Fantasy game used it: Well, by disqualifying games where exploration and combat happen on the same map, I can't use Final Fantasy XII, by far the most "action-y" game in the main series. So, with a biiiiiit of a stretch, I'm going to point to the PSP side-game, Final Fantasy: Dissidia, which has an extremely simplistic, tile-based overworld that quickly segues into elaborate 3D battles.

Phew! Close one!

Next time: Intense refinement, and intense weirdness!