Darren is a scientist and an educator by day, and a writer and reviewer by night. While he enjoys shooters, RPGs, platformers, strategy, and rhythm games, he takes particular interest in independent games. Additionally, he produces the Zero Cool Podcast, and he plays board games quite a bit.
FULL DISCLOSURE: Darren Nakamura knows several people in the videogame industry, most of whom are Destructoid alumni. These include:
Anthony Burch, writer for Gearbox Software
Ashly Burch, notable voice actor
Nick Chester, publicist for Harmonix Music Systems
Chad Concelmo, writer for Golin Harris
Aaron Linde, writer for Gearbox Software
Jayson Napolitano, publicist for Scarlet Moon Productions
Brad Nicholson, publicist for Uber Entertainment
Alex Ryan, publicist for Kalypso Media
Jim Sterling, notable voice actor
If I could toot my own horn for just a bit, I'd say that I think I'm pretty good at turn-based strategy games. I spent countless hours playing Civilization III, I recently extolled the virtues of Might & Magic: Clash of Heroes, and if one were to take a look at my save file on Advance Wars 2: Black Hole Rising, he'd see a totally golden menu, signifying complete domination over the game.
In Advance Wars 2, I S-ranked every mission in the hard campaign, and made that game beg for mercy. So naturally, going into the critically acclaimed PS3 strategy-shooter, I felt pretty confident in my abilities.
But then the skill ratings started coming in. B-rank on the tutorial mission. C-rank on the next. D-rank, D-rank, D-rank. "What am I doing wrong?" I thought. But after some more consideration, I think the real question is, "What is this game doing right?"
What Valkyria Chronicles does that contrasts it with Advance Wars is so simple, it's impressive how much it changes the game. Rather than the nameless, faceless forces that each AW commanding officer has in tow, all of the soldiers fighting under Lieutenant Welkin have unique names, faces, voices, and personalities.
It originally appears as a throwaway feature in a game about war. The player can set up his squad from a long list of recruits, and he can view short bios on each unit. From there, the brilliance really begins to show. As Welkin fights more battles with a particular soldier, that character's bio page gets updated with more and more information. It implies that while this team is fighting together, they are also talking to one another, sharing with each other their lives, hobbies, dream, and fears. Giving a name to each soldier makes the player feel as though he has not only handpicked this team, but that he needs to take care of them as well.
Gameplay-wise, there is little penalty for losing a soldier in battle. They can be replaced with others of the same class after a battle, with nearly identical combat ability. The only real penalty of losing a nonessential character to the enemy's fire is the weight of guilt on the player's conscience.
After coming upon this revelation, I realize now some things about other games I've played in the past. A more apt comparison to the Advance Wars games is the Fire Emblem series, and yet, the one key difference of permanent character death in Fire Emblem has kept me from finishing the game on two separate playthroughs, while I have beaten three of the Advance Wars games, each two times over.
It has been said that a great military leader is not only one who can win a battle and bring back all of his men, but one who knows when to sacrifice his team to win the war. But if my soldiers have names, I cannot be that man. I am no general; I cannot lead my men to death.
But as I continue through the game, earning my C-ranks and D-ranks, I will take solace in knowing that although I am a poor military leader, not a single member of Squad 7 will be left behind.