SPOILERS FOR TOMB RAIDER (2013) FOLLOW. YOU HAVE BEEN WARNED.
Wait, what do you mean it's not February anymore? It's 100% still February, I mean- *checks calendar*
Well, to be fair, there was a lot of personal stuff that came up for some time and that caused me to lose about a week's worth of potential gametime.
So, here we are, at the final writeup (but not the last article in this series, there's a post-mortem/recap/thing of my 4iF going up tomorrow-ish). What did I play this time around? Tomb Raider (2013), which I'm just going to assume that we're all okay calling it Tomb Raider, because adding that (2013) every time I write the title of the game is going to get tedious.
Raiding Dem Tombs
Surprisingly enough, this game called Tomb Raider has very little in the way of tombs to raid. There's a few optional tombs which basically boil down to "Solve this one-room puzzle", and the puzzles are kind of tricky at first. You wouldn't believe how long it took me to realize that in the first optional tomb you come across, there are cocooned bodies hanging on a thing weighing it down. The solution is to burn the bodies, then use counter-weight to raise the thing to get to the treasure. I was sitting there for a good 20 minutes before I figured this out.
I eventually attuned myself to the game's logic, and by the end of my roughly 12-hour journey, I was exploring all the things, doing all of the impossible jumps, and shooting all the bad men who just wanted to kill me. Although, despite all of my extensive searching (read: spamming the survival view button and deciding whether or not I could grab a collectible or not), I still only beat the game with 79% complete. I know that I for sure missed a tomb in the Shantytown, and a bunch of other collectibles because I deemed them too much of a hassle, or I just plain missed them.
Plotting a Course
(This is a thing that really happens in Tomb Raider. It's a little insane in some parts)
Now there's the matter of the plot. In it's simplest form, Tomb Raider is the tale of Lara Croft as she struggles (and ultimately succeeds) to overcome various adversities thrown at her on this strange island.
The much, much, much longer version is that Lara's looking for the lost kingdom of Yamatai, and then her boat suddenly blows up via a rather intense storm, stranding her and her crew on a nearby island. In the aftermath of the accident, she gets separated from the group and eventually finds her best friend Sam (who's a descendant of Himiko, the Sun Queen, and ruler of Yamatai) and this strange guy, Mathias, and Lara promptly passes out. Queue a bunch of "Where's Sam?" and about three-quarters of a game finding Sam and attempting to rescue her, followed by a brief moment in the game where the two are reunited only for Sam to be kidnapped again while Lara is fetching some stuff for the surviving crew (Spoilers: a large portion of the crew died throughout this game.) The rest of the game is Lara entering a demon/zombie-infested temple to try to stop the game's antagonist, Mathias (shocker! the strange guy in the beginning was the villain and is insane? who knew?), from sacrificing Sam's soul so that Himiko's soul can continue to live on in Sam's body. Needless to say, Lara kills Mathias in probably the most bad-ass QTE I've played all month (She finally does the dual-wield pistols thing from the early games!), and rescues Sam from a terrible fate.
All of that aside, I enjoy a bonkers-ass plot, and Tomb Raider delivered it in spades. The plot was largely by-the-books, and anyone could guess what was going to happen at any time, and I frigging loved it.
Well, I'm done my Four in February. I had a bunch of fun (for the most part), and the next thing I'm doing is going to write my epilogue for the series, which should be out tomorrow, barring any major mishaps. I'll briefly recap each game, and look at the month as a whole. No more writing about games until... well... sometime after Tuesday, because Hotline Miami 2 is a thing that's out on Tuesday.
See you next time!