8 Video Games That Killed You By Accident
Wrong place, wrong time.
It probably goes without saying but the actual act of creating a video game is an incredibly challenging affair.
Beyond all of the hours spent learning how to correctly animate your lead hero’s rad 90’s soul patch, you’ve got the almost monolithic task of slotting all of your pieces together in a manner that won’t keel over and die at the first hurdle.
It might be shocking to realize, but even the biggest triple-A video game titles that have had months, even years of careful attention and millions of dollars poured into them, are basically held together with duct tape and the collective will of every developer who worked on it.
Therefore, it’s not at all surprising to find that glitches and bugs still end up making their way to market from time to time.
From the missing faces of Assassin's Creed to the absolute insanity of the Cougar People from the original Red Dead Redemption, some glitches go on to become absolutely infamous, yet rarely do these little bugs end up absolutely destroying the player.
Well, these examples are at the top of the sh*t list as not only did these coding errors ruin the immersion, but in some cases obliterated their chances of ever finishing the title!
8. Broken Pro Mode Broken QTE’s! - Resident Evil 4 (Switch & PC)
If you’re anything like us, then you’ll have played through the majestic Resident Evil 4 multiple times, experiencing the joys of the kinetic action, horrible monsters, and of course, Leon S. Kennedy’s floppy fringe again and again.
However, if you were playing the game on PC or Switch, you might be experiencing another terrifying scenario, that being that the QTE’s randomly never seemed to work!
To be more specific the bug only reared its head in Professional Mode, which required the player to smash buttons quicker than other difficulties during certain Quick-Time Events, yet thanks to an issue caused by the frame rates on both Switch and PC, the player literally couldn’t input them fast enough when using keyboards or Switch Pro controllers!
Professional Mode punishing Pro controller users? That’s deeply ironic. Although I doubt that Switch players were appreciating the situation and more likely screaming at their TVs as to why the hell things weren't working as intended.
7. Inverted Difficulty - Spec Ops: Stealth Patrol
If there’s one thing that we know more than ever thanks to films, TV, and video games hammering home the point, it’s that war is indeed Hell. Therefore it might be tempting to nudge things in your favor a little when it comes to lacing up and hitting the trenches by dropping down the difficulty in war-based video games.
Well, I’ve got some bad news for you, my friend, because if you were looking for an easy ride in Spec Ops: Stealth Patrol then you’re going to experience a world of misery and pain.
This is because thanks to an issue with coding, the difficulty settings for the highest and lowest challenge were swapped by accident meaning that if you selected “Private” you were going to be absolutely obliterated by crack shot enemies and bullet sponge bosses!
Therefore those looking to ease themselves into the waters of war ended up being drowned without even knowing why!
6. Fast Travel... Into The Void - Batman Arkham Origins
While it might not be on anyone's vacation destination list, Gotham City is a big old lad with a tonne to see and do. Mostly the things to see are people getting beaten up by Batman and the “do” are doing a U-turn out of the city as soon as possible because the place is an utter hell hole of villainy.
That being said, at least the rain and endless population of goons are mildly better than the cold black void of nothingness that players could easily find themselves in thanks to a horrible bug in Batman: Arkham Origins.
For some reason a coding conflict when using the games fast travel system would open up a litany of issues, and on launch, players reported that the Batwing would take forever to take them to their chosen destination, long enough in fact that some people reset the game assuming it to have been stuck in a hang state.
Yet things got even worse for those that did wait out the lengthy ride, because when loading the player back into the map, certain locations wouldn’t render correctly causing Batman to fall into the floor and the endless void below.
To add some Joker Gas to the cake, the game would also autosave at this point, meaning you were now trapped forever, requiring a full save reset to get going again. Brutal.
5. No Boss For You - Bubble Bobble Revolution
A tough and unfair boss battle can be the bane of many players' existence, causing hours if not weeks of game time spent trying to figure out how to counter-cheese these walking fromageries of fury.
Yet you know what’s even more infuriating than that? A Boss that doesn’t even bother to bloody show up! Such was the case of the rather abysmal DS title Bubble Bobble Revolution, which was meant to be a celebration of the series but ended up being jeered instead of cheered thanks to a horrible bug on the game's 30th stage.
Once reaching the end of a stage, a boss is meant to appear to challenge the player, but the bastard must have slept through his alarm because nothing happens!
Because the player can’t progress and because there’s no time limit, you’re stuck here for eternity meaning that while this technically didn’t kill the protagonist, it bloody well will kill your interest in this skip fire of a game.
4. Deadly Regular Enemies - Outriders
Poor old Outriders, it’s not had a particularly smooth ride since launch.
From developers People Can Fly tweaking the endgame loop to be less rewarding so it buys them time to make more content, to full inventory wipes, to the horrible server issues that caused a shocking 93% of player drop-off at one point, it’s a clear example of a game which should have spent more time in the oven.
Yet, even when you are able to play the game, that doesn’t mean things are going to end well for you, as thanks to a new glitch that was introduced in the patch fix for the inventory wipe issue, players can now be killed in just one hit by regular enemies.
That’s right, your badass world warrior can be taken down in just a single blow by a regular grunt all because the code of Outriders looks like it’s gone ten rounds with Mike Tyson in his prime.
Developers please, take some time to fix your games before launch.
3. Full Factory Reset - Ratchet & Clank: A Crack In Time
The Ratchet and Clank series may indeed be running at full steam once more with the recent PS5 drop wowing audiences around the world, but is it really surprising that a series with this much wrench-whacking has seen the series loose a few screws along the way?
There are numerous horrible bugs that not only kill player progress but in some rare instances the system itself. Take for example A Crack In Time, which had players reporting that using the Dynamo Of Doom in the Battleplex Arena Fights would cause two lines of code to enter a state of conflict, and as you can imagine, when a video game begins arguing with itself that’s never a good thing!
This conflict caused such a cascade of faliures that not only would players save files become corrupted, but it could actually affect the PS3 itself leading some to have to perform a full system reset!
At least players could play the game again afterwards, small consolation I know, but the same couldn’t be said for the poor souls playing Secret Agent Clank on a PS2 slim, because thanks to some horrific hardware issues, the game would soft lock sometimes and scratch the bloody disc rendering it unplayable!
2. Slimline PS2 Catastrophe - Jax X: Combat Racing
Poor old Slimline PS2, you can’t catch a break, can you? As here you are again killing players through no fault of their own!
So to be clear, we absolutely adore Jak X: Combat Racing as it’s a genuinely fun burnout-inspired kart racer complete with all the vehicular violence you could ask for. It’s got a dumb but funny story, addictive gameplay, and some really fun multiplayer options.
It’s also got a monstrous glitch that will absolutely obliterate your save file should you play the game on a PS2 Slim. The glitch would cause your save file to become corrupt, but to such an extent that while you could keep saving over it, the underlying problem would remain, meaning that when you tried to load the game back up again, the save would load the game state but be unplayable, and would then deny you the ability to delete it!
You were simply stuck with this half-game state, being unable to progress and unable to delete it, and short of playing the game on a different PS2 model or doing some dodgy internal reworking, this was you absolutely done for.
1. Dying In A Cutscene - Spider-Man (PC)
I have incredibly fond memories of the original PS1 Spider-Man game. The graphics, at the time, were impressive, the level of detail and love for the source material awe-inspiring, and the ability to unlock all manner of amazing secrets was just the icing on the cake.
However, for PC players, they likely had a bit of a different experience, as the old Web-head head was turned into a complete blockhead when it came to the developers messing up the port. The game was optimized around PCs at the time of the original release in 2000, however, when the game landed in 2001, significant changes to most players' rigs caused the game to process things at a higher frame rate.
This change affected one level in particular in a major way. During a sequence in which Spider-Man chases Venom through a block of flats, the game uses an in-engine cutscene to move the action along, culminating in Spider-Man jumping out of a window and giving control back to the player.
On the PS1 this works as intended, but on PC’s running at a higher frame rate, Spider-Man jumps too soon and clonks his head on the window, not making the jump and sending players to their deaths over and over.
There was literally nothing they could do to save poor old Peter and watching this massive glitch get roasted in forums was about as painful as the lump on Spidey’s head.