Video Game Trilogies With the Worst Endings
Arkham Knight
Batman: Arkham Asylum, when released, was the best Batman, nigh, superhero game ever made. When Batman: Arkham City was released, it took that title for itself. Sadly, Batman: Arkham Knight wasn’t able to do the same. It came nowhere near that title either. Arkham Knight is in no way a bad game, per se, but it’s a bad Arkham game. The first two games in the trilogy, and even the prequel, sat high on the pedestals of video game storytelling.Their plots were unique, exciting, fun and most of all, inherently Batman.
In Arkham Knight, any somewhat-seasoned Batman fan could have called the identity of the Arkham Knight right from the get go. That’s because the plot of this trilogy finale is the same storyline that sees Jason Todd as the Red Hood. Jason Todd is brutally beaten by the Joker. He’s angry with Batman for failing to save him. As a result, he exacts revenge on Batman as a masked villain. This plot was exciting 20 years ago in comic books; not so much in what should have been the greatest superhero game of all-time.
Beyond the story, the game also implemented the one thing that players have wanted since day one: the Batmobile. Instead of relishing in the joys of driving one of the greatest vehicles in pop culture, players were forced to endure lengthy, repetitive and worst of all, boring missions in the tank-mode of the Batmobile. They even botched a boss fight with one of Batman’s greatest adversaries, Deathstroke, by turning it into a tank-on-tank fight. Arkham Knight, I love you, but you were not the Batman video game we needed or deserved.
