Bane Of The Builders by Bogdan Baliuc [Comp01]

IFDB page: Bane of the Builders
Final placement: 28th place (of 51) in the 2001 Interactive Fiction Competition

In what is either a shameless rip-off or an unwitting duplication of the Heechee backstory behind the Gateway games (and novels), this game posits a “mysterious race known as the Builders [who] had left many traces and artifacts throughout the galaxy.” The game opens as a planet has been discovered that might yield the secret of the Builders’ demise, though it’s unclear how the simple existence of “an energy source” would promise such vital information. No doubt the answer could be supplied by the foremost expert on Builder civilization, a fellow known only as “the Professor.” (I was torn as to whether to picture him as the Professor from Futurama or the Professor from Gilligan’s Island.)

The PC’s role is that of a starship ensign who has become “quite friendly” with the Professor (though apparently not friendly enough to learn a first or last name), and who is sent down to accompany said Professor on his investigative mission in this Builder artifact. Now, it can fairly be said that this scenario is rather illogical — would a lowly ensign really be the only one to accompany a scientist on such an expedition, and if so, would he really be asked to wait around in the ship instead of providing armed support, and would he only start worrying after the Professor goes missing for almost a day?

However, such objections aside, I enjoyed the setup of this game. It felt pleasurably reminiscent of sci-fi juveniles from the 1940s and 50s, right down to the cheesy idioms uttered by the characters. (“Thank Space you’re here!”) I especially enjoyed how Star Trek and its clones have become so ingrained in the culture that when the game provided a blaster “set to kill”, I knew that “SET BLASTER TO STUN” would work, even though the game provided no explanation of the blaster’s settings. It worked. Unfortunately, letdowns occur throughout the game that prevent it from being a fun romp through Golden Age and TV sci-fi tropes.

The problem isn’t with the writing, which is pretty serviceable throughout, even earning extra points from me for using “its” and “it’s” correctly the entire time. The formatting is fine too, although it seems to miss a few blank lines here and there. The implementation, on the other hand, is a bit more deeply troubled. Several times, the game seemed to want to produce the effect of the room’s contents shifting in front of the PC’s eyes; the room description would print, then a line reading “The world around you suddenly shimmers and changes…”, encased with blank line or two on either side, and another room description would print. So far, so good.

Except that sometimes, the descriptions were identical. Other times, a third room description would print after the second one, with the “shimmer” line printing without blank lines preceding it. I doubt this was intentional — it’s a feature that needed more testing before the game’s release. Another serious problem is that in a climactic scene, the most important object is unimplemented. I was more than a little nonplussed to be told about a Nasty Evil Menace by the game, but to be told, “You can’t see any such thing” when I asked to examine the Menace.

The biggest problem, though, is the puzzles. First of all, there’s a maze. There’s no redeeming twist to make it interesting or better — in fact, the only twist makes it worse: the maze doesn’t use compass directions, instead relying (quite arbitrarily) on “left”, “right”, “forward”, and “back” instead. Consequently, you not only need to keep in mind where you are in the maze, you have to keep in mind which way you’re facing. This is the sort of thing that feels a lot more like work than fun to me in a game.

Perhaps even worse are a couple of authorial telepathy puzzles, which demand highly implausible or even nonsensical actions to solve, and offer no clues whatsoever as to these solutions. I’m not sure whether I object more the puzzle whose solution seems impossible based on its object’s description, or the one whose solution is just totally illogical. Either way, having them both in the same game is not a good thing. I have sympathy for people who struggle with puzzle design, because I’m one of them. But it’s better to have no puzzles at all than puzzles that aren’t any fun.

Rating: 5.2

Lovesong by Mihalis “DarkAng3l” Georgostathis [Comp01]

IFDB page: Lovesong
Final placement: 48th place (of 51) in the 2001 Interactive Fiction Competition

This game was my first introduction to the Quest development system, and I wish I could say I was impressed. I mean that. I’m all for people using their skills to create IF stuff that’s new, cool, and functional. What I can’t get very enthusiastic about, though, is people using their skills to create IF stuff that isn’t as good as stuff that already exists. Sure, Quest looks nice and everything. But unless the author of Lovesong broke or disabled something, its parser is less sophisticated than, say, that of the first Monkey Island game. Based on the help text, the parser seems to understand 19 verbs. Counting synonyms. And 9 of those are directional commands. And another one was (I think) added by the game’s author.

Such simplicity allows the game to be almost completely mouse-driven (or it would if the mouse support didn’t break halfway through), but really… what’s the point of that? It’s one thing to present a mouse interface in a graphic adventure, but a text adventure? Why? Legend tried it, but I can’t imagine that many people actually played all (or even most) of any Legend text game using the mouse alone. I guess it cuts down on guess-the-verb, but really, is the gain worth the price?

It seems to me that what Quest allows people to do is to create text games with the interface of a graphical game. To my mind, that’s a pointless endeavor — it deprives text games of one of their major strengths, and adopts a “hands-off-the-keyboard” aesthetic from graphical games that has a stultifying effect on game design. The worst of both worlds. No doubt Quest has some features unused by Lovesong, and those may go some distance toward making it useful. But ultimately, I don’t think that any nifty features are going to make a big difference. You know why? Sure you do: THE PARSER IS MORE IMPORTANT THAN THE NIFTY FEATURES. Same old song.

Of course, no matter what development system had been used to write this game, Lovesong would still be deeply troubled. The big problem here is English. Apparently, English is not the author’s first language. As the game’s author bio asserts, “Please forgive me, but me English are not fluent enough. I pray that some mistakes won’t ruin your gaming experience.” Well… sorry, but it’s really hard to enjoy a text game written in broken English. (Unless the English is broken on purpose, a la Gostak or For A Change, but that’s a different matter entirely.)

In fact, I have to wonder: if someone isn’t fluent in English, but wants to create a game, should that game really be a text adventure in English? I’ll probably get flamed for that, and really, I don’t mean to be some kind of Guardian of IF Purity, but a text adventure is a piece of prose, just like a novel, short story, or poem. If you’re not fluent in a language, how can you possibly craft a good piece of prose in that language?

Maybe it can be done, but Lovesong isn’t it. Its plot is sorta sweet, but the whole thing is so hampered by the twin burdens of its straitjacketed development system and its badly mangled writing that there’s not much opportunity to enjoy anything else about the game. In addition, it has its own implementation problems, though it’s always hard to tell what’s the game’s fault and what’s the system’s fault. Several times, the game just had no response at all to a command. About halfway through, the mouse buttons stopped working. Towards the end, the “save” command stopped working. Oh well — at least I can now say I’ve tried a Quest game.

Rating: 2.1

Lunatix: The Insanity Circle by Mike Snyder [Comp99]

IFDB page: Lunatix – The Insanity Circle
Final placement: 12th place (of 37) in the 1999 Interactive Fiction Competition

Early on in Lunatix, I typed “X TUKE.” The game responded, “It looks just like you might have expected.” Of course, there’s no “tuke” in the game — I meant to type “tile” but my right hand had strayed a bit from its accustomed spot on the keyboard. I’m glad it happened, though, because the incident taught me something important about Lunatix: its parser pretends to understand more than it does. In my book, this is a big no-no. In fact, if I ever write a Parser Manifesto, my first principle will be, “Parsers must not pretend to understand more than they do.” Even a fairly innocuous violation of this rule, Inform’s famous “You can’t see any such thing,” has caused no end of debate on raif. When a game pretends to understand more than it does, you can never really be sure when you’re encountering a bug, because bugginess has been built directly into the interface.

What’s more, it’s a cop-out. Instead of doing the often tedious work of creating descriptions for the available objects, the game elides the absence of these descriptions by acting like it recognizes them when it doesn’t. As a player, I find this pallid deception infuriating. Unfortunately, Lunatix‘s parser does something even more infuriating, which has led to the formation of the second principle in my hypothetical Parser Manifesto: “Parsers must not give smarmy, unhelpful error messages.” My encounter with Lunatix was filled with exchanges like this (the words after the ellipses are my input):

...FILL WATER GUN
Your logic, although interesting, is flawed.
...TURN ON FAUCET
That's a pretty crazy idea, but it didn't work.

These kinds of responses make me want to scream obscenities at the game, and sometimes I did, along with feeble protests like “No it isn’t! Wanting to fill a water gun with water is not flawed logic! Turning on a faucet isn’t a crazy idea!” Then I remembered that talking to yourself is a sign of impending mental collapse, so I stopped. But my blood pressure stayed high.

The problem with this kind of message is that the game is willfully occluding its own shortcomings at the player’s expense. Error messages that insult the player, when in fact it is the parser that has failed, piss me off. I’d so much rather see the game say “I don’t know that verb” or “You can’t fill that” — that way I know exactly what hasn’t been implemented, and that knowledge will be useful to me throughout the game. Instead, Lunatix sneers at me and acts like its flaws are my fault.

Which brings me to the third principle of my Parser Manifesto: “Parsers must not ask questions without being prepared to receive an answer.” I had lots of exchanges with the game that went like this:

...POUR CPU
What are you trying to pour out?
...CUP
In a perfect world, that might have worked.
...POUR CUP
You empty the cup's contents onto the floor.

OK, so I made a typo in my first command, and the game asked me a disambiguating question. Fair enough. But wait! Further evidence reveals that the question only appeared to be for disambiguation. Actually, the parser wasn’t asking me a question at all, but giving me a message along the lines of “I only understood you as far as wanting to pour.” By phrasing that message as a question, Lunatix tricks me into thinking it is following the standard set by every other major parser: ask the player a question and process the answer. Instead, it’s only prepared to follow through with the first half of that standard, and gives me a snippy error message in the bargain. Grrr.

These kinds of problems have been more or less eliminated in the default library parsers used by most major IF tools, but Lunatix doesn’t use one of those parsers. Instead, it is a “homebrewed” creation written in (from what I can glean from the readme) QBasic, and presenting a radically different interface than most IF games do. The game splits the screen into four windows: the top half of the screen is split vertically between a square graphics window (displaying a picture of the current room) and a square text window, which always displays the textual description of the current room. Taking up most of the bottom half of the screen is a rectangular text window, which displays the game’s responses to the player’s input. Below that, a frame around a one line text field, is a window for the player’s input. It’s a bit reminiscent of the Legend interface, except instead of a compass rose and clickable command menus, there’s just a room description next to the graphic.

The graphics themselves are grainy and pixellated (or at least, they were on the two monitors I used to play the game), but still manage to be appropriately atmospheric at times, and even rather attractive once in a while. More importantly, they add significant content to the game — there are some objects that would be difficult to envision when described in text, but the presence of the graphic clarifies the setting a great deal. The window with the textual room description was nice, too, as it allowed systematic examination of the first-level nouns without having to periodically “LOOK” to remember what those nouns are. Of course, the game doesn’t actually implement most of these nouns, but that’s not the window’s fault.

The only difficulty I had with this window is that it didn’t always automatically update when something drastic had changed about the room, unless I explicitly typed “L” again. Thus, after solving a puzzle I might see a picture of a normal hallway, while the description alongside it raved about the giant squid blocking my path. In addition, lots of keen features were implemented in the interface, like command recall with the up-arrow, splash screens at the beginning and end of the game, a weirdly pulsating cursor, and nifty sound effects. So I can say with certainty that Lunatix is the most technically competent homebrewed game in the competition, perhaps even the most technically competent homebrewed game in the history of the competition. Unfortunately, all the snazzy windowing and gee-whiz effects in the world don’t really make up for its substandard parser.

The other part of the game’s core, its story, is OK. It’s one of those IF scenarios whose premise rationalizes why it is full of patently ridiculous things. In this case, you’re the unscrupulous director of an insane asylum and you’ve been given a drug which replicates insanity. This is a cozy explanation for why nothing you see really makes any sense, and seems to be just a setup for lots of different code and one-use-object puzzles. These puzzles are mostly OK, too. They’re more or less logical (within the confines of the completely nonsensical story) and, with one or two exceptions, pitched at the right level of difficulty. There is one real howler towards the end which makes almost no sense but will be deeply appreciated by fans of The Penguin on the old Adam West Batman show.

So in other words, the story and puzzles aren’t great, but they aren’t terrible either. Unfortunately, the combination of fair-to-middling plot with really-irritating parser makes the game less fun to play than it should be. See, (he said, mounting his soapbox) an IF game is a fusion of parser and story. The beauty of the modern IF languages is that they have freed designers from most of the hassle of worrying about the parser, allowing them to focus the bulk of their creative energy on the story. When a game eschews these time-tested solutions, it doesn’t just double its work, but increases it exponentially. Lunatix, strong as it is, isn’t quite up to the task.

Rating: 7.1