Reviews by Wade Clarke
horror
View this member's profilePrevious | 31-40 of 48 | Next | Show All
If you think being alive is tough, try being undead., November 7, 2012(I originally published this review on 15 October 2012 as part of my blog of IFComp 2012. This was the 19th of 26 games I reviewed. The game had been updated once during the competition before I played it.)
A Killer Headache casts the player as a zombie in a posthuman world with the immediate goal of ridding oneself of one's blinding headache by finding and eating more brains. It's truly a sad time to be a zombie when you have to live off the grey matter of animals and other zombies, but what saddened and maddened me was how excruciatingly difficult I found this game to be. In common with Changes, also from the 2012 IFComp, A Killer Headache has a world model of great sophistication, but it's even harder than Changes, and its nested hint menus almost induced apoplexy in me.
A Killer Headache was apparently inspired by a long and existentially discussion about zombies on the intfiction.org forums. I sped read the discussion after playing the game and can say that cumulatively, the participants knew their zombie stuff, as I claim to myself. Author Mike Ciul has considered the gamut of post Night of the Living Dead ideas and come up with his own version of the zombie mythology. The zombies range in sentience from below average to above, but they are all still possessed by their hunger, which can blind them to almost everything else. They specifically want brains, a schtick begun by the film Return of the Living Dead in 1985, and some of the humour of this game is also in keeping with that film's supposedly funnier aesthetic. (That's to say that RoTLD marked the arrival of "funny" zombies in zombie movies, but that I didn't find that film very funny myself; no slur on this game's humour intended.) An example would be the pathetic, moaning conversation you can have with the severed head of your friend Jim in the game's first location, your trailer.
The practicalities of being undead are foremost amongst this game's interests. The first puzzle is just getting out of your trailer. Your lack of coordination makes fiddling with the doorknob annoying and your lack of strength means that using brute force tends to destroy parts of your own body. Various enemies can tear your hands and feet off, hampering your future hazard-negotiating abilities. Falling down a ravine on your stupid zombie legs could result in an eternity of being pecked at by vultures. The game's commitment to the hopeless grisliness of zombie existence assuming zombies have feelings of a kind, which is this game's atypical premise is unwavering.
The difficulty which ensues is also unwavering. You're constantly being interrupted or killed by enemies while in the process of trying to solve difficult and fiddly puzzles, often under time pressure or with the added complication of your concentration being dragged away into pre-zombiedom flashbacks. This is clearly a point of the game, to convey that zombie "life" is indeed arduous. The point is effectively made and felt, but I don't think the experience should be quite so impractical to move through as a game. When you die, it tends to be several moves deep into a losing streak of actions, and to verify your suspicions about your situation often requires exploring several branches of the nested hint menus, paging in and out, going deeper and shallower and reading the lists of topics which are so convoluted that they cross reference each other.
A lot of the difficulties of play are also a consequence of what is exceptional about this game: its highly involved world model. The different groups of enemies interact with each other in complex ways, roving the desert, staking out objects and locations, fighting each other and fighting over you. The behaviour of the hated mob of zombie children is especially impressive. However, the author has not missed an opportunity to turn any particular permutation of circumstances into another hazard for the player, and the hint topics reflect this, reading like a troubleshooting manual for a day in hell. Did the dogs tear your hand off? Did they tear your foot off? Have they trapped you in the diner? Have the children trapped you in the diner?
My player wherewithal was gradually eroded over time as I kept trying and failing to solve my zombie problems. Some solutions were quite abstract ((Spoiler - click to show)put the other head on your shoulder), some relied on the kind of small-scale fiddling that has proved eternally difficult to implement to everyone's satisfaction ((Spoiler - click to show)I had terrible problems trying to find the commands to express what I wanted to do with the pump and gas tank), some were solutions I was too late to try ((Spoiler - click to show)try to keep your limbs in this game; it's better that way) and some were just very demanding. Dealing with the (Spoiler - click to show)mob of zombie kids occupying the diner near the end saw me dying on almost every move. I was spending about four times as much time moving in and out of the hint menus as I was playing. I had also been trying to play using speech-to-text, and being constantly driven back to the keyboard to fiddle with the menus was intolerable in my trammeled state, so this was where I gave up, unfortunately missing out on some existential ending, according to other reviews of this game.
A Killer Headache is dense, cleverly constructed and well written, and its savage entitites show a wide range of behaviours. The whole thing is harrowing. I just wish I hadn't found it so agonising to play. Perhaps the context that IFComp creates wasn't right for this game. Without the desire to try to finish this in two hours and the knowledge I still had a pile of other games to get through, I expect I would have been more receptive to the challenges it posed. What I don't have any kind words for are its nested hint menus. Nested hint menus drive me nuts in any game it's about the only extreme prejudice I have in text adventuring and the complex nature of A Killer Headache managed to show this particular method of dispensing information in its worst light.
The child told not to go into the cellar is unlikely to not go into the cellar., July 19, 2012David Whyld's The Cellar was part of the H.P. Lovecraft-themed Commonplace Book Project of 2007 organised by Peter Nepstad. This was a remarkable project whose IF angle I knew nothing about prior to researching it in relation to The Cellar. I had known what Lovecraft's Commonplace Book was: the place where the author used to jot down unused story ideas. While the Book's contents have been used as a launching point for IF games or IF competitions on more than one occasion, what was neat about the 2007 project was that the six games which participated were set up for play as part of an exhibition in Switzerland's Maison d'Ailleurs, aka The Museum of Science Fiction and Utopias. Further details are available in Peter Nepstad's article about the project in SPAG#50.
Concerning The Cellar, it is no spoiler to reveal which idea from the Commonplace Book the game is based on, as it is displayed on startup:
Mans body dies - but corpse retains life. Stalks about - tries to conceal odour of decay - detained somewhere - hideous climax.
The game is written from the point of view of a character initially standing outside of its unsettling events: the boy Nevare, whose father made him promise not to go into the cellar after returning from a trip to Africa. When the game begins, you (Nevare) find yourself alone in the house one day, consumed by curiosity and with an opportunity to at last search for the key to the forbidden room.
The prose of The Cellar is quite good, and the game's revelations fall comfortably (or should that be uncomfortably?) into the Lovecraft mould, as do its methods of writing, perhaps. One character emerges to tell the game's backstory at great expositional length. It is the quality of this story that is the soul and effect of this game, but the linearity of the whole piece and its broad sidelining of interactivity are very apparent. The choice moment of being a child in a room and having to look around for an object from the world of adults is repeated a few times, and it's well done, but these are the only moments in which you get to really do something other than listen to another's story. Of course, it isn't literally "another's"; being a tale of family, this story involves Nevare indirectly, which turns out to be a salient point for the denouement of The Cellar. However, I imagine many regular IF players would simply wish they could do more in this game. I wished that, but I still enjoyed the story. I can also imagine a game depicting some of the told material in interactive fashion, though this isn't a case where speculating on a significantly different game that isn't will pay dividends. The Cellar's linearity might also have made it more accessible to random passers by in an exhibition. Either way, its story is a good realisation of Lovecraft's jotted idea.
Books, glorious books!, July 17, 2012Dead Cities hails from the Lovecraft-themed Commonplace Book Project of 2007 and uses the following jotting of Lovecraft's as its inspiration:
"An impression - city in peril - dead city - equestrian statue - men in closed room - clattering of hooves heard from outside - marvel disclosed on looking out - doubtful ending."
While I've yet to play through all of the project games as I write this, I'm guessing that this one is the most technically ambitious of the bunch. It presents attractively in a multi-pane window which divides up the main text, an inventory list, a hint panel and black-and-white pencil sketches of many of its situations and objects. Suggested commands from the hint panel can also be clicked to enter them into the main window. Unfortunately, these flourishes are not trouble-free. I ran into a fair few bugs while playing, several of them related to the display, some of them serious (no save possible because it was not possible to restore) and was rarely able to determine exactly where the fault lay. I will discuss these issues at the end of the review.
Dead Cities is a Lovecraft pastiche long on conversation, domesticity and quality prose. Lovecraft was good at fetisihising all kinds of things by dwelling upon them at what I like to think he would describe as preternatural length, and Jon Ingold achieves something similar here with the rare books which appear in this game. The player is a solicitor charged by Carter Arkwright with obtaining the signature of Carter's dying uncle. Carter seeks to avoid inheritance tax bankruptcy by acquiring his uncle's valuable books before his death, books which range from rare Isaac Newtons to Necronomicon-like volumes.
It is necessary in the first place to attend to social niceties in this game. You'll tie up your horse, make small talk with the maid and humour an old man. I would say that these things seem to flow easily here, when they often don't in IF, except that with my general dislike of the tell/ask system of IF conversation which Dead Cities uses, the truth is that I was unable to cleave myself away from the hint panel, which perfectly yes'd and no'd and asked and told my way all through the introductory section of the game and then quite far into the game's core conversation with old man Arkwright. The hint panel feature strikes me as an excellent way to show people how to play IF, and would probably have worked very well for random folks looking at this game in the context of an exhibition. For regular IFfers, it may be a bit too much of an easy temptation, but personally I never say no to an opportunity to skip asking and telling.
The conversation scene with Arkwright has that black humour about it of someone trying to extricate valuable information (or just valuables) from an old person who is dying and knows it. Of course in this game you can say that it was all just business because you're playing a hired solicitor, but there is some scope in your yes-ing and no-ing to treat the old man well or poorly, or somewhere inbetween, which is interesting.
To speak of later more hair-raising shenanigans would be to spoil this not particularly long game. There is a lot of room in it to try little variations in your interactions with the game's few NPCs, but there are perhaps only a handful of opportunities to change a bigger picture. I found a couple of endings hard to read in that they made me wonder if I'd missed chunks of the game, as if I could have achieved something more drastic. But there's no walkthrough and no hints for the later part of Dead Cities, so I decided to be content with what I'd done. The general high quality of the prose and overall flow of events were the real attractions for me.
Concerning technical troubles, I can say that I was unable to successfully restore a saved game of Dead Cities in the current versions of Mac interpreters Gargoyle and Zoom doing so produced a Glulx error. The game's hint panel spiralled out of control on me more than once, cycling madly through the hints, and in Zoom I found it was sometimes necessary to resize the game window mid-session to prevent the interpreter from pausing after every line of text. Dialogue and hints snuck into the inventory window occasionally, too. I believe this game was put together in two months for the Commonplace project, so it's already punching above its time-weight in overall quality, but it looks like it could have benefited from more testing, and it's probably become a victim of some degree of inconsistency in delivery of the relatively nascent Glulx format, or tweaks to that format over time.
It's significantly more exciting than 'Moderately Impactful Breach'., July 16, 2012Critical Breach puts you in the role of something like one of the low ranking scientists working for the bad guys in the Resident Evil games. The kind of white-coated underlings who do the dangerous lab work on the zombie DNA and are first to be torn apart when some giant mutant springs out of a petri dish.
The game has a core of two busy lab rooms sporting computers, scanners, medical miscellany and one specimen cage containing your charge, the horrible Scorpig. Your goal is to implant a chip in that little bastard, a procedure which does not go routinely. This main part of the game is very satisfying, coming on like a significant but not overly tough set piece from a larger adventure. There's good interactivity amongst the many props at your disposal, a fair bit to do and a fair bit to work out. The game successfully conveys a feeling of the dangerousness of the PC's situation without ever killing the player. I did get stuck once, at which point I consulted the walk-through and discovered that (Spoiler - click to show)a particular object which common sense had told me would never fit inside another particular object actually did so I blame the game's failure to make clear the size of this object.
Unfortunately, the post-Scorpig section of the game is poor. It may also be short, but it dragged down my experience with its relatively lame implementation (EG a vital noun makes no appearance in the prose at any point), vagueness of purpose and possible bugginess. I was stuck in one room for ages, and when I turned to the walk-through, it didn't work (Spoiler - click to show)nor did its instructions on getting either of the game's endings.
I was tempted to lop a star off my score for the messy endgame, but I felt that would fail to accurately reflect the fun I had in the laboratory section, which comprises the bulk of Critical Breach. I had also been expecting a small game from the outset, and wouldn't have minded if it hadn't continued beyond the lab anyway. It's a good and basically satisfying dose of puzzle in a sci-fi setting. An update to the endgame would be great, though.
But I am in my grave, and, oh, The difference to me!, July 14, 2012I was going to begin this review by saying: 'Not to be confused with the 2009 game of the same title, genre, initial situation and initial geography,' and then I realised how dumb that sounded. If ever a human being should be allowed to accidentally confuse a pair of games with each other from a position of ignorance, it should be in the case of these two Awakenings, though admittedly this one has a 'The' in front of it.
Now that I have kindly allowed for human fallibility, I can say that Dennis Matheson's lone IF game, 1998's The Awakening, is a well written piece of goth horror in which you wake up in a grave in the pouring rain and must seek to solve the mystery of your predicament. The prose is steeped in Lovecraftian dread and 'unnameable'-ness, and the development of the plot moves strongly in the direction of one of Lovecraft's short tales.
At the time of writing this review, I was mostly in the habit of playing more recent IF games IE from the mid 2000s and on and as I played The Awakening, I discovered that I needed to shift my playing style and mindset a bit to accommodate what feels like a game from a different time. The differences were subtle, but they spoke to me about the adventure games I am used to playing, which could be generalised as coming from both the old school and the new school. The 90s games are in a middle period for me. I had no awareness of them at the time, and this one certainly feels more like a small Infocom title than something newer.
The puzzles, though not numerous, are quite finicky and also subtle. Important props are sometimes buried with equal subtley in the room descriptions. It is possible to make your game unwinnable or to miss out on points, and there's also the technical limitation of only one UNDO being allowed. I don't think anyone would say this is a really difficult adventure, and there are in-game hints you can call upon, but it asks a little more of the player puzzle-wise than more modern games.
Atmosphere is king in The Awakening, what with its shuddery graveyard and dilapidated church settings. Some of the gettable objects about the place are just there to enhance the story and the reality of the situation, and there are a couple of nasty NPCs. (Spoiler - click to show)I have to confess that in the case of the guard dog, I only got stuck because I found the description of its chain inadequate. Folks who like non-explicit Lovecraft spinoffs, graveyard spookiness or a bit of rigour in their adventuring should enjoy this middle sized mystery.
Rain rain go away, why me sleeping in a grave?, July 13, 2012Awakening is a short to moderate length horror adventure of likeable clarity. To solve the existential mystery of your identity there are two main things you need to do in this game: Pay attention to the descriptions of the rain-drenched church grounds you'll find yourself wandering and pay attention to the automatic feedback you'll receive from your character's senses. Nor should you forget that you woke up by an open grave when the game began. Like I said, three things.
Awakening won the Saugus.net Halloween Contest of 2009 and delivers a Halloweenish variation on the IF amnesia theme. Though a little overladen with adjectives, it has a strong mood of ceaseless rain and mud and a good way with the burden of the numerous physical sensations experienced by your character. Your bedraggled state gives you strong motivation to try to improve your lot by exploring, or at least to try to do something loftier than mope about by a grave.
The implementation is rusty in some places but then surprisingly detailed in others. While there are a handful of inflexible moments, the game as a whole isn't complex enough to be undone by them. Awakening's mood is sustained by good location writing and its world is small enough that you don't have to retrace too much ground if you get stuck. Some mystery, some mostly staple puzzling and a moody locale of small inventory make for a satisfying goth horror outing.
The For3st House gets simultaneously better and worse., February 16, 2012Keen followers of The Forest House saga would have been pretty happy with the ending of part two, and probably at least mildly curious to see what would happen in part three. The answer is: you get half a game which is potentially the best in the series, followed by half a game which is easily the worst.
Basically the third episode seems too ambitious for anyone to be able to bring off properly in just three hours of programming, the competition limitation which defines all three games. So the further you play, the worse the programming gets, until the building is practically falling down around you.
The kid from episode one is now grown and married, "With a gorgeous wife to your left and beautiful son to your right" as the game says. But this is a Forest House game, so it's not long before people need to start getting on down to The Forest House to progress the plot.
This game features an animated NPC, a first for the series. It's your wife, and she dutifully follows you around, guides you in the right direction and offers some advice. This is a very cool start to the game, and the conversations actually clear up some of the family relations that have popped up in the earlier games.
Unfortunately things go downhill once you get into the supernatural half of the adventure. First, a bunch of room descriptions vanish. This is clearly a bug, even though there are other weird room shenanigans going on, including is a semi-endless stairway, again inspired by Silent Hill. Second: (Spoiler - click to show)The fight with The Beast demonstrates more new programming, but feels silly. And finally the game just crumbles into programming hell. Its responses become erratic and inconsistent, things disappear or don't disappear which shouldn't or should respectively. (Spoiler - click to show)The end is supposed to present a few choices but I could only interact with one of them; the others seemed broken or bizarre. If you can make it to the finale, it offers a bunch of fairly crazy exposition.
Over the course of three Forest House games, the author demonstrated a growing range of abilities. It's probably time for him to string them all together in a game not ensmallened or bugged-up by a three-hour programming time limit. That limit hurt this third game in the series the most.
Small scale grand guignol fun, February 16, 2012This comic horror mini-adventure was written in three hours for Ectocomp 2010, and fits a clever central conceit and a great 'Aha!' moment into a handful of locations.
The game begins with your head being sawed off by an evil bad guy and placed on a table. To speak more explicitly on the content in this review would, unfortunately, amount to game-wrecking, given the petite size of Headless, but what I do particularly like about this game is that it doesn't fall down that speed IF hole of being overreaching and underimplemented. Headless's design is totally amenable to the format's logistical restrictions, and the game has a good trick that's fun to work out. This is one "they done sawed my head off" game I am not shy about recommending to the non-squeamish and sundry.
Effective in its aim but low on interactivity., December 5, 2011All Alone is a very short horror game riffing on those urban myths about what can happen to women who are unfortunate enough to receive a creepy phone call late at night. You play one such woman fielding one such phone call; you're alone in your apartment when the call arrives, a storm's moving in and the TV news is yelling at you about the local serial killer.
The game is effective in evoking the fear people can experience and generate in their own homes at night, and eliciting that fear from a handful of rooms and domestic props. It also uses a couple of sound effects at choice moments. Unfortunately, it's also tremendously short and not really very interactive. Suspense is built up from a sequence of timed steps which mostly proceed no matter what you're doing. Admittedly this is a rather dull and mechanical perspective on how the game works, but if that suspense is the game's sum effect (Spoiler - click to show)(though the final twist is pretty good, too) it's too little for me in an interactive medium.
One more note: Reviews contemporary to All Alone's release (11 years ago at this time of writing) often quote the author's advice on how to play it that is, with lights out, alone, at night. This advice wasn't anywhere in the game that I could find, so I assume it was on a promotional website which no longer exists or in a readme file which is no longer attached to the game.
Well-designed creepiness., November 18, 2011When I came to play this game, I thought, "I see political trouble ahead for Blind from reviewers, based on the title and tagline
" that tagline being: "Who says blindness is a handicap?" As it turns out, Blind isn't about overcoming blindness through medical advancement or political agitation. It is about overcoming blindness by having you play a young blind woman who must escape from the house of a cannibalistic serial killer.
Blind women in peril (or women whose eyeballs are demonically possessed - that one doesn't apply to this game) have a rich history in thriller and horror films. Audrey Hepburn played one in Wait Until Dark (1967), foiling a drug-dealing criminal in her own unlit apartment. In that film it was all about the drugs. In many later blind-woman-in-peril films, and in Blind, the criminal's goal is the blind woman herself, his motives sexual and sadistic. This takes the game into creepy and harrowing terrain, and puts the player in a desperate survival situation.
In technical terms, Blind's sensory schtick is less than perfect. As you cannot see, you are given other verbs to discover information about your environment, such as 'feel' and 'smell'. 'Look' remains implemented, giving general feedback from your other senses on your present location. Being able to use several senses multiplies the amount of feedback you can get from each object in the game, but sometimes it can feel like a simple obligation to have to 'examine' each item in three or more different ways, and more objects could use more describing. Nevertheless, the overall effect works in that you do progress through the game by applying sometimes unexpected senses to the obstacles you encounter in a way that a sighted person wouldn't.
I was surprised to learn that the author is not particularly a fan of the horror genre, as he demonstrates a pretty good understanding of it in Blind. Some of the heroine's realisations about her plight (and the plight of those who went before her) as she stumbles about the killer's house are written with great psychological and physiological realism. Unfortunately, the game is also capable of undercutting such moments with the odd joke at the expense of the fourth wall, or occasionally managing to frame the heroine in a pervy way, even though it's her POV. These weak spots do not detract from the game's overall sincerity of effect, nor from what turns out to be a very elegant and detailed game design.
While Blind's early scenes distressed the adventure gamer in me by presenting me with a huge number of implemented household items which I could pick up (I was having visions of having to construct some incredible escape device from my packrattings, and I feel I am only being kind to future players in saying -- that is not what you have to do
(Spoiler - click to show)At least upstairs. When you get downstairs, some assembly may be required.) Blind demonstrates a lot of interactive possibilities and outcomes in its second act down in the basement. Violence has been used against you; how much and what kind of violence are you prepared to resort to in order to escape? Some possibilities seem to be a stretch when derived from the context sensitive hint system, but other clever and resourceful actions for the heroine to take are well implemented. You might have to face your captor more than once, and the game becomes particularly dangerous and exciting as it approaches its climax.
I also like that when you first complete Blind it presents you with a list of achievement-like extras you might want to try to avail yourself of in a subsequent game. Some of the proffered feats are easy to pull off, others quite difficult. In any case, I found this to be a more strongly motivational approach to inviting replays than those typical 'amusing' lists, which I've never really liked. And the second act gamespace is both small and detailed enough that I think most players who enjoyed the game are likely to be interested in going for the extras.
Version 1.6 of Blind (the final IFComp 2011 version) could use more polish in proofreading and implementation, but its core design is good enough that some roughness is unlikely to be bothersome for any player who is interested in its subject matter. It certainly doesn't betray any sign of its having had no testers beyond the author; I find it to be as least as well implemented as many games which placed above it. Blind is an imperfect but strong horror-thriller puzzle game, with moments of authentic creepiness and gruesomeness.
Previous | 31-40 of 48 | Next | Show All