Reviews by Wade Clarke

(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.

(I originally published this review on 11 October 2012 as part of my blog of IFComp 2012. This was the 15th of 26 games I reviewed.)

Based on its opening scene, I thought The Test is Now READY was going to be a zombie game, but this scene turned out to be on its own. Test drops you into a series of unconnected but difficult situations. Your choice of action in each scenario will inevitably have extreme (usually fatal) consequences for one or more of the parties involved, including yourself. Quick to play and undeniably galvanising, this game is well suited to the context of this competition, but not all of its scenarios are equally strong, varying in logical sturdiness, plausibility and implementation. They are all equally easy to spoil, however, and player freshness is important for the premise, hence the remainder of my review is solid spoiler:

(Spoiler - click to show)The torture-a-suspect-to-save-millions scenario is very discomfort-making, and probably the strongest in terms of goading agonised thinking. The grisly prose in this section is vivid, the important actions all implemented. When I compare the quality of this scenario to the one in which your son's foot is trapped in the train tracks as a train approaches, the latter's problem is that it is not vividly portrayed, nor are the responses to obvious actions convincing. I didn't have a sense of how far away the train really was at different times, or of the physical arrangement of the space or of the positions of the important players in relation to each other. This probably compounded my annoyance at too basic responses like, "You can't help your son," when I tried to free him. But what I did particularly like about this scenario were its epilogues, which quickly summarise how the mother's life goes as a consequence of the actions she takes by the train tracks. They demonstrate that some situations really are impossible to negotiate successfully.

The hysterical quality of some of the scenarios is justified in retrospect by the fact that they have been designed to deliberately test the ability of an artificial intelligence (which is us) to make difficult decisions. I still didn't feel this made the blood donor scenario more credible, though. There's something about waking in hospital and being told in one fell swoop that you have the only blood in the world that can save this woman, and that that's why there's a tube coming out of you and going into her. That's why this was the easiest scenario for me. I ripped the tube out of my arm immediately and walked out.

The trouble with the you-can-choose-to-be-high-forever scenario is that unlike with the others, I did not find the nature of the choice to be clear. I didn't press the drug-releasing button once and think, "Oh okay, my choice is between getting high or being responsible." I was just trying to understand what kind of situation I was even in. Once I knew that the button delivered drugs, I walked out of the room.

The assessment of player personality and disposition at the end of the game is kind of fun, even if I suspect there will be a camp of players who won't like the AI revelation. Not all of the scenarios needed to be as painful as the torture one, obviously, but more of them could have benefited from a greater sense of immediate urgency of situation, achieved through more focused writing and implementation.

(I originally published this review on 22 October 2012 as part of my blog of IFComp 2012. This was the last of the 26 games I reviewed.)

I would have preferred the last competition game I play to not be about sport, let alone Gridiron. But now that I have played – nay, won! – Kicker, I'm glad it was my last game because it managed to surprise me. This is a game in which you play the placekicker on a Gridiron team, but it's an easy game to play for the sporty and the unsporty alike. It is also, after a fashion, not what either camp would expect from the premise. Or perhaps exactly what they'd expect.

The game's thorough message is that the role of placekicker is tedious and thankless, and close to being a joke in the eyes of one's teammates. You RUN ONTO THE FIELD, GIVE THE SIGNAL, KICK THE BALL and then RUN OFF THE FIELD. Then you mill about on the sidelines for twenty turns or so before the coach urges you to repeat the kicking process. In the style of a conceptual art piece, the player has to ride out an entire interminable game of football in this manner, boringly entering the same commands again and again to reinforce the idea as lived practice, with the extra joke that any and all attempts to find stimulation on the sidelines, whether through conversation or action, are doomed to failure. Other players shun you, a film crew ignores you, cheerleaders ignore you and there's basically nothing else to do.

Driven to the boredom the game seeks to muster, I tried to bring down my team by disobeying the coach in various situations. For instance, by not running onto the field when he asked me to run onto the field, or by not running off the field when he asked me to run off the field. My stratagems didn't ruin my team's prospects but I was fired twice. Happy to find that the game was not completely unyielding, I undid my tomfoolery and pressed on with entering "Z" or "WATCH THE GAME" a zillion times to see if anything wacky would eventually happen. I had grown quite weary by the time my team won, and our winning was the thing that happened.

The programming of the football game's progress is good and the prose is clean. A few commands I tried weren't recognised, but otherwise this is technically a solid game which is explicit about the commands you need to type if you want the match to keep going, but also relaxed enough to assure you, with good cause, that "You'll figure it out."

I've always thought of Gridiron as that ridiculous game where the players' physical attributes and skills are completely ghettoised. The kind of sport where one guy might have a massive right arm that he spends all his life pumping, except when he's on the field doing nothing but standing on a prearranged spot and waiting for a chance to clothesline some passer-by with that arm. Playing Kicker certainly did nothing to change my prejudices, but what it did do was let me win a sports IF game without understanding or caring about the featured sport at all, and it took a swing at at least one element of that sport while it was at it. For these things I am grateful, even if the game worked its magic by daring me to give up in the face of intense boredom.

(I originally published this review on 8 October 2012 as part of my blog of IFComp 2012. This was the 11th of 26 games I reviewed.)

Thou shouldst save and save often in Castle Adventure! for thou art without UNDO capability and opportunities for thine stuckening abound. This is a solidly executed rescue-the-princess toughy delivered in a simple 1980s style. None of Castle's puzzles are too tricky individually, but the overall difficulty is multiplied by the combination of the game's large map (I would estimate 100 rooms) and the fact that you can wreck your game in various ways. If Castle Adventure hadn't shipped with its Invisiclue hints, I imagine I would have been in danger of giving up on several occasions, and to make use of the clues still requires a good familiarity with the gameworld. However, I think anyone who gets into this game will enjoy acquiring that familiarity, as the map design is really excellent. Even with so many rooms, and so many of them being empty, they have a distinct style of logical arrangement and clear description that makes them easy to navigate. The empty rooms also add a sense of scale which helps give the game its atmosphere. By the time I completed Castle Adventure, I had its whole world in my head.

This is a game about the good old joys of unfettered fantasy adventuring. Forests, castles, secret passages, creatures to help and hinder, bare bones descriptions and anachronistic jokes when you look at things. Your goal of rescuing the princess isn't accompanied by a bunch of mythology, it's just self-evidently what the hero does in a world like this. And Castle Adventure is very polished. I don't recall seeing any typos or encountering any bugs I could guarantee were bugs. That is to say that there were some slightly cumbersome command moments, but the game has the spirit of a two word parser game, even if it isn't one literally, and it's possible that moments of inflexibility are just a part of the style.

A handful of puzzles seem to slyly comment on the great anti-intuitive difficulty which sometimes accompanies old school games. (Spoiler - click to show)I especially liked the part where I had to keep typing GET TORCH in a darkened room until I did manage to find the thing. Once I had it, I wondered how I was going to light it, and spent several turns trying to do so until I examined it and discovered it was an electric torch, the only such modern appliance in this otherwise ye olde game. Another potentially daunting moment was when the Princess, whom I was escorting home, fled upon seeing the ghost. If I'd been more rational at the time, I would have thought the situation through and realised that the minor maze of an area into which she'd fled was closed in. This suggests the entirely logical solution to the puzzle: You just go up into that area and check each room until you find her. But I was briefly having visions of having to explore all of the game's 100ish rooms again looking for her.

The condition for getting the game's super happy ending is probably its sneakiest feature, pretty much guaranteeing nobody will achieve it without replaying the whole thing from the start. (Spoiler - click to show)That condition is that the player must give the gold key back to the thieving magpie before entering the castle. Just reading this information in the hints brought a smile to my minor failure face. Overall, Castle Adventure was very happy-making for me. It may feel too standard for some players and its old school spirit will deter others (in fact it plainly repelled many, based on reviews I read) but in its chosen field of uncomplicated two-wordish princess rescue it is finely designed, technically polished and subtly idiosyncratic.

The Forgotten Girls drops the player into the bare feet of an Indian girl sexually enslaved in a brothel. Considering the potentially confronting, bleak and dour qualities of the subject material – and it is the game's stated aim to raise awareness of the problem – The Forgotten Girls surprised me by turning out to be thoroughly action packed. As the heroine strives to rescue her friend and effect an escape, we see a range of the brothel's residents' behaviours through her eyes, ranging from the workaday to the cruel. The game's practical and non-exploitative approach keeps it from being didactic. For players who are concerned about encountering any explicit sexual abuse in the game, there is none on camera: it is only implied and out of game time. There are violent scenes, though.

The game's puzzles actually turn out to be fairly classic adventure game stuff: escapes, dealing with locked things, avoiding enemies. A central scene involving one character who is being tortured achieves the strange and novel feat of also managing to be a bit cute at the same time, as your character(Spoiler - click to show) takes this opportunity to create a series of amusing distractions to get rid of the guards. I found this scene to be particularly well executed because it extrapolates some interesting outcomes from simple commands. Had the same scene demanded the player spell out every element of his or her intentions in microscopic detail, it would likely have been a nightmare of worst-of-Infocom pedantry.

The game does have a few weaknesses in basic areas. You have to specify with which key you want to open what door, it's pretty strict on synonyms in general, and its effect is at times undermined by Inform's default delivery style, which remains unadorned here. EG 'You can see a can of beans (in which are some brown beans), a table (on which are Pari, some ropes, an iron rod, and a purse (closed))'. Considering the cleanliness and cleverness of the action overall, these aren't big problems. The game also has good built in hints in the typical style and offers helpful advice during its opening turns in a fashion inviting to newcomers.

The Forgotten Girls finds an engaging way into harsh subject matter. It's practically minded, uncomplicated and clear-eyed. It certainly bends reality a little to adventure game conceits, but does so in a way that's good for playability.

The excellent Andromeda Dreaming shares a universe with and is set immediately prior to the events depicted in Marco Innocenti's sci-fi adventure Andromeda Awakening (The Final Cut). Awakening saw the player take on the role of a scientist exploring an alien underground in the wake of a planetary disaster. In Dreaming, a new character, Aliss, wakes to find herself quarantined to a bunk in cylindrical space pod 19-Q, bound for somewhere. As Aliss, you're unsure of where you came from or where you're going, and so you begin to engage the other bunk dwellers in one cryptic-seeming conversation after another, sliding in and out of a sleep in which dreams reveal fragments of unsettling memories.

Dreaming has a wonderful structure, a nervous-making and palpable trajectory, its own very funny slang language (sported by the loquacious NPC Kadro) and extra frisson for people who have played Andromeda Awakening, though doing so is not a prerequisite. Extra frisson can also be derived retrospectively by playing Awakening after Dreaming.

Dreaming uses the quarantine pod as a hub location, a necessarily sparse and isolated one. Even if there was something in here to fiddle with, you couldn't reach it as you are strapped down in your bunk. All you can do initially is talk to the other pod inhabitants or go to sleep, yet these are the only actions needed in this location to drive the story forward, as it is your conversations and dreams which fill in the blanks of your predicament. Through just a handful of changeable features in the pod – different bunks being open or closed at different times, different characters being awake or asleep, a TV screen being on or off – the author is able to convey that groggy sense of time passing in a hermetically sealed space that anyone who has flown will recognise.

The conversations are managed by the same menu-based quips system Joey Jones has used effectively since his sci-fi adventure Calm. Aliss mostly has hesitant queries at her disposal, and they're mostly hesitant queries that are similar to each other because they all have the same goal of trying to elicit any and all information from the other party. Thus the interest is carried by the other characters' responses. My only technical quibble with the game is that it's possible to lose your bearings a bit if you UNDO during a menu conversation.

The various dream locations Aliss finds herself in demonstrate different levels of vividness, with temporary restrictions on the parser working perfectly to deliver an aesthetic of the intangible or incomplete; dreams with holes in them, or in which forgotten details are replaced by familiar ones. Another good trick on display is the technique of describing specific details before the broader ones, as if the memories are like close-ups that are stuck on certain things. In purely mechanical terms, the dreams are simple and linear, but their effect is entirely involving. The transitions from dreams back to the now are also well executed. Crucially, the returns to consciousness aren't announced. All the game has to do to achieve this is not reprint the room description, resulting in the player inevitably bumping back into the present with a command that doesn't work because the location has changed. It's a simple but totally effective aesthetic trick achieved with the parser alone.

To speak on the game's revelations about the situation it presents would be spoilerage. Instead, I'll just say I think Andromeda Dreaming is one of 2012's best IF games. It makes a virtue of its strong linearity by expressing its meaning through its structure. Trickiness is conveyed simply. Limitations turn out to be assets. The game is funny, unsettling and affecting.

If you complete it once, you may then wish to read the following: (Spoiler - click to show)There are many endings. Not several – at least twice that.

I hadn't played a one-move game before I played I'm Having a Heart Attack and it turned out to be an excellent introduction to this mini-genre. The game puts you in the shoes of an actor starring in some kind of pro-health commercial, one in which your character might be about to have a heart attack in the wake of a poorly lived life. The director's nearby, the camera's rolling and there are a few domestic props and food items within reach. With your single move, you determine how the scene will be performed. The viability of any one performance is determined by the director, whose enthusiastic interpretations of your actions are highly amusing. Each viable performance scores you another point out of a possible 41, plus there are an unknown number of bonus points up for grabs for trying out more meta or 'guess the verb' type actions. The scene loops, which makes a lot of sense in the context, giving you the opportunity to stumble around the set, fiddling with the props in a creative manner and trying on gratuitous emotions as the director eggs you on.

The game is addictive and progress tends to come in waves. One successful action will often cause a rash of similar actions to pop into your head. The director's feedback is also helpful. The more of it that you read, the more you may connect with the game's mindset and work out what other angles might lead to performances. I scored more than half the available known points plus a bunch of unknown points in my first session with the game, and I intend to revisit it to try to find more.

Dead 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.

Critical 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.

I 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.