Reviews by OtisTDog

OK, so you're a police officer. A cross-dressing police officer who likes the styles of the 60s. (And a werewolf, but that's not important.) And you have a sidekick: the creepy, giggling pyromaniac Donald McRonald, who is technically not a trademark violation. And you have a gun, which: "Sometimes you shoot folks with it, other times you just point it at folks." And a boa -- the constrictor sort, but that's really more of a deadly prank played by your fellow police officers than anything you can use.

And you are investigating a disturbance at the cemetery. A cemetery where the locals buried all the members of an "evil circus" that once terrorized the town, an incursion handily repelled by the trigger-happy constabulary to which you belong. And there are jelly doughnuts.

So... this is the kind of situation that, as a player, one has to embrace wholeheartedly in order to get any enjoyment out of the game. If the wacky, goofy, random and bizarre doesn't amuse you, then you may find yourself blinking in incomprehension at this enthusiastically off-beat work by J. J. Guest, noted author of To Hell in a Hamper. Personally, I found it to be about 90% amusing. There were some wrong notes that didn't jibe with my own sense of humor, but it was generally an entertaining and engaging short play experience. (Note that I played the expanded Inform 7 version, not the original ADRIFT version.)

However, I got really, really stuck. A lot. So much was going on in terms of joke delivery that it was almost hard to pay attention to what serves as the plot on a mechanical basis. Implementation is very spare with respect to NPC interactions, many of which are required to advance the game. With so many generic negative responses to various attempts, the modern player is quickly trained to stop trying -- it takes a concerted old-school style brute force approach to discover certain possibilities(Spoiler - click to show). I'm thinking specifically here of the gorilla, which must be threatened for no good reason to obtain the cigar, and the fact that escaping the first encounter with the main villain can only happen at a certain point. This results in guess-the-verb situations that are always offputting in such an otherwise polished work, and the very constrained implementation of interactions leaves little to do by way of experimentation when one doesn't have a clear idea of what to do next. (Although there is a hint system, it's very vague and, as MathBrush notes, occasionally non-functional.)

The thing that impressed me the most about this game was the soundtrack. Guest assembled an interesting ambient score from various bits of free-to-use music and sound effects, and the game cycles through them over time. (It's actually one giant 17 1/2 minute track; the length keeps the repetition below the threshold of obvious notice.) The soundtrack plays extremely smoothly, and unlike many attempts at background music which I've encountered, this one does not begin to grate in short order. In fact, rather than searching for a way to turn it off, I found myself turning it back on whenever it was automatically stopped by an >UNDO command.

This work gets high marks as a concept, but the execution falls a little short of what it needs in order to be truly recommendable to the general public or the novice. For those who like "weird" humor, there is plenty to like about it as is, and for those who don't, well... Guest provides occasional laughworthy quips that don't rely on weirdness at all. (Example: "For the record: Alligator breath smells like people who wondered what alligator breath smells like.") I'm putting it in the "good, not great" category, which means I think it's worth taking the time to play and study, and I would gladly revisit an updated version.

Mother Loose is one of those games that was developed as a labor of love and then subsequently released to the world. Its public debut was via IF Comp 1998, only the fourth such competition at the time, where it placed 6th of 27. This first effort by author Irene Callaci is now largely forgotten -- its more subtle charms lost in the glare of the multiple novae (Anchorhead, Spider and Web and Photopia) that dominated the public's attention in that year.

Ms. Callaci seems to have been something of a natural in producing interactive fiction. For a first effort, especially one that the author claims was produced while learning not just Inform 6 but object-oriented programming in general, Mother Loose is a remarkably high-quality result. It has a rich level of object implementation that encourages exploration and delivers plenty of vividly descriptive prose but which nonetheless does an excellent job of focusing the player's attention on those few things that are important. It makes use of a compass display in the status bar and has a built-in menu supplying author credits, an introduction to playing IF and in-game hints. There were essentially no bugs at the coding level, and I don't recall any misspellings or typos in the text.

This work includes several NPCs reflecting various levels of programming effort. Taken together, they are practically a guided tour of the major implementation styles, ranging from the practically inert and lifeless (a lamb) to the mute and command-ignoring flavor element (a kitten) to the comic relief chatterbox (a wolf) to the well-crafted exposition vending machine (an egg) to something occasionally engaging in life-like social interactions (a little girl). Ms. Callaci's successful efforts here were recognized; this work was nominated for both Best Individual NPC and Best NPCs in the 1998 XYZZY Awards.

Puzzle implementation is by contrast much sparer. There are only handful of obstacles in the game's dozen or so rooms. However, these have multiple solutions, and the greater difficulty in solving them comes from minor guess-the-verb issues rather than from deducing what must be done. (Of particular note here is one solution to a puzzle involving the well: (Spoiler - click to show)If you try to communicate with the stuck cat, be aware that it does not understand generic commands; one can only speak to it like a real cat. Commands that specifically work include (Spoiler - click to show)>SAY HERE KITTY or >CAT, COME OUT.)

The game's greatest innovation is the way that it gently mocks standard IF tropes by categorizing all significant PC actions as either naughty or nice. It's quite funny how certain actions yield both points and disapproving remarks. In addition to the running commentary provided by the narrator, the player's choices become significant at the end of the game. It's clear that the author intended the game to be enjoyable either way, and it definitely adds some richness to the limited scenario -- I couldn't resist replaying it to try out both paths.

A minor but still interesting novelty was the way that certain NPCs seem to "take over" some of the parser's responses when they are around. Where a command like >ASCEND TREE will normally result in a message about an unrecognized verb, when the wolf is present, the game instead responds "'Huh?' The wolf raises an eyebrow." This type of interaction does not seem to have much function and may be only a side-effect of the implementation of one particular puzzle, but it has a subtle though definite effect, reorienting the player's attention to the NPCs' presence in response to fruitless experimentation.

If there is a notable weakness to this game, it's that it takes some poking around to figure out what kind of game this will be and what kinds of goals are suitable. If one lacks the old school sensibility of wanting to solve puzzles just because they're there, it would be easy to walk around for a while and then give up in frustration. (This is especially true in light of the inclusion of several prominent objects without much apparent function. Some of these may be simple flavor elements, but others suggest the leftovers of abandoned lines of development.)

With a little guidance, this work is a very good introduction to IF for children. Even without guidance, the built-in hints will probably be enough, if they are necessary at all. Modern kids may need to be introduced to the very idea of nursery rhymes before any of it starts to make sense, but, as others have noted, nothing about the gameplay requires any deep knowledge of them in order to make progress. The more kids introduced to interactive fiction early, the more players there will be in the future, and games like this are essential to creating a positive impression of the art form in young readers.

A Flustered Duck starts out seeming promising enough: The PC, a downtrodden pig-boy working on the farm of the tyrannical Granny Grabby, has somehow scrimped and saved enough to finally buy the diamond ring that he needs to propose to the girl of his dreams -- but, he is thwarted in his designs when the farm's duck, a favorite of Granny's, ingests the ring during an unlikely accident.

It's a fanciful setup, vaguely remniscent of Lost Pig, and after 50 moves or so (enough to get out of the prologue and off the farm), I was well-primed for the series of mildly-comic obstacles that would surely stand between the protagonist and his goal. What I was not prepared for was being plunged into a nonsensical world of odd vignettes connected only by the most tenuous moon logic.

I don't really have a problem with the classic "pastiche" style of Adventure and the Infocom canon. Nor am I opposed to humor based on silliness. This world, however, just fundamentally didn't make sense, often veering past silly to a level of weirdness that was so unexpected as to be disconcerting. I and the two people with whom I was playing lost our ability to suspend disbelief within a few hundred moves, but we persevered in order to give the game a fair chance to recover.

Unfortunately, it never did. Though we did finish the game, we did so only after receiving plentiful help from the integrated hint system, which is context-sensitive and well-implemented. There was no occasion on which we regretted having consulted it. Even after having run the gauntlet of puzzles, all three of us were fairly horrified by the actual retrieval of the ring -- instead of being triumphant this moment was more than a little repugnant, as it involved (Spoiler - click to show)hacking into the duck with a knife and pulling the gore-covered ring from its torso. Although this act has no lasting physical consequences due to a magical countermeasure, I think the experience would leave the duck in a state better described as "traumatized" than as merely "flustered." After delivering the ring and mentally reviewing the activities of the PC that day, I cannot say that I was left thinking that he and his love interest would share a happy future, which rendered the end unsatisfying.

On a technical front, this piece was put together pretty well. Aside from a scoring bug (explained below), the only other one that stands out is a repeated message on picking something up (Spoiler - click to show)(the television) that doesn't make sense after the first time. The prose is very serviceable, and I can't recall any typographical errors.

Although this game didn't work for the three of us, your mileage may vary. For the edification of would-be authors and to advise potential players, following are some specific gripes that we had with the game. Many of these are generic gripes against the "very old school" style, but I will still call them out here because the introduction of this game falsely suggests the more player-friendly style of later eras.

(Spoiler - click to show)
1. Information given about the observable environment is deliberately incomplete. Objects in plain sight of the PC (Spoiler - click to show)(e.g. a penny on a table) go unmentioned unless the supporter on which they sit is examined. In some cases, objects in unobstructed view must be located with specific >EXAMINE commands. In an early and egregious case, even the presence of objects comparable in size to the PC (Spoiler - click to show)(furniture objects in the living room, including the penny-concealing table) are omitted from the initial description of a room.

2. Numerous objects are hidden inside or under objects described vaguely, often things whose existence and/or reason for being in that location are unhinted. While >EXAMINE and >SEARCH are generally equivalent, in at least one case (Spoiler - click to show)(berries on some bushes), >SEARCH gives no indication of a critical object's presence while >EXAMINE does.

3. The game implements a novel mechanic in which, upon taking an object for the first time, it is automatically examined... if it has not yet been examined. This is a neat idea, but it does not work well for a particular object (Spoiler - click to show)(a surfboard), which provides more information when examined while holding it. This critical extra information is easy to miss as a result. The effect is particularly off-putting in the context of a game including many objects that serve no specific purpose.

4. The game implements a hold-all object, but the logic controlling automatic shuffling of objects into it has faults, such that sometimes the object-juggling fails, causing the intended action to fail. It's not clear whether that's due to a bug affecting the "player's holdall" type of object in Inform 7 5U92 or due to an issue with custom code. While this would normally be a minor annoyance, this bug interacts with another bug related to scoring (Spoiler - click to show)(a point awarded for putting the poodle into the correct object so that it can be smuggled past its owner), such that the correct command will result in no score increase the second time it is tried. The combination of bugs creates an unintentional (and extremely irksome) last lousy point scenario.

5. Some actions must be repeated multiple times in order to trigger progress, even though the response to earlier attempts are failure messages that logically discourage additional attempts. This is particularly problematic in the game's opening vignette, in which the PC must try to >CATCH DUCK no less than four times to cause it to fly away, which allows the PC to leave the farm. (This was, incidentally, the first circumstance prompting use of hints -- an ill omen.)

6. In one miniature scene, the PC must select one of several items being offered by an NPC (Spoiler - click to show)(the gnome wizard). In reality, only one of the items can actually be selected, though choosing an "incorrect" one results in what seems to be a YES/NO prompt to confirm the choice. There doesn't seem to be any gameplay purpose to the frustration created for the player here; the scene would work just as well if the NPC just handed over the only allowable item.

From time to time, Andrew Plotkin has written works that are more about demonstrating what is possible from a technology standpoint than they are about delivering great stories. Lists and Lists is one of this type, and it certainly makes a deep impression when one finds oneself interacting with a Scheme interpreter instead of a normal command prompt.

The provided plot is the flimsiest excuse for presenting a test of programming skill in a language that few people are likely to be familiar with. The difficulty curve of the challenges is not linear, and it increases sharply toward the end of the series.

I don't normally recommend IF that is purely about the logic puzzles, but this piece is such a unique achievement that I think it's a must-see for anyone interested in IF as a whole. Arguably, at its core it is not so much IF as it is INF (Interactive Non-Fiction). Equally arguably, it is a stand-out example of puzzle design featuring a consistent, discoverable logical framework with very fair hinting and considerable challenge -- though I think any such argument would be disingenuous because none of Plotkin's genuine games are so derivative of the work of others. In any case, it is worth reviewing as a notable experiment, and as a bonus you'll learn something about an historically-significant programming language!

(Note: My scoring rubric implies that this work should earn a five-star score on the basis of its introduction an entirely new technique. However, although it was enjoyable and remarkable, I can't honestly say that it feels like a proper game to me, nor do I think it was truly intended to be thought of as one.)

After finishing this game, I was surprised to learn that it placed a respectable 4th of 27 entries in the 2007 IF Comp. This is remarkable -- it clearly demonstrates how much higher the average quality of comp entries has climbed over the course of the last decade and a half.

This game is very competently programmed in Inform 6 and presented no bugs during various playthroughs. The writing is serviceable, and I noticed only a handful of typographical errors (all of which were misplaced homonyms). The story, however, is a mish-mash of unrelated elements that create essentially no synergy.

In terms of "marketing materials," the game patterns itself after the Infocom style -- and especially after Planetfall. As with that game, feelies include a military service ID card and various documents relevant to the PC's new career. The feelies also imply that this game takes place in the same universe as that commercial-era classic, with the player character being the sibling of Planetfall's recently-enlisted Ensign Seventh Class who serves aboard the S.P.S. Feinstein. The most innovative item among the feelies of Across the Stars was the sample transcript, which covers the player character's experience when first joining the crew of the ship aboard which the story begins. (This is a departure from Infocom's practice, which presented sample transcripts from stories that were similar but unrelated.) The ostensible background provided by the feelies is wholly irrelevant to actual gameplay, though, and they can be skipped without losing anything of value.

The game itself is difficult to describe, because it mixes several elements and styles without committing to any of them enough to warrant a strong categorization. The basic segments of the plot are as follows: 1) (Spoiler - click to show)sabotage your ship while avoiding the occasional search by pirates who have captured the rest of the crew, 2) (Spoiler - click to show)explore an ancient temple from an alien culture to learn about their culture and history, 3) (Spoiler - click to show)defeat some dangerous creatures and rescue an NPC, 4) (Spoiler - click to show)get to the NPC's ship and activate its emergency beacon so that you can both be rescued. One or two of these segments might have served as the whole plot of a modern comp game; here, each is treated so breezily that it feels like four half-stories and zero complete ones.

In terms of richness of setting, most of it is found in plot segment 2, which -- oddly -- seems almost wholly optional. In fact, the IFDB-linked walkthrough (which seems to have been for an earlier version of the game) pretty much skips this part. It appears that much of it was grafted on later, and complications to the main plot added to require engagement with these new pieces.

If this was the development strategy, then it is easiest to explain the game's shortcomings as simply the result of it not reflecting any integrated vision of a whole. However, this is a fatal flaw, because in its final form the plot basically requires the player character to (Spoiler - click to show)secure the primary magical artifact of an ancient world religion solely in order to use it as a light source!

At first I thought that this aspect of gameplay was the result of the authors allowing plenty of freedom in the path that the player takes through the game, such that being a good guy is optional. I would have respected that, but review of the source code suggests that this is part of the critical path to reaching the end. I found the overall experience to be somewhat distasteful.

The authors themselves seemed to have trouble coming to grips with the game as a whole; the subtitle of "the Ralckor Incident" seems an odd choice, as the subtitular creature really only figures prominently into plot segment 3. If tasked with naming the game, I might suggest (Spoiler - click to show)"the Taking of the Supalace" (segment 1) or (Spoiler - click to show)"Prophecy of the Protector" (segment 2) or even (Spoiler - click to show)"Escape from Brakis VI" (segment 4). The pacing and structure of the game made it seem to me as though the proposed segment 2 title would fit best, but given the resolution of that segment it would really only do so in an ironic manner.

Playing this game may still be worthwhile as an exercise for the would-be author, because on the local scale of individual rooms, objects and actions there is much to admire about this work. I would not really recommend it to players as entertainment, however. If you want action-adventure, a rich fictional history with layers of meaningful symbolism, engaging and purposeful NPCs, and epic quests to save a world, then you will likely be disappointed by this work that seems to offer all of these things but ends up delivering none.

[Full Disclosure: I know the author of this work personally, and I served as a beta tester for this game.]

"I don't want to play in a world where I can't kick a pirate using karate." So said Janet Murray, author of Hamlet on the Holodeck, in a 1988 article about Plundered Hearts (MIT Technology Review, May/June 1988, p. 16). Well, Janet... it took almost 35 years, but your cri du coeur has been answered, and answered well!

A Matter of Heist Urgency is an unusual offering. Rooted in a series of silly short stories written for a grade schooler who enjoys horses and superheroes, it was developed into a short game as a fun way of introducing that grade schooler to interactive fiction. Having reached about 25,000 words in size and a level of playability that was very newbie-friendly, it was then further developed to be an entry in IF Comp 2022, doubling its word count in the process. The result is a fast-paced, smoothly-flowing, and very amusing short game that has been favorably compared to a Saturday morning kids' cartoon.

The game is "puzzleless" in the sense that there is nothing intended to impede the story's progression to its successful conclusion. By the same token, it is "merciful" on the Zarfian scale -- the player may be left with varying degrees of satisfaction at the outcome, but the player character cannot die or even really lose. That said, the game does reward engagement, and there is some light thinking to be done in order to achieve the highest rankings, which are issued at the end of the game even though there is no formal score. (To be less ambiguous, I should instead say that the game has no point rewards; it does indeed have a musical score.)

Critical reception in the context of the competition was mixed. The "marketing materials" (i.e. cover and blurb) developed for the game emphasize the word "heist" in the title, which may set genre expectations of a complex puzzling-solving exercise involving tight timing and intricate details. (This perception may also be reinforced by the blurb's claim of a "robust" hint system, though in hindsight that is clearly tongue-in-cheek.) In contrast, the cover illustration depicts cartoon horses and a pirate ship, and the blurb characterizes the game as "a delightfully short action-comedy" with "intense fights with kung-fu llamas," so arguably it delivers exactly what it says on the tin.

The humor of the piece is its strong point, but it is also perhaps idiosyncratic. Players seem to decide whether or not the game appeals to them very quickly, beginning with their perception of the pun in the title. Much of the humor depends on juxtaposition: The illustration of Anastasia as a rainbow-maned equine invites a comparison to "My Little Pony," but the way the plot plays out is closer to "The A-Team."

The game's tone is unapologetically playful, and it works best when approached in a playful mood. The setting is essentially the Land of Make Believe, which you may recall spending time in as a child. Character archetypes are deployed without any consideration for historical accuracy; instead they are chosen to evoke a specific mood and expectations in the player. This creates a fluid version of in-game reality that can subject the player to surprises(Spoiler - click to show) (a pirate with a jetpack??) but still feels consistent in the sense of keeping the scenario and the interaction fun. If you're the kind of person who is preoccupied by the question of how a horse can pick up a coconut, then... well, I would normally say not to play this game, but, in fact, the existing scientific sample (N=2, from ferkung's and Rovarsson's reviews) suggests that you will still enjoy this game.

Personally, I have found the game to be very enjoyable, even through many replays, because there are countless details in the implementation that reward you for poking around by responding with small jokes. I am especially impressed by one of the new scenes added post-competition (in release 5): It is a very "cinematic" flashback sequence using a method of synchronized music and text that I hadn't encountered elsewhere, though a similar technique was later employed in Little Match Girl 4. (Note that this scene is shown only if you are victorious in the first fight; if you lose, you instead get to play a very funny interlude from the protagonist's early training.)

As you have no doubt gathered by now, this is not a "serious" piece. However, its development was taken seriously by the author, first with the intention of creating a memorable and enjoyable introduction to interactive fiction, then with the intention of crafting a light-hearted and diverting short experience for judges working through a field of entries that generally strive for more literary merit.

Given my involvement, it's not appropriate to let my star rating count toward the average, but I give it high marks due to its very good implementation quality, memorable and amusing characters, and judicious use of sound. I encourage everyone looking for a half hour of pure entertainment to give this piece a try. I also highly encourage use of a sound-capable interpreter, which is essential for appreciating the scene-enhancing music and the special flashback sequence mentioned above.

Another Earth, Another Sky, the second installment of the popular Earth and Sky series, is a significant step up from its predecessor in terms of technical sophistication. Object implementation is complete but not very deep, matching a relatively spare descriptive style for locations. What stands out most is the "situational implementation" -- the game's bug-free logic is prepared for a wide variety of actions that the player character (Earth) might take, or might ask the key NPC (Sky) to do.

This attention to scenario detail was atypical at the time, and the game was exceptionally well-received. Not only did it win the 2002 IF Comp, it received 2nd place in the comp's Miss Congeniality rankings and was later nominated for five XYZZY awards (winning only Best Use of Medium). This last is almost certainly due to the use of comic-book style graphical elements (title cards and onomatopoeia-based "sound effects"), an affordance of the Glulx virtual machine that was still little-used at the time.

Unlike the first installment, which sweeps the player along quite quickly, this episode has a slower and more contemplative pace. The bulk of the action occurs in three parts: (Spoiler - click to show)a short investigation at an abandoned cabin, a much longer investigation on an unusual artificial planetoid, and a brief climax and denouement. The second portion will take up the bulk of the playtime, consisting of one long puzzle about gaining access to the endgame. The scenario is designed such that you must explore the entire area to find the pieces that you need, creating a "travelogue" type of experience that encourages you experience the sights, sounds and smells of the various geographical sections. Sprinkled through this are various optional discoveries that let the thorough player unravel the mystery that serves as a plot, but a full explanation will be provided before the cliffhanger ending in any case.

The game does not stand very well on its own, since the plot continues the events of the first game and seems largely designed to supply backstory for the third episode. The climax encounter with a new NPC is disappointingly short, especially when contrasted with the earlier interaction with the PC's superhero sibling. Rather than attempt this as standalone entertainment, it is probably best enjoyed as part of the series.

One minor item of interest is that the startup menu allows the player to optionally specify details of the resolution of key events that occurred during his or her playthrough of the first episode. The answers have a small impact on the introductory text, but I did not notice any other consequence.

I downloaded An Act of Misdirection many years ago, having seen it mentioned in passing in a positive way. The only thing that I remembered about it when I loaded it up this morning was that you play the part of a stage magician, and that you had to figure out the steps of the performance.

"Well, this should be interesting," I thought after reading the run-up to the first command prompt. Imagine my delight as I found that the way had been carefully prepared for my bumbling first attempts, that hints and nudges were craftily placed within every turn of phrase of the interaction. These hints began small and subtle but escalated to large and glaring when needed to get my attention, and rapidly taught me both to follow their lead and to take advantage of the breaks in the action to "work the crowd" for a response.

I have noted in the past about certain games' ability to follow the player until the player can learn to follow them. This is accomplished so expertly here that it seems effortless. The only point where I got stalled too long was a place where a little thinking about the logic of performances of this type would have sufficed. (Spoiler - click to show)Specifically, having used a blunt instrument for its intended purpose, it makes sense that it can be disposed of thereafter. (Spoiler - click to show)A hint from your assistance about which item he expects to catch would have smoothed the way here; if there was one, I missed it. The correct move was apparent enough when I stopped to consider it... it just took me a while to do so because I was swept up in the urgency of keeping the show going. The author, Callico Harrison, should truly take a bow for this achievement; not many games manage to instill this sense of immediacy.

Having come to this game mostly "cold," I wasn't even aware that there was a horror component to it. I would imagine that this situation has been relatively rare since the game's initial release -- this IFDB page, for example, clearly labels it as such -- but knowing about it is a massive spoiler! If you have already played the game you can imagine my own shock, echoing that of the fictional audience, as the performance reaches its culmination. The first act had been an Act of Misdirection, indeed.

Moving on from there, Ms. Harrison demonstrates a surprisingly rich and deep command of language in painting the scenes of the protagonist's origin story. Many people seem to find this second section to be inferior to the first; I did not. The same craft and skill is used to keep the action moving with clues, now less blatant in their prompting of the right command. The parser is fairly free in its interpretation of your input at this point, redirecting your intent when you are "close enough" in order to keep the scene moving briskly. Call it "railroaded" if you like, but I prefer to think of it as the game urgently requesting your cooperation to play along so as not to ruin the intended pacing. I found myself eager to catch up as the game led me through a chaotic situation, glancing this way and that at glimpses of Victorian life before being tugged along to a more contemplative setting where the horror begins in earnest.

Here Ms. Harrison shows that her command of the psychology of horror is as great as that of her command of language -- indeed, I found this section to be a master class of the technique for "showing, not telling" in the context of interactive fiction. I expect to spend much time scrutinizing the writing here to better understand how she so expertly conveys key knowledge indirectly; important realizations suddenly appear in your mind at the center of a flourish of well-chosen connotations. A second bow in encore is called for here.

If there is anything to criticize about this work, it is that it is over too quickly, and that certain details of the scenario are not clear after a first playing. I am glad to see that other reviewers almost universally recommend a second playthrough, and I look forward to doing so... preferably with other players who don't know what to expect.

As a final note, I want to point out that this game was written in Inform 6, and it is a remarkable feat to achieve such a level of polish with that toolset. Very few games of the era are its equal in this respect, though nowadays Inform 7 makes it easier (if not exactly easy) to build scenarios of comparable quality.

Ms. Harrison does not seem to have ever produced another standalone work of IF (though she did contribute to Cragne Manor), but if she does she will find me among those waiting "in anticipation of something magical" to try her next work.

Back to Life... Unfortunately is an entertaining but significantly buggy game. I played version 3, obtained from the IF Archive. (At least, I think it was version 3. The game banner claims to be version 2, but the response to the command >BUGS implies otherwise.)

As noted by another reviewer, the game's humor starts well but doesn't hold up for long; there are really only so many ways to tell the same joke. However, by the time the humor has worn off, you are likely to have achieved several "successes," so you will be well-motivated to finish the game on the basis of wanting to complete the remaining puzzles. Regrettably, you are likely to run into trouble while doing so.

Many of the issues stem from the use of ADRIFT to write the game. As I've noted elsewhere, the most frustrating thing about ADRIFT as a player is that it lacks a proper parser and does not differentiate well between errors that are caused by failure to understand the arrangement of words vs. the failure to understand the words themselves. The game's gravest errors are where it provides inaccurate feedback, giving the player the perception that certain required commands would have no effect or would be unrecognized. I got hung up for quite a while on the syntax required to mark boxes on a form; since the need to do this is immediate and obvious, it is no spoiler to relay that the correct syntax is of the form >TICK BOX 1. (Just >TICK BOX is treated as a totally unrecognized command -- a disambiguation message would have helped tremendously here.) The worst offender of this class was (Spoiler - click to show)(see numbered hint 3 below). Attempting to use any other direct object results in a message instructing the player to say which of several indirect objects is intended. Specifying the correct indirect object in the command via its typical adventurese abbreviation (i.e. color only) will not work and falsely claim that there is no effect.

There is a built-in hint system, but it is not very extensive and does not help with guess-the-* problems. (Even here there is a significant inconsistency: While >HINT works as a command, the response to >HINTS claims there are no hints in the game.) (Spoiler - click to show)If you get really frustrated, there is a command >CLUES that will point the way to 100% spoilage. Since the game is enjoyable and worth playing, I offer the following hints:

1. Handling an intruder: (Spoiler - click to show)After exploring a bit, you will hear the sound of an intruder in your chambers. (Spoiler - click to show)You should immediately >LISTEN as soon as you are notified of this. Should you fail to do so, it will seem as though the noise was a false alarm. Go back to the Throne Room and >LISTEN to trigger the next part of the sequence. (Spoiler - click to show)An assassin! Oh, no!... but wait a minute, don't you want to die? (Spoiler - click to show)As the game hints, you don't want to die at the hands of this particular person -- once was enough.(Spoiler - click to show)You can't handle the intruder alone. He will kill you.(Spoiler - click to show)The guards can help here. (Spoiler - click to show)You have to call them -- but it only works correctly from the Laboratory. (Spoiler - click to show)If you don't do things this way, you will miss two opportunities to die.

2. Dealing with the problems of the kingdom: (Spoiler - click to show)You don't want to rule anymore. That's someone else's job. Someone specific. (Spoiler - click to show)Your High Chancellor is very... effective, shall we say, but he can't do the job alone. (Spoiler - click to show)Your layabout son is the proper ruler at this point. You will need to "encourage" him. (Spoiler - click to show)Did you know that you can >CALL GUARDS from the Throne Room? (Spoiler - click to show)They will provide you with a ring allowing telepathic communication. Pay attention to its introduction. (Spoiler - click to show)Examine it carefully before putting it on. (Spoiler - click to show)Your son isn't eager to take up his duties, but he is eager to avoid any displeasure. (Spoiler - click to show)Especially pain. (Spoiler - click to show)>SMASH RING -- but only while wearing it in the Throne Room, for inexplicable reasons. That will get his attention. (Spoiler - click to show)Then >TALK TO TOROMIN again -- but only somewhere other than the Throne Room, for inexplicable reasons.

3. An optional death: (Spoiler - click to show)If you have handled the intruder correctly, you will get two items that he was carrying. (Spoiler - click to show)One is easily applied to your goal. The other requires some work to use. (Spoiler - click to show)The leaf has an odor that reminds you of something. (Spoiler - click to show)Your lab has something that can help. (Spoiler - click to show)You want to heat it up. Which potion is best for this? (Spoiler - click to show)For inexplicable reasons, >PUT LEAF IN PURPLE won't work (and falsely claim that nothing happened), but >PUT LEAF IN POTION or >PUT LEAF IN PURPLE POTION will have a result.

4. A required death: (Spoiler - click to show)As you have discovered, your minions are quite adept at bringing you back to life. How can you stop them? (Spoiler - click to show)You need to be not just killed but obliterated. (Spoiler - click to show)Earthly methods are insufficient here; you need divine intervention. (Spoiler - click to show)Divine is not the same as infernal! (Spoiler - click to show)You probably found a scroll discussing "words of power" in the Laboratory. (Spoiler - click to show)Oh, darn -- the words are missing. But this was your scroll, supposedly, so maybe you already know them? (Spoiler - click to show)You can just say >WORDS OF POWER to use them -- in the right place. (Spoiler - click to show)The right place being someplace open to the sky. (Spoiler - click to show)No, not the balcony. (Spoiler - click to show)The Throne Room needs to be prepared before it will work. So do you. The scroll is specific about this. (Spoiler - click to show)Holy water is the tool for the job. (Spoiler - click to show)You can drink some to prepare yourself, but you need a way to get some to the Throne Room. (Spoiler - click to show)The only container that can be used for this must be ordered using the mouldy scroll (obtained via >CALL GUARDS in the Throne Room). (Spoiler - click to show)The genie in a bottle is a red herring. (Spoiler - click to show)The fiery potion won't kill you but does provide you with a container. (Spoiler - click to show)You can >FILL VIAL in the Laboratory and >SPRINKLE WATER in the Throne Room.

Although the goal is to reach a score of 10, the way to achieve this best score is, unexpectedly, to forego one of the opportunities (Spoiler - click to show)(see numbered clue 1 above). Doing so provides the PC with needed items that can't be obtained any other (legitimate) way. Sharp-eyed players will note that the score (measured in "successful suicide attempts") goes up even when the PC chooses not to die here, and that this mysterious extra death is needed to get to 10. The reason for this is not clear; it seems to be a bug.

The least bothersome issues encountered in the course of play were several misspellings that looked like the result of depending on a spellchecker instead of human proofreading. Of particular note were two phrases: "the semi-literature Toromin" (instead of "semi-literate") and "full extent of the water" (presumably instead of "of the law"?) -- the remainder were sound-alike errors that are easier to miss.

The problems were frequent and severe enough to sharply reduce my opinion of the gameplay experience, which is why I've given it two stars. However, I did like this game, and I encourage people to try it out. Its premise is solid, and the writing is above-average. It ended up being the first of a series, followed by two sequels that received respectable rankings within the competitions in which they were entered. With some corrections in place, this game would definitely warrant three stars. Until that happens, don't hesitate to use the clues above as a way of smoothing out the roughest parts.

Wisher, Theurgist, Fatalist is a short game with an unusually ambitious scope. It is intended as an homage (self-described as "fanfic" in the game's banner) of an RPG system proposed by Jenna Moran (the outdated URL for which is also shown in the game's banner; the Wayback Machine has an archived version).

I had never heard of this RPG, and a cursory review of its rules suggests that it was proposed as a game mostly in jest. Rules are frequently written in a joking manner, such as the following passage: "Don't play WTF when operating heavy machinery. Use caution when playing WTF while tired, drunk, or punchy, as it may increase the chance that the shadow lurking beyond the edge of the world shall immure you all in timeless misery. If you are or think you might be pregnant, talk to your doctor about playing WTF." Even the RPG's acronym (WTF) implies that it is not intended to be taken seriously.

However, the author of the RPG has published other commercial role-playing games, and the part of the WTF rules that are not in jest describes a collaborative story-building RPG system. That system as described appears to be at least 90% satire. I don't have enough experience with this type of game to comment on WTF's playability, but I assume that it is possible with the right set of participants. (A word of warning: The rules' example of play, from which the title of this review was drawn, might give you pause.)

The remaining 10% of the non-jest portion appears to be an outline of the RPG author's philosophy and/or methodology for creating fantasy stories (and/or possibly for living), which is interesting but is not the point of this review. The only part that is relevant is the prescribed gross structure of a game of the RPG, which begins in the the Civilized Lands. (Per the prescribed outline, the story is intended to progress from there to the Savage People and the Fairies, then on to the Ur-Toads -- optionally first attempting to reach the Dragons of the Deeps -- and thence to the Conclusion. Understand that these segments of the journey and their names are in some sense composed of mythic archetypes, and would seem to be highly fluid in their execution. The only requirement is that certain types of narrative challenge are overcome at each step.)

Xavid, the author of the work of interactive fiction which is the point of this review, seems to have been inspired by the RPG's more poetic sections to create a parser game rooted in the RPG ruleset. This is a goal that on the face of it seems manifestly impossible, as the ruleset is unapologetic about its massive ambiguities, and computer programs don't do ambiguity well. As a consequence, many (indeed, most) of the mechanics of the RPG are simply ignored by the IF. Perhaps unexpectedly, what remains seems, in fact, to be a pretty good adaptation of the intended play experience to the parser medium.

The human player takes the role of the player character, who is the Wisher, and indirectly takes the roles of the Theurgist and Fatalist, who are both non-player characters that become obedient to PC commands after minor puzzles are solved. Each of these roles has the ability to influence certain in-game objects by injecting those objects with a quality that is associated with the role. For Wishers, this is "valence," the relevance of that thing to the narrative. For Fatalists, this is truth (as judged within the story world). For Theurgists, this is "mechanical support," ostensibly referring to RPG game mechanics (but rather significantly re-defined in the IF).

Each of these qualities will be discovered in the course of play and can be used by the appropriate character to invest objects with supernatural influence for the purpose of solving the IF's puzzles, all of which offer multiple solutions. In addition, the Wisher and Theurgist characters have a limited ability to use other special influence, by affecting the thoughts of creatures and physical qualities of things respectively. (In the RPG, the Fatalist's special power is the ability to declare what is true about the history of the world. It would be difficult to implement in a meaningful way, so in the IF this character is largely reduced to the source of in-game lore.)

The events of the game cover the characters' travails in the first part (i.e. the Civilized Lands segment) of an RPG game, in which they must obtain the (vampire) queen's blessing to set out on their quest for the Jewel of All Desiring. This portion is very sparsely implemented, largely composed of single-sentence room descriptions and "You can't see any such thing." parser errors. However, mechanically the game performs very well, implementing some relatively tricky things without any noteworthy bugs. The built-in hint system is available if needed, which goes a long way toward keeping player interest from getting derailed by guess-the-verb and/or guess-the-noun frustration. The writing, limited though it is, is well-focused on what is necessary to create a minimum of atmosphere and adequate context for the game's puzzles.

The conclusion of the game is quite unexpected... and very thought-provoking. (Spoiler - click to show)Having reached the object of the quest, the player must wish the world into existence. (Spoiler - click to show)(In accordance with the rules of the RPG, this will be the world that the characters experienced -- yes, it's very meta that way.) The game asks a series of questions about the actions taken by the characters, soliciting your -- as in you, the player's -- input on the matter. Questions are phrased such that they ask whether or not you agree that aspect of the story. At the end of the ten questions, your score is given, and the maximum score accords with answering yes -- answering yes honestly -- to all questions. If the player does not like their score, they are implicitly invited to play again to find other solutions to the puzzles.

This game left me with mixed feelings. On the one hand, the concept behind it is compelling, and the implementation reflects insightful and inventive design in adapting the more ephemeral aspects of the RPG as written. On the other hand, everything about the game's text and interaction is so bare-bones that on the whole it feels flat and empty -- in stark contrast with the tidbits of evocative and compelling text pulled from the ruleset and delivered via the Fatalist. Ultimately, I decided that this flatness is what would matter most from the perspective of the average player, which is why I've given this work only two stars.

I remind the reader that, in my book, two stars is not a bad rating. I certainly think that this game is worth experiencing and contemplating -- it doesn't take long. Perhaps Xavid will return to this project and expand it to the point where it better fulfills its potential. If not... well, perhaps someone else will come along to take another shot at realizing the vision shimmering in the distance here.