Showing posts with label game design. Show all posts
Showing posts with label game design. Show all posts

Wednesday, July 02, 2008

Gamer's Diary - Puzzle Quest, Lego Indiana Jones

Puzzle Quest - Still grinding. Still enjoying grinding.

Lego Indiana Jones - J--- and I played through two more levels. It seems that this game has a shorter playing time than the Lego Star Wars games. Perhaps our familiarity with those games has trained us in its conventions, so that we play through the levels faster. No matter; we still have fun with it.

From a game design point of view, the no-die feature succeeds brilliantly at taking the game-over angst out of the game while leaving the fun intact. Make no mistake though; this game holds little attraction for the hardcore, for the kind of player who exults in beating a level of Ninja Gaiden Black after the 73rd attempt. It makes its only two concessions to the hardcore gamer in the studs mechanic (which provides opportunities to buy in-game bling by performing well), and in the statistics and bonuses it provides for completion junkies.

The drop-in drop-out co-op also increases the game's accessibility for kids while making it a vehicle for adult-child bonding.

Tuesday, June 24, 2008

RPG Battle Systems

Yesterday I saw an ad for an Xbox 360 RPG with turn-based battles (something I like in an RPG), and it reminded me of some ideas that have percolated in the back of my mind for some time now.

Nobody cares about your stupid battle animations. They resemble cutscenes but lack half the justification: They offer pretty scenes but do nothing to advance the plot. I find them interesting to watch the first time, after that they just slow down the gameplay. This holds doubly true for "summons" animations.

I think a move should take (barring an introductory battle animation) no more than one second from the time the player picks his action from the menus. Yeah, you read me right, one second. We don't put up with this kind of crap in action games, why should we in RPGs?

In my more cynical moments I think the developers do this on purpose, specifically to slow down the gameplay. After all, how can your RPG meet the (legally required?) 40 hour minimum playtime if you don't slow the player down?

In any case, overlong battle animations break a cardinal rule of game design, and one of media development: "Don't waste the player's time," and "Kill your darlings". Long battle animations waste the player's time, keeping him from continuing the gameplay, and as for the second, I'll explain by quoting Samuel Johnson: "Read over your compositions, and wherever you meet with a passage which you think is particularly, fine, strike it out."

Game designers often make the error of thinking that what they've created looks so fine, that everyone will want to see it...over and over. Final Fantasy X exemplifies this mistake. Not only did they think their battle animations so fine that you could only shorten the summons ones, not eliminate them, they thought their cutscenes so fine that they made them unskippable.

At the other end of the wasting-the-player's-time and kill-your-darlings scale we find Puzzle Quest, which gets it right. Perhaps the limited space for the game and limited resources for development forced adherence to these principles, or perhaps the designers used their noggins rather than their vanity when crafting the game.

You won't find any battle animations in Puzzle Quest, except for the (very brief) lightning bolt that damages a party's health. Each move, not counting a chain of moves, takes no more than a second. Cutscenes last only a short time, conveying through speech balloons the minimum necessary to advance plot and gameplay. The game moves along at a fast clip, never wasting the player's time.

Your stupid semi-turn-based semi-action-oriented battle system sucks. If you the designer wish to give me a turn-based battle system, then do that. If you want to give me an action battle system, then do that. But don't give me some half-baked combination of the two. I find little more infuriating than having to pick an action from a complex menu while the enemy's action bar charges. I know that when his bar fills, he will instantly lauch an attack. No time spent perusing menu choices for him, no sir!

Final Fantasy VII has this kind of system. Your bar charges, then the enemy's does. You can't even begin to pick an action until your bar becomes full. The instant the enemy's bar fills, he attacks. Even Final Fantasy X sins a little here; though 95% of the time you can make totally turn-based moves, when you pick a limit break move it forces you to play a twitch-based minigame. I find this frustrating, especially as I age.

I prefer games that stay firmly in their lanes, like Puzzle Quest and Xenosaga and Dragon Quest 8 on the turn-based side, and Mass Effect, Final Fantasy XII and Crackdown on the action side. All three action-based RPGs handle their battle systems differently, but all have good arguments for them. None of the action-based ones try to mix in turns, and none of the turn-based ones try to mix in an action twitch-fest.

Saturday, June 21, 2008

Gamer's Diary - Bait and Switch

If you don't want story elements of Star Ocean: Till The End of Time spoiled for you, stop reading now.

I've had a couple more hours of Star Ocean 3, and I must say the game has left me bitterly disappointed. First, it confirmed my earlier suspicions by maintaining the same glacial pace as before. Second, it compounds the sin of including fantasy magic ("symbology") by stranding our young hero on a medieval planet (!) with elf-like natives (!!) oppressed by an evil wizard (!!!) (actually an advanced-technology human), stripped of his technology and with only his trusty sword (!!!!) for a weapon.

Thus the bait-and-switch of this article's title. I went in expecting science fiction and instead got medieval fantasy. At least Xenosaga had the decency to stay in science fiction land despite its use of "ether" effects.

I will give it one more chance; I will consult an online walkthrough to see whether the game detours briefly into medieval fantasy land or spends the bulk of its time there. If the former holds, I will grit my teeth and play through the medieval portion. If the latter holds, out it goes.

Friday, June 20, 2008

Gamer's Diary - Star Ocean 3? More Like Ennui Ocean 3

I think that the publisher subtitled Star Ocean 3 with Till The End of Time not because the story takes the characters to the end of the universe, nor because the main characters have a love that lasts forever, but because it will take you that long to get through the interminable interactive cutscenes.

Seldom have I seen characters take so many words to say so little. And I found on many occasions that between snippets of conversation that the characters would pause. And do nothing. For 15 to 30 seconds. I kid you not. They did not emote. They did not make funny faces. They did not say things with body language. They did not engage in fisticuffs or greco-roman wrestling matches. They. Did. Nothing.

Forever.

I said last time that I would be able to reach the first save point within five minutes of being handed control of the character. I made a mistake. It took more like half an hour. That doesn't count the half hour I spent in the battle tutorial. It was the cutscenes that slowed me down, including one that was mandatory for getting to the invasion event.

I have a theory about what happened. Play-testing revealed that players could complete the game in 20 hours. Marketing could not accept a length less than the 40 hours standard for RPGs. Some genius bigwig stood up in a focus group meeting and said, "I know! Cutscenes take up half our game's length. Let's just make them three times as long, and players will take 40 hours to get to the end." No one dared challenge the bigwig's logic, and so here we stand.

At this point, with a couple of hours of gameplay under my belt, I have trouble understanding the positive reviews this title garnered from the gaming press. Perhaps RPG reviewers, inured to this kind of padding, didn't even notice. Perhaps the publisher leaned on them to give good reviews. Or perhaps they were just such Square Enix fanboys that their slavish brand devotion colored their opinions and blinded them to the game's faults.

I don't know. What I do know is that I will give this game a couple more hours of gameplay to engage me, and if it does not, I'll put it on the list of games I give away to my friends.

Thursday, June 19, 2008

Gamer's Diary - Star Ocean, Last Remnant

Having seen a trailer for Star Ocean 4, and realizing the series consists of science fictional JRPGs, I decided I wanted to play them. I like science fictional RPGs. I found that the publisher had never released the first two entries in the series in the US, but had released the third, Star Ocean: Till The End of Time, for the PlayStation 2. And it had a very reasonable price at the local GameStop.

So I put it in the console, started it up, and spent the next hour wandering around the resort planet's hotel, talking to the inhabitants and barging into people's rooms. I had no idea of where I should go or what I should do. Finally I figured out how to get into the battle simulator (the game's combat tutorial), and when I left that the game proper began.

An unknown force attacked the planet, and the hotel residents (including my characters) teleported to an emergency transporter room. There I found a save point, used it, and that was the end of my free time for the evening.

I don't think that the hour I spent wandering means that the game has a slow pace, or that it gets off to a slow start. I think rather that it means that the game gives you a lot of not-very-important things to see and do at the outset. I will start the game over tonight and I expect to arrive at the save point no more than five minutes after I get control of the characters. Because this time I know what to do and where to go.

All this suggests that I wasted most of the time I spent playing and didn't learn much about the game (especially since I cut short the battle tutorial) or its story. That has some truth to it, though I did find out a couple of relevant facts.

First I found that the game has a battle system that uses auto-attack, much like Final Fantasy XII but without the seamless integration into the game world. One can pause the battle at any time to change the attack or use an item.

Second I found that one class of attacks makes use of "symbology". The game calls it that in order to avoid calling it "magic". As if nobody can figure that out. Why can't JRPG developers get away from using magic spells in their games? Other games have health packs for healing and guns for distance attacks...why can't these do that? The concept of nanotechnology for medicine has been around since at least the early 90s. I found this lazy reliance on magic one of the most disappointing things about Xenogears and Xenosaga - though they called it "ether" there.

I expect to have more to say about this title after I get futher in it tonight (and play through the battle tutorials!).

I came across the trailers for The Last Remnant again recently, and they reminded me of why I both anticipate and scorn this upcoming RPG. On the one hand, it looks very pretty and promises the kind of turn-based combat I like in a JRPG. On the other, one couplet in the first trailer sets my teeth on edge: "Who created those remnants? And for what purpose?"

If the localization team erred in translating those lines, that bothers me. If they didn't, it bothers me more. A translation error in the game's trailer suggests that more and worse will come in the game. If they translated it correctly, it suggests that the game developmers have no idea of what makes a remnant a remnant: a usually small part, member, or trace remaining of a larger whole. One does not create remnants; the destruction of the whole leaves them behind. Since the game's story revolves around remnants of an earlier civilization, this bodes ill for the game's nonsense factor.

Wednesday, June 18, 2008

Gamer's Diary - Ahoy!

Last night I spent a little time playing Puzzle Pirates. Or perhaps I should say, reading Puzzle Pirates. I spent far more time reading the game's documentation and tutorials than I spent actually playing.

Once in the game, I spent most of my time learning how to manage my hut and booty, and wandering into the island's shops. Finally I rediscovered the mission interface, and accepted a mission to learn swordfighting. Having played that puzzle and losing to an NPP (non-player pirate), it was time to quit.

I learned two things from my reading of the documentation and my brief time in-game. First I found that the game has in it a lot to do, and second that I don't have to do everything.

I suppose that when I decided to try Puzzle Pirates I thought that it would just be a slightly enhanced multiplayer version of Puzzle Quest. Boy did I goof. It has a lot in it to do, from buying and selling on the islands, to manning duty stations on a ship, to building and owning ships and buildings, to taking on various levels of command authority (including fleet admiral or colonial governor), to participating in a naval blockade. And one can do many other things besides.

However, unlike many other MMOs, one need not spend most of one's time in these non-puzzling activities. Nor must one grind for hours, night after night, for experience points or gold. The player can engage in all the non-puzzle game activities if he wishes, or spend the bulk of his time with the puzzles. If she wishes, she can log on once or twice a week, play puzzles for twenty minutes, and quit. Tyler Durden, in Fight Club, said it very well: "You determine your own level of involvement."

Wednesday, June 11, 2008

Gamer's Diary: Puzzle Pirates

In my quest for a MMORPG that doesn't suck, I decided to try Yohoho! Puzzle Pirates. A quick googling told me that a Linux version of the client exists, so I would not have to reboot to Windows or mess with Wine in order to play. Off I went to the website.

It pleased me to discover that I could play directly in the browser; Java powers the client. But what delighted me was clicking on the download link, and finding myself on a page with a link for downloading the Linux installer and instructions on how to run it. The website had detected my PC's operating system, and sent me to a page containing the appropriate installer. Now that I call good customer service.

A few minutes later, after a trouble-free install process and some tweaking of Ubuntu's menus to put the client launcher icon where I liked it, I was online and playing.

My first impression is that one spends the bulk of one's time playing the puzzles. I like this; it means that grinding levels presents a diversion rather than a chore, that the lack of story - and therefore of plot and of world-saving roles - becomes irrelevant, and combat has the fun of puzzle solving rather than the boredom of auto-attack.

The game has elements that do not thrill me as much. Some of the puzzles have Tetris at their core, and I dont like the real-time pressure this puts on the player. Of the other two I played, carpentry had a time-pressure element, and bilge pumping appeared not to. So off to the bilges I go then. Yarrr!

I also did not like that when I chose melee training, the game put me on a ship manned by players rather than NPCs. Almost immediately another ship attacked and I had to play a Tetris variant for the boarding action, without any time to read the instructions for the puzzle.

Now that ship's captain has made me a full member of the crew. As a result, I do not seem to have access to the tutorials any more. The next time I log on, I intend to leave that crew and find the training ship once more.

So, I have mixed feelings about Puzzle Pirates, but I mean to finish the tutorials and give it a few hours after that to engage my interest. If it fails I can always resort to the single-player game Puzzle Quest for my RPG/puzzle fun.

A quick note on Puzzle Quest: It joins the ranks of a growing number of games that don't penalize the player for losing or dying. I like this. For me it does not reduce the fun factor at all. In Puzzle Quest, when the player loses a battle not only is it not a game-over-restore-from-save, not only does the player not lose any items, weapons, or skills, but instead gains a small number of experience points. Terrific!

Tuesday, June 10, 2008

Why I don't play MMORPGs

MMOs resemble work too much. And they resemble real life too much.

The Grind. The producers can't possibly create 20-60 hours of good, fresh content a month with a $15 USD subscription fee, so they space out the content by making players slowly perform mind-numbingly repetitive tasks to get it. One endlessly battles the same enemies or harvests the same resources in hopes of finding something marginally worth keeping.

The Roles Not Played. I play video games in part to play the role of the hero or villain, to become for those hours the person who saves or destroys the village, the city, the country, his people, the world, the galaxy, the universe, or even the multiverse. To become someone that matters, someone who makes a difference, as opposed to real life, where most of us have the mundane fates of regular janes and joes and jobs that don't involve saving the world.

The structure of an MMO makes this impossible. Every player can't play the hero. Only one person or party can save the world; not everyone can become the best. As Syndrome said in The Incredibles, "[...]because when everyone is super, no one will be." I suppose you could instance the whole game world. And then you'd just have a single-player RPG online. With more grinding.

The Stories Not Told. This problem outweighs the others. The aforementioned grind/content issue limits story variety and depth. The inherent structure of an MMO (real-time play, PvP, and grouping) kill videogame storytelling conventions and make it difficult to tell a party-based story. What if a member crucial to a major plot point can't play when the other members of the party do? Ways may exist to counter these factors, but to my knowledge nobody today does it.

Apologists will reply that the player makes the story. They'll point to events like some of the great swindles in EVE Online or a particularly brutal crushing of an enemy in Ultima Online. Wrong.

The sort of events described have problems. First they occur only rarely, second they require unreasonable effort, third they have a dark side, and fourth they reek of banality.

These events merit attention because they occur so rarely. All but a tiny fraction of players will never experience events like these. Most players will simply grind their play time away for as long as they stay. I meant thiswhen I said MMOs too much resemble real life.

Then we come to the effort required. In order to have even a chance at that kind of epic win, the player will have to spend untold hours grinding to get a character with the necessary stats. I meant this, and the grind in general, when I said MMOs too much resemble work.

These events have a dark side: every epic win comes with an epic fail. Every gank has someone who got ganked. Every swindle comes with a number of people who got swindled. Every brutal crushing has a crushee. And in some games, merely recovering from such a blow can take months. Months that feel like work, not play. So for the majority of players that participate in these events, the story has an unhappy plot with a bad ending. Again, it too closely resembles real life. And work.

And finally we see the banality of it all. Most of these events have no plot, no theme, no interesting characters. They have just the gankers, the gankee, and the gank. The swindle comes closest of any of these to the requirements of a story, and only the swindler gets a good one.

The Battles Not Fought. In part, people play single-player RPGs - and videogames in general - for the fun of combat. Much of the fun in a single-player RPG lies in picking the right combination of party members, attacks, weapons, and spells to defeat the enemy party. Most MMOs have an auto-combat system that involves picking those things in advance, then when combat begins waiting for your character or the enemy's to win. It sucks all the fun out of fighting.

Abandon All Hope? Not yet. All of the problems I've outlined above may have solutions or work-arounds. Game producers can reduce grinding by making additional content unnecessary, by implementing procedurally generated content, by giving diminishing returns for levels, by introducing handicapping systems, and so on. MMOs can compensate for the lack of messianic roles by making more ordinary roles fun to play in other ways, perhaps by giving them cool and unique items and combat moves. They can fix the story problems by eliminating the need for stories, or make stories part of the environment without giving the player any crucial role. Lastly, no reason exists why MMOs cannot have interesting combat, whether turn-based or real-time, that more directly engages the player.

I have heard of some MMOs that solve one or more of these problems, and intend to look into them further. Guild Wars and Age of Conan are supposed to have interesting combat. Puzzle Pirates (which I mean to try) attempts to solve all the issues by making puzzle-solving the central activity, thus greatly reducing the impact on the player of grinding, roles, and story.

I welcome comments, especially those naming MMOs that have solved, reduced or avoided these problems.

Saturday, June 07, 2008

Gamer's Diary - GRID, Tomb Raider: Angel of Darkness

GRID

The kid had a softball game Thursday night (tie game and she caught a pop fly for an out), so instead of happily co-op-ing on Lego Indiana Jones, I had the flat to myself. I looked at my evening's agenda, and it had one word on it: GRID.

I spent several hours with it, interrupted only by supper and DVR'ed Battlestar Galactica, and I had a blast.

Simulation purists (or as I like to call them, sim snobs) may kvetch about the lack of perfect accuracy in the car physics and damage modelling. "Cry me a river," says I. It's fun, and it feels realistic enough to impart the sensation that I'm racing against other drivers, and that we're all beating the crap out of each other. And that's where it's at.

Let's face it - if all were simulated perfectly, most of us normal humans wouldn't be able to get the cars off the starting line, much less keep them on the track or win races. No, what we want is a physics and damage model accurate enough to make the game feel real, while forgiving enough to make it accessible to mortals. And that, GRID delivers.

Tomb Raider: Angel of Darkness

Last weekend, I picked up a couple of titles in my continuing quest to replace my PC games with console equivalents. One was Star Wars Jedi Knight: Jedi Academy, which performed much as I expected. The graphics weren't as pretty on the Xbox, but the gameplay was just as good. The other was Angel of Darkness.

Yeesh. More like Angel of Suckness.

I remember playing TRAoD on the PC when it came out, and being puzzled by the low reviews. I set the PC controls to the Lara-relative movement scheme, as I was familiar with it from all the other Tomb Raider games. With that scheme, it played very much like those games. No problem.

But then last weekend I played the PS2 version, and I understood where all the bad reviews came from. There were crappy textures. There were low-poly models. There was slowdown in inexplicable places. Controlling Lara was like trying to thread a needle while wearing catcher's mitts on both hands. And all this was apparent in the first five minutes of play.

Unlike the PC version, it isn't possible to choose a different control scheme; the player is locked into a camera-relative one. That would be okay if she reacted instantly and smoothly to inputs, as she does in Legend and Anniversary. Instead she very slowly turns to face in the direction the player pushes the stick, and then begins to run flat-out. This is particularly annoying when, for instance, one is trying to get her to turn around for a jump. Typically she will turn around, then instantly run off the edge to her doom. Engaging the walk function doesn't help, as she won't turn around with it engaged. And all that's just for starters.

By the time I'd gotten her to the roof, I was ready to throw the controller through the TV screen. Now I'm astonished that the review scores weren't lower. It's an unplayable mess.

Wednesday, January 16, 2008

DVD Controls for Video Games

Games should come with features allowing them to be controlled like DVDs. The player should be able to rewind, fast-forward, skip ahead and back, and jump in at any chapter point. Every cutscene, whether video or game-engine-rendered, should have full DVD controls. And all cutscenes should be viewable at any time.

Games are entertainment, and as such they should support the same kinds of user control we enjoy with our other media.

There are a number of problems involved in making this happen, and it's not right for every kind of game. There are technical, social, and design problems, and games with neither a linear nor a branching storyline are unsuited for some of these features. But for games which do tell a story these controls should be present. And even for the other kinds the underlying philosophy can be applied.

Games without any plot to speak of cannot have any kind of skipping ahead, as there's no plot event to skip ahead to. This includes some sports and simulation games (such as SSX or Gran Turismo), competitive multiplayer modes of games with a plot, and games light on plot (such as Crackdown). However, the principle is still valid.

Even if they can't fast-forward, they could provide ways to rewind, something similar to the undo feature found in many word processing programs. It would consume quitte a bit of storage, but a game could log all the player inputs and game events, and give the player the option to rewind to any point since the game began and play from that point.

This is nothing new and has been done before in various forms; games such as Doom and Quake and most recently Halo 3 have offered the option of recording gameplay and replaying it later (though not the option of jumping back into the action).

Skipping back is easier to implement, and really only requires keeping a save for each checkpoint passed. Something like this has long been available for PC games in the form of unlimited saves and save-anywhere, a typical feature of first-person shooters. It's more difficult for consoles, where storage space for game saves has until recently been quite limited. But the recent growth in available storage (in the form of hard drives, as well as higher-capacity flash) makes this less of an issue than ever.

Going back to a previous chapter presents exactly the same challenge as going to a previous checkpoint, but with an additional possible solution. Some games already offer this. Those that do, such as Halo and Doom, reset the player's status and give him a fixed set of weapons at the beginning of each chapter (or level, if you prefer). This makes it easy for games like Halo and Killzone to give the player the option of replaying any completed chapter.

Fast-forwarding is a tougher nut to crack. It would require the game to essentially take the player's place and play itself, and at increased speed. With modern games already using all of the processing power available to them, this would seem impossible. But there are tricks and shortcuts that can reduce the processing load, and some games that already do pieces of the solution:

  • Don't render every frame. In many games a large portion of the time is spent rendering each frame. When fast-forwarding at 2X, you would only need to render every other frame to achieve the same framerate.
  • Allow a lower framerate. This reduces the amount of time spent rendering even more. A framerate as low as 3 fps would be enough for most purposes, and is on a par with some DVD players.
  • Simplify the display. Gran Turismo 4 has a fast-forward when run in B-spec mode; it's just a 2D map of the track and a leaderboard. Something similar could be done for many games. RPGs come to mind. This would reduce the redering load even further.
  • Simplify the world model. There's no need to have the player's character aim his weapon, then compute bounding box intersections to see if there's a hit. Rather, combat can be resolved at least in part by using RPG-style dice rolls to figure hits and damage. Similar things can be done with physics-based events and other processor-intensive interactions.
  • Simplify computations during empty time. The game doesn't have to process visibility calculations on every frame; it only has to predict when the player will become visible to other characters and only calculate position until that time is reached.
The other part is that the game has to have AI good enough to take the player's place...which we can already see in a few games, such as the drivatar in Forza Motorsport, and the companion characters in Lego Star Wars.

Skipping ahead presents much the same problem as fast-forwarding, with some additional solutions. Skipping rather than fast-forwarding allows further simplification of the game world and its interactions; even visibility and proximity calculations do not need to be done. Skipping ahead a checkpoint's worth can also be handled exactly like jumping to a chapter.

Jumping to an arbitrary chapter or level allows the game to completely ignore game events, and simply set the player's state as well as the game world's to a reasonable value. Halo and Killzone already do this; the player begins each chapter with an appropriate set of weapons and everything else in the level in their predefined places. Games with more complex state such as RPGs would need to have a developer play through the story first to determine a reasonable state for the game at each chapter point.

As for cutscenes, some games already allow the player to go back and view ones they've already seen through gameplay (e.g. Star Wars X-Wing, Tomb Raider Anniversary). But I think that's not quite enough; they should be treated like chapter points or checkpoints and viewable at any time during the game.

And while I've seen a few games that allow pausing of cutscenes, far too many make them unskippable or only skippable. I've yet to see one that permits fast-forwarding and rewinding of cutscenes. When they can be upwards of twenty minutes long (Xenosaga), not being able to repeat or skip around is highly annoying. Life does intrude, after all.

I expect objections to these features to fall into two categories: the can'ts and the shouldn'ts. The can'ts in turn come in two varieties: technical and economic. I'll begin my discussion of the can'ts with a negotiated surrender. You're right, but.

It's not technically feasible to implement all of these features for every game. Some would require AI we don't yet know how to write, or more system resources (whether storage or processor cycles) than are available. Some games have a structure that just isn't suited for fast-forwarding or skipping ahead. But some do.

It's not economically feasible to implement all these features for every game, either. Some, though technically possible, would cost more than they'd be likely to bring in in terms of additional sales. Others might lengthen a game's development cycle beyond practicality.

However, this doesn't mean that these features shouldn't be considered, just because they might not be feasible. Rather, they should be part of any game's planning cycle, to be evaluated rather than dismissed out-of-hand.

Regarding the shouldn'ts, however, quarter is neither expected nor given. Here too the objections fall into two major categories. There is the competitive objection, and the directorial objection.

The competitive objection is that, particularly with the features that involve skipping forward, the player hasn't yet earned the privilege of seeing that content and should be prevented from doing so until he beats the current challenge. Skipping ahead is cheating, and also takes away the challenge that makes playing the game worthwhile.

No.

There is more than one reason to play a game. One is for the challenge, to have one's prowess measured by the game (or by others through the game in multiplayer). But that's only one. There are others. Another is to have a interactive dramatic experience. A third is to have fun playing with nifty toys.

Only when playing for a challenge, or a combination of a challenge and the other reaons, is it appropriate for the game to treat the player as an opponent and withhold dramatic content as a reward for passing the game's test, for winning, for beating the game. In the interactive drama case, the player is not opponent but audience; he paid the price for viewing the content when he bought the game. Similarly for the toy case, the player paid the price for using the uber-weapon (or driving the uber-car) when he bought the game.

One way to handle these apparently contradictory requirements is to allow the player to declare at the beginning of play how he'd like to enjoy the experience - as a dramatic participant, player with toys, or as a competitor. In the first case, the player would be given access to the sorts of DVD-like controls I outlined above. The second is like the first, except that vehicles, weapons and other things not available at the beginning of the narrative would now be available at any point. And the third would turn off all the skip-forward controls and some of the skip-back ones, while adding rewards like medals and achievements for succeeding at various tasks in the game.

A player in challenge mode would be able to switch to either of the other two modes, and players in the other two modes would be able to switch between them, but they wouldn't be able to switch to the challenge mode without starting the chapter or game over.

Some games already implement these modes to various degrees, but without the DVD controls. A notable example is Lego Star Wars, which has a story mode and a challenge mode (free play). Dying in story mode has little consequence, except to cost the player in-game money required to buy trinkets that competitive gamers will appreciate but which don't affect progress through the story. However, like Halo, the ability to skip ahead is not provided. The developers could have offered such an option, since each chapter starts from a fixed state, but chose to make the chapters serially unlockable instead.

So it's possible to satisfy the competitive player while also giving the story-focussed and toybox players what they want - including DVD controls. This completely negates the competitive objection.

The second of the shouldn'ts is the directorial objection. Holders of this view would have it that indeed there are entertainment players as well as competitive ones, and that the entertainment player must progress through the game along the path(s) chosen by the developers, or communication of the developer's artistic vision will suffer.

No.

Imagine the absurdity of this when applied to other media. How would you like a book where you couldn't skip to the end or to a favorite passage, where you had to finish chapter 9 before being allowed to read chapter 10?

How about a videotape that won't fast-forward? Or a DVD that disables all the navigation controls as soon as the movie starts playing in order to recreate the theater experience? Or a music CD that can only be played in order?

The only reason we put up with abominations like the unskippable cutscenes in Final Fantasy X is that we've been conditioned to accept it in videogames where we wouldn't in any other media. Partly this is because it's far harder to implement navigational controls for games than for linear noninteractive media, and partly this is because we're used to thinking of games as competitions rather than interactive storytelling.

There's one specific variant of the directorial objection I'd like to deal with before moving on: that DVD-like controls would ruin the feelings of suspense and fear in horror games. This was the argument used by the developers of Call of Cthulhu: Dark Corners of the Earth to justify their use of a save point system rather than save-anywhere, and the painfully large distance between save points. This argument has it that if you can just restore from a quicksave when you die, you won't feel any fear.

This is patently false. Were this the case, horror movies would create no sense of suspense or fear in their audiences; after all, there's no equivalent to repeating a tough part when you're in the movie theater. Repeating a long tough part in a game isn't scary. It's boring and frustrating. And if fear of being bored and frustrated is all they have to offer, then that's pretty weak sauce.

Horror movies create fear in the audience through the situations, sights, and sounds. Horror games should do the same.

So... the directorial objection doesn't hold water either.

And with the can'ts and the shouldn'ts out of the way, I'll summarize. Games should be enjoyable in the same way our other media are, with DVD-like navigation controls. These controls should be implemented whenever it is technically and economically feasible to do so, and let the objectors go pound sand.

UnCivilized

Sid Meier's Civilization games have gotten many accolades over the years. I never dug strategy games that much, but recently discovered they can be fun (e.g. Advance Wars, Command and Conquer). So I picked up Civilization Chronicles when it was released.

After having spent an evening each with Civilization, Civilization II and Civilization III, I wonder what all those reviewers saw that I'm missing.

Because I'm not enjoying these games at all.

To me, they are deadly dull. Move this unit here, build that city there, attack this, defend that, blah, blah, blah.

I can think of some reasons for this:

  • Openness: The game may be too open. There are many roads to success, and many to failure, and they all look the same. Openness is often touted as a much-desired feature in games. I say there can be too much. Too many choices without any good way to evaluate them before committing to one is a recipe for frustration.

  • Feedback: There is little to let you know how you're doing and where your trouble areas are. Or rather, there's too much feedback of the wrong kind; a myriad of tiny details but little in the way of a dashboard or color-coded map to tell you the "strategic weather" in various parts of the game world.

  • Micromanagement: I felt like I had to tell every unit what to do on every turn. Group commands seemed inefficient, and none of my units seemed to have even the most basic self-defense AI.

  • Lack of Action: Because of the micromanagement, turns take a long time, and the action that does occur seems muted. The two strategy games I mentioned enjoying have action going on all the time. In Advance Wars and its sequels, every turn involves one or more battles, positioning units for a battle, and building units to battle with. Command and Conquer and its sequels are the same, but in real time.

  • Lack of Story: With the exception of competitive multiplayer games, sports games, board games, puzzle games and arcade games, I prefer games to be interactive storytelling rather than pure tests of skill. The primary mode of play in the Civilization games is a randomly generated map and scenario. I find this far less interesting than those optional scenarios that do tell a story.

    It's worth noting that in all games which offer both a randomized universe and a story mode, I will always choose the story mode. In fact, given a choice between a puzzle-like fixed goal and a randomized setup I'll always pick the puzzle. I tried the conquest modes in Starfleet Command 3, and found it nearly as dull as I'm finding the Civilization games. I quit playing Bejeweled 2 after finishing the puzzle mode; the randomized survival mode I found uninteresting.

It may be that playing the "canned" Civ scenarios will make it interesting again for me. I'll know more after playing Civilization IV.

Tuesday, November 28, 2006

Making Unsafe Saves Safer

If you've ever worried about losing your Xbox, Xbox 360 or PS2 game saves (to an accident, mistake, hardware failure or small child), then you may have tried to make backups of your saves, only to find that you can't copy some of them. In this article I'll describe the problem, guess at the reasons for it, present some advice for game makers, and finally pass on what workarounds I know of to make backups of these 'uncopyable' game saves.

The Problem

A few months after I bought an Xbox and a PS2, I realized I had hours of progress on some games that I'd be unhappy about losing.

So I set out to save my saves. I have purchased memory cards for all my systems to backup saves onto, and tried to copy my saves to the cards.

The first system I had trouble with was the Xbox. Ordinarily when a save is selected, the Xbox dashboard offers options to copy or delete. But on some of my games, only the delete option was offered. Some web research revealed that Microsoft offers developers the ability to mark saves so that the dashboard won't copy them.

What the-???!!!

Out of my library of 79 Xbox titles, 15 have save games that are uncopyable either explicitly, or practically (Fatal Frame's saves are five times the size of an Xbox memory card). That's about one out of five. The titles from my collection with the problem are:

  • Black
  • Burnout 2: Point of Impact
  • Burnout 3: Takedown
  • Call of Cthulhu: Dark Corners of the Earth
  • Darkwatch
  • Driver 3
  • Fatal Frame
  • Fatal Frame II: Crimson Butterfly: Director's Cut
  • FlatOut
  • Forza Motorsport
  • Half-Life 2
  • Jade Empire Limited Edition
  • Psychonauts
  • Silent Hill 4: The Room
  • Star Wars Knights of the Old Republic II The Sith Lords

I checked my PS2 saves, and there was a property on each save called "file protection" that made me nervous. Just this year I picked up two titles that turned out to have uncopyable saves:

  • TOCA Race Driver 2
  • TOCA Race Driver 3
Sure enough, the 'file protection' save property was on. So Sony offers the same kind of game save copy protection to developers that Microsoft does. It seems to get used far less often, though; only those two out of the 28 PS2 titles I've tested have uncopyable saves.

Just recently I started backing up my Xbox 360 saves, and two out of the 10 titles I own won't allow copying of save files:

  • Perfect Dark Zero
  • Gears of War

The Reasons

After the surprise and outrage over not being able to copy some of my game saves subsided, I began to see the reasons why a console maker might offer such a thing, and why game publishers might use it. The purpose is not, despite how it may appear, to prevent players from using their saves on a friend's system, nor to make players restart their games from scratch in the event of a hard drive or memory card failure. Those are just side effects.

Nor is the intent to stop the hardcore hackers, those who are willing to modify the console hardware to get what they want. With hardware mods all bets are off. Legal tactics are the method of choice for suppressing hardware mods.

No, the intent of the manufacturer, the game publishers, and the game developers is to stop casual activities they don't want. I think there are four main reasons why some game saves are uncopyable: online cheating, piracy, homebrew, and offline cheating.

Online Cheating: The idea here is that a game that gets a reputation as a playground for cheaters will sell less. This also applies to games which are single-player only but which have online leaderboards. The easiest way to cheat online is with a hacked gamesave. The cheater transfers the save to a PC, applies a hacking tool, and transfers it back. Some forms of cheating don't even require a hack; if a game stores online progress in offline saves, then merely having a backup of a save is a kind of cheating. Wins can be copied to the backup, while losses can be erased by restoring from it. Making game saves uncopyable closes this particular avenue for cheating, though of course it still leaves open hardware mods and net hacks (and does nothing to stop save hacking on systems where there's no built-in hard drive).

Piracy: This affects the manufacturer's bottom line as well as the publisher's, as the manufacturer gets a percentage of game sales revenue. Not every pirated copy of a game represents a lost sale, but some number of copies do. In order to reduce the amount of this going on, the manufacturers have taken steps to prevent burned copies of games from running on the console. These include [a] Microsoft using a DVD-ROM drive that has trouble reading writable media (or in more recent hardware revisions, is deliberately configured to reject DVD-Rs), [b] Microsoft using an unusual disk format that can't be read by PC DVD readers, [c] Microsoft writing into the disk loading program a check to see if the game disk has been cryptographically signed by Microsoft, and [d] Sony writing their loader to check the disk media type to make sure it's a commercially pressed game disk rather than a burned copy.

One of the more convenient ways pirates use to get DVD-R copies of games to run is hacked saves. Some games contain bugs that can be exploited to make part of a game save's data executed as code, thus enabling the pirate to run a game loader that doesn't check for the cryptographic signature or media code. Making the game saves uncopyable closes this opening for casual pirates, at least on the Xbox where the only way to get the save onto a PC is to first get it off the Xbox hard drive and onto a memory card. Serious pirates can still use hardware mods in order to play their downloads, but this requires skill and money, thus greatly reducing the number of people playing burned copies.

Homebrew: Many game consoles are sold at a loss. This is true in particular of the P52, the Xbox, and the Xbox 360, at least for the first year or two after their introduction. The way the manufacturer makes money is through licensing fees on games. In return for the licensing fee (and other conditions such as certification), Microsoft adds the cryptographic signature that will allow the game to run on the console, and both console makers press the disks on commercial media. If people could easily make games run on the console without the cryptographic signature or correct media code, then there'd be no reason for anyone to pay the licensing fee. Then instead of losing money on the console and making it back on the games, the console manufacturers would just be losing money. Not only that, but the quality of games would be completely uncontrolled and there could be a repeat of the Atari 2600 fiasco from the 80s. Not an attractive proposition.

As mentioned before, the easy way to get unsigned code and burned disks to run is to exploit a game bug with a hacked save. Again, not being able to copy saves for that game closes that loophole (on the Xbox). Hardware modders can still run homebrew games, but that's a tiny fraction of the financial exposure that would come from everyone being able to run unlicensed games.

Offline Cheating: I don't see a financial reason to stop cheats in offline games, so I'm going to chalk this one up to pure anal-retentiveness. I know for sure that there are developers who wish to force a particular game experience on the player. For instance, in the case of Call of Cthulhu: Dark Corners of the Earth, the developers had the option to create a save-anywhere feature, but--quite deliberately--chose to have savepoints instead, so that the player could not (for instance) choose to save during a frightening and deadly action scene. The designers wanted the player to feel the fear of having to do the entire scene over again, in addition to fearing the things trying to kill the player's character.

With this sort of high-handed attitude, the player must experience the form of enjoyment intended by the game designer and no other. Given that, I can understand if not approve of attempts to stop single-player offline cheating. Even something as simple as loading an earlier (backed-up) save in order to get out of the corner the player has painted himself into, rather than having to start the game over from the beginning, can circumvent the designer's intended experience. And cheating via hacked saves? That completely demolishes it. Making the saves uncopyable prevents debasement of the designer's work by the casual cheater.

Or I could give the benefit of the doubt and suppose that the saves are actually uncopyable in order to prevent online cheating, piracy hacks and homebrew hacks.

So... With all these reasons why console manufacturers and game makers would want uncopyable Xbox saves, why are any saves copyable at all? I think it's due to a combination of factors, including a lack of anal-retentiveness, an evaluation that the losses stopped by preventing game save backups are less than the losses created by angering customers, and having other less onerous methods of achieving the same results. It's telling, I think, that Microsoft thought these problems serious enough that they deliberately removed from the Xbox 360 a function to copy Xbox saves for backward compatible games, and also prevented those saves, once created on the 360, from being copied onto memory cards. That's right; no original Xbox game saves can be copied from the Xbox 360 hard drive onto a memory card.

Some of these copy/no copy decisions, however, appear to defy logic, leaving the above explanations in doubt. For instance, take Burnout 3: Takedown. The saves on the PS2 version can be freely copied, but the ones on the Xbox are locked. Yet the saves for Burnout: Revenge can be copied on both platforms. One could argue that the problems with copyable saves on Burnout 3 were fixed with Revenge, and that there's not much point in protecting saves on the PS2 as it has no internal hard drive. But then there's TOCA Race Driver 3, which has saves copyable on the Xbox but not on the PS2! Try to make sense of that one.

Advice for Game Makers

Though using game save copy protection may stop abuses like casual softmodding for piracy or homebrew, and casual savehacking for online or offline cheating, it also stops legitimate players from from safeguarding their progress. Game makers may come to the conclusion that hindering the abuses is worth more to them than the goodwill of their legitimate customers, but what if they didn't have to choose one or the other? What if there were ways to stop the abuses without angering the customers?

Let's go through the reasons mentioned above for uncopyable saves, and see if there aren't other solutions. I will begin by stipulating that these other solutions are ineffective against modchips and other hardware hacks; but then, so are 'uncopyable' saves.

Online Cheating: If all online progress is stored on the server rather than the console, then online cheating by hacking the save becomes impossible, as the player doesnt have an offline save to hack. Some material, such as downloaded multiplayer expansion maps, has to be stored on the console, as broadband comnections are not yet fast enough to make on-demand maps practical. However, this kind of static content can incorporate cryptographic signatures that are validated at load time, making savehacked maps useless.

But what about games that use offline single-player progress to unlock online bonuses, or that keep online leaderboards of single-player achievements? The first of these is a bad idea for game design reasons, and both can be handled by a fairly simple technique.

With the exception of co-op story mode, multiplayer and single-player modes in games tend to be very different experiences. In fact, they're usually different enough to be like completely separate games, appealing to players with opposite tastes and skills. Single-player content draws those who prefer to be told a story and progress through the content to its end, beating the game, while multiplayer draws those who want pick-up-and-play action where they're competing against or teaming with other people. Skills that are necessary to dominate one mode are often useless in the other. Even players who enjoy both kinds of experience tend to play them as separate games; I know I do.

Worlds apart as the two play modes are, it doesn't make sense to tie progress in one to the other; most multiplayer enthusiasts I've heard from are uninterested in single-player game modes. Requiring single-player progress in order to unlock multiplayer bonuses makes a game a chore rather than fun. If there's going to be online multiplayer progress, it should be tied to online multiplayer achievements.

That said, if the game designer is going to insist on tyeing mutliplayer features to single-player achievement, or if an online leaderboard of single-player scores is wanted, then the way to do it is to provide a separate online single-player mode. Such a mode would be playable only online, with all save data being stored on the server. This eliminates savehack cheating, so that the save data on the console can be freely copied.

Piracty and Homebrew: The solution to this one is basic software quality control. Treat save data as input and validate it before using it. Array bounds checking, offset range validation, and other input verification techniques are basic tools for safe programming, as are automated unit tests that check for such vulnerabilities. If buffers can't overflow, then executable code can't be altered to give an attacker access.

Offline Cheating: Oh come on. This isn't a problem that needs solving. Really. In fact, leaving this vulnerability open may increase sales and will certainly increase the game's enjoyability for those with lesser skills.

Workarounds

For original Xbox games, the only workaround I can offer is for the one game that prevents copying to memory card by being too big: Fatal Frame. For the others, nothing short of running Xbox Linux or an alternative dashboard will give the ability to copy the protected saves. And both of those require a modchip or (for older machines not connected to Xbox Live) a savehack. Here's the workaround for Fatal Frame:

  • Get an Xbox USB adapter. This is a device that plugs into a controller port and provides a USB socket.
  • Get a USB flash drive that's compatible with the Xbox and big enough to hold the save (64MB or larger). You can find lists of these drives by searching the Web. I use a Lexar Jumpdrive Secure 128MB.
  • Plug the flash drive into the adapter, the adapter into a controller port, and format the drive.
  • Copy your Fatal Frame save to the flash drive.

For PS2 and Xbox 360 games, the general strategy for backing up saves is this:

  • Start the game with the original memory device inserted, as well as the backup.
  • Load the save from the original device.
  • Remove the original memory device.
  • Switch the game's save location to the backup device.
  • Make the game save itself to the backup device (usually by tweaking some game setting, then tweaking it back).
The reason for removing the first memory device is because some games will attempt to delete the old save when you change which memory device you're using.

The above strategy will work for both TOCA Race Driver 2 and TOCA Race Driver 3 on the PS2. You can drop the removal step, as neither game tries to delete the old save.

For the Xbox 360 game Perfect Dark Zero, the above strategy works when the original save is on a memory card. Just drop the settings change step, as the game saves itself the moment you change the save location. But when the original save is on the hard drive, a variation on the technique is necessary, as I think it unwise to remove the hard drive while the console is running! To copy your save from the hard drive to a memory card, do this:

  • Insert the memory card.
  • Start the game and proceed to the main menu.
  • Change the save location to the memory card.
  • Remove the memory card.
  • Change the save location to the hard drive.

For the Xbox 360 game Gears of War the above strategy will not work, and a different technique is necessary. A Gears save cannot be copied to an empty memory device; the 360 complains that it can't copy the save to a new profile. However, an existing save tied to the same profile can be overwritten. So:

  • Start the game with both memory devices inserted.
  • Change the save location to the backup memory device.
  • Start a new single-player game.
  • Skip cutscenes as much as possible and play until the first checkpoint is passed.
  • Quit the game.
  • Exit to the dashboard.
  • Copy the game save from the original device to the backup device, overwriting the save just created.
  • After this, the save can be copied from the original device to the backup device without a problem.

Tuesday, October 17, 2006

Levelling the Playing Field: Mice And Analog Sticks in First-Person Shooters

During a game of SOCOM 2, player Red One catches sight of Blue One. Blue has his back to Red, so Red decides to try for a headshot. Red aims at Blue, but the crosshair stops to the left of him. So he tugs the analog stick up and right. But he overshoots, so he tugs left. Overshoots again, and tugs right. Tugs left. Right. Left. Down and right. While all of this is going on, Blue notices Red's presence, turns, and tosses a grenade. The grenade goes off, and Red is dead.

Before the next match, Red reduces his control sensitivity so he can aim precisely and get a headshot next time on Blue.

Red creeps along a wall, past a closed door, peeks around the corner, and there's Blue. Red aims and gets a headshot on Blue. But then he hears the door open behind him. He tries to turn but with the decreased control sensitivity it takes a long time. Long enough for Blue One's teammate Blue Two to kill Red.

Frustrating, isn't it?

Had it been a PC shooter such as Counter-Strike, the mouse would have given Red the precision control to get the headshot as well as the turning speed to deal with a threat from behind.

This is why people who have played PC shooters tend to prefer them to shooters on the consoles.

Console shooter designers are faced with a dilemma: if they make the input ramp steep enough to provide quick turning when the stick is pushed over all the way, then the turning speed rises too quickly near the stick's dead zone for precision aiming. But if they make the ramp shallow enough to provide slow turning in the area near the dead zone, then it is still too slow when the stick is pushed over all the way.

A number of solutions to the problem have been tried, with varying degrees of success. Many involve eliminating to one degree or another the need for precision aiming. These include:

  • Aiming assistance - either the crosshair or the shots will drift towards the target when the player's aim is close enough
  • Target lock
  • Target lock with fine tuning
  • Large hitboxes around targets
  • Inaccurate automatic weapons with high rates of fire
  • Large blast radius for explosive weapons
  • Enemies who aim or react slowly and aim inaccurately
  • Translating the position of the analog stick, within a certain range, into the position of the aiming crosshair. Outside that range, stick position is translated into turning speed.
  • Accelerating turning speed with time - the longer the stick is held in one position, the faster the turning speed becomes.
In addition to these solutions, many shooters pass the dilemma on to the player by giving him an input sensitivity control. Not that I think having such a control is bad; it's just not a way to fix the problem at hand.

The above, by the way, is one reason that console and PC versions of the same shooter cannot play on the same server; every solution above, if applied equally to both PC and console, continues to leave the advantage in the hands of the PC user. If applied to one but not the other, it results in battlefields that are incompatible and can't run on the same server.

There is a solution, however, that I believe can level the playing field and even give console players a slight edge over the keyboard-and-mouse crowd:

Input Acceleration

I first encountered this when playing Half-Life on a laptop PC. It wasn't always practical to use a mouse when I wanted to play, so I began experimenting with the TrackPoint device. For those of you not familiar with it, the TrackPoint is a tiny pressure-sensitive joystick that sits between G and H on a laptop keyboard and is meant to substitute for the mouse. The harder you push it, the faster it moves the pointer across the screen.

Most people don't like TrackPoint devices because of the difficulty in controlling them: on low sensitivity they can get accuracy but not speed, and on high sensitivity they can get speed but not accuracy. Sound familiar?

This is where input acceleration comes in. With input acceleration turned on, a gentle to moderate push results in slow pointer movement for pixel-perfect accuracy, while a medium to hard push sends the pointer zipping across the screen. When applied to Half-Life, this permitted precision aiming with a gentle push and quick turning with a hard push.

Without input acceleration, doubling the pressure doublea the speed, tripling the pressure triples the speed, and so on. With input acceleration, doubling the pressure might give four times the speed, tripling it might give nine times, and so on.

If input acceleration were applied to an analog stick as to the TrackPoint in my laptop, this would give console gamers the speed and accuracy they need in order to compete with mouse-and-keyboard users.

In fact, it should give them a slight edge. Using the left stick for running and strafing is superior to using the keyboard, because it allows the player to more precisely control movement speed. And having all the buttons within finger's reach means a quicker response than when they're scattered over a keyboard.

So if input acceleration is so good, why isn't it in use? Well, it could be that some console shooters do use this method to make aiming easier, and I either haven't played them or I haven't noticed. That would then make the question why it's not used more.

I suspect the three major factors are ignorance, inertia, and haste. Some developers are ignorant of the possibility of using the technique, so it isn't even considered. For others, there's inertia; it's easier to do what's already been done than to invent something new. For many of the existing solutions, there may even be code available that can be lifted and reused. Finally, there's haste. Software development tends to be on tight schedules, never more so than when the project is a port from a PC shooter. When deadlines are tight, the risk to the ship date from using a known solution is far less than using something new.

On the other hand, analog sticks have a travel and are operated by the thumb, while TrackPoint sticks don't move and are operated by the more dexterous index finger. It could be that developers have tried it, and the differences between analog sticks and pressure sticks mean that input acceleration doesn't work nearly as well for consoles as for notebooks. In which case I, and this entire article, are full of it. Wouldn't be the first time.