Tag: graham nelson

Temple of Kaos by Peter Gambles [Comp03]

IFDB page: Temple of Kaos
Final placement: 15th place (of 30) in the 2003 Interactive Fiction Competition

Much to my dismay, Temple Of Kaos has nothing to do with Maxwell Smart or Agent 99. I mean, sure, getting permission from whoever owns the rights to the show would probably be an insurmountable hurdle, but legal problems aside, wouldn’t Get Smart make a fantastic IF milieu? The Shoe Phone, the Cone Of Silence… I can just picture it. This Temple of KAOS, however, isn’t the stronghold of a nefarious organization of evil spies whose efforts must be thwarted by the agents of CONTROL, but rather a bizarre otherworld, where rules of time, space, and spelling (it’s called KAOS for no discernible reason) don’t apply.

Basically, the two salient features of this game are its disregard for making sense, and its propensity to express itself in verse, sometimes free, sometimes blank, and usually with end rhymes. As such, it’s a highly experimental game, and while I think both of the experiments fail in this instance, they illuminate some remarkable territory along the way.

Let’s tackle the nonsensical part first. In the ABOUT text, the author states that part of his intention with the game is to “interfere, out of sheer mischief, with some of the normal perceptions / causal relationships of IF space-time.” Mission accomplished, and in some parts of the game, the technique works well. The first section in particular contains a puzzle which utterly confounds standard expectations of how the world ought to work, but it’s possible to figure out the alternate system of reality at work in the puzzle, and thereby defeat it. The process of doing so is really fun, reminiscent of the flavor of The Gostak or For A Change. More specifically, the reason the puzzle works is that even though the PC’s actions don’t produce the expected results, they do produce some results, and from these results it’s possible to deduce what’s really going on. The same can’t be said of most of the other puzzles in the game.

Even for IF set in a much more mundane universe, feedback design is one of the toughest parts of puzzle creation — you don’t want to be so obvious that the puzzle becomes a non-puzzle, but your feedback also mustn’t be so obscure (or nonexistent) as to leave the player shaking her head in confusion even when the solution is revealed. Most of the puzzles in TOK err on the latter side of this line. I think that for every puzzle after the first one, I looked at the hints, and for most of them even the hints were insufficient. (Thankfully, the author provided a walkthrough.)

For some puzzles, the solution made a tortured kind of sense once I’d looked it up, but for many, I found myself just following the walkthrough’s instructions with a shrug. Sufficient feedback is very important in any IF puzzle, but in a world where the normal rules don’t apply, feedback becomes utterly crucial — how are we supposed to figure out the rules without the ability to gather any evidence about them? TOK usually (though not always) fails to provide enough feedback to make its puzzles solvable, which takes a lot of the fun out of playing.

What does provide some fun is the game’s tendency to present its room and object descriptions in a shaky kind of poetry. For instance, the first room description:

In the North Chamber

Chamber of the north, so empty, still, all noise grates
Black as night the chest your thought awaits.
The other chamber southward lies
Cloaked in mystery's disguise.

Most, but not all, of the game’s verse rhymes like this — sometimes the lines lack rhyme or even consistent meter. Moreover, there’s a fair bit of prose mixed in, as conversation, library responses, or descriptions of action, and the presence of these rather ordinary bits of writing juxtaposed with the more elevated verses tends to drain the effectiveness of each. The other problem with the poetry is reminiscent of what happened in Graham Nelson‘s final game, The Tempest. That is, it’s tough enough to craft IF prose that communicates clearly and concisely, and that also provides enough information to the player, but to do so in verse is much, much harder. TOK‘s poetry isn’t at as great a disadvantage as The Tempest, which forced itself to use prewritten lines as room and object descriptions, but it can still be rather opaque.

Usually the lines aren’t pure gibberish, and they sometimes even manage to pack a few clues in, but nevertheless it does take some time to translate, for instance, “Black as night the chest your thought awaits” into “There’s a black chest here.” The poetry technique is ill-chosen in combination with the game’s nonsensical laws of time, space, and causality, since either one by itself is confusing enough but together they can be utterly impenetrable. However, TOK does give some glimpses of how compelling an IF game in pure verse could be, and of how fascinating it might be to play in a universe with a completely different set of basic rules. Play it for these glimpses, but don’t be afraid to reach for the walkthrough.

Rating: 6.5

The Fat Lardo and the Rubber Ducky by Somebody [Comp03]

IFDB page: The Fat Lardo and the Rubber Ducky
Final placement: 29th place (of 30) in the 2003 Interactive Fiction Competition

Call this game “Insultatron.” Its purpose is to insult you in as many ways as possible, though not with a great deal of creativity. If that sounds like fun to you, than you’ll probably love the game. If not, then you’re like me.

Well, actually, there’s a minute or two of fun to be had. I kind of enjoyed the way the game got more and more exasperated with describing the setting, and finally just gave up on the whole thing. Also, a couple of the library default replacements were a bit funny, though most were just dumb and vile, sometimes extremely vile, so searching through for the funny ones isn’t a very rewarding activity. It is a bit amusing to see the genteel Graham Nelson library responses poking through on occasion — they sound very odd in this context.

In the end, this game is pretty dull. Actually, it’s pretty dull all the way through. Also, insults don’t really carry the same punch when they’re misspelled. But at least the game knows it’s stupid. Doesn’t that count for something? Actually… no.

Rating: 1.8

About the Infocom >RESTART Reviews

>INVENTORY started as a pandemic project. I’d known for a long time that I wanted to get my many comp reviews, and various others, off of my student website, but it wasn’t until the spring of 2020 that I found myself with the time and motivation to get this site started. My son Dante was 14 at the time, and all these new reviews, brought into the light, piqued his interest.

So he started reading, and learning about the 1990s IF cast of characters — Graham, Zarf, Rybread, and so forth. He also learned about IF history as it stood up to that point, and in particular how Infocom loomed large for all of us at that time. We’d talked about Infocom before — in fact, when he was five we played Zork together for about 45 minutes, resulting in much cuteness.

Meanwhile, revisiting those old reviews started to give me a hankering to spend some time in the Infocom worlds again. So I decided to replay some Infocom games, and Dante decided he’d like to join in. Because we (and a whole lot of IF-ers) started with Zork, I thought that’s where we could restart. I listed out what I think of as the 9 Zorkian Infocom games:

  • Zork I
  • Zork II
  • Zork III
  • Beyond Zork
  • Zork Zero
  • Enchanter
  • Sorcerer
  • Spellbreaker
  • Wishbringer

Then, to make it a nice even list of 10 games, I added Moonmist, more or less at random. It was a game I’d never finished, it seemed like it was going to be on the easier side, and it had a little historical significance, apparently, for being one of the first games featuring a lesbian character. Dante is an LGBTQ+ activist, so I liked that connection, though as it turns out the depiction is very slight indeed.

Even before I embarked on this replay project, Dante had been exploring newer corners of the IF world — Lock & Key, Counterfeit Monkey, Steph Cherrywell’s games, and some others. So he was familiar with the basic idiom and mechanisms of these games. Essentially, he was right about where I was at his age in 1984, except that his primary text game experiences had been with 21st-century interactive fiction. Plus, he’d been playing video games of all sorts pretty much since he could talk, as opposed to me whose only other video gaming came at the pizza parlor, skating rink, or occasional arcade. Oh, and those friends’ houses lucky enough to contain an Atari 2600.

A vintage Infocom advertisement, with an image of a brain and the caption "We unleash teh world's most powerful graphics technology".

So our Infocom odyssey was a combination of me revisiting childhood memories, with dim recollections of puzzles and landscapes, and him seeing these vintage games through fresh eyes, his expectations shaped by a far more evolved version of text games and computer games in general. I’m still the faster typist between us, so I sat at the keyboard and read aloud, while he directed the action. We transcripted all our interactions, so that I could remember how they went when I wrote the reviews. We also used the invaluable Trizbort to map our progress, generally starting out with the automapping and then inevitably abandonding that when some mazy thing confused its relatively simple algorithm.

If I remembered a puzzle’s solution, I’d try to keep my trap shut and give him the pleasure of solving it for himself, though sometimes if we crossed the line between fun flailing and ragequit flailing, I might drop a subtle hint. More often than not, I didn’t remember the puzzle either, so we could genuinely collaborate on solving it. When we got really stymied we’d turn to the invaluable .z5 Invisiclues at the Infocom Documentation Project, but that wasn’t terribly often.

So as I write about these games, I’m writing about that experience. I’m not trying to write the definitive history of an Infocom game — for my money Jimmy Maher has got that territory 100% nailed down. Instead, I’m presenting an idiosyncratic and personal account of how Dante and I experienced those games — how I felt upon returning to those oft-trod trails and how Dante’s insights illuminated them for me like a trusty brass lantern.

We started Zork I on August 5, 2020, and finished Moonmist on December 20. Given sufficient time and interest, there may be more to come! Note that all of these reviews will be spoiler-laden — they aren’t written to promote a game but rather to analyze an experience, so I won’t shy away from getting specific.

Wrecked by Campbell Wild [Comp00]

IFDB page: Wrecked
Final placement: 39th place (of 53) in the 2000 Interactive Fiction Competition

There are several points in Wrecked where the game collars you to proclaim just how awesome its development system is. For example, you meet someone who (surprise surprise!) just happens to be coding an ADRIFT game on a nearby computer. Ask her about it, and she’ll say to you, “I’m making an ADRIFT adventure. I’ve tried using Inform, TADS and Hugo, but I’d say ADRIFT is by far the best.” In another location, you can gain some points with the command “write graffiti,” something I would never have thought to do without the handy walkthrough to prod me. The graffiti the game chooses to write? “ADRIFT rocks!”

Apparently, Wrecked suspects that its own merits are not enough to convince you of ADRIFT’s supremacy, but that if it just shouts slogans at you once in a while, that might do the trick. For me, the former was true, but the latter, predictably, was not. I’ve already catalogued the shortcomings of ADRIFT in my review of Marooned, so I don’t see the need to rehash them here — the bottom line is that ADRIFT isn’t a bad system overall, and has some nifty features to recommend it, but its parser (which is MORE IMPORTANT THAN NIFTY FEATURES) is substandard, its model world needs work, and it’s still lacking in key functions like UNDO and SCRIPT. A random NPC might think it beats Inform, TADS, and Hugo, but a quick conversation with this NPC demonstrates that her powers of discernment are, after all, rather limited. The game’s self-hyping moments are offputting, as it would have been if Graham Nelson had chosen to have “Inform RUELZ!” scribbled on the side of the house in Curses, or if the spaceship in Deep Space Drifter had been named the USS TADS Is Supreme.

On the other hand, Wrecked is definitely a better showcase for ADRIFT than is Marooned. Those extraneous newlines that I blamed on the ADRIFT system in my review of Marooned turned out to be that game’s doing — they’re nowhere to be found in Wrecked. Many more first-level nouns are implemented, making the auto-complete option work much better, though it still doesn’t work flawlessly. Also, there’s no starvation puzzle in Wrecked, which sets to rest my fears that such a puzzle is standard issue in every ADRIFT game.

However, just being a better game than Marooned doesn’t make Wrecked a great game in itself. One part of the reason why I didn’t care for Wrecked is that it just feels very dated to me. It’s an old-school adventure, something that might have fit comfortably into the mainstream circa 1983 or so. You know the kind: you find a bowling ball with a button on the side, and when you push the button, the ball opens up to reveal a sapphire bracelet, which you then give to the sailor on the dock, who will reward you with a chicken pot pie that you can feed to the vicious warthog, allowing you to sneak into his lair and retrieve the bag of marbles, etc. etc. Everything is pretty much thrown together without any rhyme or reason, loosely grouped together under a threadbare rubric of plot and setting. Like I said, old-school. Unfortunately for Wrecked, the old school of IF lost its accreditation some time ago. To my mind, senseless grouping of stuff without any indication of internal consistency is something IF has outgrown, like mazes and starvation puzzles. Seeing it in a year 2000 competition entry isn’t going to score a lot of points from me.

However, even if I were willing to set aside the deep flaws in both the parser and the design of the game, there would still be the matter of the bugs. Most severe among these is the game-killing bug I encountered about an hour and 45 minutes into the game: despite all conditions being correct, I was unable to complete a critical puzzle, even though I knew from a previous play session that it was possible to complete this puzzle. Because ADRIFT makes a habit of overwriting old save files with the current save unless you explicitly tell it to do otherwise (by selecting “save as” from the menu bar — typing “save” will overwrite without prompting), I would have had to start from scratch and wind my way once more through all the nonsensical contortions required by the game’s plot, and there was no guarantee that I wouldn’t encounter the same bug again.

That bug ended my dealings with Wrecked, but there were other errors along the way. The voice was in first person, but would occasionally slip into second person. Sometimes the game failed to recognize rather important objects. In one supremely frustrating section, the game adamantly refused to recognize the word “keyhole,” despite a promiently featured keyhole in the location; it responded to all commands along the lines of “put key in keyhole” with “I can’t put anything inside the small key.” In short, between the bugs, the parser, the hype, and the lack of any kind of logic, Wrecked wasn’t a lot of fun, and it’s not likely to win many converts to ADRIFT. No matter how many times it insists that ADRIFT rocks.

Rating: 4.0

Asendent by Nate Cull and Doug Jones as Sourdoh Farenheit and Kelvin Flatbred [Comp00]

IFDB page: Asendent
Final placement: 51st place (of 53) in the 2000 Interactive Fiction Competition

It’s the little things in life that help me keep my sense of irony. Like this: right after I finish a game that pays tribute to Graham Nelson, I get this game, which is apparently a tribute to Rybread Celsius. A tribute to Rybread Celsius. The world never ceases to baffle me. As I’ve written before about Rybread, he seems to have a devoted cult of followers, but I’ll never be one of them. I guess I’m just old fashioned enough to like my games with error-free prose and code, and I also sort of like them to, y’know, make some kind of sense. Asendent is, if anything, actually worse than anything Rybread ever produced. Certainly the spelling is worse, especially compared to the later Rybread (see L.U.D.I.T.E.) The code is also quite horribly buggy, though it thankfully leaves the debug verbs available, so players can be sure they’re not missing anything.

As with Comp00ter Game, Asendent looks like it might have some point to make, but just like Comp00ter Game, that point was lost on me. To me, it just seemed like a really horrible game. What’s the point of producing such a thing, especially on purpose? The intro seems to suggest it’s hallucinatory, and Rybread games certainly are that, though they don’t tend to trumpet the fact themselves. But it’s not the terrible spelling that makes them hallucinatory. It’s the imagery. Asendent can’t compare to a real Rybread game when it comes to startling images, and its imitation seems pale indeed. The purpose of its imitation is a mystery. A tribute to Rybread Celsius. People are so odd.

Asendent took me about 10 minutes, at the end of which I shook my head and got ready for the next entry. Hey, just like a real Rybread game!

Rating: 0.8

Letters From Home by Roger Firth [Comp00]

IFDB page: Letters From Home
Final placement: 12th place (of 53) in the 2000 Interactive Fiction Competition

Graham Nelson once described interactive fiction as “a narrative at war with a crossword.” Letters From Home takes a definite side in this battle by being an interactive narrative where the main goal is to complete a crossword, and whose entire purpose is structured around puzzle-solving, the “crossword” part of the metaphor.

The explicit connection with that metaphor is just one of the many pieces of Nelsoniana scattered throughout the game. From the introductory text, to the Jigsaw (grandfather clock and Titanic mementos) and Curses (sprawling mansion filled with relics of distinguished ancestors) references, to the somber traces of wartime, the whole thing comes across as a loving tribute to Graham. Being a Nelson admirer myself, I couldn’t help but be impressed by the various clever nods to him peppered throughout this game. There’s also a hilarious Zork allusion in a throwaway parser response and even a passing reference to the author’s own Cloak Of Darkness demonstration page for the various IF languages.

The main attraction in Letters, though, is the puzzles. This is one of those games whose plot is thin to nonexistent, and whose mimesis gets shattered (literally) in the course of puzzle-solving. The game isn’t particularly straightforward about announcing what your objective is supposed to be, but it comes clear after a bit. At first, Letters seems to be a standard-issue “collect your inheritance by solving puzzles” game a la Hollywood Hijinx, but the plot and the mimesis both evaporate rather quickly as it becomes clear that the real point of the game is collecting the letters of the alphabet by finding things that represent or resemble them in some way.

For example, you find a cup of tea, and sure enough, it represents the letter T. Once you get the hang of it (hint: leave your sense of realism at the door), most of these puzzles are fun, and a few are quite remarkable. Some, though, are marred by ambiguous writing. For example, one of the necessary objects is described as stuck to a skylight. Perhaps because of architectural styles where I live, I don’t expect that I’ll be able to reach up and touch a skylight — they tend to be placed in high ceilings. Consequently, I thought that the puzzle was to find a way to reach this object — I climbed stuff, searched for a ladder, tried to haul furniture into the room, all to no avail. Finally, I turned to the hints, which just said to… take it. I did, and it worked.

Now, part of the problem here was no doubt my fault: I should have just tried taking the item. However, I’d submit that if you’re writing descriptions (especially terse descriptions like those in this game) where critical puzzle pieces depend on how the player envisions the room, there had better be a lot of clues in place to make sure that you’re communicating clearly. Letters From Home sometimes fails to do this.

I didn’t finish the game in the two-hour judging period — no great surprise since I’m guessing there are twenty-six letter puzzles, some of which require multiple steps. In addition, there’s a time limit, which I blithely exceeded. So I don’t know much about the ending, and probably missed half the puzzles. I doubt the ending has much of a punch — there’s virtually no narrative in this game, and solving the puzzles is its own reward. As for the half I missed, if they’re anything like the half I found, I’ll bet they’re a lot of fun, though occasionally needlessly frustrating.

Letters was coded quite well — I only found one bug, though a rather amusing one. The game’s time limit is 12:00 noon, and it creates atmosphere by having the village chimes toll on the hour. However, once it gets past noon, the chimes toll thirteen times, then fourteen times, and so on. The funny thing is, the game is so unrealistic that at first I didn’t even notice the oddness of the extra chimes. In a world where everything keeps turning into letters of the alphabet, and abstract concepts like letters can be carried around in your inventory, what’s a little extra chiming?

Letters From Home is a fun, lexicographically oriented puzzlefest that needs a bit more work on writing and coding before it can reach the Nelsonian level to which it aspires. This review has been brought to you by the letters “G” and “N”.

Rating: 8.2

Enlisted by Greg Barry [Comp00]

IFDB page: Enlisted
Final placement: 23rd place (of 53) in the 2000 Interactive Fiction Competition

Enlisted, a military adventure with a Star Trek streak, imagines a Space Force that functions a bit like the French Foreign Legion reputedly did — as a last resort for people in desperate circumstances who need to escape their lives. The PC, fresh from an intertwined bankruptcy and divorce, certainly fits this category, and from the outset Enlisted gives its space Navy a distinctly authentic feel. There are still forms, though they’re now in electronic format. There are still humiliating medical exams, though now those exams are automated and high-tech. And there are still unpleasant surprises, like finding out that the length of your tour of duty is defined by how long it feels to you — the time you sleep away in cryogenic fugue doesn’t count. From the captain’s mission briefing speech to the endless, identical corridors of your ship, Enlisted creates a very convincing world.

Granted, there are a number of flaws that hinder the feeling of immersion — the writing often feels awkward, and is sometimes burdened with errors. In addition, there are still some bugs left in the game, as well as some basic errors like listing incorrect information about exits from a location; overall, Enlisted feels like it still needs one more attentive round of proofreading and debugging. Nonetheless, though I can’t claim a lot of personal authority on the subject, having never served in the military, the whole thing still just feels right. It captures the sense of being processed by a giant, bureaucratic system, as well as the excitement of setting out on a mission, encountering unexpected dangers and crises, and solving those problems. It’s not mimesis, exactly — a number of things are abstracted away in the name of high-tech — but the objects, settings, and situations felt genuine.

The problem is that genuineness isn’t always a virtue. Certainly, I was delighted when I encountered the other enlistees (“They look uncomfortable in their stiff and shiny uniforms and are mumbling amongst themselves.”) and the bevy of governmental-sounding acronyms at every possible location, but I was very disappointed by some of the things that the game chooses to display realistically. In particular, I’m thinking of a puzzle that requires you to travel outside the space station in an EVA (Extra Vehicular Activity — told you there were acronyms everywhere) suit. Using commands like “turnr” (turn right), “roll” (forward roll), and “lthrust” (low thrust), you must painstakingly maneuver the suit to a variety of locations based on x, y, and z coordinates.

I went through stages with this puzzle. At first, it baffled me completely — I ended up dozens of units away from anything, and totally unable to stop myself or correct my momentum. Then, after a restore, I started to get the hang of it, and thought it was amazingly cool. Once I had a mental picture of how the PC was traveling on x, y, and z axes, how turning and rolling could alter its orientation with regard to these axes, and how I could start and stop by turning and thrusting, it was fun and exciting to get myself maneuvered to the first place I needed to go. Then, when I realized that I’d need to go through this laborious process something like five more times, I started to get really annoyed. What started out as fun very rapidly devolved into tedium, and not only that, messing about with the EVA took the lion’s share of my 2-hour playing time, so much so that I didn’t even come close to finishing the game, despite typing straight from the walkthrough for the last half hour.

The more games I review, the more importance I place on one particular rule from Graham Nelson‘s legendary “Players’ Bill Of Rights”: “Not to have to do boring things for the sake of it.” The EVA suit stuff from Enlisted felt quite realistic — probably, traveling in a space suit via a backpack thruster and positioning system would be just as fiddly and drudging as the game makes it seem. However, reproducing this process does not make for enjoyable interactive fiction. As with regular fiction, we don’t expect to have to sit through the boring parts of an adventure, even though realistically there would probably be many of those. This puzzle would have been excellent if, for example, the player needed to use the manual turn/thrust method to reach the first target, and that target had contained an autopilot module which allowed the rest of the EVA stuff to be done automagically via a Starcross-ish command like “SET X TO 2. SET Y TO -2. SET Z TO 0. START AUTOPILOT” Instead, we have a few minutes of excitement and then long stretches of painful and tricky mucking about. If I wanted that, I’d have joined the real Army.

Rating: 6.7

Chaos by Shay Caron [Comp99]

IFDB page: Chaos
Final placement: 19th place (of 37) in the 1999 Interactive Fiction Competition

Most interactive fiction games use the second person voice, and make it clear from the outset that this is their mode. Think of “You are standing in an open field west of a white house,” or “You are Primo Varicella.” Chaos appears to follow in this tradition, describing a character named Captain Chaos but using the second person form of address several times in asides like “You know what I mean” or “you guessed it.” Admittedly, the “I” in the first phrase throws a bit of a spanner into the works, and a player might well have cause to wonder who the “I” is that’s apparently speaking. The parser? The author? Some sort of in-game narrator? For me, though, it went by so fast that I allowed myself to suspend that question. From the introduction, I presumed I was Captain Chaos’ sidekick, there to help him with a sudden power failure on his jerry-built hovercraft. But then I typed in my first command, and this is how it went:

> I

Chaos has a Evil Overlord list.

What? But what’s in my inventory? After a few commands, I slowly began to understand that the game was responding to my commands as if they were guiding Captain Chaos himself, then describing the results referring to the Captain in the third person — “Chaos walks south”, “He picks up the screwdriver,” etc. What’s more, from time to time the Captain Chaos character will offer some commentary on the command chosen, relating tangential or backstory facts about the parts of the environment he encounters while being guided by the player’s commands. The more of this that goes on, the more prominent one question becomes: Who is the PC of this game? Apparently the introduction was addressing me — me the player, not some avatar within the story with whom I am expected to identify. And who is Captain Chaos addressing with his asides? Again, it’s the player. In a real sense, the player is the PC in Chaos. You, the player, control Captain Chaos with your commands, but he is aware of your presence, at least enough to make the occasional remark to you. And if all that’s not complicated enough, wait until he finds (or you find, or something) the technology that allows him to control another entity remotely.

This is all rather haphazardly done in this particular game, as evidenced by my confusion at the first few prompts. I found myself bumping into unexpected forms of address, and having to puzzle out exactly what was supposed to be happening, or at least what it seemed like was supposed to be happening. Moreover, many of the questions raised by these narrative choices, such as those I mentioned about the use of “I” in the introduction, are just never answered. In fact, there is no announcement of any kind — subtle, blatant, or otherwise — that Chaos will overturn a fundamental IF convention, and the result is a rather jarring feeling of displacement. The creation of this feeling doesn’t really seem to serve the story, at least not in any specific way I could determine.

Nonetheless, I found it quite interesting. I was reminded of other competition games which have fiddled with the narrative voice, such as Christopher Huang’s Muse and Graham Nelson’s Tempest. Both of these games took a slightly different approach, having the parser itself take on a character, speaking to the player in the first person and executing the player’s commands as if they were that character’s own actions. Tempest even complicated matters further by explaining that its player’s role is as “the magical will” of Shakespeare’s Prospero, guiding Ariel (the parser’s character) through the various scenes of the play. These tactics have a bit of a distancing effect on the player, setting identification at one remove and shifting the action from the player character to the parser character. Chaos, though it explains nothing of its strategy, actually creates one further remove by allowing neither a player character nor a parser character but another character altogether to be the focus of the action. Yet when this third character (third person, you might even say) speaks outward in the second person voice, it addresses the player (in a “Dear reader” sort of way) and brings the game and player closer together than almost any other IF I’ve seen.

Orchestrated strategically and used creatively, these techniques could make for a masterful, groundbreaking work of IF. Chaos isn’t that work, but its experimentation does open up some very interesting, and mostly unexplored, territory. Beside this, the plot of the game seems quite inconsequential. There’s a ship to be repaired, and various puzzles to solve, some required and some optional. These puzzles are decent, and the writing is passable, and although there are a number of coding problems, the game is at least finishable. It’s a bit of a throwaway, though, a mediocre competition entry except for the unique approach it takes, almost offhandedly, to forms of address in IF. I enjoyed thinking about Chaos more than I enjoyed playing it, but if the author’s next game explores the techniques employed here in a consistent, systematic, and clear way, the result will be well worth a few false starts.

Rating: 6.6

Erehwon by Rick Litherland as Josiah Pinkfoot [Comp99]

IFDB page: Erehwon
Final placement: 11th place (of 37) in the 1999 Interactive Fiction Competition

Erehwon reminded me of a Saturday Night Live skit I saw years ago. I don’t remember the details very well, and no doubt somebody will step in to correct me, but the basic premise was something along the lines of a group of people who wrote a numbered joke catalog, and when they’d get together for their annual convention, they’d just sit around and say things to each other like “Hey, number 534!” and then roar with laughter. Wandering through Erehwon, I felt like an outsider at that convention. There were plenty of inside jokes, some of which seemed to be oriented towards residents of the U.K., though of course, I couldn’t tell. Even the walkthrough would occasionally say things like “If this doesn’t mean anything to you, don’t worry about it.” OK, whatever. But it wasn’t even so much the inside jokes that made me feel like an alien visitor as much as it was the heavy emphasis on mathematics and geometry. For me, a game that says “the dual of a Platonic solid!” means about as much as a game that says “Hey, number 534!”

Erehwon seems to make a basic assumption that the player will find things like dodecahedrons and Hamiltonian circuits interesting, and that assumption led me to suspect strongly that I’m not part of the target audience for this game. Am I confessing to some sort of failure to reach the proper heights of geekdom here? (And I mean “geek” in the positive sense, let me hasten to add.) I know a lot of IF devotees approach it from the Computer Science side, and could sit endlessly enraptured in discussions of, say, non-Euclidean geometry. I’m not one of them. I come more from the Lit. side, and could sit endlessly enraptured in discussions of, say, feminist theory and postmodernism. There is an appearance by Stanley Fish, the namesake of a prominent literary critic and advocate of a theory of reading which fits in particularly well with IF, but the game never gave much indication that it recognized the allegiance. Or if it did, it sailed over my head along with many of the other references. For these reasons, Erehwon underwhelmed me, not primarily through any specific fault of its own, I think, but just because we’re not a particularly good match.

However, I do have some complaints that stem specifically from my viewpoint as an IF player. Heading the list of these is a huge maze. Again, I recognize that this is probably my own prejudice, but I just don’t like mazes. I don’t care how mathematically cool they are — I still don’t like them. Now, in fairness, I must point out that the game does provide for a couple of solutions which obviate the need to map the maze. However, as a player I had no way of knowing that without reference to the walkthrough, and therefore ended up spending much of my first hour of Erehwon gritting my teeth and trying to map this giant maze. You might contend that I should have understood that mazes without alternate solutions are simply unacceptable in modern IF and looked harder for the alternate solution, taking it on faith that one existed. Maybe so, but I find that I can take very little on faith in comp games — after all, I would think that proper spelling and grammar would be de rigeur as well, but plenty of games lack those basic ingredients (not that Erehwon was one of them.)

Besides, the path to those solutions is blocked by the other problem puzzle in the game, a puzzle which echoes one that appears in Trinity, but enlarges it for no clear reason. The main problem with this puzzle is that it violates one of the basic tenets outlined in Graham Nelson‘s classic Player’s Bill of Rights: not to have to do boring things for the sake of it. Indeed, a winning session will involve several trips through this puzzle, each of which entails ten moves at the very least, and it’s not at all clear that the size of the puzzle adds anything positive to the game. Aggravating the situation, the puzzle also has a rather arbitrary solution, at least so far as I could tell, and following any other track will get you hopelessly lost, making the whole thing into the basic equivalent of yet another maze.

It’s clear that there is a crystalline and beautiful mathematical philosophy behind each of these puzzles, but for me as a player, the translation of those philosophies into interactive fiction was awkward and unsuccessful, an ambitious washout. Much the same could be said for an alternate mode of navigation with which the game experiments. I tried it for a bit, and indeed was forced to use it at a couple of points in order to solve puzzles (puzzles that seemed arbitrarily constructed to require the alternate navigation method), but avoided it much of the rest of the time. I did appreciate the irony, though: in most games, the objection to the compass rose approach to navigation is that you don’t have a compass. In Erehwon you actually do have a compass, but are nonetheless forced to abandon compass-rose navigation at several points. I thought that was pretty funny. Indeed, there are lots of funny moments in Erehwon, one of its main strengths being its humor. Most of the inside jokes were past me, but there were quite a few funny moments that required no special knowledge to enjoy. For instance, this exchange with the parser:

>N
North Boulevard

On both sides of the so-called boulevard (more of a dirt track) is an
impenetrable ferret.

>X FERRET
Did I say ferret? I meant forest. It's stoatally impenetrable.

As I laughed, I was reminded of some of the funnier moments in Hitchhiker’s Guide, where the parser momentarily rears up to take on a personality, using its trusted status as the reliable narrator to pull the rug out from under us and make us laugh at the same time. Those of you who’ve played Hitchhiker’s will know what I’m talking about. Those of you who haven’t: Hey, number 534!

Rating: 5.4

Spodgeville Murphy and the Jewelled Eye Of Wossname by David Fillmore [Comp99]

IFDB page: Spodgeville Murphy and the Jewelled Eye Of Wossname
Final placement: 25th place (of 37) in the 1999 Interactive Fiction Competition

The 1996 IF competition was won by a Graham Nelson game with the highly improbable name The Meteor, the Stone, and a Long Glass of Sherbet. Since then, every year we’ve had at least one entrant with a long, silly name. In 1997, there was The Obscene Quest of Dr. Aardvarkbarf and Phred Phontious and the Quest for Pizza. In 1998, we had I Didn’t Know You Could Yodel. And this year, David Fillmore brings us Spodgeville Murphy and the Jewelled Eye of Wossname. Is there a causal relationship here? Probably not. More likely, a long and goofy title allows the author to set up some basic expectations about the work at hand. In essence, titles like this say: “Check me out! Boy, am I wacky! Prepare to be taken on a zany and madcap adventure through an absurd universe!” However, the comparison with Meteor is instructive in the following way: having set up the above expectation, Nelson subverted it by using a silly and comedic scenario (riding an elephant next to an aristocratic airhead) as the entry point into what became a rather atmospheric and austere cave adventure. The surprise value of this shift lent strength to the sense of wonder that the game worked to impart. His successors, on the other hand, have struggled vainly to live up to the wacky promise of their titles, providing a few funny moments along the way but generally falling far short of the joy of coherent absurdity. Wossname, sadly, is no exception.

The game certainly does have its funny moments. Its introduction effectively parodies the genre of Enchanter, Beyond Zork, and Path to Fortune with lines like this: “Another champion must be sought; an idiot unskilled in anything but adventuring…” The title page pulled off a good joke by presenting the game with a dramatic flourish, crowned with a grand-looking box quote from Shakespeare, a quote which turned out to have no relevance at all to the game, and very little meaning in general. (“It is an old coat.”) Finally, typing “Zork” leads to one of the best easter eggs I’ve ever found in a competition game. Go on, try it — I won’t spoil it by trying to describe it. But for every funny moment, there were several more that just fell flat. The “full” score listing might have been funnier if not for the fact that last year’s Enlightenment did the same thing with much more panache. Several allusions to various sources (the Zork games, Indiana Jones) were so obvious as to belie any cleverness. Lots of other attempted jokes were just, well, not that funny, and little is more tedious than unsuccessful attempts at humor (as anybody who has watched a lame sitcom can tell you.)

Adding to this tedium is the fact that the game is plagued with a number of errors, both in writing and coding. Now, the writing errors were much less frequent, and many had to do with formatting — strange line breaks, random strings of spaces and the like. Misspellings and grammar errors were relatively few, though at one point the game does manage to misspell the name of its own main character. Coding errors, however, were abundant. For example, every time you climb a particular object the game dutifully reports that you clamber onto it, reprints the room description with additional information now available to you, then inexplicably protests that you’re already on the object. At another time, the ceiling falls in, but this cataclysmic event has absolutely no effect on anything sitting on the ground. “Drop all” just doesn’t seem to work. Most egregious, though, is the fact that the final puzzle hinges on an item which, as far as I can determine, is never mentioned in any description. I only found it accidentally, through the fact that the parser includes scenery objects in its response to commands like “get all”. I felt clever for solving the puzzle by tricking the parser, but it didn’t make me any more impressed with the game. What’s more, I spent the half-hour before that floundering around in circles, trying to figure out what in the hell I could possibly be missing. Normally I ascribe this sort of thing to lack of beta-testing, but the credits indicate that no less than seven people tested the game, so I don’t know. Perhaps the time it took them to read the title preempted their ability to test the whole game?

Rating: 5.2