Batman: Arkham Knight - 10 Things It Must Learn From Origins

4. Don't Make Cuts Noticeable

A clear problem with Origins' rushed release - cuts are never pleasant to notice. A number of elements within Origins were unfortunately axed before it hit shelves in October 2013. The running train from the E3 demo is nowhere to be seen in the main game, and it's fairly clear that Montréal intended for Lady Shiva's side mission to be much larger in scope than it ended up being. City had some pretty obvious narrative cuts as well, with Batman's relationship with Talia never being as fully explored as it was intended to be. The lack of development between the two meant that the pivotal moment in which Batman actually had to choose between saving the city or saving her felt completely unnatural - deviating from Batman's personality rather strangely. Point is, it felt jarring to notice these omissions. Rocksteady are already known for their polish, but every developer is in danger of overstretching themselves in one way or another. Breaking immersion in such a way would be disastrous for Knight.
Content Producer/Presenter
Content Producer/Presenter

Resident movie guy at WhatCulture who used to be Comics Editor. Thinks John Carpenter is the best. Likes Hellboy a lot. Can usually be found talking about Dad Movies on his Twitter at @EwanRuinsThings.