Five Years Later: 10 Things You Learn Replaying Batman: Arkham Knight

How does Rocksteady's divisive Arkham threequel hold up now that it's half a decade old?

Warner Bros. Interactive Entertainment / DC Comics

In today's culture, it's rare for a game to universally be expected to be excellent. High profile disappointments such as Watch Dogs and Anthem have created a culture where nearly every major game release brings with it some form of trepidation.

That didn't happen with Batman: Arkham Knight.

Having produced two of the best licensed games the medium had even seen with Batman: Arkham Asylum and Batman: Arkham City, gamers and critics alike were fully prepared for Rocksteady Studios to hit another home run with the finale to their Batman trilogy. The mystery surrounding the identity of the Arkham Knight, and the inclusion of a fully playable Batmobile meant anticipation was high.

Upon release however, the reaction was much more mixed. The Arkham Knight's identity was branded a predictable disappointment, and the Batmobile sections were widely derided for being dull and out of character for Batman. These issues, coupled with a disastrous PC port that was plagued with technical faults, resulted in a much more mixed reaction than the previous two games.

These ten observations come having replayed the game nearly five years later, removed from the euphoria surrounding the its original release, which revealed certain elements of the game which may have been overlooked or under-appreciated upon release.


You either die a hero or you live long enough to see yourself thinking Batman v Superman was actually quite a good movie