Not a good use of my time.

[prog]

OK, the endgame of Half Life 2: Episode Two is messed up. Basically it involves hitting targets with unique missiles that are only avalable at certain points on the map, and the idea is that if you miss - which is very easy to do - you need to retreat to another part of the map to pick up another missile.

But that's not fun, so instead I just save the game before pulling the trigger, and then keep reloading it until I don't miss. Not that reloading - which takes about ten seconds of staring at a blank screen - is much fun either. And according to GameFAQs (which supports the save-before-firing strategy), I get to do this thirteen times!

This is the first time I have felt the need to "save every ten steps" at any point in the Half Life 2 games - up until now I've saved only before doing something really risky, maybe a couple of times per chapter - and it seems like a design flaw that this method now feels like the correct way to solve the level.

It feels less like I'm playing an action game and more like I'm fixing a bug, changing some variables and restarting the process and seeing what happens this time. I'd happily charge the game my full consulting rate, but it's incapable of signing contracts, so to hell with it.

Comments

[radiotelescope.livejournal.com]

I noticed a couple of scenes in Lego Indiana Jones which worked this way. (There may have been the same in Lego Star Wars, but I don't remember.) E.g., if you don't get away from the rolling boulder, it just rolls over you and carries you ignominiously into the next scene. Of course you'll have to go back and try again if you're aiming at the 100% completion score, but for just getting through the plot it's fine.

I thought that was an excellent design decision.