Halo 3 Review
Halo 3 is probably the most popular game in the long running Halo Franchise. It was a system seller for the Xbox 360 and for many people, it was their gateway into the series. So while Halo 3 has managed to craft this legendary status around itself. Does it live up to it? And, looking back over 10 years since its launch, has it held up compared to modern games. These are the questions I intend to answer as I take a look back at the heavy hitting title of 2007 and give my honest opinions of it.
Starting with the story, we have to talk about the fact that Halo 2 was originally going to be the end of the franchise, and that Halo 3 only came about because Bungie set their sights too high and had to end Halo 2 on a cliffhanger. Because of this, Halo 3 has to both tell its own story, as well as finishing off Halo 2's. Halo 3 is comprised of 10 missions, though one is just a cutscene and doesn't really count. So all in all there are 9 missions in the game, making it somewhat shorter than Halo 2. The big issue for me when it comes to Halo 3's campaign is the pacing, or lack of it. The story goes nowhere for 6 out of the 9 missions, preferring to faff about on Earth. These 6 missions are what I believe to be the way Bungie were going to finish Halo 2, or how they were retro-actively ending Halo 2 at least. Specifically Mission 5 is where I believe the ending for Halo 2 would have been. Mission 6 has lots of problems of its own that need to be brought up. To sum it up, in Mission 6, the Flood arrives at Earth on an infected Covenant Battle-cruiser. Long time fans of the Halo series will know the Flood as the all consuming parasite responsible for wiping out the Forerunners, and who took over High Charity (The Covenants Holy City) at the end of Halo 2. So this is a pretty big deal. On board the Flood infested ship, Master Chief finds a message from Cortana talking about the Ark, this is the beginning of the issues. Cortana didn't know about the Ark, she wasn't with Johnson and Miranda when 343 Guilty Spark revealed its existence to them, so how could she have found out about it? One option could be that she took it from the database of Installation 04, but if so why didn't she tell anyone about it? It would seem like a pretty big deal to me, especially when there's a portal to it on Earth that she seems to know about as well. Secondly, how did she even get the message on the ship in the first place? She was on High Charity, the message is on a physical storage device. Did she create it and put it on the back of a Flood to carry into the vessel? And when & how did she record it without the Gravemind knowing? She was being interrogated by him after all and we know how it can corrupt AIs. The threat at the start of the mission, the Flood is also dispatched by the Covenant at the end, meaning the stakes for Earth are pretty much over. The Covenant have left and the Flood on the planet are dead. This mission also introduces us to a new plot point. According to Cortana, there's a way to stop the Flood for good at the Ark, without having to fire the remaining Halo rings, a Forerunner weapon that perhaps, wasn't finished in time to save them, but could save us. Unfortunatly, Halo 3 immediatley drops this plot point, making the entirety of mission 6, pointless. The plot point leads no-where and the threat introduced at the start of the level, is gone by the end of it. It feels like the remainder of some earlier draft of the story, one that I would have liked to see for sure.
As so much time is spent at Earth, it means by the time the game actually gets to the Ark, there's only 4 missions left in the campaign. This doesn't give you a lot of time to really explore the ark, like you could explore the ring in Halo CE. 2 missions in on the Ark and the Prophet of Truth is dead, killed in a cutscene like the Prophet of Mercy before him. This is so that the game can say 'Aha! The Gravemind is actually the true villain!' as he betrays you just after helping you reach Truth. The trouble is the game only has 2 missions left at this point, and in only one of them do you actually interact with the Gravemind to any large degree. His betrayal is also somewhat odd, his tentacles raise up above Master Chief and the Arbiter as he talks about how he's going to kill everything, then fails to grab a slow moving Pelican Dropship as it escapes, only succeding at knocking Arby and Chief off of it before having his tentacles retreat and sending waves of combat forms to attack you, basically it builds up a boss fight and then nothing happens, you just trudge back through the same hallway you fought through not 5 minutes earlier, only now you're fighting the Flood. The mission after that has you delve into the Flood nest in order to retrieve Cortana. The mission itself looks great, the flood biomass over the walls really gives you an idea of what could happen if the flood gets loose. The level layout is extremely confusing and you may find yourself dying a lot as there are constantly spawning enemies including many Flood Pureforms, alongside the confusing layout, you may find it to be an exercise in frustration. This level also serves to rob the Flood of some of their menace. Looking at it lore wise, Master Chief just walked into the belly of the beast, grabbed his holographic friend had a quick chat with her and then strolled back out again. The Flood don't even seem to do anything to stop the damaged pelican he escapes on from leaving. It makes them seem incompetant. The final mission of the game has you heading to a Halo Ring, the intent being to fire it to kill the Flood infestation. This actually conflicts with what we were told in Halo CE, that the Halos don't kill the Flood, they kill its food and let it starve to death. You fight through more Combat Forms and the gravemind taunts you a little, then you get to the final chamber. Guilty Spark informs us that the ring isn't ready to fire, and that it'll take a few more days before it's ready. When Johnson informs him that they don't have that much time, Spark goes rampant and kills him, this had been foreshadowed earlier when Spark zapped a marine who wanted to check out his internals, to make sure he was functioning right, but anyone who had played from Halo CE could probably see this betrayal coming a mile off. You then have to go through an easy and boring boss fight against Guilty Spark before you can finally activate the Halo ring, as the ring is unfinished it starts falling apart, destroying itself and dealing massive damage to the Ark. Which conveniantly solves that plot hole of the Rings only killing the Floods food. This leads to the final section of the game, a Warthog run similar to the one from Combat Evolved, though not as fun. And then the campaign ends. It's a bit sudden, and they of course tease that the franchise will be continued in the future (Which it was, with Halo 4)
Now that I've finished talking about the single player, I can move onto the multiplayer. This is what most people will remember when it comes to Halo 3, as it had a massive online community back when it was released. Halo 3 offered a good range of game-modes for the player to enjoy and a wide range of maps to play on, though you may find people vetoing maps until they get the ones they want, which means you'll find yourself playing on Valhalla or Guardian a lot for instance. The weapon sandbox has been expanded from Halo 2, now new Brute weapons are in the mix as well. Unfortunatly, there's not much reason to use them. There's not a lot that sets the Spiker apart from the SMG for instance, or the Mauler from the Shotgun. The Gravity Hammer is a fun new power weapon that rivals the Energy Sword and I think it's an excellent addition to the game. Two new grenade types have been added as well, the Fire-bomb grenade and the Spike Grenade. The Fire-bomb is what it says on the tin, an incendiary grenade that burns the person it hits to death. The Spike Grenade is similar in some ways to the Plasma Grenade, it sticks onto a vehicles or surface and explodes, the difference being that the Spike Grenade is somewhat directional. Like the Fire-bomb, it's a one hit kill. Some new vehicles have also been added to the mix. The UNSC gets the Hornet VTOL and the Mongoose ATV. The Covenant lose the Spectre from Halo 2, but gain the Brute Chopper and Prowler. The Chopper is the Brute equivelant to the Ghost, only has the special ability of being able to destroy light vehicles by ramming into them whilst boosting, which is usefel in game-modes like Capture the Flag, if the enemy team is escaping with the flag in a Warthog. The Prowler on the other hand is pretty much just the Spectre, but with a Brute theme. It has a single turret on the front, rather than the rear and two side skirts for passengers to hold on. Aside from that, there's nothing else unique about it, as I said; it's a Spectre with a Brute skin. Halo 3 was also popular for Major League Gaming at first. Though there were some noticable problems for those ultra competitve players. Halo 3's netcode was a little poor, this made blood-shots (Shots that hit the enemy from your perspective, but don't register in the game, and so do no damage) rather common, which annoyed a lot of competitive players. Halo 3 also did not utilize hitscan like the previous games in the series had, rather players had to lead shots if they wanted them to land. This took a bit of getting used to for a lot of veteren players. The Battle Rifle also had some poor weapon spread as it would seem as though one shot was always going to miss, unless you were right in your enemies face. The Assault Rifle also felt a little weak as well. This may in part be due to the sound design used on the weapons, which I felt was a little sub-par in a lot of ways. Another new feature that was added in Halo 3 was Forge mode, that let people edit maps by adding in new weapons of vehicles or items and the like wherever they wanted. The mode was a bit simplistic but I won't count that against the game here as it was the first instance of the feature and what players did with it far exceeded their expectations.
Overall I'd say Halo 3 is a pretty solid game, despite what may appear as my hatred for it, I do actually like the game. But its multiplayer far outdoes its campaign. Halo 3 is an old game now, going on 11 years old. You'll find the population for online is rather low, struggling to get above 2000 people at the best of times. This is compounded by the fact the player base is split across the Master Chief collection, Halo 3 on Xbox One backwards compatibility and those still playing the game on the Xbox 360. There are some issues with the multiplayer netcode, but if you're just playing casually, then you probably won't notice too many issues. While the weapon sandbox is a little dull, it's not too bad and there's a nice variety between the weapons. The campaigns story is quite bad but you'll probably have a lot of fun with the missions themselves, the scarab fights are quite fun (even if they make the scarab feel like a bit of a pathetic miniboss) and the settings are somewhat diverse. Halo 3 is available on the Xbox 360, as a backwards compatible title on the Xbox One and is also in the Masterchief Collection. If you would like to purchase a copy, then follow the link below:
Halo 3 - Xbox 360
Starting with the story, we have to talk about the fact that Halo 2 was originally going to be the end of the franchise, and that Halo 3 only came about because Bungie set their sights too high and had to end Halo 2 on a cliffhanger. Because of this, Halo 3 has to both tell its own story, as well as finishing off Halo 2's. Halo 3 is comprised of 10 missions, though one is just a cutscene and doesn't really count. So all in all there are 9 missions in the game, making it somewhat shorter than Halo 2. The big issue for me when it comes to Halo 3's campaign is the pacing, or lack of it. The story goes nowhere for 6 out of the 9 missions, preferring to faff about on Earth. These 6 missions are what I believe to be the way Bungie were going to finish Halo 2, or how they were retro-actively ending Halo 2 at least. Specifically Mission 5 is where I believe the ending for Halo 2 would have been. Mission 6 has lots of problems of its own that need to be brought up. To sum it up, in Mission 6, the Flood arrives at Earth on an infected Covenant Battle-cruiser. Long time fans of the Halo series will know the Flood as the all consuming parasite responsible for wiping out the Forerunners, and who took over High Charity (The Covenants Holy City) at the end of Halo 2. So this is a pretty big deal. On board the Flood infested ship, Master Chief finds a message from Cortana talking about the Ark, this is the beginning of the issues. Cortana didn't know about the Ark, she wasn't with Johnson and Miranda when 343 Guilty Spark revealed its existence to them, so how could she have found out about it? One option could be that she took it from the database of Installation 04, but if so why didn't she tell anyone about it? It would seem like a pretty big deal to me, especially when there's a portal to it on Earth that she seems to know about as well. Secondly, how did she even get the message on the ship in the first place? She was on High Charity, the message is on a physical storage device. Did she create it and put it on the back of a Flood to carry into the vessel? And when & how did she record it without the Gravemind knowing? She was being interrogated by him after all and we know how it can corrupt AIs. The threat at the start of the mission, the Flood is also dispatched by the Covenant at the end, meaning the stakes for Earth are pretty much over. The Covenant have left and the Flood on the planet are dead. This mission also introduces us to a new plot point. According to Cortana, there's a way to stop the Flood for good at the Ark, without having to fire the remaining Halo rings, a Forerunner weapon that perhaps, wasn't finished in time to save them, but could save us. Unfortunatly, Halo 3 immediatley drops this plot point, making the entirety of mission 6, pointless. The plot point leads no-where and the threat introduced at the start of the level, is gone by the end of it. It feels like the remainder of some earlier draft of the story, one that I would have liked to see for sure.
As so much time is spent at Earth, it means by the time the game actually gets to the Ark, there's only 4 missions left in the campaign. This doesn't give you a lot of time to really explore the ark, like you could explore the ring in Halo CE. 2 missions in on the Ark and the Prophet of Truth is dead, killed in a cutscene like the Prophet of Mercy before him. This is so that the game can say 'Aha! The Gravemind is actually the true villain!' as he betrays you just after helping you reach Truth. The trouble is the game only has 2 missions left at this point, and in only one of them do you actually interact with the Gravemind to any large degree. His betrayal is also somewhat odd, his tentacles raise up above Master Chief and the Arbiter as he talks about how he's going to kill everything, then fails to grab a slow moving Pelican Dropship as it escapes, only succeding at knocking Arby and Chief off of it before having his tentacles retreat and sending waves of combat forms to attack you, basically it builds up a boss fight and then nothing happens, you just trudge back through the same hallway you fought through not 5 minutes earlier, only now you're fighting the Flood. The mission after that has you delve into the Flood nest in order to retrieve Cortana. The mission itself looks great, the flood biomass over the walls really gives you an idea of what could happen if the flood gets loose. The level layout is extremely confusing and you may find yourself dying a lot as there are constantly spawning enemies including many Flood Pureforms, alongside the confusing layout, you may find it to be an exercise in frustration. This level also serves to rob the Flood of some of their menace. Looking at it lore wise, Master Chief just walked into the belly of the beast, grabbed his holographic friend had a quick chat with her and then strolled back out again. The Flood don't even seem to do anything to stop the damaged pelican he escapes on from leaving. It makes them seem incompetant. The final mission of the game has you heading to a Halo Ring, the intent being to fire it to kill the Flood infestation. This actually conflicts with what we were told in Halo CE, that the Halos don't kill the Flood, they kill its food and let it starve to death. You fight through more Combat Forms and the gravemind taunts you a little, then you get to the final chamber. Guilty Spark informs us that the ring isn't ready to fire, and that it'll take a few more days before it's ready. When Johnson informs him that they don't have that much time, Spark goes rampant and kills him, this had been foreshadowed earlier when Spark zapped a marine who wanted to check out his internals, to make sure he was functioning right, but anyone who had played from Halo CE could probably see this betrayal coming a mile off. You then have to go through an easy and boring boss fight against Guilty Spark before you can finally activate the Halo ring, as the ring is unfinished it starts falling apart, destroying itself and dealing massive damage to the Ark. Which conveniantly solves that plot hole of the Rings only killing the Floods food. This leads to the final section of the game, a Warthog run similar to the one from Combat Evolved, though not as fun. And then the campaign ends. It's a bit sudden, and they of course tease that the franchise will be continued in the future (Which it was, with Halo 4)
Now that I've finished talking about the single player, I can move onto the multiplayer. This is what most people will remember when it comes to Halo 3, as it had a massive online community back when it was released. Halo 3 offered a good range of game-modes for the player to enjoy and a wide range of maps to play on, though you may find people vetoing maps until they get the ones they want, which means you'll find yourself playing on Valhalla or Guardian a lot for instance. The weapon sandbox has been expanded from Halo 2, now new Brute weapons are in the mix as well. Unfortunatly, there's not much reason to use them. There's not a lot that sets the Spiker apart from the SMG for instance, or the Mauler from the Shotgun. The Gravity Hammer is a fun new power weapon that rivals the Energy Sword and I think it's an excellent addition to the game. Two new grenade types have been added as well, the Fire-bomb grenade and the Spike Grenade. The Fire-bomb is what it says on the tin, an incendiary grenade that burns the person it hits to death. The Spike Grenade is similar in some ways to the Plasma Grenade, it sticks onto a vehicles or surface and explodes, the difference being that the Spike Grenade is somewhat directional. Like the Fire-bomb, it's a one hit kill. Some new vehicles have also been added to the mix. The UNSC gets the Hornet VTOL and the Mongoose ATV. The Covenant lose the Spectre from Halo 2, but gain the Brute Chopper and Prowler. The Chopper is the Brute equivelant to the Ghost, only has the special ability of being able to destroy light vehicles by ramming into them whilst boosting, which is usefel in game-modes like Capture the Flag, if the enemy team is escaping with the flag in a Warthog. The Prowler on the other hand is pretty much just the Spectre, but with a Brute theme. It has a single turret on the front, rather than the rear and two side skirts for passengers to hold on. Aside from that, there's nothing else unique about it, as I said; it's a Spectre with a Brute skin. Halo 3 was also popular for Major League Gaming at first. Though there were some noticable problems for those ultra competitve players. Halo 3's netcode was a little poor, this made blood-shots (Shots that hit the enemy from your perspective, but don't register in the game, and so do no damage) rather common, which annoyed a lot of competitive players. Halo 3 also did not utilize hitscan like the previous games in the series had, rather players had to lead shots if they wanted them to land. This took a bit of getting used to for a lot of veteren players. The Battle Rifle also had some poor weapon spread as it would seem as though one shot was always going to miss, unless you were right in your enemies face. The Assault Rifle also felt a little weak as well. This may in part be due to the sound design used on the weapons, which I felt was a little sub-par in a lot of ways. Another new feature that was added in Halo 3 was Forge mode, that let people edit maps by adding in new weapons of vehicles or items and the like wherever they wanted. The mode was a bit simplistic but I won't count that against the game here as it was the first instance of the feature and what players did with it far exceeded their expectations.
Overall I'd say Halo 3 is a pretty solid game, despite what may appear as my hatred for it, I do actually like the game. But its multiplayer far outdoes its campaign. Halo 3 is an old game now, going on 11 years old. You'll find the population for online is rather low, struggling to get above 2000 people at the best of times. This is compounded by the fact the player base is split across the Master Chief collection, Halo 3 on Xbox One backwards compatibility and those still playing the game on the Xbox 360. There are some issues with the multiplayer netcode, but if you're just playing casually, then you probably won't notice too many issues. While the weapon sandbox is a little dull, it's not too bad and there's a nice variety between the weapons. The campaigns story is quite bad but you'll probably have a lot of fun with the missions themselves, the scarab fights are quite fun (even if they make the scarab feel like a bit of a pathetic miniboss) and the settings are somewhat diverse. Halo 3 is available on the Xbox 360, as a backwards compatible title on the Xbox One and is also in the Masterchief Collection. If you would like to purchase a copy, then follow the link below:
Halo 3 - Xbox 360
Comments
Post a Comment