Batman: one of the best superheroes ever, has some of the best villains ever, lead of a currently stellar comic book run, and star of two of the best movies of the past decade. The Dark Knight has been killing across all forms of media, with the exception of video games, where his success wasn’t so successful until 2009, when Rocksteady released Batman: Arkham Asylum and blew away everyone’s expectations. Since then, the surprise hit has grown into a massive franchise all on its own, complete with an animated film, soundtrack, art book, and comic. Arkham City was a massive hit, Arkham Origins was a bit of a step backwards, and this year, Rocksteady concluded the trilogy with Arkham Knight. The game came out to a lot of positive reception, praise for its combat and storytelling, and in some places, is a contender for Game of the Year. Except it really…. shouldn’t be, at least not to me.
Now look, I’m not gonna say that the people who loved Arkham Knight are wrong, because taste is something that there’s no way to gauge for everyone in the world. And to be completely honest, I was on the same train of “OMG this game is amazing” as everyone else was when I first finished the game. But after a while, as I thought about the game more and more, there were issues that I just wasn’t able to wave off.
Incidentally, if you haven’t played it yet, I’m about to spoil it, so fair warning.
The majority of issues with Arkham Knight lie in the story it tries to tell. The previous two Arkham games, Asylum and City, were written by Paul Dini, who a lot of people remember as the man behind the excellent Batman animated series from the 90s. Knight is the first game in the Rocksteady trilogy to not be written by him, and nowhere is this more apparent in this story of jumbled up plot threads than the titular villain himself.
When the game was first announced, Rocksteady said “he’s an original character we created,” but in actuality, it turns out at the end that he’s Jason Todd, the second Robin who died and was later brought back to life as the vigilante Red Hood. The deception would be less of an issue in and of itself, but the real sticking point is that the Knight is a walking reference to something that only exists as a bone to the hardcore Batman fans.
Jason’s never been mentioned in anything related to the Arkham series up to this point. If you haven’t read the comics (or didn’t see the Under the Red Hood movie) and didn’t already figure it out through the sloppily added in flashbacks at the game’s halfway point, you’re just going to be like “who the hell’s this guy?” Once he’s revealed, he just takes off his armor and shifts the color of his helmet to red to show that he’s the Red Hood, disappears, and then just shows up to do Batman a solid as if saving Bruce this one time makes up for kidnapping his friend and putting a gun to his head multiple times.
Knight’s not the only problem with the story. With the Joker dead with a capital ‘D’, the big villains (or rather, the ones who’ve made at least two appearances in earlier material in the series up to now) have all come together courtesy of Scarecrow so they can all kill Batman. The master of fear had a big appearance back in Arkham Asylum as a bit of a trickster, gassing up Batman basically for a laugh at random appearances.
He was arguably one of the best parts of that stellar game before Killer Croc up and ate him, so him back in action as the bad guy sounds like prime time for something more mischievous and sinister, right? Yeah, no. Instead, his grand plan is to get revenge on Batman for his ruined face (not Batman’s fault, but whatever), and his grand plan is to cover all of Gotham in his fear gas, but only hours after he’s told the citizens of Gotham to get the hell out of town or he’ll gas them.
I get that this is all based on comics, a medium where Lex Luthor stole 40 cakes, but why in the seven fucks would you tell people to get out of town and then just gas it when only your private army and the bad guys you personally invited to join you in this plan make up the majority of the population at that point? Poison Ivy, Harley Quinn, and Scarecrow are the only bad guys in the game who had some kind of reason to be involved beyond just showing up to show up. Even Joker just feels like he’s there more out of obligation than out of real need for the story, and while Mark Hamill is once again excellent in the role, his side plot just goes to show how overused he is.
This was an issue in City too; bad guys just being there so Batman has someone from his rogues gallery to beat up every couple of hours. Two-Face and Penguin don’t have anything to do in the story beyond “hey, they’ve been in the last two, so why the hell not?” The real purpose to their hanging around is to justify their appearance for the side missions, and while that’s all well and good, the time spent on little divergent starter missions like Riddler’s whole thing with Catwoman feel like DLC criminals awkwardly stapled into the main plot. Even villains who literally are just side missions, like Deathstroke or Azrael, don’t get the due they deserve; you spend most of your time breaking Deathstroke’s stuff while he insults you, and Azrael’s missions make you wonder why they even included him in City for how much of a non-entity he is.
Arkham Knight is the longest game in the series, but that’s not the praise it sounds like. For the former, it means that the story annoyingly pads itself out and goes on about an hour or two longer than it really needs to. Aside from the story problems and the incredibly bad decision to lock the full ending behind completing everything (the Riddler missions aren’t that fun), blame can be laid on the big new feature that is the Batmobile.
It’s easily one of Batman’s most iconic gadgets next to the Batarang, and the initial announcement had plenty of excitement attached to it. Unfortunately, the vehicle itself isn’t all that fun to play; controls are awkward, switching from normal mode to “battle mode” is just stupid (why would you not want it to be in battle mode?), and the game practically forces you to use it, either with an annoying puzzle or a tedious battle with multiple tanks at once that quickly wears out its welcome. There’s one mission during the tail end of the game where you have to outrun a giant drill. It should be a tense but fun highlight, but after the cutscene ends, the game has your car facing the business end of the drill as it’s ready to tear you to pieces, because that clearly makes sense.
More than anything else, Arkham Knight’s biggest glaring issue is that it isn’t really sure what it wants its title character (the first one) to be. The game literally has a mechanic built around Batman fighting alongside his family, then the story forces them offstage unless it’s to put them in peril. It wants to give him the most iconic superhero line ever, but it feels like it’s only in there because they’ve got Kevin Conroy in the role. If Arkham Knight was just sure of what it wanted from its lead character and had better writing and pacing, it could’ve been a satisfying conclusion. As it is, it’s just like Dark Knight Rises: great, until you stop and think about it.
Guess this really is how the Batman died.
About the author
