10 Movie Franchises That Didn't Care About HUGE Plot Holes

The fact that Batman (Christian Bale) blatantly kills people throughout the Dark Knight saga wouldn't really be considered a plot hole if not for the almost fetishistic obsession Christopher Nolan has with Batman's no-kill rule.

It's a major plot point throughout the trilogy that the Caped Crusader won't cross the line of killing his enemies, to the point that The Joker (Heath Ledger) even tries to goad him into it in The Dark Knight.

But this completely ignores the fact that Batman killed many people in Batman Begins: he burned down the League of Shadows' base and left countless unconscious acolytes to die, and at the end of the movie brought about the circumstances through which Ra's al Ghul (Liam Neeson) was killed.

The movie tries to hand-wave it with the "I don't have to save you" shtick, but as any first-year law student will tell you, creating a deathly situation and then failing to prevent death is open-and-shut manslaughter.

Meanwhile in The Dark Knight, he literally tackles Harvey Dent (Aaron Eckhart) off the top of a ledge, killing him.

Though this was done in order to save Jim Gordon's (Gary Oldman) young son, a kill is a kill, and if you're going to govern yourself by such an arbitrary, black-and-white no-kill policy, then you're also going to be held accountable by it.

But Bats' secret blood-lust doesn't even stop there: in The Dark Knight Rises, he fires at Talia al Ghul's (Marion Cotillard) stolen Tumbler, causing it to crash and mortally wound her.

The character logic here is all over the place, which in a superhero trilogy so thoroughly driven by its central character is a major failing.

If Nolan could've just brought himself to deal with the complexity of a hero being shackled by an honour code, then it wouldn't have been a problem.

But clearly, the director wanted the audience to believe the laughable assertion that Batman's never really killed anyone.