RSS

Tag Archives: lucasarts

Ten Great Adventure-Game Puzzles

This blog has become, among other things, an examination of good and bad game-design practices down through the years, particularly within the genre of adventure games. I’ve always tried to take the subject seriously, and have even dared to hope that some of these writings might be of practical use to someone — might help designers of the present or future make better games. But, for reasons that I hope everyone can understand, I’ve spent much more time illuminating negative than positive examples of puzzle design. The fact is, I don’t feel much compunction about spoiling bad puzzles. Spoiling the great puzzles, however, is something I’m always loath to do. I want my readers to have the thrill of tackling those for themselves.

Unfortunately, this leaves the situation rather unbalanced. If you’re a designer looking for tips from the games of the past, it certainly helps to have some positive as well as negative examples to look at. And even if you just read this blog to experience (or re-experience) these old games through the sensibility of your humble author here, you’re missing out if all you ever hear about are the puzzles that don’t work. So, when my reader and supporter Casey Muratori wrote to me to suggest an article that singles out some great puzzles for detailed explication and analysis, it sounded like a fine idea to me.

It’s not overly difficult to generalize what makes for fair or merely “good” puzzles. They should be reasonably soluble by any reasonably intelligent, careful player, without having to fall back on the tedium of brute-forcing them or the pointlessness of playing from a walkthrough. As such, the craft of making merely good or fair puzzles is largely subsumed in lists of what not to do — yes, yet more negative reinforcements! — such as Graham Nelson’s “Bill of Player’s Rights” or Ron Gilbert’s “Why Adventure Games Suck and What We Can Do About It.” It’s much more difficult, however, to explain what makes a brilliant, magical puzzle. In any creative discipline, rules will only get you so far; at some point, codification must make way for the ineffable. Still, we’ll do the best we can today, and see if we can’t tease some design lessons out of ten corking puzzles from adventure games of yore.

Needless to say, there will be spoilers galore in what follows, so if you haven’t played these games, and you think you might ever want to, you should absolutely do so before reading about them here. All ten games are found in my personal Hall of Fame and come with my highest recommendation. As that statement would indicate, I’ve restricted this list to games I’ve already written about, meaning that none of those found here were published after 1992. I’ve split the field evenly between parser-driven text adventures and point-and-click graphic adventures. If you readers enjoy and/or find this article useful, then perhaps it can become a semi-regular series going forward.

And now, with all that said, let’s accentuate the positive for once and relive some classic puzzles that have been delighting their players for decades.


1. Getting past the dragon in Adventure

By Will Crowther and Don Woods, public domain, 1977.

How it works: Deep within the bowels of Colossal Cave, “a huge green dragon bars the way!” Your objective, naturally, is to get past him to explore the area beyond. But how to get him out of the way? If you throw your axe at him, it “bounces harmlessly off the dragon’s thick scales.” If you unleash your fierce bird friend on him, who earlier cleared a similarly troublesome snake out of your way, “the little bird attacks the green dragon, and in an astounding flurry gets burnt to a cinder.” If you simply try to “attack dragon,” the game mocks you: “With what? Your bare hands?” You continue on in this way until, frustrated and thoroughly pissed off, you type, “Yes,” in response to that last rhetorical question. And guess what? It wasn’t a rhetorical question: “Congratulations! You have just vanquished a dragon with your bare hands! (Unbelievable, isn’t it?)”

Why it works: In many ways, this is the most dubious puzzle in this article. (I do know how to make an entrance, don’t I?) It seems safe to say that the vast majority of people who have “solved” it have done so by accident, which is not normally a sign of good puzzle design. Yet classic text adventures especially were largely about exploring the possibility space, seeing what responses you could elicit. The game asks you a question; why not answer it, just to see what it does?

This is an early example of a puzzle that could never have worked absent the parser — absent its approach to interactivity as a conversation between game and player. How could you possibly implement something like this using point and click? I’m afraid a dialog box with a “YES” and “NO” just wouldn’t work. In text, though, the puzzle rewards the player’s sense of whimsy — rewards the player, one might even say, for playing in the right spirit. Interactions like these are the reason some of us continue to love text adventures even in our modern era of photo-realistic graphics and surround sound.

Our puzzling design lesson: A puzzle need not be complicated to delight — need barely be a puzzle at all! — if it’s executed with wit and a certain joie de vivre.


2. Exploring the translucent maze in Enchanter

By Marc Blank and David Lebling, Infocom, 1983

How it works: As you’re exploring the castle of the mad wizard Krill, you come upon a maze of eight identical rooms in the basement. Each location is “a peculiar room, whose cream-colored walls are thin and translucent.” All of the rooms are empty, the whole area seemingly superfluous. How strange.

Elsewhere in the castle, you’ve discovered (or will discover) a few other interesting items. One is an old book containing “The Legend of the Unseen Terror”:

This legend, written in an ancient tongue, goes something like this: At one time a shapeless and formless manifestation of evil was disturbed from millennia of sleep. It was so powerful that it required the combined wisdom of the leading enchanters of that age to conquer it. The legend tells how the enchanters lured the Terror "to a recess deep within the earth" by placing there a powerful spell scroll. When it had reached the scroll, the enchanters trapped it there with a spell that encased it in the living rock. The Terror was so horrible that none would dare speak of it. A comment at the end of the narration indicates that the story is considered to be quite fanciful; no other chronicles of the age mention the Terror in any form.

And you’ve found a map, drawn in pencil. With a start, you realize that it corresponds exactly to the map you’ve drawn of the translucent maze, albeit with an additional, apparently inaccessible room located at point P:

B       J
!      / \
!     /   \
!    /     \
!   K       V
!          / \
!         /   \
!        /     \
R-------M       F
 \     /
  \   /
   \ /
    H       P


Finally, you’ve found a badly worn pencil, with a point and an eraser good for just two uses each.

And so you put the pieces together. The Terror and the “powerful spell scroll” mentioned in the book are encased in the “living rock” of the maze in room P. The pencil creates and removes interconnections between the rooms. You need to get to room P to recover the scroll, which you’ll need to defeat Krill. But you can’t allow the Terror to escape and join forces with Krill. A little experimentation — which also causes you to doom the world to endless darkness a few times, but there’s always the restore command, right? — reveals that the Terror moves one room per turn, just as you do. So, your objective must be to let him out of room P, but trap him in another part of the maze before he can get to room B and freedom. You need to give him a path to freedom to get him moving out of room P, then cut it off.

There are many possible solutions. One is to go to room H, then draw a line connecting P and F. Sensing a path to freedom, the Terror will move to room F, whereupon you erase the connection you just drew. As you do that, the Terror moves to room V, but you erase the line between V and M before he can go further, trapping him once again. Now, you have just enough pencil lead left to draw a line between H and P and recover the scroll.

Why it works: Solving this puzzle comes down to working out how a system functions, then exploiting it to do your bidding. (Small wonder so many hackers have found text adventures so appealing over the years!) First comes the great mental leap of connecting these four disparate elements which you’ve found scattered about: an empty maze, a book of legends, a map, and a pencil. Then, after that great “a-ha!” moment, you get the pleasure of working out the mechanics of the Terror’s movements and finally of putting together your plan and carrying it out. Once you understand how everything works, this final exercise is hardly a brain burner, but it’s nevertheless made much more enjoyable by the environment’s dynamism. You feel encouraged to sit down with your map and work out your unique approach, and the game responds as you expect it to.  This simulational aspect, if you will, stands in marked contrast to so many static adventure-game puzzles of the “use X on Y because the designer wants you to” variety.

It’s worth taking note as well of the technology required to implement something like this. It demands a parser capable of understanding a construction as complicated as “draw line from H to P,” a game engine capable of re-jiggering map connections and rewriting room descriptions on the fly, and even a measure of artificial intelligence, including a path-finding algorithm, for the Terror. Nobody other than Infocom could have implemented a puzzle of this dynamic complexity in 1983. I’ve often noted that the keystone of Infocom’s design genius was their subtly advanced technology in comparison to anyone else working in their field; this puzzle provides fine proof of what I mean by that.

Our puzzling design lesson: Technology isn’t everything in game design, but it isn’t nothing either; the tools you choose to work with have a direct impact on the types of puzzles you can attempt. A corollary to this statement is that the technology which goes into design affordances is often far more subtle than that which allows whiz-bang graphics and sound.


3. Getting the babel fish in The Hitchhiker’s Guide to the Galaxy

By Douglas Adams and Steve Meretzky, Infocom, 1984

How it works: You’ve escaped planet Earth just seconds before its destruction at the hands of a Vogon Constructor Fleet. You’re now in the hold of one of the Vogon ships:

Vogon Hold
This is a squalid room filled with grubby mattresses, unwashed cups, and unidentifiable bits of smelly alien underwear. A door lies to port, and an airlock lies to starboard.

There is a satchel here.

In the corner is a glass case with a switch and a keyboard.
It looks like the glass case contains:
an atomic vector plotter

Along one wall is a tall dispensing machine.

That dispensing machine contains babel fish, which, when inserted into your ear, will allow you to understand the many strange alien languages you’ll soon be encountering. Rather than belabor this famously extended puzzle point by point, I’ll just provide you with a transcript of the steps you need to go through to solve it. In real life, of course, you would spend much more time bumbling and fumbling than does our ideal player here.

>examine machine
The dispenser is tall, has a button at around eye-level, and says "Babel Fish" in large letters. Anything dispensed would probably come out the slot at around knee-level. It bears a small label which reads "Another fine product of the Sirius Cybernetics Corporation."

>i
You have:
no tea
a thing your aunt gave you which you don't know what it is
a towel
It looks like your gown contains:
pocket fluff
The Hitchhiker's Guide
an electronic Sub-Etha signaling device
a loose pile of junk mail
a toothbrush
a flathead screwdriver

>push button
A single babel fish shoots out of the slot. It sails across the room and through a small hole in the wall, just under a metal hook.

>remove gown
Okay, you're no longer wearing your gown.

>hang gown on hook
The gown is now hanging from the hook, covering a tiny hole.

>push button
A single babel fish shoots out of the slot. It sails across the room and hits the dressing gown. The fish slides down the sleeve of the gown and falls to the floor, vanishing through the grating of a hitherto unnoticed drain.

>put towel on drain
The towel completely covers the drain.

>push button
A single babel fish shoots out of the slot. It sails across the room and hits the dressing gown. The fish slides down the sleeve of the gown and falls to the floor, landing on the towel. A split-second later, a tiny cleaning robot whizzes across the floor, grabs the fish, and continues its breakneck pace toward a tiny robot panel at the base of the wall. The robot zips through the panel, and is gone.

>cover panel with satchel
Okay, the satchel is lying on its side in front of the tiny robot panel.

>push button
A single babel fish shoots out of the slot. It sails across the room and hits the dressing gown. The fish slides down the sleeve of the gown and falls to the floor, landing on the towel. A split-second later, a tiny cleaning robot whizzes across the floor, grabs the fish, and continues its breakneck pace toward a tiny robot panel at the base of the wall. The robot plows into the satchel, sending the babel fish flying through the air in a graceful arc. A small upper-half-of-the-room cleaning robot flies into the room, catches the babel fish (which is all the flying junk it can find), and exits.

>put mail on satchel
Okay, the loose pile of junk mail is now sitting on the satchel.

>push button
A single babel fish shoots out of the slot. It sails across the room and hits the dressing gown. The fish slides down the sleeve of the gown and falls to the floor, landing on the towel. A split-second later, a tiny cleaning robot whizzes across the floor, grabs the fish, and continues its breakneck pace toward a tiny robot panel at the base of the wall. The robot plows into the satchel, sending the babel fish flying through the air in a graceful arc surrounded by a cloud of junk mail. Another robot flies in and begins madly collecting the cluttered plume of mail. The babel fish continues its flight, landing with a loud "squish" in your ear.

Why it works: This is easily the most famous text-adventure puzzle of all time, one whose reputation for difficulty was so extreme in the 1980s that Infocom took to selling tee-shirts emblazoned with “I got the babel fish!” In truth, though, its reputation is rather exaggerated. There are other puzzles in Hitchhiker’s which rely heavily — perhaps a little too heavily — on the ability to think with the skewed logic of Douglas Adams. This puzzle, however, really isn’t one of them. It’s certainly convoluted and time-consuming, but it’s also both logical in a non-skewed sense and thoroughly satisfying to work out step by step. From the standpoint of the modern player, its only really objectionable aspects are the facts that you can easily arrive at it without having everything you need to solve it, and that you have a limited amount of tries — i.e., a limited number of spare babel fish — at your disposal. But if you have made sure to pick up everything that isn’t nailed down in the early part of the game, and if you use the save system wisely, there’s no reason you can’t solve this on your own and have immense fun doing so. It’s simply a matter of saving at each stage and experimenting to find out how to progress further. The fact that it can be comfortably solved in stages makes it far less infuriating than it might otherwise be. You always feel like you’re making progress — coming closer, step by step, to the ultimate solution. There’s something of a life lesson here: most big problems can be solved by first breaking them down into smaller problems and solving those one at a time.

Importantly, this puzzle is also funny, fitting in perfectly with Douglas Adams’s comedic conception of a universe not out so much to swat you dead all at once as to slowly annoy you to death with a thousand little passive-aggressive cuts.

Our puzzling design lesson: Too many adventure-game designers think that making a comedy gives them a blank check to indulge in moon logic when it comes to their puzzles. The babel fish illustrates that a puzzle can be both funny and fair.


4. Using the T-removing machine in Leather Goddesses of Phobos

By Steve Meretzky, Infocom, 1986

How it works: While exploring this ribald science-fiction comedy, Infocom’s last big hit, you come upon a salesman who wants to trade you something for the “odd machine” he carries. When you finally find the item he’s looking for and take possession of the machine, he gives you only the most cryptic description of its function: “‘It’s a TEE remover,’ he explains. You ponder what it removes — tea stains, hall T-intersections — even TV star Mr. T crosses your mind, until you recall that it’s only 1936.”

Experimentation will eventually reveal that this “tee-remover” is actually a T-remover. If you put something inside it and turn it on, said something becomes itself minus all of the letter Ts in its name. You need to use the machine to solve one clever and rather hilarious puzzle, turning a jar of untangling cream into unangling cream, thereby to save poor King Mitre’s daughter from a tragic fate:

In the diseased version of the legend commonly transmitted on Earth, Mitre is called Midas. The King was granted his wish that everything he touched would turn to gold. His greed caught up with him when he transformed even his own daughter into gold.

King Mitre's wish was, in fact, that everything he touched would turn to forty-five degree angles. No one has ever explained this strange wish; the most likely hypothesis is a sexual fetish. In any case, the tale has a similar climax, with Mitre turning his own daughter into a forty-five degree angle.

This is pretty funny in itself, but the greatest fun offered by the T-remover is in all the other places you can use it: on a tray (“It looks a little like Ray whatsisname from second grade.”); on a rabbit (“A bearded rabbi wearing a prayer shawl leaps out of the machine, recites a Torah blessing, and dashes off in search of a minyan.”); a raft (“It sinks like a stone. I guess a raf doesn’t float nearly as well as a raft.”); a pair of cotton balls (“Let’s just say that some poor male raccoon is speaking in a particularly high-pitched voice.”).

Why it works: The T-removing machine is sometimes held up as another puzzle concept that couldn’t possibly work in any other medium than text. I’m not sure if that’s literally true — later in this very list we’ll see another funny wordplay-based puzzle that does work inside a graphic adventure — but it certainly is true that no responsible producer would agree to pay for all the work required to implement all those one-off, just-for-fun responses in graphics. In text, though, they’re just a matter of an additional sentence or two.

Adventure designer Bob Bates likes to point out that the vast majority of what the player attempts to do will always be wrong; that’s just the nature of the endeavor. When she does one of these wrong things, the designer needs to do as much as possible to entertain her. A later generation would dub this the “juicy” approach to game design: rewarding curiosity and creativity, even if none of it contributes directly to the prosaic task of finishing the game. Steve Meretzky had a great puzzle already with the T-remover, King Mitre, and the untangling/unangling cream. He could have left it at that by coming up with excuses for why you couldn’t put other things in the T-remover. Instead he stayed faithful to his invention and implemented many alternatives alongside the “correct” use of the machine.

Our puzzling design lesson: Don’t ignore the “else” in the “if, then, else” of an adventure game. It makes your game feel like a living world rather than an arbitrary collection of logic gates to be navigated, and shows that you respect your player’s creativity.


5. Escaping the pirate Lafond in Plundered Hearts

By Amy Briggs, Infocom, 1987

How it works: Would I be engaging in too much gender stereotyping if I noted that the puzzles in the only Infocom game to be written by a woman often deal in social intelligence rather than abstract logic? This is another fairly lengthy sequence, so it’s best if I once again just show you what happens if you do everything correctly.

"Welcome, ma petite." Lafond bows you in.

Lafond's Bedroom
Lafond's bedroom shows all the outpourings of his megalomania. Royal hues of
purple and gold weigh down the hangings on the bed and the eastward window, as if trying to smother the moonbeam shining in.

Lafond is leering, lip curled.

A lace-covered table crouches beside a wing-backed chair in one corner. Sitting on the table is a green goblet, a blue goblet and a flagon.

"Have some wine." Lafond pours wine into two glasses, giving a blue one to you. "Drink this down. We have a long night ahead of us." He drains his own.

>drink wine
You empty the blue goblet of wine.

"Good girl," he says, "Let's see more cooperation of this sort."

Suddenly, the door slams open. It is Jamison, coatless, sword bared, his shirt ripped. "Thank God I am not too late. Leave, darling, before I skewer this dog to his bedposts," he cries. The scar on his cheek gleams coldly.

With a yell, Crulley and the butler jump out of the darkness behind him. Nicholas struggles, but soon lies unconscious on the floor.

"Take him to the dungeon," Lafond says, setting down his glass. "You, butler, stay nearby. I do not wish to be disturbed again.

"Now that we are rid of that intrusion, cherie, I will change into something more comfortable. Pour me more wine." He crosses to the wardrobe removing his coat and vest, turned slightly away from you.

>pour wine into green goblet
You fill the green goblet with wine.

"In private, call me Jean, or whatever endearment you choose, once I have approved it." Lafond is looking into the wardrobe.

>squeeze bottle into green goblet
You squeeze three colorless drops into the green goblet. You sense Lafond
hesitate, then continue primping.

The butler enters, laying a silver tray of cold chicken on the table. "The kitchen wench has gone, your grace. I took the liberty of fetching these
myself." He bows and leaves the room.

"Sprinkle some spices on the fowl, ma petite," Lafond says, donning a long brocade robe, his back to you. "They are hot, but delicious."

>get spices
You take a pinch of spices between your thumb and forefinger.

"Tsk. The cook has gone too far. She shall be 'leaving us' tomorrow." Lafond adjusts the lace at his neck.

>put spices on chicken
You sprinkle some spices on a wing and nibble it. The peppery heat hits you like a wave, leaving you gasping, eyes watering.

Lafond strolls to the table smiling slyly. "But you haven't finished pouring the wine." He tops off both glasses. "Which glass was mine? I seem to have forgotten." He points at the green goblet and smiles in a way that does not grant you confidence. "Is this it?"

>no
You shake your head, teeth clenched.

"Ah yes, of course." Lafond obligingly takes the blue goblet.

He inhales deeply of the bouquet of his wine, then turns to you. "You must think me very naive to fall for such a trick. I saw you pour something into one of these glasses -- although I cannot smell it." He switches goblets, setting the blue goblet into your nerveless grasp and taking up the other, smiling evilly. "Now you will drink from the cup intended for me."

>drink from blue goblet
You empty the blue goblet of wine.

"Good girl," he says. Lafond takes the leather bottle and drops it out the window. "You shall not need this. You may suffer no headaches in my employ."

He lifts his glass to drink, but stops. "Your father, for all his idiotic meddling in other people's business, is not a fool. I doubt you are, either." He calls in the butler, ordering him to empty the green goblet. The man reports no odd taste and returns to his post.

>get spices
You take a pinch of spices between your thumb and forefinger.

Lafond draws near, whispering indecencies. He caresses your lily white neck, his fingers ice-cold despite the tropic heat.

>throw spices at lafond
You blow the spices off your fingertips, directly into Lafond's face. He
sneezes, his eyes watering from the heat of the peppers. Reaching blindly for some wine, he instead upsets the table, shattering a glass. Lafond stumbles cursing out of the room, in search of relief.

>s
You run out -- into the butler's barrel chest and leering grin. You return to the bedroom, the butler following. "The governor said you were not to leave this room."

>z
Time passes...

The butler seems to be having some problems stifling a yawn.

>z
Time passes...


The butler's eyes are getting heavier.

>z
Time passes...

The butler collapses, head back, snoring loudly.

>s
You creep over the prostrate butler.

Why it works: Plundered Hearts is an unusually driven text adventure, in which the plucky heroine you play is constantly forced to improvise her way around the dangers that come at her from every direction. In that spirit, one can almost imagine a player bluffing her way through this puzzle on the first try by thinking on her feet and using her social intuition. Most probably won’t, mark you, but it’s conceivable, and that’s what makes it such a good fit with the game that hosts it. This death-defying tale doesn’t have time to slow down for complicated mechanical puzzles. This puzzle, on the other hand, fits perfectly with the kind of high-wire adventure story — adventure story in the classic sense — which this game wants to be.

Our puzzling design lesson: Do-or-die choke point should be used sparingly, but can serve a plot-heavy game well as occasional, exciting punctuations. Just make sure that they feel inseparable from the narrative unfolding around the player — not, as is the case with so many adventure-game puzzles, like the arbitrary thing the player has to do so that the game will feed her the next bit of story.


6. Getting into Weird Ed’s room in Maniac Mansion

By Ron Gilbert, Lucasfilm Games, 1987

How it works: In Ron Gilbert’s first adventure game, you control not one but three characters, a trio of teenage stereotypes who enter the creepy mansion of Dr. Fred one hot summer night. Each has a unique skill set, and each can move about the grounds independently. Far from being just a gimmick, this has a huge effect on the nature of the game’s puzzles. Instead of confining yourself to one room at a time, as in most adventure games, your thinking has to span the environment; you must coordinate the actions of characters located far apart. Couple this with real-time gameplay and an unusually responsive and dynamic environment, and the whole game starts to feel wonderfully amenable to player creativity, full of emergent possibilities.

In this example of a Maniac Mansion puzzle, you need to search the bedroom of Weird Ed, the son of the mad scientist Fred and his bonkers wife Edna. If you enter while he’s in there, he’ll march you off to the house’s dungeon. Thus you have to find a way to get rid of him. In the sequence below, we’ve placed the kid named Dave in the room adjacent to Ed’s. Meanwhile Bernard is on the house’s front porch. (This being a comedy game, we won’t question how these two are actually communicating with each other.)

Dave is poised to spring into action in the room next to Weird Ed’s.

Bernard rings the doorbell.

Ed heads off to answer the door.

Dave makes his move as soon as Ed clears the area.

Dave searches Ed’s room.

But he has to hurry because Ed, after telling off Bernard, will return to his room.

Why it works: As graphics fidelity increases in an adventure game, the possibility space tends to decrease. Graphics are, after all, expensive to create, and beautiful high-resolution graphics all the more expensive. By the late 1990s, the twilight of the traditional adventure game as more than a niche interest among gamers, the graphics would be very beautiful indeed, but the interactivity would often be distressingly arbitrary, with little to no implementation of anything beyond the One True Path through the game.

Maniac Mansion, by contrast, makes a strong argument for the value of primitive graphics. This game that was originally designed for the 8-bit Commodore 64 uses its crude bobble-headed imagery in the service of the most flexible and player-responsive adventure design Lucasfilm Games would ever publish over a long and storied history in graphic adventures. Situations like the one shown above feel like just that — situations with flexible solutions — rather than set-piece puzzles. You might never have to do any of the above if you take a different approach. (You could, for instance, find a way to befriend Weird Ed instead of tricking him…) The whole environmental simulation — and a simulation really is what it feels like — is of remarkable complexity, especially considering the primitive hardware on which it was implemented.

Our puzzling design lesson: Try thinking holistically instead of in terms of set-piece roadblocks, and try thinking of your game world as a responsive simulated environment for the player to wander in instead of as a mere container for your puzzles and story. You might be surprised at what’s possible, and your players might even discover emergent solutions to their problems which you never thought of.


7. Getting the healer’s ring back in Hero’s Quest (later known as Quest for Glory I)

By Lori Ann and Corey Cole, Sierra, 1989

How it works: Hero’s Quest is another game which strains against the constrained norms in adventure-game design. Here you create and develop a character over the course of the game, CRPG-style. His statistics largely define what he can do, but your own choices define how those statistics develop. This symbiosis results in an experience which is truly yours. Virtually every puzzle in the game admits of multiple approaches, only some (or none) of which may be made possible by your character’s current abilities. The healer’s lost ring is a fine example of how this works in practice.

The bulletin board at the Guild of Adventurers tells you about the missing ring.

You go to inquire with the healer. Outside her hut is a tree, and on the tree is the nest of a sort of flying lizard.

Hmm, there’s another of these flying lizards inside.

I’ll reveal now that the ring is in the nest. But how to get at it? The answer will depend on the kind of character you’ve built up. If your “throwing” skill is sufficient, you can throw rocks at the nest to drive off the lizard and knock it off the tree. If your “magic” skill is sufficient and you’ve bought the “fetch” spell, you can cast it to bring the nest to you. Or, if your “climb” skill is sufficient, you can climb the tree. If you can’t yet manage any of this, you can continue to develop your character and come back later. Or not: the puzzle is completely optional. The healer rewards you only with six extra gold pieces and two healing potions, both of which you can earn through other means if necessary.

Why it works: This puzzle would be somewhat problematic if solving it was required to finish the game. Although several lateral nudges are provided that the ring is in the nest, it strikes me as dubious to absolutely demand that the player put all the pieces together — or, for that matter, to even demand that the player notice the nest, which is sitting there rather inconspicuously in the tree branch. Because solving the puzzle isn’t an absolute requirement, however, it becomes just another fun little thing to discover in a game that’s full of such generosity. Some players will notice the nest and become suspicious, and some won’t. Some players will find a way to see what’s in it, and some won’t. And those that do find a way will do so using disparate methods at different points in the game. Even more so than Maniac Mansion, Hero’s Quest gives you the flexibility to make your own story out of its raw materials. No two players will come away with quite the same memories.

This melding of CRPG mechanics with adventure-game elements is still an underexplored area in a genre which has tended to become less rather than more formally ambitious as it’s aged. (See also Origin’s brief-lived Worlds of Ultima series for an example of games which approach the question from the other direction — adding adventure-game elements to the CRPG rather than the other way around — with equally worthy results.) Anything adventures can do to break out of the static state-machine paradigm in favor of flexibility and dynamism is generally worth doing. It can be the difference between a dead museum exhibition and a living world.

Our puzzling design lesson: You can get away with pushing the boundaries of fairness in optional puzzles, which you can use to reward the hardcore without alienating your more casual players. (Also, go read Maniac Mansion‘s design lesson one more time.)


8. Blunting the smith’s sword in Loom

By Brian Moriarty, Lucasfilm Games, 1990

How it works: Games like Hero’s Quest succeed by being generously expansive, while others, like Loom, succeed by boiling themselves down to a bare essence. To accompany its simple storyline, which has the rarefied sparseness of allegory, Loom eliminates most of what we expect out of an adventure game. Bobbin Threadbare, the hero of the piece, can carry exactly one object with him: a “distaff,” which he can use to “spin” a variety of magical “drafts” out of notes by tapping them out on an onscreen musical staff. Gameplay revolves almost entirely around discovering new drafts and using them to solve puzzles.

The ancestor of Loom‘s drafts is the spell book the player added to in Infocom’s Enchanter series. There as well you cast spells to solve puzzles — and, in keeping with the “juicy” approach, also got to enjoy many amusing effects when you cast them in the wrong places. But, as we saw in our earlier explication of one of Enchanter‘s puzzles, you can’t always rely on your spell book in that game. In Loom, on the other hand, your distaff and your Book of Patterns — i.e., drafts — is all you have. And yet there’s a lot you can do with them, as the following will illustrate.

Bobbin eavesdrops from the gallery as Bishop Mandible discusses his plan for world domination with one of his lackeys. His chief smith is just sharpening the last of the swords that will be required. Bobbin has a pattern for “sharpen.” That’s obviously not what we want to do here, but maybe he could cast it in reverse…

Unfortunately, he can’t spin drafts as long as the smith is beating away at the sword.

Luckily, the smith pauses from time to time to show off his handwork.

Why it works: Loom‘s minimalist mechanics might seem to allow little scope for clever puzzle design. Yet, as this puzzle indicates, such isn’t the case at all. Indeed, there’s a certain interactive magic, found by no means only in adventures games, to the re-purposing of simple mechanics in clever new ways. Loom isn’t a difficult game, but it isn’t entirely trivial either. When the flash of inspiration comes that a draft might be cast backward, it’s as thrilling as the thrills that accompany any other puzzle on this list.

It’s also important to note the spirit of this puzzle, the way it’s of a piece with the mythic dignity of the game as a whole. One can’t help but be reminded of that famous passage from the Book of Isaiah: “And they shall beat their swords into ploughshares, and their spears into pruning hooks: nation shall not lift up sword against nation, neither shall they learn war any more.”

Our puzzling design lesson: Wonderful games can be and have been built around a single mechanic. If you’ve got a great one, don’t hesitate to milk it for all it’s worth. Also: puzzles can illuminate — or undermine — a game’s theme as well as any other of its aspects can.


9. Teaching the cannibals how to get a head in The Secret of Monkey Island

By Ron Gilbert, Lucasfilm Games, 1990

How it works: For many of us, the first Monkey Island game is the Platonic ideal of a comedic graphic adventure: consistently inventive, painstakingly fair, endlessly good-natured, and really, truly funny. Given this, I could have chosen to feature any of a dozen or more of its puzzles here. But what I’ve chosen — yes, even over the beloved insult sword-fighting — is something that still makes me smile every time I think about it today, a quarter-century after I first played this game. Just how does a young and ambitious, up-and-coming sort of cannibal get a head?

Hapless hero Guybrush Threepwood needs the human head that the friendly local cannibals are carrying around with them.

Wait! He’s been carrying a certain leaflet around for quite some time now.

What’s the saying? “If you teach a man to fish…”

Why it works: One might call this the graphic-adventure equivalent of the text-adventure puzzle that opened this list. More than that, though, this puzzle is pure Ron Gilbert at his best: dumb but smart, unpretentious and unaffected, effortlessly likable. When you look through your inventory, trying to figure out where you’re going to find a head on this accursed island, and come upon that useless old leaflet you’ve been toting around all this time, you can’t help but laugh out loud.

Our puzzling design lesson: A comedic adventure game should be, to state the obvious, funny. And the comedy should live as much in the puzzles as anywhere else.


10. Tracking down the pendant in The Lost Files of Sherlock Holmes

By Eric Lindstrom and R.J. Berg, Electronic Arts, 1992

How it works: This interactive mystery, one of if not the finest game ever to feature Arthur Conan Doyle’s legendary detective, is notable for its relative disinterest in the physical puzzles that are the typical adventure game’s stock in trade. Instead it has you collecting more abstract clues about means, motive, and opportunity, and piecing them together to reveal the complicated murder plot at the heart of the story.

It all begins when Holmes and Watson get called to the scene of the murder of an actress named Sarah Carroway: a dark alley just outside the Regency Theatre, where she was a star performer. Was it a mugging gone bad? Was it the work of Jack the Ripper? Or was it something else? A mysterious pendant becomes one of the keys to the case…

We first learn about Sarah Carroway’s odd pendent when we interview her understudy at the theater. It was a recent gift from Sarah’s sister, and she had always worn it since receiving it. Yet it’s missing from her body.

We find the workplace of Sarah’s sister Anna. She’s also in show biz, a singer at the Chancery Opera House. The woman who shared a box with Sarah during Anna’s performances confirms the understudy’s story about the pendant. More ominously, we learn that Anna too has disappeared.

We track down Anna’s solicitor and surrogate father-figure, a kindly old chap named Jacob Farthington. He tells us that Anna bore a child to one Lord Brumwell some years ago, but was forced to give him up to Brumwell without revealing his parentage. Now, she’s been trying to assert her rights as the boy’s mother.

More sleuthing and a little bit of sneaking leads us at last to Anna’s bedroom. There we find her diary. It states that she’s hired a detective following Sarah’s murder — not, regrettably, Sherlock Holmes — to find out what became of the pendant. It seems that it contained something unbelievably important. “A humble sheet of foolscap, depending on what’s written upon it, can be more precious than diamonds,” muses Holmes.

Yet more detecting on our part reveals that a rather dense blackguard named Blackwood pawned the pendant. Soon he confesses to Sarah’s murder: “I got overexcited. I sliced her to make her stop screaming.” He admits that he was hired to recover a letter by any means necessary by “an old gent, very high tone,” but he doesn’t know his name. (Lord Brumwell, perhaps?) It seems he killed the wrong Carroway — Anna rather than Sarah should have been his target — but blundered onto just the thing he was sent to recover anyway. But then, having no idea what the pendant contained, he pawned it to make a little extra dough out of the affair. Stupid is as stupid does…

So where is the pendant — and the proof of parentage it must have contained — now? We visit the pawn shop where Blackwood unloaded it. The owner tells us that it was bought by an “inquiry agent” named Moorehead. Wait… there’s a Moorehead & Gardner Detective Agency listed in the directory. This must be the detective Anna hired! Unfortunately, we are the second to ask about the purchaser of the pendant. The first was a bit of “rough trade” named Robert Hunt.

We’re too late. Hunt has already killed Gardner, and we find him just as he’s pushing Moorehead in front of a train. We manage to nick Hunt after the deed is done, but he refuses to say who hired him or why — not that we don’t have a pretty strong suspicion by this point.

Luckily for our case, neither Gardner nor Moorehead had the pendant on him at the time of his death. We find it at last in their safe. Inside the pendant, as we suspected, is definitive proof of the boy’s parentage. Now we must pay an urgent visit to Lord Brumwell. Is Anna still alive, or has she already met the same fate as her sister? Will Brumwell go peacefully? We’ll have to play further to find out…

Why it works: Even most allegedly “serious” interactive mysteries are weirdly bifurcated affairs. The game pretty much solves the mystery for you as you jump through a bunch of unrelated hoops in the form of arbitrary object-oriented puzzles that often aren’t all that far removed from the comedic likes of Monkey Island. Even some pretty good Sherlock Holmes games, like Infocom’s Sherlock: The Riddle of the Crown Jewels, wind up falling into this trap partially or entirely. Yet The Lost Files of Sherlock Holmes stands out for the way it really does ask you to think like a detective, making connections across its considerable length and breadth. While you could, I suppose, brute-force your way through even the multifaceted puzzle above by visiting all of the locations and showing everything to every suspect, it’s so much more satisfying to go back through Watson’s journal, to muse over what you’ve discovered so far, and to make these connections yourself. Lost Files refuses to take the easy way out, choosing instead to take your role as the great detective seriously. For that, it can only be applauded.

Our puzzling design lesson: Graham Nelson once indelibly described an adventure game as “a narrative at war with a crossword.” I would say in response that it really need not be that way. A game need not be a story with puzzles grafted on; the two can harmonize. If you’re making an interactive mystery, in other words, don’t force your player to fiddle with sliding blocks while the plot rolls along without any other sort of input from her; let your player actually, you know, solve a mystery.


(Once again, my thanks to Casey Muratori for suggesting this article. And thank you to Mike Taylor and Alex Freeman for suggesting some of the featured puzzles.)

 
 

Tags: , , , , , , , , , , , ,

Indiana Jones and the Fate of Atlantis (or, Of Movies and Games and Whether the Twain Shall Meet)

You ask why there are movements in movie history. Why all of a sudden there are great Japanese films, or great Italian films, or great Australian films, or whatever. And it’s usually because there are a number of people that cross-pollinated each other.

— Francis Ford Coppola

Over the course of the late 1970s and early 1980s, George Lucas and Steven Spielberg remade the very business of film-making for better or for worse, shifting its focus from message movies and character dramas to the special-effects-heavy, escapist blockbusters that still drive Hollywood’s profits to this day. These events, which we might call the rise of the culture of the blockbuster, have long since been enshrined into the canonical history of film, filed under the names of these two leading lights.

Yet no two personalities could possibly have brought about such a dramatic shift on their own. Orbiting around Lucas and Spielberg was an entire galaxy of less prominent talents whose professional lives were profoundly affected by their association with these two new faces of modern Hollywood. They were the fellow travelers who helped Lucas and Spielberg to change the movie industry, all without ever quite being aware that they were part of any particular movement at all. Among the group were names like John Milius, Walter Murch, Willard Huyck, Randall Kleiser, Matthew Robbins, and Hal Barwood. “I can’t speak for the others,” says Robbins, “but it was my impression that nobody had the foggiest idea that there was any ‘next wave’ coming. Nobody had set their sights — except perhaps for George [Lucas].”

Out of this group of slightly lesser but undeniably accomplished lights, Hal Barwood is our special person of interest for today. He first met George Lucas in the mid-1960s, when the two were students together in the University of Southern California’s film program. Lucas, who had only recently abandoned his original dream of driving race cars in favor of this new one of making movies, was shy almost to the point of complete inarticulateness, and was far more comfortable futzing over a Moviola editing machine than he was trying to cajole live actors into doing his bidding. Nevertheless, there was a drive to this awkward young man that gradually revealed itself over the course of a longer acquaintance, and Barwood — on the surface, a far more assertive, impressive personality — soon joined Lucas’s loose clique in the role of follower rather than leader. Flying in the face of a Hollywood culture which valued realistic character dramas above all else, Lucas, Barwood, and their pals loved science fiction and fantasy, didn’t consider escapism to be a dirty word, and found the visual aesthetics of film to be every bit as interesting as their actors’ performances.

The bond thus forged would remain strong for many years. When Lucas, through the intermediation of his friend and mentor Francis Ford Coppola, got the chance to direct an actual feature film, Barwood added the first professional film credit to his own CV by helping out with the special effects on what became THX-1138, a foreboding, low-budget work of dystopic science fiction that was released to little attention in 1971. When Lucas hit it big two years later with his very different second film, the warmly nostalgic coming-of-age story American Graffiti, he bought a big old ramshackle mansion in San Anselmo, California, with the first of the proceeds, and Barwood became one of several fellow travelers who joined him and his wife in this first headquarters of a nascent corporate entity called Lucasfilm.

George Lucas, standing at far right, discusses Star Wars with his sounding board in the mid-1970s. Steve Spielberg is wearing the orange cap, and Hal Barwood sits on the fence behind him.

Working together with his good friend Matthew Robbins, Barwood wrote a science-fiction script called Star Dancing during the same period. The two commissioned a former Boeing technical illustrator and CBS animator named Ralph McQuarrie to paint some concept art, thereby to help them pitch the project to the studios. In the end, though, Star Dancing never went anywhere — until Lucas, who was toying with ideas for a second, more crowd-pleasing science-fiction movie of his own, saw McQuarrie’s paintings and was greatly inspired by them, hiring him to develop the vision further for what would become Star Wars. McQuarrie’s concept art had much to do with the eventual green-lighting of Star Wars by 20th Century Fox, and he would continue to shape the look of that film and its two sequels over the long course of their production.

Barwood and Robbins, for their part, became two of the eight people entrusted to read the first draft of the film’s script. He and the others in that San Anselmo house then proceeded to slowly shape the Star Wars script we know today over the course of draft after draft.

Even as they helped Lucas with Star Wars, Barwood and Robbins were still trying to make it as screenwriters in their own right. They sold their first script, a chase caper called The Sugarland Express, to George Lucas’s up-and-coming pal Steven Spielberg, a more recently arrived member of the San Anselmo collective; he turned it into his feature-film directorial debut in 1974. More screenwriting followed, including an uncredited rewrite of the 1977 Spielberg blockbuster Close Encounters of the Third Kind, the first film to benefit in a big way commercially from the new interest in science fiction ignited by Star Wars, which had been released about six months prior to it.

Yet the pair found screenwriting to be an inherently frustrating profession in an industry which regarded the director as a movie’s ultimate creative voice. “In writing, you’re always watching directors ruin your stuff,” says Barwood. “As a writer, you have a certain flavor, style, and emphasis in mind when you write the script, and you’re always shocked when the director comes back with something else. There’s a tendency to want to get your hands on the controls and do it yourself.” Accordingly, Matthew Robbins personally directed the duo’s 1978 comedy Corvette Summer, starring Mark Hamill — Luke Skywalker himself — in his first big post-Star Wars role. The film was a commercial success, even if the reviews weren’t great; it turned out that there was only so much you could do with Hamill, the very archetype of an actor who’s good in one role and one role only.

The duo’s next big project that was their most ambitious, time-consuming, and expensive undertaking yet. Dragonslayer was a fantasy epic based loosely on the legend of St. George and the dragon, and was once again directed by Robbins. The special effects were provided by George Lucas’s Industrial Light and Magic. In fact, Dragonslayer became the very first outside, non-Star Wars project the famous effects house took on. Being at least as challenging as anything in any of the Star Wars films, the Dragonslayer effects took them some eighteen months to complete.

Dragonslayer‘s pedigree was such that it was widely heralded in the Hollywood trade press as a “surefire success” prior to its release. But it had the misfortune to arrive in theaters on June 26, 1981, two weeks after Lucas and Spielberg’s new blockbuster collaboration, Raiders of the Lost Ark. The latter film shared with Dragonslayer the distributor Paramount Pictures. “Paramount was quite satisfied to go through the summer with the money they were going to get from Raiders of the Lost Ark,” says Barwood, “and paid no attention to our movie. They just dropped it. They just forgot about it.” Dragonslayer flopped utterly, badly damaging the duo’s reputation inside Hollywood as purveyors of marketable cinema.

Barwood got his one and only chance to direct a feature film in 1985, when he took the reins of Warning Sign, yet another screenplay by himself and Robbins. In a telling sign of the damage Dragonslayer‘s failure had done to their careers, this latest film, a fairly predictable thriller about a genetic-engineering project run amok, had a budget of about one-quarter what the duo had had to work with on their fantasy epic. It garnered mediocre reviews and box-office receipts, and no one seemed eager to entrust its first-time director with more movies. Barwood and Robbins, both frustrated by the directions their careers had taken since Corvette Summer, decided their long creative partnership had run its course.

George Lucas (far left) and some of his old compatriots at Skywalker Ranch in the mid-1980s. Matthew Robbins is third from left, Hal Barwood fourth from left.

So, Hal Barwood found himself at something of a loose end as the 1980s drew to a close. He was still friendly with George Lucas, if perhaps not quite the bosom buddy he once had been, and he still knew many of the most powerful people in the movie industry, starting with Steven Spielberg — who had gradually shown himself to be, even more so than Lucas, the personification of the new, blockbuster-oriented Hollywood, his prolific career cruising along with hit after hit. But, as Spielberg basked in his success, Barwood had parted ways with his partner and seen his directorial debut become a bust. He hadn’t had a hand in a real hit since 1978, and he hadn’t sold a script at all in quite some time. Just to rub salt into the wounds, his old compatriot Matthew Robbins managed to score another modest hit of his own at last just after the breakup, with the distinctly Spielbergian science-fiction comedy Batteries Not Included, which he directed and whose screenplay he had written with others.

Perhaps it was time for Hal Barwood to try something completely different. He had actually been mulling over his future in this cutthroat industry for some time already. During the promotional tour for Warning Sign, he had made a rather odd comment to Starlog magazine, accompanied by what his interviewer described as a “nervous laugh”: “If movies don’t pan out for me, I have a second career lurking around the corner in entertainment software, working on animated computer games, which I’m doing right now. They’re very sophisticated, animated adventure games.”

Barwood had in fact been fascinated by computers for a long time, ever since he had first encountered the hulking number-crunching monstrosities of the 1960s at university. In 1980, while hanging around the set of Dragonslayer, he had programmed his first game on a state-of-the-art HP-41C calculator as a way of passing the time between takes. Soon after, he joined the PC Revolution, buying an Apple II and starting to tinker. He worked for years on a CRPG for that machine in his spare time — worked for so long that it was still in progress when the Apple II games market began to collapse. Undaunted, he moved on to a Macintosh, where he programmed a storyboarding system for movie makers like himself in HyperCard, selling it as shareware under the name of StoryCard.

With all this experience behind him, it was natural for Barwood now to consider a future in games instead of movies — a future in an industry where the budgets were smaller, the competitors were fewer, and it was much easier to come up with an idea and actually see it through from beginning to end in something like its original form. All of this made quite a contrast to the industry where he had cut his teeth. “The movie business is very difficult for most of us,” he says. “We don’t usually get a majority of our projects to completion. Most of our dreams turn into screenplays, but they stall out at that stage.”

Given his long association with George Lucas, Barwood decided to talk to Lucasfilm Games. They were more than happy to have him, and could certainly relate to the reasons that brought him to their doorstep — for, like Barwood, they had had a somewhat complicated life of it to date in the long shadow cast by Lucas.


Before there was Lucasfilm Games, there was the Lucasfilm Computer Division, founded in 1979 to experiment with computer animation and digital effects, technologies with obvious applications for the making of special-effects-heavy films. Lucasfilm Games had been almost literally an afterthought, an outgrowth of the Computer Division that was formed in 1982, a time when George Lucas and Lucasfilm were flying high and throwing money about willy-nilly.

In those days, a hit computer game, one into which Lucasfilm Games had poured their hearts and souls, might be worth about as much to the parent company’s bottom line as a single Jawa action figure — such was the difference in scale between the computer-games industry of the early 1980s and the other markets where Lucasfilm was a player. George Lucas personally had absolutely no interest in or understanding of games, which didn’t do much for the games division’s profile inside his company. And, most frustrating of all for the young developers who came to work for The House That Star Wars Built, they weren’t allowed to make Star Wars games — nor, for that matter, even Indiana Jones games — thanks to Lucas having signed away those rights to others at the height of the Atari VCS fad. Noah Falstein, one of those young developers, would later characterize this situation as “the best thing that could have happened” to them, as it forced them to develop original fictions instead — leading, he believes, to better, more original games. At the time, however, it couldn’t help but frustrate that the only Lucasfilm properties the games division had access to were middling fare like Labyrinth.

Still, somebody inside Lucasfilm apparently believed in the low-profile division’s potential, for it survived the great bloodletting of the mid-1980s. In response to George Lucas’s expensive divorce settlement and the realization that, with the Star Wars trilogy now completed, there would be no more enormous guaranteed paydays in the future, the company’s executives, with Lucas’s tacit blessing, took an axe to many of their more uncertain or idealistic ventures at that time. Among the divisions that were sold off was the rest of the Computer Division that had indirectly spawned Lucasfilm Games; it would go on to worldwide fame and fortune under the name of Pixar. As for the games people: in 1986, they got to move into some of the vacant space all the downsizing had opened up at Skywalker Ranch, Lucasfilm’s sprawling summer camp cum corporate campus in Marin County, California.

The wall separating Lucasfilm Games from the parent company’s most desirable intellectual properties finally began to fall at the end of the 1980s, when the games people were given access to… no, not yet to Star Wars, but to the next best thing: Indiana Jones, George Lucas’s other great cinematic success story. Raiders of the Lost Ark, the first breakneck tale of the adventurous 1930s archaeologist, as conceived by Lucas and passed on to Steven Spielberg to direct, had become the highest-grossing film of 1981 by nearly a factor of two over its nearest competitor; as we’ve seen, it had trampled less fortunate rivals like poor Hal Barwood’s Dragonslayer into the dust during that year’s summer-blockbuster season. A 1984 sequel, Indiana Jones and the Temple of Doom, had done nearly as well. Now a third and presumably final film, to be called Indiana Jones and the Last Crusade, was in the offing. With the earlier licensing deals they had made for the property now expired, the parent company wanted their games division to make an adventure game out of it.

Indiana Jones and the Last Crusade: The Graphic Adventure1 was designed by Noah Falstein, David Fox, and Ron Gilbert, all of whom had worked on previous Lucasfilm adventure games, and written using the division’s established SCUMM adventuring engine. This committee approach to the game’s design is typical of the workaday nature of the project as a whole. The designers were given a copy of the movie’s shooting script, and were expected not to deviate too much from it. Ron Gilbert, a comedy writer by disposition and talent, found the need to play it relatively straight particularly frustrating, but it seems safe to say that all of the designers’ creative instincts were somewhat hemmed in by the project’s fixed rules. The end result, while competently executed, hasn’t the same vim and vinegar as Maniac Mansion, the first SCUMM adventure, nor even Zak McKracken and the Alien Mindbenders, the rather less satisfying second SCUMM game.

The boxing scene which opens the game of Indiana Jones and the Last Crusade was a part of the film’s original script which was cut in the editing room. Scenes like these make the game almost of more interest to film historians than game historians, serving as a window into the movie as it was conceived by its screenwriter Jeffrey Boam.

Perhaps the most interesting aspect of the game arises from the fact that its designers were adapting from the shooting script rather than the finished movie, which they got to see in the Skywalker Ranch theater only when their own project was in the final stages of bug-swatting and polishing. They actually implemented parts of Jeffrey Boam’s script for the movie far more faithfully than Steven Spielberg wound up doing, including numerous scenes — like the boxing sequence at the very beginning of the game — that wound up being cut from the movie. Nevertheless, the game suffers from the fundamental problem of all such overly faithful adaptations from other media: if you’ve seen the movie — and it seemed safe to assume that just about everybody who played the game had seen the movie — what’s the point in walking through the same story again in game form? The designers went to considerable lengths to accommodate curious (or cantankerous) players who make different choices from those of Indiana Jones in the movie, turning their choices into viable alternative pathways rather than mere game overs. But there was only so much they could do in even that respect, given the constraints under which they labored.

Of course, licensed games exist first and foremost because licenses sell games, not because they lead to better ones. Indiana Jones and the Last Crusade became the cinematic blockbuster of the year upon its release in May of 1989, and the game also did extremely well when it hit stores a few weeks later. Having taken this first step into the territory of Lucasfilm’s biggest franchises and been so amply rewarded for it, the people at the games division naturally wanted to keep the good times going. There were likely to be no more Indiana Jones movies; Harrison Ford, the series’s famously prickly star, was publicly declaring himself to be through with playing the character. But did that necessarily mean that there couldn’t be more Indiana Jones games? With the license now free and clear for their use, no one at Lucasfilm Games saw any reason to assume so.


It was at this juncture that Hal Barwood entered the picture, interested in trying a new career in games on for size. Just about any developer in the industry would have jumped at the chance to bring someone like him aboard. Talk of a merger of games with cinema to create a whole new genre of mass-media entertainment — the interactive movie, preferably published on CD-ROM complete with voice acting and perhaps even real-world video footage — dominated games-industry conferences and magazine editorials alike as the 1990s began. But for all their grandiose talk, the game developers clustered in Northern California were all too aware that they lacked the artistic respectability necessary to tempt most of those working with traditional film and video in the southern part of the state into working with them on interactive projects. Hal Barwood might have been no more than a mid-tier Hollywood player at best, but suffice to say that there wasn’t exactly a surfeit of other Hollywood veterans of any stripe who were willing to work on games.

In an online CompuServe conference involving many prominent adventure-game designers that was held on August 24, 1990, not long after Barwood’s arrival at Lucasfilm Games, Noah Falstein could hardly keep himself from openly taunting his competitors about what he had and they didn’t:

One way we’re trying to incorporate real stories into games is to use real storytellers. Next year, we have a game coming out by Hal Barwood, who’s been a successful screenwriter, director, and producer for years. His most well-known movies probably are the un-credited work he did on Close Encounters and Dragonslayer, which he co-wrote and produced. He’s also programmed his own Apple II games in 6502 assembly in his spare time. I’ve already learned a great deal about pacing, tension, character, and other “basic” techniques that come naturally — or seem to — to him. I highly recommend such collaborations to you all. I think we’ve got a game with a new level of story on the way.

Falstein was in a position to learn so much from Barwood because he had been assigned to work with him as his design partner on his first project — the idea being that Barwood would take care of all the “basic” cinematic techniques Falstein enthuses about above, while Falstein would keep the project on track and make sure it worked as a playable adventure game, with soluble puzzles and all the rest.

Ironically given what Raiders of the Lost Ark had done to Dragonslayer, Hal Barwood’s one big chance to become a truly major Hollywood player, the game in question was to be another Indiana Jones game — albeit one with an original story, not bound to any movie. The initial plan had been to sift through the pile of rejected scripts for the third Indiana Jones film and select a likely candidate from them for adaptation into a game. But it turned out that the scripts were all pretty bad, or at least not terribly suitable for interactive adaptation.

The Azores is one of the many exotic locations Indy visits in Indiana Jones and the Fate of Atlantis, all of which are brought to life with aplomb by Lucasfilm Games’s accomplished art team.

So, Barwood and Falstein decided to invent their own story, and thus went looking for legends of lost civilizations that might be worthy of an intrepid archeologist who had already found the Lost Ark of the Covenant and the Holy Grail. “George [Lucas] has established a criterion for Indiana Jones adventures,” said Barwood, “and it’s basically that he should only find things that actually existed — or at least could have existed.” The fabled sunken island of Atlantis seemed the right mixture of myth and history. Barwood:

Our eyes fell upon Atlantis because not only is it an ancient myth known by almost everyone, but it also has wonderful credentials, in that it was first mentioned by Plato a couple thousand years ago. In addition to that, in the early part of this century, the idea was taken over by spiritualists and mystics, who attributed to the Atlanteans this fantastic technology, with airships flying 100 milers per hour, powered by vrill and firestone. When we found this out, we thought to ourselves, “Does this sound as interesting as the Holy Grail? Yes, it does.” Even though it’s a myth, the myth is grounded in a wonderful collection of lore.

The legend’s wide-ranging wellsprings would allow them to send Indy traipsing between exotic locations scattered over much of the world: New York City, Iceland, Guatemala, the Azores, Algiers, Monte Carlo, Crete, Santorini, finally ending up under the ocean at the site of Atlantis itself.

The game known as Indiana Jones and the Fate of Atlantis hits all the notes familiar to anyone who has seen an Indiana Jones film. It seems that the mythical Atlanteans were quite a clever lot, having harnessed energies inconceivable to modern scientists. The Nazis have gotten wind of this, and are fast piecing together the clues that will let them find the undersea site of Atlantis, enter it, and take the technology for themselves, thereby to conquer the world. It’s a fine premise for a globetrotting story of thrills and spills — silly but no more silly than any of those that got made into movies. There’s even a female sparring partner/love interest for Indy, just like in the films. This time her name is Sophia, and she’s a former archaeologist who’s become a professional psychic, much to the scientific-minded Indy’s dismay. Let the battle of barbs begin!

Barwood’s first interactive script really is a good one, with deftly drawn plot beats and characters that, if not exactly deep, nobly fulfill their genre-story purposes as engines of action, tension, or comic relief. Other game writers of the early 1990s weren’t always or even usually all that adept at such basic techniques of fiction as “pacing, tension, and character.” To see how painful a game can be that wants to be like the Indiana Jones movies but lacks the writers to pull it off, one need look no further than Dynamix’s Heart of China, with its humor that lands with the most leaden of thuds, its hero who wants to be a charming rogue but misplaced his charm, and its dull supporting characters who are little more than crude ethnic stereotypes. When you play Fate of Atlantis, by contrast, you feel yourself to be in the hands of a writer who knows exactly what he’s doing.

The game is full of callbacks to the movies’ most famous catchphrases.

That said, the degree to which Indiana Jones and the Fate of Atlantis is truly cinematic can be and too often is overstated. Games are not movies — an obvious point that game developers of the early 1990s frequently lost sight of in their rush to make their interactive movies. Hal Barwood, the Hollywood veteran brought into Lucasfilm Games to apply his cinematic expertise, was ironically far more aware of this fact than were many other game designers who lacked his experience in the medium they were all so eager to ape. Speaking to the science-fiction writer and frequent games-industry commentator Orson Scott Card in 1990, Barwood made some telling observations:

“The companies making animated games keep talking as if games resembled movies,” he [Barwood] said. “But they don’t resemble movies all that much.”

He granted some resemblances, of course, especially with animated film. The dependence on artists; the trickle rate of production, where you’re producing the game or film at the rate of only minutes, or even seconds, of usable footage a day; and the dominant role of the editing process.

Still, though, when it comes to the art of composing a game, inventing it, he said, “What it really resembles is theater. Plays.”

Why? Because as with a play, you have only a few settings you can work with, and they can usually be viewed from only a single angle and at the same distance. You can’t do any meaningful work with closeups (to design and program genuine realistic facial expressions just isn’t worth the huge investment in time and disk space). It’s so hard to make actions clear that you must either rely on dialogue, like most plays, or show only the simplest, most obvious actions.

In movies, it’s just the opposite. You control the pace and rhythm of film by cutting and shifting the action from place to place. The camera never gazes at any one thing for long.

The computer games of this era which most clearly did understand the kinetic language of cinema — the language of a roving camera and a keen-eyed editor — weren’t any of the avowed interactive movies that were being presented in the form of plot- and dialog-heavy adventure games, but rather the comparatively minimalist action games Prince of Persia and Another World, both essentially one-man productions that employed few to no words. Both of these games were aesthetically masterful, but somewhat more problematic in terms of providing their players with interesting forms of interactivity, thus inadvertently illustrating some of the drawbacks of fetishizing movies as the ideal aesthetic model for games.

All the other people who thought they were making interactive movies were “filming” their productions the way only the very earliest movie directors had filmed, before a proper language of film had been created: through a single static “camera.” The end results were anything but cinematic in the way a fellow like Hal Barwood, steeped throughout his life in the language of film, understood that term. His long experience in film-making allowed him to see the essential fact that games were not movies. They might borrow the occasional technique from cinema, but games were a medium — or, perhaps better stated, a matrix of mediums, only one of which was the point-and-click adventure game — with their own unique sets of aesthetic affordances. Countless game developers seemed to be using the term “interactive movie” to designate any game that had a lot of story, but the qualities of being cinematic and being narrative-oriented were really orthogonal to one another.

As in the first Indiana Jones movie, a Nazi submarine features prominently in Fate of Atlantis.

In later years, Hal Barwood would describe a narrative-driven game as more akin to a vintage Russian novel than a movie, a “continuous experience in a fictional world”: something the player lives with over a period of days or weeks, working through it at her own pace, mulling it over even when she isn’t actively sitting in front of the computer. The control or lack thereof of pacing is a critical distinction: a game which leaves any reasonable scope of agency to its player must necessarily cede much or all of the control of pacing to her. And yet pacing is absolutely key to the final effect of any movie, so much so that the director may very well spend months in the editing room after all the shooting is done, trying to get the pacing just right. The game designer doesn’t have anything like the same measure of direct control over the player’s experience, and so must deliver a very different sort of fiction.

Indiana Jones and the Fate of Atlantis works because it understands these differences in media. It plays with the settings, characters, and themes of the Indiana Jones movies to fine effect, but never forgets that it’s an adventure game. The driving mechanic of an adventure game — the solving of intellectual puzzles — is quite distinct from that which drives the movies, and the plot points must be adapted to match. Can you imagine the cinematic Indy sticking wads of chewing gum to the soles of his shoes so as to climb up a coal chute? Or using a bathroom plunger as a handy replacement for a missing control lever inside a Nazi submarine? Puzzles of this nature inevitably make Indy himself into a rather different sort of personality — one a little less cool and collected, a little more prone to be the butt of the joke rather than the source of it. It’s clear from the very opening scenes of Fate of Atlantis, an innovative interactive credits sequence in which poor Indy must endure pratfall after pratfall, that this isn’t quite the same character we thrilled to in the movies. Harrison Ford would have walked out if asked to play a series of scenes like these.

This phenomenon, which we might called the Guybrush Threepwoodization of the hero, is very common in adventure games adapted from other media, given that the point-and-click adventure game as a medium wants always to collapse back into comedy as its default setting. (See, for example, the Neuromancer game, which similarly turns the cool cat Case from its source novel into a put-upon loser, and winds up becoming a pretty great game in the process.) Barwood and Falstein as well decided that Indiana Jones must adapt to the adventure-game genre rather than the adventure-game genre adapting to Indiana Jones. This was most definitely the right approach to take, and is the overarching reason why this game succeeds when so many other interactive adaptations fail.

The one place where the otherwise traditionalist Fate of Atlantis clearly does try to do something new has nothing directly to do with its source material. It rather takes the form of three possible narrative through lines, depending on the player’s individual predilections. After playing through the introductory stages of the game, you’re given a choice between a “Team” path, where Indy and Sophia travel together and cooperate to solve problems; a “Wits” path, where Indy travels largely alone and solves problems using his noggin; and a “Fists” path, where Indy travels alone and solves some though by no means all of his problems using more, shall we say, active measures, which translate into little action-oriented minigames for the player. The last is seemingly the closest to the spirit of the films, but is, tellingly, almost universally agreed to be the least interesting way to play the game.

The Team path, like all of them, has its advantages and disadvantages. It’s great to have Sophia around to help out with things — until she falls down a pit and needs your help getting out.

Although the message would get a little muddled once the game reached stores — “three games in one!” was a tagline few marketers could resist — Barwood and Falstein’s primary motivation in making these separate paths wasn’t to create a more replayable game, but rather a more accessible one. Lucasfilm Games always placed great emphasis on giving their players a positive, non-frustrating experience. Different players would prefer to play in different ways, Barwood and Falstein reasoned, and their game should adapt to that. “Socially-oriented” players — possibly including the female players they were always hoping to reach — would enjoy the Team path with its constant banter and pronounced romantic tension between Indy and Sophia; the stereotypically hardcore, cerebral adventure gamers would enjoy the Wits path; those who just wanted to get through the story and check out all the exotic destinations could go for the Fists path.

Falstein liked to call Fate of Atlantis a “self-tuning game.” In this spirit, until very late in development the branching pathways were presented not as an explicit choice but rather as a more subtle in-game personality test. Early on, Indy needs to get into a theater even though he doesn’t have a ticket. There are three ways to accomplish this: talking his way past the guard at the door; puzzling his way through a maze of boxes to find a hidden fire-escape ladder; or simply sucker-punching the guard. Thus would the player’s predilections be determined. In the interest of transparency and as a sop to replayability, however, the personality test wound up being replaced by a simple menu for choosing your pathway.

The first substantial interactive scene in the game, taking place outside and inside a theater in New York City where Indy’s adventuring partner-to-be Sophia is giving a lecture, was intended to function as a personality test of sorts, determining whether the player was sent down the Team, Wits, or Fists path. In the end, though, its finding were softened to a mere recommendation preceding an explicit choice of paths which is offered to the player at its conclusion.

The idea of multiple pathways turned out not to be as compelling in practice as in theory. Most players did take it more as an invitation to play the game three times than an opportunity to play it once their way, and were disappointed to discover that the branching pathways encompass only about 60 percent of the game as a whole; the first 10 percent or so, as well as the lengthy climax, are the same no matter which pathway you choose. Nor are the Team and Wits pathways different enough from one another to give the game all that much of a different flavor; they both ultimately come down to solving a series of logic puzzles. The designers’ time would probably have been better spent making one pathway through the game that combined elements of the Team and Wits pathways. Lucasfilm Games never tried anything similar again. The branching pathways were an experiment, and in that sense at least they served their purpose.

A substantial but by no means enormous game, Indiana Jones and the Fate of Atlantis nevertheless spent some two years in development, a lengthy span of time indeed by the standards of the early 1990s, being at least three times as long as it had taken to make the Last Crusade game. The protracted development cycle wasn’t a symptom of acrimony, lack of focus, or disorganization, as such things so often tend to be. It was rather a byproduct of the three pathways and, most of all, of Lucasfilm Games’s steadfast commitment to getting everything right, prioritizing quality and polish over release dates in that way that always set them apart from the majority of their peers.

Shortly before the belated release of Fate of Atlantis in the summer of 1992, Lucasfilm Games became LucasArts. The slicker, less subservient appellation was a sign of their rising status within the hierarchy of their parent company, as their games sold in bigger quantities and became a substantial revenue stream in their own right, less and less dwarfed by the money that could be made in movies. Those changing circumstances would prove a not-unmixed blessing for them, forcing them to move out of the rustic environs of Skywalker Ranch and shed much of the personality of a quirky artists’ collective for that of a more hard-nosed media enterprise. On the other hand, at least they’d finally get to make Star Wars games…

But that’s an article for another day. I should conclude this one by noting that Indiana Jones and the Fate of Atlantis2 was greeted with superlative reviews and equally strong sales; even Steven Spielberg, who unlike his friend George Lucas was a big fan of games, played through it and reportedly enjoyed it very much. A year after the original floppy-disk-based release, LucasArts made a “talkie” version for CD-ROM. Getting Harrison Ford to play Indiana Jones was, as you might imagine, out of the question, but they found a credible soundalike, and handled the voice acting as a whole with their usual commitment to quality, recruiting professional voice talent in Hollywood and recording them in the state-of-the-art facilities of Skywalker Sound.

While hard sales numbers for LucasArts’s adventure games have never surfaced to my knowledge, Noah Falstein claims that Indiana Jones and the Fate of Atlantis sold the most of all of them — a claim I can easily imagine to be correct, given its rapturous critical reception and the intrinsic appeal of its license. Today, it tends to be placed just half a step down from the most-loved of the LucasArts adventures, lacking perhaps some of the manic inspiration of the studio’s completely original creations. Nonetheless, it’s a fine, fine game, well worth playing through twice or thrice — at least its middle section, where the pathways diverge — to experience all it has to offer. This game adapted from a movie franchise, which succeeds by not trying to be a movie, marked a fine start for Hal Barwood’s new career.

(Sources: the books The Secret History of Star Wars by Michael Kaminski and Droidmaker: George Lucas and the Digital Revolution by Michael Rubin; LucasArts’s Adventurer magazine of Fall 1991, Spring 1992, and Spring 1993; Starlog of July 1981, September 1981, August 1982, May 1985, September 1985, November 1985, December 1985, and February 1988; Amiga Format of February 1992; Compute! of February 1991; Computer Gaming World of September 1992; CU Amiga of June 1992; Electronic Games of October 1992; MacWorld of June 1989; Next Generation of October 1998; PC Review of September 1992; PC Zone of January 2000; Questbusters of September 1992; Zero of August 1991 and March 1992. Online sources include Arcade Attack‘s interviews with Noah Falstein and Hal Barwood; Noah Falstein’s Reddit AMA; MCV‘s articles on “The Early Days of LucasArts”; Noah Falstein’s presentation on LucasArts at Øredev 2017.

Indiana Jones and the Fate of Atlantis is available for purchase on GOG.com.)


  1. An Action Game was also published under the auspices of Lucasfilm Games, but its development was outsourced to a British house. 

  2. Once again, there was also a Fate of Atlantis action game, made in Britain with a particular eye to the 8-bit machines in Europe which couldn’t run the adventure game. And once again, it garnered little attention in comparison to its big brother. 

 
30 Comments

Posted by on September 28, 2018 in Digital Antiquaria, Interactive Fiction

 

Tags: , , , ,

Adventure-Game Rock Stars Live in Conference

On August 24, 1990, CompuServe hosted an online discussion on adventure-game design which included Ron Gilbert, Noah Falstein, Bob Bates, Steve Meretzky, Mike Berlyn, Dave Lebling, Roberta Williams, Al Lowe, Corey and Lori Ann Cole, and Guruka Singh Khalsa. This is, needless to say, an incredible gathering of adventuring star power. In fact, I’m not sure that I’ve ever heard of its like in any other (virtual) place. Bob Bates, who has become a great friend of this blog in many ways, found the conference transcript buried away on some remote corner of his hard drive, and was kind enough to share it with me so that I could share it with you today.

If you’re a regular reader of this blog, you probably recognize all of the names I’ve just listed, with the likely exception only of Khalsa. But, just to anchor this thing in time a bit better, let me take a moment to describe where each of them was and what he or she was working on that August.

Ron Gilbert and Noah Falstein were at Lucasfilm Games (which was soon to be renamed LucasArts). Gilbert had already created the classic Maniac Mansion a few years before, and was about to see published his most beloved creation of all, one that would have as great an impact among his fellow designers as it would among gamers in general: The Secret of Monkey Island. Falstein had created Indiana Jones and the Last Crusade for Lucasfilm in 1989. Their publisher had also recently released Brian Moriarty’s Loom, whose radically simplified interface, short length, and relatively easy puzzles were prompting much contemporaneous debate.

Bob Bates, Steve Meretzky, Mike Berlyn, and Dave Lebling had all written multiple games for the now-defunct Infocom during the previous decade. Bates had recently co-founded Legend Entertainment, where he was working on his own game Timequest and preparing to publish Spellcasting 101: Sorcerers Get All the Girls, Meretzky’s first post-Infocom game and Legend’s first game ever, in a matter of weeks. Berlyn had been kicking around the industry since leaving Infocom in 1985, creating perhaps most notably Tass Times in Tonetown for Interplay; he was just finishing up a science-fiction epic called Altered Destiny for Accolade, and would shortly thereafter embark on the Les Manley games, a pair of Leisure Suit Larry clones, for the same publisher. Lebling was at something of a loose end after the shuttering of Infocom the previous year, unsure whether he even wanted to remain in the games industry; he would eventually decide that the answer to that question was no, and would never design another game.

Roberta Williams, Al Lowe, Corey and Lori Ann Cole, and Guruka Singh Khalsa were all working at Sierra. Williams was in the latter stages of making her latest King’s Quest, the first to use 256-color VGA graphics and a point-and-click interface, and the first to be earmarked for CD-ROM as a “talkie.” Al Lowe was, as usual, hard at work on the latest Leisure Suit Larry game, which also utilized Sierra’s newer, prettier, parser-less engine. The Coles were just finishing up Quest for Glory II: Trial by Fire, which would become the last Sierra game in 16-color EGA and the last with a parser.

Khalsa is the only non-designer here, and, as already noted, the only name here with which longtime readers are unlikely to be familiar. He was another of those unsung heroes to be found behind the scenes at so many developers. At Sierra, he played a role that can perhaps best be compared to that played by the similarly indispensable Jon Palace at Infocom. As the “producer” of Sierra’s adventure games, he made sure the designers had the support they needed, acted as a buffer between them and the more business-oriented people, and gently pushed his charges to make their games just a little bit better in various ways. In keeping with his unsung status, he answers only one question here.

We find all of our participants grappling with the many tensions that marked their field in 1990: the urgent need to attract new players in the face of escalating development budgets; the looming presence of CD-ROM and other disruptive new technologies just over the horizon; the fate of text in this emerging multimedia age; the frustration of not always being able to do truly innovative or meaningful work, thanks to a buying public that largely just seemed to want more of the same old fantasy and comedy. It’s intriguing to see how the individual designers respond to these issues here, just as it is to see how those responses took concrete form in the games themselves. By no means is the group of one mind; there’s a spirited back-and-forth on many questions.

I’ve cleaned up the transcript that follows for readability’s sake, editing out heaps of extraneous comments, correcting spelling and grammar, and rejiggering the flow a bit to make everything more coherent. I’ve also added a few footnotes to clarify things or to insert quick comments of my own. Mostly, though, I’ve managed resist the urge to pontificate on any of what’s said here. You all already know my opinions on many of the topics that are raised. Today, I’m going to let the designers speak for themselves. I hope you’ll find their discussion as interesting and enjoyable as I do.


 

Let’s plunge right into the questions. Before I start, I’d like to thank Eeyore, Flying Gerbil, Steve Horton, Tsunami, Hercules, Mr. Adventure, and Randy Snow for submitting questions… and I apologize for mangling their questions with my editing. And now — drum roll! — on to the first question!

Imagine ourselves five years down the road, with all the technological developments that implies: CD-ROMs, faster machines, etc. Describe what, for you, the “ideal” adventure will look like. How will it be different from current adventures?

Roberta Williams: I think that “five years down the road” is actually just a year or two away. Meaning that a year or two from now, adventure games are going to have a very slick, sophisticated, professional look, feel, and sound to them, and that that’s the way they’re going to stay for a while — standardization, if you will. I mean, how can you improve on realistic images that look like paintings or photographs? How can you improve on CD-quality voices and music? How can you improve on real movement caught with a movie camera, or drawn by a professional animator? That’s the kind of adventure game that the public is going to start seeing within a year or two. Once adventure games reach a certain level of sophistication in look and feel, standardization will set in, which will actually be a boon for all concerned, both buyers and developers alike. After that, the improvements will primarily be in the performance on a particular machine, but the look will stay essentially the same for a while.

Dave Lebling: But if those wonderful pictures and hi-fi sound are driven by a clunky parser or a mythical “parser-less interface,” is this a big improvement? I think not. We can spend $2 million or $5 million developing a prettier version of Colossal Cave. Let’s improve the story and the interface! That doesn’t have to mean text adventures, but there’s more to adventure games than pictures.

Steve Meretzky: I think that in the future the scope of games won’t be limited by hardware but by the marketplace. Unless the market for adventure games expands, it won’t be economical to create super-large environments, even though the hardware is there to support them.

Mike Berlyn: Well, I think that technology can create products which drive the market and create end users — people who need or want to experience something they could experience only on a computer. In the future, I would like to explore “plot” as a structure, something which is currently impossible due to the state of the current technology. Plot cannot be a variable until storage increases and engines get smarter. I can easily see a plot that becomes a network of possibilities.

Corey and Lori Ann Cole: We hope as well that the improvements will be in story and design as well as flash: richer stories, more realistic character interaction, etc. Technology, beyond a certain point which we’ve already reached, really isn’t a big deal. Creativity, and an understanding of the differences between “interactive movies” and games is! The move to professional writers and game designers in the industry is helping.

Ron Gilbert: I think that plot has nothing to do with technology. They are almost unrelated. It’s not CD-ROM or VGA that is going to make the difference, it’s learning how to tell a story. Anyone who is any good can tell a great story in 160 X 200-resolution, 4-color graphics on two disks.

Roberta Williams: It’s not that I don’t think a good plot is important! Obviously it is.

Dave Lebling: I didn’t mean to accuse you of not caring about plot. You of all people know about that! I just think the emphasis on flash is a symptom of the fact that we know how to do flash. Just give us a bigger machine or CD-ROM, and, wham, flash! What we don’t know how to do is plot. I don’t think today’s plots feel more “real” than those of five or eight years ago. Will they be better in five years? I hope so, but I’m not sure. We can’t just blindly duplicate other media without concentrating on the interactivity and control that make ours special. If we work on improving control and the illusion that what we interact with is as rich as reality, then we can do something that none of those other media can touch.

Corey and Lori Ann Cole: We have never really used the computer as a medium in own right.

Steve Meretzky: You haven’t used it to contact the spirit world?1

Corey and Lorin Ann Cole: There are things that can be done on a computer that can’t be done with other mediums. Unfortunately, the trend seems to be away from the computer and towards scanned images and traditional film and animation techniques.2 If this trend continues, it may be a long time before we truly discover what can be done uniquely with the computer medium. One small example: the much-chastised saved game is a wonderful time- and mind-travel technique that can be a rich tool instead of an unfortunate necessity.

Bob Bates: I agree. You can’t ask a painter at the Art Institute of Chicago to paint you a different scene. You can’t ask a singer at the Met to sing you a different song. (Well, I guess you could, but they frown on requests.) The essence of a computer game is that the player controls the action. The point is to make beautiful music and art that helps the player’s sense of involvement in the game.

I have noticed that a lot of games coming out now are in 256 colors. Does this mean that 256-color VGA is going to be the standard? Has anyone thought about 256 colors in 640 X 480 yet? And how does anyone know who has what?

Bob Bates: The market research on who has what is abominable. As for us, we are releasing our titles with hi-res EGA, which gives us really good graphics on a relatively popular standard, as well as very nice text letters instead of the big clunky ones.

Steve Meretzky: I often get big clunky letters from my Aunt Matilda.

Guruka Singh Khalsa: We’ve been doing a bit of research on who has what hardware, and an amazing number of Sierra customers have VGA cards. Looks like around 60 percent right now. As for 640 X 480 in 256 colors: there’s no hardware standard for that resolution since it’s not an official VGA mode. You won’t see games in that resolution until the engines are more powerful — got to shove them pixels around! — and until it’s an official mode. All SVGA cards use somewhat different calls.

Dave Lebling: The emerging commercial standard is a 386 with VGA and 2 to 4 megs of memory, with a 40-meg hard drive. The home standard tends to lag the commercial one by a few years. But expect this soon, with Windows as the interface.

Does anyone have any plans to develop strictly for or take advantage of the Windows environment?

Dave Lebling: Windows is on the leading edge of the commercial-adoption wave. The newest Windows is the first one that’s really usable to write serious software. There are about 1 million copies of Windows out there. No one is going to put big bucks into it yet. But in a few years, yes, because porting will be easier, and there is a GUI already built, virtual memory, etc., etc. But not now.

With the coming parser-less interfaces and digitized sound, it seems as if text may eventually disappear completely from adventures. Once, of course, adventures were all text. What was gained and what was lost by this shift? Are adventures still a more “literate” form of computer game?

Bob Bates: Well, of course text has become a dirty word of sorts in the business. But I think the problem has always been the barrier the keyboard presents as an input device for those who can’t type. Plus the problems an inadequate or uncaring game designer can create for the player when he doesn’t consider alternate inputs as solutions to puzzles. I think there will always be words coming across the screen from the game. We hope we have solved this with our new interface, but it’s hard for people to judge that since our first game won’t be out for another month…

Corey and Lori Ann Cole: Text will not disappear. Nor should it. We will see text games, parser-less games, and non-text games. And who cares about being “literate”; fun is what matters! I like words. Lori likes words. But words are no longer enough if one also likes to eat — and we do. We also like graphics and music and those other fun things too, so it’s not too big a loss.

Roberta Williams: It’s true that in books stories can be more developed, involving, and interesting than in movies. I believe that there is still room for interactive books. Hopefully there is a company out there who will forget about all the “video” stuff and just concentrate on good interactive stories in text, and, as such, will have more developed stories than the graphic adventure games. But as we progress adventure games in general are going to become more like interactive movies. The movie industry is a larger and more lucrative business than the book industry. For the most part, the adventure-game business will go along with that trend. Currently adventure games are the most literate of computer games, but that may change as more and more text will be lost in the coming years, to be replaced by speech, sound effects, and animation. But I do predict that some company out there will see a huge opportunity in bringing back well-written, high-quality interactive books. It will be for a smaller audience, but still well worth the effort.

Dave Lebling: I think you’re too  optimistic about “some company” putting out text products. We are moving from interactive books to interactive movies. I’m not optimistic about the commercial survival of text except in very small doses.3 Unlike in science fiction, you don’t have to follow a trend until it goes asymptotic. Text won’t go away, but its role will be reduced in commercial adventures. Graphics and sound are here to stay.

Al Lowe: With the coming of talkies, it seems as if all those wonderful dialog cards disappeared! You know, the ones that make silent movies so literate? It’s a visual medium! No one asks for silent movies; most Americans won’t even watch a black-and-white movie. Yes, text-only games are more “literate.” So?

Mike Berlyn: As far as the future of text is concerned, my money is on it sticking around. But I’m not sure it’s at all necessary in these kinds of games. The adventure I’m just finishing up has a little bit of text that reiterates what is obvious on the screen, and manages to add to the player’s inputs in other ways to a create fuller experience. But I still don’t think it’s necessary. I’ve done two completely text-less designs, though neither made it to the market.

Bob Bates: I don’t think it’s the loss of text as output that creates a problem for the designer; I think it’s text as input. It’s hard to design tough puzzles that can be solved just by pointing and clicking at things. And if there are no puzzles — tough puzzles — you’re just watching a movie on a very small screen. The days of the text-only adventure are over. Graphics are here to stay, and that’s not a bad thing, as long as they supplement the story instead of trying to replace it.

We’ve seen fantasy adventures, science-fiction adventures, mystery adventures, humorous adventures. Are there any new settings or themes for adventures? Is there any subject or theme that you’ve always wanted to put in an adventure but never had the chance?

Al Lowe: I’ve had ideas for a Wall Street setting for a game, but somehow I can’t get out of this Larry rut. I’d also like to do a very serious game — something without one cheap laugh, just to see if I could. Probably couldn’t, though. A serious romance would be good too.

Roberta Williams: There should be as many settings or themes for adventure games as there are for fictionalized books and movies. After all, an adventure game is really just an interactive story with puzzles and exploration woven into it. There are many themes that I personally would like to do, and hopefully will someday: an historical or series of historical adventure games; a horror game; an archaeological game of some sort; possibly a western. In between King’s Quests, of course.

Noah Falstein: I’ve always wanted to do a time-travel game with the following features: no manual save or load, it’s built automatically into the story line as a function of your time-travel device; the opportunity to play through a sequence with yourself in a later — and then earlier — time; and the ability to go back and change your changes, ad infinitum. Of course, the reason I’m mentioning all this is that I — and others here — have fried our brains trying to figure out how this could be accomplished. We’d rather see someone else do it right. Or die trying.

Ad infinitum? Won’t that take a lot of memory?

Noah Falstein: Recursion!

Dave Lebling: Gosh, my fantasy is your fantasy! I’ve always wanted to do a game based on Fritz Leiber’s Change War stories — you know, “tomorrow we go back and nuke ancient Rome!” Funny thing is, I’ve always run up against the same problem you ran up against.

Mike Berlyn: My fantasy is to finish a game that my wife Muffy and I were working on for the — sniff! — dead Infocom. It was a reality-based game that had a main character going through multiple/parallel lives, meeting people he’d met before but who were different this time through. In that way, the relationships would be different, the plot would be different, and their lives would interact differently.

Steve Meretzky: In my fantasy, I answer the door and Goldie Hawn is standing there wearing… oh, we’re talking adventure games now, aren’t we? A lot of the genres I was going to mention have already been mentioned. But one is historical interactive nonfiction. I know that Stu Galley has always wanted to do a game in which you play Paul Revere in April of 1775. And before I die I’m going to do a Titanic game.4 Also, in my ongoing effort to offend every man, woman, and child in the universe, someday I’d like to write an Interactive Bible, which would be an irreverent comedy, of course. Also, I’d like to see a collection of “short story” adventure games for all those ideas which aren’t big enough to be a whole game.5

Bible Quest: So You Want to Be a God?. I like it, I like it.

Corey and Lori Ann Cole: Ah, but someone will sue over the trademark…6

Bob Bates: The problem of course is marketing. The kinds of games we want to write aren’t always the kinds of games that will sell. This presents something of a quandary for those of us who like to eat.

This question was submitted by Tsunami, and I’ll let him ask in his own words: “Virtually every game I have played on my computer is at least partially tongue-in-cheek. What I am interested in is games with mature themes, or at least a more mature approach to their subjects. Games that, like good movies or plays, really scare a player, really make them feel a tragedy, or even make them angry. What are each of you doing to try to push games to this next level of human interaction?”

Steve Meretzky: Well, I think I already did that with A Mind Forever Voyaging, and it did worse commercially speaking than any other game I’ve ever done. As Bob just said, we have to eat. I’d much rather write a Mind Forever Voyaging than a Leather Goddesses of Phobos, but unless I become independently wealthy, or unless some rich benefactor wants to underwrite such projects, or unless the marketplace changes a lot, I don’t think I’ll be doing a game like A Mind Forever Voyaging in the near future. Sigh.

Corey and Lori Ann Cole: Computers are so stupid that even the smartest game tends to do silly things. So, it’s easier to write a silly game. And the development process on a humorous game tends to be more fun. Quest for Glory II: Trial By Fire is fundamentally a very serious game in terms of story line, but we kept lots of silly stuff in to break up the tension. I call it the “roller-coaster effect.” We want the player to get extremely intense about the game at points, but then have a chance to catch his or her breath with comic relief and plain fun.

Bob Bates: My games are usually fairly “mature,” but when 90 percent of what a player tries to do in a game is wrong, you have to keep him interested when he is not solving a puzzle. The easiest way to do this is with humor; you don’t want him mad at you, after all. But I agree that we all should strive to create emotions in the player like what we all felt when Floyd died in Planetfall.

Roberta Williams: I agree with the sentiment that most adventure games, at least up to now, have been not quite “serious” in their approach to the subject matter at hand. I think the reason for that, for the most part, is that professional writers or storytellers have not had their hands in the design of a game. It’s been mostly programmers who have been behind them. I’m not a professional writer either, but I’m trying to improve myself in that area. With The Colonel’s Bequest, I did attempt a new theme, a murder mystery, and tried to make it more mature in its subject matter — more “plot” oriented. I attempted to put in classic “scare” tactics and suspense. I tried to put in different levels of emotion, from repulsion to sadness to hilarity. Whether I accomplished those goals is up to the player experiencing the game. At least I tried!

Noah Falstein: I venture to predict that we all intend to push games this way, or want to but can’t afford it — or can’t convince a publisher to afford it. But I’ll toot the Lucasfilm horn a bit; imagine the Star Wars fanfare here. One way we’re trying to incorporate real stories into games is to use real storytellers. Next year, we have a game coming out by Hal Barwood, who’s been a successful screenwriter, director, and producer for years. His most well-known movies probably are the un-credited work he did on Close Encounters and Dragonslayer, which he co-wrote and produced. He’s also programmed his own Apple II games in 6502 assembly in his spare time. I’ve already learned a great deal about pacing, tension, character, and other “basic” techniques that come naturally — or seem to — to him. I highly recommend such collaborations to you all. I think we’ve got a game with a new level of story on the way.7

Mike Berlyn: I disagree with the idea that hiring professional storytellers from other media will solve our problems for us. Creating emotions is the goal here, if I understood the question. It isn’t whether we write humor or horror, it’s how well we do it. This poses a serious problem. Interactivity is the opposite of the thing that most… well, all storytellers, regardless of medium, require to create emotion. Emotion is created by manipulation. And it is impossible to manipulate emotions when you don’t know where the player has been and you don’t know where the player is going. In linear fiction, where you know what the “player” has just experienced; you can deliberately and continuously set them up. This is the essence of drama, humor, horror, etc. Doing this in games requires a whole different approach. Utilizing an experienced linear writer only tends to make games less game-ish, less interactive, and more linear. In a linear game like Loom, you’re not providing an interactive story or an adventure game. All you’re doing is making the player work to see a movie.

Dave Lebling: Well, emotion also comes from identification with the character in the story. You can’t easily identify in a serious way with a character who looks like a 16 X 16-pixel sprite.8 If he or she is silly-looking, he or she isn’t much more silly-looking than if he’s serious-looking: for example, Larry Laffer versus Indy in Indiana Jones and the Last Crusade. So, you are at a disadvantage being serious in graphical games. Better graphics will improve that eventually. But even so, I think Bob hit the point perfectly: the player does a lot of silly things, even if there is no parser — running into rocks in the graphic games, for example — and you can’t stay serious. The other thing is that, in my experience, serious games don’t sell. Infocom’s more serious games sold poorly. Few others have tried, and most of those have sold poorly too.

Corey and Lori Ann Cole: A really good game — or story — elicits emotions rather than creating them. A good design opens up the player’s imagination instead of forcing them along a path. A frustrated player is too busy being angry at the computer to experience the wonder and mystery of his or her character and the game’s world. By having fair puzzles and “open” stories, we allow players to emote and imagine.

Okay, now we turn from software to hardware. One of the most striking developments over the last few years has been the growing use of MS-DOS machines for game development. This has led some Amiga and Mac owners to complain that there aren’t any good adventures out for their machines, or that the games that are out for those platforms don’t make good use of their full graphics and sound capabilities. How can this problem be solved?

Corey and Lori Ann Cole: Well, I just about went broke trying to develop Atari ST software a few years ago. This was what made it possible to pull up roots and come to Sierra to do games. But I think the real value of all the alternative platforms has been to force IBM and the clone-makers to play catch-up. Myself, I’m waiting for ubiquitous CD-ROM and telecom. I’d really like to be doing multiplayer games in a few years. In the meantime, the cold hard reality is that IBM clones is where the money is — and money is a good thing.

Roberta Williams: Ha! We at Sierra, probably the most guilty of developing our games on MS-DOS machines, are trying to rectify that problem. This past year, we have put teams of programmers on the more important non-MS-DOS platforms to implement our new game-development system in the best way possible for those machines. Emphasis is on the unique capabilities of each machine, and to truly be of high quality on each of them. Our new Amiga games have been shipping for several months now, and have been favorably received — and our Mac games are nearly ready.

Dave Lebling: Get an installed base of 10 million Macs or Amigas and you’ll see plenty of games for them. Probably even fewer are needed, since programmers have the hots for those platforms. But in reality what you need is companies like Sierra that can leverage their development system to move to different platforms. As Windows and 386-based machines become the IBM standard, the differences among the platforms become less significant, and using an object-oriented development system lets you port relatively easily, just like in the old days. Graphics will still be a problem, as the transforms from one machine to another will still be a pain.

Al Lowe: Money talks. When Mac games outsell MS-DOS games, you’ll see Mac-designed games ported to PCs. When Amiga games are hot, etc. In other words, as long as MS-DOS sales are 80 percent or more of the market, who can afford to do otherwise?

Mike Berlyn: I think we all want our games on as many systems as possible, but in reality the publishers are the ones who make the decisions.

When you design a game, do you decide how hard it’s going to be first, or does the difficulty level just evolve?

Ron Gilbert: I know that I have a general idea of how hard I want the game to be. Almost every game I have done has ended up being a little longer and harder than I would have liked.

Noah Falstein: I agree. I’ve often put in puzzles that I thought were easy, only to find in play-testing that the public disagreed. But since Indiana Jones and the Last Crusade I firmly believe that one good way to go is to put in multiple solutions to any puzzles that are showstoppers, and to make the remaining ones pretty easy. I think that’s the best for the players.

Dave Lebling: I think alternate solution are a red herring because you can’t make them radically different in difficulty or the easier one will always be found first.

Noah Falstein: But if you provide incentives to replay the game, you can make both beginners happy, who will find the easy alternative, and experienced gamers happy, who will want to find every solution…

Dave Lebling: Yes, but what percentage of people replay any game? What percentage even finish?

Steve Meretzky: Games that are intended for beginners — e.g., Wishbringer — are designed to be really easy, and games intended for veterans — e.g., Spellbreaker — are designed to be ball-busters. But since of course you end up getting both types for any game, my own theory is to start out with easy puzzles, have some medium-tough puzzles in the mid-game, and then wrap it up with the real whoppers. (Don’t ask me what the Babel-fish puzzle was doing right near the beginning of Hitchhiker’s Guide to the Galaxy.)

Roberta Williams: Usually the decision of how difficult the game is going to be is made about the time that the design actually begins. And that decision is based on who the main player of the game is going to be. In other words, if it’s an adventure game for children, then obviously the game will be easier. If it’s for families, the game will be harder than for children, but easier than a game strictly for adults. If it’s a game with adults in mind, then the difficulty level lies with the designer as he or she weaves the various puzzles into the plot of the story. I think even then, though, the decision of how difficult it’s going to be is made around the start of the design. Speaking personally, I usually have a good sense of which puzzles are going to be more difficult and which ones are easier to solve. There have been a few times when I miscalculated a puzzle. For instance, in King’s Quest II I thought the bridle-and-snake puzzle was fairly straightforward, but no, it wasn’t. And in The Colonel’s Bequest I didn’t think that discovering the secret passage in the house would be as difficult for some people as it turned out to be.

Corey and Lori Ann Cole: We try to keep the puzzles on the easy side in the sense of being fair; hints are somewhere in the game. But sometimes the best-laid plans of designers and developers go out the window when programming push-time comes, to mix several metaphors. But we definitely plan difficulty level in advance. The Quest for Glory series was intended to be somewhat on the easy side as adventure games go because we were introducing the concept of role-playing at the same time.

Dave Lebling: I think it’s relatively easy to make a game really hard or really easy. What’s tough is the middle-ground game. They tend to slop over to one extreme or the other, sometimes both in different puzzles, and you get a mishmash.

Mike Berlyn: I tend to design games that have various levels of difficulty within themselves, and so can appeal to a broad range of players. Like Steve, I like to open with an easy one and then mix up the middle game, saving the toughest stuff for the endgame.

Corey and Lori Ann Cole: We made a real effort to graduate the puzzles in Quest for Glory I, easier ones in the early phases.

Al Lowe: Does anyone else feel we should lighten up on our difficulty level so as to attract a broader audience and broaden our base of players?

Mike Berlyn: Making games easier isn’t going to attract more players. What will is designing and implementing them better.

Roberta Williams: Perhaps a parser-less interface would help. But I still think that each game should be thought out in advance as to who the target audience is, and then go from there on difficulty level.

Bob Bates: I agree that what is needed is not easier puzzles. I think that players want tough but fair puzzles. Where’s the rush that comes from solving an easy puzzle? What will keep them coming back for more?

Dave Lebling: One person’s easy puzzle is another’s never-solved brain-buster. There need to be a range of games and a range of puzzles in each game. Even Wishbringer, Infocom’s “easiest” game, had huge numbers of people stuck on the “easiest” puzzles.

Adventure designs have recently been criticized for becoming shorter and/or easier. Do you agree with this criticism, and, if so, how do you change a design to make a product longer and/or harder? And are harder games commercially viable?

Dave Lebling: Games are already too easy and not easy enough, and other paradoxes. Meaning that the intentional puzzles are getting too easy, and the unintentional ones — caused by size limitations, laziness, lousy parsers, bugs, etc. — are still too hard. Harder games are commercially viable, but only if the unintentional difficulty is reduced. We aren’t real good at that yet.

Roberta Williams: It may be true, to a certain extent, that adventure games have become shorter and/or easier than in the past. Four to ten years ago, adventure games were primarily text-oriented, and, as such, could be more extensive in scope, size, and complexity. Since the introduction of graphics, animation, and sound — and, coming up, speech — it is much more difficult, if not impossible, to achieve the same sort of scope that the earlier adventure games were able to accomplish. The reason for this is mainly limitations of memory, disk space, time, and cost. We adventure-game developers increasingly have to worry about cramming in beautiful graphics, realistic animation, wonderful sound, and absorbing plots, along with as many places to explore as possible, alternate paths or choices, and interesting puzzles. There is just so much space to put all that in. Something has to give. Even CD technology will not totally solve that problem. Though there is a very large disk capacity with CD, there is still a relatively small memory capacity. Also, the way the adventure-game program needs to be arranged on the CD creates problems. And as usual, with the new CD capabilities, we adventure-game developers are sure to create the most beautiful graphics you’ve ever seen, the most beautiful music you’ve ever heard, etc., etc. And that uses up disk space, even on CD.

Mike Berlyn: Shorter? Yeah, I suppose some of the newer games, whose names will remain untyped, are easier, shorter, etc. But unfortunately, they aren’t cheaper to make. I hate to tell you how much Altered Destiny is going to cost before it’s done. Accolade and myself have over ten man-years in this puppy, and a cast of many is creating it. When I created Oo-Topos or Cyborg or even Suspended, the time and money for development were a fraction of what this baby will cost. In addition, games like King’s Quest IV are larger, give more bang for the buck, and outshine many of the older games.

Steve Meretzky: A few years ago, I totally agreed with the statement that adventure games were getting too short and easy. Then I did Zork Zero, which was massive and ultimately quite hard. A good percentage of the feedback distilled down to “Too big!” It just took too long to play, and it was too hard to keep straight everything you had to do to win the game. Plus, of course, it was a major, major effort to design and implement and debug such a huge game. So, I’ve now come to the conclusion that a nice, average, 50-to-100-room, 20-to-30-hours-of-play-time, medium-level-of-difficulty game is just about right.

Corey and Lori Ann Cole: There is plenty of room left for easier games, especially since most “hard” games are hard only because they are full of unfair outguess-the-designer — or programmer or parser — puzzles. Nobody wants to play a game and feel lost and frustrated. Most of us get enough of that in our daily lives! We want smaller, richer games rather than large, empty ones, and we want to see puzzles that further the story rather than ones that are just thrown in to make the game “hard.”

Al Lowe: I’ve been trying for years to make ’em longer and harder!

Groan…

Al Lowe: But seriously, I have mixed emotions. I work hard on these things, and I hate to think that most people will never see the last half of them because they give up in defeat. On the other hand, gamers want meaty puzzles, and you don’t want to disappoint your proven audience. I think many games will become easier and easier, if only to attract more people to the medium. Of course, hard games will always be needed too, to satisfy the hardcore addicts. Geez, what a cop-out answer!

Bob Bates: You have to give the player his money’s worth, and if you can just waltz through a game, then all you have is an exercise in typing or clicking. The problem is that the definition of who the player is is changing. In trying to reach a mass market, some companies are getting away from our puzzle roots. The quandary here is that this works. The big bucks are in the mass market, and those people don’t want tough puzzles. The designers who stay behind and cater to the puzzle market may well be painting themselves into a niche.

Noah Falstein: Al and Bob have eloquently given the lead-in I was intending. But I’d like to go farther and say that we’re all painting ourselves into a corner if we keep catering to the 500,000 or so people that are regular players — and, more importantly, buyers — of adventure games. It’s like the saber-toothed tiger growing over-specialized. There are over 15 million IBM PC owners out there, and most of them have already given up on us because the games are too… geeky. Sorry, folks! Without mentioning that game that’s looming over this discussion, we’ve found that by making a very easy game, we’ve gotten more vehement, angry letters than ever before — as well as more raves from people who never played or enjoyed such games before. It seems to be financially worthwhile even now, and if more of us cater to this novice crowd, with better stories instead of harder puzzles, there will be a snowball effect. I think this is worth working towards, and I hope some of you will put part of your efforts into this. There’s always still some room for the “standard-audience” games. Interestingly enough, 60 to 100 rooms and 20 to 30 hours is precisely the niche we arrived at too! But let’s put out at least one more accessible game each year.

Dave Lebling: Most of the points I wanted to make have been made, and made well, but I’d like to add one more. What about those 20 million or more Nintendo owners out there? What kinds of games will hook them, if any? Have they written us off? I don’t think our fraction of the IBM market is quite as small as Noah’s figures make it look. Many of those IBM machines are not usable for games by policy, as they are in corporate settings. But all of the Nintendos are in home settings. Sure, they don’t have keyboards, but if there was a demand for our sort of game — a “puzzle” game, for want of a better word — there would be a keyboard-like interface or attachment, like the silly gun or the power glove. There isn’t. Why? Are we too geeky? Are puzzles and even the modicum of text that is left too much? We will have the opportunity to find out when the new game systems with keyboards start appearing in the US.

What do you all think about the idea of labeling difficulty levels and/or estimated playing time on the box, like Infocom used to do at one time?

Steve Meretzky: That was a pretty big failure. As was said earlier about puzzles, one person’s easy is another person’s hard.

Al Lowe: Heh, heh…

Steve Meretzky: For example, I found Suspended to be pretty easy, having a mind nearly as warped as Berlyn’s, but many people consider it one of Infocom’s hardest.

Bob Bates: The other Infocommies here can probably be more accurate, but my recollection is that labeling a game “advanced” scared off people, and labeling a game “easy” or “beginner” turned off lots of people too. So most of the games wound up being released as “standard,” until they dropped the scheme altogether. Still, I think some sort of indication on a very easy game, like the ones Noah was talking about, is in order. The customer has a right to know what he is purchasing.

Corey and Lori Ann Cole: But Loom was rated as an easy game, and people who were stumped on a puzzle felt like this meant they were dumb or something.

Mike Berlyn: Good point! I’m not sure that labeling a product as being easy, medium, or difficult is a real solution. I know some games which were labeled “beginner” level were too tough for me. What we as designers need to do is write better, fairer, more rounded games that don’t stop players from exploring, that don’t close off avenues. It isn’t easy, but it’s sure my goal, and I like to think that others share this goal.

Okay, this is the last question. What is your favorite adventure game and why?

Noah Falstein: This will sound like an ad, but our audience constitutes a mass market. Ron Gilbert’s next game, The Secret of Monkey Island, is the funniest and most enjoyable adventure game I’ve ever played, including the others our company has done. I’ve laughed out loud reading and rereading the best scenes.

Steve Meretzky: Based simply on the games I’ve had the most fun playing, it’s a tie between Starcross — the first ever adventure game in my genre of choice, science fiction — and the vastly ignored and underrated Nord and Bert Couldn’t Make Head or Tail of It.

Roberta Williams: I hate to say it, but I don’t play many adventure games, including our own! I really love adventure games, though. It was this love of adventure gaming that brought me into this business. However, nowadays I’m so busy, what with working on games of my own, helping my husband run the company, taking care of the kids and the house, and doing other extracurricular activities, that I literally don’t have time to play adventure games — and we all know how much time it does take to play them! Of the adventure games that I’ve played and/or seen, I like the games that Lucasfilm produces; I have a lot of respect for them. And I also enjoy the Space Quest and Leisure Suit Larry series that my company, Sierra, produces. Of my own games, I always seem to favor the game I’m currently working on since I’m most attached to it at that given moment. Right now, that would be King’s Quest V. But aside from that, I am particularly proud of The Colonel’s Bequest since it was a departure for me, and very interesting and complicated to do. I am also proud of Mixed-Up Mother Goose, especially the new version coming out. And looking way back, I still have fond memories of Time Zone, for any of you who may remember that one.

Corey and Lori Ann Cole: Of adventure games, we liked the original mainframe Zork and Space Quest III. But our favorite games are Dungeon Master and Rogue, the only games we keep going back to replay. As for our favorite of all two games we’ve done, we’re particularly proud of what we are doing with Quest for Glory II: Trial By Fire. We’re also proud of the first game, but we think Trial by Fire is going to be really great. Okay, end of commercial, at least as soon as I say, “Buy our game!” But seriously, we’re pleased with what we’ve done with the design.

Bob Bates: “You are standing outside a white house. There is a mailbox here.”

Mike Berlyn: This is my least favorite question in the world. (Well, okay, I could think up some I’d like less.) But it’s a toss-up between A Mind Forever Voyaging, Starcross, and the soon-to-be-forgotten masterpiece, Scott Adams’s Pirate Adventure. Yoho.

Dave Lebling: Hitchhiker’s Guide and Trinity. Both well thought-out, with great themes. But beyond those, the original Adventure. I just played it a little bit last night, and I still get a thrill from it. We owe a lot to Will Crowther and Don Woods, and I think that’s an appropriate sentiment to close with.


  1. One of my favorite things about this transcript is the way that Steve Meretzky and Al Lowe keep making these stupid jokes, and everybody just keeps ignoring them. I fancy I can almost hear the sighs… 

  2. It’s worth noting that the trend the Coles describe as “unfortunate” was exactly the direction in which Sierra, their employer, was moving in very aggressive fashion. The Coles thus found themselves blowing against the political winds in designing their games their way. Perhaps not coincidentally, they were also designing the best games coming out of Sierra during this period. 

  3. This was not what many participating in the conference probably wanted to hear, but it wins the prize of being the most prescient single statement of the evening. Note that Lebling not only predicted the complete commercial demise of text adventures, but he also predicted that they would survive as a hobbyist endeavor; the emphasis on the word “commercial” is original. 

  4. Steve Meretzky’s perennial Titanic proposal, which he pitched to every publisher he ever worked with, became something of an industry in-joke. There’s just no market for such a game, insisted each of the various publishers. When James Cameron’s 1997 film Titanic became the first ever to top $1 billion at the box office, and a modest little should-have-been-an-obscurity from another design team called Titanic: Adventure Out of Time rode those coattails to sales of 1 million copies, the accusations flew thick and fast from Meretzky’s quarter. But to no avail; he still hasn’t gotten to make his Titanic game. On the other hand, he’s nowhere near death, so there’s still time to fulfill his promise… 

  5. Meretzky had pitched both of these ideas as well to Infocom without success. In the longer term, however, he would get one of his wishes, at least after a fashion. “Short stories” have become the norm in modern interactive fiction, thanks largely to the Interactive Fiction Competition and its guideline that it should be possible to play an entrant to completion within two hours. 

  6. Legal threats from the makers of the board game HeroQuest had recently forced the Coles to change the name of their burgeoning series of adventure/CRPG hybrids from the perfect Hero’s Quest to the rather less perfect Quest for Glory. Obviously the fresh wound still smarted. 

  7. After some delays, the game Falstein is talking about here would be released in 1992 as Indiana Jones and the Fate of Atlantis. It would prove to be a very good adventure game, if not quite the medium-changer Falstein describes. 

  8. It’s interesting to see Lebling still using the rhetoric from Infocom’s iconic early advertising campaigns

 
47 Comments

Posted by on February 16, 2018 in Digital Antiquaria, Interactive Fiction

 

Tags: , , , , , , , , , , , ,

Monkey Island (or, How Ron Gilbert Made an Adventure Game That Didn’t Suck)

Shortly after completing Maniac Mansion, his first classic graphic adventure, Ron Gilbert started sketching ideas for his next game. “I wanted to do something that felt like fantasy and might kind of tap into what was interesting about fantasy,” he remembers, “but that wasn’t fantasy.” Gilbert loved the Pirates of the Caribbean ride at Disneyland, which took guests through a whole pirate adventure in fifteen minutes. He only wished that he could linger there, could get out of the little boat that carried guests through the attraction and wander amid the scenery. What the need to keep shoveling amusement-park guests through a paid attraction disallowed, a computer game could allow. Thus was the idea for The Secret of Monkey Island born.

The game casts you in the role of Guybrush Threepwood, a lovable loser who wants to become a pirate. Arriving on Mêlée Island, a den of piratey scum and villainy, he has to complete a set of trials to win the status of Official Pirate. Along the way, he falls in love with the island’s beautiful governor Elaine — her name sets the game up for a gleeful The Graduate homage — and soon has to rescue her from the villain of the story, the evil ghost pirate LeChuck.

The Disneyfied piracy wasn’t hard to do, especially after Gilbert discovered a charming little historical-fantasy novel by Tim Powers called On Stranger Tides. Nor was the goofy humor that was so much his stock in trade as a game designer. What did make things complicated, however, was his desire to create a more playable, forgiving adventure game than even Maniac Mansion had managed to be. Gilbert admits that he was struggling, with no more than the beginnings of a design document or, for that matter, a design philosophy, when a mandate came down from Lucasfilm Games’s parent company’s management: they wanted an adventure game to go with the upcoming film Indiana Jones and the Last Crusade. Such a mandate was unusual for the privileged little artists’ enclave that still was Lucasfilm Games at this time, but, given the freedom they had so generously been granted for so long, they were hardly in a position to argue about it. Ron Gilbert, Noah Falstein, and David Fox joined forces to grind out the Indiana Jones game, while Monkey Island went on hold for more than six months.

It was just possibly the best thing that could have happened. The delay gave Gilbert time to continue thinking about adventure-game design in the abstract, to continue groping toward that elusive something — or, better said, somethings — that would make his future games different. Hardly a theorist by nature, he nevertheless sat down and wrote out a manifesto of sorts as a way of codifying his opinions, titling it, in inimitable Ron Gilbert fashion, “Why Adventure Games Suck.” This semi-legendary document, probably the most influential ever written on the subject of adventure-game design, was published in the December 1989 issue of The Journal of Computer Game Design (the paper-based adjunct to the Computer Game Developers Conference).

Some of what Gilbert has to say in his manifesto feels a little rambling and esoteric today, while the vast majority of what does feel relevant we’ve already had reasons to discuss on other occasions — what with the general state of adventure-game design in the 1980s, sometimes on all too many other occasions. Still, the document itself and the ideas it contains can only be regarded as hugely important to the evolution of the adventure game.

Consider what the manifesto has to say about the age-old problem of locking the player out of victory without her knowledge.

I forgot to pick it up

Never require a player to pick up an item that is used later in the game if she can’t go back and get it when it is needed. It is very frustrating to learn that a seemingly insignificant object is needed, and the only way to get it is to start over or go back to a saved game. From the player’s point of view, there was no reason for picking it up in the first place. Some designers have actually defended this practice by saying that “adventure-game players know to pick up everything.” This is a cop-out. If the jar of water needs to be used on the spaceship and it can only be found on the planet, create a use for it on the planet that guarantees it will be picked up. If the time between the two uses is long enough, you can be almost guaranteed that the player forgot she even had the object.

The other way around this problem is to give the player hints about what she might need to pick up. If the aliens on the planet suggest that the player find water before returning to the ship, and the player ignores this advice, then failure is her own fault.

In The Secret of Monkey Island and all of the Lucasfilm adventure games that would follow it, Gilbert and his colleagues implemented an extreme remedy to this problem. Rather than admitting a failure to pick up the right object at the right time to be even potentially the player’s “own fault,” they made certain it was always possible to go back and get said item. Locking yourself out of victory, in other words, became literally impossible.

Now consider what the manifesto has to say about arbitrarily killing the player and about another related old bugaboo, requiring knowledge from past lives.

Live and learn

As a rule, adventure games should be able to be played from beginning to end without “dying” or saving the game if the player is very careful and very observant. It is bad design to put puzzles and situations into a game that require a player to die in order to learn what not to do next time. This is not to say that all death situations should be designed out. Danger is inherent in drama, but danger should be survivable if the player is clever.

As an exercise, take one complete path through a story game and then tell it to someone else, as if it were a standard story. If you find places where the main character could not have known a piece of information that was used (the character who learned it died in a previous game), then there is a hole in the plot.

Again, Gilbert and the rest of Lucasfilm would push much further than even the above would imply in their own future designs. Despite the claim that “danger is inherent to drama” — a claim, one has to assume, about which Gilbert must have come to think better — they made it impossible for the player to die, no matter what she did.

Gilbert tells us at the end of his manifesto that he’d like to “get rid of save games” altogether.

If there have to be save games, I would use them only when it was time to quit playing until the next day. Save games should not be a part of game play. This leads to sloppy design. As a challenge, think about how you would design a game differently if there were no save games. If you ever have the pleasure of watching a non-game player playing an adventure game you will notice they treat save games very differently than the experienced user. Some start using it as a defense mechanism only after being slapped in the face by the game a few times, the rest just stop playing.

It’s this idea of designing adventure games as if saves didn’t exist that’s the real key to understanding what made The Secret of Monkey Island and the Lucasfilm adventures which would follow it so different, even so revolutionary. Everything else springs from this one adjustment in perspective. I last played The Secret of Monkey Island nine months or so ago, when my wife and I were on a little holiday in Venice. Each evening, after a long day spent exploring the alleys and canals, we’d retire back to our cozy little hotel and I’d poke at Monkey Island for an hour or two on my laptop before bed. Having played heaps of older adventure games for years prior to getting to Monkey Island — the life of a digital antiquarian sadly doesn’t leave much time for games that aren’t on the syllabus! — I must have experienced it much as its first players did. And I have to say, it’s downright difficult to express how freeing it was to know that I didn’t need to save every ten minutes, didn’t need to stress over the potential of somehow locking myself out of victory with every action. Instead, I could feel free to explore and experiment, knowing the game would take care of me. I don’t say that every game needs to be this way, but I do know that The Secret of Monkey Island is, along with its immediate Lucasfilm predecessor Loom, perhaps the first adventure games I’ve ever played for this blog that felt like natural holiday companions, things to relax into and just enjoy rather than assault with deadly seriousness. And yet The Secret of Monkey Island in particular manages this feat without ever feeling trivial. The game represents a remarkable historical watershed, as of an entire culture of game makers and players waking up and realizing that all the little aggravations they had thought adventure games had to include really didn’t need to be in there at all.

Cheerfully blatant anachronisms like the grog machine and Stan the used-boat salesman are everywhere. Ron Gilbert has mentioned the grog machine as one of his great lessons in “copyrights and trademarks.” Apparently getting it to look enough like a Coke machine to make the joke work but not so much that Lucasfilm was likely to get sued was quite the exercise in triangulation.

Taken apart from its immense importance as a model for future designs at Lucasfilm and elsewhere, The Secret of Monkey Island might initially seem a less than overwhelming package. It exists in very typical adventure-game territory for its era, at first glance dismayingly so. We’ve got yet another sad-sack loser of a protagonist, wandering through a comedy landscape built from pop-culture detritus, anachronisms, and meta-humor. The whole ought to read as lazy as most such efforts. Yet two things save the day, both of which feel intrinsic to the people who wrote the game, Ron Gilbert and his two assistant writers Tim Schafer and Dave Grossman. The first is the marvelously unaffected quality of the humor. The game is consistently, off-handedly funny without ever conspicuously straining to be in the manner of its peers. Where their humor is labored, Monkey Island‘s is effortless. And then there’s the related quality of a certain sweetness about the game. Guybrush Threepwood is the ultimate innocent. He just wants to be a Disney version of a pirate and to rescue and win the hand of the beautiful Elaine; guile is a foreign concept to him. Not only is The Secret of Monkey Island that rarest of beasts, a self-styled comedy adventure that’s genuinely, consistently funny, it’s about as likeable a game as has ever been made. This is a game where when a cannibal asks you how to “get ahead” he means… no, that one’s just too much fun to spoil.

The Secret of Monkey Island isn’t flashy or self-consciously spectacular in the way that so many contemporaneous Sierra adventures strained to be, but it is sophisticated in its aesthetics in a way few other games of its era can match. Still working with 16-color EGA graphics (a 256-color VGA version, from which the screenshots in this article are drawn, was released within a few months of the original), artists Steve Purcell and Mark Ferrari used their limited color palette to good effect to evoke the various moods of the various environments, while Michael Land crafted a gentle reggae-influenced soundtrack to plink away unobtrusively in the background or swell up into the foreground as circumstances dictated. Playing The Secret of Monkey Island really does feel like wandering through a delightful pirate theme park (a quality which the rather infamous ending of the sequel, which we won’t go into further in this article, would take very much to heart).

Most of all, The Secret of Monkey Island thrives on its puzzle design. The game’s plot plays out in four chapters, within each of which you have broad discretion to solve puzzles at your own pace and in your own order. (“Give the player options” is another commandment in “Why Adventure Games Suck.”) Its most famous puzzle, “insult sword-fighting,” says much about the game’s personality as a whole: instead of fighting with swords, pirates in this game like to fight via insults. You need to collect these insults and their ripostes as you explore, then apply them just right to win the “sword fight.” (Hey, anything’s better than a sharp sword in the gut, right?) The idea was born as Ron Gilbert was watching old pirate movies of the Errol Flynn stripe, and noticed that the opponents spent as much time verbally as physically assaulting one another. What with a verbal joust being far easier to implement in an adventure game than a sword-fighting engine, it didn’t take him long to run with the idea.

But really the entirety of the puzzle design, top to bottom, is just superb, managing to be funny and clever and occasionally challenging without ever devolving into the random using of each object on each other object. Throughout, attention is paid to you the player’s time and sanity in a way very few games of the era bother to do. For instance, at one point you need to follow another character through the jungle to find a secret location. Most games of the time would happily make you do this over and over, every time you want to return to said location — not least because doing so could serve to boost the length of the game at no expense. The Secret of Monkey Island only makes you do it once, then proceeds to do it for you from then on. “No point in having to solve the same puzzle over and over,” said Gilbert. Amen to that.

The game’s system of nudging you on to the correct solution to many puzzles is subtle to the extent that many players never even notice it’s there — and this, it must be said, again feels like the way it ought to be. At the beginning of the game, you’re expected to fulfill three tasks to prove to the pirates on the island that Guybrush has what it takes to become a pirate as well. As you poke around the island, your challengers actually take note of what you’ve done, and will offer some hints based on your progress if you go back and talk to them. “We want to guide the player subtly through the game,” said Gilbert’s colleague David Fox. “If the game works right, it should know that you’re stuck somewhere and it should give you a little help in a subtle way, so that you can solve the puzzle without feeling like it was solved for you.” In the context of 1990, the year of The Secret of Monkey Island‘s release, this was astonishingly progressive design. “As opposed,” remarked Fox wryly, “to the kind of game where the designer seems to be saying, ‘Aha! I’ve got you this time!’ and you have to spend three hours of gameplay to find some hidden object that you need to solve one puzzle.”

A rare example of a game where every element complements every other element, The Secret of Monkey Island has gone down in history as one of the finest, most justly beloved graphic adventures ever made. And for any aspiring adventure designer, even today, it’s a veritable master class in how to make an adventure game that most definitively doesn’t suck.

Released in October of 1990 as Lucasfilm’s second adventure of the year, The Secret of Monkey Island shared with its immediate predecessor Loom its pretend-the-player-can’t-save approach to design. Loom, however, had been a bridge too far for many traditionalist adventure gamers. What with its aggressively minimalist interface and portentous setting and story, it felt like an adventure game filtered through the aesthetics of a European avant-garde film. But The Secret of Monkey Island was, to strain the metaphor, all Hollywood. Whatever its innovations, it was also very much a meat-and-potatoes adventure game in the old style, complete with a menu of verbs, a comic tone, lots of object-oriented puzzles to solve, and a length more in keeping with that people had come to expect from a $40 boxed adventure game. It was thus far better equipped to deliver the gospel of “Why Adventure Games Suck” than Loom had been. While Loom had been greeted with critical uncertainty, reviewers fell over themselves to praise The Secret of Monkey Island, which wasted no time in becoming Lucasfilm Games’s biggest hit to date. It marks an enormously important watershed in the history of Lucasfilm’s adventure games in general, the moment when they commercially and creatively came fully into their own. The classic era of Lucasfilm adventures begins in earnest with The Secret of Monkey Island, which would become nothing less than the ideal most of the games that would follow would strive, sometimes perhaps a little too self-consciously, to reach.

Its commercial performance aside, The Secret of Monkey Island‘s enormous importance in the history of the art of adventure-game design in general shouldn’t be neglected. For many designers working at other companies, Ron Gilbert’s no-deaths-and-no-dead-ends approach hit home with the force of revelation. Both Corey Cole, co-designer of the Quest for Glory series for Sierra, and Bob Bates, co-founder of Legend Entertainment, brought up The Secret of Monkey Island unprompted in recent interviews with me as a work that made a huge impression on them. By no means would all designers push as far as Ron Gilbert had in the name of making a more playable adventure game. Corey Cole’s design partner Lori Ann Cole, for example, pronounced herself to be against “capricious” death in adventure games, but insisted that the possibility of death needed to be present to foster “personal involvement” and “an emotional stake” and to elevate the game above “mere amusement” — all of which positions strike me as perfectly reasonable for the very different sort of adventure games she and Corey were making. Still, everyone serious about the art of adventure-game design simply had to reckon with The Secret of Monkey Island, had to decide what its lessons really were and how to apply them. The game’s impact was such that to speak of a pre-Monkey Island and post-Monkey Island era of adventure games wouldn’t be at all out of order.

As the 1990s began, times were beginning to change inside Lucasfilm Games. With the fire hose of cash that had been the Star Wars and Indiana Jones film franchises now ebbing and no new sequels in either blockbuster franchise on the horizon, Lucasfilm in general was concentrating on becoming a more commercially savvy organization. These changes inevitably affected the games division. Just about the instant that The Secret of Monkey Island was hitting store shelves, a major corporate reorganization was in progress at Lucasfilm, which saw the games division given far more resources — their personnel roll grew from about 25 to more than 100 between 1989 and 1991 — but also given much closer supervision. They would now be expected to justify each of their projects to the accountants. This transformation of Lucasfilm Games from sideline to major profit center was by no means viewed as a comprehensively bad thing by everyone working inside the games division — it did after all lead to them finally being let loose on the Star Wars intellectual property, something they’d been wishing for for years — but it would change the character of the place and the games that came from it forever.

The changes meant that the two sequels to Loom which Brian Moriarty had hoped to make would never be realized; Moriarty was instead sent off to work on a new educational-games initiative. A sequel to the big hit The Secret of Monkey Island, however, became a major priority under the new order, especially as Lucasfilm, now devoting lots of resources to flight simulators and those aforementioned Star Wars games, had no other adventures on their calendar for 1991. Released in December of 1991, Monkey Island 2: LeChuck’s Revenge didn’t disappoint commercially. Benefiting from the enormous good will accrued by its predecessor, it became another bestseller, and won a number of the game-of-the-year awards that a tardy industry should have been awarding to its predecessor (inertia being the force it is, most of the awards for 1990 had gone to Sierra’s pretty but horribly designed King’s Quest V, which served as its own argument for “why adventure games suck”). Today, the sequel remains almost as beloved as the original among hardcore Lucasfilm fans.

Personally, though, I’m not such a big fan of Monkey Island 2 as I am of its predecessor. Ron Gilbert had spent two and a half years designing, writing, and developing the first Monkey Island, alone or with others. He was given just a year for Monkey Island 2, a game that’s at least 50 percent larger, and I fancy I can see this disparity in the end result. The writing is neither as sharp nor as sweet. For the first time in a Ron Gilbert game, some of the humor is more gross than clever — spitting, with attention to the color and consistency of your loogies, is a major puzzle mechanic — and some of the rest is weirdly mean-spirited. Guybrush Threepwood has been transformed from the gee-whiz innocent of the first game to a bit of a raging asshole, the type of guy who steals a monocle from an innocent character who can’t see a thing without it and locks another guy who didn’t do anything to him inside a coffin. I don’t know to what I should attribute the change in tone — whether to changes going on inside Lucasfilm Games at the time, to changes going on in the personal lives of Ron Gilbert and/or the other members of his writing team, to the pressure of getting a bigger game out in much less time, or simply to happenstance. I know only that it doesn’t sit that well with me.

Captured by LeChuck in Monkey Island 2. The game will arbitrarily let you use only one item you’re carrying to effect your escape, and there’s no way to know ahead of time what that item is. Guess what that means you have to do…

In terms of puzzle design, the sequel also marks a big step down from its predecessor. While the no-deaths-and-no-dead-ends approach to design is still present, Monkey Island 2 constantly violates another of the dicta found in Ron Gilbert’s manifesto.

Arbitrary puzzles

Puzzles and their solutions need to make sense. They don’t have to be obvious, just make sense. The best reaction after solving a tough puzzle should be, “Of course, why didn’t I think of that sooner!” The worst, and most often heard after being told the solution, is, “I never would have gotten that!” If the solution can only be reached by trial and error or plain luck, it’s a bad puzzle.

Monkey Island 2 is full of these sorts of, to use Ron Gilbert’s own words, “bad puzzles.” Many solutions are so outlandish that you can stumble upon them only by using every object on every other object. At one point, for instance, you’re carrying a monkey around in your inventory (don’t ask!) when you come upon a closed water valve you need to open. Using the monkey on the valve does the trick because “monkey wrench.” Now, credit where it’s due, there’s some real wit to this. Yet it’s the sort of thing absolutely no player will ever think of on her own, especially given that the game hasn’t heretofore shown any interest in this sort of wordplay. (And that’s without even beginning to consider the problems of localization to other languages than English, which tends to render a puzzle like this into a complete non sequitur.) As you get deeper into the game, there’s more and more of this sort of thing, along with pixel hunts, an infuriating maze, and puzzles that can only be solved by trying to pick up every seemingly immovable item on the screen. Monkey Island 2 at times seems like an experiment in how annoying an adventure game can be without technically violating Lucasfilm’s no-deaths-and-no-dead-ends policy.

Arbitrary puzzles that can be solved only through trial and error would prove to be Lucasfilm’s Achilles heel going forward; too many of the games to come would feature puzzles designed more to create a laugh at how ridiculous they are than to be interesting or satisfying to solve. The end result is to create a feeling in the player of playing the interface rather than participating actively in the game world.

Despite my complaints, by no means was Lucasfilm’s progressive design philosophy completely abandoned for Monkey Island 2. The puzzle you need to solve to get through the swamp is a prime example. After you figure out what object to use as a paddle, the game solves the puzzle for you on each return visit.

Perhaps aware that they had crossed a line in trying to make Monkey Island 2 more difficult than its predecessor, Lucasfilm added a “Lite” mode to the game which scales the complexity of the puzzle structure back dramatically. Unfortunately, most players agree that the Lite mode goes too far in the other direction, removing most of the interest from the game. Taken together, the very presence of the two modes speaks to a design that didn’t quite hit the sweet spot of the first game, and to a design team that at some intuitive level may have realized this.

Shortly after completing Monkey Island 2, Ron Gilbert left Lucasfilm Games, resulting in a long hiatus for Guybrush, Elaine, LeChuck, and company. Given my snail’s pace through history, there will thus likely be an almost equally lengthy hiatus before they’ll grace these pages again. For now, I can only strongly encourage you to make the time to play The Secret of Monkey Island if you haven’t already. It’s as strong a comedy adventure as you’ll ever see, and as historically important an adventure game as any released since Crowther and Woods’s seminal original Adventure. While you can take or leave its sequel as you see fit, The Secret of Monkey Island is one adventure game that everybody really ought to play. It’s just that important. And even better, it’s just that good.

(Sources: the films From Bedrooms to Billions: The Amiga Years and its associated extras; the book Droidmaker: George Lucas and the Digital Revolution by Michael Rubin; A.C.E. of April 1990; The Adventurer of Fall 1990, Spring 1991, and Fall 1991; Computer Gaming World of December 1990, June 1991, October 1991, November 1991, January 1992, May 1992, and November 1992; Retro Gamer 34. Also Ron Gilbert’s blog, The Grumpy Gamer.)

 
 

Tags: , , ,

Loom (or, how Brian Moriarty Proved That Less is Sometimes More)

In April of 1988, Brian Moriarty of Infocom flew from the East Coast to the West to attend the twelfth West Coast Computer Faire and the first ever Computer Game Developers Conference. Hard-pressed from below by the slowing sales of their text adventures and from above by parent company Activision’s ever more demanding management, Infocom didn’t have the money to pay for Moriarty’s trip. He therefore had to go on his own dime, a situation which left him, as he would later put it, very “grumpy” about the prospect of his ongoing employment by the very company at which he had worked so desperately to win a spot just a few years before.

The first West Coast Computer Faire back in 1977 had hosted the public unveiling of the Apple II and the Commodore PET, thus going down in hacker lore as the moment when the PC industry was truly born. By 1988, the Faire wasn’t the hugely important gathering it once had been, having been largely superseded on the industry’s calendar by glitzier events like the Consumer Electronics Show. Nevertheless, its schedule had its interesting entries, among them a lecture by Chris Crawford, the founder of the Computer Game Developers Conference which Moriarty would attend the next day. Moriarty recalls showing up a little late to Crawford’s lecture, scanning the room, and seeing just one chair free, oddly on the first row. He rushed over to take it, and soon struck up a conversation with the man sitting next to him, whom he had never met before that day. As fate would have it, his neighbor’s name was Noah Falstein, and he worked for Lucasfilm Games.

Attendees to the first ever Computer Game Developers Conference. Brian Moriarty is in the reddish tee-shirt at center rear, looking cool in his rock-star shades.

Falstein knew and admired Moriarty’s work for Infocom, and knew likewise, as did everyone in the industry, that things hadn’t been going so well back in Cambridge for some time now. His own Lucasfilm Games was in the opposite position. After having struggled since their founding back in 1982 to carve out an identity for themselves under the shadow of George Lucas’s Star Wars empire, by 1988 they finally had the feeling of a company on the rise. With Maniac Mansion, their big hit of the previous year, Falstein and his colleagues seemed to have found in point-and-click graphical adventures a niche that was both artistically satisfying and commercially rewarding. They were already hard at work on the follow-up to Maniac Mansion, and Lucasfilm Games’s management had given the go-ahead to look for an experienced adventure-game designer to help them make more games. As one of Infocom’s most respected designers, Brian Moriarty made an immediately appealing candidate, not least in that Lucasfilm Games liked to see themselves as the Infocom of graphical adventures, emphasizing craftsmanship and design as a way to set themselves apart from the more slapdash games being pumped out in much greater numbers by their arch-rivals Sierra.

Brian Moriarty on the job at Lucasfilm.

For his part, Moriarty was ripe to be convinced; it wasn’t hard to see the writing on the wall back at Infocom. When Falstein showed him some photographs of Lucasfilm Games’s offices at Skywalker Ranch in beautiful Marin County, California, and shared stories of rubbing elbows with movie stars and casually playing with real props from the Star Wars and Indiana Jones movies, the contrast with life inside Infocom’s increasingly empty, increasingly gloomy offices could hardly have been more striking. Then again, maybe it could have been: at his first interview with Lucasfilm Games’s head Steve Arnold, Moriarty was told that the division had just two mandates. One was “don’t lose money”; the other was “don’t embarrass George Lucas.” Anything else — like actually making money — was presumably gravy. Again, this was music to the ears of Moriarty, who like everyone at Infocom was now under constant pressure from Activision’s management to write games that would sell in huge numbers.

Brian Moriarty arrived at Skywalker Ranch for his first day of work on August 1, 1988. As Lucasfilm Games’s new star designer, he was given virtually complete freedom to make whatever game he wanted to make.

Noah Falstein in Skywalker Ranch’s conservatory. This is where the Games people typically ate their lunches, which were prepared for them by a gourmet chef. There were definitely worse places to work…

For all their enthusiasm for adventure games, the other designers at Lucasfilm were struggling a bit at the time to figure out how to build on the template of Maniac Mansion. Zak McKracken and the Alien Mindbenders, David Fox’s follow-up to Ron Gilbert’s masterstroke, had been published just the day before Moriarty arrived at Skywalker Ranch. It tried a little too obviously to capture the same campy charm, whilst, in typical games-industry fashion, trying to make it all better by making it bigger, expanding the scene of the action from a single night spent in a single mansion to locations scattered all around the globe and sometimes off it. The sense remained that Lucasfilm wanted to do things differently from Sierra, who are unnamed but ever-present — along with a sly dig at old-school rivals like Infocom still making text adventures — within a nascent manifesto of three paragraphs published in Zak McKracken‘s manual, entitled simply “Our Game Design Philosophy.”

We believe that you buy games to be entertained, not to be whacked over the head every time you make a mistake. So we don’t bring the game to a screeching halt when you poke your nose into a place you haven’t visited before. In fact, we make it downright difficult to get a character “killed.”

We think you’d prefer to solve the game’s mysteries by exploring and discovering. Not by dying a thousand deaths. We also think you like to spend your time involved in the story. Not typing in synonyms until you stumble upon the computer’s word for a certain object.

Unlike conventional computer adventures, Zak McKracken and the Alien Mindbenders doesn’t force you to save your progress every few minutes. Instead, you’re free to concentrate on the puzzles, characters, and outrageous good humor.

Worthy though these sentiments were, Lucasfilm seemed uncertain as yet how to turn them into practical rules for design. Ironically, Zak McKracken, the game with which they began publicly articulating their focus on progressive design, is the most Sierra-like Lucasfilm game ever made, with the sheer nonlinear sprawl of the thing spawning inevitable confusion and yielding far more potential dead ends than its designer would likely wish to admit. While successful enough in its day, it never garnered the love that’s still accorded to Maniac Mansion today.

Lucasfilm Games’s one adventure of 1989 was a similarly middling effort. A joint design by Gilbert, Falstein, and Fox, Indiana Jones and the Last Crusade: The Graphic Adventure — an Action Game was also made — marked the first time since Labyrinth that the games division had been entrusted with one of George Lucas’s cinematic properties. They don’t seem to have been all that excited at the prospect. The game dutifully walks you through the plot you’ve already watched unfold on the silver screen, without ever taking flight as a creative work in its own right. The Lucasfilm “Game Design Philosophy” appears once again in the manual in almost the exact same form as last time, but once again the actual game hews to this ideal imperfectly at best, with, perhaps unsurprisingly given the two-fisted action movie on which it’s based, lots of opportunities to get Indy killed and have to revert to one of those save files you supposedly don’t need to create.

So, the company was rather running to stand still as Brian Moriarty settled in. They were determined to evolve their adventure games in design terms to match the strides Sierra was making in technology, but were uncertain how to actually go about the task. Moriarty wanted to make his own first work for Lucasfilm a different, more somehow refined experience than even the likes of Maniac Mansion. But how to do so? In short, what should he do with his once-in-a-lifetime chance to make any game he wanted to make?

Flipping idly through a computer magazine one day, he was struck by an advertisement that prominently featured the word “loom.” He liked the sound of it; it reminded him of other portentous English words like “gloom”, “doom,” and “tomb.” And he liked the way it could serve as either a verb or a noun, each with a completely different meaning. In a fever of inspiration, he sat down and wrote out the basis of the adventure game he would soon design, about a Loom which binds together the fabric of reality, a Guild of Weavers which uses the Loom’s power to make magic out of sound, and Bobbin Threadbare, the “Loom Child” who must save the Loom — and thus the universe — from destruction before it’s too late. It would be a story and a game with the stark simplicity of fable.

Simplicity, however, wasn’t exactly trending in the computer-games industry of 1988. Since the premature end of the would-be Home Computer Revolution of the early 1980s, the audience for computer games had grown only very slowly. Publishers had continued to serve the same base of hardcore players, who lusted after ever more complex games to take advantage of the newest hardware. Simulations had collected ever more buttons and included ever more variables to keep track of, while strategy games had gotten ever larger and more time-consuming. Nor had adventure games been immune to the trend, as was attested by Moriarty’s own career to date. Each of his three games for Infocom had been bigger and more difficult than the previous, culminating in his adventure/CRPG hybrid Beyond Zork, the most baroque game Infocom had made to date, with more options for its onscreen display alone than some professional business applications. Certainly plenty of existing players loved all this complexity. But did all games really need to go this way? And, most interestingly, what about all those potential players who took one look at the likes of Beyond Zork and turned back to the television? Moriarty remembered a much-discussed data point that had emerged from the surveys Infocom used to send to their customers: the games people said were their favorites overlapped almost universally with those they said they had been able to finish. In keeping with this trend, Moriarty’s first game for Infocom, which had been designed as an introduction to interactive fiction for newcomers, had been by far his most successful. What, he now thought, if he used the newer hardware at his disposal in the way that Apple has historically done, in pursuit of simplicity rather than complexity?

The standard Lucasfilm interface of the late 1980s, shown here in Maniac Mansion.

Lucasfilm Games’s current point-and-click interface, while undoubtedly the most painless in the industry at the time, was nevertheless far too complicated for Moriarty’s taste, still to a large extent stuck in the mindset of being a graphical implementation of the traditional text-adventure interface rather than treating the graphical adventure as a new genre in its own right. Thus the player was expected to first select a verb from a list at the bottom of the screen and then an object to which to apply it. The interface had done the job well enough to date, but Moriarty felt that it would interfere with the seamless connection he wished to build between the player sitting there before the screen and the character of Bobbin Threadbare standing up there on the screen. He wanted something more immediate, more intuitive — preferably an interface that didn’t require words at all. He envisioned music as an important part of his game: the central puzzle-solving mechanic would involve the playing of “drafts,” little sequences of notes created with Bobbin’s distaff. But he wanted music to be more than a puzzle-solving mechanic. He wanted the player to be able to play the entire game like a musical instrument, wordlessly and beautifully. He was thus thrilled when he peeked under the hood of Lucasfilm’s SCUMM adventure-game engine and found that it was possible to strip the verb menu away entirely.

Some users of Apple’s revolutionary HyperCard system for the Macintosh were already experimenting with wordless interfaces. Within weeks of HyperCard’s debut, a little interactive storybook called Inigo Gets Out, “programmed” by a non-programmer named Amanda Goodenough, had begun making the rounds, causing a considerable stir among industry insiders. The story of a house cat’s brief escape to the outdoors, it filled the entire screen with its illustrations, responding intuitively to single clicks on the pictures. Just shortly before Moriarty started work at Lucasfilm Games, Rand and Robyn Miller had taken this experiment a step further with The Manhole, a richer take on the concept of an interactive children’s storybook. Still, neither of these HyperCard experiences quite qualified as a game, and Moriarty and Lucasfilm were in fact in the business of making adventure games. Loom could be simple, but it had to be more than a software toy. Moriarty’s challenge must be to find enough interactive possibility in a verb-less interface to meet that threshold.

In response to that challenge, Moriarty created an interface that stands out today as almost bizarrely ahead of its time; not until years later would its approach be adopted by graphic adventures in general as the default best way of doing things. Its central insight, which it shared with the aforementioned HyperCard storybooks, was the realization that the game didn’t always need the player to explicitly tell it what she wanted to do when she clicked a certain spot on the onscreen picture. Instead the game could divine the player’s intention for itself, based only on where she happened to be clicking. What was sacrificed in the disallowing of certain types of more complex puzzles was gained in the creation of a far more seamless, intuitive link between the player, the avatar she controlled, and the world shown on the screen.


The brief video snippet above shows Loom‘s user interface in its entirety. You make Bobbin walk around by clicking on the screen. Hovering the mouse over an object or character with which Bobbin can interact brings up an image of that object or character in the bottom right corner of the screen; double-clicking the same “hot spot” then causes Bobbin to engage, either by manipulating an object in some way or by talking to another character. Finally, Bobbin can cast “spells” in the form of drafts by clicking on the musical staff at the bottom of the screen. In the snippet above, the player learns the “open” draft by double-clicking on the egg, an action which in this case results in Bobbin simply listening to it. The player and Bobbin then immediately cast the same draft to reveal within the egg his old mentor, who has been transformed into a black swan.

Moriarty seemed determined to see how many of the accoutrements of traditional adventure games he could strip away and still have something that was identifiable as an adventure game. In addition to eliminating menus of verbs, he also excised the concept of an inventory; throughout the game, Bobbin carries around with him nothing more than the distaff he uses for weaving drafts. With no ability to use this object on that other object, the only puzzle-solving mechanic that’s left is the magic system. In the broad strokes, magic in Loom is very much in the spirit of Infocom’s Enchanter series, in which you collect spells for your spell book, then cast them to solve puzzles that, more often than not, reward you with yet more spells. In Loom the process is essentially the same, except that you’re collecting musical drafts to weave on your distaff rather than spells for your spell book. And yet this musical approach to spell weaving is as lovely as a game mechanic can be. Lucasfilm thoughtfully included a “Book of Patterns” with the game, listing the drafts and providing musical staffs on which you can denote their sequences of notes as you discover them while playing.

The audiovisual aspect of Loom was crucial to capturing the atmosphere of winsome melancholia Moriarty was striving for. Graphics and sound were brand new territory for him; his previous games had consisted of nothing but text. Fortunately, the team of artists that worked with him grasped right away what was needed. Each of the guilds of craftspeople which Bobbin visits over the course of the game is marked by its own color scheme: the striking emerald of the Guild of Glassmakers, the softer pastoral greens of the Guild of Shepherds, the Stygian reds of the Guild of Blacksmiths, and of course the lovely, saturated blues and purples of Bobbin’s own Guild of Weavers. This approach came in very handy for technical as well as thematic reasons, given that Loom was designed for EGA graphics of just 16 onscreen colors.

The overall look of Loom was hugely influenced by the 1959 Disney animated classic Sleeping Beauty, with many of the panoramic shots in the game dovetailing perfectly with scenes from the film. Like Sleeping Beauty, Loom was inspired and accompanied by the music of Pyotr Ilyich Tchaikovsky, whom Moriarty describes as his “constant companion throughout my life”; while Sleeping Beauty draws from Tchaikovsky’s ballet of the same name, Loom draws from another of his ballets, Swan Lake. Loom sounds particularly gorgeous when played through a Roland MT-32 synthesizer board — an experience that, given the $600 price tag of the Roland, far too few players got to enjoy back in the day. But regardless of how one hears it, it’s hard to imagine Loom without its classical soundtrack. Harking back to Hollywood epics like 2001: A Space Odyssey, the MT-32 version of Loom opens with a mood-establishing orchestral overture over a blank screen.


To provide the final touch of atmosphere, Moriarty walked to the other side of Skywalker Ranch, to the large brick building housing Skywalker Sound, and asked the sound engineers in that most advanced audio-production facility in the world if they could help him out. Working from a script written by Moriarty and with a cast of voice actors on loan from the BBC, the folks at Skywalker Sound produced a thirty-minute “audio drama” setting the scene for the opening of the game; it was included in the box on a cassette. Other game developers had occasionally experimented with the same thing as a way of avoiding having to cover all that ground in the game proper, but Loom‘s scene-setter stood out for its length and for the professional sheen of its production. Working for Lucasfilm did have more than a few advantages.

If there’s something to complain about when it comes to Loom the work of interactive art, it must be that its portentous aesthetics lead one to expect a thematic profundity which the story never quite attains. Over the course of the game, Bobbin duly journeys through Moriarty’s fairy-tale world and defeats the villain who threatens to rip asunder the fabric of reality. The ending, however, is more ambiguous than happy, with only half of the old world saved from the Chaos that has poured in through the rip in the fabric. I don’t object in principle to the idea of a less than happy ending (something for which Moriarty was becoming known). Still, and while the final image is, like everything else in the game, lovely in its own right, this particular ambiguous ending feels weirdly abrupt. The game has such a flavor of fable or allegory that one somehow wants a little more from it at the end, something to carry away back to real life. But then again, beauty, which Loom possesses in spades, has a value of its own, and it’s uncertain whether the sequels Moriarty originally planned to make — Loom had been envisioned as a trilogy — would have enriched the story of the first game or merely, as so many sequels do, trampled it under their weight.

From the practical standpoint of a prospective purchaser of Loom upon its initial release, on the other hand, there’s room for complaint beyond quibbling about the ending. We’ve had occasion before to observe how the only viable model of commercial game distribution in the 1980s and early 1990s, as $40 boxed products shipped to physical store shelves, had a huge effect on the content of those games. Consumers, reasonably enough, expected a certain amount of play time for their $40. Adventure makers thus learned that they needed to pad out their games with enough puzzles — too often bad but time-consuming ones — to get their play times up into the region of at least twenty hours or so. Moriarty, however, bucked this trend in Loom. Determined to stay true to the spirit of minimalism to the bitter end, he put into the game only what needed to be there. The end result stands out from its peers for its aesthetic maturity, but it’s also a game that will take even the most methodical player no more than four or five hours to play. Today, when digital distribution has made it possible for developers to make games only as long as their designs ask to be and adjust the price accordingly, Loom‘s willingness to do what it came to do and exit the stage without further adieu is another quality that gives it a strikingly modern feel. But in the context of the times of the game’s creation, it was a bit of a problem.

When Loom was released in March of 1990, many hardcore adventure gamers were left nonplussed not only by the game’s short length but also by its simple puzzles and minimalist aesthetic approach in general, so at odds with the aesthetic maximalism that has always defined the games industry as a whole. Computer Gaming World‘s Johnny Wilson, one of the more sophisticated game commentators of the time, did get what Loom was doing, praising its atmosphere of “hope and idealism tainted by realism.” Others, though, didn’t seem quite so sure what to make of an adventure game that so clearly wanted its players to complete it, to the point of including a “practice” mode that would essentially solve all the puzzles for them if they so wished. Likewise, many players just didn’t seem equipped to appreciate Loom‘s lighter, subtler aesthetic touch. Computer Gaming World‘s regular adventure-gaming columnist Scorpia, a traditionalist to the core, said the story “should have been given an epic treatment, not watered down” — a terrible idea if you ask me (if there’s one thing the world of gaming, then or now, doesn’t need, it’s more “epic” stories). “As an adventure game,” she concluded, “it is just too lightweight.” Ken St. Andre, creator of Tunnels & Trolls and co-creator of Wasteland, expressed his unhappiness with the ambiguous ending in Questbusters, the ultimate magazine for the adventuring hardcore:

The story, which begins darkly, ends darkly as well. That’s fine in literature or the movies, and lends a certain artistic integrity to such efforts. In a game, however, it’s neither fair nor right. If I had really been playing Bobbin, not just watching him, I would have done some things differently, which would have netted a different conclusion.

Echoing as they do a similar debate unleashed by the tragic ending of Infocom’s Infidel back in 1983, the persistence of such sentiments must have been depressing for Brian Moriarty and others trying to advance the art of interactive storytelling. St. Andre’s complaint that Loom wouldn’t allow him to “do things differently” — elsewhere in his review he claims that Loom “is not a game” at all — is one that’s been repeated for decades by folks who believe that anything labeled as an interactive story must allow the player complete freedom to approach the plot in her own way and to change its outcome. I belong to the other camp: the camp that believes that letting the player inhabit the role of a character in a relatively fixed overarching narrative can foster engagement and immersion, even in some cases new understanding, by making her feel she is truly walking in someone else’s shoes — something that’s difficult to accomplish in a non-interactive medium.

Responses like those of Scorpia and Ken St. Andre hadn’t gone unanticipated within Lucasfilm Games prior to Loom‘s release. On the contrary, there had been some concern about how Loom would be received. Moriarty had countered by noting that there were far, far more people out there who weren’t hardcore gamers like those two, who weren’t possessed of a set of fixed expectations about what an adventure game should be, and that many of these people might actually be better equipped to appreciate Loom‘s delicate aesthetics than the hardcore crowd. But the problem, the nut nobody would ever quite crack, would always be that of reaching this potential alternate customer base. Non-gamers didn’t read the gaming magazines where they might learn about something like Loom, and even Lucasfilm Games wasn’t in a position to launch a major assault on the alternative forms of media they did peruse.

In the end, Loom wasn’t a flop, and thus didn’t violate Steve Arnold’s dictum of “don’t lose money” — and certainly it didn’t fall afoul of the dictum of “don’t embarrass George.” But it wasn’t a big hit either, and the sequels Moriarty had anticipated for better or for worse never got made. Ron Gilbert’s The Secret of Monkey Island, Lucasfilm’s other adventure game of 1990, was in its own way as brilliant as Moriarty’s game, but was much more traditional in its design and aesthetics, and wound up rather stealing Loom‘s thunder. It would be Monkey Island rather than Loom that would become the template for Lucasfilm’s adventure games going forward. Lucasfilm would largely stick to comedy from here on out, and would never attempt anything quite so outré as Loom again. It would only be in later years that Moriarty’s game would come to be widely recognized as one of Lucasfilm Games’s finest achievements. Such are the frustrations of the creative life.

Having made Loom, Brian Moriarty now had four adventure games on his CV, three of which I consider to be unassailable classics — and, it should be noted, the fourth does have its fans as well. He seemed poised to remain a leading light in his creative field for a long, long time to come. It therefore feels like a minor tragedy that this, his first game for Lucasfilm, would mark the end of his career in adventure games rather than a new beginning; he would never again be credited as the designer of a completed adventure game. We’ll have occasion to dig a little more into the reasons why that should have been the case in a future article, but for now I’ll just note how much an industry full of so many blunt instruments could have used his continuing delicate touch. We can only console ourselves with the knowledge that, should Loom indeed prove to be the last we ever hear from him as an adventure-game designer, it was one hell of a swansong.

(Sources: the book Game Design Theory and Practice by Richard Rouse III; ACE of April 1990; Questbusters of June 1990 and July 1990; Computer Gaming World of April 1990 and July/August 1990. But the bulk of this article was drawn from Brian Moriarty’s own Loom postmortem for, appropriately enough, the 2015 Game Developers Conference, which was a far more elaborate affair than the 1988 edition.

Loom is available for purchase is from GOG.com. Sadly, however, this is the VGA/CD-ROM re-release — I actually prefer the starker appearance of the original EGA graphics — and lacks the scene-setting audio drama. It’s also afflicted with terrible voice acting which completely spoils the atmosphere, and the text is bowdlerized to boot. Motivated readers should be able to find both the original version and the audio drama elsewhere on the Internet without too many problems. I do recommend that you seek them out, perhaps after purchasing a legitimate copy to fulfill your ethical obligation, but I can’t take the risk of hosting them here.)

 
62 Comments

Posted by on February 18, 2017 in Digital Antiquaria, Interactive Fiction

 

Tags: , ,