Army of Two (PS3)

(Page 1 of 2)

After months of starts and stops; after EA gave Army of Two the green light (prematurely, it turned out) and sent review builds out to reporters last fall only to subsequently announce that said builds were not actually ready for prime time and that we should disregard them; after more retooling and retweaking; after some speculation among my fellow journalists that EA would dump the IP outright, cancel the game, and cut their losses; after all this, the curtain parts, and Army of Two, easily among the most beleaguered titles in recent memory, tentatively steps into the spotlight.

Ta da.

Nervous as a parent at a ballet recital, I loaded up the review build, quietly rooting for Army of Two in its early moments. Why the emotional attachment? Three reasons: One, I have a weakness for trying to find the good in supposedly damned games; two, I respected EA for realizing the game needed more development time and for tinkering with it for a few extra months rather than pushing yet another piece of crapware onto consumers; and three, I'm personally partial to co-op play as opposed to Halo-style kill-them-all-and-let-the-server-sort-them-out Deathmatches.

Around 20 minutes into the game's introductory tutorial, something terrible happened: the review build crashed. Worse still: a week later, the game crashed/froze again while playing the final boxed version of the game on the PlayStation 3.

So far, it looked like this cursed project was still cursed.

The game tells the story of a hyperbolized, war-torn world where the traditional government-run military has been replaced by privately owned and operated teams of mercenaries-for-hire. Unfortunately, these privately owned mercenaries have decided to make a grab for power, causing corpse-generating dust-ups in Somalia, Afghanistan, Iraq, China and Miami. Each geographic site functions as a discrete level in the game.

Playing as either Rios or Salem, a couple of square-jawed, bull-necked soldiers who in spirit are second cousins to Gears of War's Marcus Fenix, I was dropped into various war zones and assigned a series of objectives and targets, each worth a specific dollar value. Example: "Eliminate weapons cache for $4,400."

The object of the game, of course, is to use teamwork -- wits, strategy and firepower -- to gain the upper hand against foes. This is generally done by having one member of the team gain the attention of the enemy horde while the second member sneaks around behind and shoots them while they're distracted.

In the game's vernacular, the one doing the distracting is generating Aggro, the gaming equivalent of waving your arms in the air, letting out a wolf whistle, and saying, "Woo hoo, bad guys, over here!" The more Aggro one generates -- you'll literally begin glowing red -- the more interested the enemies become in you.

This is the core gameplay dynamic of Army of Two: guy number one does the distracting while guy number two does the sneaking/killing/maiming. Unfortunately, the inherent problem with this dynamic is that generating Aggro, turning yourself into a human bullet-cushion -- in short, being guy number one -- is dramatically less fun than doing the sneaking/killing/maiming, aka being guy number two. When playing cooperatively, no matter if I played online or via split-screen, petty arguments inevitably broke out between me and my partners. Example:

"OK, you do the Aggro this time. Over."