20 Worst Game Breaking Bugs & Glitches

The Batman: Arkham series features some of the best superhero games ever developed, from 2009’s Batman: Arkham Asylum through to 2015's Batman: Arkham Knight (and, no, we’re not counting Suicide Squad Kill the Justice League). Each new instalment gave us better graphics, gameplay, villains and storylines, building an authentic Gotham we could live and breathe.

While 2013’s Batman Arkham: Origins is not the best of the series, it features everything we would want from a prequel entry, set years before the first Arkham game. The story is built around a gang war between a pre-mutation Bane and a healthier Joker, and offers us access to aspects of Bruce Wayne’s younger life never before seen in the series.

Sadly, then, Origins was hampered by glitches and technical issues from its launch. It wasn’t uncommon for the game to crash or freeze, and falling through the scenery became a quirk of a long gaming session. While generally this bugginess was possible to play around, there was one deadly flaw: if the game glitched, froze or crashed while it was saving, the save file was corrupted and it was game over. WB Montreal released some patches and fixes to deal with this, but not only was way too little attention afforded to it, they gave up on this kind of technical support within the first year of release.