Sunday 15 January 2012

That bit where... Call of Duty 4: Modern Warfare

Back in 2007, we were bored of first person shooters. It seemed like every month, a new game came out that was set in bloody World War II. By that time it had been done to death, we all knew the scenarios, the weapons and the outcome of every battle (the Nazis lose, spoilers).

But then, rising out of the swamp of FPS mediocrity came Call of Duty 4: Modern Warfare. Wait a second, this is set, like, today? That's so real! It gave us a new enemy, instead of fighting Nazis, we were now fighting anyone who wasn't American or British, and in doing so the developers were staying as close to current affairs as possible...

Along with that, there were new weapons to enjoy, the guns that every nine year old can talk about at length today were largely unknown before this game came out. They also highlighted how much guns from the 40s sucked...you mean I don't have to load a new bullet into the chamber after firing every shot? War is awesome!

Five years later, we're praying for something different from FPS developers, but oh well, it was good for a while.



Anyway, there were two highlights of the game for me, one of them being the Ghillie mission, simply because it was something different. Instead of shooting everything that moved, you had to stealth your way through, picking your shots and trying not to get detected. Then there was that bit after you assassinated the guy with the helicopter which oh so nearly crashes into you! But then it stops, phew! My favourite part of the game though, was a moment of extreme poignancy that seemed so out of place and yet fitted in so perfectly.

Call of Duty 4: Modern Warfare - Shock and Awe


"All U.S. forces, be advised, we have a confirmed nuclear threat in the city. NEST teams are on site and attempting to disarm. I repeat we're..."

In the mission entitled 'Shock and Awe', you are tasked with attacking Al-Asad's (the villain of the piece) rumoured position in his capital city. However, half way through the mission a retreat is called after a nuclear threat in the city is detected. During the retreat, you stop off to rescue a downed helicopter pilot who is under fire.



Everyone bundles into an evac helicopter and as you take off you see several other helicopters making their escape from the city, phew, everyone's going to make it.

And then the nuclear device detonates.

You watch as the mushroom cloud billows skywards and the shockwave makes it way towards you, destroying everything in it's path. We're far enough away, right? We're still going to make it. But the shockwave keeps coming, enveloping the other helicopters in a cloud of dust and rubble, and then it hits you. Your helicopter spirals out of control, crashes into the ground and then everything fades to black.



Did I fail the mission? That's not supposed to happen is it?

You wake up, manage to crawl your way out of the wreckage and drag yourself onto your feet. The sun has disappeared behind the smoke, and everything around you is just a shell of what it once was. At least you're alive though, someone will come soon to save you. You fall back to the ground and close your eyes.

Someone will be there soon.



It is later revealed that 30,000 people died in the blast, Marines, OpFor and civilians all wiped out. I had never played a game where such a catastrophic event occurred right before my eyes. Nor can I remember playing a game in which I had completed a mission, and several of the game's main characters died, all in one moment.

I congratulate you, CoD4:MW, not only for having an acronym longer than most game titles, but for putting this incredible sequence into a game, allowing a slight insight, just for a moment, into what it would actually be like to be in that situation. Maybe war isn't so awesome after all.

Thanks for reading.

No comments:

Post a Comment