Showing posts with label bad boss battles. Show all posts
Showing posts with label bad boss battles. Show all posts

Thursday, March 12, 2020

Bad Boss Battles in Gaming History - Part Ten

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!
  • Pokemon Sword and Pokemon Shield (NSW)
  • Luigi's Mansion 3 (NSW)
  • Spyro Reignited Trilogy (PS4, XB1, NSW, PC)
  • Sonic Mania (PS4, XB1, NSW, PC)
  • Super Monkey Ball: Banana Blitz (PS4, XB1, NSW, PC, Wii)

SPC just can't seem to get away from the number ten this week. Earlier the site celebrated Mario Day on March 10th, which saw a top ten list of the ten best Mario games of the past ten years, and now the tenth installment of Bad Boss Battles in Gaming History arrives in style on the site.

A good boss battle sticks with you for all the right reasons, and soon after beating it, you want to go back and do it all over again. The bosses on this list, however, are the absolute opposite of that, for the most part. These are annoying, broken, unfair, poorly designed, or just plain old disappointing. Whatever the case may be, the following boss battles lean more towards bad than fun, and as we'll see, even the greatest of games can have lulls in excitement and entertainment when it comes to their bosses while some shouldn't have included them to begin with.

Before we begin, though, check out all nine previous parts of this ongoing series of articles, and then check after the break for the latest boss entries:




Thursday, August 1, 2019

Bad Boss Battles in Gaming History - Part Nine

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • Marvel Ultimate Alliance 3: The Black Order (NSW)
  • Crash Bandicoot 2: Cortex Strikes Back (PS1, PS4, XB1, NSW, PC)
  • Crash Team Racing: Nitro-Fueled (PS4, XB1, NSW)
  • Super Mario Galaxy 2 (Wii)
  • Killzone 2 (PS3)

Exactly one week ago, SuperPhillip Central took a look at some of the best boss battles in games. Now, the site takes a decidedly different approach with some truly terrible boss battles. After all, you've got to take the good with the bad, the yin with the yang, and any other cliche that you can come up with. These bosses can be frustrating, unfair, poorly designed, no challenge, or are otherwise--and most important of all--just not any fun for varying reasons.

Check out past installments of Bad Boss Battles in Gaming History with the following links, and then check after the jump for this edition's picks.




Tuesday, May 2, 2017

Bad Boss Battles in Gaming History - Part Eight

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • Yooka-Laylee (PS4, XB1, PC)
  • Metroid Prime 2: Echoes (Wii, GCN)
  • Ys I (Multi)
  • Mega Man X2 (SNES)
  • Sonic the Hedgehog 2 (GG)

A good boss battle is one that sticks with you long after you've beaten it. It's fun, it's inventive, and it challenges you in a fair way. A bad boss battle is one that sticks with you like something on the bottom of your shoe. No, not gum. Something worse (and stinkier). They can be poorly designed, irritating as all get out, and just plain not fun to play. They can end a play-through, or at the very least make you dread getting to that point in a game, a game you otherwise really enjoyed. Some of the bosses on this edition of Bad Boss Battles in Gaming History can qualify as those. Some more than others.

Before checking out these five additions to the list, check out all past volumes of Bad Boss Battles in Gaming, found in the following links:


Because of possible spoilers, please find the continuation of this article after the break.

Thursday, November 24, 2016

Bad Boss Battles in Gaming History - Part Seven

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • The Legend of Zelda: Skyward Sword (Wii)
  • Hyrule Warriors (Wii U, 3DS)
  • Bloodborne (PS4)
  • Final Fantasy Tactics (PS1, PSP)
  • Mega Man 2 (NES)

Thanksgiving was celebrated for a lot of folks in the States, and while you may have had your fill on turkey, dressing, and all the fixings, I would like to talk about a different kind of turkey. No, it has nothing to do with the feathered creature at all. I'm talking about boss battles that are turkeys-- fights that are annoying, badly designed, or just plain "ICK!" Check out past parts of Bad Boss Battles in Gaming History with these links:


The Imprisoned - The Legend of Zelda: Skyward Sword (Wii)


The Legend of Zelda: Skyward Sword is a pretty polarizing entry in the franchise. That's the case either because of the motion controls or the game's need to hand-hold for a significant duration of the adventure. I'm on the side that really enjoyed the game, finding the motion controls to be an extension of my own movements, really feeling like Link doing away with enemies and solving puzzles either in the overworld or in dungeons.

By and large, Skyward Sword features some of the most entertaining boss battles in the series. That's why it's so disappointing that one of the worst bosses in Zelda's history doesn't just show up in the game once but three times!


This boss is the Imprisoned, a big black beast that either marches slowly or slides and slithers around on its belly. While each encounter with the Imprisoned has some variations, the fact that you have to face it three times turns a game I can go back to easily into one that makes me think twice about doing so. Everything from how annoying it is to deal damage to the time constraints you have to beat the boss in time creates one Zelda boss that I hope I never have to fight again.

The Imprisoned - Hyrule Warriors (Wii U, 3DS)


...DAMMIT! Here's a first for Bad Boss Battles in Gaming History-- the same boss appearing two times in one volume! While the Imprisoned was indeed a tedious pain in Skyward Sword, it managed to be just as obnoxious and maybe even more so with its various appearances in Hyrule Warriors for the Wii U and Hyrule Warriors: Legends for the Nintendo 3DS.


In Hyrule Warriors, whenever the Imprisoned appears on the map, you know you're in for a fight. It's a battle of attrition as you slash, slice, or slam away at the standing beast's toes. Once those have been eliminated, the Imprisoned falls onto its chest. It's here where the boss's health gauge is vulnerable. The fact that even with a relatively strong character you're still slowly chipping away at this foe's health is one to be aware of and dread. Then, when it rises back up to its two feet, it starts sending out utterly painful shockwaves with each step, making getting in to take out its respawning toes all the more annoying. The Imprisoned is a creature that had a lot of promise in Skyward Sword, whiffed at that (thrice), and then whiffed at it again with its appearance in Hyrule Warriors.

Micolash, Host of the Nightmare - Bloodborne (PS4)


Generally the bosses in FROM Software's highly acclaimed series of Souls games feature fun, frenetic action with a challenging-but-never-unfair difficulty. I say "generally" because one of the bosses in the much beloved PlayStation 4 exclusive Bloodborne does not meet these qualifications.

Micolash, Host of the Nightmare-- I'll just call him Micolash for short, as he isn't really deserving of such an extravagant moniker-- is a boss that has you slowly pushing through enemy after enemy while trying to navigate a labyrinth. The enemies are annoying to contend with, and the maze itself is a confusing mess.

Upon catching up to Micolash, the "fun" continues, except this time it's in the form of an attack that can kill with one strike. May I also add that this boss absolutely loves to use this one-hit kill move over and over and over again? Micolash from Bloodborne is a rare miss from the developers as an entertaining boss battle, as he is anything but.

Wiegraf / Velius - Final Fantasy Tactics (PS1, PSP)


Final Fantasy Tactics is an often loved spin-off in the famed RPG franchise. Its ability to craft an engaging narrative while giving players a robust turn-based tactical RPG is something that many developers still try hard to beat, and often fail at doing. While the majority of the game makes it my favorite tactical RPG around, there is one sticking point for many a-beginner that if you don't have prior information to, you're probably going to find yourself cussing like a sailor.

Riovanes Castle is a three-part area in Final Fantasy Tactics. The second part is the most challenging, having Ramza face off against villain Wiegraf in a one-on-one confrontation before moving back to his starting spot. Then, he pulls out the Aries stone and transforms into the hell demon Velius. While it may be comforting that Ramza's party enters into the fray, it's short-lived, as Velius summons three Lesser Demons to settle the score.


Velius and the Lesser Demons are extraordinarily tough customers, but that would be fine and would make for a challenging boss battle. What makes this battle bad is how Final Fantasy Tactics' save system works. You are able to save your data between each of the three parts of Riovanes Castle. The problem is that you can become stuck in an unwinnable fight by being under-leveled with no way to return to the world map, because when you lose the fight, you get a game over, forcing you to reload your save. If you saved in between the first part and the second part of Riovanes Castle, you're stuck doing the second fight. Many promising save files were put to an abrupt end by not only not having a second save before entering Riovanes Castle, but also the largest jump in difficulty seen in the game yet. Some really weird oversight must have slipped by the developers, because for many, the many hours it takes to get to this point of the game meant that some just gave up and didn't get to enjoy the rest of this otherwise fantastic game.

Boobeam Trap - Mega Man 2 (NES)


Ending on a game that is a part of the recently released NES Classic Mini from Nintendo, Mega Man 2 is one of the greatest adventures the Blue Bomber has ever had. (Though I do prefer 3, but that's an article for another day.) However, there is one boss in the game that makes the game less than perfect: the Boobeam Trap, found at the conclusion of Dr. Wily Stage 4.

The boss is like a puzzle. Sounds cool so far, right? There are several Boobeams that are positioned out in the open and behind walls. These enemies require Mega Man to use Crash Bombs to destroy them, all the while they occasionally launch projectiles at our hero. The problem comes from the limited amount of weapon energy for the Crash Bomb that Mega Man has. He can only shoot seven bombs before his weapon energy is empty. The puzzle comes from being required to destroy all Boobeam targets before Mega's weapon and life energy runs out.

The problem here is that many Boobeams are placed beyond walls that also require the Crash Bomb to destroy them. So, in essence, you have to use all seven of Mega Man's Crash Bombs smartly and perfectly to solve the puzzle, or else you'll not only be unable to beat the boss, but when you are put back outside the boss room, you'll have to tediously round up enough weapon energy capsules from fallen foes to have a full supply of Crash Bombs to try the boss fight again. Sorry, but puzzles like these not only have no place in a Mega Man boss fight, but it makes for a really sizable sore spot in an otherwise excellent game.

Thursday, October 1, 2015

Bad Boss Battles in Gaming History - Part Six

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • Star Fox Adventures (GCN)
  • Metroid: Other M (Wii)
  • DmC: Devil may Cry (PS3, 360)
  • Borderlands (PS3, 360)
  • Resident Evil (PS1)

Are you ready for part six of Bad Boss Battles in Gaming History? In a sense, I'm going to be beating these bosses all over again, but instead of with Arwings and Power Beams, I'll be using the might of words to skewer these disappointing, annoying, boring, and/or awful bosses. If you have recommendations for bad boss battles for future installments of this long-running series, SuperPhillip Central would love to have them. First though, let's get you caught up to speed on past entries of the series:


Thursday, July 23, 2015

Bad Boss Battles in Gaming History - Part Five

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • Batman: Arkham Knight
  • Batman: Arkham Origins - Blackgate
  • Castlevania: Lords of Shadow
  • Ratchet & Clank: Going Commando
  • Various Super Mario games

Welcome to some more boss bashing! It's part five of Bad Boss Battles in Gaming History, where we take a look together at some of the poorer fights, confrontations, and encounters within video games. These fights can be boring, annoying, anticlimactic, or just plain not fun. Since there are spoilers in these articles, you can check out part five after the break.

Thursday, February 26, 2015

Bad Boss Battles in Gaming History - Part Four

WARNING: POTENTIAL SPOILERS FOR THE FOLLOWING GAMES AHEAD!

  • Uncharted: Drake's Fortune
  • Gears of War 2
  • Super Meat Boy
  • Mega Man X6
  • Yoshi's Story

Bad Boss Battles in Gaming History is back, everyone, for another installment! It's time once again to take these bosses to the woodshed, but this time I'm not going to defeat them, I'm going to roast them for being the total opposite of good. Whether they're annoying, misplaced, not any fun, hard for all the wrong reasons, too easy, or something else negative, I'm putting these five boss battles in their rightful place as bad ones!

Atoq Navarro - Uncharted: Drake's Fortune (PS3)


Before we begin, I'm referring to the entire chapter, Chapter 22 - Showdown, in Uncharted: Drake's Fortune as the fight with Atoq Navarro, the final boss of the game. What occurs is a series of shootouts that has hero Nathan Drake ducking behind cover in the form of crates to pick off Navarro's henchmen and blasting the destructible boxes that Navarro hides behind.


The basic but still annoying premise of this chapter is to blast the boxes that Navarro uses as cover so they break apart, giving the main villain reason to retreat. Drake must time his shots carefully, as Navarro is equipped with not only his three mercenary henchmen in this first outing, but also a high-powered shotgun that can take an unassuming player down in seconds. With Navarro retreated, Drake can focus on the mercenaries, killing them before making chase.


The next setup has three more mercenary enemies, Navarro, and boxes for Drake to take cover behind. However, the latter can be destroyed by the henchmen and Navarro, so it means that Drake only has a set amount of time to take care of all four before he's proverbially naked, able to be killed quite quickly.

Once Navarro's cover is destroyed by Drake, he once again retreats. When the mercenaries are dead, Drake can run after him. This last arrangement has Navarro hiding behind indestructible cover, so here Drake has to pick off each of the three mercenaries one by one before Navarro runs away to a final platform.


It's here that Navarro stands out in the open, shooting in several bursts. When the shots finish, Drake can exit cover, move into Navarro's proximity and start a quick-time event, displaying Drake punching the snot out of his rival. A second time this is done, and the finale of the game occurs with Navarro's foot getting caught in a rope's loop, pulling him underwater to drown.


The timing required for the majority of this chapter is so precise that it makes for a highly frustrating experience for a player without the proper knowledge. Not only that, but throwing in a cliche quick-time event when Uncharted: Drake's Fortune had little to none prior to the endgame, makes for an unexpected change in gameplay. It all adds up to a painful to play chapter, and a very good reason why I don't generally like to replay the first Uncharted game.

Lambent Brumak - Gears of War 2 (360)


From the chapter in the book of "Bad Boss Battles" called "Total Letdowns of Bosses" comes this final boss from Gears of War 2, a title that had plenty of other issues with it outside of a disappointing final boss to worry about. Throughout the game it seems that a villain known as Skorge will be the final challenge to defeat in order for the Gears crew to successfully (but temporarily) save the day. In fact, Skorge is all but given the red carpet treatment to be the final villain to face.


However, players are thrown a curve ball when Skorge is defeated in the penultimate chapter. While some games would then have a more powerful, more dreaded, and more awesome challenge to take what was perceived as the main villain's place, Gears of War 2 instead gives players an incredibly weak on-rails sequence that ends with thirty seconds of holding down one button to take down the Lambent Brumak, the final boss of Gears 2, with the Hammer of Dawn weapon. "...That's it?" is a common thought or utterance to come from one's mind or mouth after the brief and deflating confrontation takes place. Ironically, the developer behind Gears of War 2, Epic Games, made a totally un-epic finale to their game.

Little Horn - Super Meat Boy (PC)


It's no coincidence that the boss that awaits you in the world called Hell is also the one that feels like hell playing. Super Meat Boy is an otherwise wonderfully designed game with clever, tight and responsive platforming that is quite fair. Usually when you die, it's because you didn't play well enough. However, the boss in the Hell world of Super Meat Boy is the antithesis of great design. Good bosses telegraph their attacks so you can be observant of that and hopefully evade them. Little Horn in Super Meat Boy is not a good boss.

In this boss fight, Little Horn pounds his big meaty hands on the platform he resides behind, as well as taking his forehead and smashing it to the ground, requiring you to dodge his offensive advances. The issue here is that again, there's no way to determine what attack is about to do, meaning that defeating the boss on one's first try is nigh impossible. Instead, you will most likely face Little Horn dozens upon dozens of times in order to simply memorize his attack pattern, as his attacks go in the same order every time. This is not good design, and it's confounding to me how a team that did everything else so terrifically with Super Meat Boy did so inexcusably horrible with this one boss fight.

High Max - Mega Man X6 (PS1)


Let me get this out of the way-- Mega Man X6 is a poor Mega Man game, and the second weakest Mega Man X game on home consoles. It's got a fetish for one-hit kill spikes, and it suffers from massively horrid level design. Now that I've let out that bundle of sunshine, let's talk about the boss of the second level of Gate's Laboratory, High Max.

High Max is a greatly annoying boss to fight due to his high defense, high health, and just how long the battle with him takes. Even if you cheese the fight through running into him with Commander Yammark's special weapon and purposefully take damage to do so, the fight is still a lengthy one.


The boss starts out by summoning two powerful force fields on both of his sides. At least one of these needs to be destroyed through giving an insane amount of damage to it for it to be removed, thus allowing you to unleash your attacks directly to High Max. You only get to hit him a minuscule amount of times before he calls back his extra defense.


The fact that one needs to actually cheese through the fight to take down High Max more quickly makes the battle such a bad one to me. Otherwise, you're stuck damaging the boss for small amounts of health each round his force field is down. It's just another thing to add to the pile of why I don't particular care for Mega Man X6.

Cloud N. Candy - Yoshi's Story (N64)


From a frustratingly time-consuming boss to an insultingly easy boss, Cloud N. Candy is but one of the bosses that can be battled halfway through the Yoshis' journey in the Nintendo 64 cult classic Yoshi's Story. It's obvious that Nintendo developed this game with children in mind. It's a simple game to beat, but it's a much more challenging one to master. Sure, you can just randomly eat any fruit to collect the 20 you need to complete a level, or you can do the incredibly challenging act of finding and munching down all 20 melons in a given level.


Nevertheless, there is no level of mastery needed for the battle again Cloud N. Candy, a cute play on words of "cotton candy". The boss slowly moves around the battlefield (or should it be a called a "massacre-field" since the boss is so darned simple to beat?), making large, floaty jumps in the process. All Yoshi has to do is take its tongue, lick, and lap up parts of the boss. With each successful lick, the boss becomes smaller and smaller. No worries about taking damage, as each time Cloud N. Candy has a piece taken off of it by Yoshi, it heals Yoshi. You can just jam on the tongue button to turn a once large mound of clouds into nothing within seconds. If only there were more danger and complexity to be found with this boss, which in its current state has next to zero, so Cloud N. Candy wouldn't be yet another boss to be considered by me as bad.

Side-note: Doing a no-damage run on this boss is not considered impressive!


===

Have your own disliked boss battles that you've had the misfortune of playing? Let the SuperPhillip Central community know in the comments below!