Once and Future by G. Kevin Wilson [IF-Review]

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

IFDB Page: Once and Future

Swords and Sledgehammers

Note: This review contains minor spoilers.

If we wanted to make a short list of the people who had a major impact on the course of 1990’s interactive fiction, who would we include? Graham Nelson, Mike Roberts, and Kent Tessman would have to be in, for creating the major development systems (and, in Nelson’s case, a couple of major games) of the decade. Adam Cadre and Andrew Plotkin would make the list, for contributing some of the most important games of that period and, in Plotkin’s case, for crucial technical innovations as well. We can’t forget Volker Blasius, Dave Baggett, and David Kinder for founding and maintaining the IF Archive. And there’s one more name we couldn’t leave off: Gerry Kevin “Whizzard” Wilson.

Kevin contributed lots of things, all of which have their roots in his boundless, unstoppable enthusiasm for IF. He founded SPAG, the IF review webzine that I now edit. He organized and ran the first IF competition, and shepherded it through its first few years, as it became one of the most dominant forces in amateur IF, as well as one of the engines powering the IF Renaissance we currently enjoy. He labored to make Activision realize the value of the Infocom properties they own, and as a result brought some fascinating internal Infocom documents into public view, and brought paychecks and publication to the winners of the first IF Comp. He gave us one of our legends, too. I refer, of course, to Avalon. Avalon was the game that Kevin announced in 1993, estimating it’d take a month or two to finish. Two months turned into six, into a year, into many many years. The game seemed to be Kevin’s bête noire, the place where his enthusiasm was an anchor instead of a sail. That enthusiasm led him to keep expanding the game, perfecting it, adding more and more, while at the same time hyping it relentlessly in his every Usenet post, of which there were quite a few indeed. “Avalon” became synonymous with “overhyped vaporware.”

Then, in 1998, it happened. Avalon was released, albeit retitled Once And Future (OAF), since the name “Avalon” was already trademarked by another game. The trademark mattered, because the game was released commercially, the first pure text adventure to claim that distinction since the Infocom era. The company behind this venture was Cascade Mountain Publishing (CMP), run by Mike Berlyn, former Infocom Implementor. OAF was CMP’s flagship product, a thirty-dollar game touted as the return of “quality interactive fiction.” The story from here gets short and sad, for CMP founders rather quickly and tanks quietly, in the process apparently torpedoing the release of the Inform Designer’s Manual (4th ed.) for a good long time. While sales figures for OAF have never been released, it clearly never took off. Finally, on April 1st of 2001 (with no apparent irony), OAF is released as freeware.

I was one of the people who bought the original, thirty-dollar package. In fact, due to a CMP blunder, I actually received two copies, the second of which I gave away as a prize in last year’s comp. But for whatever reason, I never quite got around to playing it until now. When I finally did play the game, the weight of its history and its hype couldn’t help but burden the experience. It’s impossible to say how I would have viewed OAF had it been released humbly, for free, by an unknown author, but I think my reaction would have been quite a bit different. As it is, I find it difficult not to make this review a laundry list of faults. This game, upon which so much hope was riding, about which we heard so much and for which we waited so long, is far from perfect. In addition, as a commercial product it begs comparison not only to its contemporaries, the graphical adventures of the late Nineties, but also to its Infocom predecessors. Whether these are fair comparisons I don’t know, but OAF suffers by them. In the light of these considerations, I hope to make my criticisms as constructive as possible, and to remember the invaluable contributions of its author, the obstacles that stood in the way of its creation, and the gaming era from which it originated.

In that spirit, I want to focus on some of the things I loved about Once And Future. First of all, that’s a great title, far better than “Avalon.” OAF, for those of you new enough not to already know, is the story of Frank Leandro. Frank is a young soldier in Vietnam who, after sacrificing his life to save his friends, finds himself entrusted by King Arthur to journey through the fairy-tale realm of Avalon, collecting mythically resonant items like Excalibur and the Holy Grail and, finally, traveling through time to prevent a Great American Tragedy. In other words, he travels to the land of Once Upon a Time, at the behest of the man T.H. White dubbed the Once And Future King, in order to obtain One chance to save the Future. Where “Avalon” was a flat description of the landscape, “Once And Future” evokes the game’s genre, its themes, and its literary ambitions.

Those ambitions are important too. Kevin started this game in 1993, a time when serious themes and literary content were the exception rather than the rule in text adventures. He used a heavily characterized PC in the face of rather overwhelming IF tradition to the contrary, and injected that PC’s own distinctive voice into NPC interactions well before Varicella and its ilk. Come to that, he used a gimmick in the very first few moves of the game that feels fresh to us even now, at least according to Shrapnel and No Time To Squeal. I’m not the first to observe that this game would have been considered quite revolutionary indeed had it been released in 1994 (as originally planned). Still, the point bears attention. I suppose it’s the IF writer’s curse that because we most often work solo and our work is so demanding and detailed, there is a tremendous gap between conceiving an idea and realizing it in its finished form, and during that gap any number of things may come along to steal our thunder. It’s no wonder that some IF authors hate to see concepts blithely discussed; I’m of the mind that execution is just as important as concept, but it’s got to sting to see your game’s ideas called old hat, when in fact they may have been stunningly original at the time you first began work.

The best part about OAF, though, is this: it’s fun. The game is genuinely fun for long stretches at a time. It’s a rollicking text adventure of the old school, offering wonderfully open-ended design and puzzles that challenge the mind and care little for how arbitrary they ultimately are. Once And Future‘s love for the Infocom tradition shines through continuously and, at times, the game’s sheer scope and its cleverness manage to hit the same high notes as its predecessors. As literary as it may aspire to be, OAF is a game first and foremost, and, although plenty of critical attention has been lavished on its story and writing, to me the real star of the show is the puzzles. [I’ll be naming several of these by way of example for those who have already played the game, but I don’t think it’ll spoil anything for those of you who haven’t.] There are lots and lots of them, and most of them quite enjoyable. Of course, many of them are rather easy as well, which for me coincides neatly with enjoyability. Freeing Merlin, obtaining Excalibur, and helping the old man are all examples of that pleasant sort of IF puzzle in which there’s an action that makes sense, I try it, it works, and I am made happy. Even some of the tougher ones provided me with time well-spent, like the diamond puzzle and the earlier parts of the Mountain King puzzle.

When the puzzles did go wrong, it often wasn’t because they were too difficult, but rather because the series of steps necessary to execute the solution was long and tedious. A perfect example here is the braziers — the concept is straightforward enough, and a helpful mnemonic is even provided (a very nice touch), but actually carrying out this concept entails a great deal of tedious tromping back and forth and mucking about with fiddly liquid commands. The problem here is that the fun part of puzzle-solving is the actual figuring out — the rest is just follow-through, and if made sufficiently involved, becomes drudgery. The lesson for designers is to keep the emphasis on the former, and make the latter fairly streamlined, or at the very least entertaining in its own right. The worst offender in this category was the business with the blue paste — there isn’t even any figuring out involved, just a lot of mind-numbing inspection of nearly-identical objects.

Another area where the puzzles run into difficulty is bugginess. I suppose that in the technical sense there aren’t any game-stopping bugs in OAF, but having the game actually fail to respond to a command its documentation specifically recommends (ASK MERLIN ABOUT SPIRITS) comes close enough in my book. In addition, the game isn’t free from guess-the-verb problems. In fact, the particular final puzzle I encountered (there are a variety of them, depending on the character’s inventory in the final scene) had me so stumped that I actually went onto ifMUD, found somebody who had a hint book, and determined that I had in fact figured out the right action (an action which was rather nonsensical in itself), but the game hadn’t recognized any of the several commands I’d used to get it across. Once provided with the right verb, I was finally able to reach the game’s ending. It’s just the sort of problem that’s bound to plague a large game, but that doesn’t make it any more excusable.

Okay, clearly I’ve gotten to the part where I discuss OAF‘s flaws, so let me cut straight to its biggest one: the writing. Now, let me be clear about this. It’s not that OAF is poorly written in the way that a Rybread Celsius game is poorly written, or in the way that the games that occupy the bottom third of the comp standings tend to be poorly written. On the contrary, most of OAF‘s prose is clean, error-free and basically serviceable. However, it is punctuated with serious problems nonetheless, not the least of which is its plethora of overwhelmingly maudlin, trite moments. Here’s a sample, from a scene in which Frank sees a Vietnam buddy vegetating in a hospital bed:

>X MARK
"Is this Mark?" you think, as you look into the vacant, staring eyes. His mouth hangs slack, and there are no signs of intelligence. Gone is the sparkle from his young brown eyes. He lies there, wasted and immobile, a monument to man's folly.

Lines like “a monument to man’s folly” and “gone is the sparkle from his young brown eyes” are, I’m guessing, supposed to evoke goosebumps and a solemn nod, but all they elicit from me are groans. I don’t think it’s that I’m so jaded and hardbitten — rather, the lines take a redundant, sentimental shortcut around genuine emotion. I’ve already been told that Mark’s eyes are “vacant” and “staring” — does the point that they’re not sparkling really need to be made? Similarly, making stentorian statements like “a monument to man’s folly” short-circuits any possibility of my reaching that sort of conclusion on my own, and inclines me instead to see the narrative voice as irritatingly grandiose. [By the way, I’ve no doubt that this sort of thing has shown up in my own writing from time to time, and I groan when I see it there, too.]

When the writing isn’t being overdramatic, it frequently strays into cutesiness. In fact, one of the very first things a player is likely to see (because it’s in Frank’s initial inventory) is a candy bar object called “Mr. Mediocrebar.” In case you’re not familiar with American candy, this is a jokey reference to a Hershey product called “Mr. Goodbar.” The problem with this isn’t whether the candy bar ever serves a purpose — even useless objects have their place in IF. The problem is with the name. Calling the candy “Mr. Mediocrebar”, a name that no actual candy would ever have, immediately undercuts mimesis. It’s as if the author is playfully nudging us in the ribs and saying, “Hey there, this is all for fun, just a game. None of it’s real, and you certainly don’t need to take it seriously.” This sort of approach might work in a light farce, but it jars horribly against the somber Vietnam setting and the Big Themes to come. Furthermore, because the candy bar may well remain in the player’s inventory for the entirety of the game, its name has this deleterious effect over and over again. Not to mention the fact that it makes players think of the word “mediocre” throughout the game, which is hardly desirable.

Worst of all, though, is what I call the Sledgehammer Writing. Here’s an example: the player is in the throne room of a mysterious ruler called The Straw Man. This ruler sits silently and impassively on his throne. While in the room, Frank hears someone approaching, and hides. It’s a woman who tells the Straw Man her problem; he doesn’t respond, and by talking it out, she solves it on her own, and leaves. Then this happens again. Then it happens yet again, and this time, as she cries on his lap,

out of the corner of your eye, you notice the first sign of movement from the Straw Man that you’ve seen. His arm slips from the armrest of the throne, coming to rest on her shoulder. Reaching up to grasp his arm, she continues to cry for a little while before regaining control of her emotions.

Okay, so we probably know what’s coming, right? Sure we do:

But when the Straw Man’s arm slipped from the armrest, you noticed something. The Straw Man is just a plain old scarecrow.

Dum dum DAAA! But wait, there’s more:

Kind of funny, really, that the best ruler, the wisest person that you’ve ever seen, turns out to be a dummy.

Okay, I get the point. But still more awaits:

But maybe it says something too. People don’t always want or need advice, sometimes they just want someone to listen to them, and hold them.

WHAM WHAM WHAM! HERE IS THE MESSAGE I AM GIVING YOU! It’s as if the game has so little trust in its readers that after making its point subtly, then blatantly, it feels that it still must spell the whole thing out in painfully obvious terms, just to make sure we get it. This sort of thing isn’t just cringeworthy, it’s insulting; OAF would have been so much stronger had a little restraint been shown in scenes like this.

Finally, sometimes the writing just suffers from a simple lack of clarity. For instance, at a point in the game when Frank has been transformed into a mouse, reading a magical scroll gives this response:

Your head begins to spin as you read the scroll. Your hands start to glow red and twist into a more human shape. You briefly ponder what would happen if you were to become a full-sized human inside this mouse hole. It’s not a pretty thought. The scroll quietly dissolves to ash.

When I read this, I thought: Uh-oh, I’m about to die. I’d better UNDO, then get out of this mousehole before I read the scroll. Problem was, I couldn’t leave the mousehole without dying. In frustration, I sought a hint from Google and finally realized that I had been misled — the above message wasn’t presaging that I was about to be crushed, but rather that a several-turns-long growing process was beginning and that I needed to exit the mousehole before the process completed.

Speaking of that mousehole, it’s a good instance of one of OAF‘s primary qualities: its expansiveness. This quality is both a strength and a weakness, in my view. Certainly in terms of the game as a whole, it’s a strength — one of the best things about OAF is how big it is. Unlike the bite-sized IF that dominates current output, this game is a five-course meal. Then again, there are times when the “more is better” approach is a bit more dubious. For instance, hanging on the wall of the initial location is a paper listing “Murphy’s Laws of Combat”, a list that’s twenty-five items long. This little touch adds a bit of authenticity and characterization, but it also presents the player with a large, somewhat jokey wodge of text to read at the beginning of the game (following immediately upon the game’s long and somewhat non-sequitur-ish opening text), slowing down the pace of a scene that otherwise moves very quickly. Then there’s the geographical expansiveness, of which the mousehole is such a perfect example. According to my maps (I made them in GUEMap and have uploaded them to the IF Archive), the underground area of OAF comprises no less than twenty-seven rooms. The only purpose of this area is to provide a couple of puzzles that lead to an item that (along with a different item from another area) lets you solve another puzzle that ultimately yields one of the main necessary items for your final goal. The great majority of these twenty-seven rooms serve no purpose for obtaining that item. They’re just there for… scenery, I guess, or perhaps to make the world feel larger. A couple of them support items that comprise one of the game’s several dangling plot threads, but that’s about it.

I don’t think this approach to IF map design is optimal. A few non-essential rooms here and there can be a good thing, fleshing out the landscape and making the world feel a bit more whole. On the other hand, when the majority of the map seems to be made of non-essential rooms, something is a little out of balance. This happened to me on my first game — I had a puzzle planned out that would require a sandy beach, and it made sense to have several beach locations. In the end I cut the puzzle, but couldn’t quite bear to cut all the locations. Not only had I toiled to produce them, I thought they gave the landscape a greater sense of completeness. Of course, the game was rightly criticized for having a lot of filler rooms, and I learned my first lesson in the importance of pruning. (And judging from the length of this review, I still have quite a few lessons to go in that particular curriculum.) If I were writing that game today, I’d let my descriptions and transitions do a bit more of the space-establishing work, and I’d be less afraid to get rid of things that didn’t really serve the game except as decoration. I can’t help but feel that such an approach would have benefited OAF greatly as well.

Another strangeness about the maps is how gridlike they feel. The game contains several large landscapes, and in most of them, only movement in the cardinal directions is allowed, even though there are no logical barriers to diagonal movement. The locations are apparently evenly spaced from one another, despite the fact that they may represent radical shifts in landscape, so that a beautiful forest might nestle up against a blasted heath, with no apparent transition between the two. The result is that the setting has a very mechanical, unnatural feel, a feel that repeatedly reminds us that we are playing a game rather than traversing a real landscape. Again, whether this works is a matter of context — the grid layout might be great for a science-fiction game where the landscape is supposed to seem rigid and mechanical, but it doesn’t do justice to OAF‘s more natural, outdoorsy setting. There are a few areas in which the map is laid out in a fun, clever way, but these are almost always in the service of a puzzle.

Aside from its maps, OAF has a number of design successes. The game is fairly open-ended, so that a variety of puzzles are usually available at one time. It combines a Zorkish “wide landscape” with lots of Trinity-esque “little areas” by having lots of separate wide landscapes, which gives the game a chaptered feeling without needing formal divisions. The bottlenecks between these areas tend to work pretty smoothly, though I was hugely frustrated at one point — I failed to obtain an item from one area to solve a puzzle in another one, and wasn’t given another chance to do so, forcing me to restore from quite a ways back. Still, that was the only time that the game closed itself off for me, and given the era from which it originated, that’s not too bad.

The design of the story wasn’t quite so elegant. I mentioned dangling plotlines, and there are quite a few of them. I got to the end of the game, and instead of feeling resolution, I said, “That’s it?” For one thing, that ending inserts a sudden romantic subplot that was utterly unbelievable because it hadn’t been developed at all in any of the rest of the game. Moreover, the conclusion left so many questions unanswered about things that happened elsewhere in the game, it felt quite unsatisfying. For example, at one point you have a friendly kitty accompanying you on your travels. Then, in the process of solving a puzzle, that cat becomes lost, and possibly hurt. And you never find out what’s happened to it, or if it’s OK. Designers, don’t DO this! If your story puts an animal or companion in jeopardy, establish its final status before ending the game! The cat is just one example — there’s also stuff down in the mousehole that seems to imply a story, but the story goes nowhere. Instead, that stuff is just sort of there. The line between subplot and background color is a fine one, and OAF crosses it more than once, I think without realizing it’s done so. Subplots need to be resolved by the time the game ends, or else players end up feeling like I did: cheated.

The other problem I had with the story is more philosophical, and I suppose more idiosyncratic. The final quest of the game involves traveling in time to prevent a historical event. It’s an event that actually happened, but according to the game’s version of King Arthur, the world will be doomed if it isn’t changed. To me, this sort of story is wrongheaded. The pieces of our history, both good and bad, are what comprise our current reality, and living in that reality now, I found it hard to swallow King Arthur’s assertion that my world is doomed. In fact, I found it a lot more persuasive to think that Frank was being misled by a demon in holy guise, and was nonplussed [Ed. note: based on the length of this review, I think not!] to see that the game wasn’t going in that direction. The abstract question of whether the world might be better had certain parts of history been changed is an interesting one, to be sure, but I wasn’t at ease getting a protagonist to do something that in all likelihood would have prevented my own birth.

On a technical note, the game hangs together fairly well, especially for a work of such grand scope. It’s only natural that despite the five-year gestation period, this game would have more rough edges than smaller pieces of IF, and indeed it does. There are several times at which OAF gives default responses that don’t make sense. These details probably should have been seen to, but oversights like that are forgivable. Similarly, there were a number of bugs here and there, but nothing overly catastrophic or distracting. I have to admit, though, that I was disappointed by the NPCs. After all, this is the game that won the 1998 XYZZY award for Best NPCs, but they all seemed rather thin to me. Mordred, in particular, in spite of being a crucial part of Arthurian iconography, has almost nothing to say, nothing to do, and spends the majority of the game, in Michael Gentry’s words, “just sort of irritably standing around as though waiting for a bus.” Even some of the supposedly more fleshed-out characters, such as Merlin, suffer from serious lacunae in their knowledge. I’ve already mentioned that ASK MERLIN ABOUT SPIRITS doesn’t work, despite the documentation’s promise to the contrary. There are also exchanges like this one, which took place in Stonehenge after Frank had seen some strange blue stones:

>ask merlin about stones
Merlin says, "There are a lot of stones here. Which one do you mean?"

>ask merlin about blue stones
Merlin says, "There are a lot of stones here. Which one do you mean?"

>blue
There's no verb in that sentence!

>ask merlin about blue
Merlin says, "Frank, I'm rather busy right now, can't that wait?"

>ask merlin about bluish stones
Merlin says, "There are a lot of stones here. Which one do you mean?"

>merlin, the blue ones, like I JUST $^%$ING SAID
I don't know the word "ones".

Or, similarly, when Frank has an unusual carved blue stone in his inventory.

>show stone to merlin
Which stone do you mean, the carved blue stone, or the flat stone?

>carved
Merlin isn't impressed.

>ask merlin about carved blue stone
Merlin says, "There are a lot of stones here. Which one do you mean?"

Thanks a lot Merlin, you’re a big help. There were lots and lots of gaps like that, and to make matters worse, Merlin’s default “I don’t know” message was “Merlin pretends not to hear you.” And you can’t even KILL MERLIN WITH EXCALIBUR.

I spent several weeks playing through Once And Future, and I’m not sorry I did. For one thing, it’s an important part of recent IF history, and for another thing, as I said before, it’s fun. Still, it was a bit of a letdown. I suppose that after the hype, buildup, and fanfare it got, it couldn’t help but be a letdown, at least a little bit. On top of that, it was no doubt to the game’s disadvantage that I played it in 2002. However unfair it might be to judge what’s essentially a 1994 game by 2002 standards, it’s impossible not to, because, well, it is 2002. Styles have changed, and parts of OAF haven’t aged well. The bottom line is that it feels like the work of a beginning writer, one who has promise and may have matured through the process, but whose novice mistakes remain. That doesn’t mean it’s not worth playing — it most certainly is — but don’t believe the hype.

Landscape and Character in IF [Misc]

[The following article was my contribution to the 2011 IF Theory Reader]

If we reduce interactive fiction to its essence, we can view it as a triangular relationship between three basic elements: Landscape, Character, and Action. It’s possible to write IF without objects, plot, NPCs or myriad other ingredients, but as soon as that first room description appears, it introduces a landscape, just as the first prompt ushers in the concept of Action.1 I would further argue that the interaction between these two elements inevitably creates some concept of Character. The character that emerges is the being that would perform the actions selected when presented with the landscape (and situation) at hand. Even if that character is not human, not organic, or not even embodied (an omniscient narrator, for instance, though that voice is almost never used in IF because of the form’s powerful insistence on connecting Action with viewpoint), Action must have an agent, and that agent is what we call the Player Character.

In this formulation, the only one of the triumvirate completely under the game’s control is Landscape. Action is entirely in the hands of the player, and Character lies halfway between the two. That last statement may require a bit more unpacking. If Character is determined by Action, why isn’t it entirely in the hands of the player as well? The answer is that while Action does determine Character, it isn’t the sole determining factor. The game itself can shape character by statements as blatant as “You’re Tracy Valencia,” or by something as subtle as a particular word choice in a parser response. However, I would contend that while blatant character-shaping statements and even subtle nudges from default responses are far from inevitable in IF, some sense of landscape must be included in any IF game, and that both the design and the description of this landscape are extremely powerful factors in determining character. It is my aim in this essay to examine the ways in which Landscape influences and creates Character, and to raise what I hope will be some interesting questions about the nature of their interrelationship.

MAP DESIGN

[This section contains minor spoilers for Adventure, Planet Of The Infinite Minds, Strangers In The Night, and Suspect. It contains medium-level spoilers for Lost New York and Stone Cell, and major spoilers for Shade and 1981.]

Space is continuous. The landscape of interactive fiction, however, consists of discrete units, connected to each other in various ordinary and sometimes extraordinary ways.2 By convention we call these units “rooms”, but in fact they can be anything from a tiny subsection of a room to an entire town, country, planet, or universe. How does a game’s subdivision of continuous space affect our perception of the character in that game? Let’s look at some examples.

An illuminating comparison exists between two pieces of IF with urban settings: Neil DeMause’s Lost New York (1996) and Rich Pizor’s Strangers In The Night (1999). In the former, the character travels through Manhattan and other areas of New York City during various points in history. The game frequently compresses neighborhoods, boroughs, and other such swaths of territory into single rooms, albeit lovingly described ones:

Lower East Side
The scene around you is one unmatched in any other time and place in human history: Acres of identical four- and five-story tenements packed cheek-to-jowl with people, people who spill out onto the sidewalks and fire escapes in search of a little space, a little air. The el tracks continue down the street to the north and south; to the east, the tenements seem to stretch on forever, though you're pretty sure they eventually end at the East River shore.

Within each time period, these areas connect to each other directly, even though they may have been separated by miles in reality. Occasionally, a “traveling message” such as “You trudge north for close to a mile, finally arriving at…” will interpose itself between locations, but more often the traveling interval passes instantaneously and without comment.

Strangers In The Night, on the other hand, painstakingly sets out its generic city map as a street grid, and provides almost no description for the lion’s share of its locations:

Broadway and 11th
You are at the intersection of Broadway and 11th Avenue. To the southwest is the security door for your apartment building; the Broadway Sineplex (which a few downtown residents still consider an amusing name for a movie theatre) lies to the northeast.

>n
Broadway (10th & 11th)

>n
Broadway and 10th
One of the streetlights is dim here; the shadows that are cast against the sidewalk are oddly deformed, giving the corner an otherworldly feel.

>n
Broadway (9th & 10th)
Somewhere in the distance, a car alarm starts blaring it's [sic] Call of the Wild to the concrete jungle. This is followed a few moments later by the sound of figerglass [sic] crunching and safety windshields shattering until the alarm ceases.

>n
Broadway and 9th

>n
Broadway (8th & 9th)

>n
8th and Broadway
Carl Tuck's Coffehouse [sic] is to the southeast.

At first glance, it might appear that about half the locations contain room descriptions. In fact, however, only the first and the last do; the dim streetlight and the car alarm are random atmospheric messages that can pop up in any street location. In fact, the only time a non-random message, or a description of any kind, appears is when the location adjoins the entrance to a puzzle-solving area, or to the PC’s home. The game’s city grid is comprised of about 80 locations, all of which may well have been compressed into one room in Lost New York.

It’s a natural impulse to discuss these choices as they relate to game design, or to talk about their successes and failures in creating immersion or facilitating strategy. What may not be so natural is to think about how these choices influence the way we think about the player character; I would contend that consciously or not, we perceive these two characters differently based on the way the games construct their surroundings. What we know about the PC of Lost New York is that she3 knows New York City well enough to identify its various areas instantly, even as they appeared over a hundred years ago. In fact, the game’s easy recognition of areas such as “The Goats” and “Ladies Mile”, not to mention the copious historical detail infused into many room descriptions, creates a tension between the game’s identification of the PC as “a tourist” and what we know about her from her subsequent experiences.

Someone who could wander through New York’s past with so much information at hand must be intimately familiar with the city, either through experience or study. Her interest and perception is mostly broad strokes — she’s more interested in generalities of an area than in its specific details, and her sense of history is sweeping rather than finely grained — but her knowledge is quite comprehensive. Even if the game had insisted that this was the PC’s first trip to the city, we would have to conclude that she is someone who for whatever reason has immersed herself in New York City history; how else to explain such detailed knowledge in the midst of the extraordinary experience of time travel? If the game proved unable or unwilling to address and resolve this question, that lacuna could hardly be anything but a flaw in the work, just as it would be in a novel where the main character knows things she shouldn’t.

Unlike the PC of Lost New York, the character in Strangers has almost no interest in ordinary detail, let alone history. He never finds himself musing about ironies or architecture as he treads the streets, and in fact usually notices nothing but the bare identity of the location. Together with the game’s specification of the PC as a vampire, these facts can lead us to a few conclusions about this character. He sees the city not as human tapestry or even interesting backdrop, but rather as a sort of maze he must navigate in order to locate prey. The lack of room descriptions impels us to move quickly from one location to the next, replicating the urgency of the character’s thirst for blood. His disinterest in local color might even be seen as an undead disdain for the fleeting effluvia of mortal life. The game’s overall presentation isn’t quite strong enough to give this effect full potency, but all the same we know quite well that there is a significant difference between these two characters. The Lost New York PC, even if she were a vampire searching the streets for prey, couldn’t help but notice the landscape and be aware of its heritage, while the Strangers PC could be thrust into any time in the city’s history and would evince a similar disregard for anything but the most minimal details of place.

On the other end of the detail spectrum from Strangers is Andrew Plotkin’s Shade (2000), where the entirety of the action appears to be taking place in the player character’s studio apartment. In this one-room environment, however, movement is possible, and the game responds to this movement not by placing the character in a new room (as is the case with most IF), but rather by making a series of alterations to room description and scope for the current room. If the PC is in the center of the apartment, for example, the game first mentions objects close at hand, such as the computer desk and stereo, while reserving mention of the kitchen and bathroom areas for the later parts of the room description. When that character moves to the kitchen, however, text about the counter, the refrigerator, and such occupies the beginning of the room description. The desk and stereo are still visible from that location, and still mentioned, but are only visible, not accessible for touching or other manipulation until the character returns to the center of the apartment.

When Shade was released, this approach to map design was hailed as an innovative subversion of the conventional IF map, which it is. It is also a fitting choice for characterization purposes. The overlapping, connected nature of the apartment landscape makes clear to us that this is an environment with which the character is intimately familiar, and that even while he inhabits one area of it, his awareness of the other areas does not abate. The map design makes the apartment belong to the character in a way that it would not were it separated into discrete rooms. This sense of familiarity, of safety, and of enclosure makes the game’s later revelations all the more powerful, as the familiar dissolves into the strange, and safe enclosure into fatal exposure.

A similar effect, the subdivision of one room into many separate locations, appears in a variety of games, including Infocom’s Suspect (1984) and Steve Kodat’s Stone Cell (1999). In the former, it’s a grand ballroom that the game presents as nine separate locations, and the effect is to make the room feel enormous. The character in Suspect is a reporter at a party being given in a mansion, and the game’s map design underscores her sense of awe at the opulent surroundings — where the house’s owner’s perception of the ballroom might be closer to that of the character in Shade, the guest’s mind demands more concrete conceptual boundaries in order to take in the scope of the area.

Stone Cell achieves a different effect by performing the same gridlike subdivision on a much smaller room, the eponymous stone cell. Room descriptions and common sense tell us that this room is much smaller than the ballroom in Suspect, so the game’s partitioning of that space, rather than conveying immensity, instead reflects the PC’s awareness of the room’s tiniest details as a result of his imprisonment. What makes this design particularly effective is that the game initially presents the cell as one location, then expands it into a grid after the character sleeps, thus reflecting not only the character’s growing familiarity with his surroundings but also his growing desire to scrutinize each detail of the premises in hopes of escape.

The opposite effect is available, too, when games compress the extremely large, even the inconceivably large, into a single room description. One of the more extreme examples of this technique occurs in Alfredo Garcia’s Planet Of The Infinite Minds (2000), where the character might find himself here:

The Beginning of Space
All around you, distant suns flicker and twinkle. Painfully bright points of light seem to appear suddenly from out of the ether, as another retracts into obscurity. En masse, the effect renders a carnival of vibrant colours and astonishing beauty.

The simple fact of the character’s existence in this location tells us something about that character: that she has transcended humanity, attaining a sort of bodiless, godlike status. Since the game starts with the PC as a simple librarian, its transportation of her to such an abstract vista carries with it the implication of personal disembodiment and removal from reality as well. What’s more, her ability to know that the location is “The Beginning Of Space” rather than, say, a Christmas tree festival viewed through a hangover, suggests a metahuman omnipotence that we must assume has been granted to the character, at least temporarily.

The connection between map design and character stretches to the deepest roots of IF, for the majority of Adventure‘s (1976) map is named and divided in ways that would make sense to a spelunker. From the way that the game comfortably names areas of the cave as “rooms”, and indeed even the names of those rooms, which draw on caving vocabulary such as “Bedquilt” and “Y2”, we can clearly identify that the character in that game is an experienced cave explorer. Thus, even in the earliest days of IF, when games made virtually no overt effort to characterize the PC, character was already emerging as a function of landscape. The character in Adventure, while unraced, gender-neutral, ageless, nameless, and faceless, was nonetheless made distinct from the player herself by the way he perceived the landscape of the cave, seeing rooms and twisty little passages where a different character might have experienced the area quite differently.

In the hands of a skilled author, the effect of landscape on character can make for a portrayal that is very striking indeed. Take, for instance, Adam Cadre’s 1981 (2001)4. The first room description of the game is as follows:

New Haven, Connecticut
New Haven. The worst place on earth. The town is dirty and industrial, the students are sloppy, everything is horribly expensive. And you had to cash in $3600 of your stock to get here. But it was necessary. Four years at this place is enough to ravage anyone. You have to rescue her, your first true love.

Her dormitory lies to the north.

Already, we can see a dramatic narrowing of scope occurring. The character is so unconcerned with the details of his location that he compresses an entire town into one unit, dismissing all of it as “the worst place on earth.” Then the broad outlines of location gain sudden, sharp focus: “Her dormitory lies to the north.” The contrast between the vague, reviled whole of New Haven and the focus on the dormitory, set apart in its own line, suggests to us that the character’s concentration on his goal is unhealthy, perhaps even obsessive, and moving north confirms this suspicion:

New Haven, in her dormitory
You're standing in front of her door. It's closed. It's always closed. You've shoved approximately one hundred poems and letters under that door. You figure she's probably read about half of them.

Scope narrows even further here, from one building to the tiny area in front of one of that building’s doors. The room descriptions certainly confirm our impression of the main character’s unbalanced and obsessive nature, but even without them, the basic funneling performed by the map design would get the point across admirably. When we discover that the PC is John Hinckley, Jr., and that the door in question is to Jodie Foster’s dorm room at Yale, the revelation is terrifically powerful, because via its map design, the game has already taken us directly into the viewpoint of its would-be assassin.

ROOM DESCRIPTIONS

[This section contains minor spoilers for A Change In The Weather, Heroes, Varicella, and Zork I. It contains medium-level spoilers for Once And Future and Wearing The Claw, and major spoilers for Nothing More Nothing Less.]

Of course, in 1981 it’s more than just map design that clues us into the character — the room descriptions themselves make it clear that we are seeing the game’s landscape as filtered through one individual’s highly idiosyncratic viewpoint. Short, choppy sentences give the text a jittery feel, contributing to the general tone of uneasiness. We know the character has some access to wealth because of the “$3600 of your stock” line. We also know the character is either a heterosexual male or a homosexual female from the reference to the true love as “her.”5 And we certainly know how he feels about New Haven.

Cadre is particularly skilled at bringing character across through room description, as in this example, the first room in Varicella (1999):

Salon
You've funneled the lion's share of the palace improvements budget -- and most likely the tiger's share as well -- into renovating the salon... not that the Philistines you live among are equipped to appreciate it. From the plush Quattordici chairs to the handsome volumes in the library to the imported Ming tea service to the steward you hired to attend to your grooming needs, this is an oasis of taste and comfort in what is otherwise a fairly uncomfortable and tasteless building. Ah, well. When you become Regent you'll have greater latitude to redecorate. The arched windows overlook the western gardens, while the exit leads east.

This description follows several paragraphs of introduction, which announce the player character as one Primo Varicella, Palace Minister to a recently deceased king, and Machiavellian schemer for the throne. Even without that introduction, though, this room description would frame the character aptly. From the “lion’s share” clause we know that the character is in charge of improvements to a palace, and from the room name we know that he is in the Salon mentioned in the first sentence; therefore we can conclude that he is employed by the palace in which the game begins — a succinct way to bring across Varicella’s position and occupation. Moreover, the phrase “live among” tells us that he resides at the palace as well. The “tiger’s share” clause gives us an example of his sardonic humor, and the “Philistines” reference an example of his snobbery. His identification of the chairs and tea service, and the contrast to the “uncomfortable and tasteless” remainder of the building, communicate clearly that this is a man of very strong preferences, a persnickety aristocrat whose refined tastes run to the extremely expensive. Finally, the character’s ambitions, and the drive behind them, are summarized neatly: “When you become Regent you’ll have greater latitude to redecorate.” Just by seeing one room through this character’s eyes, we learn all the essential facts about him that will carry throughout the game.

If there’s a continuum that measures the degree to which a game’s room descriptions blatantly shape character, it’s fair to say that Varicella is probably on the extreme end of it. Does that mean that the room descriptions of games on the other end don’t shape character at all? Predictably, my answer is no — the effect is just a bit more subtle. To illustrate, let’s compare descriptions from two different games, neither of which has character as its focus. First, from Andrew Plotkin’s A Change In The Weather (1996):

Rocky Outlook
A wide angular tongue juts out from the hillside. The park stretches off to the north and west, a vast expanse of luminous meadowland, patched with the dark emerald of forest. The streams are already shadowed in their beds. In the distance, a lake reflects red fire, beneath the greater fire that leaps silently on the horizon.

A trail leads southwest down the hill, towards the bridge. From where you stand, it turns southeast and continues upward, deeply cut into the hillside. A narrower trail leads more steeply up to the east.

Zork I (1981) by Infocom offers a location that is very nearly analogous:

Rocky Ledge
You are on a ledge about halfway up the wall of the river canyon. You can see from here that the main flow from Aragain Falls twists along a passage which it is impossible for you to enter. Below you is the canyon bottom. Above you is more cliff, which appears climbable.

Though their locations may be similar, these two characters are very different indeed. Weather‘s wanderer takes the entire first paragraph to describe the area with intense, poetic language. The words don’t directly narrate the emotions felt by the character, nor impute opinions like the descriptions in Varicella, but they deploy vivid adjectives like “luminous” and “dark emerald”, and powerful metaphors — the tongue of rock, the red fire of sunset reflected in a lake, the setting sun as a “greater fire that leaps silently on the horizon.” This is a character whose soul is moved by the grandeur of a natural landscape. Only after this reverent depiction does the character notice practical details: the trails and where they lead.

Zork‘s PC, on the other hand, goes directly for the practical. She mentions the river’s passage only in terms of whether she can enter it. What she notices about the cliff is that it is climbable. Though the natural scene — a canyon, a river, a waterfall — is probably quite impressive, the description is almost entirely mechanical. There are no rapturous sentences about the stark rock of the cliff or the sparkling river. Adjectives are almost entirely absent, and where they do exist their purpose is highly prosaic: “river” further identifies “canyon”, as “Aragain” does “Falls” and “canyon” does “bottom.” Other descriptors exist solely to describe travel options: “impossible” and “climbable”. Indeed, she sees every element of the scene only in terms of how it can be manipulated or traversed, and this viewpoint is consistent throughout the game, just as the intense description of natural phenomena is a constant in Weather. Both games’ main focus is puzzle-solving, but when we compare how their characters each view a similar scene, it becomes clear how different the characters are from each other.

Comparing the PCs of two different games illuminates important differences between the characters, and the effect is even more potent when several points of view are available within the same game — instead of seeing how two different characters view analogous locations, we get to see how they view the exact same location. Several recent games have made use of this technique: J. Robinson Wheeler’s Being Andrew Plotkin (2000), Stephen Granade’s Common Ground (2000) and my own LASH (2000) among them. The current apex of POV-diversity, though, probably belongs to Heroes (2001) by Sean Barrett. This game offers a minimal landscape of something like a dozen locations, but gives five different viewpoint options through which to view it. For instance, the opening location of the game as viewed by a Zork-like adventurer:

Temple Way
The grimy, ramshackle buildings of Oldtown dutifully try to reform themselves as you progress east down Temple Way, but nothing besides the temple itself makes any real pretense of belonging anywhere other than Oldtown. Or rather, nothing besides the temple and Baron Sedmon's nearby mansion.

a King:

Avenue
This broad avenue leads right into Temple Square, the heart of fabulous New Oldtown. Towering over the square to the east you do perceive your stark white Temple of Justice, beautiful and well-appointed, offering a statement to the neighborhood: this, this is what progress is about. Sadly, the buildings around you are scarcely up to this new standard; Baron Ventillado's house north of the square is much more satisfactory. How you hate having to come here. This would all be so much simpler if Blackhelm were found dead one morning, but it's never happened yet, despite your best efforts.

a thief:

Shadowy Road
Sturdy, functional buildings lie in and out of shadow on the road to the temple square. Simple architecture, devoid of handholds; closely spaced buildings, devoid of alleyways; uncut walls, devoid of windows: the builders in this area knew how to encourage amateurs to go elsewhere.

a mage:

East-West Road
Randomly arranged paving stones form this street, proceeding east towards a more attractive arrangement. The darkened buildings lean sloppily over the edge of the street, reducing the energetic potential of the strict east-west layout. West the road leads back into the seething mess that is Oldtown.

and finally, a dragon:

Open Tunnel
We were surrounded by the man-things' structures, structures of dead trees and rock and distortions of iron. Beneath us we felt the arrangements of stone into a path for man-things' mobile receptacles. We could smell hints of the Crystal along the path to the east.

Where the adventurer just sees a temple, the King sees the temple as his own possession, a symbol of his attempts to renovate and improve the city. Where the mage sees leaning buildings distorting the street’s pristine geometry, the thief sees those same leaning buildings as a source of precious shadow. Through the use of a past-tense, second-person plural voice, Heroes renders the dragon’s viewpoint quite alien, and emphasizes that dissonance by showing us how the dragon sees the street: an “open tunnel”, contrasted with the more irregular shapes of nature and constructed by contemptible “man-things.” Heroes takes excellent advantage of Landscape’s ability to reveal Character, and through its use of multiple viewpoints, it leverages the power of the Landscape-Character axis to accomplish something more: the revelation of Landscape via accumulated details from a variety of characters. The descriptions coalesce in the player’s mind to create a picture of the location that is much more complete than any one viewpoint could provide, while at the same time establishing distinct portraits of each viewpoint character.

Other games have made use of changing room descriptions in order to demonstrate change or progression in a single PC, or to give us that character’s revised perspective as a situation changes. Nothing More, Nothing Less (2001) by Gilles Duchesne is a case in point. The first puzzle of this slice-of-life game takes place in a bathroom, initially described like so:

Bathroom
I’ve seen bigger bathrooms, but must admit this smaller one suits our needs well. There’s a small sink with a cabinet under it, a mirror, a bathtub (equiped [sic] with a shower head and curtain) and a toilet.

However, after the character urinates6, the toilet clogs and begins to overflow. Unprompted, the game reprints the room description, which now reads as follows:

Bathroom
I’ve seen bigger bathrooms, but must admit this smaller one suits our needs well. There’s a small sink with a cabinet under it, a mirror, a bathtub (equiped [sic] with a shower head and curtain) and a toilet.
Right now, my attention is also grabbed by: the toilet tank. Water keeps flowing from the tank, nearing the bowl’s edge.

The room description stays the same, but the game adds a sentence to demonstrate that the character’s attention has become focused on one particular aspect of the room: the toilet tank. This sentence serves gameplay purposes, indicating that the toilet tank is in fact implemented and thereby hinting toward the solution of the “overflowing toilet” puzzle. In addition to this, the attention sentence demonstrates a shift in the character, showing us his revised perspective as well as the fact that he’s quick-witted enough to think immediately of the toilet tank in this crisis. The other sentence is typical of IF room descriptions, indicating an action currently taking place in the room and lending urgency to the character’s desire to solve the puzzle. After the character opens the tank, lifts the toilet float, and fixes the stuck valve to stop the toilet running (alas, too late to prevent water flowing onto the floor), the game once again reprints the room description, this time altered considerably:

Bathroom
I’m now standing barefoot in some icy water. I’ve seen bigger bathrooms, but must admit this smaller one suits our needs well. In fact, at this very moment I’m terribly glad the floor isn’t bigger, as it would only mean more water to remove. There’s a small sink with a cabinet under it, a mirror, a bathtub (equiped [sic] with a shower head and curtain) and a toilet.
Right now, my attention is also grabbed by: my towel.

There are several changes, doing several different sorts of work within the description. The first, the “icy water” sentence, indicates a change in the room itself, one that is reflective of situation rather than character, though of course the way the character chooses to relate this situation — emphasizing discomfort by noting his bare feet and describing the water as “icy”, conveying a mood of urgency without panic — does accomplish some characterization. A later sentence takes a fact of the bathroom addressed by earlier descriptions (its small size) and relates it to the new situation, revealing a practical and rather optimistic side to the viewpoint character. This sentence also demonstrates that the character’s perspective, while pragmatic, is not particularly scientific, since a larger floor wouldn’t actually mean more water to remove, only a greater surface area from which to remove it. Later, we get a new “attention” sentence; the toilet tank is no longer in focus, and instead the character is thinking of his towel. Note that this towel was not mentioned in any of the previous room descriptions, because the character had no particular need of it. Nothing More, Nothing Less makes extensive use of this technique, heightening realism by filtering not only the general experience of landscape through the PC, but also specific points of focus as well. Finally, once the toilet is plunged and the water toweled and mopped, the PC has showered, and his feline nemesis has entered the room, the bathroom’s description changes to this:

Bathroom
This a bathroom, of which I’ve seen more than enough in the last minutes. Come to think of it, I’ve seen enough of it for the whole day. And the presence of that hairy pest doesn’t improve my morale. Azrael licks one of his paws, while keeping an eye on me.

The character’s perspective on the bathroom has changed once more, marking the end of his progression from bland interest, through urgent focus, and resting finally at mild exasperation. The emotional registers aren’t extreme, but the room descriptions convey very clearly the changes taking place within the character as a response to the changes that occur around him. In games like this, Landscape does even more shaping of Character than usual by virtue of its changing prose.

A final aspect of how Landscape reveals Character lies in the concept of elision: what rooms does the game avoid describing, and how do those gaps influence our understanding of the character? Many games take the character, via non-interactive cut-scenes, or even simple transitions, through landscape that we never get to see from the PC’s perspective. My experiences as an author have taught me about this phenomenon; in my first game, Wearing The Claw (1996), I elided an entire sea voyage. In practical terms, I made this choice because I didn’t have the time, energy, or skill to implement the journey as an interactive experience, but its absence from the game couldn’t help but affect the PC’s characterization. His reluctance to relate the details had to be explained somehow, so I made him someone who is deeply intimidated by the ocean, someone who would want to block out the experience of being at sea as much as possible:

Soon you find yourself at sea for the first time in your life, and you learn that the rocking and swaying of a small boat on a choppy sea does little to relax you. Nausea swells and recedes like the the [sic] waves beneath you, and though the journey to the isle of the Goergs takes little more than an hour, it ends none too soon for you.

I’m not willing to make the claim that elision always contributes to characterization — sometimes cuts are in place just to serve a story’s structure, leaving things unimplemented even though the character certainly would notice them. However, there are times that what isn’t described is just as important as what is. These sorts of gaps are particularly noticeable when they contrast with the player’s expectations, as happens from time to time in Kevin Wilson’s Once And Future (1998). One particularly memorable absence in that game is the matter of the cat: late in the game, Frank Leandro (the PC) is required to obtain a bit of cat hair for a magical recipe, and conveniently enough happens across a stray cat who sheds a bit into his hand and rides his shoulder for a while. A while later, that cat jumps into the chimney of a boarded-up house (chasing a bird) and disappears. Frank has a sword that cuts through anything, but the game forbids him from cutting through the boards to find the cat, saying “You could, but there’s not much point to it.” So however much the player may want to make sure that the kitty is okay, she is constrained by Frank’s disinterest; the inside of the house isn’t part of the map, because Frank doesn’t see the point of exploring it.

A PC-CENTRIC VIEW OF INTERACTIVE FICTION

[This section contains minor spoilers for The Beetmonger’s Journal, medium-level spoilers for Hamlet (the Shakespeare play), and major spoilers for Photopia.]

It’s possible that objections may arise to some of the points I make above, on the grounds that what I ascribe to character could just as easily be seen as a particular author’s writing style, a game’s depth of implementation, or even the formal constraints of IF itself. It’s quite true that I’m taking a PC-centric view — this is how I experience interactive fiction, and it’s easy to feel that it’s simply how the form works, but I certainly acknowledge that there are other, equally valid approaches. It’s also true that the PC is not the only possible point of view within a work of Interactive Fiction. In The Beetmonger’s Journal (2001) by Scott Starkey, for instance, some very nifty POV-jumping occurs in sections where the PC is the hero of some stories being read by the frame characters — from time to time those characters are interrupted in their reading, and we get a small cut-scene from their point of view.

However, what I would argue for is the extreme difficulty of disconnecting the point-of-view from the Player Character at the point of action. The IF prompt implies a certain kind of remote control: the player is to type in an action which will then be executed within the game. Invariably, this action is performed by the PC. Indeed, this is the very definition of Player Character. Similarly, landscape descriptions, especially when that landscape is available for traversal and manipulation from the game prompt, almost cannot help but be filtered through the PC, because all the knowledge conveyed in them is available for use at the point of action. If room description were to convey something that the PC couldn’t possibly know, such as the color of an object when the character is blind, the result would be severe cognitive dissonance for the player. If we type “OPEN BLUE DOOR” and the blind PC is able to do so, we must conclude that the PC is not blind after all — that’s how powerful the connection is between Character and Action. Because Landscape, Character, and Action are so intimately connected, it’s quite difficult to avoid making Landscape a function of Character, especially as the two get nearer and nearer to Action.

Given this PC-centric take on IF, it’s worth asking what possibilities reveal themselves as open or closed in its light. We’ve already seen some of what’s opened, from Heroes‘ cumulative place-building to Shade‘s resonant evocation of the familiar, and no doubt future games will continue to explore the power of the Landscape-Character axis. Conversely, one element that seems rather alarmingly curtailed is the possibility of dramatic irony. For instance, imagine Shakespeare’s Hamlet as an IF game, in which the player controls Hamlet, but is allowed (as a reader) to see Polonius stepping behind the arras in the queen’s bedroom. In order to retain the dramatic irony of the scene, Hamlet must stab the arras and inadvertently kill Polonius, but why would the player order him to do so, knowing what Hamlet doesn’t? In other words, how can the player be allowed to know things that the character doesn’t if that knowledge is expected to facilitate dramatic irony? The only answer I can think of is to force the PC’s actions, to make Hamlet stab Polonius no matter what the player orders, but as soon as that happens, the interactivity drops out of the IF game, and thus Action is removed from the equation. I’m not prepared to contend that this sort of dramatic irony is impossible, but the game that solves this problem will be a major breakthrough.

The work that’s probably come the closest to this grail is Adam Cadre’s justly revered Photopia (1998). Thanks to its fragmentation of the narrative line and its array of POV characters, when the climactic scene arrives, we know all the awful freight of what’s about to happen. We also can’t stop it — in order to achieve its dramatic irony, Photopia must remove our power to act. There’s an argument to be made that this sort of moment becomes even more powerful in interactive fiction, the useless prompt underscoring the inevitability of the character’s tragic fate. That’s as may be, but it doesn’t change the fact that PC and Action are still inextricably connected, and the only way the PC can be made to do something inevitable is to remove control from the player. Photopia cleverly makes the inevitable moment a car accident, thus giving the PC only a split-second to react (and thus providing a plausible context for lack of choice) and making his default desires identical to the player’s desires (STOP THE CAR!), but in the final analysis, the moment is still achieved by removing control from the player, and indeed the great majority of the criticism directed towards Photopia has been of its non-interactivity.

If Action is to retain its place in the IF triangle, Landscape and Character must remain inextricably connected. Their powerful bond to each other creates many exciting possibilities for the development of both, possibilities that have begun to be exploited in the last several years, and which no doubt will continue to yield opportunities for development. What’s also true is that noticing this connection and its potential still only scratches the surface of character development and landscape exposition in IF. Character can be revealed not just through landscape, but through objects, plot, direct narrative, and many other devices. In turn, while character is the primary lens for landscape, that landscape can alter greatly from the passage of time, from plot events, from NPC actions, or hundreds of other vectors, and each change to character and landscape deepens both. We’ve only just started finding the techniques, and it’s a heady feeling. We’re at the beginning of an art form — there’s much more undiscovered territory to explore.

Endnotes

1 A note about terms here: First, I should note that by “interactive fiction”, I refer to text IF. Some of the points here are certainly applicable to graphical or mixed-media IF as well, but some may not be. Secondly, the general concepts of Landscape, Character, and Action aren’t meant to be taken too literally. IF could be (and in many cases has been) created with a map of entirely abstract locations, or one location, or location descriptions that consist entirely of describing what’s absent. Similarly, actions might involve no actual action (WAIT, for example, or THINK), and a character can be anything from an intrepid adventurer to an ear of corn. However, I would contend that these elements are present in some form in all IF — indeed, the absence of these elements (such as the absence of landscape in Eliza) removes the work from what might reasonably be called interactive fiction.
[Back to reference]

2 This trait isn’t entirely restricted to text games, but while no text game offers continuous space, some graphical games, such as Half-Life and Zork: Grand Inquisitor, do in fact offer a continuous, unbroken environment through which the PC travels. In that case, map design becomes a much less powerful factor in fixing Character, and in fact it might be argued that in those cases, the term “map design” has more or less lost its meaning, and might be better called “level design” or something similar.
[Back to reference]

3 The subject of how description influences our perception of PC gender could occupy another entire essay, and is out of scope for this one. Consequently, in the case of games that don’t explicitly specify the gender of the PC, I’ll rather arbitrarily select one, trying to hit a more or less even ratio between the two.
[Back to reference]

4 1981 is credited to the pseudonymous A.D. Mcmlxxxi, and Cadre has never claimed credit for it. In private correspondence, he explained that this is because the game was a bit of a rush job, not polished enough for something he would put his own name on. He agreed to be credited for the game in this essay on the condition that I put in a note explaining that he “wasn’t actually trying or anything with that one.” That 1981 is the game Cadre produces when he isn’t even breaking a sweat is a testament to his skill as an author.
[Back to reference]

5 Or a bisexual of either sex, it probably should be said.
[Back to reference]

6 This is one of the very few times that excretion has appeared in an IF game without being a function of rather dodgy toilet humor. Instead, the game plays it completely straight — just another element in its realistic scenario.
[Back to reference]

Unnkulia X by Valentine Kopteltsev [Comp00]

IFDB page: Unnkulia X
Final placement: 27th place (of 53) in the 2000 Interactive Fiction Competition

In the beginning, there was the 1995 IF competition. This competition had but One Rule: all entries must be winnable in two hours or less. The competition has gotten grander and more complex since then, but it has remained a competition for short games, not Curses-length epics. Somewhere along the way, though, the One Rule got mutated a little. I quote from this year’s rules: “Judges must base their judgement of each game on at most the first two hours of play… Authors may write a game of any length they desire, but should keep this rule in mind when determining the length of their entry.” This rule has been in this form, more or less, since 1998. Still, the competition has remained oriented towards short games.

There are some obvious reasons for this. For one thing, it takes less time to write a short game. The more objects, locations, NPCs, plot points, and such you cram into your game, the more work your game will be to produce, at least if you want to maintain a reasonable level of quality. I would argue, however, that there are other reasons to keep long games out of the competition. From a judging standpoint, I don’t feel comfortable evaluating a game unless I’m reasonably confident that I’ve seen most or all of it. If A Mind Forever Voyaging, for instance, were to be entered in an IF competition, I know for certain that I wouldn’t have an accurate picture of it after only 2 hours of play. I felt differently about Zork III before and after the Royal Puzzle. I could go on, but you get the idea. Consequently, the ratings given to a large game don’t really reflect the game as a whole, just its beginning sections. Also, it’s really comparing apples to oranges to put something like Worlds Apart up against something like, say, Winter Wonderland. Even if two games have a similar tone, or similar puzzles, or a whole raft of other similarities, length does matter. Ahem.

Nowadays though, the competition has become, to use a worn-out but apt phrase, a victim of its own success. Authors enter anything they write into the competition just because it’s so high-profile and receives so much ink (or electrons, or whatever.) They figure that even in the worst case, they’ll get a whole bunch of people playing and writing about their game, so why not enter it? I feel a rant coming on about this. The first part of my rant is directed at authors. Look, people, entering a game that is too long (or too buggy, or too poorly proofread, or otherwise inappropriate for the competition) is an abuse of the judges’ time. The feedback and recognition you get this way are ill-gotten.

Moreover, I would contend that especially in the case of overlong games, you’re not really benefiting that much, because whatever recognition and feedback you get are only based on the first two hours, not your game as a whole. You created an entire game, but if it’s just one of fifty entries, and it’s quickly apparent that two hours ain’t gonna cover it, not by a long stretch, how many of those players do you think will return to your game? How many people will see and give you feedback about the other three-fourths of the game that they didn’t get to during the comp? How much are you really benefiting from all that comp attention?

And while I’m on the topic, let’s move to the second part of my rant, which is directed to the community at large. Listen, I love the competition. It’s one of my favorite things about the IF community. But let’s face the problems that it has. The magnetism of the competition, the idea that it’s the best place for every game, is something we all need to work harder to address. Do your part. Release a long game (or a short one) outside of the competition. Write a review of a non-comp game for SPAG or XYZZYNews. Participate in things like the IF Review Conspiracy and the IF Book Club. Most importantly, post post POST about non-comp games. Make a commitment to post a reaction to any non-comp game you play. It doesn’t have to be a review. It doesn’t have to be thorough. Hell, it doesn’t even have to be smart. It just has to be done, because if it doesn’t get done, the authors who don’t abuse the competition will end up losing out, and that’s not right. So please — do it. Your efforts will benefit yourself and everybody else in the IF community.

Just to be democratic, the third part of my rant is addressed to myself, and people like me, people who write long, thorough reviews of every comp game. We are part of the problem. I recognize that consistency is important to us, and that’s why we devote more or less the same amount of space to each comp game. However, there can and should be limits. Don’t even play games that have catastrophic bugs, let alone review them. Any attention those games get contributes to the perception that it’s better to release a buggy game in the comp than a polished game in the Spring. We must work to prove that this perception is fallacious and untrue. As for overlong games, review them if you feel you must, but don’t feel obligated to spend much of the review talking about the game itself — spend it instead on some adjacent topic like the problem of inappropriate games in the competition.

I mean, for god’s sake, Unnkulia X is 865K! The thing is only 45K smaller than Once and Future! It’s freaking huge! Yes, it’s fairly well done, implemented with care and only a few lapses in English. (There’s a lot of unfamiliar diction, which I assume is attributable to the author’s first language being something other than English, but most of these alien word choices are rather refreshing instead of jarring.) Of course, I only got 60 points out of 300 after two hours, so these assessments are based on what I have to assume is the first fifth or so of the game. If it were the whole game, I’d probably give it about a 9. Considering it’s a fifth of the game, I think that works out to about a…

Rating: 1.8

Aftermath by Graham Somerville [Comp00]

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

Sometimes a comp game can be summed up in one word. Of course, that never stops me from going ahead and writing three paragraphs about it anyway, explaining why that word fits, but for those with a distaste for verbosity, that one word can be a handy precis. Aftermath is such a game, and the word, I’m sorry to say, is “dismal.” The game’s topic is war, and not the glory of triumph in battle or the allure of military machinery, but the dismal, dismal existence of lone soldiers on frost-covered battlefields, struggling out from under heaps of bodies and fighting off the human vultures who scavenge through the corpses’ belongings.

This topic, by itself, is quite a downer, but still could be the basis of an excellent game. Unfortunately, Aftermath‘s dismal characteristics don’t stop there. The writing is dismal, the grammar is dismal, the spelling is dismal, the coding is dismal, and the puzzles are beyond dismal. Run-on sentences and other grammar bungles are everywhere, programming errors are legion, and there are as many spelling mistakes as dead bodies. (And with this game, that’s really saying something.) In fact, after I finished the game (with an inexplicable 120 out of 100 points) and received the ending message, I found myself still at the prompt. When I typed “L”, the game said “It looks like an ordinary to me.” I still had all my possessions (including “a apple”), but was trapped in a bizarre post-game limbo. It was almost as hard to figure out as some of the game’s puzzles.

Oy, those puzzles! From the very beginning of the game, I quickly determined that guessing the verb, as well as the noun, was going to be necessary in numerous cases. On top of that, several times very particular objects (or sub-objects) must be examined before the game will reveal things that, by all rights, should be dead obvious (pardon the pun) to the PC. Sadly, that’s not even the worst of it. There’s one puzzle in particular that made me say to my monitor, “How in the hell was I supposed to know to do that?” My monitor never answers me when I ask it that kind of stuff — probably for the best, since it’s not the kind of question that really has a good answer. I’d be quite surprised to learn of anyone who solved all the puzzles in Aftermath without the walkthrough, because not only do they require reading the author’s mind, but they occasionally fly in the face of all logic and sense as well.

The real shame is that an IF game in the war genre could be so good, and Aftermath falls so short of its potential. Heaven knows there’s a ton of inherent drama in war, drama that works from Henry V to Platoon have mined to spectacular effect. What’s more, it’s the kind of genre we don’t see very often in IF, which tends to be more or less dominated by science fictional and fantastic themes (a trend to which I’ve made my share of contributions.) Once and Future starts out in a war, but quickly shifts into Arthurian Fantasy mode. Remembrance delves into WWI, but in a way that could hardly be called interactive. In fact, the only memorable IF game in the war genre I’ve played is Persistence of Memory, which leaves great swaths of territory still untouched.

Aftermath, unhappily, can only manage to come up with gratuitous gore and relentless dreariness, sprinkled throughout with wince-worthy histrionics and unintentionally funny English and TADS errors. It’s all the more disappointing, because the game could have been so moving. Aftermath has a very solid theme, and its basic plot engine, the idea of a character who is the sole survivor of a battle and is obsessed with building a monument to the dead, could have made for a dynamite story. Aftermath isn’t that story, though. Instead its only success, as well as its disappointing failure, lies in the fact that it is just so dismal.

Rating: 3.1