player’s bill of rights

howling dogs by Porpentine [XYZZY]

[I originally reviewed this game for the XYZZY Awards, as part of a project to review all the 2012 nominees for Best Writing. howling dogs took home the Best Writing award, which shows you how out of step I apparently am with that year’s voters.]

IFDB page: howling dogs

So it turns out there’s this unfortunate consequence to not paying attention, which is that you don’t know about stuff. Case in point: there is someone called Porpentine, who has written a number of IF games in different formats, as well as poetry, fiction, essays, and various other work. I had never heard of her prior to opening this game, probably because I am pretty detached from the IF scene nowadays. In any case, she apparently has quite a fan base, or at least this game does, judging from its 5 XYZZY nominations, including one for Best Game. However, I am sorry to say that I am not among its fans.

Part of this comes down to taste. I’ve mentioned in the past that I have trouble relating to games that get too abstract. When metaphor piles upon metaphor, with nothing concrete underpinning them, the whole thing tends to kind of slide off me. When the base scenario is a futuristic metal cube (or hamster cage, or something) with no exit and no explanation of why you’re imprisoned there, and we launch from that into (for instance) hallucinatory dreamscapes of invasion by it’s-not-clear-what, or maybe you’re the one doing the invading (it’s not clear), while inanimate objects and landscape features talk to you, only to be interrupted by a sub-hallucination of a tranquil tea party… well, my mind starts asking why I should care, and what is the point exactly? I know there are people who really dig this kind of thing. I’m just not one of them, despite my nagging feeling that this distaste will prevent me from hanging out with the cool kids.

That’s not to say that I need metaphor-free quest plots where everything is spelled out in big block letters. Some of my very favorite writers can be so bizarre and elliptical that it is sometimes almost impossible to detect what they’re on about — Emily Dickinson, Tori Amos, and Stevie Nicks come to mind. Yes, these are writers of poetry and lyrics, where perhaps a great remove is easier to tolerate, but I’ve enjoyed many a surreal IF game too — Blue Chairs, For A Change, Shrapnel, and so forth. I think it comes down to trust. I can let my mind and emotions fall backward into some pretty strange territory as long as I trust that I’m in the hands of someone who knows what they’re doing. Unfortunately, my trust was immediately blown, right out of the gate, by this game’s opening text:

One morning at dawn the nurse shook him awake because his sobs were being heard in the next room. Once he was awake he could hear that not only was the patient next door but the two hundred dogs kept in the hospital courtyard for use in the laboratory had also been threatened by his sobbing and clearly were howling still

I looked at this and thought, “Best writing? But… it’s incoherent!” Even setting aside the fact that the total lack of commas makes the whole thing feel extremely plodding, it’s just nonsensical. Taking out some of the extraneous stuff, I get this sentence: “Not only was the patient but the dogs had also been threatened.” It simply does not parse.

Then a bit more of the passage revealed itself, and I saw that it was not by Porpentine at all, but rather by someone called Kenzaburo Oe. Since I was disengaged from the story anyway at this point, I googled the name to see if he is a real person. Yep, he’s a real person who, uh, seems to have won the Nobel Prize for Literature. Say wha? Now I was really confused. Maybe it made sense in the original Japanese, and was badly translated? After further googling I determined that no, it made sense in the original English, before it was mangled. Here’s Oe’s original sentence, from his novella The Day He Himself Shall Wipe My Tears Away:

Once he was awake he could hear that not only the patient next door but the two hundred dogs kept in the hospital courtyard for use in the laboratory had also been threatened by his sobbing and clearly were howling still

If I boil this one as I did the other one, I get: “Not only the patient but the dogs had also been threatened.” That’s a sentence that works just fine, because it doesn’t have an errant “was” inserted between “only” and “the”. The entire passage is Oe’s work, except for the “was”, which I have to assume came from Porpentine. He Himself is about someone who (maybe) has cancer, so perhaps the idea here is that the “was” is the cancer that infects the sentence? It certainly kills the thing stone dead. Having left the story almost immediately to do this much research, I was not inclined to be so charitable. To me it seemed like a fundamental error, one which bespoke a basic disinterest in comprehensible language, coming as it does in the crucial first sentences of the game. While the rest of howling dogs did in fact parse (well, most of it), I didn’t find much to contradict that belief.

Take, for instance, the description of the central room, one of the most frequently repeated passages of the game:

A room of dark metal. Fluorescent lights embedded in the ceiling.

The activity room is in the north wall. The lavatory entrance, west, next to the trash disposal and the nutrient dispensers. The sanity room is in the east wall.

So far so good with the first part — two terse Emily Shortesque sentence fragments sketch a grim, depressing cell. Their sparseness is in keeping with the spartan accommodations. However, things start to go wrong in the second part. Two rooms are described as “in” walls. In? How can a room be in a wall, when it’s walls that define rooms? The image I got was of an indentation in the wall, though when I followed the leads, the game treated them as separate locations. That suggested to me that although the use of the word “in” had to be intentional (it happens twice, after all), it was not used to create a pervasive effect as much as to inject alienating and unfamiliar diction for its own sake.

Between these two sentences is another fragment, but this one doesn’t work nearly so well as the first ones. The short appositive and the long prepositional phrase that follow the subject had me waiting for a verb. “The lavatory entrance, yes, yes… what about it?” Then I thought perhaps that this was a case of a word wrongly removed rather than wrongly inserted. “The lavatory entrance is west…” would have worked just fine. It was a little bit funny that the lavatory is the only space grand enough to rate an actual entrance, rather than just being “in” the wall, but I don’t think the humor was intentional. For that matter, I found very little humor of any kind in howling dogs. This is a dour game, which is fine as an artistic choice, but puts further pressure on the language to live up to the apparently Very Serious intentions behind it.

So that I don’t spend this entire review excoriating and picking apart the game’s writing, I will note that there were some striking parts. As I said, I’m not much for the highly abstract, but when the action neared the ground, I found it pretty compelling. The murder scene is gripping and dramatic — I particularly liked the detached observation about the knot. The advice on how best to be assassinated was clever, and did a good job of cueing the right word in the “giant wodge of text” scene. I’ll note, though, that it’s only thanks to the “howling dogs spoilers” text file that I knew there was such a thing as a “right word” in that scene, which suggests that the game’s design fails to stand up on its own. I certainly would have given up on it without that file. For that matter, it led me to the “correct” ending (the one that isn’t marked “false terminus”), which was my favorite part of the game, particularly the “gap” effect.

That scene was the closest I came to an emotional connection with howling dogs, but by that time it was far too late — I had already checked out. I could cite many more places where the writing falls down, but I think I’ve made my point, so instead I’ll end by stepping out of my prescribed area, because I think this is important. Game designers, if you want to make a game with a repetitive structure, in which progress depends on returning again and again to the same mechanic, DO NOT frontload that mechanic with arbitrary, unrewarding actions. When I found out I had to follow the whole “nutrient dispensers” path each and every time I wanted to see the next scene, I groaned aloud. Long ago, Graham Nelson wrote a Bill of Player’s Rights, one of which was “Not to need to do boring things for the sake of it.” howling dogs really should have heeded that advice — tedium adds neither fun nor gravitas to a story. In fact, I could say the same thing for layers of abstraction and self-consciously serious prose.

Lock & Key by Adam Cadre [IF-Review]

[I originally reviewed this game for Mark Musante’s site IF-Review, in 2003.]

IFDB Page: Lock & Key

Death Becomes You

[NOTE: Lock & Key has a twist right at the beginning, and I’m going to give it away because it’s not practical to discuss the game without doing so. So if you haven’t played it yet and you want to be surprised, go play it before reading this, at least up to the twist anyway.]

I love editing SPAG, but the job does have its down-sides. For instance, I’m frequently obliged to read reviews of games I haven’t played yet. Most of the time, this isn’t much of a problem, since SPAG reviews are required to be spoiler-free. However, there is a small, occasional section of the ‘zine called SPAG Specifics, wherein reviewers are allowed to spoil as much as they like in the interest of promoting specific, detailed discussion about particular games. When I get a review for this section, I need to read it whether I’ve played the game in question or not.

That’s exactly what happened to me with Lock & Key — I’d played the game enough to get beyond the initial twist, see the setup, say “Cool”, and vaguely resolve to play it whenever I found the time. Shortly afterward, Eytan Zweig submitted a thoughtful, fairly critical review of the game for SPAG Specifics, and I decided that I wanted to wait a while to play the game after that, so that the review would fade enough in memory that it wouldn’t color my perceptions. Now it’s been about a year since that issue, Lock & Key has just won a handful of XYZZY Awards, and I have a new laptop I needed to test this past weekend; the stars were aligned, and I finished the game.

I wasn’t disappointed. Cadre’s writing shines as usual, as does his knack for giving every game a fresh angle. In this one, you play a prison designer and security expert in a mildly jokey pseudo-medieval milieu. Your job is to craft the perfect sequence of death-traps for the King’s dungeon, enough to defeat even the hardiest adventurer who might try to escape it. If you succeed, you’ll make a fortune and be able to retire. If you fail, well, you get beheaded. Those medieval managers really knew how to motivate their employees.

The meat of the game is its one and only puzzle, the one for which it earned the XYZZY for Best Individual Puzzle: setting the traps. It’s not that setting the traps themselves is all that difficult, but choosing the right ones… ah, that’s another matter. See, once you’ve finished constructing your ideal dungeon, it is put to the test by Boldo, a thick-thewed adventurer who, in the best IF fashion, seems to have an endless inventory of items that happen to counteract your traps perfectly. Every time he encounters a death-trap, you get to see exactly how he defeats it, and this in turn allows you to begin scheming about how you might deprive him of that method. Like Varicella, the game is highly iterative — the chances you’ll beat it the first time through are virtually nil, and this is by design. Instead, Boldo’s many triumphs allow you to make your own advances towards building the perfect dungeon upon restarting.

It’s a deeply rewarding puzzle of marvelously interlocking elements. Not only does it operate on several levels to begin with, it builds on itself to make lots of little “aha!” moments combine into a greater experience of overall insight. In addition, the game’s use of graphics do it a great service, presenting a clean and attractive game board to help players to see exactly what choices they’ve made.

My favorite part of the puzzle, though, is the hinting. The prose that describes Boldo conquering your traps is funny and enjoyable to read on its own merits, but it also frequently contains wonderfully subtle hints about how the dungeon might be better constructed. For the sake of spoiler-avoidance, I won’t quote any of those hints here, but I will say that they capture the feel that Infocom at its best was able to provide, of prose that is just as good on a game level as it is on a story level.

So Lock & Key wholly deserved its XYZZY for Best Puzzle. The other awards, I’m not so sure about. At the end of the XYZZYs, Lock & Key went away with the prizes for both Best Individual NPC (Boldo) and Best NPCs in general. The fact that it won these accolades for NPCs with whom (for the most part) the player cannot directly interact AT ALL is rather astonishing. I’m not sure what to make of it. Perhaps writing is just much, much more important than coding when it comes to NPCs, at least as far as the XYZZY voters are concerned. Certainly Boldo reacts to the traps placed by the player, and the descriptions of his reactions are all great and funny, but that’s a very limited sort of interaction, nothing at all like the dozens and dozens of responses that make up the typical fully-fleshed IF NPC. I wonder: can great writing alone make a great NPC?

Maybe sometimes it can, but I’ve yet to see it. Certainly this game’s excellent writing didn’t make Boldo an excellent NPC. He’s simply a cipher, an intentionally broad cliche whom the PC never meets, instead only watching cut-scenes of him on a sort of magic TV. He’s entertaining enough for the purpose he serves, but he hardly feels like a deeply implemented NPC, though he’s the deepest of the bunch. The other NPCs — the King, a gladiator named Musculo, and a host of others who appear in brief cameos — are present only in cut-scenes. The only exception to this, the only NPC who even responds to “ASK”, is the guard at the beginning. His response: “No talking in the dungeon!”

I would contend that the really remarkable character in Lock & Key is the player character. What’s remarkable about him? [1] Why, his cleverness, of course — his ability to string together just the right combination of traps to defeat Boldo. More to the point, what’s remarkable is the way in which the game constructs this cleverness. Like Primo Varicella, the PC of Lock & Key is what I’ll call an accretive PC, meaning that he becomes more and more himself with each iteration of the game, as the player’s knowledge accretes.

In most IF games, your character will never live up to you — it will never be able to do most of the things you can think of, nor say most of the things you can say. This is still true of Lock & Key and Varicella, but in an important way, what’s also true of those games is that you must live up to your character. You’re told a salient quality about the PC at the outset of the game — his expertise in dungeon design, or his Machiavellian plan to take over the regency — and then you must take him through one iteration after another until you yourself have attained enough of that quality to guide the PC to a successful conclusion. When you finally do reach that conclusion, it’s as if you’ve finally learned the real story, and all the failed attempts leading up to it exist only in shadowy parallel universes. This is who the character was all along — it just took you a while to catch up with him.

Of course, the case could be made that all IF PCs are like this to some degree. That may be true, but then again it’s de rigueur in most other IF to avoid game designs in which the PC must learn something by dying. Graham Nelson even made it Rule Number Three in his Player’s Bill Of Rights. [2] Of course, when a player must be able to step successfully into the PC’s viewpoint without any previous knowledge whatsoever, it becomes rather hard to give that PC any sort of expertise in the game world, which is why we so frequently see PCs who suffer from amnesia, or are fish-out-of-water, or other such tricks. Lock & Key and Varicella break this rule so brilliantly that it doesn’t even seem like a valid rule anymore. Why shouldn’t the player learn from past lives? After all, unless the PC is placed in some sort of contrived situation to deprive her of all her natural knowledge, she’ll inevitably know more than the player does the first time that player begins the game.

After a while, the requirement to match the PC’s knowledge with the player’s can begin to feel like a bit of a cage, and the most common contortions an IF game goes through to live inside it (such as amnesia) have long since lost their appeal. Even the freshest ones can still feel a bit tired and gimmicky unless done exactly right. The accretive PC is one key to this cage — it’s wonderfully refreshing to play a character who’s really good at something, and even better to become good at it yourself. Of all the jail-breaks that happen in Lock & Key, this one is the most satisfying.

—

[1] I’m referring to the PC as a male for convenience’s sake — I don’t recall its gender ever being specified in the game.

[2] See his excellent article The Craft Of Adventure, available in the info directory of the IF Archive.

Zork Zero [Infocom >RESTART]

IFDB page: Zork Zero
[This review contains lots of spoilers for Zork Zero, as well as at least one for Zork I. Also, I wrote an introduction to these Infocom >RESTART reviews, for those who want some context.]

The earliest game in the Zork chronology was one of the latest games in the Infocom chronology. Zork Zero emerged in 1988, two years after the company was bought by Activision, and one year before it would be shut down. Zork was Infocom’s most famous franchise by far, and this prequel was the company’s last attempt to milk that cash cow, or rather its last attempt with original Implementors on board. Activision-produced graphical adventures like Return to Zork, Zork: Nemesis, and Zork: Grand Inquisitor were still to come, but those were fundamentally different animals than their namesake. Zork Zero, written by veteran Implementor Steve Meretzky, was still a text adventure game.

However, there was a little augmentation to the text this time. Along with a few other games of this era, Zork Zero saw Infocom dipping its toe into the world of graphics. The text window is presented inside a pretty proscenium arch, one which changes its theme depending on your location in the game, and also provides a handy compass rose showing available exits. Some locations come with a thumbnail icon, many of which are pretty crudely pixelated, but some of which (like the Great Underground Highway) are rather memorable. Most crucially, several important puzzles and story moments rely upon graphics in a way that hadn’t been seen before in a Zork game, or any Infocom game for that matter. In order to make these nifty effects work in Windows Frotz, our interpreter of choice, Dante and I had to do a bit of hunting around in the IF Archive — thus it was that we solved our first puzzle before we even began the game.

>EMBIGGEN ZORK. G. G. G. G.

Once we did start, we found that graphics weren’t the only way Meretzky found to expand on the Zork legacy. He also expanded on it by… expanding it! Over and over again, we were knocked out by the scope of this game. It’s enormous! Our Trizbort map had 208 rooms, and that’s not even counting ridiculous location “stacks” like the 400-story FrobozzCo building or the 64-square life-sized chessboard. By contrast, our map for Zork I had 110 rooms, and Zork III had a meager 59. So many locations. So many puzzles. So many objects. So many points! You’ll score a thousand hard-won points in a successful playthrough of Zork Zero. Dimwit Flathead’s excessiveness is a frequent butt of Meretzky’s jokes in this game (e.g. a huge kitchen that “must’ve still been crowded when all 600 of Dimwit’s chefs were working at the same time”), but if Dimwit were to design an IF game, it would definitely be this one.

The largesse still doesn’t apply to writing noun descriptions, though. For example:

>X CANNONBALL There's nothing special about the cannonball.

>X UNICORNS There's nothing unusual about the herd of unicorns.

>X FJORD It looks just like the Flathead Fjord.

Even this late in Infocom’s development, they still hadn’t adopted the ethos that the most skilled hobbyists would take up later, of enhancing immersion by describing everything that could be seen.

Similarly, inventory limits are still around to vex us, and they hit especially hard in a game like this, which is absolutely overflowing with objects. Because of those limits, we followed our tried-and-true tactic of piling up all our spare inventory in a single room. In the case of Zork Zero, we knew we’d be throwing a bunch of those objects into a magic trophy case cauldron, so we stacked them in the cauldron room. By the time we were ready for the endgame, that room’s description was pretty hilarious:

Banquet Hall Many royal feasts have been held in this hall, which could easily hold ten thousand guests. Legends say that Dimwit's more excessive banquets would require the combined farm outputs of three provinces. The primary exits are to the west and south; smaller openings lead east and northeast. A stoppered glass flask with a skull-and-crossbones marking is here. The flask is filled with some clear liquid. A 100-ugh dumbbell is sitting here, looking heavy. Sitting in the corner is a wooden shipping crate with some writing stencilled across the top. A calendar for 883 GUE is lying here. You can see a poster of Ursula Flathead, a four-gloop vial, a shovel, a box, a spyglass, a red clown nose, a zorkmid bill, a saucepan, a ring of ineptitude, a rusty key, a notebook, a harmonica, a toboggan, a landscape, a sapphire, a glittery orb, a smoky orb, a fiery orb, a cloak, a ceramic perch, a quill pen, a wand, a hammer, a lance, an easel, a wooden club, a bag, a silk tie, a diploma, a brass lantern, a notice, a broom, a funny paper, a stock certificate, a screwdriver, a gaudy crown, a ticket, a dusty slate, a treasure chest, a blueprint, a saddle, a fan, a steel key, a walnut shell, a manuscript, an iron key, a package, a T-square, a fancy violin, a metronome, a scrap of parchment, a proclamation, a cannonball, a sceptre and a cauldron here.

That certainly wasn’t everything, but you get the idea.

In fact, this game was so big that its very size ended up turning into a puzzle, or at least a frustration enhancer. Dante and I flailed at a locked door for quite a while before realizing that we’d had the key almost since the beginning of the game. We forgot we’d obtained an iron key by solving a small puzzle in one of our earliest playthroughs, and the key itself was lost in the voluminous piles of stuff we had acquired. When we finally realized we’d had the key all along, it was nice to open up the door and everything, but it also felt a bit like we should be appearing on the GUE’s version of Hoarders.

Not only did the scope of Zork Zero obscure the answers to puzzles like that, it also functioned as a near-endless source of red herrings. It’s possible to waste immense amounts of time just checking locations to see if you’ve missed anything, because there are just so many locations. The FrobozzCo building was of course an example of this, but even more so was the chessboard, which soaked up tons of our time and attention trying to figure out what sort of chess puzzle we were solving. Not only was exploring the whole thing a red herring, but so was making moves and doing anything chess-related!

The cover of Zork Zero

On the other hand, the game’s sprawling vistas can also evoke a genuine sense of awe, somewhat akin to seeing the Grand Canyon from multiple viewpoints. There was a moment in the midgame where we’d been traversing a very large map to collect various objects, and then the proper application of those objects opened up a dimensional gateway to an entirely new very large map. Shortly afterward, we realized that in fact, the puzzle we’d just solved had in fact opened up five different dimensional gateways, some of which eventually connected to our main map but many of which did not! Moments like that were breathtaking, not just because of all the authorial work they implied, but also because of the gameplay riches that kept getting laid before us.

Sometimes, to make things even sillier, the effects of the giant inventory would combine with the effects of the giant map. One of those offshoot maps mentioned above contained a special mirror location, which would show you if there was anything supernatural about an object by suggesting that object’s magical properties in its reflection. Super cool, right? Well yeah, except that inventory limits, combined with incredible object profusion, required us to haul a sliver of our possessions during each trip to the mirror, and each trip to the mirror required a whole bunch of steps to accomplish. (Well, there was a shortcut through a different magical item, but we didn’t realize that at the time, and in fact only caught onto that very late in the game, so didn’t get much of a chance at optimization.)

So yes, the mirror location was a wonderful discovery. Less wonderful: hauling the game’s bazillion objects to the mirror in numerous trips to see if it could tell us something special. But then when we found something cool that helped us solve a puzzle: wonderful! This is quintessential Zork Zero design — an inelegant but good-natured mix of cleverness, brute force, and sheer volume. The capper to this story is that there’s one puzzle in particular that this mirror helps to solve, but we fell prey to Iron Key Syndrome once again and somehow failed to bring that puzzle’s particular objects (the various orbs) to the mirror, obliging us to just try every single one orb in the puzzle until we found the right one.

>RECOGNIZE ZORK TROPE. G. G. G. G.

Those orbs felt pretty familiar to us, having just recently palavered with Zork II‘s palantirs. (Well, the game calls them crystal spheres, but c’mon, they’re palantirs. Or, as Wikipedia and hardcore Lord of the Rings people would prefer, palantíri.) However, familiar-looking crystal balls were far from the only Zork reference on hand. As I said, Zork Zero appeared late in Infocom’s history, and with the speed at which the videogame industry was moving, Zork I had for many already acquired the reflected shine of a bygone golden age. Thus, nostalgia was part of the package Infocom intended to sell with this game, which meant Zork tropes aplenty.

One of the best Zorky parts of the game concerns those dwellers in darkness, the lurking grues. In the world of Zork Zero, grues are a bygone menace. As the in-game Encyclopedia Frobozzica puts it:

Grues were eradicated from the face of the world during the time of Entharion, many by his own hand and his legendary blade Grueslayer. Although it has now been many a century since the last grue sighting, old hags still delight in scaring children by telling them that grues still lurk in the bottomless pits of the Empire, and will one day lurk forth again.

Oh, did I fail to mention that this huge game also contains an interactive Encyclopedia Frobozzica, with dozens of entries? Yeah, this huge game also has that. In any case, “the bottomless pits of the Empire” might sound familiar to longtime Zork players, or to readers of Infocom’s newsletter, which was for several years called The New Zork Times, until a certain Gray Lady‘s lawyers got involved. As NZT readers would know, there was a time before Zork was on home computers, before it was even called Zork at all. It was called Dungeon, at least until a certain gaming company‘s lawyers got involved.

In Dungeon, there were no grues in the dark places of the game, but rather bottomless pits — a rather fitting fate for someone stumbling around in a dark cave, but the game was more than just a cave. As the NZT tells it:

In those days, if one wandered around in the dark area of the dungeon, one fell into a bottomless pit. Many users pointed out that a bottomless pit in an attic should be noticeable from the ground floor of the house. Dave [Lebling] came up with the notion of grues, and he wrote their description. From the beginning (or almost the beginning, anyway), the living room had a copy of “US News & Dungeon Report,” describing recent changes in the game. All changes were credited to some group of implementers, but not necessarily to those actually responsible: one of the issues describes Bruce [Daniels] working for weeks to fill in all the bottomless pits in the dungeon, thus forcing packs of grues to roam around.

Sure enough, in Zork Zero prequel-ville, when you wander into a dark place, you’ll get the message, “You have moved into a dark place. You are likely to fall into a bottomless pit.” In fact, at one of the lower levels of the enormous map, we found a location called “Pits”, which was “spotted with an incredible quantity of pits. Judging from the closest of them, the pits are bottomless.” Across the cavern, blocked by those pits, was “an ancient battery-powered brass lantern”, another major Zork nostalgia-carrier. Fittingly, to get to the traditional light object, we had to somehow deal with the even-more-traditional darkness hazard.

Lucky for us, yet another puzzle yielded an “anti-pit bomb”, which when thrown in the Pits location causes this to happen:

The bomb silently explodes into a growing cloud of bottomless-pit-filling agents. As the pits fill in, from the bottom up, dark and sinister forms well up and lurk quickly into the shadows. Uncountable hordes of the creatures emerge, and your light glints momentarily off slavering fangs. Gurgling noises come from every dark corner as the last of the pits becomes filled in.

Thereafter, when the PC moves into a dark place, the game responds with a very familiar message: “You have moved into a dark place. You are likely to be eaten by a grue.” Luckily, the game provides an inexhaustible source of light in the form of a magic candle, so there are no terrible light timers to deal with. Some things, nobody is nostalgic for.

A screenshot from Zork Zero showing the message "You have moved into a dark place. You are likely to fall into a bottomless pit."

Lack of a light timer made it easier to appreciate this game’s Wizard of Frobozz analogue, the jester. Like the Wizard, this guy pops up all over the place at random times, creating humorous magical effects which generally block or delay the PC. Sometimes those effects are themselves Zork references, such as when he sends a large deranged bat swooping down, depositing the PC elsewhere as it shrieks, “Fweep! Fweep!” Also like the Wizard, his effects get less funny the more they’re repeated. And also also like the Wizard, he figures prominently into the game’s plot.

However, unlike the Wizard, he functions in a whole bunch of other capacities as well. He’s the game’s primary NPC, appearing to deliver jokes, adjudicate puzzles (especially riddles), occasionally help out, congratulate solutions, and hang around watching the player struggle. He’s not quite an antagonist but certainly not an ally, and you get the sense he’s controlling far more than he lets on. In other words, he’s an avatar for the game itself, and in particular the twinkling eyes of Steve Meretzky.

>LAUGH. G. G. G. G.

Meretzky’s writing is witty and enjoyable throughout — it’s one of the best aspects of the game. He clearly revels in tweaking Zork history, as well as in reeling off line after line about the excessive Dimwit, e.g. “This is the huge central chamber of Dimwit’s castle. The ceiling was lowered at some point in the past, which helped reduce the frequency of storm clouds forming in the upper regions of the hall.” Probably my favorite Zork reference was also one of my favorite jokes in the game:

>HELLO SAILOR [The proper way to talk to characters in the story is PERSON, HELLO. Besides, nothing happens here.]

Meretzky is also not above retconning previous bits of Zork lore that he disagrees with, such as his Encyclopedia Frobozzica correction of a detail in Beyond Zork‘s feelies: “The misconception that spenseweed is a common roadside weed has been perpetuated by grossly inaccurate entries in the last several editions of THE LORE AND LEGENDS OF QUENDOR.”

Speaking of feelies, this game had great ones, absolutely overflowing with Meretzky charm. Infocom was still heavily into copy-protecting its games via their documentation, and in typically excessive fashion, this game did that many times over, providing a map on one document, a magic word on another, and truckloads of hints (or outright necessary information) in its major feelie, The Flathead Calendar. This calendar called out to yet another aspect of Zork history, the wide-ranging Flathead family, with members such as Frank Lloyd Flathead, Thomas Alva Flathead, Lucrezia Flathead, Ralph Waldo Flathead, Stonewall Flathead, and J. Pierpont Flathead. The game’s treasures are themed around these figures, which was not only a lot of fun but also allowed me to do a bit of historical education with Dante, who still references Flatheads from time to time when mentioning things he’s learning in school.

The feelies establish a playful tone that continues through to the objects, the room descriptions, and the game’s general landscape. There are also great meta moments, such as the “hello sailor” response above, or what happens when you dig a hole with the shovel you find: “You dig a sizable hole but, finding nothing of interest, you fill it in again out of consideration to future passersby and current gamewriters.” Also enjoyable: the response to DIAGNOSE after having polymorphed yourself, e.g. “You are a little fungus. Other details of health pale in comparison.”

Meretzky even brings in a trope from Infocom’s mystery games, in probably the most ridiculous joke in the entire thing. There’s a location containing both a cannonball and a number of “murder holes”, “for dropping heavy cannonballs onto unwanted visitors”. This is obviously an irresistible situation, and the results are worth quoting in full:

>DROP CANNONBALL THROUGH HOLE As you drop the cannonball through the murder hole, you hear a sickening "splat," followed by a woman's scream! "Emily, what is it!" "It's Victor -- he's been murdered!" "I'll summon the Inspector! Ah, here he is now!" You hear whispered questions and answers from the room below, followed by footsteps on the stairs. The jester enters, wearing a trenchcoat and smoking a large pipe. "I'm afraid I'm going to have to order Sgt. Duffy to place you under arrest, sir." You grow dizzy with confusion, and your surroundings swirl wildly about you... Dungeon A century's worth of prisoners have languished in this dismal prison. In addition to a hole in the floor, passages lead north, southeast, and southwest.

None of these characters (except the jester) occur anywhere in the game outside this response. Sergeant Duffy, as Infocom fans would know, is who you’d always summon in an Infocom mystery game when you were ready at last to accuse the killer. By the way, the Dungeon isn’t locked or anything — it’s a gentle joke, not a cruel one. The only real punishment is having to traverse the huge map to get back to wherever you want to be. I’ll stop quoting Meretzky jokes in a second, but I have to throw in just one more, because of the surprising fact that it establishes:

>EAT LOBSTER 1) It's not cooked. 2) It would probably bite your nose off if you tried. 3) You don't have any tableware. 4) You don't have any melted butter. 5) It isn't kosher.

Turns out the Zork adventurer (or at least the pre-Zork adventurer) is not only Jewish, but kosher as well! Who knew? Though, given that the kosher objection comes last, after lack of cooking, tableware, and butter, their commitment may be a bit halfhearted after all.

Amidst all the humor, Meretzky hasn’t lost his touch for pathos either, with a design that themes several puzzles around the sense of ruin and decay. For example, we found an instruction to follow a series of steps, starting from “the mightiest elm around.” In Zork Zero, this is an enormous tree stump. Meretzky has learned some lessons from Planetfall and A Mind Forever Voyaging about how to make a landscape that inherently implies its bygone better days. Even in the Zork prequel, the adventurer is traversing a fallen empire.

>REMEMBER PUZZLE. G. G. G. G.

Zork Zero isn’t just a prequel in narrative terms. As we kept finding old-timey puzzles like the rebus or the jester’s Rumpelstiltskin-esque “guess my name” challenge, Dante had the great insight that as a prequel, this game was casting back not just to an earlier point in fictional universe history, but to puzzle flavors of the pre-text-adventure past as well. Relatedly, as we ran across one of those vintage puzzles — The Tower of Hanoi Bozbar — he intoned, “Graham Nelson warned us about you, Tower of Bozbar.”

He was referencing a bit in Graham’s Bill of Player’s Rights, about not needing to do boring things for the sake of it: “[F]or example, a four-discs tower of Hanoi puzzle might entertain. But not an eight-discs one.” Zork Zero‘s tower split the difference by having six discs, and indeed tiptoed the line between fun and irritating.

However, if we’d been trying to do it without the graphical interface, the puzzle would have vaulted over that line. The game’s graphics are never more valuable than when they’re helping to present puzzles rooted in physical objects, like the Tower or the triangle peg solitaire game. Clicking through these made them, if not a blast, at least bearable. Those interactions do make for an amusing transcript, though — hilarious amounts of our game log files are filled with sentences like “You move the 1-ugh weight to the center peg” or “You remove 1 pebble from Pile #3” or “You are moving the peg at letter D.”

Just as some concepts are much easier to express with a diagram than with words, so are some types of puzzles much easier to express with graphics. Infocom had long been on the record as disdaining graphics, and indeed, I still think text has a scene-setting power that visuals can’t match. Meretzky’s descriptions of Dimwit’s excessive castle have more pith and punch than a visual representation of them could possibly muster. However, a picture is so much better than a thousand words when it comes to conveying a complex set of spatial relations. Even as early as Zork III‘s Royal Puzzle, Infocom leaned on ASCII graphics to illustrate those spatial relationships, because that just works so much better. Once they had more sophisticated graphics available, the range of Infocom’s puzzles could expand. It’s ironic that the first thing they did was to expand backwards into older puzzle styles, but then again it’s probably a natural first step into exploring new capabilities.

Going along with the overall verve of the game, those old chestnut puzzles revel in their old chestnut-ness. Zork Zero is a veritable toy chest of object games, logic challenges (e.g. the fox, the rooster, and the worm crossing the river), riddles, and other such throwbacks. Of course, there are plenty of IF-style puzzles as well. (There’s plenty of everything, except noun descriptions.) Sometimes these could be red herrings too — all the Zorky references kept leading us to believe we might see an echo of a previous Zork’s puzzle. Hence, for example, we kept attempting to climb every tree we saw, fruitlessly.

The IF parts of the game don’t hesitate to be cruel, either. I’ve mentioned that every single Zork game made us restart at some point — well Zork Zero was no exception. In this case, it wasn’t a light timer running out or a random event closing off victory, but simply using up an item too soon. We found a bit of flamingo food early in the game, and fed it to a flamingo… which was a mistake. Turns out we needed to wait for a very specific flamingo circumstance, but by the time we found that out, it was far too late. This flavor of forced-restart felt most like the experience we had with Zork I, where we killed the thief before he’d been able to open the jewel-encrusted egg. The difference is that restarting Zork Zero was a much bigger deal, because we had to re-do a whole bunch of the game’s zillion tasks.

A screenshot from Zork Zero showing Peggleboz, its version of the triangle peg solitaire game

On the other hand, while this game does have a maze, it is far, far less annoying than the Zork I maze. In general, the design of Zork Zero does a reasonably good job of retaining the fun aspects of its heritage and jettisoning the frustrating ones. Except for that inventory limit — interactive fiction wouldn’t outgrow that one for a while longer. And while there are a couple of clunkers among the puzzles (I’m thinking of the elixir, which is a real guess-the-verb, and throwing things on the ice, which is a real head-scratcher), for the most part they’re entertaining and fun.

Before I close, since I’ve been talking about old-fashioned puzzles, I’ll pay tribute to a moment in Zork Zero which beautifully brought together old and new styles. As one of several riddles in the game, the jester challenges the PC to “Show me an object which no one has ever seen before and which no one will ever see again!” Now, we tried lots of solutions to this — air, flame, music, etc. — but none of them worked, and none of them would have been very satisfying if they had worked. Then, at some point, we realized we had a walnut with us, and if we could open it, the meat inside would certainly qualify as nothing anyone had seen before.

Then, after much travail, we were able to find a magic immobilizing wand, then connect that wand with a lobster, which turned into a nutcracker. After that it was a matter of showing the walnut to the jester to solve the riddle. That was a satisfying moment, made up of connecting one dot to the next, to the next, to the next. But it wasn’t quite over:

>SHOW WALNUT TO JESTER "True, no one has seen this 'ere me -- but thousands may see it in years to be!"

>EAT WALNUT "I'm very impressed; you passed my test!

That final capper turned a good puzzle into a great one — a solution that felt smart and obvious at the same time. Unfortunately, eating that walnut wasn’t enough to defeat Zork Zero‘s hunger puzzle. (Not a hunger timer, mind you — a reasonable and contained hunger puzzle.)

For that, we needed to become a flamingo, and eat the flamingo food. RESTART!

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

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

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