RSS

Monthly Archives: November 2015

The 68000 Wars, Part 4: Rock Lobster

In the years following Jack Tramiel’s departure, Commodore suffered from a severe leadership deficit. The succession of men who came and went from the company’s executive suites with dizzying regularity often meant well, were often likable enough in their way. Yet they were also weak-willed men who offered only timid, conventional ideas whilst living in perpetual terror of the real boss of the show, Commodore’s dilettantish chairman of the board and interfering largest stockholder Irving Gould.

The exception that proves the rule of atrocious management is Thomas Rattigan, the man who during his brief tenure saved Commodore and in the process the Commodore Amiga from an early death. Rattigan wasn’t, mind you, a visionary; he never got the time to demonstrate such qualities even if he did happen to possess them. His wasn’t any great technical mind, nor was he an intrinsic fan of computers as an end unto themselves; in common with a rather distressing number of industry executives of the time, Rattigan, like Apple’s John Sculley a veteran of Pepsi Cola, seemed to take a perverse pride in his computer illiteracy, saying he “never got beyond the slide rule” and not even bothering to place a computer on his desk. He may not have even been a terribly nice guy; the thousands of employees he laid off, among them virtually the entire team that had once been Amiga, Incorporated, certainly aren’t likely to invite him to dinner anytime soon. No, Rattigan was simply competent, and carried along with that competence a certain courage of his own convictions. That was more than enough to make him stand out from his immediate predecessor and his many successors like the Beatles at a battle of the bands.

Thomas Rattigan

Thomas Rattigan

Rattigan was appointed President and Chief Operating Officer of Commodore International on December 2, 1985, and Chief Executive Officer on April 1, 1986, succeeding the feckless former steel executive Marshall Smith, whose own hapless tenure would serve as a blueprint for most of the Commodore leaders not named Rattigan who would follow. After replacing Tramiel in February of 1984, Smith had fiddled while Commodore burned, going from the billion-dollar face of home computing in North America to the business pages’ favorite source of schadenfreude, hemorrhaging money and living under the shadow of a gleeful deathwatch. The stock had dropped from almost $65 per share at the peak of Tramiel’s reign to less than $5 per share at the nadir of Smith’s. It was Rattigan, in one of his last acts before assuming the mantle of CEO as well as president, who negotiated the last-ditch $135 million loan package that gave Commodore — in other words, Rattigan himself — a lease on life of about one year to turn things around.

Some of the changes that Rattigan enacted to effect that turnaround were as inevitable as they were distressing: the waves of layoffs and cutbacks that had already begun under Smith’s reign continued for some time. Unlike Smith, however, Rattigan understood that he couldn’t cost-reduce Commodore back to profitablity.

The methods that Rattigan used to implement triage on the profit side of the ledger sheet were unsexy but surprisingly effective. One was entry into the burgeoning market for commodity-priced PC clones, hardware that could be thrown together quickly using off-the-shelf components and sold at a reasonable profit. Commodore’s line of PC clones would never do much of anything in North America — the nameplate was too associated with cheap, chirpy home computers for any corporate purchasing manager to glance at it twice — but it did do quite well in Europe; in some European countries, especially West Germany, the Commodore brand remained as respectable as any other.

Rattigan’s other revenue-boosting move was even more simple and even more effective. Commodore’s engineers had been working on a new version of the 64. Dubbed internally the 64CR, for “Cost Reduced,” it was built around a redesigned circuit board that better integrated many of the chips and circuitry using the latest production processes, resulting in a substantial reduction in the cost of production. The chassis and case were also simplified — for example, to use only two instead of many different types of screws. While they were at it, Commodore dramatically changed the look of the machine and most of its common peripherals to match that of the newer Commodore 128, thus creating a uniform appearance across their 8-bit line. As Rattigan said, “I think you’ve got to give people the opportunity not to have a black monitor, a green CPU, and a red disk drive.”

Commodore 64C

Commodore 64C

All of which was very practical and commonsensical. Looking at the new machine, however, Rattigan saw an opportunity to do something Commodore had never done before: to raise its price, and thereby to recoup some desperately needed profit margin. This really was a revolutionary thought for Commodore. Ever since releasing their VIC-20 model that had created the home-computer segment in North America, Commodore had competed almost entirely on the basis of offering more machine for less money than the other folks — an approach that did much to create the low-rent image that would dog the brand for the rest of the company’s life. Commodore had always kept their profit margins razor thin in comparison to the rest of the industry, trusting that they would, as the old saying/joke goes, “make it up in volume.” Now, though, Rattigan realized that the 64 had much more than price alone going for it. Almost everyone buying a 64 in 1986 was motivated largely by the platform’s peerless selection of games. Most, he theorized, would be willing to pay a little more than what Commodore was currently charging to gain access to that library. Thus when Commodore announced the facelifted 64 — now rechristened simply the 64C for obvious reasons — they also announced a 20 percent bump in its wholesale price. To ease some of the pain, they would bundle with it something called GEOS, an independently developed graphically-oriented operating environment that claimed to turn the humble 64 into a mini-Macintosh. (It didn’t really, of course, but it was a noble, impressive effort for a machine with a 1 MHz 8-bit processor and 64 K of memory.) Anyone who’s been around manufacturing at all will understand just what a huge difference a price increase of that magnitude, combined with a substantial reduction in manufacturing cost, would mean to Commodore’s bottom line if customers did indeed prove willing to continue buying the new model in roughly the same numbers as the old. Thankfully, Rattigan’s instincts proved correct. The 64C picked up right where the older model had left off, a brisk — and vastly more profitable — seller.

Sometimes, then, the simplest fixes really are the most effective. Taken together with the cost-cutting, these two measures returned Commodore to modest profitability well before Rattigan’s one-year deadline expired. Entering 1987, the company looked to be in relatively good shape for the short term. Yet questions still swirled around its long-term future. If Commodore didn’t want to accept the depressing fate of becoming strictly a maker of PC clones for the European market, they needed a successful platform of their own that could become the successor to the 64, which was proving longer lived than anyone had ever predicted but couldn’t go on forever. That successor had to be the Amiga. And therein lay problems.

The Amiga was in a sadly moribund state by the beginning of 1987. The gala Lincoln Center debut was now eighteen months in the past, but it felt like an eternity. The excitement with which the press had first greeted the new machine had long since been replaced by narratives of failure and marketing ineptitude. Commodore had stopped production of the Amiga in mid-1986 after making just 140,000 machines, yet was still able to fill the trickle of new orders from warehouse stock. Sure, some pretty good games had been made for the Amiga, at least one of which was genuinely groundbreaking, but with numbers like those how long would that continue? Already Electronic Arts had quietly sidled away from their early declarations that together they and the Amiga would “revolutionize the home-computer industry,” turning their focus back to other, more plebeian platforms where they could actually sell enough games to make it worth their while. Ditto big players in business and productivity software like Borland, Ashton-Tate, and WordPerfect. The industry at large, it seemed, was just about ready to put a fork in Commodore’s erstwhile dream machine.

The Amiga’s most obvious failing was one of marketplace positioning. Really, just who was this machine for? There were two obvious markets: homes, where it would make the best games machine the world had yet seen; and the offices of creative professionals who could make use of its unprecedented multimedia capabilities. Yet the original Amiga model had managed to miss both targets in some fairly fundamental ways. Svelte and sexy as it was, it lacked the internal expansion slots and big power supply necessary to easily outfit it with the hard drives, memory expansions, accelerator cards, and genlocks demanded by the professionals. Meanwhile its price of almost $2000 for a reasonably complete, usable system was far too high for the home market that had so embraced the Commodore 64. Throw in horrid Commodore marketing that ignored both applications in favor of positioning the Amiga as some sort of challenger to the PC-clone business standard, and it was remarkable that the Amiga had sold as well as it had.

If there was a bright spot, it was that the Amiga’s obvious failing had an equally obvious solution: not one but two new models, each perfectly suited for — and, hopefully, marketed toward — one of its two logical customer bases. Rattigan, industry neophyte though he was, saw this reasoning as clearly as anyone, and pushed his engineers to deliver both new machines as quickly as possible. They were officially announced via a low-key, closed-door presentation to select members of the press at the January 1987 Winter Consumer Electronics Show. The two new models would entirely replace the original, which had always been officially called the Amiga 1000 but had seldom been referred to by that name heretofore. The Amiga 2000 would be the big, professional-level machine, with a full 1MB of memory standard — four times that of the 1000 — and all the slots and expansion possibilities a programmer, artist, or video-production specialist — or, for that matter, a game developer — could possibly want.

Amiga 2000

Amiga 2000

But it was the Amiga 500 that would become the most successful Amiga model ever released, as well as the heart of its legacy as a gaming platform. Designed primarily by George Robbins and Bob Welland at Commodore’s West Chester, Pennsylvania, headquarters — the slowly evaporating original Los Gatos Amiga team had little to do with either of the new models — the 500 was code-named “Rock Lobster” during development after the B-52’s song (reason enough to love it right there if you ask me). Key to the work was a re-engineering of Agnus, the most complex of the Amiga’s custom chips, to make it smaller, simpler, and cheaper to manufacture; the end result was known as “Fat Agnus.” That accomplished, Robbins and Welland managed to stuff the contents of the 1000’s case into an all-in-one design that looked like a bulbous, overgrown Commodore 128.

Amiga 500

Amiga 500

The Amiga 500 wasn’t, especially in contrast to the 1000, going to win any beauty contests, but it got the job done. There was a disk drive built into the side of the case, a “trap door” underneath to easily increase memory from the standard 512 K to 1 MB, and an expansion port in lieu of the Amiga 2000’s slots that let the user add peripherals the old-fashioned Commodore way, by daisy-chaining them across the desktop. Best of all, a usable system could be had for around $1000, still a stratum or two above the likes of a 64 or 128 but nowhere near so out of the reach of the enthusiastic gamer or home hacker as had been the first Amiga. Compromised in some ways though it may have been from an engineering standpoint, enough to prompt a chorus of criticism from the old Los Gatos Amigans, the Amiga 500 was a brilliant little machine from a strategic standpoint, the smartest single move the post-Tramiel Commodore would ever make outside of electing to buy Amiga, Incorporated, in the first place.

But unfortunately, this was still Irving Gould’s Commodore, a company that seldom failed to follow every good decision with several bad ones. Amiga circles and the trade press at large were buzzing with anticipation for the not-yet-released new models, which were justifiably expected to change everything, when word hit the business press on April 23 that Thomas Rattigan had been unceremoniously fired. Like the firing of Jack Tramiel three years before when things were going so very well, it made and makes little sense. Gould would later say that Rattigan had been fired for “disobeying the chairman of the board” — i.e., him — and for “gross disregard of his duties,” but refused to get any more specific. Insiders muttered that Rattigan’s chief sin was that of being too good at his job, that the good press his decisions had been receiving had left Gould jealous. Just a couple of weeks before Rattigan’s firing, Commodore’s official magazine had published a lengthy interview with him, complete with his photo on the cover. To this Gould was reported to have taken grave exception. Yet Rattigan hardly comes across as a prima donna or a self-aggrandizer therein. On the contrary, he sounds serious, thoughtful, grounded, and very candid, explicitly rejecting the role of “media celebrity” enjoyed by Apple’s John Sculley, his former colleague at Pepsi: “When you have lost something in the range of $270 million in five quarters, I don’t think it’s time to be a media celebrity. I think it’s time to get back to your knitting and figure out how you’re going to get the company making money.” Nor does he overstate the extent of Commodore’s turnaround, much less take full credit for it, characterizing it as “tremendous improvement, but not an acceptable performance.” It seems hard to believe that Gould could be petty enough to object to such an interview as this one. But at least one more piece of circumstantial evidence exists that he did: Commodore Magazine‘s longtime editor Diane LeBold was forced out of the company on Rattigan’s heels, along with other real or perceived Rattigan loyalists. It made for one hell of a way to run a company.

True to form of being less of a pushover than Gould’s other executive lapdogs, Rattigan soon filed suit against Commodore for $9 million, for terminating his five-year employment contract four years early for no good reason. Commodore promptly counter-sued for $24 million, the whole ugly episode overshadowing the actual arrival of the Amiga 500 and 2000 in stores. After some five years of court battles, Rattigan would finally be awarded his $9 million — yes, every bit of it — just at a time when everything was starting to go sideways for Commodore and they could least afford to pay him.

With Rattigan now out of the picture — Gould had had him escorted off the campus by security guards, no less — Gould announced that he would be taking personal charge of day-to-day operations, a move that filled no one at the company other than his hand-picked circle of sycophants with any joy. But then, for Gould day-to-day oversight meant something different than it did for most people. He continued to live the lifestyle of the jet-setting super-rich, traveling the world — reportedly largely to dodge taxes — and conducting business, to whatever extent he did, by phone. Thus Commodore was not only under a cloud of rumor and gossip at this critical moment when these two critical new machines were being introduced, but they were also leaderless, their executive wings gutted and reeling from Gould’s purge and their ostensible new master who knew where. There was, needless to say, not much in the way of concerted promotion or messaging as the months marched on toward Christmas 1987, the big test of the Amiga 500.

While it didn’t abjectly fail that test, it didn’t really skate through with honors either. On the one hand, Amigas were selling again, and in better numbers than ever before. The narrative of the Amiga as a flop that was soon to be an orphan began to fade, and companies like Electronic Arts began to return to the platform, if not always as a target for first-run games at least as a consistent target for ports. WordPerfect even ported their industry-standard word processor to the Amiga. But on the other hand, the Amiga certainly wasn’t going to become a household name like the 64 anytime soon at this rate. In addition to the nearly complete lack of Commodore advertising, distribution remained a huge problem. Many people who might have found the Amiga very interesting literally never knew it existed, never saw an advertisement and never saw it in a store. Jack Tramiel’s decision to dump the 64 into mass-market channels like Sears and Toys “R” Us had been a breaking of his own word and a flagrant betrayal of his loyal dealers from which Commodore’s reputation had never entirely recovered. Yet it had also been key to the machine’s success; the 64 was available absolutely everywhere during its heyday, an inescapable presence to tempt plenty of people who would never think to walk into a dedicated computer store. Now, though, having laboriously and with very mixed results struggled to rebuild the dealer network that Tramiel had demolished, Commodore refused to do the same with the Amiga 500, even after some of those dealers had started to whisper through back channels that, really, it might be okay to offer some 500s through the mass market in the name of increasing brand awareness and corralling some new users who would quite likely end up coming to them for further hardware, software, and support anyway. But it didn’t happen, not in 1987, 1988, or the bulk of 1989.

The Amiga thus came to occupy an odd position on the American computing scene of the late 1980s, not quite a failure but never quite a full-fledged success either. Always the bridesmaid, never the bride; the talented actor never quite able to find her breakout role; pick your metaphor. Commodore blundered along, going through more of Irving Gould’s sock-puppet executives in the process. Max Toy, unfortunately named in light of the image that Commodore was still trying to shake, took over in October of 1987, to be replaced by Harold Copperman in July of 1989. Meanwhile the two Amiga models settled fairly comfortably into their roles.

Video production became the 2000’s particular strong suit. Amigas were soon regular workhorses on television series like Amazing Stories, Max Headroom, Lingo; on films like Prince of Darkness, Not Quite Human, Into the Homeland; on lots of commercials. If most of this stuff wasn’t exactly the pinnacle of cinematic art, it was certainly more Hollywood work than any other consumer-grade PC was getting. More important, and more inspiring, were the 2000s that found homes in small local newsrooms, on cable-access shows, and in small one- or two-person video-production studios. Just as the Macintosh had helped to democratize the means of production on paper via desktop publishing, the Amiga was now doing the same for the medium of video, complete with a new buzzword for the age: “desktop video.”

The strong suit of the Amiga 500, of course, was games. At first blush, the Amiga might seem a hard sell to game publishers. Even in 1988, after the 500 and 2000 had had some time to turn things around for the platform, a hit Amiga game might sell only 20,000 copies; a major blockbuster by the platform’s terms, 50,000. The installed base still wasn’t big enough to support much bigger numbers than these. An only modestly successful MS-DOS game, by contrast, might sell 50,000 copies, while some titles had reportedly hit 500,000 copies on the Commodore 64 alone. Yet, despite the raw numbers, many publishers discovered that the Amiga carried with it a sort of halo effect. Everyone seriously into computer games knew which platform had the best graphics and sound, which platform had the best games, even if some were reluctant to admit it openly. Publishers found that an Amiga game down-ported to other platforms carried with it a certain cachet inherited from its original version. Cinemaware, the premiere Amiga game developer and later publisher in North America, used the Amiga’s halo effect to particularly good commercial effect. All of their big releases were born, bred, and released first on the Amiga. They found that it made good commercial sense to do so, even if they ultimately sold far more copies to MS-DOS and Commodore 64 owners. While it’s true that Cinemaware could never have survived if the Amiga had been the only platform for which they made games, neither could they have made a name for themselves in the first place if the Amiga versions of their games hadn’t existed. Some of the same triangulations held sway, albeit to a lesser extent, among other publishers.

All told, the last three years of the 1980s were, relatively speaking, the best the Amiga would ever enjoy in North America. By the end of that period, with the 64 at last fading into obsolescence, the Amiga could boast of being the number two platform, behind only MS-DOS, for computer games in North America — a distant second, granted, but second nevertheless — while Commodore stood as the number three maker of PCs in North America in terms of units sold, behind only IBM and Apple. And Commodore was actually making money for most of this period, which was by no means always such a sure thing in other periods. But perhaps more important than numbers and marketshare was the sense of optimism. Every month seemed to bring some breakthrough program or technology, while every Christmas brought the hope that this would be the one where the Amiga finally broke into the public consciousness in a big way. To continue to be an Amiga loyalist in later years would require one to embrace Murphy’s Law as a life’s creed if one didn’t want to be positively smothered under all of the constant disappointments and broken promises that could make the platform seem cursed by some malicious higher power. But in these early, innocent times everything still seemed so possible, if only there would come the right advertising campaign, the right change in management at Commodore, the right hardware improvements.

But, ah, Commodore’s management… there lay the rub, even during these good years. Amiga owners watched with concern and then alarm as Apple and the makers of MS-DOS machines alike steadily improved their offerings whilst Commodore did nothing. In 1987, Apple debuted the Macintosh II, their first color model, with a palette of millions of colors to the Amiga’s 4096 and a hot new 16 MHz 68020 CPU inside. Yes, it cost several times the price of even the professional-grade Amiga 2000, and yes, 68020 or no, the Amiga could still smoke it for many animation tasks thanks to its custom chips. But then, even Apple’s prices always came down over time, and everyone knew that their hardware would only continue to improve. That same year, IBM introduced their new PS/2 line, and with it the new VGA graphics standard with about 262,000 colors on offer. More caveats applied, as Amiga fans were all too quick to point out, but the fact remained that the competition was improving by leaps and bounds while Commodore remained wedded to the same core chipset that they had purchased back in 1984. The Amiga 1000 had been a generation ahead of anything else on the market at the time of its release, but, unfortunately, generations aren’t so long in the world of computers. Gould and his cronies seemed unconcerned about or, still more damningly, blissfully unaware of the competition that was beginning to match and surpass the Amiga in various ways. In 1989, IBM spent 10.9 percent of their gross revenue on R&D, Apple 6.7 percent. And Commodore? 1.7 percent. The one area where Commodore did rank among the biggest spenders in the industry was in executive compensation, particularly the salary of one Irving Gould.


For the 1989 Christmas season, Commodore launched what would prove to be their first and last major mainstream advertising campaign for the Amiga 500. The $20 million campaign featured television spots produced by no less leading lights than Steven Spielberg’s Amblin Entertainment and George Lucas’s Lucasfilm. The slogan was “Amiga: The Computer for the Creative Mind.” The most lavish of the spots featured cameos by a baffling grab bag of minor celebrities, including Tommy Lasorda, Tip O’Neill, the Pointer Sisters, Burt Bacharach, Little Richard, and astronauts Buzz Aldrin, Gordon Cooper, and Scott Carpenter. Commodore’s advertising agency announced confidently that 92 percent of Americans would see an Amiga commercial an average of twenty times during November and December. Commodore would even begin selling 500s through mass-market merchandisers at last, albeit in a limited way, going through Sears and Service Merchandise alone. The campaign was hyped in the Amiga press as a last all-out effort to make that ever-elusive big breakthrough in North America. Sure, it was something they really needed to have done back in 1987, when the 500 first debuted, but at least they were doing it now. That was something, right? Right? In the end, it proved a heartbreaker of the sort with which Amiga fans would grow all too familiar over the years to come: it had no appreciable effect whatsoever. And with that Commodore slipped out of the mainstream American consciousness along with the decade with which their computers would always be identified.

The next year the first of a new generation of unprecedentedly ambitious games arrived — games like Wing Commander, Ultima VI, Railroad Tycoon — that looked, sounded, and played better on MS-DOS machines than they did on Amigas, thanks to the ever-improving graphics cards, sound cards, and new 32-bit 80386 processors in those heretofore bland beige boxes. Cinemaware that same year released Wings, the last of their big Amiga showcases, and then quietly died. The Amiga’s halo effect was no more. Just like that, an era ended.

And yet… well, here’s where things get a little confusing. As the Amiga was drying up as a gaming platform in North America, it was in many ways just getting started in Europe, with most of the classics still to come. Let’s rewind and try to understand how this parallel history came to be.

Commodore had always been extremely strong in Europe, going all the way back to their days as a maker of calculators. Their first full-fledged computer, the PET, had been little more than a blip on the radar in North America in comparison to its competitors the Radio Shack TRS-80 and the Apple II, yet it had fostered a successful and respected line of business computers across the pond. Commodore’s most consistently strong markets then would also prove the strongest of their twilight years: Britain and, especially, West Germany. Both operations were granted much more autonomy than the North American operation, and were staffed by smart people who were much better at selling Commodore’s American computers than Commodore’s Americans were. Germans in particular developed a special affinity for the Commodore brand, one that was virtually free of the home-computer/business-computer dichotomy that Commodore twisted themselves into knots trying to navigate in the United States. In Germany a good home computer was simply a good home computer, and if the same company happened to offer a good business computer, well, that was fine too.

batmanpack

When Commodore’s European leadership looked to the new Amiga 500, they saw a machine sufficient to make the traditional videogame demographic of teenage boys, who were currently snatching up Commodore 64s and Sinclair Spectrums, positively salivate. They unapologetically marketed it on that basis. Knowing what their buyers really wanted the machine for, they quite early on took to bundling together special packages, usually just in time for Christmas, that combined a 500 with a few of the latest hot games. A particular home run was 1989’s so-called “Batman Pack,” which included the game based on the hit Batman movie, a fresh new arcade conversion called The New Zealand Story, the graphically stunning casual flight simulator F/A-18 Interceptor, and, since this was an Amiga after all, the platform’s signature application, Deluxe Paint II. Deluxe Paint aside, there was no talk of video production or productivity of any other stripe, no mention of the Amiga’s groundbreaking multitasking operating system, no navel-gazing discussions of the platform’s place in the multimedia zeitgeist. Teenage boys didn’t want any of that. What they wanted was great games with great graphics, and that’s exactly what Commodore’s European operations gave them. You were just buying a fun computer, a game machine, so you didn’t need to go through a dealer. From the beginning, the Amiga 500 was widely available at all of the glossy electronics stores on European High Streets. The West German operation went even further: they started selling Amigas through grocery stores. Buy an Amiga 500, hook it up to a television, pop in a disk, turn it on, and start playing.

The British and especially the Germans took to the Amiga 500 in numbers that Commodore’s North American executives could only dream of. By early 1988, Commodore could announce that they had sold 500,000 Amigas worldwide, a strong turnaround for a marque that had been all but left for dead a year before. A rather astonishing 200,000 of those machines, 40 percent of the total, had been sold in West Germany alone; Britain accounted for another 70,000. Even now, with the Christmas season behind them, Commodore West Germany was selling a steady 4000 Amiga 500s every week. A few months later came the simultaneously impressive and depressing news that the total market for Amiga hardware and software in West Germany (population 60 million) was now worth more than that for the United States (population 240 million). And where Germany led, the rest of Europe followed. Eighteen months later, with worldwide Amiga sales closing in on 1.5 million, it was the number one gaming computer in Europe, a position it would continue to enjoy for several years to come. Just about to begin its fade from prominence as a game machine in the United States, in Europe the Amiga’s best years and best games were still in front of it, as bedroom coders learned to coax performance out of the hardware of which its designers could hardly have conceived. The old Boing demo, once so stunning that crowds of trade-show attendees had peeked suspiciously under tables looking for the workstation-class machine that was really generating that animation, already looked singularly unimpressive. The story of the Amiga 500 in Europe was, in other words, the story of the Commodore 64 happening all over again. Commodore was now making the vast majority of their money in Europe, the North American operation a perpetual weak sister.

When journalists for the Amiga trade press in North America visited Europe, they were astounded. Here was the mainstream saturation that they had only been able to fantasize about back home. A report from a correspondent visiting a typical department store in Cologne must have read to American readers like a dispatch from Wonderland.

I came across a computerized book listing that was running on an Amiga 500. As I approached the computer department, I was greeted by a stack of Amiga 500s. I could not believe the assortment of Amiga titles on the book rack (hardcover ones, too!). I found two aisles full of Amiga software, consisting mostly of games. The Amiga selection was more than that of any other computer.

In a sense, it was just a reversion to the status quo. After all, prior to the introduction of the VIC-20 in 1981, Commodore’s income had been similarly unevenly distributed between the continents. Seen in this light, it’s the high times of the 1980s that are the anomaly, when American buyers flocked to the VIC-20 and the 64 and for a time made what had always been fundamentally a European brand — although, paradoxically, a European brand engineered and steered from the United States — into an intercontinental phenomenon. Not that that was of much comfort to the succession of executives who came and went from Irving Gould’s hotseat, fired one after another for their failure to make North American sales look as good as European sales.

But I did promise you 68000 Wars in the title of this article, didn’t I? So where, you might well be wondering, was the Amiga’s arch-rival the Atari ST in all this? Well, in North America it was a fairly negligible factor, although Atari would continue to sell their machine there almost as long as Commodore would the Amiga. The hype around the ST had dissipated quickly with the revelation in late 1986 that Atari really wasn’t selling anywhere near as many of them as Jack Tramiel liked to let on, and the Amiga 500, so obviously audiovisually superior and now much closer in price, soon proved a deadly foe indeed. The ST retained its small legion of loyal users: desktop publishers unwilling to splurge on a Macintosh, who took full advantage of its rock-solid monochrome high-resolution screen and Atari’s inexpensive laser printer, thereby truly making the ST live up to its old “Jackintosh” nickname; musicians, both amateur and professional, who loved its built-in MIDI port; programmers and hardware hackers who favored its simple, straightforward design over the Amiga’s more baroque approach; people who needed lots and lots of memory for one reason or another, on which terms Atari always offered the best deal in town (they released 2 MB and 4 MB ST models as early as 1987, when figures like that were all but inconceivable); inveterate Commodore haters and/or Atari lovers who bought it for the badge on its front. Still, there was little doubt which platform had won the 68000 Wars in North America. In the wake of the Amiga 500’s release, Atari began increasingly to turn to other ways of making money: buying the Federated chain of consumer-electronics stores; capitalizing on nostalgia for the glory days of the Atari VCS by continuing to sell both the old hardware and the cartridges to run on it; wresting away from Epyx a handheld gaming machine, the first of its kind, that was ironically designed by members of the old Amiga, Incorporated, team. When all else failed, there was always Jack Tramiel’s old hobby of lawsuits, of which he launched quite a few, most notably against the former owners of Federated for overstating their company’s value and against the new kid on the block in console gaming, Nintendo, for their alleged anti-competitive practices.

In Europe, the ST also came out second best to the Amiga, but the race was a much closer one for a while. Along with their love for all things Commodore, Germans found that they could also make room in their hearts for the Atari ST. It found a home in many German markets it never came close to cracking in the United States, being regarded as a perfectly respectable business computer there for quite some time. It also continued to do fairly well with gamers, thanks to Atari’s pricing strategies that always seemed to keep its low-end model just that little bit cheaper than the Amiga 500, enough to be a difference-maker for some buyers. When the Amiga became the biggest gaming computer in Europe, it was the Atari ST that slipped into the second spot. It would take the much more expensive MS-DOS machines some years yet to overtake these two 68000-based rivals. The economic chaos brought on by the reunification of West and East Germany, which caused many consumers there to tighten their wallets, only helped their cause, as did the millions of new price-conscious buyers who were suddenly scrambling for a piece of that Western computing action following the fall of the Iron Curtain.

The story of the Amiga, and to some extent also that of the ST, is often framed as a narrative of frustration, of brilliance that never got its due. There are some good reasons for that, but it can also be a myopic, America-centric view, ignoring as it does a veritable generation of youngsters on the other side of the Atlantic who grew up knowing these two platforms very well indeed. When I was writing my book about the Amiga, I couldn’t help but note the markedly different responses I got from friends in Europe and the United States when I told them about the project. Most Americans have no idea what an Amiga is (“Omega?”); most Europeans of a certain age remember it all too well, flashing me smiles redolent of nostalgia for afternoons spent before the television with their mates, when the summer seemed endless and the possibilities limitless. Instead of lamenting might-have-beens too much more, I expect to spend quite some articles over the next few years talking about the Amiga’s innovations and successes — and, yes, I’ll also have more to say about the Amiga’s perpetually overlooked little frenemy the Atari ST as well. Whether you grew up with one of these machines or you too aren’t quite sure yet what to make of this whole “Omega” thing, I hope you’ll stick around. Some amazing stuff is in store.

(Sources: Invaluable as always for these articles was Brian Bagnall’s book On the Edge: The Spectacular Rise and Fall of Commodore. I can’t wait for the better, longer version. The long-running “Roomers” column in Amazing Computing is my go-to source for a month-by-month chronology of developments on the Amiga scene, and the source of most of the nit-picky factoids in this article. The issues of Amazing used include: March 1987, June 1987, July 1987, August 1987, October 1987, November 1987, December 1987, February 1988, April 1988, May 1988, June 1988, July 1988, August 1988, September 1988, November 1988, December 1988, January 1989, February 1989, March 1989, April 1989, May 1989, June 1989, July 1989, August 1989, September 1989, October 1989, November 1989, December 1989, January 1990, April 1990, May 1990, June 1990, February 1991, March 1991, April 1991, May 1991, December 1991. Commodore Magazine‘s fateful interview with Thomas Rattigan appeared in the May 1987 issue. Other sources include Retro Gamer 39 and of course my own book The Future Was Here. Hey, it’s not every day a writer gets to cite himself…)

 
85 Comments

Posted by on November 27, 2015 in Digital Antiquaria, Interactive Fiction

 

Tags: , , , ,

Cliff Johnson’s Fool’s Errand

The Fool's Errand

One sunny day, a light-hearted fool strolled along a hilly path, whistling a merry tune. A long wooden pole was slung over his shoulder and attached to it was a cloth bundle which carried his life’s possessions.

“What a marvelous afternoon!” he exclaimed to no one in particular, pausing to appreciate the lovely countryside.

Soon the trees parted and the path led to a small clearing, ending abruptly at the edge of a treacherous cliff. But the fool was undaunted and kept at his swift pace, steadily approaching the sheer drop.

“Your folly is most curious,” a voice boomed. “Have you no fear of death?”

Just as one leg dangled over the side of the cliff, the fool hesitated.

“Who dares to interrupt my errand?” he demanded impatiently.

“I dare,” the bright yellow sun replied.

“Well, then,” the fool considered, “I seek the fourteen treasures of the world and I am told that a man who strays from his path is lost.”

“That may well be true,” spoke the sun, “but I fear that you are already lost. Take this map as my gift. It will aid you in your quest.”

And in a flash of light, an aged parchment appeared at his feet.

“At last! A path to follow!” cried the fool, happily taking the map.

“Perhaps,” the sun murmured, “yet things are never as simple as they may seem.”

But the fool had already run back down the hill and did not hear the sun’s parting words.

Long before “game developer” was recognized by universities as a legitimate career to which one could aspire, people from a dizzying array of backgrounds stumbled into the field. Plenty were the programmers and technologists that you might expect, but plenty of others came from places much farther afield. Infocom, just to take one example, included among their ranks a construction engineer, a journalist, a science-fiction author, a medical doctor, and two lost literature majors, while Sierra’s two most prominent designers were a former housewife and a former jazz musician. Other companies could boast architects, psychologists, rocket scientists, poets, and plain old high-school students. Taken in this light, the story of Cliff Johnson, a filmmaker who decided to start making computer games instead, may not seem quite so atypical. The first game he made, however, is anything but typical. The Fool’s Errand is one of the precious gems of its era, despite — because of? — having been made by a fellow with little intrinsic interest in computers and even less in playing games on them. For an industry that has so often struggled to get beyond a handful of fictional and mechanical genres inspired by a tiny sliver of the rich cultural tapestry of the human race, it’s yet one more reminder of just what a good thing a little diversity can be.

Born in 1953 in Connecticut as the only child of a pair of schoolteachers, Cliff Johnson manifested creativity and curiosity almost from the moment he arrived. As a boy, he spent hours tramping around the woods and dales that surrounded his family home. He loved maps, loved to imagine himself an explorer on the hunt for hidden pirate treasure (“X marks the spot!”). When not roaming the woods, he loved making things with his own hands, whether that meant playing with an erector set or spending long afternoons in the basement doing home-grown chemistry experiments. Gunpowder was easy, the formula printed in lots of places. Chlorine gas proved more tricky, both to make and to get rid of; thankfully the basement had some windows just below its ceiling that helped Cliff get rid of the evidence before Mom and Dad made it home.

Any possibility of Cliff becoming a cartographer or a scientist was, however, derailed on the day that he saw the classic horror flick House on Haunted Hill, starring no less an icon than Vincent Price. Like millions of other kids across the country, he became a B-movie fanatic, a devotee of all things monstrous, horrific, and/or alien. But unlike most fans, Cliff’s personality demanded that he do more than passively consume his obsession. Getting his hands on a Super 8 camera, he started making his own little movies. His technique evolved with impressive speed; soon he was doing stop-motion with live actors to craft his special-effects sequences, a tricky proposition even for professionals. As he got older and his teenage tastes, relatively speaking, matured, he discovered the allure of camp, moving from pulpy horror to slapstick comedy. His magnum opus, shown in his high-school auditorium on three glorious evenings, was called The Return of the Freshman. (It was, naturally, a sequel, and one with a name that beat George Lucas to the punch by thirteen years at that.)

Cliff Johnson

The summer before, while The Return of the Freshman was still in its planning stages, Cliff and his parents had visited Disneyland. He was no stranger to amusement parks, but knew them as the seedy, vaguely disreputable places they generally were at that time, echoes of the still older traveling circuses. Disneyland, however, was something different. In addition to being clean and wholesome and family-friendly, care had been taken with their rides and other attractions to turn them into real experiences. Cliff was particularly entranced by the lovingly sculpted animatronic characters who actually moved. “I could do that!” was his boyish response; after all, he’d gotten quite good at sculpting monsters and props for his movies. Back home, the local amusement park, a run-down place called Lake Compounce, had a ride called Laff-in-the-Dark that had fallen on hard times. Once full of chills and thrills, its bits and pieces had broken down and been removed one by one, so that now it was largely just a ride through a pitch-black tunnel. Cliff asked the Norton family that ran the park for permission to walk through the ride while it was closed, measuring its every dimension, sketching its every curve and straightaway. He and his girlfriend Janice then made models and sketches illustrating how they thought the ride could be restored to its former glory. Showing an audacity that would serve him well throughout his life, Cliff formally proposed their services to the Nortons. For $1000, they would bring a little taste of Disneyland to Lake Compounce. The Norton family agreed, and thus, between shoots for The Return of the Freshman, Cliff along with cast and crew and Janice built monsters and lights and installed them in the ride. The Norton patriarch, also the mayor of the city of Bristol at that time, was so thrilled with Cliff’s work that he agreed to appear in his movie. He played himself, looking out of his window at City Hall at a flying saucer whizzing by. (“What a sport!” remarks Cliff today.)

Cliff did such a good job on that hometown ride that word got out on the amusement-park circuit about this talented teenager who, being a teenager, worked pretty cheap. He spent the next few years traveling the country as far from home as Colorado and California, making monsters for low-rent amusement parks and saving money for his dream of attending film school right in the heart of Hollywood, at the University of Southern California.

He finally began USC Film School in 1974. University worked on him just as it ideally ought to, opening new intellectual vistas. Having entered an aficionado of monster movies and Disney, perhaps primed for a career in Hollywood special effects — and at a good time too, what with George Lucas and Steven Spielberg just around the corner — he discovered there a new world of film, film made as art for art’s sake. More specifically, he discovered avant-garde animation. Working under Professor Gene Coe, a semi-legendary figure at USC, he made a number of experimental films that did very well on the festival circuit, earning several prizes. He still remembers his years at USC as some of the best and most artistically productive of his life.

But then, in 1979, he was suddenly finished, with a freshly minted Master’s Degree in his hand and no clear idea of what to do next. Virtually the entire avant-garde animation industry, to the extent that such a thing existed at all, existed in Canada and Europe rather than the United States. Cliff couldn’t see himself moving there, but he also no longer had any desire to become a part of the mainstream Hollywood machine that surrounded him in Southern California. So, he became an entrepreneur, an all-purpose filmmaker-for-hire who served a client list consisting mostly of big corporations that needed films made for practical in-house purposes and didn’t want to pay too much for the service. Cliff, by now an accomplished animator as well as cameraman, could do entire films virtually by himself, adding charts and graphics and titles and cartoons and whatever else was needed to his live-action footage to meet his clients’ needs. He did a large number of training films for Southern California Edison in particular, producing, as he would later put it, “such notable works as Heating, Air Conditioning and Ventilation and other film classics.” Yes, it was pretty boring stuff, but it was a pretty decent living.

And yet the fact remained that his new life was as much of a creative comedown from his art-for-art’s-sake days at USC as it was a financial windfall. An artistically stymied Cliff thus began to look around for diversions from his dull working life. Three influences in particular came together at this time to start him in earnest down the road toward The Fool’s Errand.

First, there were his parties. As far back as his teenage years, he had loved to throw elaborate multimedia parties — multimedia in the old sense of the word, implying the blending of different sorts of media in a physical rather than a digital space. He would fill the rooms of a house with lights, sound, music, film, figures, and props, and arrange his guests’ progress through the house so as to tell a little story or illustrate a theme. Soon he began adding an interactive element, a little puzzle or mystery for his guest to solve. These mysteries were, he notes wryly today, “more jobs for Watson than Sherlock,” but, despite or because of their simplicity, his guests really took to them. He kept throwing the parties, growing ever more elaborate all the while, through his time at USC and especially while working as a filmmaker-for-hire, when he desperately needed the creative outlet they provided.

Next, there was Masquerade. Soon after leaving USC, Cliff became one of countless thousands of people all over the world to be fascinated by a little children’s picture book called Masquerade. Written by a reclusive English painter named Kit Williams, it tells the story of a hare who carries a treasure from the Moon to the Sun, with fifteen of Williams’s intricate paintings as illustrations. What so enthralled Cliff and all those others, however, was the end of the book, which reveals that the hare has lost his treasure, and that it’s up to you, the reader, to find from clues scattered through the book where it now lies in the real world. Masquerade became an international phenomenon that obsessed treasure hunters and puzzle solvers for more than two-and-a-half years, selling nearly 2 million books in the process. Cliff, who didn’t personally enjoy solving puzzles all that much, was perhaps less obsessed than many of those buyers, but he found the idea of Masquerade, of a book that could stand alone but could also serve as a grand puzzle, endlessly intriguing as something he might create. [1]For better and often for worse, Masquerade‘s connection to computer gaming extends far beyond the story of Cliff Johnson. The man who first “solved” the riddle and was awarded the hare in March of 1982, one Dugald Thompson, did so, it was revealed years later, largely by cheating. A friend of his had as his current girlfriend a former girlfriend of Kit Williams. While Kit had never outright told her where the treasure — a golden hare sculpted by Kit himself — lay, he had inadvertently dropped enough clues that she could point Thompson in the right direction.

After he was awarded the prize, Thompson formed a company called Haresoft to release an unspeakably horrible computer game called Hareraiser that supposedly contained further clues pointing to a new location of the golden hare. If it did, nobody ever worked them out. More likely, the game was yet another instance of fraud committed by Thompson, designed to make a quick buck from the players that it sent off on a wild goose chase after its nonexistent clues. It justly bombed, Haresoft went into liquidation, and Thompson was forced by his creditors to sell the golden hare at auction.

Long before those events, Masquerade had inspired other British game developers to embed real-world treasure hunts and other puzzles in their own games, perhaps most notably the hunt for the “Golden Sundial of Pi” buried in the Sussex Downs by Mel Croucher and Christian Penfold of Automata. All told, that golden hare had one hell of a long reach.

And finally, there was the tarot deck. Not remotely of a spiritual or supernatural bent, Cliff nevertheless came upon a lovely Rider-Waite tarot deck and found himself fascinated with the characters and ideas represented there.

A section of the Fool's Errand treasure map.

A section of the Fool’s Errand treasure map.

All of these influences merged together in a 1981 project that would prove to be a non-computerized prototype of the final version of The Fool’s Errand that was still six years in the future. Wanting to create another fun and unique experience for his friends as a Christmas gift, like all those themed parties, Cliff decided to write, just for them, a little book much like Masquerade, telling the story of a Fool who wanders through a fairy-tale land based loosely on the world of the tarot. Filling the back of the book, after the 21-page story, were another 14 pages containing pieces of a treasure map; shades of Cliff’s childhood roaming the Connecticut woodlands dreaming of pirate maps and buried treasure. The player should cut out and assemble the pieces using clues from the story, which was divided into 81 sections, each relating to one piece of the map. Accomplishing that got you to an endgame, a crossword requiring you to correctly place the names of 13 treasures mentioned in the story to decode a final message: “Merry Christmas!” (Those of you who’ve already played The Fool’s Errand on a computer will recognize all of this as essentially the second half of that game, the part you embark on after completing all of the initial puzzles.) Unlike Masquerade, over which so many puzzlers fretted for years, The Fool’s Errand was designed to be a pleasant challenge but not an exhausting one, solvable in a single long, lazy holiday afternoon. He was thus disappointed when, out of the dozens of people to whom he sent the book, only three actually solved it. The lesson he took away was that, while he believed his friends to be a pretty intelligent group on the whole, this sort of complex puzzle required a special kind of intelligence — or, perhaps better said, a special kind of personality — that made it a poor fit for most of them. He put his storybook back on the shelf, and returned to the themed parties that were so much better received.

But Cliff’s reputation among his friends as a devious mind was now established, and would lead to his introduction to the brave new world of computerized puzzle design. One of his friends, Allen Pinero, came to him with a proposition. Pinero had jumped onto the home-computer bandwagon early, purchasing an Apple II, and had devised a unique text-adventure engine that let the player control two characters at once through a split-screen view. With the core programming in place, though, he was having some trouble devising a plot and puzzles — in short, something for the characters to actually do. Despite knowing nothing about the state of the art in home computers, much less adventure games — he’d never played or even seen one in his life before Pinero showed him a few of Scott Adams’s to prime his pump — Cliff came up with a plot that tangled together several stories from Greek mythology; the two characters under the player’s control became none other than Jason and Hercules. He also devised a batch of puzzles that often required the characters to work together from different rooms, and to illustrate their adventures he drew pictures freehand, which Pinero than translated into vector graphics on the screen. Released in late 1982 by Scott Adams’s Adventure International, Labyrinth of Crete, like most Adventure International games by that time, made little impact in either the trade press or at retail, although it did sell well enough through their mail-order catalogs that they funded ports to the Atari 8-bits and the Commodore 64.

For Cliff it was a fun little experience in its way, but also a frustrating one. It’s safe to say that it didn’t ignite any dormant passion for computers or computer games. He chafed constantly at the limitations of the two-word parser and the primitive world model. It often seemed that nine out of ten ideas he proposed were greeted by Pinero with a “Sorry, can’t do that,” followed by some esoteric technical reasoning he didn’t really understand and didn’t really care to. Pinero’s Apple II itself remained to him an incomprehensible and irascible black (or rather beige) box, all strident squawks and ugly colors. He was, needless to say, completely baffled by Pinero’s efforts to program the thing. If anything, the experience only confirmed his dislike of computers. He certainly didn’t rush out to buy one himself. He and Pinero did discuss doing another game together, but Pinero in particular was feeling completely burnt-out by all the work that had gone into the first — far more work than he had ever imagined it would be.

Cliff’s opinion of computers didn’t change until one day in late 1984 when he idly wandered into a store selling the Apple Macintosh and promptly fell in love. Ironically, he had long since shot one of his corporate films inside Xerox’s famed Palo Alto Research Center, the very place where most of the ideas behind the Macintosh were invented. For whatever reason, that experience had left little impression on him, done nothing to alter his opinion of computers as balky, unpleasant contraptions. The Macintosh itself, however, just did it for him right away. He loved its friendly demeanor, loved the simplicity of its point-and-click operating system, loved the elegance of its crisp black-and-white display in contrast to the ugly blotches of pixelated color he remembered on the screen of Pinero’s Apple II. He became just another of the thousands of creative souls, many of them far removed from your typical computer nerd, who saw magic possibility in “the computer for the rest of us.” He simply had to have one. A few thousand dollars later, he was armed with a shiny new 512 K “Fat Mac” with all the bells and whistles, purchased with vague justifications that it would be useful for his business.

Cliff was perhaps unusually receptive to the idea of a life-changing event at about this point. His work as a filmmaker was more stultifying than ever. Even a chance to do animations for a brief-lived children’s television series called Out of Control, which was broadcast by the Nickelodeon cable channel as their first original series ever, hadn’t lifted his malaise. So, yes, he was looking for a way out even before he wandered into that store. Soon his new Macintosh would provide it.

He first programmed his Macintosh by writing macros for keeping track of his business finances in the Microsoft Multiplan spreadsheet. His programming began in earnest, however, only when a friend of his, knowing he was very enamored with his new computer, gifted him with a copy of Microsoft BASIC for the machine. It was, surprisingly for this inveterate computer hater, not quite Cliff’s first exposure to the language. The only computerized gadget he had ever owned prior to purchasing his Macintosh had been an Atari VCS game console, for which he had received, again as a gift, Atari’s “BASIC Programming” cartridge. Delivered as a hedge to fretful parents thinking of replacing Junior’s game console with a real home computer, it was a shockingly primitive creation even by the standards of its day. Programs, which had to be laboriously entered using Atari’s infuriating “keyboard controllers,” could be all of 63 characters in length, and couldn’t be saved. But despite it all, Cliff had found the experience of programming vaguely interesting, enough to devote an afternoon or two to, as he puts it, “getting a tiny square to move around the screen.” Now, with this latest gift of a BASIC, those memories came back, and he started learning to program his Macintosh with real enthusiasm. The natural question then became what to do with his burgeoning skills.

Cliff happened to be acquainted with Philip Proctor and Peter Bergman of the legendary comedy troupe The Firesign Theatre. For a time, they all discussed bringing Firesign’s most famous character, the hard-boiled detective Nick Danger, to interactive life via some sort of adventure game. Yet that puzzle-filled storybook that Cliff had made several years before, the one that had left him feeling like it was a genuinely great idea that just hadn’t found the right audience, kept popping into his head. People who played on computers at that time — yes, even “computers for the rest of us” like the Macintosh — tended to be the sort of people who noticed the little things, who were intrigued by them. What might they make of a computerized puzzle book? Married by this point, he told his wife Kathy one day that he had to drop the filmmaking business, had to drop everything and find out. With Kathy still attending university, they would just have to live on savings and credit cards while he saw it through. Thus was The Fool’s Errand reborn as a computer game.

Let’s be clear: it was a crazy thing to do. Having programmed for a bare handful of months, Cliff proposed programming a commercial-quality game. Having never seriously played a computer game in his life, he proposed designing one. Knowing no one in and nothing about the games industry, he proposed selling his creation at some point to a publisher. He didn’t even like to solve puzzles, not really. His consolation, if he had only known it, might have been that he was mirroring to an uncanny degree Kit Williams, the man who had set him down this path in the first place. Kit also had never evinced the slightest interest in actually solving puzzles, had conceived the grand puzzle that was Masquerade strictly as a gimmick to get people to really look at his artwork and — let’s be honest here — to sell books.

Cliff started, as you’d expect, with his old storybook itself. His original story of the Fool’s wanderings through a tarot-inspired fairy-tale land went into the computer version almost verbatim. The patchwork treasure map also went in, consisting of the same 81 tiles, each linked to a section of the story; it would be much easier to unscramble on the monitor screen, requiring only mouse clicks rather than scissors and glue. And the crossword full of treasures, your reward for completing the map, remained as the final puzzle. But fleshing out this spine, often called today the “meta-puzzle” of the game, would be a collection of other, smaller puzzles that were new to the computer version. Entering each treasure in the final puzzle, for instance, would require not just that you figure out what that treasure should be from the story but that you solve another set-piece puzzle as well. And most of the story itself would be hidden from you at the beginning; opening up the other sections for reading would require, you guessed it, solving puzzles.

A friend of Cliff’s used to have a subscription to Games magazine, and would loan him each issue after he was finished with it, by which time all of the puzzles were marked up with his solutions. Cliff didn’t care. He wasn’t so interested in solving the puzzles, which took time he didn’t feel he could spare anyway, as he was in looking at how they were put together, enjoying them almost as one might a work of art. Although he didn’t realize it at the time, he was already thinking like a game designer. Now that subconscious preparation was about to serve him well.

The individual puzzles he crafted for his game are multifarious, many of them old favorites of the sort that he had studied in those magazines: word searches, anagrams, cryptograms, crosswords, mazes, jigsaws. Others, however, are delightfully original, like the tarot-inspired card game that requires you to first figure out what the rules are before you can concentrate on actually winning the thing. Some, like the word-concatenation puzzles, are almost naive outgrowths of Cliff’s early experiments with BASIC. A few, the least satisfying in my opinion, are essentially action games, dependent as much on reflexes as smarts.

Through the early months, Cliff was writing each puzzle as its own self-contained BASIC program, unclear exactly how he would tie them together to create a unified experience. Most of his problems came down to Microsoft BASIC itself. Because it was interpreted rather than compiled, it was painfully slow. Even worse, its programs required that the end user also have Microsoft BASIC in order to run them. In short, it was an environment for casual hobbyists and students of programming, not for the creation of a full-fledged commercial game. About a year after he’d first bought his Macintosh, a life-saver arrived in the form of ZBASIC, a compiled version of the language whose programs could run on any Macintosh, and at several times the speed of the Microsoft version at that. There were unfortunately enough syntactical differences between the two dialects that Cliff had to spend quite some time porting his code, but he ended up with a much more powerful and flexible language that was up to the task of implementing The Fool’s Errand.

Very much the amateur, self-taught programmer, Cliff’s code was, as a few technical friends told him at the time and as he freely admits today, neither terribly efficient nor terribly well-structured. Yet it had a couple of overriding virtues: it worked, and Cliff at least understood how it worked. Throughout the development of The Fool’s Errand, he constantly shared his puzzles in progress with his wife, with his old friend and Labyrinth of Crete partner Allen Pinero, and with another old friend, David Wood. Still, Cliff remained haunted by a “morbid pessimism” that at some point the whole house of cards, built from dozens of little BASIC programs all piled atop and beside one another, would collapse into hopeless chaos.

But it didn’t happen, and by the end of 1986 he had something complete enough to start shopping to publishers. Cliff still knew next to nothing about the games industry, but once more that old audacity, that willingness to just call his supposed betters and ask for whatever it was he wanted, served him well. A few publishers showed serious interest, despite the fact that the Macintosh market was still quite a minor one when it came to games. He met with Activision, publisher of what remains to this day the only computer game to have ever really captured Cliff’s interest as a player, the casual Mahjong puzzler Shanghai. They were quite willing to sign him, but the royalty they offered seemed rather paltry and, even worse, they insisted that he sign over to them his copyright. If there was one thing Cliff’s years in and around Hollywood had taught him you should never do, it was that. So he ended up signing instead with a young Macintosh-centric publisher called Miles Computing. Tiny though they were by the standards of the industry at large, they had already made a decent name for themselves in Macintosh circles with games like Harrier Strike Mission, which as the platform’s first available flight simulator had done very well for itself, and a line of clip-art disks for desktop publishers. They offered a much better royalty than Activision, were willing to let him keep his copyright, and were based right there in Southern California.

What Miles wasn’t terribly good at doing, Cliff soon learned to his dismay, was actually selling software that didn’t spontaneously sell itself. Released at last in April of 1987 with absolutely no promotion, The Fool’s Errand sank without a trace. One or two reviews buried deep inside magazines, lukewarm and noncommittal, became the full extent of its press presence. Cliff was left in an uncomfortable limbo, unsure what to do with himself next. His savings were exhausted, his credit-card debt was now approaching $50,000, and his royalties were so minimal as to be virtually nonexistent. He wasn’t eager to return to his old business of filmmaker-for-hire, and wasn’t sure he could anyway; once you fall out of people’s Rolodexes in Hollywood it’s damnably hard to get yourself back in. But, based on the evidence so far, this computer-game thing wasn’t exactly proving to be a financial winner either. The name of his game was now seeming sadly apropos. Making The Fool’s Errand, it seemed, had itself been a fool’s errand.

Cliff Johnson, 1987

The game’s life preserver, and thus Cliff’s as well, came in the form of a superlative feature review (“5 Mice!”) written by the prominent Macintosh pundit and columnist Neil Shapiro for the July 1988 issue of MacUser. Shapiro was the first reviewer to take the time to properly dig into the game, to understand what it was and what it was doing. He liked what he saw. In fact, he really liked what he saw. “Cliff Johnson has taken computer gaming, turned it inside-out and upside-down, and redefined the state of the art,” he wrote. He continued to champion the game relentlessly over the months that followed. The floodgates opened; The Fool’s Errand became a hit. A suddenly much more enthusiastic Miles Computing belatedly funded ports to the Commodore Amiga, the Atari ST, and MS-DOS. Cliff, who had nothing to do with programming those versions, was never happy with the way they looked or played. He considers them “Bizarro World” versions of his game, ugly, simplified, and buggy to boot. It was a long, not entirely successful struggle for him just to keep the worst of the porters’ razzle-dazzle videogame flourishes out of the end results. Still, in combination they sold far more copies than the Macintosh original. Total sales of The Fool’s Errand reached 100,000 copies by the end of 1989, perhaps not quite a blockbuster by the standards of the big boys but by far the biggest hit that little Miles Computing had ever enjoyed. Certainly it was more than enough to let Cliff pay off his credit cards and remain a game developer. We’ll be continuing to follow him in his new career in future articles.

For now, though, let’s talk about The Fool’s Errand itself just a little bit more. It’s one of those singular works that defies (transcends?) the conventional wisdom — including plenty of the wisdom that I spout routinely right here on this blog. Having chided people from Scott Adams to Ken Williams for refusing to engage with the games made by others outside their companies, I must admit that Cliff Johnson didn’t know a thing about other computer games at the time he wrote The Fool’s Errand, and never bothered to learn — and yet his game turned out brilliantly. Having harped endlessly on the importance of testing and player feedback, I must admit that The Fool’s Errand was seriously played by just three people not named Cliff Johnson prior to its release — and yet, again, his game turned out superbly, and about as bug-free as a game can be to boot. What is there to say, other than don’t try this at home, kids?

In his Mac User review, Neil Shapiro rather brilliantly described The Fool’s Errand as a “whole buffalo” game. Everything you see on the screen is important, nothing extraneous or inexplicable. When you first start the game, it’s both underwhelming and a little baffling, nothing more than a handful of puzzles — most of them fairly trivial — and a few scattered fragments of a story that doesn’t make much sense. And so you shrug your shoulders and have a go at one of the puzzles, maybe starting with something simple like the word search for names of countries. Slowly you begin to peel back layer after layer of the onion. Are certain words in the story printed in boldface? It’s not just for aesthetic effect; there’s a reason for it that will become clear in time. Have no idea what to do with this scrambled map? Work on other, simpler problems for a while and insight might just come. Finished all of the puzzles from the initial menus and think you’re about to win? You’re about halfway actually, with the tastiest parts of the onion still waiting for you. I can’t emphasize enough what a wonderfully intriguing experience solving The Fool’s Errand becomes. My wife Dorte and I played it together, as we do many of the games I write about here, and enjoyed one of the most captivating gaming experiences we’ve ever shared. (I suspect that Dorte, a puzzle addict who’s much better at most kinds of them than I am, would delete the “one of” from that sentence.)

Chatting with me about The Fool’s Errand, Cliff was at pains to emphasize how incredible it is to him that people today, almost thirty years later, continue to enjoy his first game. Like most designers at the time, he wasn’t thinking beyond the next year or so, and certainly gave no thought whatsoever to The Fool’s Errand as a work for posterity. Yet it feels every bit as contemporary and compelling today as it must have then, the very definition of a timeless work. I think we can ascribe that timelessness to a number of things. Far more than just a collection of puzzles, there’s a beauty about this design, its many strands looping over and entwining one another like a Bach fugue: the text with its simple diction of Myth; the pictures, which are so lovely and evocative that black-and-white seems an aesthetic choice here, not a limitation of the hardware; the intricately fashioned meta-puzzle itself, leading to that Eureka! moment when it all comes together. Perhaps most of all, there remains a generosity of spirit about The Fool’s Errand that bleeds through the screen. As Cliff has stated many times, his goal is never to absolutely stymie you, to prove that he’s the cleverer by presenting you with impossible dilemmas. He wants to tempt and entice and, yes, to challenge you — what fun would The Fool’s Errand be otherwise? — but ultimately he wants you to succeed, to peel back the onion and to share in The Fool’s Errand‘s mysteries. There’s no nonsense in the game; it always plays fair. Take your time with it, and it will reward you in spades.

So, I think you should play this game if you haven’t already. If you enjoy the sorts of games I usually feature on this blog, I think this one will blow you away. The state of classic Macintosh emulation in general being a disgraceful mess for such an historically important platform, I want to do all I can to make that as easy as possible for you. I’ve therefore made a zip that contains the most user-friendly of the early Macintosh emulators, Mini vMac, in versions for Windows, (modern) Macintosh, and Linux. The zip also includes the ROM file that Mini vMac needs to run (please, nobody tell Apple!), the disk images for the game along with a formatted save disk, the original instruction manual, and some brief instructions I’ve written to get you going with the whole package. Give it a shot. If I’ve done my part properly, it won’t be hard at all, and I think you’ll be glad you did. This one is touched, folks.

(Sources: This article is mostly drawn from a long interview I conducted with Cliff himself. Much other information about his life, career, and games can be found on his personal website, although, in keeping with The Fool’s Errand itself, you sometimes have to dig a bit in unexpected places for it.

If you play and enjoy The Fool’s Errand, be sure to check out The Fool and His Money, the long-awaited 2012 sequel that Cliff describes as “everything The Fool’s Errand is times ten.” Dorte and I haven’t had the pleasure yet ourselves, but, believe me, we will just as soon as I can break free of all my moldy oldies for long enough.)

Footnotes

Footnotes
1 For better and often for worse, Masquerade‘s connection to computer gaming extends far beyond the story of Cliff Johnson. The man who first “solved” the riddle and was awarded the hare in March of 1982, one Dugald Thompson, did so, it was revealed years later, largely by cheating. A friend of his had as his current girlfriend a former girlfriend of Kit Williams. While Kit had never outright told her where the treasure — a golden hare sculpted by Kit himself — lay, he had inadvertently dropped enough clues that she could point Thompson in the right direction.

After he was awarded the prize, Thompson formed a company called Haresoft to release an unspeakably horrible computer game called Hareraiser that supposedly contained further clues pointing to a new location of the golden hare. If it did, nobody ever worked them out. More likely, the game was yet another instance of fraud committed by Thompson, designed to make a quick buck from the players that it sent off on a wild goose chase after its nonexistent clues. It justly bombed, Haresoft went into liquidation, and Thompson was forced by his creditors to sell the golden hare at auction.

Long before those events, Masquerade had inspired other British game developers to embed real-world treasure hunts and other puzzles in their own games, perhaps most notably the hunt for the “Golden Sundial of Pi” buried in the Sussex Downs by Mel Croucher and Christian Penfold of Automata. All told, that golden hare had one hell of a long reach.

 
47 Comments

Posted by on November 20, 2015 in Digital Antiquaria, Interactive Fiction

 

Tags: ,

Border Zone

Border Zone

Unlike many early peers such as Sierra, who began publishing at least as many third-party titles as titles they developed themselves in the wake of their first success, Infocom throughout their independent existence prided themselves on keeping everything in-house. Every game they released was written right there in their Cambridge offices by their own dedicated little band of Implementors. But Activision’s pressure to release many more games every year in the wake of their acquisition of Infocom finally changed that in late 1986. Infocom desperately needed more Imps to meet Activision’s craving, but weren’t in a position to pay for any more full-time employees. While they could continue to promote eager testers and programmers from other parts of the company, always their most fecund source of new blood for the Imp pool, there was an obvious point of diminishing returns at play there as well: every tester they promoted to Imp meant one less person to test all of those new games that were now coming down the pipe. After promoting Amy Briggs, who was destined to go down in history as the last person ever to become a full-time Imp at Infocom, it was time to beat some other bushes. Like so many companies before and since who couldn’t afford real employees, Infocom filled the labor gap with contractors willing to work remotely for an initial advance against royalties. After all, modems — even expensive, state-of-the-art ones like the two they now hung off their venerable old PDP-10 — were a lot cheaper than employees.

This change represented, I shouldn’t neglect to emphasize, an enormous attitudinal shift for Infocom. They had never before paid anyone whatsoever on a royalty basis; all of the Imps had always worked for a flat salary. In retrospect we can see this instant as marking the beginning of a sea change in what Infocom really was, from a true creative collective making games together to a mere label under which Activision released any game that was even vaguely adventure-like or story-oriented. It would take a few years for that change to reach its full fruition, but the process started here.

Having elected — or been forced — to make this change in their way of doing business, the natural next question for Infocom was who these new contractors should be. One signee was an enterprising Californian named Bob Bates, founder of a tiny would-be adventure developer he called Challenge, Inc.; I’ll be telling his story in a future article. For other contractors, Infocom turned to some old friends, former Imps who had left the fold. With time and resources at a premium, that made a lot of sense: they already knew ZIL, knew how the Infocom development process worked and what would be expected of them as writers and designers.

Infocom thus reached out to Mike Berlyn, who had left the company back in early 1985 to found a design studio of his own, Brainwave Creations, with his wife Muffy. Having already shipped their first adventure game, Interplay’s text/graphic hybrid Tass Times in Tonetown — and through Activision as publisher at that — they were now sniffing around for a home for the new dimension-bending comedic caper they had on the boil. Much as Berlyn’s mercurial nature could make him difficult to work with at times, everyone at Infocom had always liked him personally. If they must work with outside contractors, he certainly seemed like one of the least objectionable choices. They got as far as signing an initial development deal before things fell apart for reasons that to my knowledge have never been fully explained.

Infocom’s other attempt to get the old band back together again would prove more fruitful even as it could also seem, at least on the surface, a much more surprising move. Marc Blank, you see, hadn’t just quit Infocom a year before. After months of squabbling with Al Vezza’s board over Cornerstone and pretty much every other decision they were making, he had been summarily fired.

Blank moved on to, of all places, Infocom’s erstwhile suitors Simon & Schuster, where he became “Vice President of Computer Software Development,” his responsibilities to include “artificial intelligence, expert systems, sorting out new technologies like optical and disk storage.” The brash young Blank, however, soon found he didn’t fit all that well within the conservative old halls of Simon & Schuster. He left what he calls today a “terrible” job within a few months.

Blank’s next stop would prove more extended. He moved to California to work with a company called American Interactive Media, a new corporation with roots in the music industry who were now so closely associated with the Dutch consumer-electronics giant Philips as to blur the line between independent contractor and subsidiary. Philips had initiated a project to bring the brand new technology of CD-ROM to consumers via a set-top box for the living room, and American Interactive was to create games and other content to run on it. In the long run, this would prove another frustrating experience for Blank; Philips’s gadget wouldn’t finally be released until 1991, an astonishing seven years after the project had been started, and for all sorts of reasons would never take off commercially. For the time being, however, it felt fantastic. A guy who loved nothing better than to take a Big New Idea and give it practical form, Blank felt like he was taking interactivity to the logical next step after Infocom, working not with plain old text but with a whole rich universe of multimedia potential at his fingertips.

While he was about inventing the future for Philips, though, he wasn’t above doing some more work for his Infocom friends from the past. And Infocom was very eager to work with him again. The people he had pissed off enough to get himself fired were largely gone from the newly slimmed-down, games-only edition of the company. Truth be told, most of the people still there had agreed with every sullen argument and veiled jab he had ever delivered to Al Vezza and his cronies. They called, Blank said yes, and Border Zone was born.

It would prove a classic Marc Blank project. Never a gamer, he claims that to this day he’s never played a single Infocom game, other than those he wrote himself, to completion. Nor does he have much intrinsic interest in writing or game design as disciplines unto themselves. During his time with Infocom and even before, when working on the original MIT Zork, he preferred to see himself as the wizard behind the curtain, crafting the magic behind the magic, so to speak, that enabled people like Dave Lebling and Steve Meretzky to do their thing. It was Marc Blank who tinkered endlessly with the parser in that original Zork, taking it from a clone of Adventure‘s primitive two-word jobber to one that wouldn’t be fully equaled by anyone else for well over a decade. It was Blank who came up with vehicles you could ride in and characters you could talk to. It was Blank who sat down with Joel Berez and figured out just how Zork could be chopped up and delivered onto microcomputers via a cross-platform virtual machine, an event that marks the beginning of the real story of Infocom as a maker of computer games. And for his pièce de résistance, it was Blank who radically upended people’s very ideas of what an adventure game could be with his interactive murder mystery Deadline, not in the name of art or literature but simply because he found doing so such a fascinating technical exercise.

When Blank wrote and designed a game, he did so essentially as a demonstration of the one or more Big New Ideas it contained, with the thinking that, new technology now to hand, better writers and designers than him could make something really cool with it. Selling his own skills in those departments short though he may have been, Blank manifested no innate need to create in the sense of crafting a single unified work and stamping his name on it as its author. He was perfectly happy to just help others with the interesting technical questions raised by their own would-be creations, as when he built the system for Mike Berlyn’s Suspended that let you play by issuing commands not to a single avatar but to six different robots, each with its own unique outlook and capabilities. Tellingly, Blank authored — or rather co-authored, with Dave Lebling — his last game during his tenure as an Infocom employee, Enchanter, more than two years before he left. Once other Imps were readily available to implement games, he was content to let them while he did other interesting things.

If Blank was suddenly eager now, three years after Enchanter had been published, to write a game again, it could only mean that he had another very compelling Big Idea which he wanted to put through its paces. This time it was real time.

On the surface, it was far from a new idea. As far back as 1982’s The Hobbit, games from other companies had incorporated a timer such that, if you sat too long at a command prompt without doing anything, the program would process a turn as if you had entered a “wait” command, presumably in the name of keeping you on your toes and adding a dollop of urgency to the experience. In addition to The Hobbit and its descendants, Synapse Software’s BTZ engine (“Better than Zork,” although it really wasn’t) had also used this mechanic — a somewhat odd choice for a line which otherwise strained to promote itself as even more cerebral and “literary” than Infocom, but there you go. On the whole it had proved little more than an annoyance, here and everywhere else it had turned up. The actual games it sat atop did nothing of real interest with it. They weren’t actually real-time games at all, rather turn-based games with a chess timer grafted on.

Blank’s idea, which he worked with Infocom’s systems programmers to build into the new version 5 Z-Machine, was to do something much more sophisticated and thoughtful with real time. He had always been deeply interested in creating more dynamic, realistic environments, in pushing back the boundaries of Infocom’s games as simulations. Consider what made him find Deadline so exciting back in 1982:

You’re in this world where all these things are going on. People are doing things. They stop here, talk to someone, go here. Some things would change depending on what you did, but you could sit in one place and watch people come and go. I loved that the world was alive. Instead of exploring a dead world, you’re in a dynamic world with other things going on that you can impact, and what people then do will change, and that will then resonate out, etc. I had no idea how to do that. I had to make it up as I went along. That to me was the fun part.

Now, in Border Zone, the world would live and change, often completely outside of your view, even as you read, thought, and typed your commands. Blank would remove the artificiality of the turn-based structure and create a truly living world behind the words that you read on the screen. You might be in a train compartment trying frantically to hide some key piece of evidence to avoid arrest. As you do so, a guard is following his own schedule, moving from compartment to compartment in the train, getting ever closer, all unbeknownst to you until he bursts into your cabin. If you do manage to get everything sorted in your  compartment before the guard turns up, you’re left to wait — literally to wait, sitting there watching the seconds tick by on the clock on your real-world wall, knowing some sort of security check must be coming, wondering if you hid everything well enough. Nothing quite like this had ever been done before. It absolutely teemed with complications, ran contrary to some of the most bedrock assumptions in Infocom’s development system. It would be a massive technical challenge to get working correctly. But then, massive technical challenges were what Blank lived for.

As usual for Blank, the fictional premise, plot, and puzzles were chosen after the Big Idea, in answer to the question of what sort of fiction would demonstrate said Idea to best effect. Thankfully, and again as usual for Blank, what he came up with proved far more compelling than one might expect from a designer so eager to declare himself so uninterested in game design. He settled on spy fiction. Stu Galley had actually already tried to craft a spy thriller for some six months between implementing Seastalker and Moonmist, but had finally given up on it as just too complex to bring off with Infocom’s technology at that time. Now, though, Blank thought he might have cracked the code. Spy fiction should make an excellent fit for a game of nail-biting real-time tension. And it certainly didn’t hurt that it was enjoying considerable commercial success at the time: countless readers of writers like John le Carré, Robert Ludlum, and Frederick Forsyth were enjoying a final spot of classic Cold War intriguing in a world that was soon to change in ways that absolutely no one could ever have predicted.

There’s a bit of the typical Infocom in-jokery, now getting more tired than not, in “Frobnia,” the name of the fictional Eastern Bloc country where much of the action of Border Zone takes place. The principal feelie, a tourist brochure and phrase book for Frobnia, also plays for laughs of the “in America you break law, in Soviet Russia law breaks you!” stripe, complete with poorly translated English, and that’s okay because it’s actually pretty sharp and funny stuff. But otherwise Blank plays it straight, and in the process does a good job evoking classic spy thrillers like Day of the Jackal. Border Zone is, like Nord and Bert, a segmented game, telling a single story in three parts from three points of view; breaking it up like this helped to keep the complexities of this real-time, player-responsive world from becoming overwhelming. While Blank didn’t lift much if any text or code directly from Galley’s previous stab at the spy genre, a game that was to be called Checkpoint, the plot of Border Zone‘s opening sequence in particular bears a marked similarity to Galley’s outline: “You, an innocent train traveler in a foreign country, get mixed up with spies and have to be as clever as they are to survive.” In the first part, then, you play the role of an ordinary American businessman who’s entrusted with some vital documents by an American agent on a train that’s about to cross the border from Frobnia into the ostensibly neutral but Western-leaning (and equally fictional) nation of Litzenburg. In the second, you play the American agent himself, who, having palmed the documents on the businessman, must still escape his KGB pursuers. And in the third, you play a KGB agent with secrets of his own on the scene of the attempted assassination of the American ambassador to Litzenburg — an assassination pointed to by the documents. It all feels appropriately morally murky, and is about as intricately plotted as you can reasonably expect from a work with a fraction of the word count of the novels that inspired it.

Still, and as Blank would no doubt agree, the most interesting aspect of Border Zone is what it does technically and conceptually within its fictional premise. Going yet one step beyond those early mysteries, this is the most complex and responsive world simulation Infocom would ever manage, and, like Plundered Hearts, one of their relatively few games that comes close to delivering on their marketing’s promise of interactive fiction as being “like waking up inside a story.” Most interactive fiction, then and now, is fixated on things, on rooms and their contents, to a degree that can feel downright strange to the uninitiated. Border Zone steps away from that fixation to focus not on what things are in the world but on what’s happening there. The old rooms-and-connections model of geography is still there below the surface, but it’s radically de-emphasized. Many rooms have no set-piece descriptions at all to separate them from the story that’s happening to you and all around you, giving the text a sense of urgent flow. Consider, for example, this extract from the second part, from which you could remove the command prompts to end up with something that would read pretty well as an avant-garde second-person novel (a little Italo Calvino, anyone?).

You are standing at the back door of the hut, which can be circled to the northwest and the southwest. On all other sides lies the forest. A small window in the door gives a view into the house.

>n
You walk around to the north side of the hut.

Two men, presumably from the automobile parked at the end of the roadway south of the clearing, are in quiet conversation with a man, presumably the owner of the hut, who stands leaning against the closed front door. They seem to be lecturing him about something, for he speaks little and nods often.

You watch as the lone guard returns to the group. He appears relieved that he has nothing to report.

The dogs are no closer, but now they seem to be off to the south.

>n
A branch falls from a nearby tree, startling you briefly. You turn back and press on through the forest.


>n
You can hear a pack of dogs off to the south.

You continue through the forest, until you come to the edge of a wide clearing to the north - this is the border zone. From atop three guard towers standing in a line from east to west, searchlights play across the zone, brightly illuminating everything in their path. On either side of the towers are tall
fences, running parallel to the border, making a direct assault all but impossible.

>n
You run across the open field at a good clip, though you are hampered by slick- surfaced shoes. You're past the halfway point, but wait! The light from the rightmost tower is heading right at you! You freeze, and consider turning back, but it's too late. The searchlight is upon you now, and before you can react, the night is filled with the sound of wailing sirens.

****  You have been arrested  ****

It’s not that geography isn’t important, but the scale is shifted. As you duck from hiding place to hiding place trying to avoid a searchlight’s beam, the details of each piece of snowy tundra where you crouch aren’t so important, but where you are in the bigger picture — specifically, in relation to that questing beam — certainly is. Map-making is, as one would hope, completely deprecated. Where necessary, the feelies provide maps that are good enough to orient you to your environment, and the game itself also strains, within the limitations of its text-only presentation, to give a visual overview of the situation in the status line when you’re doing things like dodging guards and searchlight beams.

But what’s most important of all is the other people in the world, especially the ones with machine guns trying to hunt you down. The “puzzles” in this game aren’t really puzzles at all, but rather grounded, realistic situations that you need to come to understand and manipulate to your advantage. Suffice to say that there are no riddles or sliding blocks in this one, folks.

All that said, there’s an unavoidable irony about Border Zone: although this approach was inspired by the desire to make a scenario that would be a good match for the real-time component, just about everything it does could have been done just as easily — and, I would argue, just as successfully — using a conventional turn-based approach. In short, I’m not sure how much real time really adds to the experience. As with so many technically esoteric or ambitious touches in games, the real time in Border Zone feels ultimately more interesting for the programmer than it is for the player. Certainly there remain quite a number of unsolved problems. Border Zone‘s visual presentation, for example, leaves a lot to be desired. For all the new capabilities of the version 5 Z-Machine, its display is still limited to two “windows”: a static top window, generally used for the status line and other persistent information like Beyond Zork‘s room description and automap, and a scrolling bottom window for the main body of a game’s text. The ideal setup for Border Zone would have the command prompt in a static window of its own below the scrolling text — notably, this is the layout used by Synapse for their pseudo-real-time games — but this was apparently one step too far for Infocom’s programmers. Instead the command prompt is still in-lined with the rest of the text, meaning that when things happen around you outside of your direct prompting your command is rudely interrupted to tell you about it; then the partially completed command is printed again and you can finish what you were trying to do. It works, but it’s pretty ugly, not to mention disconcerting until you get used to it.

Border Zone doesn't quite know how to make the command prompt work together with real time in an aesthetically pleasing way.

Border Zone doesn’t quite know how to make the command prompt work together with real time in an aesthetically pleasing way.

While that could be fixed easily enough with more advanced screen-layout capabilities, other problems with Border Zone feel more intractable. Given the careful reading that interactive fiction requires, you’re likely to be chronically short on time the first time through a scenario, then twiddling your thumbs waiting for things to happen on subsequent tries. And, believe me, you will be playing through each of these segments much more than once. Much like Beyond Zork, Border Zone promises one type of experience only to deliver another. The heavy emphasis on simulation and dynamism would seem to imply that this is an emergent experience, one where you can have a different experience every time out. Actually, though, that’s not the case, largely because, for all the world’s complexity, there’s no randomness to it at all. Everyone will follow the same patterns every time — complex patterns, yes, but patterns nevertheless — unless you interfere with them, which in turn will only set them on another deterministic course. This leads to a mode of play that isn’t as different from the interactive mysteries Blank earlier pioneered as many a player might wish.

In other words, this is another try-and-try-again game. Essentially you start playing by doing what seems the natural thing for a character in your circumstances, until you die or get captured or otherwise fail. Then you analyze the situation, come up with an idea as to how you might avoid the negative outcome, and try again. Rinse and repeat. Border Zone isn’t as punishing as the mysteries can be because each of its segments is so compressed, limited to no more than ten or fifteen minutes of real — i.e., wall-clock — time. It’s here, however, where the real time component can also become actively annoying. When you know the series of steps you need to follow to get to a certain point, you want to be able to “wait” in the game for each decision, not be forced to literally sit around waiting in real life. (It is possible to “wait for” a specific number of seconds, but that can be tough to plan out, not to mention deadly if you get it wrong.) And when you come to one of the junctures that require really precise timing, where you need to hit the enter key to submit your command at just the precisely right instant, it can be extremely frustrating when you, as another superspy would say, “miss it by that much” and have to start again.

Each sequence in Border Zone feels like a single bravura action sequence from a good James Bond flick, which is, one senses, exactly the effect intended. What with all the learning by death, playing can feel oddly like choreographing the delicate ballet that is such a sequence, trying again and again until you get all the drama and thrills just right. One notable side effect of the extreme time compression is that Border Zone, even with all three of its sections taken together, is one very short adventure game. Its rather expansive 175 K story file, which would seem to promise a much longer experience, is padded partially by an in-game InvisiClues-style hint system and partially by the complexities of the real-time system itself, but most of all by the overhead involved in implementing a world of depth rather than breadth. Everything was a trade-off in game development in Infocom’s day. In this case, Blank has dramatically increased your scope of possibility and the number of moving parts in the world around you at the expense of game length. Most of the things you might think to try in Border Zone work logically and have logical consequences in the context of the world and its other actors, even if most of them must inevitably be the wrong things, things that ultimately lead to failure. And yet, even duly accounting for the many replays that will be necessary to finish each sequence, it’s very difficult to spend more than three or four hours on Border Zone. That was a major problem for a commercial computer game selling for $30 or more. It’s not hard to understand why gamers would be put off by the entertainment-per-dollar ratio at play here, not hard to understand why publishers usually opted for longer if sketchier experiences over an intricately tooled Swiss watch of a game like this one.

How much its extreme brevity had to do with Border Zone‘s poor sales reception is, given everything else that was going so wrong for Infocom at the time, hard to say. Certainly they tried hard to make it accessible to as many customers as possible. Despite running under the new version 5 rather than the version 4 Z-Machine of Nord and Bert, it became the second in Infocom’s “LZIP” line of larger-than-usual games that were nevertheless shoehorned into the Commodore 64. Still, sales were bad enough to give Border Zone the title of worst-selling all-text Infocom game in history: less than 12,000 units. Thus it wound down Infocom’s demoralizing 1987 just as it had begun, by setting a sales record of the wrong type. It doubtless didn’t help Border Zone‘s cause that it was released in the immediate wake of the much higher profile and more enthusiastically promoted Beyond Zork.

One of Infocom’s least remarked and, one suspects, least played games today, Border Zone deserves better than that fate. I’m not sold on the case it makes for real-time interactive fiction, and little surprised that that avenue has gone all but completely unexplored through all of the years of non-commercial experimentation that has followed Infocom’s demise. But Border Zone is much more than just a failed technical experiment. Even if real time were taken out of the picture entirely, it would stand as an experience able to get the pulse pounding and the juices flowing, something that textual interactive fiction isn’t exactly known for. It’s also a very solvable game, and one where every challenge truly is part and parcel of the story you’re living. That, again, is something not a whole lot of interactive fiction, vintage or modern, can lay claim to. I highly recommend that you give it a play, and experience yet one more utterly unique Infocom game for yourself.

(Sources: As usual with my Infocom articles, much of this one is drawn from the full Get Lamp interview archives which Jason Scott so kindly shared with me. Also useful was the April 1986 Questbusters.)

 
42 Comments

Posted by on November 13, 2015 in Digital Antiquaria, Interactive Fiction

 

Tags: , ,

Beyond Zork

Beyond Zork

For a company that’s long since gone down into history as the foremost proponent of the all-text adventure game, Infocom sure spent a lot of years fretting over graphics. As early as 1982, well before starting their iconic text-only advertising campaign, they entered into discussions with Mark Pelczarski of Penguin Software about a possible partnership that would have seen Antonio Antiochia, writer and illustrator of Penguin’s hit adventure Transylvania, drawing pictures for Infocom games using Penguin’s The Graphics Magician. When that combination of Penguin’s graphics technology with Infocom’s text-only Z-Machine was judged impractical, the all-text advertising campaign went forward, but still Infocom refused to rule out graphics internally. On the contrary, they used some of the revenue from 1983, their first really big year, to start a graphics research group of their own under the stewardship of Mike Berlyn. But that attempt at a cross-platform graphics system, a sort of Z-Machine for graphical games, petered out almost as quietly as the Penguin deal, resulting only in Berlyn’s unique but ultimately underwhelming computerized board game Fooblitzky. Specifying a single set of graphics capabilities achievable by all of the diverse computers on the market meant that those graphics had to be very primitive, and, thanks to the fact that they were running through an interpreter, slow to boot. In the end Fooblitzky made it only to the Apple II, the Atari 8-bits, and the PC clones, and even that was a struggle. Certainly trying to combine this already problematic system with the sort of adventure game that was Infocom’s bread and butter seemed hopeless. Thus the graphics group was quietly dispersed amid all the other downsizing of 1985. Strike two.

After completing Trinity in 1986, Brian Moriarty decided to see if he could make the third time the charm. The fundamental problem which had dogged Infocom’s efforts to date had been the big DEC PDP-10 that remained at the heart of their development system — the same big mainframe that, once lauded as the key to Infocom’s success, was now beginning to seem more and more like a millstone around their necks. Bitmap graphics on the DEC, while possible through the likes of a VT-125 terminal, were slow, awkward, and very limited, as Fooblitzky had demonstrated all too well. Worse, mixing conventional scrolling text, of the sort needed by an Infocom adventure game, with those graphics on the same screen was all but impossible. Moriarty therefore decided to approach the question from the other side. What graphic or graphic-like things could they accomplish on the PDP-10 without losing the ability to easily display text as well?

That turned out to be, if far from the state of the art, nevertheless more than one might expect, and also much more than was possible at the time that they’d first installed their PDP-10. DEC’s very popular new VT-220 line of text-oriented terminals couldn’t display bitmap graphics, but they could change the color of the screen background and individual characters at will, selecting from a modest palette of a dozen or so possibilities. Even better, they could download up to 96 graphics primitives into an alternate character set, allowing the drawing of simple lines, boxes, and frames, in color if one wished. By duplicating these primitives in the microcomputer interpreters, Infocom could duplicate what they saw on their DEC-connected dumb terminals on the computer monitors of their customers. Like much of the game that would gradually evolve from Moriarty’s thought experiment, this approach marked as much a glance backward as a step forward. Character graphics had been a feature of microcomputers from the beginning — in fact, they had been the only way to get graphics out of two of the Trinity of 1977, the Radio Shack TRS-80 and the Commodore PET — but had long since become passé on the micros in light of ever-improving bitmap-graphic capabilities. Once, at the height of their success and the arrogance it engendered, Infocom had declared publicly that they wouldn’t do graphics until they were confident that they could do them better than anyone else. But maybe such thinking was misguided. Given the commercial pressure they were now under, maybe primitive graphics were better than no graphics at all.

Thus color and character graphics became the centerpieces of a new version of the Z-Machine that Dave Lebling, Chris Reeve, and Tim Anderson, Infocom’s chief technical architects, began putting together for Moriarty’s “experimental” project. This version 5 of the Z-Machine, the last to be designed for Infocom’s PDP-10-based development system, gradually came to also sport a host of other new features, including limited mouse support, real-time support, and the ability, previously hacked rather rudely into the old version 3 Z-Machine for The Lurking Horror, to play sampled sound files. The most welcome feature of all was one of the least flashy: an undo command that could take back your last turn, even after dying. Game size was still capped at the 256 K of the version 4 Z-Machine, a concession to two 8-bitters that still made up a big chunk of Infocom’s sales, the Commodore 128 and the Apple II. For the first time, however, this version of the Z-Machine was designed to query the hardware on which it ran about its capabilities, degrading as gracefully as possible on platforms that couldn’t manage to provide its more advanced features. The graphically primitive Apple II, for instance, didn’t offer color and replaced the unique character-graphic glyphs with rough approximations in simple ASCII text, while both 8-bitters lacked the undo feature. Mouse input and sound were similarly only made available on machines that were up to it. Infocom took to calling the version 5 games, of which Moriarty’s nascent project would be the first, “XZIPs,” the “X” standing for “experimental.” (Even after Moriarty’s game was released and the format was obviously no longer so experimental, the name would stick.)

Moriarty's new interface running on an Amiga. Note the non-scrolling status window at top left that currently displays the room description, and the auto-map at top right. You can move around by clicking on the map.

Moriarty’s new interface running on an Amiga. Note the non-scrolling status window at top left that currently displays the room description, and the auto-map at top right. You can move around by clicking on the map as well as by typing the usual compass directions.

The interface gracefully (?) degraded on the Apple II.

The same interface gracefully (?) degraded on the Apple II.

Of course, it was still up to Moriarty to decide how to use the new toolkit. He asked himself, “What can I do within the constraints of our technology to make the adventuring experience a little easier?” He considered trying to do away with the parser entirely, but decided that that still wasn’t practical. Instead he designed an interface for what he liked to call “an illuminated text adventure.” Once again, in looking forward he found himself to a surprising extent looking back.

In watching myself play, I found the command I typed most was “look.” So I said this is silly, why can’t the room description always be visible? After all, that’s what Scott Adams did in his original twelve adventures, with a split-screen showing the room description, exits, and your inventory at the top, while you type in the bottom. So I said, let’s take a giant step backward. The screen is split in half in most versions. On the left side of the top half is a programmable window. It can contain either the room description or your inventory. So as you walk from room to room, instead of the description coming in-line with your commands, as it does now in our games, this window is updated. If you say, “inventory,” the window changes to show your possessions.

Another thing I liked about the old Scott Adams games was the list of room exits at the top of the screen. That’s a part of writing room descriptions that has always bugged me: we have to have at least one sentence telling where the exits are. That takes up a lot of space, and there are only so many interesting ways to do that. So I said, let’s have a list of exits at the top. Now, that’s not such a revolutionary idea. I thought of putting in a compass rose and all this other stuff, but finally I came up with an onscreen map that draws a typical Infocom map — little boxes with lines and arrows connecting them. The right side of the upper screen has a little graphics map that draws itself and updates as you walk around. It shows rooms as boxes and lines as their connections. If you open a door, a line appears to the next room. Dark rooms have question marks in them. The one you’re in is highlighted, while the others are outlined.

This onscreen map won’t replace the one you draw yourself, but it does make it much easier to draw. It won’t show rooms you haven’t been to yet, but shows exits of your current room and all the exits of the adjoining rooms that you’ve visited.

There’s even more to this re-imagining of the text adventure. On machines equipped with mice, it’s possible to move about the world by simply clicking on the auto-map; function keys are now programmable to become command shortcuts; colors can be customized to your liking; even objects in the game can be renamed if you don’t like the name they came with. And, aware that plenty of customers had a strong traditionalist streak, Moriarty also made it possible to cut the whole thing off at the knees and go back to a bog-standard text-adventure interface at any time by typing “mode” — although, with exits now absent from room descriptions, it might be a bit more confusing than usual to play that way.

Remapping the function keys.

Remapping the function keys, just one of many useful bells and whistles.

But really, it’s hard to imagine any but the most hardcore Luddites choosing to do so. The new interface is smart and playable and hugely convenient, enough to make you miss it as soon as you return to a more typical text adventure, to wish that it had made it into more than the single Infocom game that would ultimately feature it, and to wonder why more designers haven’t elected to build on it in the many years since Infocom’s demise. Infocom wrote about the new interface in their Status Line newsletter that, “never a company to jump into the marketplace with gaudy or ill-conceived bells and whistles, we have always sought to develop an intelligently measured style, like any evolving author would.” It does indeed feel like a natural, elegant evolution, and one designed by an experienced player rather than a marketeer.

With the new interface design and the technology that enabled it now well underway, Moriarty still needed an actual game to use it all. Here he made another bold step of the sort that was rapidly turning his erstwhile thought experiment into the most ambitious game in Infocom’s history. It began with another open-ended question: “What kind of game would go well with this interface?” He settled on another first for Infocom: still a text adventure, but a text adventure “with very strong role-playing elements,” in which you would have to create a character and then build up her stats whilst collecting equipment and fighting monsters.

I spent a lot of time playing fantasy games like Ultima and Wizardry and, one that I particularly liked a lot, Xyphus for the Macintosh. And I realized it was fun to be able to name your character and have all these attributes instead of having just one number — a score — that says how well you’re doing. I thought it would be nice to adopt some of the conventions from this kind of game, so you don’t have one score, you have six or seven: endurance, strength, compassion, armor class, and so on. Your job in the game is, very much like in role-playing games, to raise these statistics. And your character grows as you progress through the puzzles, some of which cannot be solved unless you’ve achieved certain statistics. You can somewhat control the types of statistics you “grow” in order to control the type of character you have.

Viewing the state of your character

Viewing the state of your character.

In conflating the CRPG with the text adventure, Moriarty was, yet again, looking backward as much as forward. In the earliest days of the entertainment-software industry, no distinction was made between adventure games and CRPGs — small wonder, as text adventures in the beginning were almost as intimately connected with the budding tabletop RPG scene as were CRPGs themselves. Will Crowther, creator of the original Adventure, was inspired to do so as much by his experience of playing Dungeons and Dragons as he was by that of spelunking in Kentucky’s Mammoth Cave. Dave Lebling was a similarly avid Dungeons and Dragons player at the time that he, along with three partners, created the original mainframe Zork, the progenitor of everything that would follow for Infocom. It was Lebling who inserted Dungeons and Dragons-style randomized combat into that game, which survived as the battles with a certain troll and thief that served as many players’ introductions to the perils of life in the Great Underground Empire in Zork I on microcomputers. About the same time, Donald Brown was creating Eamon, the world’s first publicly available text-adventure creation system that also happened to be the first publicly available CRPG-creation system. When Byte magazine made the theme of its December 1980 issue “Adventure,” no editorial distinction was made between games where you wandered around solving puzzles and those where you wandered around killing monsters. Years before Infocom would adopt the term “interactive fiction” as their preferred name for their creations, Lebling described Zork for that issue as a “computerized fantasy simulation,” a term which today smacks much more of the CRPG than the text adventure. In the same issue Jon Freeman, creator of Temple of Apshai and many of its sequels, spent quite some pages laboriously describing his approach to adventuring, which offered “character variation” that “affects the game in many ways.” He struggles, with mixed results, to clarify how this is markedly different from the approach of Zork and Scott Adams. In retrospect, it’s obvious: he’s simply describing the difference between a CRPG and a text adventure. Over time this difference became clearer, even intuitive, but for years to come the two forms would remain linked in gamers’ minds as representing separate sub-genres more so than categories onto themselves. “Adventure-game columnists” like Computer Gaming World‘s Scorpia, for instance, continued to cover both into the 1990s and beyond.

That’s by no means inexplicable. The two forms shared plenty in common, like a story, a love of fantasy settings, and the need to explore a computer-simulated world and (usually) to map it. The forms were also connected in being one-shot games, long experiences that you played through once and then put aside rather than shorter experiences that you might play again and again, as with most action and strategy games of the period. And then there was the simple fact that neither would likely have existed in anything like the form we know them if it hadn’t been for Dungeons and Dragons. Yet such similarities can blind us, as it did so many contemporary players, to some fairly glaring differences. We’ll soon be seeing some of the consequences of those differences play out in Moriarty’s hybrid.

By the time that Moriarty’s plans had reached this stage, it was the fall of 1986, and Infocom was busily lining up their biggest slate of new games ever for the following year. It had long since been decided that one of those games should bear the Zork name, the artistic fickleness that had led the Imps to reject Infocom’s most recognizable brand for years now seeming silly in the face of the company’s pressing need for hits. Steve Meretzky, who loved worldbuilding in general, also loved the lore of Zork to a degree not matched even by the series’s original creators. While working on Sorcerer, he had assembled a bible containing every scrap of information then “known” — more often than not in the form of off-hand asides delivered strictly for comedic effect — about the Flathead dynasty, the Great Underground Empire, and all the rest of it, attracting in the process a fair amount of ridicule from other Imps who thought he was taking it all far, far too seriously. (One shudders to think what they would say about The Zork Compendium.) Now Meretzky was more than eager to do the next Zork game. Whirling dervish of creativity that he was, he even had a plot outline to hand for a prequel, which would explain just how the Great Underground Empire got into the sorry state in which you first find it in Zork I. But there was a feeling among management that the long-awaited next Zork game ought to really pull out all the stops, ought to push Infocom’s technology just as far as it would go. That, of course, was exactly what Moriarty was already planning to do. His plan to add CRPG elements would make a fine fit with the fantasy milieu of Zork as well. Moriarty agreed to make his game a Zork, and Meretzky, always the good sport, gave Moriarty his bible and proceeded to take up Stationfall, another long-awaited sequel, instead.

It was decided to call the new Zork game Beyond Zork, a reference more to its new interface and many technical advancements than to the content of the game proper. Having agreed to make his game a Zork, Moriarty really made it a Zork, stuffing it with every piece of trivia he could find in Meretzky’s bible or anywhere else, whilst recreating many of the settings from the original Zork trilogy as well as the Enchanter trilogy. Beyond Zork thus proclaimed to the world something that had always been understood internally by Infocom: that the Enchanter trilogy in a different reality — a better reality according to marketing director Mike Dornbrook’s lights — could have just as easily shipped as Zork IV through VI. But Moriarty didn’t stop there. He also stuffed Beyond Zork with subtler callbacks to almost the entire Infocom catalog to date, like the platypus, horseshoe, and whistle from Wishbringer and the magical umbrella from Trinity. Mr. Prosser, Arthur Dent’s hapless nemesis from The Hitchhiker’s Guide to the Galaxy, shows up as the name of a spell, and Buck Palace, the statuesque B-movie star from Hollywood Hijinx, is the default name for your character if you don’t give him another. There are so many references that upon the game’s release Infocom sponsored a contest to see who could spot the most of them. Especially in retrospect, knowing as we do that we are now coming close to the end of the line for Infocom, all of the backward glances can take on an elegiac quality, can make Beyond Zork feel like something of a victory lap for an entire era of adventure gaming.

I’m less pleased with the actual plot premise of Beyond Zork, which, as unplanned sequels so often tend to do, rather clumsily undermines the message of its predecessor. Moriarty’s game builds on Spellbreaker, which saw you destroying magic in the name of saving the world. The ending of Spellbreaker:

You find yourself back in Belwit Square, all the Guildmasters and even Belboz crowding around you. "A new age begins today," says Belboz after hearing your story. "The age of magic is ended, as it must, for as magic can confer absolute power, so it can also produce absolute evil. We may defeat this evil when it appears, but if wizardry builds it anew, we can never ultimately win. The new world will be strange, but in time it will serve us better."

Strange as it may sound, I judge that jarring last sentence to be nothing less than Dave Lebling’s finest moment as a writer. It’s an ending that can be read to mean many things, from an allegory of growing up and leaving childish things behind to a narrative of human progress as a whole — the replacing of a “God of the gaps” with real knowledge, simultaneously empowering and depressing in the way it can leach the glorious mystery out of life.

But still more depressing is the way that Beyond Zork now comes along to muck it up. You play a novice enchanter (where have we heard that before?) who, even as the wise and powerful hero of Spellbreaker sets about destroying magic, is dispatched by the Guild to retrieve the “Coconut of Quendor” that can safeguard it for a return at some point in the future. Why couldn’t Moriarty just leave well enough alone, find some other premise for his game of generic fantasy adventure? About the best thing I can say about the plot is that you hardly know it’s there when you’re actually playing the game; until the last few turns Beyond Zork is largely a plot-free exercise in puzzles, self-improvement (in the form of easily quantifiable statistics and equipment), and monster bashing.

On those terms, Beyond Zork seems to acquit itself quite well in the early going. Brian Moriarty remains the most gifted prose stylist among the Imps, crafting elegant sentences that must make this game, if nothing else, among the best written generic fantasies ever. Zork always had a bipolar personality, sometimes indulging in unabashed comedy and at others evoking majestic, windy desolation. Perhaps surprisingly in that it comes from the author of the doom-laden Trinity, Beyond Zork leans more toward the former than the latter. But then anyone who’s played Wishbringer knows that Moriarty can do comedy — and the juxtaposition of comedy with darker elements — very well indeed. I particularly like the group of Implementors you meet; this sort of meta-comedy was rapidly becoming another Zork tradition, dating back to the appearance of the adventurer from the original trilogy in Enchanter or, depending on how you interpret the ending of Zork III, possibly even earlier. Moriarty lampoons the reputation the Imps had within Infocom, usually expressed jokingly but not always without an edgy undercurrent, of being the privileged kids who always got all the free lunches and other perks, not to mention the public recognition, while the rest of the company, who rightfully considered themselves also very important to Infocom’s success, toiled away neglected and anonymous.

Ethereal Plane Of Atrii, Above Fields
The thunderclouds are compressed into a flat optical plane, stretching away below your feet in every direction.

A group of Implementors is seated around a food-laden table, playing catch with a coconut.

One of the Implementors notices your arrival. "Company," he remarks with his mouth full.

A few of the others glance down at you.

>x coconut
It's hard to see what all the fuss is about.

A tall, bearded Implementor pitches the coconut across the table. "Isn't this the feeb who used the word 'child' a few moves ago?" he mutters, apparently referring to you. "Gimme another thunderbolt."

>get coconut
The Implementors won't let you near.

A cheerful-looking Implementor catches the coconut and glares down at you with silent contempt.

"Catch!" cries the cheerful-looking Implementor, lobbing the coconut high into the air.

"Got it." A loud-mouthed Implementor jumps out of his seat, steps backwards to grab the falling coconut... and plows directly into you.

Plop. The coconut skitters across the plane.

>get coconut
As you reach towards the coconut, a vortex of laughing darkness boils up from underfoot!

"More company," sighs the cheerful-looking Implementor.

You back away from the zone of darkness as it spreads across the Plane, reaching out with long black fingers, searching, searching...

Slurp! The coconut falls into the eye of the vortex and disappears, along with a stack of lunch meat and bits of cutlery from the Implementors' table. Then, with a final chortle, the vortex draws itself together, turns sideways and flickers out of existence.

"Ur-grue?" asks the only woman Implementor.

"Ur-grue," nods another.

>ask implementors about ur-grue
"I think I just heard something insignificant," remarks an Implementor.

"How dull," replies another, stifling a yawn.

"This is awkward," remarks a loudmouthed Implementor. "No telling what the ur-grue might do with the Coconut. He could crumble the foundations of reality. Plunge the world into a thousand years of darkness. We might even have to buy our own lunch!" The other Implementors gasp. "And it's all her fault," he adds, pointing at you with a drumstick.

"So," sighs another Implementor, toying with his sunglasses. "The Coconut is gone. Stolen. Any volunteers to get it back?"

One by one, the Implementors turn to look at you.

"I'd say it's unanimous," smiles the cheerful-looking Implementor.

A mild-mannered Implementor empties his goblet of nectar with a gulp. "Here," he says, holding it out for you. "Carry this. It'll keep the thunderbolts off your back."

>get goblet
The Implementor smiles kindly as you take the goblet. "And now you will excuse us. My fellow Implementors and I must prepare for something too awesome to reveal to one as insignificant as you."

At first, the CRPG elements seem to work better than one might expect. Randomized combat in particular has for many, many years had a checkered reputation among interactive-fiction fans. It’s very difficult to devise a model for combat in text adventures that makes the player feel involved and empowered rather than just being at the mercy of the game’s random-number generator. There weren’t many fans of the combat in Zork I even back in the day, prompting Infocom to abandon it in all of their future games; only the usually pointless “diagnose” command remained as a phantom limb to remind one of Zork‘s heritage in Dungeons and Dragons. Even Eamon as time went by moved further and further away from its original incarnation as a sort of text-only simulation of Dungeons and Dragons, its scenarios beginning to focus more on story, setting, and puzzles than killing monsters.

Battling a rat-ant (say, is that a Starcross reference?) in Beyond Zork.

Battling a rat-ant (say, is that a Starcross reference?) in Beyond Zork.

Beyond Zork doesn’t entirely solve any of the problems that led to those developments, but it does smartly make the process of preparing for the combats more compelling than the combats themselves can possibly be. As you explore the world and solve puzzles, you level up and improve your ability scores. Among other things, this lets you fight better. You can also sell treasure for money, a nice twist on the treasure-hunt model of old-school text adventuring, and use it to buy better weapons, armor, and magic items. As you improve yourself through these means and others, you find that you can challenge tougher monsters. Thus, while the combat is still not all that interesting in itself — it still comes down to the same old “monster hits you for X points of damage, you hit monster for Y points of damage,”  rinse and repeat until somebody is done for — the sudden ability to win a battle in which you previously didn’t have a chance can feel surprisingly rewarding. Many of the monsters take the place of locked doors in more conventional text adventures, keeping you out of places you aren’t yet ready for. It feels about as satisfying to defeat one of these as it does to finally come across the key for a particularly stubborn lock in another game. Indeed, I wish that Moriarty had placed the monsters more carefully in order to guide you through the game in the right order and keep you from locking yourself out of victory by doing the right things in the wrong order, as I’ll describe in more detail shortly.

It also helps that the combats are usually quite low-stakes. While undo is disabled in combat — how ironic that Infocom introduced undo in their first game ever with a good reason not to allow it! — it’s always obvious very quickly when you’re over-matched, and usually fairly trivial to back away and go explore somewhere else before you get killed. One other subtle touch, much appreciated by a big old softie like me who can even start to feel bad for the monsters he kills in Wizardry, is that you rarely actually kill anything in Beyond Zork. Monsters usually “retreat into the darkness” or something similar rather than expiring — or at least before expiring. While I suspect Moriarty did this more to avoid implementing dead monster bodies than to make a statement, I’ll take my instances of mercy wherever I can find them.

Beyond Zork blessedly doesn’t take itself all that seriously, whether as a CRPG or as anything else. Instead of the painfully earnest orcs and dragons that populate most CRPGs, Beyond Zork‘s monsters are almost uniformly ridiculous: Christmas tree monsters singing dreadful carols (anyone who’s ever visited a shopping mall on Black Friday can probably relate), cruel puppets who attack by mocking you (they “recite your nightly personal habits in excruciating detail” among other attacks), dust bunnies (got any lemony-fresh Pledge handy?). In a sense Beyond Zork is just another genre exercise for Infocom, albeit in a ludic rather than a literary genre this time, and as usual for them it can sometimes feel as much parody as homage. There are alternate, puzzlely solutions that can be used to defeat many monsters in lieu of brute strength, and usually in more entertaining fashion at that. In fact, in many cases cleverness is the only way forward. Vital clues to the various monsters’ weaknesses are found in the game’s version of Dungeons and Dragons‘s Monster Manual, the accompanying feelie “The Lore and Legends of Quendor”; if only other companies offered such entertaining and clever copy protection! And if fighting fair and square or puzzling your way around the monsters aren’t enough alternatives for you, you can just use your Wand of Annihilation or other magic. Not just monsters but also many other problems can similarly be defeated in various ways. Beyond Zork is surprisingly flexible.

But, sadly, it’s often dangerously flexible. Which brings us to the part of this article where I have to tell you why, despite its many innovations, despite Moriarty’s usual fine writing, and despite some fine puzzles, Beyond Zork in my opinion just doesn’t add up to all that great of a game.  I think I can best explain how things go wrong by dissecting one particularly dismaying sequence in some detail.

Fair warning: heavy spoilers begin here!

So, I come upon a mother and baby hungus — “part sheep, part hippopotamus,” as “The Legends and Lore of Quendor” helpfully tells us — caught in a bad situation.

Quicksand
A strip of dry path winds alongside a pool of quicksand. You see a baby hungus stuck into the wet, gritty surface.

A mother hungus is standing nearby, gazing anxiously at her baby.

Luckily, I happen to have found a Stave of Levitation. What I need to do seems pretty obvious.

>point stave at baby
The baby hungus bellows with surprise as he rises out of the quicksand! Sweat breaks out on your forehead as you guide the heavy burden over the mud and safely down to the ground.

[Your strength just went down.]

The ungainly creature nuzzles you with his muddy snout, and bats his eyelashes with joy and gratitude. Then he ambles away into the jungle to find his mother, pausing for a final bellow of farewell.

[Your compassion just went up.]

Heartwarming, isn’t it? But you know what’s less heartwarming? The fact that I’ve just locked myself out of victory, that’s what. I needed to do something else, which we’ll get to in a moment, before rescuing the little fellow. It will, needless to say, likely be a long, long time before I realize that, especially given that the game actually rewards me by increasing my Compassion score. (As for the Strength loss, never fear, I’ll recover that automatically in a few turns.) This is terrible design, of the sort I expect from early Sierra, not late Infocom. I wrote in an earlier article that “we should reserve a special layer of Hell for those designs whose dead ends feel not just like byproducts of their puzzles and other interactive possibilities but rather intentional traps.” See you down below, Beyond Zork.

Beyond Zork is absolutely riddled with these sorts of traps, forcing you to restart many, many times to get through it, wondering all the while whether you didn’t render this latest puzzle you’re wrestling with insoluble a long time ago by some innocent, apparently correct action like the one above. What makes this even more baffling is that in other ways Beyond Zork is presented as an emergent, replayable experience, the sort of game where you take your lumps and move on until you either win or lose rather than constantly restoring and/or restarting to optimize your play. Taking a cue from the roguelike genre, large chunks of Beyond Zork‘s geography are randomly generated anew every time you play, as are the placement of most magic items and their descriptions; that Stave of Levitation I just used may be a Stave of Annihilation in another playthrough, forcing me to make sure I make good use of the various shops’ ability to identify stuff for me. As the manual tells you, “No two games of Beyond Zork are exactly alike!” But what’s the point of that approach when most of those divergent games leave you fruitlessly wandering about, blocked at every turn, wondering where you went wrong? Even an infamously difficult roguelike like NetHack at least puts you out of your misery when you screw up. By the time you do figure out how to tiptoe through this minefield of dead ends, you’ve internalized the whole game to such an extent that the randomness is just a huge annoyance.

The deterministic text adventure and the emergent CRPG end up rubbing each other raw almost every time they touch. When you discover a cool new magic wand or spell, you’re afraid to use it to vanquish that pesky monster you’ve been struggling with for fear that you’ll need to use it to solve some deterministic puzzle somewhere else. Yes, resource management was always a huge part of old-school dungeon crawls like Wizardry and The Bard’s Tale — arguably the hugest part, given that their actual combat engines were often little more sophisticated than that of Beyond Zork — but there was always a clear distinction between things you might need to solve puzzles and things for managing combat. The lack of same here is devastating; the CRPG aspects are really hard to enjoy when you’re constantly terrified to actually use any of the neat equipment you collect.

And just as the text adventure undermines the CRPG, the CRPG also undermines the text adventure. Near the hungi — never fear, we’ll return to that problem shortly! — I find this, yet another callback to Spellbreaker:

>w
Idol
A stone idol, carved in the likeness of a giant crocodile, stands in a clearing.

You see a tear-shaped jewel in its gaping maw.

You see a tear-shaped jewel on the idol's maw.

>x idol
This monstrous idol is approximately the size and shape of a subway train, not counting the limbs and tail. The maw hangs wide open, its lower jaw touching the ground to form an inclined walkway lined with rows of stone teeth. A tear-shaped jewel adorns the idol's face, just below one eye.


>enter idol
You climb up into the idol's maw.

The stone jaw lurches underfoot, and you struggle to keep your balance. It's like standing on a seesaw.

>get jewel
The idol's maw tilts dangerously as you reach upward!
Slowly, slowly, you draw your hand away from the tear-shaped jewel, and the jaw settles back to the ground.

>u
You edge a bit further into the open maw.

Creak! The bottom of the jaw tilts backward, pitching you helplessly forward...

This sequence begins a veritable perfect storm of problems, starting with the text itself, which contradicts itself and thus makes it hard to figure out what the situation really is. Is the jewel in the idol’s maw, on the idol’s maw (the weird doubled text is present in the original), or stuck to the idol’s face? Or are there two jewels, one stuck on his face and one in (on?) his maw? I’m still not sure. But let’s continue a bit further.

>turn on lantern
Click. The lantern emits a brilliant glow.

Inside Idol
This long, low chamber is shaped much like the gizzard of a crocodile. Trickles of fetid moisture feed the moss crusting the walls and ceiling.

>squeeze moss
The moss seems soft and pliant.

The moss is “Moss of Mareilon.” As described in “The Lore and Legends of Quendor,” squeezing it as I’ve just done will lead to a dexterity increase a few turns from now. And so we come to one of the most subtly nasty bits in Beyond Zork. To fully explain, I need to back up just a little.

Earlier in the game, in a cellar, I needed to climb a “stairlike spiral” of crates to get something on top of them. Alas, I wasn’t up to it thanks to a low dexterity: “You teeter uncertainly on the lowest crates, lose your balance, and sprawl to the ground. Not very coordinated, are you?” Luckily, some Moss of Mareilon was growing right nearby; I could squeeze it to raise my dexterity enough to get the job done.

So, when I come to the idol, and find more Moss of Mareilon growing conveniently just inside it, that combined with the description of my somewhat clumsy effort to grab the jewel leads to a very natural thought: that I need to squeeze the moss inside the idol to increase my dexterity enough to grab the jewel. I do so, then use a handy magic item to teleport out, then do indeed try again to grab the jewel. But it doesn’t work; I still can’t retrieve the jewel, still get pitched down the idol’s throat every time. After struggling fruitlessly with this poorly described and poorly implemented puzzle — more on that in a moment — I finally start thinking that maybe it can’t be solved because I didn’t give my character enough dexterity at the very beginning of the game. This can actually happen; Beyond Zork is quite possibly the only text adventure ever written in which you can lock yourself out of victory before you even enter your first command. (“The attributes of the ‘default’ [pre-created] characters are all sufficient to complete the story,” says the manual, which at least lets you know some of what you’re in for if you decide to create your own.) So, I create a brand new character with very good dexterity, and spend an hour or so, cursing all of the randomizations all the while, to get back to the idol puzzle. But I still can’t fetch the diamond, not even after squeezing the moss.

It does seem that the game has, once again, actively chosen to mislead me and generally screw me over here. But, intentionality aside, a more subtle but more fundamental problem is the constant confusion between player skill, the focus of a text adventure, and character skill, the focus of a CRPG. Let me explain.

A text adventure is a much more embodied experience than a CRPG. There’s a real sense that it’s you — or, increasingly in later games, a character that you are inhabiting — whom you are guiding through the simulated world. Despite the name, meanwhile, a CRPG is a more removed experience. You play a sort of life coach guiding the development of one or more others. Put another way, one genre emphasizes player skill, the other character skill. Think about what you spend the most time doing in these games. The most common activity in a text adventure is puzzle-solving, the most common in a CRPG combat. The former relies entirely on the wit of the player; the latter, if it’s done well, will involve plenty of player strategy, but it’s also heavily dependent on the abilities of the characters you guide. After all, no amount of strategy is going to let you win Wizardry or The Bard’s Tale with a level 1 party. CRPGs are process-intense simulations to a greater degree than text adventures, which rely heavily on hand-crafted content, often — usually in these early years — in the form of puzzles of one stripe or another. This led Jon Freeman in his Byte article to call text adventures, admittedly rather reductively, not simulations or even games at all but elaborate puzzle boxes built out of smaller puzzles: “It can be quite challenging to find the right key, the right moment, and the right command to insert it in the right lock; but once you do, the door will open — always.” In a CRPG, on the other hand, opening that lock might depend on a random number and some combination of a character’s lock-picking ability, the availability of a Knock spell, and/or the quality of the lock picks in her pack. More likely, the locked door won’t be there at all, replaced with some monster to fight. Sure things aren’t quite so common.

Of course, these distinctions are hardly absolute. CRPGs, for example, contained occasional player-skill-reliant puzzles to break up their combat almost from the very beginning. Muddying up the player-skill/character-skill dichotomy too much or too thoughtlessly can, however, be very dangerous, as Beyond Zork has just so amply demonstrated. While one hardly need demand an absolutely pure approach, one does need to know where the boundaries lie, which problems you can solve by solving a puzzle for yourself and to which you need to apply some character ability or other. Those boundaries are never entirely clear in Beyond Zork, and the results can be pretty ugly.

All that said, I still haven’t actually solved the idol puzzle. I guessed quite quickly that the description of standing on the idol’s maw as “like standing on a seesaw” was a vital clue. The solution, then, might be to place a counterweight at the front of the maw to keep it from pitching up and pitching me in. Yet the whole thing is so sketchily described and implemented that I remain unsure what’s actually happening. If I start piling things up inside the maw, they do fall down into the idol’s stomach along with me when I reach for the jewel — apparently, anyway; they’re not described as falling with me, but they do show up in the stomach with me once I get there. But if those things fall through, why not the jewel? If it’s sitting on the idol’s tongue, it’s hard to imagine why it wouldn’t. Or is it actually stuck to the idol’s face, and the stuff about it being in the maw is all a big mistake? Yes, we’re back to that question again. It’s worth noting that the quicksand area and the hungi therein are similarly subtly bugged. If I rescue the baby before doing something with the mother, he’s described as “ambling away into the jungle to find his mother” even though she’s right there, and, since I’ve just hopelessly screwed up, will now remain there forevermore.

The solution to the idol puzzle is clued in “The Lore and Legends of Quendor.” A hungus, it says, “will instantly charge at anything that dares to threaten its kin.” I have to attack the baby hungus and make use of the mother’s rage before rescuing her son.

>attack baby
[with the battleaxe]
Your battleaxe misses the baby hungus. It's just beyond your reach.

A sound like a snorting bull turns your attention to the mother hungus. It looks as if she's about to attack!

The mother hungus charges you. Ooof!

[Your endurance just went down.]

The baby hungus bellows helplessly, and its mother responds.

>ne
The baby hungus bellows mournfully as you walk away.


Birdcries
The unnerving cries of exotic birds echo in the treetops.

>z
Time passes.

The mother hungus storms into view!

>s
Idol
A stone idol, carved in the likeness of a giant crocodile, stands in a clearing.

You see a tear-shaped jewel in its gaping maw.

You see a tear-shaped jewel on the idol's maw.

>z

Time passes.

The mother hungus storms into view!

[Your endurance is back to normal.]

>enter maw
You climb up into the idol's maw.

The stone jaw lurches underfoot, and you struggle to keep your balance. It's like standing on a seesaw.

The mother hungus clambers onto the bottom of the idol's maw, snorting with rage!

>get jewel
The idol's maw tilts dangerously as you reach upward, standing on tiptoe to grasp the sparkling treasure...

Got it! The jewel pops off the idol's face, slips from your grasp and rolls down to the mother hungus's feet, where she promptly eats it, turns and lumbers off the jaw.

Creak! The bottom of the jaw tilts backward, pitching you helplessly forward...

Getting the jewel out of the hungus is another puzzle, but a much better one, so I won’t spoil it here. (No, it doesn’t involve a laxative…)

Spoilers end.

The sequence I’ve just described is probably the ugliest in the game, but other parts suffer to a greater or lesser degree from many of the same problems. Many of the bugs and textual confusions can doubtless be laid at the feet of an overambitious release schedule, while some of the sketchy implementation is likely down to the space limitations of even the 256 K Z-Machine. In recent correspondence with another Infocom aficionado, we talked about how Trinity, another 256 K game, really doesn’t feel all that huge, how much of the extra space was used to offer depth in the form of a larger vocabulary, richer text, and more player possibility rather than breadth in the form of more rooms and puzzles. Beyond Zork, by contrast, does feel quite huge, marks the most overstuffed game that Infocom had yet released. Considering that it must also support a full-fledged, if simplistic, CRPG engine, depth was quite obviously sacrificed in places.

But Beyond Zork‘s most fundamental failing is that of just not knowing what it wants to be. In an effort to make a game that would be all things to all people, the guaranteed hit that Infocom so desperately needed, Moriarty forgot that sometimes a game designer needs to say, no, let’s save that idea for the next project. Cognitive dissonance besets Beyond Zork from every angle. The deterministic, puzzle-oriented text adventure cuts against the dynamic, emergent CRPG. The cavalcade of in-jokes and references to earlier games, catnip for the Infocom hardcore, cuts against appealing to a newer, possibly slightly younger demographic who are fonder of CRPGs than traditional text adventures. The friendly, approachable interface cuts against a design that’s brutally cruel — sometimes apparently deliberately so, sometimes one senses (and this is in its way more damning to Brian Moriarty as a designer) accidentally so. Beyond Zork stands as an object lesson in the perils of mixing ludic genres willy-nilly without carefully analyzing the consequences. I want it to work, love many of the ideas it tries to implement. But sadly, it just doesn’t. It’s a bit of a mess really, not just difficult, which is fine, but difficult in all the wrong, unfun ways. Spellbreaker is a perfect example of how to do a nails-hard text adventure right. Beyond Zork, its parallel in the Zorkian chronology, shows how to do it all wrong. I expect more from Infocom, as, based on Wishbringer and Trinity, I do from Brian Moriarty as well.

Despite receiving plenty of favorable reviews on the basis of its considerable surface appeal, Beyond Zork didn’t turn into the hit that Infocom needed it to become. Released in October of 1987, it sold a little over 45,000 copies. Those numbers were far better than those of any of the other Infocom games of 1987, proof that the Zork name did indeed still have some commercial pull, but paled beside the best sellers of previous years, which had routinely topped 100,000 copies. Enough, combined with the uptick in sales of their other games for the Christmas season, to nudge Infocom into the black for the last quarter of 1987, Beyond Zork wasn’t enough to reverse the long-term trends that were slowly strangling them. Moriarty himself left Infocom soon after finishing Beyond Zork, tempted away by Lucasfilm Games, whose own adventure-gaming star was rising as Infocom’s fell, and where he would at last be able to fulfill his ambition to dump the parser entirely. We’ll be catching up with him again over there in due time.

(Sources: As usual with my Infocom articles, much of this one is drawn from the full Get Lamp interview archives which Jason Scott so kindly shared with me. Other sources include the book Game Design Theory and Practice by Richard Rouse III; Byte of December 1980; Questbusters of August 1987 and January 1988; Commodore Magazine of March 1988.

Beyond Zork is available for purchase as part of The Zork Anthology on GOG.com.)

 
 

Tags: , ,