Space Station by David Ledgard [Comp98]

IFDB page: Spacestation
Final placement: 19th place (of 27) in the 1998 Interactive Fiction Competition

Several years ago, Graham Nelson released a piece of work he modestly referred to as a “parsing exercise.” This exercise really was a short game, a competition-sized game before there was a competition. It included the spell system from Enchanter, and several good puzzles. In fact, it was very loosely based on the sample transcript included in Infocom’s original distribution of Enchanter. This game was called Balances, and it was a big hit with the IF community. It’s probably the most-played “exercise” in the IF Archive. It also spurred a discussion, which reoccurs from time to time, about what fun it would be to create games based on the sample transcripts from various Infocom games. Now, David Ledgard has been the first person to turn that notion into a reality. He took the sample transcript from Planetfall and (apparently with the permission of Activision) implemented it in Inform, also extending it a bit so that it would comprise a full, winnable game (the transcript ends with the player’s death.) Where Balances only took a couple of ideas from the Enchanter transcript, Space Station lifts the Planetfall transcript almost verbatim. Unfortunately, the results are a little mixed.

The transcript itself is great reading. It’s funny, interesting, and well-written. Consequently, the pieces of Space Station that are copied straight from the transcript are also funny, interesting, and well-written. This is not something for which the author can really take credit, though I’m certain it was a fair amount of work to do all the transcribing and implementing. Ultimately this section of the game occupies a rather shadowy realm of authorship, its text written by an Infocommie (one presumes Steve Meretzky), and its code implied by the written text, but the final code of Space Station was written by someone else, and while he certainly implemented it in the spirit of the transcript he also (of necessity, or from an enterprising spirit) added quite a bit of his own. The seams between the two parts of the game are sometimes all too visible. For example, a scene outside the space station’s window is described (in part) thus: “Through the large observation window, you see the milky way. Where the stars are scattered thinly, and the cold of space seeps in.” When I read that, I thought “Surely Meretzky didn’t write that sentence fragment!” I was right — he didn’t. It was a part of the game’s “extensions”, and the grammatical error grated quite harshly against the polished, accomplished prose in other parts of the game. Sometimes the problem was just as bad when the game didn’t extend itself — it was quite jarring to try a legitimate (included in the room description) direction and run into the terse reply “Unimplemented!” On the other hand, there were some very funny moments in Space Station, moments that I was sure were a part of the transcript but in fact were part of the extensions as well. It was an extra treat to find out that those parts weren’t authored by Infocom. The problem is that once any seams at all showed, the split between the transcript and the rest of the game was constantly on my mind, and grammar and spelling errors (of which the game has a few) felt all the more glaring because of it.

This is a cautionary tale for anyone who decides to implement one of the Infocom transcripts. The transcripts themselves are generally excellent, as they should be from a professional company which had the important task of explaining interactive fiction to a novice public. They are well-written and entertaining, with good settings and clever puzzles. To implement one of these transcripts so that it becomes a good game in its own right, you need a few things. You need to be able to write so well that nobody will be able to tell where the transcript prose stops and yours starts. You need to be able to make your sections of the game as entertaining as the transcript section. You need to be able to extend the setting of the transcript rationally, without introducing a foreign tone or feel. You need to be able to come up with puzzles that are consistent with those in the transcript, and are done as logically as the pre-written ones. If you can do all that, then absolutely write a transcript-based game (assuming you can secure Activision’s permission, of course). Then again, if you can do all that, why waste your talent on adapting transcripts?

Rating: 6.4

Persistence of Memory by Jason Dyer [Comp98]

IFDB page: Persistence of Memory
Final placement: 9th place (of 27) in the 1998 Interactive Fiction Competition

NOTE: Because of the nature of Persistence of Memory, it’s difficult to talk about it without revealing a key secret. Therefore, be warned that any and all of the following review could be considered a spoiler.

Memory is a new twist on the one-room game. The setting is war; could be Korea, could be Vietnam, but it’s never really specified, and it doesn’t really matter. It’s a war in a foreign land, with villages, dense foliage, helicopters, rifles, and land mines. Especially land mines. In the first move of the game, you step on one, and realize that if you remove your weight from it, it will explode. Thus the potential paths which the game appears to have at its outset are reduced to one: wait. This restriction of freedom is a recurring theme in Memory. In incident after incident, the scope of action contracts until it becomes clear that there is only one action which will lead to your survival. Sometimes these actions are rather horrifying, but the game demands them if you wish to finish. I have mixed feelings about this kind of forcible plotting. On the one hand, it makes for an extremely linear game, and it curtails interactivity quite dramatically. This obstruction seems to fly in the face of the conventional wisdom about IF — it violates one of the Players’ Rights in Graham Nelson’s Craft of Adventure: “To have reasonable freedom of action.” In Nelson’s words, “After a while the player begins to feel that the designer has tied him to a chair in order to shout the plot at him.” On the other hand, I also think that interactive fiction can be a very good medium for conveying a sense of futility or entrapment. Because IF by its nature seems to require at least to a certain degree freedom of movement and action, and because it also creates a sense of immersion in the story’s world, when a piece of IF chooses to violate that perceived requirement the player’s sense of identification with the trapped character can be very strong indeed. Something about the frustration of having so few actions available to me which would not result in death made the equation of my situation with the character’s feel more intense than it would have were I just reading a story about this character.

Because of the game’s premise, you don’t seek out the puzzles; the puzzles come to you. And each puzzle must be solved if the character is to survive. Luckily, all of the puzzles make sense and have intuitive solutions, though in some of them it’s not clear what the deadly moment is until it arrives, and sometimes I found myself resorting to a save-and-restore strategy in order to defeat a puzzle’s time limit. I don’t think I could have solved the game straight through, because some puzzles had rather unexpected and uncomfortable solutions. This is where I found myself ill at ease with the game’s lack of interactivity — there’s a fine line between identifying with a trapped character versus simply feeling trapped into an action because the designer allows you no other choice, even though more options might have been available in reality. It’s hard to explain without revealing more spoilers than I already have, but some pieces of the plot felt rather forced, as though only one solution was provided because only that solution would create the game scenario desired by the designer. However, the choices worked in the end, and I found I only needed to look at the hints once, and in retrospect I think I probably could have avoided that had I spent more time on the puzzle that was stumping me.

The writing could get a little histrionic at times. Some descriptions tiptoed along the line between what works and what doesn’t. For example, the mud around your feet is described as “torpid”, a word which usually refers to a sluggish mental state. I suppose the mud’s thickness and viscosity could be compared to slow mental processes, but it’s a stretch. There weren’t too many moments like this — for the most part the prose did a fine job of conveying the situation, and in fact sometimes was quite good indeed. The description of the hairs rising on the back of your neck as you try to conceal yourself from enemy soldiers was chilling and engrossing. I found no technical errors in the writing, nor in the code. Overall, Memory does a very good job with an unusual choice of subject matter, and when it was over I felt not triumph, but relief. I suspect this is what the game intended.

Rating: 8.3

Poor Zefron’s Almanac by Carl Klutzke [Comp97]

IFDB page: Poor Zefron’s Almanac
Final placement: 7th place (of 34) in the 1997 Interactive Fiction Competition

Right about the time that Poor Zefron’s Almanac (hereafter called PZA) starts feeling like another humdrum sword-and-sorcery game, it executes a nice surprising twist. To say too much more would be to give the game away, but the fact that the author bills PZA as “an interactive cross-genre romp” is a clue toward its direction. This twist made the game refreshing and fun again, especially after the frustration it caused me when I began playing it. More on that later. PZA does several things very well, one of which is its eponymous book, a tome owned by your wizardly master Zefron and left behind after his mysterious disappearance. This almanac contains a feature unique to all the CONSULTable items in IFdom (as far as I know): it can be BROWSEd. Browsing the almanac brings forth a random entry from within its pages; not only is it great fun to read these random entries, it also gives a sense of how thoroughly the almanac has been implemented. This device would be most welcome in other IF… how I’d love to browse the Encyclopedia Frobozzica or the Hitchhiker’s Guide to the Galaxy! Just having the book at hand lent a sense of scope and excitement to PZA.

Unfortunately, my first 45 minutes or so of playing this game were extremely frustrating. PZA suffers from a couple of serious design flaws, the gravest of which is its repeated violation of the Fifth Right (from Graham Nelson’s “Player’s Bill of Rights”): not to have the game closed off without warning. Because of a fairly flexible (but extremely temporary) magic spell that becomes available at the very beginning of the game, I found myself repeatedly stranded, unable to proceed and forced to RESTART. This happened again later on in the game — I committed a perfectly logical action and found out hundreds of turns later that this action had closed off the endgame. This is a frustrating experience, and one that could easily have been avoided with a few minor changes to the game’s structure, changes which would not have had any discernible effect on puzzles or plot. In addition, there are a few areas in which the player character can be killed without warning, always an unwelcome design choice. PZA is (as far as I know) Carl Klutzke’s first game, so chalk these flaws up to education. I look forward to playing another Klutzke game as well-implemented as PZA, but designed more thoughtfully.

One nice element of PZA was its facility with IF homage. The game’s “cluple” spell not only had a name that sounded straight out of Enchanter, it was virtually identical to that series’ “snavig” spell. The almanac itself (as well as a number of other features) was a skillful allusion to The Hitchhiker’s Guide to the Galaxy. Finally, the XYZZY command response is one of the more clever I’ve seen in a while. Clearly PZA‘s author is a devotee of the old games, and his devotion shows in his work. I am hopeful that his next piece of IF will live up to his worthy aspirations.

Prose: The prose in PZA is generally very good. Rooms, objects, and random events are described concisely but with attention to detail. Some of the locations are rather sparsely treated (for example, the town consists of one location), but such skimping is always done in service of the plot, and more detail would serve to distract rather than to enrich.

Plot: This is definitely the strongest point of PZA. The game starts out with an engaging hook, and after the twist I was definitely enjoying the direction of the story quite a bit. In addition, the author has manipulated the scoring system in such a way as to give the feeling of multiple endings. Granted, many of those endings amount to one version or another of “*** You have died ***”, but not all of them. There are more and less successful solutions to the story, and they are integrated so naturally into the endgame text that they almost escape notice. One of the nicest implementations of multiple endings in the competition.

Puzzles: Here there were problems. What happens to PZA is that its individual problems are well-considered, and their solutions are perfectly logical. However, when the actions that comprise those solutions are attempted in other areas of the game, they all too often drive the narrative into a blind alley from which there is no escape. It’s one of the hardest balancing acts in interactive fiction: how to have sensible puzzles logically integrated into the game, without making the narrative too linear, which in their elements create no dead ends for the player. PZA doesn’t pull it off.

Technical (writing): I found no technical errors in the writing.

Technical (coding): Once I played PZA on WinTADS, I had no problems with it. I started out trying to use it on my old DOS version of TR, and before I could even get one command out it was giving me TADS “Out of Memory” errors. Whether this is a bug in the program of the interpreter, I don’t know enough about TADS to say.

OVERALL: An 8.0

The Tempest by Graham Nelson as William Shakespeare [Comp97]

IFDB page: The Tempest
Final placement: 25th place (of 34) in the 1997 Interactive Fiction Competition

“Yet look, how far
The substance of my praise doth wrong this shadow
In underprizing it, so far this shadow
Doth limp behind the substance.”
— William Shakespeare
The Merchant of Venice III.ii.126-129

The Tempest attempts a great deal, and achieves much of it despite being somewhat flawed. The work presents itself not as a game, but as an “interactive performance” which asks the player to perform as the magical will of Shakespeare’s Prospero, guiding the spirit Ariel (a.k.a. the parser) through the plot of The Tempest (the play), though not necessarily in the order in which Shakespeare wrote it. Remarkably, this complicated positioning of subjectivity works quite well (and opens some unexplored territory for the mixing of first, second, and third person forms of address in IF). It is blended with a new approach to dialogue which prevents the player character from speaking at all but presents many screenfuls of dialogue between other characters (and sometimes including Ariel himself), the exchanges broken up by pausing for keystrokes between each character’s lines. In a sense, the player’s commands to the parser become essentially stage directions issued to an onstage persona via a magical conduit. This idiom also works beautifully, bestowing the game with a powerful aura of theatrical performance. The Tempest is entertaining and innovative; it often feels quite magical to inhabit the Prospero/Ariel connection, and to take part in a groundbreaking interactive experience. I think that the game also has great potential as an educational tool, allowing readers to experience Shakespeare’s language in a new and thrilling way.

All this being said, however, The Tempest is not without its problems. Actually, perhaps the game just has one major problem which manifests itself in several ways. Although the author does an excellent (sometimes astonishing) job of rearranging Shakespeare’s scenes and lines to fit the interactive mode, the fit is not perfect. Several times during the game I felt faced with responses which, if not complete non sequiturs, were certainly only tenuously connected to the command I had typed. The author wrenches in bits and pieces of dialogue from all over the play for various purposes, pressing them into service as room descriptions, parser rejoinders, and other sundry purposes. Sometimes they are perfectly suited to their purpose and sometimes less so. When I was on the wrong end of this continuum, my relationship with the game became strained — the parser’s responses were beautiful, but didn’t make enough sense, and not because of any opacity in the Elizabethan English. This situation creates a problem with the game’s puzzles: usually interactive fiction prose can be written in such a way as to suggest subtle hints to the problems facing the player. However, when control of the prose escapes the author, those hints become harder and harder for a player to come by. It is to this difficulty with the prose (and, of course, to the lack of any hint system or walkthrough) that I ascribe the problems I’ve seen players having, often with the very first puzzle of the game. With a typical piece of IF, the author could simply tailor the game’s responses to help the player along — The Tempest often achieves this goal, but all too often it falls short.

Before I played The Tempest, I was unlucky enough to run across a USENET conversation which suggested that Graham Nelson is the game’s author. I thought this was a spoiler, and I admit that it did set up a bit of preconception for me before I had even seen the first word of the game. Having said that, several things about the game do have a strong air of Nelson about them. The author’s erudition is clear, from the simple choice of subject matter to the deft interweaving of other Shakespearean and Renaissance phrases into the play’s text when necessary (for example, to the command “throw x at character” the game responds “I have no aim, no, no chance of a palpable hit.”, a phrase echoing Hamlet). Such attention to scholarly detail recalls some of the finer moments of Nelson’s epics, especially Jigsaw. Moreover, the game’s help menu (which it calls its frontispiece) contains fascinating blurbs on lost islands and the play’s history, as well as notes on the game, its creation and characteristics. Such additions are strongly reminiscent of the diplomatic briefings in Nelson’s 1996 1st Place game The Meteor, the Stone, and a Long Glass of Sherbet. Finally, the author’s technical skill and innovations with Inform are tremendous, and who better to code so well than the language’s inventor? It may be that Nelson is in fact not the author of the work (in which case the author should take the comparison as a compliment of the highest order), but even if that is so, the talent behind this game is clearly a major one. The Tempest was Shakespeare’s last play, and as such carries a distinct air of finality — I only hope that whoever authored this work will not allow it to be his or her last as well.

Prose: I suppose this is where I ought to weigh in on the debate over the originality of a work like the IF version of The Tempest. It’s my opinion that the IF Tempest is absolutely a different piece of work from The Tempest, the play. Yes, the author uses almost the entire script of the play, but I would argue that such usage is not plagiarism, because whatever Shakespeare’s intentions, I think it’s safe to say that the play was not written to be adapted into interactive form. Consequently, I don’t see the IF Tempest as any less an original work than Emma Thompson’s Sense and Sensibility or, for that matter, Shakespeare’s MacBeth (whose plot was lifted from Holinshed’s histories.) Yes, the seams do sometimes show between the author’s additions and Shakespeare’s text — these are the work’s weaker moments. However, in judging The Tempest‘s prose, I judge not the quality of Shakespeare’s writing, but the quality of its usage in its new medium — on that basis, more often than not, it succeeds.

Plot: I predict that a certain contingent of voices will raise the hue and cry over what they perceive to be The Tempest‘s lack of interactivity. I wasn’t able to finish the game in two hours (far from it, in fact — I got only six points, another example of an excellent competition game which breaks the two-hour rule), but the parts I saw made it pretty clear that the game leads you along rather carefully from one plot point to the next, allowing for very little branching. My own opinion is that this structure is not a problem — after all, the piece bills itself as “more a ‘performance’ than a ‘game’,” and as such it’s perfectly appropriate for The Tempest to enforce a certain degree of rigidity to accommodate the exigencies of its plot. In fact, what this achieves is the inclusion of a much more complicated plot than is common in interactive fiction; by limiting the player’s ability to affect the narrative stream, the game allows the complexity of Shakespeare’s plotting to shine through even in this challenging new form. I’m satisfied with the trade-off.

Puzzles: As noted above, this is where I identify the major weakness of The Tempest. [SPOILERS AHEAD] I cite as an example the first puzzle of the game, where Ariel must blow a storm to upset the boat and set the plot into motion. The reason that players are finding this puzzle so difficult is that it requires rather close knowledge of the play (and not just of the play’s first scene), which most players, even very well educated ones, are not likely to have at their fingertips. No hint is given of Ariel’s powers or of his purpose in regard to the ship. [SPOILERS END] Now, in a typical IF game, there might be a sentence or two in the introductory paragraph which introduces the idea and sets players on their way. However, because of the constraints imposed by using a collage of prewritten text, these hints are unavailable and thus players flounder in a “read-the-playwright/designer’s-mind” sort of puzzle. It won’t be the last time.

Technical (writing): The prose did an excellent job with handling a number of difficult technical tasks with regard to writing and using Elizabethan English.

Technical (coding): I found only one bug in The Tempest (at least, I think it was a bug), among a thoroughly reworked library of Inform responses and the introduction of a number of excellent devices for the presentation of dialogue and clarification of the plot.

OVERALL: A 9.2

The Meteor, the Stone, and a Long Glass of Sherbet by Graham Nelson as Angela M. Horns [Comp96]

IFDB page: The Meteor, the Stone, and a Long Glass of Sherbet
Final placement: 1st place (of 26) in the 1996 Interactive Fiction Competition

I was very impressed with Sherbet, a highly inventive adventure which puts yet another imaginative spin on the Zork mythos. The game’s prose is at a very high level of quality, its world is very well-designed, and several aspects of the documentation (the context-sensitive hints and the diplomatic “briefing”) were very well done indeed. I didn’t get through the entire game in the two hours allotted, and I found myself resorting to the hints quite a lot. Often, this was because a logical puzzle had me stumped, but the first two times were due to puzzles which didn’t offer enough alternative syntax. Unfortunately, these two situations inured me to looking at the hints, thinking perhaps that my other obstacles were due to syntax problems as well. Apart from this one flaw, Sherbet was a truly excellent piece of work — well-plotted with clever puzzles, a strong sense of unfolding narrative, and rife with the pleasures of revisiting an old friend in a new context.

Prose: The game’s writing consistently maintains an exceptional level of quality. The vacuous’ Amilia’s ramblings serve exquisitely to define her character, and the “briefings” concisely draw the player’s diplomatic situation while quietly evoking Zorkian echoes. I found myself just a little confused by some of the cave descriptions, but this was mainly due to the sense of scope which the author unerringly conveys.

Difficulty: As I mentioned, the game was too difficult (and large) for me to complete in the two hours allotted for judging time, and part of this difficulty arose from problems with the first two puzzles. After finally summoning the bird of paradise, I spent a good fifteen minutes trying to pour, put, rub, insert, or otherwise attach the sherbet to the elephant before finally resorting to the hints only to discover that the game demanded I “throw” the sherbet glass. However, in other spots the difficulty of the game was quite legitimate and logical, as in the instance of the ladder problem, which was another solution I found in the hints rather than finding it myself.

Technical (coding): On the whole, the game was very well coded, and I never found the kind of irrational flaws which can snap the suspension of disbelief in interactive fiction. There were a few spots where the game suffered from a lack of synonyms, especially the elephant (as described above) and the hook (one must again “throw rope over hook” but cannot stand on the table or hamper, lasso the hook, simply “throw rope” , “put rope on hook”, or even “throw rope onto hook”.) When these problems are eliminated , the game will be very strong indeed.

Technical (writing): Sherbet is a well-written and well-proofed piece of work in which I don’t recall noticing any technical mistakes.

Plot: It was a great pleasure to get embroiled in the plot, and the premise of the main character as a diplomat rather than an adventurer provided a break from cliché married with a plausible reason for the snooping called for by the game’s structure. I’m looking forward to the endgame, which I hope will offer a tie between the game’s diplomatic beginnings and its Zorklike middle.

Puzzles Mostly discussed above in “Technical (coding)” and “Difficulty.” Many of the puzzles were real pleasures (panning and the ladder come to mind) and the twist on treasure collecting (giving all the treasures to the Zork adventurer) was brilliant. Once the puzzles are better coded the game will be really first-rate.

OVERALL — A 9.3