10 Video Game Bosses That Were Legitimately Broken
No fun allowed, only pain.
It goes without saying that video game bosses are supposedly to be challenging - they're intended to test players' skill up to that point, presenting some enjoyable push-back while still retaining a sense of fun.
But sometimes developers go too far in their quest to challenge players, and the results basically end up ruining the entire experience.
That's certainly the case with these 10 games, all of them beloved classic titles that nevertheless served up one encounter so cheap, so unfair, and so poorly programmed that players couldn't blame their failure on their own inability.
Some of these bosses were busted enough that players were forced to restart the game entirely, wait for a patch or, worse still, just rage quit the game forever more for the sake of their own mental health.
Others persevered long enough to brute-force their way through, but regardless, every single one of these bosses went above sadistic challenge to genuine betray the rest of the game, while representing anything but quality game design...
10. The Plane Tyrant - Resident Evil – Code: Veronica
Because Resident Evil's signature antagonist isn't terrifying enough already, Code: Veronica decides to hurl a Tyrant at the player within the cramped confines of a cargo plane, and it sure ain't fun.
The goal is to evade the Tyrant's powerful swipe attacks (which can kill you in just a few hits) while weakening him with what little remains of your arsenal, until you can knock him out of the plane with the cargo load.
But if it's your first time fighting the boss, it's highly likely you're massively under-prepared for the fight, which will make it nearly impossible to beat.
While you can technically use a knife to slowly chip away at the Tyrant's health enough to defeat him, you'll need a heap of healing items (which you probably don't have) and a preternatural ability to dodge its attacks.
Many players using just a single save slot had to restart the entire game with a far stricter approach to ammo/item conservation up until this fight.
Given that this would require re-playing almost half of the entire game, nobody could blame you for rage-quitting and never returning.
9. Bed Of Chaos - Dark Souls
As rewarding as it is to beat even the "easiest" boss in a Dark Souls game, occasionally FromSoftware tips the balance a little too far into "bulls***" territory, as they certainly did with the Bed of Chaos from the series' first entry.
The Bed of Chaos isn't a conventional, slogging war of attrition against a giant energy bar, but requires the player to attack three nodes attached to the tentacled plant monster. Naturally, doing so is decidedly tougher than it sounds.
While Dark Souls' best boss fights require the player to learn the enemy's strategy and adjust to it, the Bed of Chaos is sadly reliant on RNG mechanics, giving the player little choice over whether or not they're insta-killed by one of its sweep attacks.
Also, unless you've unlocked a hidden bonfire, the nearest one is an infuriatingly long sprint away from the boss, adding to how much of a dispiriting, charmless chore taking this thing down really is.
The only solace is that the boss retains some damage if the player dies, making it slightly less infuriating than it otherwise might be.
Still, the entire Lost Izalith section of the game is notorious among fans for being blatantly unfinished, and it never becomes more controller-throwingly apparent than in this cheap, lazy fight.
8. Branch D's Final Boss - Drakengard 3
Yoko Taro sure loves trolling players, huh? His action-RPG threequel is defined by its addictive hack 'n' slash gameplay...at least until Branch D's final boss fight, which abandons said gameplay in favour of a brutally difficult rhythm game sequence.
Running almost 10 minutes in length, the fight has no checkpoints and a single wrong move will result in you having to start again, complete with sitting through an unskippable, 40-second pre-fight cut-scene.
Making matters worse, the camera appears to intentionally obscure your view of the action throughout, with Taro presumably wanting players to use their ears rather than their eyes.
This is typified by the fact that, at the very end of the fight, the screen goes black and players are left to play only by ear.
The fight is so ludicrous that fans have even posted videos to help players with the timing, but let's be honest, the fight left many so spiritually broken they just watched the end of the game on YouTube instead.
7. Mike Tyson - Punch Out!!
In the annals of over-powered "f*** you" video game bosses, is there anyone more iconic than Mike Tyson in the classic NES boxing game Punch-Out!!?
Because Tyson was the fiercest boxer on the planet back in 1987, he was selected to be the game's end boss, and true to his real-life rep, he's an infuriatingly difficult one to topple.
Nintendo games may have a history of featuring overly repetitive and easily identifiable wave-based bosses, but Tyson is no such cakewalk.
His attack patterns are inconsistent and unpredictable, requiring even skilled players to study the more subtle giveaways for when he's about to lay down a strike.
Tyson's absurd speed and immense power ensured most everyone failed this thing dozens if not hundreds of times - all the more demoralising as you had to start the game from the very beginning upon failing, unless you knew the Tyson pass code (it's 007 373 5963, by the way).
6. Lawrence Barrett - Deus Ex: Human Revolution
As great as Deus Ex: Human Revolution (mostly) is, the game's generic, unimaginative boss fights were almost universally despised by critics and fans alike, having been outsourced to another dev team due to time constraints during production.
And not one of these fights proved more fundamentally broken than the first one, Lawrence Barrett.
Despite the game granting players the freedom to play stealthily up to this point, the fight requires a mandatory physical confrontation with Barrett, leaving players who committed their efforts to stealth in an incredibly tight spot.
Barrett touts a mini-gun for an arm, is a shameless bullet sponge and has a supernatural knack for figuring out where you're hiding. Oh, and the tight, arena-like confines of the battle make it tough for ill-equipped players to mount much offence.
The fight proved so jarring and unfair that many players felt forced to restart the game entirely and take a less stealth-centric approach, at least until Eidos released a Director's Cut two years later, which added stealth and hacking options to make the bosses less of a headache.
Still, frustrated players had to pay a nominal fee for the pleasure of upgrading to the Director's Cut, rather than Eidos doing the responsible thing and, you know, making it a free patch for all the paying costumers they screwed over the first time.
5. The Star Destroyer - Star Wars: The Force Unleashed
Star Wars: The Force Unleashed is a pretty underrated game for the most part, but there's one hair-pullingly awful, egregiously busted sequence that's an utter failure from a design and testing perspective.
In one level, player character Starkiller is tasked with using his Force powers to rip a Star Destroyer out of the sky.
It was featured extensively in the game's marketing campaign, yet despite its neat premise, it ultimately turned out the worst and most annoying part of the entire experience.
The player has to alternate between using their Force abilities to pull the Star Destroyer and fend off continual waves of TIE Fighters, during which the Star Destroyer will start to revert back to its original path.
The end result is both howlingly mundane and absurdly difficult, especially for PC players, as the sequence wasn't properly optimised for mouse and keyboard controls. Oof.
4. Time Eater - Sonic Generations
Sonic Generations is, for the most part, a damn fine Sonic game, at least until you face off against the final boss, Time Eater, which basically sours the entire experience.
From the irritation of having to constantly swap between the two Sonics to the awkward controls and frustratingly all-over-the-place camera, the fight is basically an exercise in how not to end an otherwise great game.
Above all else it does a horrible job of explaining what the player actually has to do, to say nothing of the sheer visual incomprehensibility of what's vomited on the screen throughout the battle.
It's probably the worst boss in the entire Sonic franchise, and certainly the most annoyingly ill-conceived.
3. Shao Kahn - Mortal Kombat 9
The final fight in Mortal Kombat 9's story mode sees Raiden facing off against the all-powerful Shao Kahn, in a battle that's hideously unbalanced and sees the player trying (and largely failing) to fend off a disgustingly over-powered enemy.
Shao Kahn has an absurd amount of health, his attacks are super-fast and ultra-powerful, he can't be grabbed and he overall represents a major difficulty spike compared to, well, every other fight in MK9's campaign.
Even highly skilled players had no other choice than to resort to cheap move spam, such as teleporting behind Kahn and blasting him with an uppercut ad nauseum until he finally falls.
For a game centred on player skill and precise mastery of its deceptively deep mechanics, it's a damn shame the final story fight ultimately forced lame tactics.
2. Ruby Weapon - Final Fantasy VII
Final Fantasy VII is unquestionably one of the greatest games of all time, but Square Enix arguably took things a little too far with the (thankfully optional) super boss, Ruby Weapon.
The solution to defeating the boss is so bizarrely specific there's little prospect of anyone figuring it out on their own.
Basically, you need to start the fight with two of your party members already dead, which will skip through the first phase of the battle where Ruby is invulnerable.
Once the second phase is triggered (indicated by Ruby burying its claws in the ground), you need to let your remaining character die, but only before tying the Phoenix summon to the Final Attack materia.
This will trigger Phoenix, insta-rezzing your party and giving you a still-insignificant chance of actually beating the bloody thing - it has 800,000 HP, after all.
Some might argue that a superboss is exempt from typical expectations of "fairness", but come on - this was straight-up ridiculous.
1. C'thun - World Of Warcraft
And finally, we conclude with a uniquely broken video game boss that exists within an MMORPG environment - World of Warcraft's absurdly challenging raid boss C'thun.
Back in the early days of the hit MMO, the grotesque Lovecraftian monster presented an unprecedented roadblock to even the most skilled and cohesive of raid groups, capable of quickly wiping all but the most attentive squads.
And as it turned out, in the early days of WoW C'thun was literally impossible to beat, given the boss' ability to cause unfathomable amounts of damage to players clustered together, making it tough to build up a strong damage-per-second offensive.
After several months of complaints, Blizzard finally agreed to nerf C'thun's powers, and the very same day the patch was released, the boss was finally toppled by a European guild.
Needless to say, WoW players have never suffered through quite that level of blatant brokenness since, with Blizzard making a concerted - and some might say over-cautious - effort to ensure that all bosses were killable by smaller raid groups.
But unlike every other busted boss on this list, WoW at least benefited from the shared, communal frustration in those early months.