Tag: steve kodat

The End Means Escape by Steve Kodat as D.O. [Comp00]

IFDB page: The End Means Escape
Final placement: 21st place (of 53) in the 2000 Interactive Fiction Competition

There have been plenty of times in my life when I’ve felt that inanimate objects are out to get me. Wait, I guess that sounds a little paranoid. Let me rephrase: oftentimes, when I trip over an object lying on the floor, or hit my head on something, or bump into a piece of furniture in a dark room, I curse that object, as if it willfully placed itself in the worst possible spot just to spite me. On some bizarre level of my brain (possibly my out-of-control ego), I feel that the pain I’m in at that moment is the object’s fault, not mine.

In my reality, I’m wrong. In the reality which begins The End Means Escape, I might very well be right. The game appears at first to be an “escape the one room” adventure, with a twist: all the objects are NPCs. I don’t mean that you’re floating in a void with a bunch of other people. I mean that in this room, everything reacts to you, often quite vocally. The walls, the floor, the ceiling, the table, the lamp, the door, the various objects strewn around — they can all be addressed and conversed with. It was rather disconcerting to be thrown into this environment without even a halfhearted explanation about what was happening, but once I adjusted, I found it quite absorbing. There’s a startling level of depth to the implementation — I kept being surprised by how many of the things I tried were accounted for in the game. I even had a fragile sense of making progress, though the whole thing was so unusual that I couldn’t rely on my typical IF cues for narrative progression.

Then, something else happened. I escaped the one room, fully expecting to have won the game, but instead moved into a realm that was even more bizarre than the one I had left, by several orders of magnitude in fact. I thought, because the “talking object” room was so well-done, that it was the whole of the game. Not so. To discuss further specifics about what proceeds from that first scene would, I think, be to move into the realm of spoilers, so I’ll just say this: the game turns out to be a string of scenarios, none of which conform to IF conventions of plot, setting, or character. Of these, the first scene is probably the most successful, but each has interesting merits. Certainly the first scene’s thoroughness of implementation is not lost on the others. Consider, for example, this startling disambiguation question:

>X YOUNG
Which young do you mean, the young man, the marking, the young man's
head, the young man's hands, the young man's skin, the young man's
feet, the young man's head of hair, the young man's forehead, the
young man's eyebrows, the young man's eyes, the young man's
eyelashes, the young man's ears, the young man's nose, the young
man's mouth, the young man's chin, the young man's neck, the young
man's fingers, the young man's thumbs, the young man's torso, the
young man's arms, the young man's legs, or the young man's hips?

The game displays an almost overwhelming capacity for describing scenery objects and making them available to various verbs. Strangely, though, where this strategy would normally heighten immersion quite a bit, it somehow fails to do so here, at least for me. I think this is because most all the game’s scenes are quite abstract and surreal, and thus I had a difficult time relating to them. Part of this is just my personal taste — I’m not overfond of highly stylized IF, and even last year’s outstanding For A Change left me feeling rather cold and distanced. The other part of it, I would contend, is that the kind of disconcerting scenes presented in TEME actively work against immersion rather than for it.

There are other things working against the game as well, such as the number of bugs in the implementation. To choose a small example, there is one point when you need to use one object to pry another object, but using the verb “pry” doesn’t work. Using the verb “cut” does, even though the response indicates that you’re prying. To choose a large example, about midway through, the whole game crashed so hard that it brought down my entire system. Now granted, I’m running Windows, so crashing the system is not all that impressive a feat. Still, I don’t expect an IF game to do it. I’ll certainly grant the possibility that the crash had to do with the combination of apps I was running at that time, but the whole experience left me feeling rather wary of TEME.

In other sections, the solution to the puzzle seemed pretty much entirely arbitrary. Of course, because the game operates on such a rarefied level, it’s quite possible that the solution made perfect sense but just went way over my head. Either way, it’s not a lot of fun trying to solve a puzzle whose eventual solution (when you extract it from help messages on Deja) just makes you say, “I was supposed to come up with that?” So yes, the game is flawed, and it’s also rather inaccessible, but it’s still a stimulating experiment in avant-garde IF. It was nothing like any piece of IF I’d ever seen, and that’s what I liked about it.

Rating: 7.5

Stone Cell by Steve Kodat as Middle Edge [Comp99]

IFDB page: Stone Cell
Final placement: 14th place (of 37) in the 1999 Interactive Fiction Competition

Joining Bliss in the rapidly burgeoning subgenre of jailbreak IF, Stone Cell doesn’t take too long to throw the PC into the eponymous prison. What happens just afterward is one of the most interesting parts of the game. When the PC is initially put in the cell, it is much as you’d expect: a simple room with a locked door to the north, and a mat and chamberpot within. However, after the PC sleeps on the mat and awakens in the cell, the mechanics of the game change radically. Suddenly, rather than just a one-location room with an exit to the north, the cell is now a 3 x 3 grid of locations, with door in one corner, the chamber pot in another, and so on. This can be a highly disorienting shift at first, but I thought it was a really cool technique, because it uses the mechanics of location in IF as a way of presenting the PC’s state of mind.

Every so often the argument crops up on raif that what IF ought to do is present location and navigation in terms tied to a specific simulated physics, so that you can specify exactly how far north you want to walk, how many degrees you’d like to turn and in what direction, etc. Predictably, these discussions bog down quickly in the face of how difficult it would be to implement and how incredibly tedious it would be for players to have to constantly type things like “WALK TWO METERS NORTH.” But even if it were possible to implement a smooth simulated physics in a text game, the question raised by Stone Cell‘s technique is whether that physics would even make a positive contribution to the interactive fictional project. The insight is this: IF with a characterized PC isn’t simply presenting a setting. It’s presenting a setting as perceived by a particular character. Consequently, a cell that seems small at first might grow in perceived granularity and detail the longer the PC is imprisoned within it.

Unfortunately, the excitement generated by Stone Cell‘s navigation-altering technique is quickly dampened by some of the game’s weaknesses. However, I think those weaknesses also have some excellent lessons to offer potential authors and anyone else interested in design and writing issues in IF, so I want to discuss them in some detail. In order to lend a little focus to the discussion, I’m going to concentrate on the portion of the game that takes place in the cell, despite the fact that there’s an entire section of the game that takes place outside the cell. I don’t think I’ll give away any spoilers, but if I do I’ll clearly mark them beforehand. Now then, having said all that, here’s the basic problem: having created a unique space for the PC’s expanded subjectivity in this prison cell via its use of navigation and location, the game fails to follow through with a similarly expanded parser and set of environmental descriptions.

For example, the cell initially has a description several sentences long, a description which engages several senses and mentions some of the PC’s emotional reactions to the cell. However, once the cell has metamorphosed into a grid, the descriptions of each grid location are extremely terse, sometimes not even full sentences. Some examples: “You slept in this corner.”; “The heart of the cell.”; “One side of the cell.” What an opportunity was missed here! Just as the PC’s perception of the cell’s size expands, so too should her awareness of the minute details of her surroundings. It seems to me that simulating the perception of being trapped in a tiny room ought to involve more description, not less. Perhaps there would be a danger of monotony, but this could be addressed through appealing to various senses and touching on emotions, even as the original description does. Instead, it’s as if she only gives the most cursory glance to her location, despite the fact that she is trapped inside and desperate for a way out.

Speaking of appealing to the senses, that brings up the other way that Stone Cell falls short of being truly involving: the parser is far too shallow. Think about the things you might do if you were trapped in a dungeon. Perhaps you’d listen at the door? Smell your straw mat? Feel along the walls, hoping to find a secret passage? If you did find a crack, might you try to pry it with something? I think so. Yet “listen”, “smell”, “feel”, and “pry” are all unimplemented, along with a host of other verbs that ought to be there. Authors, take note: if you plan to trap your players in an enclosed space, and make a puzzle out of how they are to get out, the puzzle won’t be much fun unless that space is very well implemented. The more often a player tries logical things that aren’t accounted for in the parser, the surer that player will feel that the solution is simply arbitrary.

That’s one of the worst consequences of breaking mimesis — reminding players over and over that they’re in a game, and not a very complex game at that, tends to derail any sense of emotional or intellectual involvement that those players have with the story the game is trying to tell. I was going to go on to make the same point about alternate solutions, but it strikes me that alternate solutions aren’t even necessary if enough verbs are implemented with sensible responses that nudge the player in the right direction. Unhappily, this sort of thing is exactly what Stone Cell lacks, and the lack degrades it from a great game to merely an interesting experiment in IF techniques. The experiment does teach us something, but the flaws that surround it teach us even more, and the learning process isn’t as much fun.

Rating: 5.5