Reviews by OtisTDog

After recently playing The Ghost Train by the same author and noticing the announcement that this work, too, had a recently-revised release, I decided to give this story a try to see how the author's craft had improved. My opinion is mixed.

The structure and flow of the story is very similar to that of the The Ghost Train: a catastrophic opening, followed by a fast-paced journey of exploration along fairly strict rails, followed by a chase, a time-limit sequence, and a couple of strongly-hinted "puzzles" (in function, light-duty obstacles) barring the way to the final conclusion. Less reliance on formula may benefit future works.

The implementation focus is somewhat better, with fewer elements that appear to be vestigial remnants of coding experimentation (though some(Spoiler - click to show), such as the food machine in the ship's kitchen, persist). The writing quality also seemed improved. Imagery was more subdued, and there were many fewer instances of repetition than can be found in its predecessor. However, like its predecessor, this story suffered from a fairly high rate of grammar and spelling errors, so additional proofreading efforts are warranted.

The coding quality seemed to have slipped a notch. I ran into several minor bugs that got in the way of the story, especially situations where two nouns could not be disambiguated(Spoiler - click to show), e.g. as occurs when trying to install the unburned circuit board during the lifeboat escape sequence. Also of note are those cases where critical objects are not mentioned in room descriptions and must be learnt of via other means(Spoiler - click to show), e.g. the CPU "circuit" object in the flight deck, which seemed to have no indication of its existence outside of the response to asking the computer about the CPU, even though it would have been plainly visible to the player character. In addition, synonym sickness is more evident(Spoiler - click to show), as when the lack of the word 'fuselage' as a synonym for 'ship' kept me busy for 20 minutes wandering the jungle and trying to enter through the implemented canopy object because the hatch can only be discovered via examining the 'ship', a word not used in describing the crash scene.

There is a famous quote by Antoine de Saint-Exupery: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." This is advice that any new author can benefit from, and it seems to be the single principle that best sums up the difference between this piece and its earlier cousin. Applying this maxim more diligently would surely continue the trend of improvement in future works from this author.

The incidence of first-timer foibles is about the same as in The Ghost Train, with #2, #8, #9, #10, #12, and #13 evident (this last being found mostly in out-of-place Microsoft and McDonalds humor sprinkled throughout).

Maybe it's because Halloween is coming up, or maybe it's because I just read Jimmy Maher's analysis of Transylvania at The Digital Antiquarian, but when I saw the announcement on IFDB that release 7 of this game was available, I decided to give it a try.

According to the author's own description of the game's origin, it was inspired in large part by a carnival ride of the same name. My own experience with such rides is very limited, but the ones I've encountered all seem to suffer from at least two common failings. First: In their quest to create a suitably "scary" setting, the makers heap image upon image until they have far overshot the mark, resulting in a panoply more bewildering than frightening. Second: The production quality is usually so low that suspension of disbelief is impossible for anyone but very small children. Unfortunately, Ghost Train seems to reflect both of these qualities, leaving the player with sense of having run into something that had the potential to be terrifying but didn't quite pull it off -- an encounter with Cabbage Man instead of the Creature from the Black Lagoon.

Although I give this work 2 stars, it does show some promising elements. The thing that impressed most me was the author's attempt, for at least the first half of the story, to keep the setting alive and vibrant through the use of transitory events and details happening "in the background". This isn't easy to do well, and it shows a dedication to polishing the player experience that is very much to the author's credit.

However, this level of polish is not consistent, and it is most noticeably absent in some key scenes(Spoiler - click to show): as an example, the encounter with "The Demon" that opens the final act. Here, the challenge is not pulling the player's attention to the background to give the illusion of a broader world, but focusing the player's attention on the foreground and (ostensibly, at least) forcing a plot-critical choice. It's quite odd that the player can dither about for as many turns as he or she likes while the antagonist waits patiently for a keyword.

Coding quality was, in general, good enough, though there is definitely room for improvement in those cases where the author feels compelled to clumsily spell out the correct grammar to achieve certain actions. The only thing that looked like a true bug to me ended up helping instead of hurting(Spoiler - click to show), when 'x parchments' was interpreted as referring to an object named parchment due to Inform's word length limit.

This game would benefit significantly from additional attention to proofreading and editing. It is rife with errors in spelling, punctuation, capitalization, and other aspects of grammar, and it suffers from an irritating tendency to repeat the same adjective, phrasing, or information multiple times in quick succession. In some cases this is probably not desired by the author (as when an object is mentioned both in the location's description text and via default room description rules(Spoiler - click to show), e.g. the clock in the abandoned station), but in other cases it appears to be the result of simply not re-reading what was written(Spoiler - click to show) (e.g., in the opening sequence: "On silver moonlit track it races clear" followed shortly by "The steam engine 'Bluebell,' races fast and clear").

As I've said elsewhere, horror is an exceptionally difficult genre within interactive fiction, and this piece is another example in support of that claim. I would expect most players would find it about as entertaining and diverting as the carnival ride that was its namesake -- amusing enough if you're in the right mood for it. Outside of those rare occasions, its main value is in challenging the aspiring author to ponder how one might improve on the original.

On that note, I point the reader to Michael Coyne's list of First-Timer Foibles as an evaluation guide for this work. I spotted #2, #4, #8, #10(Spoiler - click to show) (most bothersome in situations where multiple locations are used when one would suffice, such as the signal booth area), #12, and #13(Spoiler - click to show) (e.g. the spelled-out instructions for certain actions, the prompt encouragements like 'Tell me what to do.' that aren't set off as being separate from normal story text).

Produced in response to the challenge of Speed-IF 6, this lightweight entry is competently coded and can be completed in short order, but is poorly designed both as a story (the premise and micro-story seem somewhat forced) and as a game (the single puzzle isn't even clearly presented as a puzzle). This speed IF had a particularly odd assortment of seed ideas; it will be interesting to see if any of the other submissions do better.

The deficiencies of this piece are hardly unusual for speed IF, and my one-star rating is typical for the mode. The apparent quality of the coding (written in Inform 6, where haste can easily make waste) leads me to suspect that the author's other works (some of which have good ratings from small groups of players) are worth exploring.

You might need the walkthrough to discover the winning moves, but the game universe is small enough that you will likely find them through brute force with a little patience.

The only reason I started this piece was because I came across The Warlord, The Princess & The Bulldog here on IFDB. I liked the introduction to that so much that, when I discovered it was a sequel, I decided to play the first installment of the series before continuing.

A Spot of Bother has a funny premise, and I liked the humor in the introductory backstory. The absurdist tone fits perfectly with absurdist version of the universe presented in a typical "text adventure." However, the joke started to wear off pretty quickly, because the style of humor in the writing (spoofy one-liners at a brisk pace) is entirely mismatched with the structure of the game (really, really oblique puzzles that bring the action to a grinding halt, and lots of them).

Some puzzles can be bypassed by taking a hit on your lives (you get 5 to start), but others must be solved to make any progress. The limited space to explore in the game between required solutions -- often allowing progress to only one additional room -- means that there's nothing but frustration to be had if you get stuck.

To make progress, sometimes it's necessary to examine things in great detail. The lopsided object implementation -- from items mentioned in room descriptions but not "there" to items with 4 levels of detail description available -- makes this requirement particularly cruel. Couple this with an irksome tendency to require performing the same action multiple times, and any sense of fairness to the player evaporates.(Spoiler - click to show) The final insult is the pure capriciousness of exchanges like this:

> examine metal bar
This looks like a javelin of some kind, although quite why Mrs Moog had it lying around her front garden you can’t imagine.

> throw metal bar at window
You don’t see any reason to go throwing things around.

> x spike
The spike is about an inch wide and an inch tall and has the look of a good poking device to you.

> throw spike at camera
You take aim and throw. The spike hits the bars and bounces back, falling onto the ground at your feet.

So there's no reason to go throwing things around, especially not hard metal javelin-like things, when a softer wooden spike described as a poking device is so much better for the job.

There are several other examples in the same vein, unfortunately.

And believe me, stuck you will be. I have a hard time agreeing that this game is a "puzzlefest" because it doesn't seem to have very many genuine puzzles. If you accept Nick Montfort's argument that a good IF puzzle is like a riddle, the kind of riddles in this work are a lot like Bilbo's "What have I got in my pocket?" in The Hobbit -- patently unfair and likely to drive the one trying to solve them crazy.

It's hard to believe that anyone could have possibly finished this game without resorting to a walkthrough or a decompiler. There are built-in hints, but I found them to be singularly useless -- either referring to puzzles I wasn't aware of yet or confirming the existence of puzzles I was aware of already, and offering no actual hints (i.e. a nudge in the right direction without spoiling the puzzle entirely) in either case.

The game also suffers with respect to quality of implementation. There are guess-the-verb challenges of the most elemental kind. In the first room, a key item offers different responses depending on whether you use "get" or "take." In another place, "examine sign" works but "read sign" doesn't. For one obstacle, "flick switch" but not "flip" or "change" or "toggle" or "turn" or "use" or "press" or "pull" or "push" or any of the others I tried before resorting to the walkthrough. There's even a game-critical NPC that you can't examine but can talk to.

As a side note, I think I like ADRIFT less every time I run into it. What it makes me realize is that the quality of the parser creates a fundamental difference in the quality of the player experience. ADRIFT's parser appears fairly primitive, with the most irritating aspect being that it is often not apparent to a newcomer whether a word has been understood or not -- in other words, one can't differentiate parser failure from referring to an unimplemented object.

All of the above said, producing this piece took a significant effort, and with a higher-quality implementation, I'm sure I would have had a much more favorable reaction to it. I really do like the writing and even found just reading the walkthrough to be an enjoyable experience once I gave up hope of actually working through the game on my own. Perhaps if every puzzle could have been bypassed with an amusing near-death sequence, allowing the story to be completed with few points quickly, reaching the end would have been much more enjoyable, and I would have been more motivated to figure out how to get the highest score.

I still plan on playing the sequel to this piece, but it may be a while before I'm ready to risk that much frustration again.

What this game lacks in plot, puzzles, and punctuation, it makes up with a simple earnestness and a fortuitous brevity. Navigating the simple linear path through 8 or so rooms nearly devoid of implemented objects is an exercise in perseverance and a relatively lightweight one at that.

There doesn't seem to be much here; figuring out the directions linking rooms together seems to be the biggest challenge on your way to the end location. You'll find a few letters of encouragement and an apparently unnecessary lantern on the way, but there are no obstacles to overcome or reasons to care about getting there.

This is an Inform 7 6G60 release, so I'm guessing this is a first time effort by someone who has read the opening chapters of "Writing with Inform." I encourage the author to read the rest of the Inform 7 manual as well as Coyne's First-Timer Foibles, because it's clear that the imaginative seeds of something much grander are already on display here. All that's needed is more patience and polish to produce something worth playing.

I'm generally not one for keyword-driven stories, which emulate the kind of interactivity you would find in hypertext. I've always felt that that type of interaction was inherently limiting; with all the connections drawn out for the reader, there isn't much interactivity to be had other than by exploring the graph that defines the story's structure.

That said, when considered with respect to some of the more railroaded story-oriented IF out there, it actually demonstrates some comparative benefits. No chance for hunt-the-verb, hunt-the-noun, synonym sickness, or many of the other opportunities for failure that "standard" IF offers. Non-interactive NPCs seem less of an affront when the illusion of free conversation isn't even presented. So maybe there's a natural fit between this format and an all-story, no-puzzles work.

As far as plot goes, this piece is short but very interesting. In the minutes it takes to play it, the author managed to interject some surprising ideas about the mindset of the protagonist -- things that I did not expect or consider but which are immediately obvious when pointed out, things which demonstrate that the author has put some time and effort into crafting the fictional world created. (Spoiler - click to show)I especially like the way some of the ideas are revealed through characterization; the response to "mirror" in the exercise room packs a lot into a few words. The short plot and ambiguous ending practically beg for a more thorough exploration of this fictional world.

This was the first work of the author's that I've ever tried, and it left me favorably inclined to try others. Worth the time if you are seeking a quick diversion.

This is the kind of speed IF that makes the whole idea worthwhile.

This particular competition (Speed IF Jacket 2) seems to have had a looser timeline than most, with license of up to a week given by the organizer and an IFMUD post indicating that entries were still being accepted a month after the official kickoff. I don't know how long Mr. Ashwell (who was the organizer) spent creating this work, but the original poem in the introductory sequence makes it obvious that Ugly Chapter is no rush job from a writing perspective.

This work quickly convinces you that it's going to be something very different and very good. In just a few short moves, Ashwell's masterful writing brings into focus the extremely inventive narrative framework he created in which to tell this story, while outlining enough features of the setting to show that he's invested some thought into making it all hang together.

There's a certain style of writing that I love, in which the author spends little or no time on formal exposition and instead builds up a picture through details. It's a difficult trick, but when done right, this literary pointillism gives the reader the vivid impression that he or she is looking through a window at a complete and consistent universe; the individual dots begin to merge into a coherent whole. Ugly Chapter pulls this off almost offhandedly, while it's busy snaring the player's attention with expertly crafted replies to the usual opening moves, replies that quickly make it clear that 1) this game will not have a "you" in in it in the conventional sense of IF, and 2) that won't reduce your enjoyment of the work one bit.

Ugly Chapter is an excellent use of the interactive fiction medium, conscripting even the parser interface into the service of making clear what's happening as the story unfolds. Once the method by which this story is ostensibly being conveyed starts to sink in, the player is quickly railroaded to the conclusion(Spoiler - click to show), before the novelty of the reader/player simultaneously experiencing "being" both the trapped protagonist and the pathos-inspiring narrator wears off.

I would not qualify this piece as a comedy, it's more like poetry. Perhaps what's most remarkable is the way that this work so dramatically exceeds the threshold of expectation set by Speed IF Jacket 2's structure: Authors were given a set of fictional, out-of-context blurbs -- each created by a different participant and given to one other -- and were supposed to create a work to which they would apply.

It's an interesting variation on the random-seed-ideas premise; instead of X components, authors are given X perceptions. As you might expect, many blurbs were silly. A silly piece in response would be entirely expected and appropriate. A story of this quality in response is astounding; Ashwell makes the pretend blurbs seem silly in an entirely new way.

Without knowing the development time, it's hard to say whether this should truly be considered speed IF. Either way, I'm glad I didn't miss it.

After reading the fake newspaper provided as a virtual feelie for The Weapon, I was already hooked by the work's fictional universe and eager to see what the story would be. A few turns of experimentation showed that the protagonist had an interestingly different internal monologue, while the fairly convincing NPC who is your main antagonist provided some clues to the situation at hand. Sean Barrett's expert writing subtly (and, if need be, directly) clues you in that this will be a game of cat-and-mouse, that you will be the one providing the misdirection alluded to in the tagline.

At the point where the NPC asks you her first question, I took a cue from the protagonist's apparently close-mouthed nature and tried the command "nod". It was tremendously pleasing to see a realistic response. After the number of clunkier pieces I've reviewed lately, it was refreshing to see a work composed with such forethought and attention to detail.

I won't go into the details of the game, but this was definitely the best "hard SF" piece that I've played since Infocom's Starcross. As with Starcross, the logic of the puzzles was grounded in realism and did not require any feats of mind-reading to solve. In fact, one of the most remarkable aspects of this piece is the number of well-crafted puzzles that the author, Sean Barrett, manages to wring out of the relatively few moving parts implemented. It's like a haiku -- all the non-essentials are stripped away, and what's left really works.

The flipside of this is that the interaction lacks some of the meatiness that would be welcomed in such an intriguing game world. I found myself wishing for the ask/tell model of conversation just so I could pump Cheryl for information about the things mentioned in the feelie.(Spoiler - click to show) While the ending does not leave room for a sequel, I would have been very interested to see another story written in this setting. On the whole, however, I think Mr. Barrett's sense of balance is exactly right; more details might simply have diluted the experience and reduced the level of focus the current writing inspires. It says something about how engrossing I found The Weapon to be that I had nearly reached the end of it before I realized it was going to be a one-room game.

The Weapon took most of an evening of on-and-off play to complete; total length is probably about right for the IF Comp, though it seems this piece was not entered when it was released in 2001. While it made finalist for Best NPC and Best Puzzles in the 2001 Xyzzy Awards, it did not win in either category.

I teetered back and forth between 3 and 4 stars for this and ultimately decided on 4, on the grounds of its exceptionally thorough implementation, nearly frictionless gameplay, and memorable characterization and story. This is a great introductory piece of IF for sci-fi lovers, and I would heartily recommend it to anyone who likes the genre.

The first speed IF competition emerged as a sort of spontaneous affair, it's genesis on IFMUD (preserved for all time over at IFWiki) looks a lot like a transcript from "Whose Line Is It, Anyway?" Beginning with the ridiculously short development timeline of 15 minutes, it was extended in stages to two hours, at which point David Cornelson, the inventor of the concept, released Coffins. [edit: Yikes! It has been gently pointed out to me that Christopher Huang is the author of Coffins, as should have been obvious to me based on what I linked to above. That's what I get for writing while too tired.] It was the only submission.

This seminal moment might have passed unnoticed, but, about 4 weeks later, on the eve of Halloween 1998, Cornelson organized another challenge like it, and a new phenomenon in the world of IF began to take root. Dan Shiovitz participated in this event, now known as Speed IF 2, and he was one of three people other than Cornelson [edit: Again, that should read "Huang", not "Cornelson"] to submit a finished work.

This piece, with its ridiculously long title, reads like a kind of gleeful, drunken attempt to make up a ghost story on the fly while sitting at the campfire after a long day of hiking, sun, and beer. It's silly, and it's fun, and it's a good time, but it's hard to call the result a story. Nonetheless, it made me laugh, and it only takes a few minutes to play, so I'd recommend it to anyone on the grounds of its historical and comedic value.

Since I don't share Dan Shiovitz's dismay over beholders, I thought I'd give Sparrow's Song a try. Having never experienced the work of J. D. Berry before, I was pleasantly surprised by the overall quality of this piece, which was entered into Emily Short's SmoochieComp in 2001.

Although the presence of the beholder implies the story is grounded in the universe of Dungeons & Dragons, nothing else does. While it was interesting to see what Berry thinks the personality of one of these iconic monsters is, there was no compelling reason I discovered that the being in question had to be a beholder. For story purposes, it could just as easily have been a demon, or even a grizzled old veteran. It's a rare and unexpected failure of originality in this otherwise highly creative work.

The writing often has a certain poetic and lyrical quality to it that I found compelling, though on occasion the similes were a bit forced. The author has a way of adeptly conjuring huge swaths of history and exposition by sending your imagination soaring along suggested lines. The universe feels more complete by virtue of what you imagine being unchallenged by the text, which actually provides very little information about the world the protagonist inhabits.

When I first finished Sparrow's Song, I was a little confused. It seemed like much of what was implemented in the first half of the story had no relevance to either the central plot or the theme. For a while, I speculated that maybe this was a partially-finished work that had been adapted for entry into SmoochieComp by grafting on a storyline about love. However, on further reflection, I decided that this may not be the case(Spoiler - click to show): Each NPC you meet presents an exploration of love in some form: dead love, love of mankind, simple fidelity, pure lust, etc. Not a very deep exploration, it's true, but I'm willing to give Berry the benefit of the doubt.

One intriguing aspect of the story is the way it ends.(Spoiler - click to show) Having met your apparent soul mate, you discover that she is a different species and you are not biologically compatible. There are three possible solutions to this: either you change to her species, you change her to yours, or you meet half way. Each option is available, but the significance of the choice is not explored, though each would likely have serious consequences in the protagonist's universe.

This work leaves some key questions unresolved. As Emily Short notes, the nature of the love that forms the foundation of the story arc is strangely anvil-like, to say the least.(Spoiler - click to show) Personally, I thought it was strongly hinted that it was an unnatural, magic-induced kind of supercharm -- we know charms exist because of interaction with the nymph, that Tamta has been studying magic, at least one of Tamta's responses (I thought it was to "magic!", but I can't seem to recreate it now) has her explaining that she'd hoped to "set love in motion" using magic, and in another she admits to summoning the titular sparrow. In addition, Tamta has clearly been aware of you for some time, and it seems from the locket that your sister, a powerful magician, had a hand in your destiny here. I would imagine that much of the reader's opinion about the overall story would be shaped by the particular conversational topics they'd come across -- pretty good use of the medium, in my mind.(Spoiler - click to show) Another glaring question: What's up with the combinatorial explosion as a manipulable object? Amusing as the concept is, it doesn't fit the rest of the style and has no apparent purpose in this work. Maybe it should have been saved for another setting?

The conversation warrants a brief note. Opinions about it seem to be mixed, but I, for one, found the liberation from having to type "ask person about" in front of every topic to be quite welcome. Other than that, there is little functional difference between this model and the standard ask/tell. Although at least one reply seemed to indicate the system was designed to allow the spread of knowledge about topics between NPCs via talking to them about it, I did not spot any differences in behavior as a result.

I would definitely recommend trying this piece, though first-timers may be frustrated by the attention to detail necessary to get past the primary obstacle.(Spoiler - click to show) Hint: Mantras are for repeating.