The Sword of Malice by Anthony Panuccio [Comp05]

IFDB page: The Sword of Malice
Final placement: 28th place (of 36) in the 2005 Interactive Fiction Competition

The Sword of Malice is not a good game, but it is instructive, in that it provides several excellent examples of potential pitfalls that designers can and should avoid. So in the spirit of making these reviews useful, I’m going to look closely at one of those pitfalls to explain what makes it problematic. This is also the moment where I’d encourage the author to try again, but it’s been 19 years at this point, and the IF ship has clearly sailed for Anthony Panuccio.

So let’s talk about randomness. Randomness is one of my favorite things, personally, and it can be put to excellent use in an IF game — random atmospheric messages or NPC behavior, all the way up to random events that can significantly affect the story. But randomness can also be a major source of frustration when it’s misused, and a classic type of that misuse occurs in examining a volume of similar things. This comes up a couple of times in Sword, first in the pages of a diary. Try to read that diary, and here’s what happens:

>read journal
"Day 26 - ...the ritual was simplistic in nature. By simply touching the beast (the rest has been water smudged)..."

>g
"Day 5 - ...I have been caught. On my return trip from the faraway lands, the Altari caught me. Let's hope they do nothing they will regret..."

>g
"Day 5 - ...I have been caught. On my return trip from the faraway lands, the Altari caught me. Let's hope they do nothing they will regret..."

>g
"Day 26 - ...the ritual was simplistic in nature. By simply touching the beast (the rest has been water smudged)..."

>g
"Day 57 - ...the Altari have gone mad! For some reason they have begun ruthlessly torturing me all day and all night. For being such a righteous race that they claim to be, they certainly don't show it. They would seem more at home with some of 'our' prison guards...."

This is not how reading works! Sure, you don’t want to write an entire journal inside your IF game — that makes sense. But in no universe would somebody open a journal, read a couple of sentences on page 26, then flip to page 5 and do the same, then read the same part of page 5 again, then the same part of page 26 (especially if it was water-smudged and unreadable in the first place!), then part of page 57, and so on, randomly bopping around the journal. (I’m simplifying here by pretending each day takes up a page.)

As a player, it quickly becomes apparent that the game isn’t willing to play straight with me, and wants to instead act as though my character doesn’t know how to read good. That could be a character trait, of course, but you have to establish it much more clearly than this. In addition, knowing that the game is picking random entries opens up the possibility that there is key information I need to extract from the journal, but I may not be able to reach it, depending on how the dice fall.

Part of this issue could be addressed by removing entries from the pool of random pages once they’ve been read. But I would argue that even then, this method of reading just makes no sense, especially reading something chronologically arranged like a journal. Randomness doesn’t belong in this part of an IF game. If something makes sense in a sequence, provide it in a sequence.

This issue crops up again later in the game, when the PC is rummaging for supplies before going on a quest. There’s a roomful of potions, and searching them looks like this:

>x potions
Many potions fill one wall of the armoury. You scan the potions and find...

...a "Potion of Cursing". $#%!&$&(*$#*

>get potion
You can't see any such thing.

>get potion of cursing
You can't see any such thing.

>x potions
Many potions fill one wall of the armoury. You scan the potions and find...

...a "Potion of Equilibrium". Your balance isn't that bad.

>g
Many potions fill one wall of the armoury. You scan the potions and find...

...a "Potion of Indecisiveness". Hmmm...to take or not to take?

Oh, okay, so it’s just a bunch of jokes. Except, as I found out after concluding I can’t trust the game and therefore turning to the walkthrough, it isn’t! There is one potion in this random mishmash that is extremely helpful, but the rest aren’t even treated as valid objects. What’s more, though I don’t show it in this excerpt, they repeat just like the journal entries did.

In a way, this is even worse than the journal. It’s one thing to prevent me from methodically searching a book for information, but to prevent me from obtaining a useful item just because I don’t know how to search a pile of stuff and set the useless things aside? No. And the fact that the game doesn’t even treat the non-useful potions as implemented objects at all gives me the clear message that none of them will be useful, which turns out to be false. Designers, please don’t do this. Randomness isn’t completely out of place here, but a) treat objects as real, even if you’re not going to let me take them, and b) don’t repeat objects that the interaction has already established to be useless. Give me enough feedback to keep me searching.

There are many more object lessons (as it were) from The Sword of Malice, but treating them all at this level of depth would make this review much more of an effort than the game earns. (Arguably, it already is.) So I’ll just quickly list out a few more thoughts:

  • Move beyond Dungeons and Dragons. I love D&D — I’m a player and a big fan. But it is its own thing, an established set of mechanics, and your text adventure (short of going full Baldur’s Gate) will never be D&D. It’s not helped by lazy lifting like “wearing full plate armour and brandishing a large polearm” or “The skeleton has 9 hitpoints remaining.”
  • If you’re going to forbid something, give a good reason. Despite being an off-brand D&D simulator, this game will not allow you to pick up weapons, stating, “Swords, axes, polearms, and other various weapons are made available here for acquisition. For your quest, however, you do not need these weapons.” Same thing with armor. This despite the fact that later there is a full-on combat encounter with a skeleton, where I very much could have used those weapons and armor.
  • Have some moral awareness. From the game’s very first word (“War!”), it frames a moral universe in which horrible people are grasping for power, and the PC is one of those people, yet at no point does it seem to subvert that point of view at all, or show any awareness that this is a problematic way to proceed through the world. I read and listened to the history of the PC’s “race”, and said, “We sound like the bad guys.” I wish the game had known that too.

That’s enough. There’s value in playing and reviewing games like this, if only to clearly codify how to do better. But that doesn’t make them fun.

Rating: 5.2

Tough Beans by Sara Dee [Comp05]

IFDB page: Tough Beans
Final placement: 5th place (of 36) in the 2005 Interactive Fiction Competition

Tough Beans has, hands down, the most powerful opening of any Comp05 game I’ve played yet. Here’s the first screen:

Lambkin. Babydoll. Princess.

In the large oval mirror above your dresser you watch a pale hand drag a bubblegum-pink brush downward through a section of fine blond hair. It is your hand. It is your hair.

You can’t feel anything.

WHOO! That alone knocked my socks off, and then it was followed by several more screens in the same tone, depicting a PC who has been “swaddled in epithets” (what a turn of phrase!) like the 3 words that start the game, but who is starting to emerge from her doll-like stupor. (And in that spirit, let’s note here that the PC does indeed have a name: Wendy.) In fact, as we discover gradually, pieces of her have been in rebellion for a long time, but today is the day it all breaks.

Man, did I love this premise, and for the most part, Tough Beans really delivers, with several cool techniques for enhancing its narrative power. There’s that stunning intro, with multiple screens of text, each one of which blanks out the last before finally giving way to the game proper. We’ve seen that before in IF, and it’s used very well here.

There are the introspective flashbacks tied to otherwise ordinary game actions, memories from childhood that deepen our understanding of Wendy and how she got into her current situation. Sometimes, those flashbacks show us those rebellious parts of her, parts which have been dutifully squelched in support of her conformist ambitions, but which roar up to support the destroyer that emerges. This, too, is not a new technique in IF, but Dee does a marvelous job with them, writing vignettes of memory that are not only compelling on their own, but which tie elegantly to both the specific action that prompted them and the overarching themes of the game.

Then there’s something I don’t remember ever seeing, but which made for a really potent effect when it worked. Upon Wendy entering a new location, Dee will often hijack the initial room description to instead provide a little cut-scene, before then allowing the room description to, well, describe the room. Here’s an example from early in the game:

Living Room
There is so much sunlight streaming in from the window over the sofa that you have to blink your eyes a few times before they are fully focused. When your vision is restored, you notice a red rubber chew toy peeking out from behind a pillow on the couch. Barkley! As if on cue, you hear a loud snuffling sound behind you. You turn around just in time to see Derek's beloved bull mastiff settle himself down in front of the entrance to the hallway. He proceeds to gnaw on his toy with gusto, completely ignoring you as usual...

Followed by a few more paragraphs setting up a puzzle. Look again, and we get:

Living Room
The living room, like the bedroom, is still a work in progress. All the necessaries are here, however: you've got a couch, a couple shelves to hold Derek's books, a TV, and plenty of sunlight. A colorful braided rug covers the floor.

This moment really worked for me. It acknowledged that I’d changed locations, but instead of being like another room in a colossal cave, the new location instead functioned like another beat in Wendy’s story. My focus was immediately drawn to figuring out what to do with Barkley (who is not only blocking Wendy’s way but also gnawing on her shoe… ick.) It was only after the first few obvious actions failed that I took stock of the room proper, a progression which felt strongly mimetic to how a person’s actual thought processes might work in such a scenario. There were other times when the technique didn’t flow so freely for me, and I found myself wishing I could see the room without having to LOOK a second time, but for the most part, I was happy to be swept through the story as I moved through the world.

The game isn’t pure narrative — there are definitely puzzles, one of which was enough of a doozy that it sent me to the walkthrough. But in employing a deft compositional hand between depicting Wendy’s interior and exterior worlds, Tough Beans got me strongly invested in navigating through her challenges.

I successfully managed to do so, at least after that little trip to the walkthrough, where I found out that my stuckness was due to neglecting the fact that the game frequently implements descriptions for second-level objects, and it turns out sometimes they’re important. However, I only finished the game with about half the points, and here’s where the final innovation lives. Tough Beans, we learn, awards points for solving puzzles, but just as often it does so for finding opportunities to fully realize the character. As the walkthrough puts it, points are awarded “in situations where Wendy shows some backbone, spunkiness, cleverness, etc.”

I would say it’s even a little more nuanced than that, as at least one point comes from behaving in an adult, responsible manner, though several others derive from being a hellion. In any case, the game was sized well enough that I’d found the non-optimal winning solution by about 80 minutes in, and could then spend my remaining 40 minutes finding opportunities to make Wendy an even stronger version of herself. It’s an ingenious idea to have the points, at least in part, function as a character-themed “Have You Tried…?” section.

This didn’t work perfectly. I think the point awarding could have been done a bit more consistently — 10 points is too few for all the potentially relevant opportunities in the game — and I wish the walkthrough had just come out and told me how to score the points rather than coyly hinting. Moreover, I really missed the inclusion of some features that do (I think) come natively with Inform, such as a Full Score breakdown and notifications when I scored a point.

Similarly, there are just a couple of little bugs and some places throughout where the prose stumbles, often by missing a word or a punctuation mark. Nonetheless, I spent the whole game rooting for Wendy and rooting for Tough Beans, and was happy to see them both succeed in the end, even if they weren’t flawless. In fact, as the game’s excellent characterization so effectively declares, flawlessness is most emphatically not the point.

Rating: 9.5

The Colour Pink by Robert Street [Comp05]

IFDB page: The Colour Pink
Final placement: 6th place (of 36) in the 2005 Interactive Fiction Competition

The Colour Pink is one of those games that starts out with one premise and then wildly shifts gears into something else entirely. There’s nothing wrong with games like that. Heck, I even wrote one. But putting your players through a major shift incurs a responsibility, and that responsibility is to make it clear what is happening. You don’t have to do that immediately — it’s perfectly fine to let a mystery simmer and then have the solution coalesce, either slowly or quickly, at the very end or before that. But if you never explain what happened, your players are left sputtering, “Wait, but how come… what was the… why was everything, and then… WHAT???”

That was me at the end of The Colour Pink, a game which starts out sci-fi, then turns into fairy-tale/fantasy, then skids back to sci-fi at the last move (or doesn’t, depending on which ending you choose), but at no point makes it clear just what you’ve experienced. It seems like maybe you eat a hallucinogen, but apparently its effects can last forever, if you so choose? Oh, and the thing you eat has one set of effects immediately (and even some effects before you eat it, along the lines of compelling you to eat it… in some unexplained way) and then a different set of effects later? Unless the second part (the shift to fantasy) wasn’t a result of eating the thing at all, but is some other weird thing happening on the planet?

Also, there are missing people, and we never find out what happened to them. Did they turn into the animals that we meet in the fantasy land? Are they normal but we’re just experiencing them as animals? What is the War that the fantasy animals keep referencing? I guess there’s a wizard who does a thing to a princess, but what is that even about? Or is the princess not a person at all, but rather a hallucinatory projection of a missing item? There’s some whole thing at the sci-fi level about trying to create a (sci-fi) love potion, and what happens with that? Is it what causes us to be compelled to eat the hallucinatory (or whatever) food? Is the whole fantasy landscape a dream or something? Or are we sharing a dream with the missing people, and the PC is the only one who gets out? (In endings that exit it?) Why is everybody an animal except us?

Questions, questions, questions, and there are no answers forthcoming. I kept waiting for them, and they never arrived. This is a… I want to say “betrayal”, and that’s a highly charged word, so maybe it’s a little too much. It is a shirking of authorial responsibility. Now, I will own the fact that I played this game in two installments with about a two-month gap between them. Maybe my failure to understand what was going on is on me. But even in my first few moments with the game, I immediately found myself scrambling for answers, trying to get my bearings in the description of events. Here’s that introduction:

You are on an abandoned planet again. Not content with almost killing you the last time, the Captain has delegated you again to investigate another out-of-contact colony. Apparently you impressed him with your survival instincts, by evading thousands of insect-like creatures before the ship finally sent down enough people to wipe them out. Maybe your job description should just be renamed as the Expendable Explorer. Unfortunately, you have no choice but to obey the Captain’s orders.

An hour ago you were sent down into a thick jungle. When you made contact with the ship you found out that they had missed the clearing where you were supposed to land. The intervening hour was spent cutting through the energetic plant-life until you finally reached your destination.

Immediately following that, I wrote: Already confused. “When you made contact with the ship”… Wasn’t I sent down from the ship? I “found out that they missed the clearing” where I was supposed to land? Wouldn’t I have known that from the fact that I didn’t land in the clearing? What is my destination? The out-of-contact colony? Was that where the ship was supposed to land?

I mean, once each milieu settles in, there’s a bunch of running around and solving puzzles in a very familiar IF way, and taken on their own, they’re reasonably satisfying, but they’re a bit like ornaments hanging on an invisible Christmas tree. Sure, they’re fine and pretty, but nothing seems to connect them in any way, which makes everything feel arbitrary and baffling. Consequently, while I had fun at moments in the game, it kept accumulating narrative debt that it never paid off, so even with multiple endings available (and even a whole potential violent path, a la Undertale, that I never bothered to explore), I still felt kinda cheated when it was done.

Rating: 7.0

Vespers by Jason Devlin [Comp05]

IFDB page: Vespers
Final placement: 1st place (of 36) in the 2005 Interactive Fiction Competition

I came to this game knowing it had won the 2005 IF Competition. That couldn’t be helped. I was detaching from the IF community in that year, after my kid was born in June, but I was still dialed in enough to know the name of the winning game. It just took me almost twenty years to actually play the thing, that’s all. Because I just looked at its IFDB page, I also know that it won a bunch of XYZZY Awards, and that it has achieved lasting respect, still making it onto a list of Top 50 all-time IF games in 2023.

Starting with that knowledge gave me a rather unfair (albeit unavoidable) set of biases. Playing an acclaimed game, at least for me, comes with a higher initial bar of expectations, and maybe a little less tolerance for mistakes. Lucky for me, Vespers delivers on its promise, and earns its kudos. The religious subject matter is pretty alien to me, and religious games have been offputting to me in the past, so I appreciated the author’s note that Vespers “isn’t a religious game: at least not in the sense of trying to convert anyone”, and that he himself is “not Christian and wasn’t raised Christian”. Another unfair set of biases on my part, I suppose, but those upfront announcements helped me relax my guard and put my trust in the game.

Once I did that, I found it a rich and immersive experience, albeit in a disturbing way. I don’t think I’ve seen a better use of quotation boxes, with the possible exception of Trinity, which pioneered them after all. I hope it’s not too spoilery to say that Vespers uses quote boxes as a way to showcase the PC’s internal dialogue, an inner voice which becomes increasingly askew from its moorings, and which we learn later may have been leaking out for quite some time.

Yes, we have an unreliable narrator here, and maybe even an entire unreliable milieu, in a way that’s again hard to talk about without being too spoilery. And yeah, it’s a 20-year-old game (nearly), but I still strive to keep these comp reviews spoiler-free, as they’re about discovery after all. I’m making an exception, though. Fair warning: mild spoilers follow for both Vespers and Photopia, because I think there’s a fruitful comparison there.

There’s a moment in Photopia when what you’ve witnessed in the beginning comes back around, but this time with loads more meaning attached, and an oppressive sense of fait accompli. There’s nothing you can do to change what happens — after all, you already saw it happen — and indeed one of the knocks on Photopia was an alleged lack of interactivity, given the unchangeable nature of its central event. But I would argue that the very real interactivity of that game attaches the player to the event, and to the characters affected by it, with much greater ease than a similarly plotted short story could. You may not always be in the driver’s seat, but events witnessed from the passenger seat can still have a very powerful effect.

Vespers doesn’t hop perspectives the way Photopia does, but it does start with a decision already made by the PC, and everything else in the game flows from that decision. As the game goes on, the consequences of that decision become more and more clear, and it is the PC’s job to reckon with those consequences as best he can, within his declared moral framework.

And here’s where the Catholic setting becomes phenomenally useful to the game’s project, because it turns out we are dealing with an original sin. In Vespers, the sin was committed by the PC, but before he was being controlled by the player. We must inherit the consequences of that sin, and proceed as a flawed man moving through a flawed world. It’s as if the game begins with “*** You have lost ***”, and then asks, “Now what?” Nevertheless, and also true to its theme, Vespers does offer the possibility of redemption, at least on a personal level, even if a tsunami of suffering has overtaken the world. The path to get to that redemption is a very narrow one, but I think that also rings true in a Medieval setting.

I found this a brilliant use of interactive fiction, verging on profound. I have a fundamental quibble with the “good” path (albeit one that might be addressed if I understood Catholic theology better), and I did find a few places where the language or the coding fell down, but overall it’s clearly a well-tested and well-crafted game, which has absolutely earned its place among the all-time great works of interactive fiction.

Rating: 9.8

Ninja II by Paul Panks as Dunric [Comp05]

IFDB page: Ninja II
Final placement: 36th place (of 36) in the 2005 Interactive Fiction Competition

So, like the other Panks game I played from this comp, Ninja II required me to fire up a DOSBox instance to get it working. However, unlike that other game, I found myself with very little patience for this one.

I’ve already written my rap on Panks, and what’s more, this game is almost identical to his entry from Comp04 — it has one additional “puzzle”, and those scare quotes belong there. (The puzzle, which is simultaneously ridiculously hard and stupidly easy, prompts you with “Dare you beat dragon?” and leaves you to determine exactly how that phrase works as a “clue”.)

Granted, I played the earlier version of Ninja 19 years ago, and remember virtually nothing from it (except that it’s bad), but I don’t need to revisit it. I’ve done my time. Plus, re-submitting a nearly identical game to your last year’s entry is obnoxious behavior, however you slice it.

Rating: 1.9

Beyond by Roberto Grassi, Paolo Lucchesi, and Alessandro Peretti [Comp05]

IFDB page: Beyond
Final placement: Tied for 2nd place (of 36) in the 2005 Interactive Fiction Competition

Here we are again: I couldn’t finish this game in two hours. I found it quite absorbing, and with 20 minutes left, I really debated whether to turn to the walkthrough or just play out my 20 minutes with a bit less dawdling around examining things, getting as far as I could. I picked the latter, but with 5 minutes left, I really wanted to know how the story turned out. So I peeked at the walkthrough, hoping to speed through to the end. NOPE! Turns out I was midway through chapter 4 of 7 (plus an epilogue) — just about halfway through, I reckon.

Back in the day I used to penalize games like this in my ratings, hoping to discourage people from this behavior. But it’s not like whatever I put here will deter people in, like, Comp06. Plus, as Michael Coyne taught me, authors have a strong motivation to enter their too-long games in the comp, and nothing I did as a reviewer could have changed that motivation anyway. And I’m obviously not trying to go through all these Comp05 games in six weeks — I started on these almost three years ago! So while I am still stopping after two hours to write a review, I’m not going to specifically take points off anymore, except to the extent that having to stop prematurely affected my enjoyment of the game. Heck, in some games stopping after two hours feels like a gift.

Stopping Beyond was disappointing, though, because I was deeply involved with its story, being pulled along at multiple levels. At the higher level, there’s a frame story, in which the PC is the spirit of an unborn child, exploring the reason why it wasn’t born. I was very wary when I encountered this premise, fearing that it would veer into an anti-choice polemic, but I needn’t have worried. Instead this concept brings us into a compelling murder mystery, in which we play a detective looking into the murder of a pregnant woman.

Really, I shouldn’t call the unborn spirit piece a frame story, because it returns after every chapter, in interludes where we see the murder scene as a ghost, or experience a bit of what life might have been like had the mother lived, or watch different scenarios of how that night might have gone, from a godlike remove. In the prologue, the game makes clear that the PC (and thereby the player) cannot affect her fate. She will never be born, and can only learn the circumstances surrounding that fact.

Thus the game takes place under a heavy layer of inevitability, similar to Photopia — a game to which Beyond pays a neat, subtle tribute by replicating one room and item description. And yet, also like Photopia, Beyond weaves a deeply compelling story around this unavoidable death. As the detective, we’re able to investigate the scene of the crime, talk to a wide variety of connected characters, and make clever observations that lead us closer and closer to solving the crime.

As any good mystery should, the plot takes several unexpected turns, and who knows how many more were in store, given that I was only halfway through the story when I reached my time limit? Not only is the plot well-crafted, but the presentation of the game is excellent as well. The whole thing renders in tan text on a black background, setting a nicely somber mood, and fantastic illustrations appear throughout the traversal, in that same color scheme. These illustrations might appear at the top of the text window, or on either side, and the game handles their appearance, persistence, and disappearance very smoothly, in a way that always enhances the story and never disrupts it.

The one Achilles heel in Beyond, I’m sorry to say, is that the game sometimes demonstrates a rather shaky command of English. Every so often there’s a mention of a baby “wrapped in white clothings”, or a character who says, “I have took the water”, or a phrase like, “I feel like I’m bringed away.” All things considered the errors aren’t overwhelming — certainly not the trainwreck that some broken English comp games turn out to be — but enough to throw me out of the story when they happen.

Nevertheless, this bothered me much less than it might have, and that’s down to the overall outstanding craft that was put into the game. It was one of those that I wish I could give more time, and maybe someday I will, but for now, I leave the story unfinished, but with admiration.

Rating: 9.3

On Optimism by Tim Lane [Comp05]

IFDB page: On Optimism
Final placement: 24th place (of 36) in the 2005 Interactive Fiction Competition

Readers of these reviews know that brevity is… not my strong suit. However, I could review this game in one word, and that word would be: “Painful.” Because I am who I am, though, you get multiple paragraphs about how this game is painful in multiple ways.

First, it’s painful because it clearly comes from pain. This game’s world, its images, its themes — they all seem to be torn from an extravagantly suffering heart, attached to another deeply wounded person. There’s drug abuse, self-harm, buckets of tears, and I suspect it’s rooted in at least a few real events. As such, it’s a tough game to review, because I hardly want to be stomping on somebody’s feelings, even 19 years later. I hope that writing this game gave the author a bit of relief.

That said, its subject matter isn’t the only thing that makes this game painful, and here I just have to say, if you have tender feelings on behalf of the topic and the possible real-life connections, you may want to stop reading. Because this game was absolutely painful to read due to its absurdly overwrought, faux-poetic, and hyperdramatic language. Over and over again, the game reaches for profundity or eloquence, and lands comically short.

Here, have a sample picked at random:

Room of Your Joy
My eyes scanned this room of your joy for minutes. They were searching for something that could not be found; for what this room must surely contain. But this is what they found: emptiness. A horribly large, vacant room was spread out before my eyes. A room that showed the depth of your sorrow, though it was called your joy. But as my eyes perused the room longer they found that there was but one small relic left in this room: a frame about the size of a sheet of a paper plastered on the far wall. Otherwise, vacancy could have been this room's name.

Oh man. I don’t think I need to take this apart piece by piece in order to show the ridiculousness of it, so let’s just focus on one thing: the weird personification of the PC’s eyes. They seemingly act on their own, leaving absolutely no agency for the actual character. The eyes scan the room. The eyes are searching for something. They don’t find it. The room is spread out before them. They peruse it longer. It’s all eyes, no “I”.

This mannerism repeats throughout the entire game, most often to ludicrous effect. We get lines like, “To the surprise of my eyes, the statue moved”, and, “My eyes once again received the strange privelege [sic] of sight”, and “In front of my eyes lay an opening begging to be traveled.” It’s not limited to the PC either, as the game pops out gems like, “Those great faucets you call eyes,” and “the pumps we call eyes.”

Nor are the eyes singled out for this bizarre treatment. This game never says, “I pressed the button” when it could instead say, “I moved forward and applied the weight of my body upon the remote’s only button.” And oh, the heart references! Most of the game takes place inside a metaphorical (and sometimes a bit oddly literal) heart, and the poetry (oh yeah, there’s poetry) refers to hearts relentlessly. At one point, when it was waxing tragic about a heart that will “forget to pump blood through my core,” I couldn’t help but flash on Andrew Plotkin’s classic review opener for Symetry:

This is terribly, terribly unfair. I’m really sorry. But I just started laughing hysterically, and it’s not what the author intended. In the middle of an intense ending sequence, I read the line:

‘My blood pumper is wronged!’

I just lost it. It’s a very ‘Eye of Argon’ sort of line.

That’s pretty much the story with this game’s prose. You’re not supposed to laugh, but it honestly can’t be avoided.

There’s another level of pain in this game, and that is its painful design. Several times in my playthrough, I had to turn to the hints (which were clear and thorough, and for whose inclusion I’m grateful), only to find that the command necessary to resolve my conundrum felt like a truly random thing I would never have thought to do. It’s not surprising, I guess, that a game living entirely in an allegorical, metaphorical, and dreamlike landscape would have logical non sequiturs in it, but no fair trying to make other people guess at them.

That’s enough. I appreciated those hints, as I said, and there’s a moment where the game ends but you’re given the chance to go back to a crucial decision point. I thought that was a cool innovation, one I’d enjoy seeing in other games. Overall, though, my memories of this game will always be full of pain. And just a little hilarity.

Rating: 3.7

Really Late Reviews #2: Riven [misc]

[I wrote a few reviews of graphic adventure games in 2001, and Stephen Granade hosted them on the About.com interactive fiction site he ran at the time. I called them Really Late Reviews because, well, I wrote them long after the games in question had been released. About.com has gone so far down the Internet memory hole that I can no longer retrieve those reviews in the context of the site, so I’m taking their dates from the original text files on my hard drive. That means this review of Riven was written on April 23, 2001.]

As I continue my project of trying to play and review the tall pile of game CDs sitting next to my computer, I start to get an idea of how the pile got so tall in the first place. I finished the first review (of The Space Bar) late in January 2001, and now I find myself in April only just finishing the second. Somehow real life keeps getting in the way. Well, that and writing text games. Let this be a lesson to you, kids. (Though just what the lesson is, I’m not sure.)

The idea behind these “Really Late Reviews” isn’t to help people decide whether or not to buy a particular game — in the vast majority of cases, the games probably aren’t available anymore except through auction sites and dusty bargain bins. Even Riven, one of the biggest hits ever, is no longer in print, though it’s not too hard to find. Instead, these reviews try to focus on what does and doesn’t work in a specific game with an eye towards good and bad design decisions in general for adventure games.

The scrutiny is perhaps especially appropriate in this case, since Myst and Riven were such humongous hits that they had to be doing something right for somebody. The fact that they’ve both received such tremendous backlash from some hardcore adventure gamers is, to me, just more evidence of this fact. The tone of many of those complaints always reminded me of the irritation felt by longtime fans of groups like U2 and Nirvana after those groups got big, annoyance that their hip and private playground had suddenly been invaded by the unwashed masses.

It’s not that I thought that all the criticisms of Myst were baseless — on the contrary, I was just as annoyed by its anticlimactic ending and its sometimes pointless puzzles as anybody. But the vehemence of those objections always felt a bit out of place to me. I will say, though, that I’ve always been struck by the irony of Myst‘s emphasis on books, and the same is true for Riven. Here we have the adventure games that, more than any single other, took players’ hands off the keyboard and placed emphasis totally on mouse interaction, yet their central metaphor is of books as transportation devices.

In fact, when one of those books opens and we see that the pages are in fact blank, and in place of the text is an animated graphic, we might realize that there, conveniently displayed before us, is the Myst aesthetic: gorgeous art on the simplest background, divorced from (con)text as much as possible. For an old text adventurer like me, there was something amusing about the fact that the games had such a worshipful attitude towards books and pages, while eschewing actual words almost completely. I say almost because the games can’t quite manage to avoid presenting text, and consequently end up hitting players with giant swaths of it at once. But more about that later.

Of course, the point has been made before that this very ejection of text in favor of art was one of the keys to Myst‘s success, and it’s a point I find persuasive. I know that while playing Riven, I enjoyed how easy it was to find one breathtaking vista after another, even before any puzzles had been solved, with only a few mouse-clicks. That simplicity is a solid virtue, and the fact that almost anybody could figure out the interface within 60 seconds had to have helped the game’s popularity. Simplicity and dazzle are a powerful combination, and Riven has both in spades — it’s no wonder that so many other games have copied its interface.

But as easy as that interface was to use, I found it frustrating at points. For one thing, the fact that Riven‘s graphics were so detailed, with so many subtle areas of light and shadow, meant that in any given screen, there were several features that might yield results when clicked upon. Consequently, I found myself doing a lot of random clicking in a great many places. It’s not that this approach is difficult, but it does get rather tedious, especially when only one out of oh, say 75 of those clicks actually accomplished anything. Another problem with the Riven hunt-the-hotspot interface is that for unspecified areas of many screens, clicking would actually advance the PC forward, while clicking elsewhere would have no effect. Numerous were the times when I’d have to backtrack because I’d moved forward without wanting to.

The answer to these problems would have been just a little more cursor differentiation. Riven already has this feature for some areas. For example, when the cursor would turn into finger pointing right, clicking would turn the PC 90 degrees to the right. When the cursor becomes a grabbing hand, you know it’s possible to click and drag the feature beneath it. If only it had lit up on other (non-draggable) hotspots and evinced some difference between forward motion and no effect, I could have been saved a lot of pointless clicking. These features seem so obvious that I wondered whether they had been omitted in the name of making the game more challenging. If so, they certainly served their purpose, but increased challenge of that sort doesn’t make a game any more fun, just more numbing.

But even when I’d feel myself sliding into a stupor from all the fruitless clicking, Riven would always reawaken me with its phenomenal art. This game is known for its graphics, and rightly so — even its fiercest critics may allow that it’s “pretty.” I’ll say more than that: it’s stunning. The level of detail in rocks, plants, and skies made them feel indelibly real, and the effect was aided by all the tiny touches that were put in just to enhance the game’s feeling of presence. In a forest, tiny fireflies (or are they dust motes) swirl around you, for no other reason than to deepen the aura of enchantment. Water shimmers and refracts brighter and darker colors up at you, creating a remarkably mimetic effect.

From time to time you’ll see other people, always shying away from you and warning their companions of your presence like timid prairie dogs. The other thing that just knocked me out about some of the graphics in Riven was their choice of colors and level of color saturation. When an elevator descends from the ceiling, it isn’t just gold, it’s GOLD. When the pathway from that elevator leads to a huge viewport on the ocean, it’s hard not to be awed by the intense BLUEness of that panorama.

Riven‘s puzzles partook of a similar intensity and attention to detail, and there were plenty of neat ones. I won’t discuss them in too much detail, since I don’t want to spoil the game for those who might still seek it out, but I will say that the game often rewards sophisticated spatial thinking, and that the solutions often require bringing together disparate pieces of information in crafty and revelatory ways.

In fact, my main criticism of the puzzles is that sometimes they go one step too far in this direction. In one instance, several things clicked together at once in my brain and I realized that I had figured out a puzzle that was cunning and delicious, but when I went to solve it, I found it unyielding. Turns out that the game had established a pattern of clues in four out of five sub-parts of the puzzle, but had broken that pattern in the fifth part, presumably to make things more challenging. My frustration arose from the fact that where I had once felt clever for teasing out the underlying motif, I now felt cheated out of the solution I’d earned, for no compelling reason. The pattern-matching was a bit of a stretch already, and when the pattern was arbitrarily broken, the puzzle started to feel a little unfair to me. Other problems occurred in one or two combination locks whose solutions didn’t quite make enough sense, including one in particular that I had to try over and over until it worked, even though previous attempts with the same combination had failed.

This last may have been a technical problem, and if so, it was one of the few bugs I encountered in Riven. There were little problems here and there, usually having to do with the cursor changing shape erroneously, sometimes making me wonder if I was missing additional screens because of an error in the navigation routines. Besides the art, the game’s other really outstanding technical achievement was in its sound. I recently bought a new computer with a powerful soundcard and speaker set, and Riven took the fullest advantage of these. The music was understated and evocative, and the foreground sound effects achieved a remarkable level of verisimilitude. But even when these weren’t playing, the game kept up a steady stream of ambient background noises — chirping birds and insects in a forest, lapping waves at the seashore, echoing droplets of water underground, and so on.

These sounds blended seamlessly into each other and did a lovely job of completing the sense-picture started by the graphics. On the other hand, a five-second foreground sound effect that’s enchanting the first time through becomes really annoying the fifth time. Riven provided the option to skip transition animations, thank goodness, but omitted any such feature for sound effects, with the result that I sometimes had to stop a quick run through already-explored areas just so I could let a sound play yet again.

However, this interruption wasn’t as inconvenient as the numerous occasions when Riven would ask me to swap among its five CDs. I have two CD-ROM drives in my current machine, and I still felt like I was constantly disk-swapping, especially as I got further into the game and was doing a lot of hopping from one area to another. I’ve read that a Riven DVD was released which eliminates this problem, and if you’re still looking for the game, I’d highly recommend pursuing this option — the game casts such a lovely spell that I wanted it broken as little as possible.

Prisons are a recurring motif in Riven. In fact, at the beginning of the game you’re given a “prison book” that you’re supposed to use to capture the Bad Guy, but as soon as you’re transported into the game, you find yourself in an actual prison (you know, with bars), where the book gets stolen from you. On the way to retrieving it, you’ll explore a number of different cages and cells, and in fact you’ll be imprisoned yourself when the book is returned to you. All this incarceration felt like an appropriate theme, because it nicely symbolized my relationship to the plot.

I think it’s fair to say that Riven‘s story is very poorly paced. At the beginning of the game you’re given a number of teasers (and references that seem inexplicable if you haven’t played Myst and/or read the tie-in novels recently, which was exactly my situation) and then thrown immediately into the standard lovely-but-abandoned landscape. From there, it’ll be a loooong time until you get more story. Oh sure, there’ll be hints and evocative little clues of what’s going on, but I found myself wishing for more narrative throughout the game, instead of the endless wandering, button-pushing, and lever-throwing that I got instead. This feeling was not alleviated when I finally stumbled across one of the game’s several plot-advancing journals. These journals are uniformly massive, page after page of spidery handwritten text that provides plenty of plot detail and background information (more than enough, in fact) along with some well-placed puzzle hints.

The problem with these things is that they take a long time to read, and whenever I’d find one I’d sigh, realizing that my next half-hour or so would be spent slogging through a sea of text. Trapped in this stumbling rhythm, I began to feel like a starving detainee (albeit one with a very large cell in which to pace), begging piteously for a few more scraps of plot, please, and instead given massive meals every six days.

In the end, I decided that I wasn’t playing Riven for its story, and allowed myself to sink more deeply into its lovely graphics, sounds, and puzzles like a warm bath. I came out feeling refreshed and contented, more or less happy for the time I’d spent with the game.

Really Late Reviews #1: The Space Bar [misc]

[I wrote a few reviews of graphic adventure games in 2001, and Stephen Granade hosted them on the About.com interactive fiction site he ran at the time. I called them Really Late Reviews because, well, I wrote them long after the games in question had been released. About.com has gone so far down the Internet memory hole that I can no longer retrieve those reviews in the context of the site, so I’m taking their dates from the original text files on my hard drive. That means this review of The Space Bar was written on January 27, 2001.]

For several years now, I’ve had a growing pile of commercial adventure game CDs sitting next to my computer. For one reason or another, I haven’t gotten around to playing them, but when the millennium turned, I decided I was going to change all that. I’m playing through them now, and for each one I play, I’m hoping to write a review. These reviews won’t be aimed at helping people decide whether or not to buy the games — they’re mostly out of print now, so the point is pretty moot. (Although many of them could no doubt be obtained through eBay or bargain bins.) Instead, I want these “Really Late Reviews” to be meditations on what works and what doesn’t in graphical adventure games, as illustrated by the successes and failures of each work under scrutiny.

The game on top of the pile was The Space Bar, Steve Meretzky‘s first post-Legend foray into graphical adventures. Meretzky has a good name among text adventure enthusiasts like me for having written landmark Infocom games like Planetfall and A Mind Forever Voyaging. I wasn’t as fond of his later works for Legend Entertainment, the Spellcasting series, because what clever writing and puzzles they did contain were submerged in a sea of juvenile, sexist humor, but they were commercial hits and plenty of people enjoyed them. After he left Legend, he founded a company called Boffo Games, Inc., and created The Space Bar, a large adventure game that was to be Boffo’s flagship product. Despite good reviews, the game sunk, and so did Boffo. Maybe this postmortem will provide a little perspective on just where TSB went wrong.

The game puts you in the role of Alias Node, a human detective on the seedy world of Armpit VI, investigating a robbery and murder whose culprit has been traced to a dive called The Thirsty Tentacle. The bar, like the rest of the galaxy, is populated by aliens of various races, but very few other humans. Your job is to interview these aliens, looking for clues about the identity of the killer, and using your special ability of “Empathy Telepathy” to enter their memories and guide those flashbacks to discover vital bits of information. In effect, these flashbacks serve as mini-adventure games in themselves, and the bulk of TSB is spent navigating the memories of various aliens, with occasional excursions back into the Thirsty Tentacle to meet other aliens and, finally, to catch the criminal.

The aliens are definitely the best part of the game, springing as they did from the imagination of Ron Cobb, the same guy who designed the eye-popping oddities that populate the Star Wars cantina scene. Copious background information on each alien species enlivens the game, and deepens the experience of otherness that permeates the flashbacks. Visually, too, the game does a terrific job with the aliens, and here we see one of the great strengths of graphical games. Text is wonderful for evoking interior worlds, but for the presentation of bizarre shapes and structures, it’s hard to beat good graphics. For example, a text game might tell you that Sraffans have hourglass-shaped pupils, but it would be hard put to present the labyrinthine network of veins surrounding the pupil, or to take your perspective inside those eyeballs as the flashback begins. TSB uses graphics in some clever ways throughout the game, including a freaky perspective from within the compound eyes of an insectoid race.

So The Space Bar is clever, and visually engaging. It also has its fair share of funny moments, thanks to Meretzky, who’s much funnier when he’s not aiming at 13-year-olds. Unfortunately, fun as it is to look at, it’s often not much fun to play. In struggling through the game, I found myself thinking quite a bit about the problems of translating text-game writing experience to the creation of graphical games, and wondering if TSB‘s many flaws stemmed from those problems.

Take, for example, the game’s interface. If you don’t have a parser and prompt, something must obviously take their place, and in this case it was the standard 360-degree panning worldview (with a bit of up/down axis as well), augmented by a multi-purpose onscreen device called the PDA: a combination map, inventory, system command portal, voice-mail receptor, and information storehouse. The idea of the PDA is a sensible one, but its implementation in TSB was extremely clumsy. Rather than occupying a stable portion of the screen, it rises up to half-obscure the main window whenever you click on it, spending the rest of its time half-visible, with half its features unavailable.

One of the most important of these unavailable features is the voice-mail indicator, which blinks when Alias receives a message. Because the light is obscured from view except when the PDA is fully visible, you end up receiving messages and not knowing it for dozens of turns, until the little voice inside your PDA says “Have you noticed your message light is blinking?” Why no I hadn’t, probably because I CAN’T SEE IT! It’s silly that the blinking light is hidden, but even the hidden light is a better solution than the one the game adopts occasionally, which is to have the PDA suddenly rise up and stop all action as a message comes in and is played.

When this happens (and it’s usually at the worst times), the player has to wait for the game to speak its message before continuing on with any actions, and therein lies another significant difference between graphical and text adventures. Text adventures print all their output, which takes pretty much no time at all. Graphical adventures have voice-acting, which means that to receive the dialogue, the player has to wait as long as it takes for that dialogue to be spoken… every single time. The voice acting in TSB is excellent, so it’s a pleasure to hear the dialogue in real time when you’re hearing it initially, but when you already know what’s going to be said, even the best voice acting can become tedious indeed. TSB often provides the option of hitting Esc to halt these sequences, but all too often Esc doesn’t have an effect, and you’re left drumming your fingers while a phrase plays for the tenth time.

Even worse, when realtime voices are overlaid on turn-based gaming, the resulting timing confusion can turn an extremely simple puzzle into a maddeningly difficult one. For example, in one of the flashbacks, you’re waiting for your name to be called before you can leave a particular room. However, there are about 10 voice phrases that play before that happens, each of which is around 30-45 seconds long. The phrases play one per turn, so if you perform actions which advance the turn counter (examining things, inventory management, etc.) and space them less than 30 seconds apart, the phrases pile up and play one after the other. When this happens, you’ll hear your name called, and try to leave the room, but the turn when you were supposed to do that has long passed, so the game goes on to say “Oh, too bad you didn’t leave the room — you lose” as you’re frantically clicking away. Doctors recommend against this sort of game design, as it leads to many cases of heads embedded in monitors.

Another sin of sound design which TSB commits over and over is having background noises drown out crucial information. For example, there’s a scene where you’re performing your actions while a thunderstorm rages in the background. In a text adventure, the scene would look like this:

> EXAMINE WATERFALL
The water sounds funny -- there might be something behind it.

KER-POW! Deafening thunder shakes the ground where you stand.

In The Space Bar, you click on the “Examine Waterfall” icon, and what you hear is the flashback character’s voice: “The water sounds funny. There mi– KER-POW! –it.” Then the sound you hear is yourself growling, as you realize that the game has stupidly and randomly allowed a background sound to prevent you from learning information that, as the character, you should theoretically already know. In other words, an actual sound has obscured a symbolic sound, the latter of which is only meant to represent the character’s interior dialogue. This happens over and over again, in several flashbacks, and each time it does, you have to repeat the action and hope you get lucky enough to hear the information you’re supposed to have.

That same thunderstorm flashback also features another one of TSB‘s biggest gaffes: the realtime puzzle. There’s a chase sequence in this flashback in which you have to make the correct series of clicks and rotations, in an extremely limited period of time, and if you don’t the flashback ends unsuccessfully. Maddeningly enough, this is exactly the time when your PDA chooses to rise up and halt all action until it finishes playing the incoming message. Because restoring from a failed flashback is blindingly dull [you have to listen to the failure message in real time, then get past the transition animation, then trigger the flashback again, then another transition animation, then the beginning-of-flashback animation, and only then can you restore your game], the punishment for failure is quite steep.

Add to this the fact that the processor load in that flashback makes cursor movement jerky, and panning unreliable, and you have one annoying roadblock. Now, I’m not of the school of thought that believes adventure games should never ever have realtime action portions, though I do believe it’s a bad idea to throw one arcade sequence into an otherwise traditional adventure game (which is exactly what The Space Bar does.) I enjoy both adventure gaming and twitch gaming, and don’t mind seeing the two mixed, but they have to be done well — if I fail, I want it to be because of slow reflexes, not a slow processor. My P-166 seems pretty pokey these days, but in 1997, when The Space Bar came out, it was well above the game’s minimum requirements.

Still, I gritted my teeth through many attempts at this puzzle before finally, gratefully getting past it. In a text adventure, that realtime puzzle would probably still be annoying, but because the processor demands of text are minimal, the computer’s speed would very likely not be the bottleneck that impedes completion of the puzzle.

Another side effect of the increased complexity of sounds, images, and animations in a graphical adventure game is their increased size and consequent separation onto multiple disks. The Space Bar comes on three CDs, two of which contain flashback material and the other one of which contains all the sequences within the bar itself. As a result, every time a flashback begins or ends, you have to switch CDs. I needn’t point out that a text adventure is highly unlikely to fill more than one CD and therefore to require such constant switching, but I will note that the drudgery of such switches imposes unnatural limits on both design and playing.

Because I was trying to minimize CD switching, I stayed within each flashback and tried to solve them in their entirety one at a time, instead of hopping from one to the next anytime I got stuck, as I probably would have in a text game. In effect, the disk switching became another of the game’s many resource management problems, but one of its least enjoyable. The best of these puzzles take advantage of the potential of graphics to easily demonstrate spatial relationships, and end up achieving effects that would be extremely difficult in a text game. The worst of them work through the game’s regular interface, and the presence of graphics and sound slows down the solving process to no real benefit. Elements that slow the process of solving a puzzle by means of arbitrary and pointless delays make that puzzle much less fun. Text has an advantage here, because its elements very rarely cause time delays.

Another advantage of text is its ability to clearly separate objects. For instance, in one of the game’s flashbacks, you stand before a house. There’s a boat locker in front of the house, from which you must obtain a vital object. The problem is that the locker blends in a bit with the house itself, and both the house and the locker are clickable objects. Consequently, you can click on several features of the house, all of which the game will process as the house itself. The only exception to this is the locker, but when the windows, the roof, the chimney, and the pipes are all called “House”, why would a player think that the little brown square representing the locker is anything but another unimplemented house feature? What’s more, you can get irretrievably stuck in the flashback and not know why — I had to look at a walkthrough, and when I did I said, “What locker?” In a text adventure, this simply wouldn’t be an issue, because objects don’t overlap:

Beside the House
Be it ever so humble, this is your home. The roof, windows, chimney, and pipes may all be a bit ramshackle, but they're all yours.

There is a boat locker in front of the house.

There’s no chance you could miss the boat locker (as I did playing TSB), because the interface never obscures it.

Reading through this review, I’m worried that it sounds like I’m railing against graphic adventures in general, and arguing that text is always better. I hope it doesn’t sound like that, because I don’t believe that. For one thing, The Space Bar has several problems that are equally possible in text adventures (an extremely irritating maze, several bugs, one of which almost kept me from finishing the game.) For another, I don’t think that superiority and inferiority enter into the equation at all — I just think that text adventures and graphic adventures are distinctly different forms, kind of like (to employ a tired analogy) novels and films. The skill sets required to create each of them overlap a bit, but not nearly as much as you might guess. Playing The Space Bar felt reminiscent of watching a film directed by a really good novelist who knows very little about moviemaking. You can see what was intended, and if you look harder, you can see why for the most part it all falls horribly flat.

Letter to the Author: Dangerous Curves [misc]

[I beta-tested Dangerous Curves, a mystery game released in 2000. I didn’t review it, since reviewing a game I’ve beta-tested always seemed sketchy to me. However, I did write a long letter to its author, Irene Callaci. With her permission, I reprinted that letter on my website, and now I’m moving it here. Note that it includes SPOILERS. This letter is dated April 28, 2000.]

Dear Irene —

First of all, let me tell you about me and mystery games. The first mystery game I ever played was Infocom‘s Suspect, fondly bought for me as a birthday gift or something. I loved walking around the mansion, talking to the various characters, and searching all the furniture. I filled up notebooks with every utterance I could squeeze out of the characters, with lists organized by room of the items therein, with chronologies of what happened when. I waited in every single location for the entire duration of the game to see what happens. If I walked into that mansion today, I could probably navigate it entirely from memory.

The problem is this: I got absolutely nowhere at actually solving the murder. I couldn’t figure out what was significant in some places, but more importantly I just couldn’t figure out how to establish motive, method, or opportunity, let alone all three. I started to get more and more frustrated with the whole thing.

After a long, long time of this, I broke down and bought the Invisiclues. When I finally found the solution, I didn’t have a feeling of “Why didn’t I think of that?” Instead, I felt, “How in the hell was I supposed to think of that?” Since then, my track record with mysteries has been unimpressive. I did OK with Ballyhoo, but that was really more of a puzzlefest with a mystery plot tacked on at the beginning and end. I was hopeless with Deadline. I couldn’t get anywhere in Moonmist, though that may have been due more to the bugginess of the game than to my particular denseness. Even The Witness, which everybody on the IF newsgroups seems to think is a cakewalk, was totally impenetrable for me. I had only the vaguest suspicion who did it, and not the faintest clue how to prove it.

There haven’t been that many amateur attempts at mystery games, and what few there are I haven’t played, so I can’t say how well I’ve done in the post-Infocom world of mystery games. I will note, however, that I am an equally poor detective when I read mystery fiction. I basically never figure out who the murderer is ahead of the detective. Well, there was one period where I was reading a lot of Agatha Christie, and figured out that the murderer is always the least likely person. I was able to guess with a pretty good degree of accuracy using this method, but I still had to wait til the end of the book to find out just how the crime was committed.

Now let me tell you why Dangerous Curves is easily, far and away, my favorite mystery game of all time. I haven’t got this figured out exactly, but I think it has to do with the fact that the game steps outside of all the paradigms for mystery IF that I’ve seen up til now. In Infocom’s traditional mysteries, you had to establish motive, method, and opportunity. This was sometimes accomplished through the use of highly unlikely actions like TELL THE DETECTIVE ABOUT THE WEATHER, actions which required you to put together all the pieces in just the way a good mystery reader would do, and just the way that I completely suck at. I could never come up with these actions, and so I remained stuck forever, or until I looked at the hints, whichever came first. (You can probably guess what came first every time.)

Dangerous Curves doesn’t require this kind of reasoning. It allows for it, but doesn’t require it. With the help of devices like the full score listing, Frank Thibodeaux’s gentle prodding, and the anonymous tipster, I was able to put together all the pieces and, for the first time ever in a mystery IF game, feel like I was solving the crime. Let me tell you, this was a great feeling. I think one of DC’s great strengths is that while it allows for the kind of player that was great at Infocom’s mystery games, it also allows for players like me. None of the devices I listed above are required for a winning session with the game, but they sure helped me feel like I was having fun rather than banging my head against a wall. That kind of fun is a new experience for me in mystery games.

There are lots of other factors that added to my enjoyment of the game. One of the strongest of these was the outstanding writing. Even if I hadn’t been able to get anywhere in the game, I would have had a good time playing it, just because the writing was so much fun to read. It caught the perfect balance between noir and humor, similar to the balance achieved by Columbo back when it was a regular TV show. All of the historical details were just excellent, and most of the one-liners were actually funny, rather than coming off as lame pastiches of Raymond Chandler. There was also a very satisfying attention to the rhythms and musicality of language in many of the game’s longer passages. For example, from the opening text:

Her eyes watch yours as she fans the money out on the desktop. “I never mix business with pleasure. Do you?”

Not often. Not lately. “Not me,” you assure her. “Wouldn’t dream of it.”

Now that’s just a really well-written passage. Not only is it funny, and not only does it tell us a great deal about the character in a very few words, but it also rings with a great rhythm, like a good swing song, a rhythm that would make it enjoyable to read even if it made no sense at all.

Coming in close behind the writing is the game’s remarkable technical sophistication and depth of implementation. I loved knowing that I could go to the Wednesday mass and watch the churchgoers, reading lots of great text that had nothing at all to do with solving the case. It was just there to make the fictional world feel more real, and it worked beautifully. When I wrote one of these detailed responses to Suzanne after testing Worlds Apart, I told her that the source of that game’s power to immerse players came from the combination of two factors: range of interaction and rich detail. DC employs this same potent combo, and it works just as well. The more actions that got a non-default response from the parser, the more places I could go, the more people I could meet, the more things I could ask them about, and the more syntactical combinations that the parser understood, the more deeply immersed I felt in Dangerous Curves‘ Los Angeles.

A little more about that last item: I was just astonished at how much work you’d put into the parser for DC. At least two or three times per session, I would try something non-standard and find to my surprise that the parser understood it. This is the kind of improvement, I know from experience, that takes a huge amount of time and energy, but you can never be sure how many people will even find it, let alone use it, benefit from it, or comment on it. Well, I just want to tell you that I found it, and I loved it. The same goes for all the other technical feats you accomplished to make life easier for the player: the status line compass rose, the convenient handling of opening/closing and locking doors, the money that worked so well I hardly needed to worry about it at all. You took a lot of the tedious details of IF off my hands so that I could spend more time enjoying the story and the writing. Great move. In fact, during the next game I played after DC, I found myself grumbling, “Where’s my compass rose?” Your game was so good, it spoiled me!

I know we all like positive feedback, and there’s certainly plenty to give, but I do want to make this review a little more useful to you than just simple egofood, so I’ll briefly touch on a few of the game’s weaker points. I found that some actions were insufficiently clued, or at least they wouldn’t have ever occurred to me without the anonymous tipster. One example of this is giving the donut to the cop. Because so many locations in the game are implemented as one-room spots, even though they might realistically have other places to explore (for example, the Tribune, the library, or Rosie’s), I wasn’t expecting that I would be able to actually visit prisoners in the police station.

Moreover, though I could easily come up with the idea of giving the donut to the cop once I knew he wanted something, I wouldn’t have otherwise expected to be able to take it out of Rosie’s, since so many other things at Lenny’s and Rosie’s are forced to stay inside their respective locations. Of course, it’s logical that I could walk out with a donut as opposed to a beer or a blue plate special, but I sort of lumped it in with everything else. Another action I wouldn’t have come up with on my own was to get the bank teller drunk. I never saw any indication from him that he had anything worthwhile to say, nor much evidence that he was the kind of vulnerable lush who could be easily plied with alcohol to spill his secrets. Considering how little room you have left, I’m not sure what you could do to remedy these problems, and because you have the anonymous tipster in there, they’re not significant problems anyway, but I thought I’d just let you know about my experience.

The other problem is one that I’m not sure how you could solve no matter how much room you had, which is that the characters were so well-drawn that I frequently found myself straining against the interface because I wanted to tell them more. It’s really frustrating to have to try TELL JESSICA ABOUT CARLOTTA when what I really want to say is “I broke into a real estate office and learned that the Mayor’s wife owns a huge amount of property along the proposed highway site, and that’s why Vickstrom was so hot on the freeway project, and no doubt why he had your husband killed.” Unfortunately, the solution to this problem is outside of the current grasp of IF in general, not just Dangerous Curves. The fact that your game made me feel the absence of such an interface that keenly is a great credit to your writing and characterization skills, not to mention the depth of immersion you achieve in your fictional world.

Playing Dangerous Curves has been one of my favorite IF experiences in a long, long time. Thank you for that, and for the correspondence, which I’ve also enjoyed very much. Good luck with your game and your life, and keep in touch.