Halo 3

Published on

Halo 3

I went on a bit of a Halo binge a couple weeks ago. I played through Halo: Combat Evolved Anniversary and Halo 2 maybe 18 months ago and I started Halo 3 right after finishing Halo 2. I actually got 80% of the way through the game but at a certain point I stopped. I don’t recall why however. I might have got caught up in a different game or just got frustrated with a difficult part of the game, but I stopped. I didn’t picked the game back up for close to a year later. When I did start it back up recently, I found that I was just two levels from the end.

After quickly finishing up the generic room that I found myself in, I met up with some other UNSC soldiers and we came across two Scarabs. This part of Halo 3 is right up there with Gears of War 2’s insanely hard courtyard (which one? who knows?) towards the end of the game. I must’ve restarted 30 times because I didn’t realize you could take the Scarabs out by shooting them in the ass with the Falcons. If you think that was dumb for me not to know, please remember that I hadn’t touched a Halo game in over a year. After making it through that part, the rest of the game was fairly easy.

The last part of the game where you’re working your way through the hordes of the Flood, I was reminded of Halo’s biggest problem: it’s usually easier to just run past enemies than it is to fight them. Halo is usually just about getting from point A to point B. If you can get to point B without firing a shot, that’s a viable option 90% of the time. That’s how I wound up playing Halo 2 and 3 for the majority of the time. I found that just avoiding enemies and getting to the next door was sufficient.

So, in the end, Halo 3 was okay. Overall, it was an enjoyable experience, but the moment to moment gameplay didn’t really grab me. Surprisingly, the next three Halo games I played, two of which don’t even star Master Chief, were far more entertaining.