on Oct 2, 2015
I realize it’s a running joke on this show for Josh to play unconventionally and for the rest of us to rage about it, but let me drop the shtick just long enough to point out what a mess this boss fight is.
So apparently this fight is scripted to end when Calo “dies”. But the game doesn’t tell you that, and I think it’s perfectly reasonable to want to deal with Davik first. But then Davik is almost immune to damage and your squad mates obsessively cancel orders to go back to beating on Calo. This becomes all the more befuddling later when Calo shows up for another boss fight on another planet.
As if being defeated by the player isn’t enough of a death sentence, Calo then blows himself up with a detonator. And is then hit by an orbital beam. And then some scenery falls on his head. Why inflict all this damage on him when the plot mandates he needs to show up later? And of course, once you fly away, Calo has no way to escape the planet, which is currently being bombed into gravel. Which means the encounter should kill Calo five times over: Once from the fight, once from setting off a grenade in his own face, once from the death-beam, once from the falling scenery, and finally from being left behind on a planet where everyone is doomed to die.
(It actually doesn’t show the detonator go off. I can’t tell if this means the orbits death-beam hit him before he could set it off, or if this is just a byproduct of 2003 animations and cutscenes.)
Why compel the player to attack the person that needs to survive this fight? Why subject him to so much overkill if he needs to show up later? Why portray Davik as the guy who is immune to damage, when he’s the one who dies? Why make a boss fight with two foes, only one of which you’re supposed to fight, without explaining the goal to the player? I guess the player is supposed to do this fight several times and then intuit how to beat it through heavy meta-gaming?
What a mess.