1721: Run the Gauntlet

I tend to be rather wary of reboots that are simply named after the thing they're rebooting, because in my experience of them they often end up either being 1) not very good or 2) not particularly true to the original. (Or, in some cases, 3) both.)

As such, I was a bit skeptical about the prospect of a new Gauntlet game, particularly as the screenshots for it on Steam made it look like the worst kind of drab, brown, "gritty" modern-day reboot that we've seen all too frequently recently.

However, my friend Tim dropped by for a visit today, and we decided to give it a shot. £15 is a price at which I'm more than happy to take a punt on something I don't know a lot about, and so I downloaded and installed it, and we jumped into the action.

I was very pleasantly surprised to discover a very solid game indeed — and one that clearly shines the way Gauntlet was always intended to be played: in local cooperative play, with up to four players crowded around playing together.

In other words, Gauntlet, as the new game is simply called, deftly addresses my two main concerns above by being 1) good and 2) true to the original. Let's look at both elements in turn.

It's good

Gauntlet's mechanics are pretty solid. It's not trying to be Diablo or anything more complicated than the original game was: it's a straightforward hack-and-slash arcade game in which 1-4 players take on a variety of dungeons while attempting to gather as much treasure as possible.

Each of the four characters is made unique through the use of their own individual attack skills, including a super-skill that works on a cooldown. The Warrior and Valkyrie both specialise in close-combat, with their main distinction being that the Valkyrie can attack more quickly and block things with her shield, while the Warrior focuses on smashing his way through enemies. The Elf is a ranged attacker, in possession of a rapid-fire shot that works like a twin-stick shooter, a slower, more powerful sniper shot that is the only means of damaging some more powerful enemies, and a bomb, which can blow up groups of enemies. The Wizard, meanwhile, makes use of Magicka-style button combinations to cast spells — discovering which combinations do what is, seemingly, part of the fun.

These mechanics are supported by some arcade-style shenanigans where if you kill enough enemies at once (usually using a special skill) and then keep killing enemies repeatedly after that, you'll build up a chain with a score multiplier for as long as you can keep the carnage going. It's immensely satisfying to keep pressing your luck and keep the enemies coming as your score shoots through the roof — and if the Steam leaderboards are anything to go by (and if they aren't filled with cheaters, which I sadly suspect right now) it's possible to get some astronomical scores through careful combo-management. Far better than simple fire-and-forget.

When playing in co-op mode there's an element of competition, too; at the end of each level, you'll be shown how you stacked up compared to your companions in terms of points you earned by killing things and points you earned through snagging treasure. There's also a bonus for anyone who managed to keep hold of a shiny gold crown until the end of the level, making for some enjoyable scuffles as enemies knock it from your head and everyone scurries to be the first to reclaim it.

There's some interesting "progression" mechanics, too; as you play the game and achieve various milestones, you'll unlock various small bonuses to each of the four characters. None of them are game-breakingly powerful, but on occasion they can provide access to new abilities or allow you to approach things in a slightly different way. In other words, they keep things on a level playing field for those who have been playing for different amounts of time while simultaneously letting people feel like they're making "progress".

It's true to the original

While a lot is different, the core is the same: you make your way through fairly linear but maze-like levels, defeating enemies — which keep coming from enemy-spawning structures until you destroy these — and grabbing treasure. Every so often, you'll be faced with the powerful (and, in this incarnation, seemingly undefeatable) Death and have to run for your life, and, of course, there's always the risk of shooting the food, making healing somewhat more difficult. (Thankfully, the one aspect of the original which isn't maintained is the ever-ticking health bar, declining over time as a means of getting you to feed more money into the arcade machine; now, you simply have a stock of lives shared between all players which you can recharge pretty easily.)

The four-character dynamic is very true to the original, and they even keep their original colours — though they've had a bit of a makeover in some cases. The Valkyrie is no longer a sexy, skinny, bikini-clad supermodel, for example — instead she looks like a rather more formidable woman of war, as any good Valkyrie should. (Whether or not you still find that "sexy" is up to your own tastes, of course.) The characters all have voices and personalities, too, and while it's initially a little odd to hear a regional accent coming from the mouth of Questor the elf, the voices and personalities are well-chosen and give some much-needed flavour and humour to the game as a whole.

These may all sound like differences from the original rather than being true, but in reality they support the core gameplay and the core appeal element of Gauntlet, both back in the day and in this new incarnation: simple, straightforward, no-commitment dungeon-crawling with friends. It's a huge amount of fun even with just two people — I perhaps question its value as a single-player title but am willing to give it a shot — and I can imagine with four, each taking on the role of a different character, it will be an absolute blast.

And if you want even more trueness to the original? You'll be pleased to know that the sounds for picking up keys and potions are intact from the original game, the main theme plays on the title screen, and there's even a "Classic Mode" filter for the graphics, though I'm yet to try that for myself.

A pleasant surprise, then, and one I hope I'll have the opportunity to play with people again sometime soon.

1720: Jam

I've had a decent-length commute to work on several occasions throughout my life to date, and every time, I've found myself wondering how on Earth some of the road layouts I have to drive through got approved.

Take my daily journey to my current place of employment. The majority of this involves driving along a motorway that is a major route along the south coast. For starters, the road itself is in appalling condition — it's something of a bumpy ride as I leave Southampton, then smooths out a bit later, though is still a bit of a pothole-ridden mess in a few places.

It's some strange things it does with its layout that are the most baffling, though. My "favourite" — and I use this term loosely — is a short section of less than half a mile in length where the previously three-lane motorway turns into four lanes — the rightmost lane splits in two, with the new fourth lane becoming what it calls a "climbing lane". I am unsure of the exact purpose of this fourth lane, because 1) the road there isn't particularly hilly (either upwards in one direction or downwards in the other) and thus I question the need for a "climbing lane" if indeed it is for "climbing" a hill and 2) all it seems to get used for anyway is for BMW, Mercedes and Audi drivers to aggressively pull out into and then overtake the people they think are going too slowly. (Which, as I'm sure you know, can be summed up as "everyone".)

Splitting into four lanes isn't a terrible idea as it spreads the traffic out somewhat, and that particular stretch of the road tends to get very busy around rush hour. Which is why it's utterly bewildering that said four-lane stretch lasts for, as I mentioned above, less than half a mile, at which point the new fourth lane then merges back into the third, almost inevitably causing a traffic jam every single day.

Predictable traffic jams are a pain in the arse, but you can at least plan your journey around them if you know that it's 95% likely you will get stuck for at least 10 minutes in one particular spot. On my commute for another job much further back, the traffic jams around Winchester were so predictable — and so stationary — that I had the time to create a Gowalla (Foursquare precursor) check-in spot called Winchester Traffic Jam and write a description on my phone before anything moved again… then check into it every single day, because it was always in the exact same spot.

I guess the explanation for these dodgy stretches of road is simply that the amount of traffic has increased over the years, while the road capacity hasn't. But there are places where it's a clear and obvious problem; all you have to do is listen to the local radio's traffic report each day to hear exactly the same places coming up time and time again. (And the traffic report lady demonstrating her slightly annoying habit of saying "Your queue…" instead of "There is a queue…", as if queues are something desirable being handed out to everyone.)

Since you can't just shut a major road off completely — particularly while people are commuting on it — it's difficult to know how these situations could be resolved. I guess we just have to resign ourselves to the fact that yes, we are going to waste a considerable portion of our life creeping forwards at 10mph wondering if we should phone ahead to work and tell them that the traffic is, once again, quite bad.

At least it's quality time to listen to some music or podcasts — something which I missed while I was working at home.

1719: Album for the Young

I made myself a music playlist the other day. Contained therein was a selection of music from my teenage years, which is when I started actually buying CD albums and singles for myself — beginning, as I believe I've said before, with Oasis' Definitely Maybe just a day before (What's the Story) Morning Glory? came out.

Like most playlists I make, I was putting full albums rather than individual tracks in there, as I like to have a full selection of music from favourite artists available. Hitting the "Next Track" button is simple enough if you happen to be served up a stinker of an album track, so it is, for me, a case of better to have too much than too little.

Now, here's where I did things a little differently. Normally, when I put music on these days, as many people do, I believe, I choose a playlist, hit Play, then hit the Shuffle button so I get a random selection of tracks from those that I've picked. I could make the time or effort to curate playlists a little more carefully and not have to rely on Shuffle, of course, but I rarely do that these days; the only exceptions have been when I need a particular amount of music, or when I want to choose some very specific tracks to, say, take to the gym or something.

When I selected this playlist and started playing it in the car the other morning, though, I decided that I wasn't going to follow my usual pattern, and was instead going to listen to the tracks contained therein a full album at a time. If it was good enough for my fifteen year-old self, I'm sure it's still good enough for me now — and I don't like to think that the 21st century has given me such an attention span deficit that I can no longer deal with more than one track by the same artist in succession.

I used to enjoy listening to albums when I was younger. True, I rarely did it as an activity by itself — I would usually put an album on while doing homework, or reading, or something like that — but I would usually listen to a whole album once I put it on. This was at least partly due to the fact that the age of music on physical media meant that you had to get up and change a disc (or even cassette, a medium which even made it difficult to listen to a specific song) if you wanted to hear something by a different artist — but it was also due to the fact that even then, I was conscious of most albums — good albums, anyway — being designed as coherent works in and of themselves. Sure, it was the individual tracks you'd tend to hear played on the radio or the television, but a well-designed album had a beginning, middle and end: it took you on a musical journey, and sometimes even told a story.

Listening to these albums this way for the first time in a very long while has reminded me what a good experience it can be to settle down and immerse yourself in just one album; just one artist's work, the tracks presented in the order they believed that was best, rather than some arbitrary random picker thingy.

Particular highlights of drives this week have included the Manic Street Preachers' Everything Must Go, a favourite of my teenage years that I primarily picked up in the first place because a girl I fancied was totally into it; Propellerheads' decksanddrumsandrockandroll, an album I never actually owned but always enjoyed listening to; and Prodigy's The Fat of the Land, which remains, to date, a wonderfully "industrial"-sounding album filled with fire, energy and not a small degree of filth. (Not in a sexy way, either; I'm talking the kind of smoky, dusty, grimy filth that belches forth from a factory chimney.)

The latter in particular has been a pleasure to rediscover, at least in part because there's really nothing quite like it getting mainstream airplay these days; it remains a product uniquely of its time, and listening to it takes me back to the first time I heard Breathe on a school bus, courtesy of my classmate Peter Miles (a noteworthy acquaintance during my school life for being someone who challenged me to a fight that neither of us showed up for, and who was good enough to lend me a long leather coat so I could dress up as a Gestapo agent for a murder-mystery party just a couple of years ago), and discovered that an artist I'd previously written off on the grounds of the fact I didn't really like their previous single Firestarter was actually rather thrilling to listen to.

So while I'm not sure I'm going to start just sitting down and doing nothing but listening to an album — something that I've never really done, even back when iTunes was something we could only dream of — I'm certainly going to be making an effort to use the Shuffle facility a whole lot less when I'm listening to music in the future. There's an artistry in the construction of a good album, just as there is (arguably more obvious) artistry in the composition and production of an individual track; it's something that not many people take the time to appreciate these days, so it's something that I fully intend to (re-)explore a little more in the coming days.

1718: The Joyless Wankers of the Games Press

What I'm about to write would have been enormously unprofessional a few months ago, but since I'm no longer a member of the games press, nor do I have any intention of going back any time soon, I am more than happy to express myself freely.

My statement is simple: If you're that cynical about video games, find something else — anything — to write about.

I say this after a day in which not one but two utterly dreadful articles were brought to my attention — I'm not going to link to either; you can seek them out yourself if you're that interested.

First up was the review of Fairy Fencer F over on my former stomping grounds of USgamer. After witnessing… the reviewer in question's review style on a couple of other Japanese role-playing game titles — most notably the actually rather excellent Tales of Xillia 2, which he panned — and the fact that, back when I was still on the staff, he wouldn't review Atelier Rorona Plus on the grounds that a Google Image Search for the game looked "creepy", I wasn't altogether surprised to see that he tore this title to shreds, also. And he did so in such a way that told me three things: 1) he had a pre-existing dislike of the company that produced the game (Compile Heart) 2) he hadn't taken the time to engage with the game on anything more than the most superficial level and 3) he simply didn't give a shit about JRPGs as they exist in 2014.

I haven't yet played Fairy Fencer F, but given the way in which the review in question was expressed — telling people who might actually be interested in the game absolutely nothing about the game, its story or its characters and instead bashing Compile Heart and its parent company Idea Factory, bemoaning easily ignored technical issues and generally looking down its nose at people who might want to play it — I don't have much faith in it as a whole. I intend to give the game a fair shot myself once I have time to settle down with it, and when I do I intend to provide some detailed thoughts on the subject over at MoeGamer, much as I did with Tales of Xillia 2 recently.

Now, games journos will often point out how stupid it is to disagree with a review, which is, after all, a subjective opinion. And it kind of is; if you like something which someone else hates, then great; more power to you. But what we had here was more than that — it was an outright unhelpful review, instead more concerned with scrawling "I Hate Compile Heart" over everything than actually providing any sort of interesting, helpful analysis or criticism. It actually felt borderline insulting at times — though thankfully not so much as the site's notorious Hatsune Miku Project Diva F review, which was so offensive to fans of Japanese games that emphatic complaints from me and my then-colleague Cassandra led to the formation of my JPgamer column.

If this was a one-off, I wouldn't mind so much, but the reviewer in question has now done this several times — leading me to question the motivations for assigning him (or him stepping forward; I don't know which way round it was) to these titles in the first place. As the former staffer who single-handedly built up a ton of goodwill with fans of niche titles that get ignored at best, marginalised or even ridiculed at worst by other sites, I can't deny that it smarts a little to see all that goodwill getting well and truly pissed up the wall by giving the sort of games that I would have been all over — and that my fellow enthusiasts would have loved to hear more about — to someone who clearly and obviously hates them. Something that helped make USgamer unique has been lost; now it's just another site with a predictable "loljapan" attitude about it. I would rather the site simply didn't review these titles at all than let this joyless arse anywhere near one ever again, but sadly it's not up to me. How very disappointing.

But let's not get too hung up on Fairy Fencer F because this was, surprisingly, not the most stupid thing posted today. No, that honour goes to the epic-length editorial over on Polygon about finding the tutorial to the new Lord of the Rings game troubling. Why? Because at one point, you sneak up on your wife and kiss her, using the same control scheme and animations as you use later in the game to assassinate people and monsters. Somehow this bizarre objection was spun out to somewhere in the region of 1,500 words — an impressive achievement on the part of the author to take that long to say absolutely nothing, I must admit. (Although frankly, given the state of some of the entries on this blog, I'm probably not one to talk. But eh; there's a difference between a professional, commercial games site and a personal blog I use as an outlet for mental detritus.)

Polygon has been going down the toilet for a long time; I can't say I've ever been a particular fan of their uniquely pretentious brand of games journalism, nor the sanctimonious attitude of several of its staff writers, but since ditching their features staff a while back — the one part of the site that actually had anything meaningful or interesting to say — it really has been circling the drain. I wasn't surprised or angry to read this article today after someone pointed me in its direction earlier; my only real reaction was a sigh and a shake of the head. Games journalism in 2014, ladies and gentlemen; better to say 1,500 words of nothing at all about the week's big release than, you know, say nothing at all. Because if you make people angry you'll at least get some page hits as people share it indignantly.

Today has been one of numerous days that I've looked back on my time with the games press and thought "That was fun while it lasted, but I don't want to go anywhere near that ever again." If a prerequisite for being a member of the games press of 2014 is being a joyless wanker who can't find the fun in anything, then count me out. Give me a call when you ditch the clickbait business model, fire all these miserable tossers and start bringing on board people who are actually enthusiastic — even passionate — about this exciting medium. I won't be sitting by the phone waiting for your call, however; I've got better things to do.

You know, like playing games… and actually enjoying them.

1717: The Story of Your Mail Archive

During a quiet — and, I won't lie, somewhat bored — moment today, I decided to take a look back in my GMail archive and see exactly when I started using that account. I've had a number of different email accounts over the years, some of which have lasted longer than others, but I had a feeling that GMail had stuck with me longer than anything else. (Except perhaps for Hotmail, which I keep around to sign up for things I don't want to sign up my "real" email address for. And for my Xbox Live account, because in Microsoft's wisdom, they don't allow you to change the email address associated with your account, meaning I was forever stuck with it, not that email really matters to Xbox Live anyway.)

Sure enough, my GMail account has been with me for somewhere in the region of four or five years or so. Prior to that, I made use of a .mac/MobileMe/iCloud account (the name has changed several times since I opened the account in 2007 as part of my employment at the Apple Store), and before that, I was using Yahoo. Prior to that, I was using various different proprietary addresses that I got with Internet service providers, and since I moved every year while I was at university — and quite frequently thereafter, too — I changed email address a lot, much to, as I recall, the annoyance of my brother, who never knew which address to contact me on.

Anyway, I digress; my GMail account hails from 2009, and it was interesting to take a look back to what was going on in my life around then. I can use this blog for that too, of course — and often do, as narcissistic as that might sound — but looking back at past emails is a little different because it's not just a record of my thoughts spilling out on the page as I saw fit to express them; it's my thoughts spilling out on the page as I saw fit to express them to another specific person.

As those of you who have been reading this blog for a few years will recall, 2010 was Not A Good Year for Pete, and indeed the early pages of my email history reflect that to a certain degree.

Before that, however, was an email from a former colleague containing nothing but this image:

photoIt still makes me giggle.

Anyway, the first few pages of my GMail are actually made up of messages imported from my .mac/MobileMe account, which I was running in parallel with GMail for some time (and indeed still am, though I don't really use it any more). In those early messages, I can see the first time I was hired as a professional games journalist — Joey Davidson and Brad Hilderbrand were good enough to take a chance on me and hire me for the now sadly defunct Kombo.com. The pay was crap, but it was something at a time when I had nothing else, and I got something far more valuable out of that experience: friends. People I still speak to today — indeed, just today I had a quick chat with Joey via instant message, which was nice.

Around that time, I was preparing for a trip to PAX East in Boston, at which I'd have the opportunity to meet a number of members of the Squadron of Shame for the first time — and to catch up with some I'd had the pleasure of meeting once or twice before. I was also looking forward to the opportunity to cover a big event as a journalist, though sadly I wasn't enough of a bigshot at this time to be able to score a proper press badge, and as such had to write about things at the show largely from a consumer perspective.

Shortly after my return from PAX East, you may recall that my life fell to pieces, and you can see almost the exact moment this happens, since there's a sudden flurry of sympathetic messages from friends and family alike. Thus began a very dark period in my life, and one that still, I must admit, brings tears to my eyes to relive, even when looking at it through the cold, clinical view of plain text.

So let's not do that.

Instead, fast forward a bunch of pages and I was very surprised to spot an email from a familiar name: Shahid Ahmad, who is now best known as Sony's most enthusiastic employee, and champion of the Vita. Shahid apparently commented on one of my posts somewhere — I can't quite tell where from the email exchange, but it was a post about the game Mr. Robot, which I recall enjoying a great deal — and we'd evidently had a discussion about Chimera, a game which he made back in the days of the Atari 8-bit and Commodore 64 home computers, and which he has trying to remake ever since. (He was talking about a remake a while back on Twitter; apparently, he's been trying to make this happen since at least 2010.)

Somewhere around the 37,000 email mark (still in 2010), I seemingly start using GMail a bit more for communicating with people and signing up for things. There's still a bunch of stuff coming in via MobileMe, but messages without that tag are starting to appear more and more.

Around the 35,000 email mark, I start working for GamePro. Of all the sites I've worked on over the years, I think GamePro is the one that I think of most fondly and am most proud of. I feel I struck a good balance with my news coverage, and there was tangible proof that I — specifically me — was responsible for bringing in a significant amount of new traffic with the work I was doing. Unfortunately, this seemingly wasn't enough to prevent the site from being unceremoniously wiped off the face of the planet some time later, but it was nice to know at least.

Aside from my own developments, it's also interesting to see what names I still know today have been up to over the years. It's nice to see Tom Ohle of Evolve PR's name crop up a bunch of times, for example — that man's one of the hardest-working PR folks in the business, and also someone who always put across the impression of genuinely believing in the games he was representing — as well as folks I've worked alongside moving from outlet to outlet.

And then, of course, there's the first appearance of Andie in my Twitter direct messages (Twitter's email notifications used to look a whole lot different!) and… well, we all know what happened there. (She's sleeping upstairs in the house we own together right now as I write this.)

So anyway. Having rambled on for over a thousand words about nothing more than my email archives, I think I'm ready to call that a night. It's been an interesting trip back along memory lane — not always pleasant or comfortable, but certainly interesting — but I think I've sated my curiosity for now, at least.

So what's the earliest email you still have, dear reader?

 

1716: Desperately Seeking Information

Something a friend of mine said in an online chat earlier made me think about the way we, humanity, use the Internet on a daily basis — and particularly the role that social media plays in many of our lives.

He said that as human beings, we crave information. It doesn't matter what that information is, we're just hungry for it; forever consuming, devouring any input we can get our brains wrapped around, however mundane, stupid or fury-inducing.

After he said this, I took stock of my online existence since leaving Facebook and Twitter behind. I still haven't looked at the former at all; I've peeped at the latter once or twice to see if I had any mentions or direct messages — I didn't (apart from a share of this post by a dentist who clearly hadn't read it at all), which, I won't lie, smarted a bit, but I'll live.

What I have done, however, is almost immediately replace them with other things. I was always intending to make more active use of the Squadron of Shame forums, for example, but they have become my primary go-to hangout online — which makes their occasional lack of activity a little frustrating. (Come join up and talk in a chin-strokey fashion about games!) But that's not all I'm doing: instead of relying on what Twitter is talking about for a picture of the day's news — a practice which tends to give you an inherently biased picture of what is going on, due to the political tendencies of some of Twitter's most vocal users — I'm specifically seeking out sites like the BBC and the Guardian to read about stories at my own pace. (I still skip over anything that just offers me a video and no text, though; fuck video.)

I am not, however, reading a great deal about video games. This is less about losing interest in them — which my marathon Xillia 2 session this evening will emphatically attest that I am not — and more about feeling there aren't really any sites out there that speak to (or for) me. I've discussed this with a number of people with whom I share similar proclivities, and many of us tend to feel the same way: while the ad-based revenue model for these sites continues to be in place, we're never going to see the sort of coverage that we're interested in seeing. Those sites that do try different things — like Polygon with its now-defunct features section, or 1up with its community-driven nature — end up either closing down altogether, or at the very least shedding the things that made them unique and becoming yet another identikit site of daily triple-A and indie darling news churn.

But I digress. The point is, the information void I left when I cut social media out of my life was immediately filled by something else. It's a compulsion; an uncontrollable urge. As a human being, my brain demands information; it needs input. More input.

I'm not entirely sure if that's a healthy compulsion, since as I noted above, the 21st-century brain doesn't appear to be all that selective about what it wants to absorb into itself. Perhaps if the brain craved nothing but new knowledge — information that would allow it to let its host function as a better human being — that might be absolutely fine.

But no. The 21st century brain is interested in menstrual menaces and megachile perihirta (commonly known as the Western leafcutting bee); in cats drinking from squirt bottles and… oh, you get the idea.

The human brain is a mysterious thing. Whatever you may feel about the information you stuff into it on a daily basis, though, I think we can probably all agree that the Internet has had a profound impact on how we perceive, seek out and consume information these days, hmm?

1715: Twintania Downed, Again (and Again)

This evening it was my great pleasure to be a part of the inaugural Giant Bomb/Loose Cannons (aka GBomb/LoCo) raid party in Final Fantasy XIV — what I hope will be the first of many joint adventures that take place on a UK timezone-friendly schedule.

Since a couple of members of LoCo hadn't yet cleared The Binding Coil of Bahamut, Turn 5 — something of a "benchmark" for how well groups work together — we had decided that, come hell or high water, we were going to get a group of some description together and attempt it.

We'd tried this once before, filling out the extra spots in the party using Final Fantasy XIV's matchmaking Duty Finder system, but the downside of this is that you never know who you're going to get — even in challenging content like Turn 5, there's always a possibility you'll get someone who is just looking for a quick and easy clear with no fuss, and who might not have patience to deal with people who are hoping to learn the fight and practice it. Indeed, this happened to us; the first time we got to

[Editor's note: At this point, Pete was called away for another hasty attempt at Turn 5, this time with Andie in tow. It was a successful attempt, as was, I'm sure you've already guessed, the one about to be discussed.]

Ahem. Sorry. Anyway. As I was saying, the first time we got to try it together, we were lumbered with one of these people, who got all huffy when someone got hit by Twintania's notorious "divebomb" mechanic — one of the more difficult attacks in the game to dodge and otherwise deal with. Eventually, when Huffy McHuffypants left in a huff, we had to abandon our attempt as, since Turn 5 is fairly old content now, it can sometimes be difficult to get people in there unless you pre-form a group before you start.

But anyway. Tonight we assembled a crack team of GBomb and LoCo types, including a couple who had never cleared it before and a few — including me — who had. Then we jumped in.

Our first attempt went reasonably well. Twintania's companions, the three Scourges of Meracydia, all fell to our onslaught pretty quickly, and we handled Twintania's barrage of fireballs and conflagrations without breaking a sweat, since we were all, by now, pretty familiar with how this part of the fight worked. When Twintania swept off into the inky blackness high above the right hand of Bahamut, we dove into the nearby ditch between the fallen god's fingertips and waited for the angry dragon to show her face again.

Dive, and dodge; dive, and dodge; dive, and dodge; the first set of Divebombs passed without incident, and Twintania's snake-like guardians Hygieia and Asclepius showed up. We dealt some damage to the two Hygieia and then focused our attention on Asclepius again; then it was time for another set of Divebombs.

Dive, and dodge; dive, and dodge; dive, and dodge; the second set passed without worry, and one of our two paladins dragged the annoyed Asclepius and Hygieia across the right hand of Bahamut to join their two companions that had just showed up.

I used the party's collected energy to unleash my Limit Break, calling down a shower of meteors onto the heads of the snakes, killing two of them outright and seriously wounding the rest of them. As the Hygieia died, they increased Asclepius' vulnerability bit by bit, until we were all eventually dealing about twice the normal damage we usually did. It wasn't long before Asclepius fell to that onslaught, at which point we dove into one of Twintania's dropped Neurolinks, the collars that the ancient Allagans had used to control her, and which had gradually been falling from her neck one by one as the fight progressed.

At this point, things fell apart somewhat. Twintania summoned her deadly Dreadknights, and it wasn't long before they ripped through several of our number; the rest fell to her powerful Twisters attack. But not to be deterred, we picked ourselves up and tried again.

Once again, the Scourges fell, and we set to work on Twintania. The fireballs and conflagrations proved little challenge for us, and we deftly avoided the first set of Divebombs. We got a little too enthusiastic on the Hygieia this time around, however; one died before we got out of the ditch and the other was nearly shuffling off the mortal coil as we pulled them together for another Starstorm summoned by my command over black magic.

This time, the furious Twintania didn't faze us. While our lead paladin kept the attention of the giant dragon, the other made sure the Dreadknights didn't reach their destination, battering them repeatedly with their shield while I pelted them with freezing ice, which slowed their movements when they weren't stunned. A Dreadknight would fall, then we would move as one to sidestep Twintania's next Twisters; then another Dreadknight would fall, and we'd once again hop neatly out of the way of Twisters.

Finally, the weakening Twintania resorted to the same attacks her Scourges had used on us at the start of the fight; spitting huge gobs of flaming matter all over the battlefield, creating a Liquid Hell. We'd run to avoid these, but by this point our victory was all but assured; sure enough, not long after that, the beast fell to our relentless assault, and we were triumphant.

I love this fight. It's no longer the most difficult thing in the game, but it's a demanding battle that ensures everyone involved is on their toes and sets expectations appropriately high for the Second Coil of Bahamut (and the Third Coil of Bahamut, which is coming soon). It also bodes well for the group of us who are planning to tackle some of this content on a regular basis; clearing Turn 5 on a second attempt is good going by anyone's standards, and we repeated the situation almost exactly when a few hours later Andie wanted to give it a go with us, too. We seemingly work well as a team — even without using voice chat to coordinate what we were doing — and our own individual skill levels were apparently well up to the challenge Twintania offered.

So what's next? That remains to be seen; all being well, we'll be giving the first Turn of Second Coil a go this week. I've tried this battle once before and it appears to be somewhat demanding in the same way as Turn 5 is; you need to pay close attention to what is going on, and react quickly and calmly to the things that are happening around you. One mistake can leave you lying dead on the floor at a moment's notice — and potentially kill off the entire party. I have faith that we can rise to this challenge, though, and I'm looking forward to giving it a shot.

1714: Arachnid Dentistry

I had an enjoyably bizarre dream last night, or possibly early this morning — I'm not quite sure. It doesn't really matter when it occurred; what does matter, however, is that it was most peculiar, and has somehow stayed in my memory for most of the day rather than, as dreams are often wont to do, dissipating in a puff of imagination shortly after getting up.

I will preface this by saying there was no poo involved in this dream. I'm sure you're devastated.

Anyway. The main premise of the dream was that Andie and I were living somewhere that was not the house we now own between us. Instead, we were the proud owners of what appeared to be a rather house-like flat that was actually inside another building. In other words, the flat itself was multi-level, like a house, but its "front door" actually opened into a corridor of the building which contained it rather than onto the street. I recall commenting on this to dream-Andie, noting that she had been adamant about getting a house rather than a flat (she had; it was one of our few "musts" when looking for a new place) and that we'd somehow ended up with a flat instead.

For whatever reason, I elected to step outside what was seemingly our newly acquired flat to go and explore the rest of the building. I followed the corridor from our front door through another set of doors, and discovered that just a little way down from where we now lived was a dental surgery. This struck me as a little odd at the time, but I just shrugged it off. We lived next door to a dentist, and that was just how it was.

I'm not sure how long I walked for, but the building itself appeared to be rather large, with different areas fitted out in noticeably different manners. Lower down — apparently our flat was quite high up in it — the building appeared like a classy hotel, with ostentatious decor and lush carpets; higher up, meanwhile, the drab walls, endless fire doors and strangely arranged staircases called to mind some form of student accommodation I'd spent time in in the past. It wasn't the halls of residence I lived in; I have a feeling it was either some friends' halls, or possibly a sixth form college where I stayed for a residential music course while I was a teen. Either way, it was somewhat out of place when compared to the richly decorated lower levels.

At some point, I got lost. I found myself somewhere on the lower floors in what appeared to be the headquarters of an affluent, successful company — all leather sofas, marble-effect (or possibly just marble) tabletops and shiny floors. Whichever way I turned, I couldn't seem to find the way back where I came from, and eventually ended up on the street. Apparently this building was in Toronto, somewhere near where my friends Mark and Lynette used to live, as I recognised the street corner on which I found myself.

I went back into the building and found that this time I was able to successfully navigate my way back into the hotel lobby-like area, up the stairs into the dorm-like area, and eventually past the dentist back to our flat.

When I came back in, I'm not sure if the arrangement was different or if I just hadn't noticed it before, but bizarrely, there was a shower room right by the living room. Even more strangely, there was a hole in its wall where bricks had seemingly just been removed, leaving an open "window" between the shower and the living room.

For some reason, I opened the door of the shower room and lay down on the floor. There was a computer keyboard in front of me. I started typing, and as I did so, hundreds of small spiders started emerging from the shower's plughole, then crawling into the corner of the room and disappearing. As I continued to type, the spiders kept coming, but they always seemed to be going the same way. I wasn't sure what I was doing, and I didn't really want to know. All I knew was that I needed to keep typing and typing and typing and typing… you know, much like I'm doing right now.

Then I woke up in a state of some confusion that was swiftly followed by disappointment that I was probably too late to go out and get a McDonald's breakfast.

Explain that one, then.

1713: Yep, You Should Play Ethan Carter

I must confess I hadn't been paying all that much attention to The Vanishing of Ethan Carter. I knew several people whose opinions I trusted were excited about it, however, so I was always intending to give it a try. And with it releasing this week and Andie out of town for the weekend, I figured tonight would be the perfect opportunity to give it a try.

I completed it, as it happens — it's not a terribly long game, but it is a very worthwhile experience that I recommend you indulge in, preferably in a single sitting if you have three or four hours to spare.

But what is it? I hear you ask. Well, it's… Hmm. Sort of hard to describe, in one sense, but pretty simple in another.

Its developers describe it as a non-violent investigation game in which you attempt to track down clues as to the whereabouts of the titular character, a young boy who wrote a letter to the protagonist — the rather wonderfully named Paul Prospero — prior to the eventd of the game beginning.

Now, the description of "non-violent" usually points to an example of those games that are often derided (or sometimes celebrated) as "walking simulators" — games that are, in effect, little more than theme park attractions in which you wander around and have a story delivered to you through various means. Notable recent examples include Dear Esther — which kind of invented the "genre", if you can call it that; Gone Home, which famously got branded "Not a Game" upon the introduction of Steam's tagging system; and The Stanley Parable, which no-one seemed to mind too much because it was amusing.

The Vanishing of Ethan Carter is not quite in the same wheelhouse as these games. Rather than funnelling you down a specific path, Ethan Carter offers a certain degree of freedom — though there's still a natural order you'll come across the game's main… bits.

It's these "bits" that distinguish Ethan Carter from your common-or-garden walking simulator, however, because each involves a degree of puzzle-solving, deduction and thorough investigation of the environment to succeed. And in order to see the game's story through to its conclusion, you'll need to succeed in all of these little mini-adventures scattered across the map.

The exact form of these mini-episodes varies with each one: some require you to simply find a bunch of objects in the nearby vicinity; some require you to figure out what happened where in a particular situation, and then correctly identify the order the events you uncovered occurred in; some are more traditional "puzzles" requiring a bit of lateral thinking and investigation to beat. The nice thing about the game's relatively brief length is that it never feels like it's repeating itself too much: the most-repeated game mechanic is the chronology-identifying system, and that usually comes at the conclusion of some other investigative work.

The most pleasing thing about Ethan Carter, though, is that it warns you when you start that it's not going to hold your hand at all, and then it's true to its word. No navigation arrows. No journal. No flashing objectives. Just you and your brain looking out onto the lovingly detailed (albeit fairly small) open world that forms the setting for Prospero's investigations.

And what a world. It may be small, but it's beautifully crafted; this is by far one of the best-looking games I've seen for a long time. Outdoors, grass, bushes and trees blow in the wind as the sunlight streaks down through gaps in the leaves. Indoors, light streaming in through windows shows dust floating in the breeze. Textures are beautifully detailed, meaning you can easily read things like book titles and small incidental signs without having to get right up close to them, and the overall atmospheric effects are marvellously convincing: there's a lovely gentle haze in the background, and although the explorable area of the map is fairly small, the background is rendered in a convincing enough manner to suggest that the area you're tooling around in is very much part of a much larger world. It's gorgeous — and it provided the workout I've been craving for my brand new nVidia GTX 970 graphics card, which handled it perfectly on max settings without breaking a sweat. Lovely.

I shan't get into the story of Ethan Carter now, since with it being so short, it's something you really should experience yourself. I will say, however, that I enjoyed it a great deal, and can recommend it highly — even if you're not normally a fan of non-violent "walking simulators". The puzzle-solving and investigative elements elevate this far above titles like Dear Esther and Gone Home in gameplay terms, and, although short, it's a satisfying game to work through and complete.

So go on. Set aside a few hours this weekend and go find out just where Ethan Carter has got to. You won't regret it.

1712: Les Oignons

There are, as you'll know if you've been reading this blog a while now, many things that I do not like and wish to change about myself. Some of these are things I probably could change if I tried hard enough. Others are things that appear to be hard-wired into me, and I couldn't change them now even if I tried.

One of the most frustrating things in this latter category is my dislike of onions.

I have hated onions for as long as I can remember. Initially dismissed by my parents as me just being a fussy eater — like most children, I was fairly fussy about a lot of unfamiliar foods when I was young — I continued to insist that not only did I simply not like onions, but they actually made me want to be sick.

That's not an exaggeration, either; even today, if I can so much as taste a bit of raw onion, it makes me retch and completely puts me off whatever it is I am eating that has turned out to be stuffed full of onion. I won't even eat something that has had raw onion on it, because I remain convinced that raw onion infects the flavours of everything around it, making everything else taste of onion even when the offending slices themselves have long been removed.

The strange thing about my violent dislike of onion is the fact that, in many cases, I'm absolutely fine with it if it's been cooked into something. I don't mind a pasta sauce that incorporates a bit of onion, for example — so long as it's not too much — and I don't mind a curry or Chinese dish that has a bit of onion in it — though again, not too much. Basically if I can taste it, it's out; I cannot think of a single dish that is improved by the presence of onion, but handled correctly I can at least tolerate it.

What's even stranger is that over the last couple of years or so, I've started to find even specifically onion-based things more palatable than I have done in the past. I can eat and even quite enjoy an onion bhaji, for example — though in most cases these have been deep-fried to such a degree that any resemblance to actual onions is by that point purely coincidental — and I have been known to have battered onion rings with steak and the like, too — though I will add to that that I usually smother them in so much sauce that it becomes impossible to discern their oniony origins.

Despite these changes in the last few years, though, I'm doubtful I'll ever be able to eat onion in the same way as a lot of other people I know — and I certainly doubt I will ever get to a stage where I like it enough to specifically want to add it to things. This is frustrating, because it's surprising quite how much food out there — particularly stuff designed for lunchtime consumption like sandwiches, wraps and the like — is absolutely rammed full of onion, in many cases ruining what sounds like an otherwise delicious item of food for me and, more often than not, making it completely unpalatable.

Oh well. I've survived 33 years without onions; I'm pretty sure I can probably go the rest of my life without them, too.