Archive for the ‘zork-1’ Tag

Zork I: Getting Out   2 comments

I’m at the point where I have a mostly complete map, so I’m in the “logistics” phase where I am planning what order to visit the rooms and gather treasures.

It’s fairly tricky because of the thief. Just like original Zork, there’s a “lean and hungry gentleman” who can go most places on the map and will try to take any treasures you have (or ones that are lying around), and possibly stab you with his stiletto while he’s at it. You can eventually fight the thief with your sword, but it takes a higher point score to manage (like “experience points” in Dungeons and Dragons I suppose) so the fight has to wait until later in the game. Here is a result of trying to start the fight early:

Someone carrying a large bag is casually leaning against one of the walls here.
He does not speak, but it is clear from his aspect that the bag will be taken only over his dead body.
Your sword has begun to glow very brightly.

> kill thief with sword
A good slash, but it misses the thief by a mile.
The thief draws blood, raking his stiletto across your arm.

> kill thief with sword
You charge, but the thief jumps nimbly aside.
The thief just left, still carrying his large bag. You may not have noticed that he appropriated the valuables in the room.
Your sword is no longer glowing.

The other tricky element is perhaps the most clever finesse in the game, and one of the very first thing that happens.

> move rug
With a great effort, the rug is moved to one side of the room, revealing the dusty cover of a closed trap door.

> open trap door
The door reluctantly opens to reveal a rickety staircase descending into darkness.

> d
You have moved into a dark place.
The trap door crashes shut, and you hear someone barring it.

It is pitch black. You are likely to be eaten by a grue.
Your sword is glowing with a faint blue glow.

I’m not referring to the iconic “you are likely to be eaten by a grue” (which is indeed lovely) or “your sword is glowing with a faint blue glow” (which always happens with enemies nearby, and gives a nice texture to the world-building even if it is cadged from Tolkien).

Iconic enough someone made a cupcake. From Steelhead Studio.

I’m referring to the fact the way you came in is locked behind you, so you cannot take the same way out.

First: who barred the door? One might think the thief, but at least in this version of Zork, he never gets into the upstairs house. It can’t have happened on its own (“you hear someone barring it”), which is what I imagined when I was a child. Spoiler theory in rot13 (from a later Zork, so don’t reveal if you only know this game): gur qhatrba znfgre sebz gur irel raq bs gur gevybtl oneerq gur qbbe, gb sbepr gur cynlre punenpgre gb rkcyber engure guna whfg eha njnl.

Second is simply the design finesse of forcing the player to look for another exit. And there are plenty, including one a couple steps away: a chimney which is too narrow to carry much of anything, including a large treasure that is in the same room.

I overall count four distinct methods (not including the fact the trapdoor eventually will stay open), which really gives the feel of player choice. There are enough routes and it is non-obvious what the most efficient one is (I’m guessing every walkthrough of this game is very different).

One last catch is that while most of the edits from original mainframe Zork seem to be simply rooms removed (along with exits that don’t exist any more) there is one section that is changed enough I’m not sure what to do.

> e
Dome Room
You are at the periphery of a large dome, which forms the ceiling of another room below. Protecting you from a precipitous drop is a wooden railing which circles the dome.

> tie rope to railing
The rope drops over the side and comes within ten feet of the floor.

> d
Torch Room
This is a large room with a prominent doorway leading to a down staircase. Above you is a large dome. Up around the edge of the dome (20 feet up) is a wooden railing. In the center of the room sits a white marble pedestal.
A piece of rope descends from the railing above, ending some five feet above your head.
Sitting on the pedestal is a flaming torch, made of ivory.

The rope is too high to climb back up, and there doesn’t seem to be any normal exits.

There’s a few other locations with the torch room, but otherwise this seems to be a dead end (note the rope is too high to climb back up). There’s a granite wall that I recall should let me teleport with just >TOUCH GRANITE WALL, but it doesn’t work. My theory is I need to defeat the thief first, because the other end is in the thief’s lair, but it’s possible there’s another angle altogether I haven’t thought of.

This is unfortunate because the torch is the “unlimited turns” light source of the game; the lantern will eventually run out of battery and go dark. I’m confident there was a lot of intention here on the part of the authors; they probably felt like being able to walk anywhere with an unlimited light source too early would undercut the tension they did a good part building by barring the initial way out. (I remember my childhood self having particular dread of the dark in this game, especially the time my lantern winked out and all I was left with was a book of matches.)

I’m otherwise in the clear on all the rest of the puzzles, so it’s possible I’ll have won this by next time I report in.


Posted June 28, 2018 by Jason Dyer in Interactive Fiction

Tagged with

Zork I: Kishōtenketsu   1 comment

The 1981 packaging for Zork I, that followed the infamous TRS-80 packaging. Via MIT Technology Review, from the collection of Mike Dornbrook. There are other nice pictures there, including Lebling’s hand-drawn map of original Zork. Notice Infocom hasn’t settled on “interactive fiction” yet but instead calls this “An INTERLOGIC(tm) prose adventure”.

Usually, when I see people apply traditional plot structures to games, they’re thinking of the traditional rising action-climax-falling action “mountain”. Generally, the overarching story is said to have such as structure, as well as the incidents along the way; sort of a fractal mountain, so to speak.

However, I’ve been wondering if this is always the most appropriate game structure, because it relies on conflict; in some Western theory texts, you can find the claim that story always relies on conflict.

Kishōtenketsu is a structure that shows up in in Chinese, Korean and Japanese stories which can be, to a real extent, conflict-free. Instead of a Three-Act Structure, it has four:

Ki: Introduces characters and other necessary information.

Shō: Follows any lead characters, but without major changes.

Ten: Provides an unexpected development. This is the essential substitute for the climax, because it may not be a “confrontation”, but can be just an unusual change in the environment, or enigmatic development.

Ketsu: The conclusion, which unifies the original elements with the “twist”.

The key here is the the unexpected development or “twist” might not even be something resolved by the main characters, or even “resolved” in a traditional sense. Example:

1. Karen and Mira pack for a roadtrip.

2. Karen and Mira alternate turns driving, and talk about their lives.

3. Around midnight, they see what appears to be a flying saucer. They park, step out of their car, and take photos. The saucer never gets closer and eventually disappears.

4. They finally arrive at a hotel, talking about what they just saw.

And, sure: with this example you could say the conflict is “in their minds” or some such, and do the same with any other kishōtenketsu plot, but after a certain point Traditional Three-Act starts to look like person with a hammer desperately searching for nails (or maybe one of those people who tries to apply The Hero’s Journey to everything).

The rule of thumb seems to be: ten is about contrast, not conflict (conflict can arise from the contrast, but that’s a subset of the bigger idea). The ten phase can also resembles a traditional adventure game puzzle.

> e
Round Room
This is a circular stone room with passages in all directions. Several of them have unfortunately been blocked by cave-ins.

> e
Loud Room
This is a large room with a ceiling which cannot be detected from the ground. There is a narrow passage from east to west and a stone stairway leading upward. The room is deafeningly loud with an undetermined rushing sound. The sound seems to reverberate from all of the walls, making it difficult even to think.
On the ground is a large platinum bar.

> look
look look …

> take bar
bar bar …

Maybe? The first act here is the preceding actions, the description of the loud room is the development, and the parser’s reaction to any action other than movement is the twist. There’s two possible resolutions: one entirely logical involving finding the source of the noise and shutting it off (spoiled in rot13: gur arneol qnz), the other being almost hilariously abstruse (Vs lbh fnl rpub lbh trg gur zrffntr “Gur npbhfgvpf bs gur ebbz punatr fhogyl.” naq gur rssrpg fgbcf.) The first resolution is particularly satisfying and unifying — it resolves and explains the contrast.

Perhaps I’m reaching a little, but I have read people who exclude incidents such as the puzzle above from being part of a plot; yet, in terms of actual effort, and my mental memory of the trials and struggles of a game, these enigmatic elements form a story in my head. For me, the change in parser message comes across more as contrast rather than conflict. Maybe that’s why it goes unrecognized.

Posted June 25, 2018 by Jason Dyer in Interactive Fiction

Tagged with

Zork I: Storm-Tossed Trees   2 comments

This map came with the commercial packaging. I’ve never been quite sure what part of the Zorkiverse this shows.

One significant difference between playing this game compared to the original mainframe version is that back then, it was second in my project after Adventure. This time, it’s after I’ve played a long sequence leading up to 1980, and the effect is like stepping from silent movies into sound, or black and white into color.

I’m not meaning just the parser (which does allow all the full features of Infocom and modern games we’d expect, as opposed to requiring two words only). I haven’t been using the expanded parser that much. I even had to adjust at one point went finding the lantern at the start of the game; I typed ON which works just fine in some of the two-word games, but Zork was expecting TURN LANTERN ON. Whoops.

It’s more just the detail and atmosphere. You start outside, by the famous boarded-up white house, with no direction at all. Then you’re left to discover there’s a world underground. This matches a lot of the games from the same era, but even outside, it feels like all the senses are being used.

> listen to trees
The pines and the hemlocks seem to be murmuring.

You hear in the distance the chirping of a song bird.

> s
Storm-tossed trees block your way.

The small, quiet details feel like writing, not just functional description, but writing for its own sake. There is still one foot in the just-the-facts style:

You are in a clearing, with a forest surrounding you on all sides. A path leads
On the ground is a pile of leaves.

but enough extra detail to be satisfying.

> count leaves
There are 69,105 leaves here.

> jump in leaves

> move leaves
In disturbing the pile of leaves, a grating is revealed.

Posted June 23, 2018 by Jason Dyer in Interactive Fiction

Tagged with

Zork I (1980)   Leave a comment

I’ve already written about the original mainframe version of Zork (by Tim Anderson, Marc Blank, Bruce Daniels and Dave Lebling). The common wisdom is that when Infocom was formed, the game was too large to fit onto a floppy, so it was split into three parts: Zork I, Zork II, and Zork III.

The reality is more that the majority of the game became Zork I, some of the spare locations and puzzles made it into Zork II, and Zork III has almost nothing in common except for some elements of the endgame.

The ramification for me is that I still have essentially all the notes necessary to complete the game! I’m going to map it fresh to still feel like I’m playing, but this is definitely going to be more like a replay than the epic multi-month struggle mainframe Zork turned out to be. I’ll still try to slow down and make design observations, and see if I can find any new secrets.

There were quite a few Zork releases; I have release 2 (the original TRS-80 release), release 88 (the most common version, and the one I believe you get if you buy this game from and the Solid Gold release (which comes with in-game hints). I’m probably just going to do most of my playing in the newest version, because mucking about version 2, it doesn’t look that different from the last release! There just seem to be numerous bug-fixes, but others have already done an excellent job of tracking which bugs appear in all 14 known releases. (An even more extensive bug list is here.)

The earliest releases of Zork I (Versions 2 and 5) can become very confused if you nest objects too deeply in your inventory, such as putting the lunch in the sack, then the sack in the coffin. You may get very spurious output from the INVENTORY command like “Such language in a high-class establishment like this!” messages, with other random junk interspersed in it. This can also lead to the object hierarchy getting screwed up, in such a way that an INVENTORY might claim that you are carrying a bunch of rooms around!

Posted June 20, 2018 by Jason Dyer in Interactive Fiction

Tagged with