Prince of Persia: The Forgotten Sands

According to Steam, I have spent 11 hours playing Prince of Persia: The Forgotten Sands. In fact, I’ve spent something more like half an hour at it, little enough that I haven’t even made it out of the intro/tutorial level (which is strikingly similar to the tutorial level in Prince of Persia: The Sands of Time). Remember Arkham Asylum? That had a problem with Steam’s timekeeping too. It had a launcher that spawned the game in a separate process and then terminated. Since Steam only counts the time spent in the program it actually launches, its time count was way too low. But at least that didn’t lead to further troubles. PoP:TFS has the opposite problem, which is far worse: for some reason Steam can’t tell when I’ve exited the game, so it keeps on counting me as playing when I’m not. And also, because it thinks I’m still playing, it won’t let me launch any other games, or exit Steam. The only way I’ve found to exit this state is by killing the Steam process via the Windows task manager.

That’s not the only thing about the experience that reminds me of my experiences with Arkham Asylum, for just as AA introduced me to the joys of Games for Windows Live, so too is PoP:TFS my first experience with Ubisoft’s “Uplay” service and their infamous need-a-constant-network-connection-to-play DRM. It’s not clear to me how closely linked these two things are; all I can say is that I encountered them both for the first time together, and so my dissatisfaction spreads to both. The chief effect of Uplay is that I needed to exit the game to change the default resolution (800×600) to something that looks reasonably good, because most of the configuration is outside of the game, in the Uplay launcher app. The chief effect of the DRM is that, once I exited the game, I couldn’t get back in. The game gets stuck at a screen telling me that it’s “attempting to restore the network connection”, which is absurd, because I have a network connection — I can alt-tab out and surf the web, send email, etc. without problems. Goodness knows what the real problem is.

Uplay seems like a very unnecessary thing to me. It’s trying to be like Steam or GfWL, but those services at least have games from more than one publisher, and Uplay doesn’t. Still, when I first launched the game and was told I needed to register for an Uplay account first, I was actually inclined to say “Well, at least it isn’t GfWL”. I mean, when it downloaded a patch for itself, it did it fairly quickly, needed only one iteration, and didn’t ask me to restart the app. This is still worse performance than your typical single-programmer indie work on Steam, mind you, because it’s using Uplay’s built-in patcher, which doesn’t run until you try to launch the game.

But such objections pale in comparison to the DRM, which is a piece of software whose sole purpose is to prevent the game from working. In theory it’s only supposed to prevent it from working for pirates, but apparently someone at Ubisoft decided that keeping the wrong folks out was more important than letting the right folks in. It’s like one of those overzealous IP lawyers who hurt their employers’ business by harassing fan sites and alienating customers. The message it puts on the screen when it refuses to let me play even seems to acknowledge that I’ve successfully run the game before, which you’d think would be a good indication that there’s no good reason to stop me from doing so again.

I suppose I could download a crack. I mean, it’s not like DRM actually works for its intended purpose. But why bother? There are plenty of other games waiting.

Prince of Persia (2008): Tricky Ending

It took me until the ending to realize this, but the story of Prince of Persia (2008) owes quite a bit to Shadow of the Colossus. Oh, it’s less subtle about it, leaves less unsaid, puts the player in a less morally ambiguous role for the bulk of the game. But the two games share a fundamental story of a woman restored from the dead by means of a Faustian bargain with an imprisoned dark god (who speaks in both male and female voices), a bargain that leaves the buyer physically changed, corrupted (or Corrupted), and the darkness empowered. There’s some similarity of setting as well: an isolated and forgotten valley containing ruins of a dead civilization, including the massive central temple where the darkness is housed.

The chief difference is that in SotC, arranging for the woman’s resurrection by doing the bidding of the darkness is the player’s job, whereas in PoP it’s already happened: Elika’s life was the one restored, and her father, the king, was the one desperate enough from grief to listen to Ahriman’s temptations. As a result, he becomes one of the game’s recurring bosses, always waiting for you back at the temple when you have something important to do there. This state of affairs is revealed in full through dialogue about midway through the game, but disjointed visions hint at it throughout. (In fact, the very first thing you see on starting a new game is a disjointed vision, which seems like a very bad choice to me. As I’ve said before with respect to other games, the purpose of a game’s intro is to orient the player, not disorient them.)

The point is that Elika, as beneficiary of the deal, feels responsible for Ahriman’s imminent escape. This is why she’s pushing herself so hard. Also, she belongs dead, and she knows it. In the end, sealing Ahriman away again means sacrificing the life that she got from him. I’m not quite clear on which is cause and which is effect, as it makes sense either way, but they definitely go together. And what follows is one of the most interesting things about the game, or at least one of the artsiest.

Control of the story effectively ends here, but control of the avatar does not. The Prince picks up Elika’s limp corpse from where it lies, at the base of the now-luminous tree growing on the seal of Ahriman’s tomb, and control is given to the player, who pilots the Prince back outside — there being nowhere else to go. You move slowly; you can’t run or jump while carrying the body. At a certain point in the long passageway out, the credits start scrolling by on one side of the screen. This condition lasts long enough for the player to think of this state, of carrying the dead princess out, as an ending.

But of course it’s an ending that has to come to an end, when you emerge from the temple, and lay Elika down on her mother’s tomb, and still have no place to go. There’s no way out of the valley. The areas you spent most of the game exploring are unreachable without Elika’s magic. You can’t even try to kill yourself; all the cliffs are now protected by invisible walls. You can hear Ahriman whispering about how unjust the situation is, that Ormazd (Elika’s god but explicitly not the skeptical Prince’s) used Elika as his pawn and then discarded her. It’s easy to feel a similar sense of betrayal here, if not by a creator deity, then by the creator of the game.

Restoring the temple had caused four withered stumps on top of stone structures outside to grow back into small trees, each bathed in light. Reaching each of these trees required a different jumping trick — here we are after the credits, but there’s still a bit of genuine gameplay left. This left the question of what to do with the trees once I reached them. It turns out that there’s only one thing you can do, only one input recognized: the Sword button, which chops them down and re-corrupts the area around them. And it was clear: I was being given the opportunity to re-make the choice that Elika’s father made. To bring Elika back to life by giving Ahriman what he wants. To render the entire game thus far moot. To imitate Shadow of the Colossus more directly. A moral choice, leading to good and bad endings (or bad and worse, as the case may be)? No, there’s only one ending. I looked for another option, a way to just leave this place, to leave Elika dead and not make things any worse. The only options are to continue the story by destroying the world, or to quit, which is more or less the same thing.

The strange part is that I kind of feel like quitting was a legitimate option here. I don’t usually feel that way: just as shutting a film off before the final reel doesn’t change the film’s ending, so too does a game with a single scripted ending still have that ending even if you refuse to play through it. But, like I said, this game goes out of its way to make you feel like you’ve already seen the ending of the story at this point. Elika here wears the "Beyond Good and Evil" Jade outfit, unlocked on completing the game once.Nonetheless, I played on to the darker conclusion. The last thing you see is the Prince carrying Elika away, groggy but definitely living and not at all pleased, as Ahriman emerges and overtakes them, filling the sky.

Apparently a lot of people were unhappy with this ending, and a DLC epilogue was added to the console versions to pacify them. (The epilogue does not seem to be available through Steam.) However, as seems to usually be the case with unpopular endings, I like it. It is, if nothing else, gutsy. It’s not just a cheap shock ending, because it emerges from the characters — including the self-centeredness of the Prince, who proves through his actions here how little he cares about the epic struggle he’s been assisting, or even about Elika’s wishes. Also, it’s kind of a Snake Plissken ending, a way for the hero to assert his autonomy by defying the powers that dared to assume his continuing loyalty even as the reason for that loyalty was taken away. And that’s something you don’t see a lot in games. (You don’t even really see it in the Metal Gear series, which is on record as taking inspiration from Snake Plissken.) Ironic, then, that for the player, it’s the ending you get by just going along with what the game wants you to do.

Viewing it cynically, though, the whole thing was probably meant mainly as a sequel hook, and from that point of view, it was a failure. Just as well. To my mind, it works best as the last word.

Prince of Persia: Animated Motion

Playing Prince of Persia (2008) again just after sampling Angry Birds makes for an interesting contrast. I said that I was prejudiced against thinking of stuff that you play on a phone as “real games”, but in a way, Angry Birds feels like more of a game than PoP08. Even though your actions in it are limited to operating a slingshot and tapping the screen to activate special abilities, it somehow feels a lot more free than PoP‘s full movement and array of contextual actions. I think this is because the few actions you can perform in AB are more significant: any input is acted on immediately, and small differences can have large consequences. PoP, on the other hand, is designed around discrete actions, and windows of opportunity to to perform them. If you’re swinging by your arms from a horizontal flagpole, and you press the Jump button to flip to another flagpole farther along, the precise moment that you press the button doesn’t matter, as long as it’s within the interval allocated for success. I suppose this is the sort of gameplay that OnLive is ideal for.

This sort of gameplay is the consequence of a particular model of action that goes back to the original 1989 Prince of Persia, a game that was famously built around rotoscoped animation, allowing for movement of unprecedented realism. It was, in essence, the ancestor of modern motion capture — just in 2D, which meant that all they needed to capture motions was a movie camera. But a rotoscoped animation is just a static series of frames, something that can’t respond to changes. Most other platformers didn’t put such a high priority on fluidity of motion, and therefore didn’t care if they snapped directly from a walk animation to a jump, or from running at full speed to the left to running at the same speed to the right. In PoP, jumps were linked to the Prince’s stride, and switching directions meant playing a brief animation of the Prince skidding to a halt and turning around. Anyone who’s played the original for any length of time has toyed with just skidding left and right repeatedly.

Now jump forward nearly two decades and add wall-running. A wall-run is a pre-recorded animation. When the animation ends, the Prince has to go into one of his other animations, such as catching hold of a ring embedded in the wall and swinging himself further onward, or planting his feet against the wall and jumping outward, or plummeting. Unlike simple 2D rotoscoping, a 3D engine allows for blending of animations, and we see that in cases where the player is allowed to interrupt an animation at any point, such as jumping away from a wall-run. Nonetheless, in a lot of situations, animations are allowed to play out in full before further input from the player is acted on. It’s like moves in a fighting game. I compared the combat sequences to a simplified Street Fighter or Mortal Kombat before, but the same movement model, and therefore the same feel, is found in the acrobatics as well.

It should be noted that the developers really did go all-out in producing the movement animations, particularly in the way they accomodate Elika. Elika follows your every move, swinging from the same flagpoles and balancing on the same beams. When this would normally result in Elika occupying the same space as the Prince, there are special two-person animations built around it. For example, if you’re both balancing on a beam and you try to move the Prince into the spot Elika occupies, the two of them execute a tricky maneuver where they swap places by grasping each others’ arms, putting their toes together, and pivoting 180 degrees. When I saw this for the first time, I was incredulous that two strangers could pull that off without exchanging any words. But as the game goes on, you of course get used to such things. Which, also inevitably, means that they stop being impressive. It’s got so that I try to keep significantly ahead of Elika most of the time just so that I don’t have to spend time waiting for the more elaborate two-person animations to execute.

Prince of Persia (2008): Bosses and Combat

Prince of Persia (2008) is organized around groups of four. There are four colors of power-plate, and four distinct sets of zones, each of which is made of an entrance zone, a terminus, and a circle of four zones between them. And there are four bosses, each ruling over one of the four zone groups.

The bosses are a bit like ringwraiths. Former humans with bodies made of black, oily Corruption 1Come to think of it, Corruption strongly resembles petroleum, and the whole game is set in the middle east. I’m a little tempted to read allegory into this, but such things are really too subtle for this game. , they accepted power from Ahriman during their mortal lives, and consequently now serve him for eternity. Their names are apparently forgotten, because they’re all identified by their jobs: the Hunter, the Alchemist, the Concubine, the Warrior. And the peculiar thing is that most of the fighting in the game is against just these four creatures. You have to fight them over and over; every zone has a boss fight you have to win before you can cleanse it. And there isn’t a lot of combat beyond that.

To be precise, I’ve seen three other sorts of foes. In the very beginning, you have to fight some soldiers who are chasing Elika on her dad’s behalf. (Notably, you don’t kill them. They run away when defeated. I recall that The Sands of Time also had a bit at the beginning where you fought ordinary human soldiers before everyone turned into sand-wraiths, but it wasn’t so squeamish about letting them die.) Then there’s a periodic between-chapters battle against Elika’s father himself, who’s not undead yet but probably on his way, if I understand the backstory correctly. And finally, there are lesser Corrupted that spawn at specific points in the paths between corrupted zones — but there’s at most one such point per path, and it’s possible to slip by them without a fight if you’re fast enough. Even if you do fight the lesser corrupted, they’re a lot quicker to defeat than the bosses: if you can back them all the way up to a ledge or wall, you drain the rest of their lifebar automatically. A boss in a similar situation will just teleport closer to the center of the battlefield.

Combat is always one-on-one (apart from Elika’s magical assistance), and feels a bit like a simplified Street Fighter/Mortal Kombat-style fighting game, in that it’s about carefully-timed button presses rather than fluid grace — a charge that could be leveled at the platforming sequences as well. For what it’s worth, I’m rubbish at this sort of fighting. I understand that there are combos to be discovered as well, but the only combos I’ve managed to pull off are the simple ones like “sword-sword-sword-sword”.

All Corrupted, whether minor or boss, have a habit of metamorphosing into forms that are vulnerable to only a single sort of attack: turning the Corruption of their body into a sort of armor with blue highlights means you need to use sword attacks to get it off, a sort of black cloud around the feet and back needs you to pull them out with your gauntlet, and turning into a mass of black tentacles is an invitation to use Elika’s magic. You’re given a help text explaining these vulnerabilities the first time each form is used, but after that you pretty much have to just remember them (unless Elika shouts out advice, as she does sometimes). What I didn’t notice at first is that the combat QTEs work very similarly. I mentioned before not being able to react to the QTE button prompts quickly enough; I now suspect that this is intentional. What you’re supposed to do — what works — is to recognize the situation before the button prompt comes up. If a boss rears up on a tall column of Corruption, for example, it means that you’re about to be asked to press the Jump button to leap out of the way before he falls on you like a wrestler. So for once, we have QTEs that make it worthwhile to pay attention to what’s happening in the gameworld instead of just staring at the UI.

References
1 Come to think of it, Corruption strongly resembles petroleum, and the whole game is set in the middle east. I’m a little tempted to read allegory into this, but such things are really too subtle for this game.

Prince of Persia (2008): Structure and Freedom

I’ve probably been making Prince of Persia (2008) sound more linear and constrained than it is. Let me describe its structure more fully.

Points of PersiaThe map is a highly symmetrical network of zones and passageways. The divisions between zones aren’t explicitly marked; it’s possible to go from one zone to another without realizing it. Each zone starts off in a state of darkness and corruption. In fact, “The Corruption” is the name of a sort of writhing slime that covers any surface that the level designers don’t want you to touch. And each zone has a special spot called “Fertile Ground”, consistently pronounced with a long i, like “fur tile”. When Elika does her sacred magic thing on the fur tile, a Genesis-Effect-like aura spreads out from it, restoring color, making grass grow, and permanently cleansing the zone of the Corruption. (The architecture is left in ruins, but you can’t have everything.) Cleansing all of the zones is pretty much the game’s main goal.

The important thing to recognize about this is that the Corruption is a constraint on your movement. Entering a corrupted zone, you’ll find that you’re mostly confined to a single path. Cleanse it and your options open up. Which is a good thing, because you still have a good deal more to do there. The cleansing magic also makes glowy floating things called “light seeds” appear, turning the zone into a hunt for collectibles. And in this phase, the player has considerable freedom. Yes, you get the same visual cues as always for reaching them, but in some cases I’m pretty sure that I spotted and followed alternate routes to light seeds before I found the preferred one. Notably, light seeds that you collect while falling stay collected even if you get rescued by Elika. I don’t think the preferred route ever actually requires you to be rescued, but it’s a serious option.

Now, with certain exceptions, every zone in the map is open for exploration from early in the game. However, most of the fur tiles (and some of the light seeds) are in places that can only be accessed by means of special magical powers that Elika accesses one by one over the course of the game. There are four different powers, including flight and a power-climb that can take you across ceilings, but they all come down to the same thing: they all, in some way, transport the player from a special colored plate — the color determining the power — to a fixed destination. The plates are another assertion of authorial control: if you could just activate these powers from anywhere, the experience would be in the player’s hands, and we can’t have that.

So, how do you obtain these powers? By collecting light seeds. You get your first power at 60 seeds, the second at 170, the third at 340, and the fourth and last at 540. 540 is significantly less than the amount available, and (as far as I’m aware) there’s no advantage to collecting more after you’ve got all the powers, so obsessive completism is not required, unless you’re like me and just value 100% completion for its own sake. You do, however, need all four powers to complete the game, and that means a lot of hunting and backtracking to find enough seeds. Inevitably, you wind up crossing through zones that you can’t cleanse yet in order to reach ones that you can.

The interesting part, however, is that you can take the four powers in any order. Whenever you go back to the Temple to cash in your seeds, you get to choose whichever of the remaining powers you want. And the order in which you take them affects the order in which you can cleanse the zones. If you want to tackle a particular zone first, you can find out its required power (which is helpfully listed in the map screen’s zone data) and obtain that power first. You still ultimately have to cleanse all the zones, but there’s no particular ordering to them, even though there’s still a Metroidvania-like progression of decreasing constraint.

Prince of Persia (2008): An artifact of its time and place

Prince of Persia on the PC really feels like a port of a recent big-budget console game. I don’t even play recent big-budget console games, and even I can recognize this.

The most obvious signifier is the button icons. There are six basic action buttons: jump, sword, block, gauntlet, talk to Elika, and use Elika’s magic (with effects that depend on context). On a console, these are bound to the four face and two shoulder buttons. With PC controle, all six can be executed with the keyboard, but also, the game rather surprisingly supports up to four mouse buttons: by default, sword and block on left and right mouse buttons respectively, magic and gauntlet on the forward/back buttons that are usually only recognized by web browsers. The trackball that I use for PC games does in fact have these extra buttons, but I think this is the first game I’ve seen that supports them; even HTML-based games tend to not handle paging around through your browser history very well. Anyway, each of these buttons has a circular icon associated with it, each with a distinct background color. Invented for this game, they’re clearly replacements for the standard console button prompts, in both appearance and function: options in menus have button icons displayed next to them, and in the QTE-like moments in combat where you have to press or mash a specific button to execute or avoid a special move, the icon for the required button is displayed on the screen. This isn’t ideal. When it’s in combat, I usually fail to execute the move, because the symbols don’t have a strong association with their associated buttons in my mind. I do have a strong association between the buttons and their actions, but looking at the symbols is like reading a foreign language; it takes me a moment to translate from “green circle with a pair of legs in mid-leap” to “space bar”, and so by the time I know which button to press, it’s too late. I speculate that this is because it’s a two-step associative chain: the icon depicts an action which I associate with a button. On the consoles, it presumably just shows a picture of the button.

The other thing that seems particularly symptomatic of modern console games is the sheer amount of guidance the game gives you. The QTE prompts, where it tells you exactly what button to press, are the extreme case of this, of course, but it goes beyond that. In platforming, the player is basically never trusted to figure out what to do next. Sections of wall where you’re expected to do the Prince’s trademark wall-run 1The wall-run was introduced in 2003’s Prince of Persia: The Sands of Time, and quickly became known as the Prince’s signature move. I’m old enough to remember the original Prince of Persia from 1989, and at the time, I felt that his signature move was leaping across a gap, catching a ledge with just his hands, dangling for a moment, and pulling himself up. But then Lara Croft took that over, and nowadays it’s just expected of any decent platformer hero. are marked with scratches. Even if you get stuck (or, more likely, disoriented), Elika can produce a ball of light that floats ahead, showing the path to your current designated destination. Mind you, you get to designate your destination yourself — the game isn’t linear. That alone saves it from the worst excesses of the don’t-let-the-player-get-lost philosophy. Also, it is in fact still possible to wall-run in non-indicated places, and possibly even to discover shortcuts that way, although there’s a tendency for the solidity of objects to break down when you’re in a place where the game doesn’t expect you. Even so, the intense guidance robs the experience of a certain element of discovery found in prior Prince of Persias. I remember having to look carefully around a room and plan out a route, thinking “Will I be able to reach that beam from that pillar?” and the like.

And in general, the whole player experience seems very planned. The mechanics here don’t allow for a wide variety of alternate approaches. You can’t try to somersault under blade traps like in prior games — there’s no somersaulting (and, indeed, no blade traps). You can’t run away from fights. Combat generally takes place on circular platforms without exploitable environmental features; in the few places where you can exploit the environment, it’s because you’re facing a puzzle-boss who can’t be defeated any other way. The fact that you can wall-run in non-indicated places almost feels like an oversight on the developers’ part. Even when there’s no button icon on the screen telling you what to press and when, there’s a very clear sense that there’s a single right thing to do at every moment, except at planned branch points.

I’ve seen it advised that one should design games by thinking first about the experience that you want the player to have. I get the impression that a lot of big-budget games these days attempt this, but confuse experience with spectacle: they start by deciding what they want the player to see, then implement a game around making the player perform the correct actions at the correct moments to see it. For all the sophistication of its underlying engine, Prince of Persia can be viewed as a descendant of games like Cyberia. There are bits where you slide down a chute and have to clear gaps by pressing the jump button at the right moments, and other bits where you’re sent flying through the air with no control over your trajectory and have to dodge obstacles with the directional movement controls. These are both things that could have been done in a Dragon’s Lair or Rebel Assault engine without significant loss.

And yet I’m still having fun with it, which perhaps means I’m being overly sour about this sort of gameplay. Or perhaps it just points out how shallow fun is as a criterion for judging games.

References
1 The wall-run was introduced in 2003’s Prince of Persia: The Sands of Time, and quickly became known as the Prince’s signature move. I’m old enough to remember the original Prince of Persia from 1989, and at the time, I felt that his signature move was leaping across a gap, catching a ledge with just his hands, dangling for a moment, and pulling himself up. But then Lara Croft took that over, and nowadays it’s just expected of any decent platformer hero.

Prince of Persia (2008)

For our next game, we have Prince of Persia, which unfortunately doesn’t have a subtitle to distinguish it from Prince of Persia. Prince of Persia at least had the excuse of being the only game titled Prince of Persia when it was released, but I’m not playing that one, I’m playing Prince of Persia, the 2008 game with a new “prince” (apparently a thief, although I suspect he’s just pretending and incognito) assisting Elika, a young magician-princess, in keeping Ahriman, the god of darkness, from escaping his prison. I won’t call this a “reboot”, because I think it’s pretty well-established, in “expanded universe” materials if nowhere else, that PoP continuity contains multiple different Princes echoing each others’ stories at various points in history. This is just one of the ones we haven’t seen before.

I have quite a lot to say about the gameplay, but for this post, I’ll just share some early impressions.

The graphical style makes a strong first impression, somehow looking very illustration-like. It’s not cel-shaded, but there’s some similar simplification going on, or maybe it’s just the thin black outlines on the characters that make it seem that way. It reminds me of what little I’ve seen of Street Fighter IV. Still, as usual, it doesn’t take long to get used to it and not notice it any more. Elika’s magical effects, on the other hand, turn her outline and shadows, and sometimes those of Prince as well, into pale blue, and that remains a striking effect when it happens, presumably because it’s not in front of your eyes all the time.

My second strong impression is dismay at the characters’ wardrobe. It’s not nearly as direly sexualized as in Warrior Within, but there’s still a strong “who in their right mind would wear that in public” vibe. It isn’t that they show a lot of skin — both the Prince and Farah wear more revealing outfits in The Sands of Time, but garments in this PoP08 expose skin strategically. The prince wears an impractical-looking muscle shirt that’s cut to show off his slab-like pectoral and abdominal muscles, and yet manages to give the impression that he has no nipples. Elika sports a tattered top that leaves weird portions of her hips exposed and was probably intended to go with some kind of high-waisted skirt instead of the trousers she’s got on. (Those trousers seem fairly practical, mind you, especially in contrast to everything else ever worn by any woman in a Prince of Persia game.) To expand on the contrast: in The Sands of Time, Farah managed to be dignified even in her slave outfit, while the Prince was the hapless victim of gradual wardrobe loss, a symbol of his lack of control over the catastrophe that he himself helped to cause. That was their relationship in a nutshell. PoP08 turns this backward, giving the female lead a torn and ill-fitting outfit that suggests victimhood, and pairing her with a tall, muscular man who looks like he’s dressed to go cruising for chicks.

In fact, Elika’s weakness is a major plot point. Use of magic sometimes drains her to the point where she collapses onto the floor, or into the Prince’s arms. (The Prince manhandles her quite a lot, considering that they only just met.) And yet, whenever the player makes a mistake and jumps off a ledge or something, Elika uses her magic to instantly rescue him, regardless of the circumstances. Even if she’s bound up in a writhing cocoon of magical darkness and awaiting rescue, which is something that happens more than once over the course of the game, she finds a way to break out of it for just long enough to save the Prince, and then immediately becomes bound and helpless again. I suppose you could argue that this shows that the relationship between Elika and the Prince is really one of mutuality, that each of them relies on the other, but it feels more like the Prince’s needs come first, that he somehow has the right to expect a woman who’s suffering from fainting spells to run around making sure that he never has to suffer the consequences of his actions.

Am I being unfair? Perhaps. I have to admit that I simply find this incarnation of the Prince irritating. His type is what I think of as the Brendan Fraser role, all smug and cocksure, with a smirk in his voice. He keeps telling Elika that she ought to get out and live real life among ordinary people, which is not so much a piece of advice as an aggressive act of reverse-elitism, a way for him to act superior and assume authority while at the same time accusing her of the superior attitudes. And in contrast to the Prince’s arrogance in The Sands of Time, which was flaw that humanized the character and made him more sympathetic, it seems like in PoP08 the writer, or possibly just the voice actor, doesn’t even think he’s being arrogant. He’s just trying to be the common-sense voice that the audience agrees with. If the Prince and Farah in TSoT bickered like Tracy and Hepburn, the banter in PoP08 comes off more like the arguments between Spock and McCoy, and has about as much romantic tension. Fortunately, most of the dialogue is optional, and only comes up if you choose to press the “talk” button.

I had to look this up, but a growing suspicion of mine turned out to be correct: the voice actor for the Prince is none other than Nolan North, best known as the voice of Nathan Drake in the Uncharted series. I haven’t played any of the Uncharted games, and certainly didn’t recognize the voice. I just guessed this on the basis of the complaints I’ve heard about Drake.

Anyway, despite all that, I am quite enjoying the actual game. When my mind is on wall-running and leaping across chasms, I don’t much care about what my avatar is wearing, or what he sounds like. And it’s rather compelling, with a strong “one more level and then I’ll stop” factor, possibly assisted by the way that Elika’s automatic rescues keep you away from any kind of “game over” screen or save/load menu.

I recall that these auto-rescues were controversial when the game was first released, and that some people complained that it caused the game to lose something — a sense of danger or whatever. I was skeptical about this; it seemed to me that it was just expediting the die/restore or checkpoint cycle, and thus not really changing the interactivity in any significant way. Well, I don’t quite know how to justify this, but in practice, it honestly does feel different, like your failures are less significant than they should be. Perhaps it’s the fact that it’s happening within the context of the game’s fiction, and thus makes you aware of the cheatingness of infinite take-backs in a way that you don’t notice when it’s at the system level. Perhaps it’s that the game is robbing you of even the possibility of doing things wrong, and thereby reducing the sense of agency. Regardless, it only feels this way for a while. Just like the graphics, I got used to it pretty quickly.

Prince of Persia: The Sands of Time

The hype over the new Prince of Persia game inspired me to do something I’ve been meaning to do for a while: replay Prince of Persia: The Sands of Time, the 3D platforming game that reawakened the dormant franchise. Apart from just wanting to refamiliarize myself with its plot events to see if the sequels make any sense at all in terms of them, I had a specific goal in mind. I wanted to master the wall rebound.

The wall rebound consists of leaping feet-first toward a wall and then propelling yourself sword-first toward an enemy. It’s one of several special acrobatic combat maneuvers in the game that can knock an enemy down instantly, and like all such maneuvers, it consists of a series of button-presses that I couldn’t tell you, even after mastering it. It does no good for the conscious mind to memorize such things. It has to go into muscle memory to be effective. At any rate, although I managed to pull it off accidentally a few times in my initial playthrough years ago, I never really learned how to do it. Instead, I had early on come to rely on the vault move, where you leapfrog over a foe and stab him from behind, which worked really well until I started encountering enemies that could block it, at which point I basically reverted to mundane swordplay. Some time afterward, an acquaintance of mine noted that he was pretty much exclusively using the wall jump in combat toward the end of the game, so I figured I should give it a try and see if it made the endgame easier.

Part of my thought on this matter was that it might be easier to learn all the moves if I used a proper gamepad. I have the PC version, and the first time through, I used mouse and keyboard. Well, it turns out there’s a reason I used mouse and keyboard: the PC version doesn’t support anything else. My gamepad driver can be set up to emulate a keyboard, but I didn’t bother, as it makes the analog controls iffy. Even using the mouse has its problems in that regard: where a modern gamepad gives you four analog degrees of freedom (via two sticks), keyboard/mouse only gives you two. As you might expect, the game binds (camera-relative) movement to the keyboard and uses the mouse for rotating the camera. This is usually adequate, because it lets you move in any direction by positioning the camera to point in that direction and moving forward. But there are a few scenes where the camera jumps to a fixed position and becomes temporarily immobile, and one particular such bit, where you have to swing on a rope and leap off towards a spot that’s just slightly off from straight forward, is made much harder than it should have been. But then, I suppose the parts where you walk along narrow beams are made easier by having a button you can press to go straight forward.

At any rate, I did manage to figure out the wall rebound, but it turns out to really be no more powerful than the vault. Yes, there are enemies who are vulnerable to the rebound and not the vault, but there are also enemies that are vulnerable to the vault and not the rebound. One of the last fight sequences consists entirely of wave after wave of three different sorts of big muscular-looking foes, one that’s vulnerable to the vault, one that’s vulnerable to the rebound, and one that’s vulnerable to neither and which, I speculate, must have some other weakness that I never discovered. This leads me to speculate about the intent behind the combat system: that it was intended to create increasing difficulty by means of increasingly specific weaknesses. Assume that there is in fact a third knock-down move. The earliest enemies would be vulnerable to all three. Tier two enemies would be able to block one move, tier three enemies would block two. The problem with this is that the player would have to be using all the special moves regularly from early on in order to notice it, and once you know one ultra-powerful move, you don’t have a lot of motivation to try anything else. (Call it the Double Dragon syndrome.) Now, I’ve looked at guides at Gamefaqs, and there really doesn’t seem to be any support for this theory there. But that might just be a symptom of the problem. At any rate, however it happened, the end result is that the game got a reputation for weak combat that ultimately resulted in the act of overcompensation titled Prince of Persia: Warrior Within.

But you know something? I don’t really care that the combat is weak and unvaried. Combat is not what this game is about. It’s about climbing things and dodging traps. Combat serves the purpose of breaking up the climbing scenes and providing a little variety, but the bulk of my time spent on the game was spent climbing things and dodging traps.

Or, to some extent, figuring out how to climb things. One thing that struck me the second time around is that this is basically a pretty short game — I can imagine someone who knows what he’s doing playing it from start to finish in a single session. It lasts as long as it does partly because of the time you spent wandering around confused, trying to figure out where you have to go next. The game tries to help you out: the camera is always trying to lead you to the right place by panning or zooming to show you your next goal, but I find that’s often not enough. There’s one bit in the final climb where I could enter a crack in a chimney-like hollow and couldn’t figure out how to get down without dying. The solution? I was supposed to be going up, not down. Once I figured this out, I remembered being stuck in the same place in the same way in my first play-through.

Overall, I’d say The Sands of Time still holds up well. The graphics aren’t quite as detailed as you’d expect today, but graphics had already more or less plateaued in their ability to impress. There’s a nice sense of mystery in the disappearing bonus areas of questionable reality — something that the sequels sensibly didn’t even try to address. And the two main characters, the nameless Prince and his sometime companion Farah, are appealingly human: working together but constantly bickering, plainly attracted to each other but, due to circumstances, unable to trust each other. The scene where the Prince muses to himself about the possibility of marrying Farah had me wincing at his clueless arrogance, but in a good way. This is something the sequels pretty much destroyed in their attempt to macho things up. Even when Farah shows up again in The Two Thrones, she’s been transformed into just another oversexed badass.

The really interesting thing about Farah is that she could easily be the protagonist of her own game, running concurrently with the Prince’s. Farah can go places the Prince can’t and vice versa, due to Farah’s ability to squeeze through small cracks and the Prince’s trademark wall-running, so they spend long periods of time separated. Who knows what puzzles she faces while you’re off doing your part? At one point, she leaves the Prince behind, and in the areas you go through as you try to catch up, the level designers conscientiously included a plausible route of narrow cracks for her.

I notice that I haven’t even mentioned the time-rewinding factor. I guess that means it was just a gimmick.