If you rushed out excitedly to buy an Amiga in the early days because it looked about to revolutionize gaming, you could be excused if you felt just a little bit disappointed and underwhelmed as the platform neared its first anniversary in shops. There was a reasonable amount of entertainment software available — much of it from the Amiga’s staunchest supporter, Electronic Arts — but nothing that felt quite as groundbreaking as EA’s early rhetoric about the Amiga would imply. Even the games from EA were mostly ports of popular 8-bit titles, modestly enhanced but hardly transformed. More disappointing in their way were the smattering of original titles. Games like Arcticfox and Marble Madness had their charms, but there was nothing conceptually new about them. Degrade the graphics and sound just slightly and they too could easily pass for 8-bit games. But then, timed to neatly correspond with that one-year anniversary, along came Defender of the Crown, the Amiga’s first blockbuster and to this day the game many old-timers think of first when you mention the platform.
Digital gaming in general was a medium in flux in the mid-1980s, still trying to understand what it was and where it fit on the cultural landscape. The preferred metaphor for pundits and developers alike immediately before the Amiga era was the book; the bookware movement brought with it Interactive Fiction, Electronic Novels, Living Literature, and many other forthrightly literary branded appellations. Yet in the big picture bookware had proved to be something of a commercial dud. Defender of the Crown gave the world a new metaphorical frame, one that seemed much better suit to the spectacular audiovisual capabilities of the Amiga. Cinemaware, the company that made it, had done just what their name would imply: replaced the interactive book with the interactive movie. In the process, they blew the doors of possibility wide open. In its way Defender of the Crown was as revolutionary as the Amiga itself — or, if you like, it was the long-awaited proof of concept for the Amiga as a revolutionary technology for gaming. All this, and it wasn’t even a very good game.
The Cinemaware story begins with Bob Jacob, a serial entrepreneur and lifelong movie buff who fulfilled a dream in 1982 by selling his business in Chicago and moving along with his wife Phyllis to Los Angeles, cradle of Hollywood. With time to kill while he figured out his next move, he became fascinated with another, newer form of media: arcade and computer games. He was soon immersing himself in the thriving Southern California hacker scene. Entrepreneur that he was, he smelled opportunity there. Most of the programmers writing games around him were “not very articulate” and clueless about business. Jacob realized that he could become a go-between, a bridge between hackers and publishers who assured that the former didn’t get ripped off and that the latter had ready access to talent. He could become, in other words, a classic Hollywood agent transplanted to the brave new world of software. Jacob did indeed became a modest behind-the-scenes player over the next couple of years, brokering deals with the big players like Epyx, Activision, Spinnaker, and Mindscape for individuals and small development houses like Ultrasoft, Synergistic, Interactive Arts, and Sculptured Software. And then came the day when he saw the Amiga for the first time.
Jacob had gotten a call from a developer called Island Graphics, who had been contracted by Commodore to write a paint program to be available on Day One for the Amiga. But the two companies had had a falling out. Now Island wanted Jacob to see if he could place the project with another publisher. This he succeeded in doing, signing Island with a new would-be Amiga publisher called Aegis; Island’s program would be released as Aegis Images. (Commodore would commission R.J. Mical to write an alternate paint program in-house; it hit the shelves under Commodore’s own imprint as GraphiCraft.) Much more important to Jacob’s future, however, was his visit to Island’s tiny office and his first glimpse of the prototype Amigas they had there. Like Trip Hawkins and a handful of others, Jacob immediately understood what the Amiga could mean for the future of gaming. He understood so well, in fact, that he made a life-changing decision. He decided he wanted to be more than just an agent. Rather than ride shotgun for the revolution, he wanted to drive it. He therefore wound down his little agency practice in favor of spearheading a new gaming concept he dubbed “Cinemaware.”
Jacob has recounted on a number of occasions the deductions that led him to the Cinemaware concept. A complete Amiga system was projected to cost in the neighborhood of $2000. Few of the teenagers who currently dominated amongst gamers could be expected to have parents indulgent enough to spend that kind of money on them. Jacob therefore expected the demographic that purchased Amigas to skew upward in age — toward people like him, a comfortably well-off professional in his mid-thirties. And people like him would not only want, as EA would soon be putting it, “the visual and aural quality our sophisticated eyes and ears demand,” but also more varied and nuanced fictional experiences. They would, in other words, like to get beyond Dungeons and Dragons, The Lord of the Rings, Star Wars, and Star Trek as the sum total of their games’ cultural antecedents. At the same time, though, their preference for more varied and interesting ludic fictions didn’t necessarily imply that they wanted games that were all that demanding on their time or even their brainpower. This is the point where Jacob diverged radically from Infocom, the most prominent extant purveyor of sophisticated interactive fictions. The very first computer game that Jacob had ever bought had been Infocom’s Deadline. He hadn’t been all that taken with the experience even at the time. Now, what with its parser-based interface and all the typing that that entailed, its complete lack of audiovisual flash, its extensive manual and evidence reports that the player was expected to read before even putting the disk in the drive, and the huge demands it placed on the player hoping to actually solve its case, it served as a veritable model for what Jacob didn’t want his games to be. Other forms of entertainment favored by busy adults weren’t so demanding. Quite the opposite, in fact. His conception of adult gaming would have it be as easy-going and accessible as television. Thus one might characterize Jacob’s vision as essentially Trip Hawkins’s old dictum of “simple, hot, and deep,” albeit with a bit more emphasis on the “hot” and a bit less on the “deep.” The next important question was where to find those more varied and nuanced fictional experiences. For a movie buff living on the very doorstep of Tinsel Town, the answer must have all but announced itself of its own accord.
Bookware aside, the game industry had to some extent been aping the older, more established art form of film for a while already. The first attempt that I’m aware of to portray a computer game as an interactive movie came with Sierra’s 1982 text-adventure epic Time Zone, the advertising for which was drawn as a movie poster, complete with “Starring: You,” “Admission: $99.95,” and a rating of “UA” for “Ultimate Adventure.” It was also the first game that I’m aware of to give a credit for “Producer” and “Executive Producer.” Once adopted and popularized by Electronic Arts the following year, such movie-making terminology spread quickly all over the game industry. Now Bob Jacob was about to drive the association home with a jackhammer.
Each Cinemaware game would be an interactive version of some genre of movies, drawn from the rich Hollywood past that Jacob knew so well. If nothing else, Hollywood provided the perfect remedy for writer’s block: “Creatively it was great because we had all kinds of genres of movies to shoot for.” Many of the movie genres in which Cinemaware would work felt long-since played-out creatively by the mid-1980s, but most gaming fictions were still so crude by comparison with even the most hackneyed Hollywood productions that it really didn’t matter: “I was smart enough and cynical enough to realize that all we had to do was reach the level of copycat, and we’d be considered a breakthrough.”
Cynicism notwithstanding, the real, obvious love that Jacob and a number of his eventual collaborators had for the movies they so self-consciously evoked would always remain one of the purest, most appealing things about Cinemaware. Their manuals, scant and often almost unnecessary as they would be, would always make room for an affectionate retrospective on each game’s celluloid inspirations. At the same time, though, we should understand something else about the person Jacob was and is. He’s not an idealist or an artist, and certainly not someone who spends a lot of time fretting over games in terms of anything other than commercial entertainment. He’s someone for whom phrases like “mass-market appeal” — and such phrases tend to come up frequently in his discourse — hold nary a hint of irony or condescension. Even his love of movies, genuine as it may be, reflects his orientation toward mainstream entertainment. You’ll not find him waiting for the latest Criterion Collection release of Bergman or Truffaut. No, he favors big popcorn flicks with, well, mass-market appeal. Like so much else about Jacob, this sensibility would be reflected in Cinemaware.
Financing for a new developer wasn’t an easy thing to secure in the uncertain industry of 1985. Perhaps in response, Jacob initially conceived of his venture as a very minimalist operation, employing only himself and his wife Phyllis on a full-time basis. The other founding member of the inner circle was Kellyn Beeck, a friend, software acquisitions manager at Epyx, fellow movie buff, and frustrated game designer. The plan was to give him a chance to exorcise the latter demon with Cinemaware. Often working from Jacob’s initial inspiration, he would provide outside developers with design briefs for Cinemaware games, written in greater or lesser detail depending on the creativity and competency of said developers. When the games were finished, Jacob would pass them on to Mindscape for publication as part of the Cinemaware line. One might say that it wasn’t conceptually all that far removed from the sort of facilitation Jacob had been doing for a couple of years already as a software agent. It would keep the non-technical Jacob well-removed from the uninteresting (to him) nuts and bolts of software development. Jacob initially called his company Master Designer Software, reflecting both an attempt to “appeal to the ego of game designers” and a hope that, should the Cinemaware stuff turn out well, he might eventually launch other themed lines. Cinemaware would, however, become such a strong brand in its own right in the next year or two that Jacob would end up making it the name of his company. I’ll just call Jacob’s operation “Cinemaware” from now on, as that’s the popular name everyone would quickly come to know it under even well before the official name change.
After nearly a year of preparation, Jacob pulled the trigger on Cinemaware at last in January of 1986, when in a matter of a few days he legally formed his new company, signed a distribution contract with Mindscape, and signed contracts with outsiders to develop the first four Cinemaware games, to be delivered by October 15, 1986 — just in time for Christmas. Two quite detailed design briefs went to Sculptured Software of Salt Lake City, a programming house that had made a name for themselves as a porter of games between platforms. Of Sculptured’s Cinemaware projects, Defender of the Crown, the title about which Jacob and Beeck were most excited, was inspired by costume epics of yesteryear featuring legendary heroes like Ivanhoe and Robin Hood, while SDI was to be a game involving Ronald Reagan’s favorite defense program and drawing its more tenuous cinematic inspiration from science-fiction classics ranging from the Flash Gordon serials of the 1930s to the recent blockbuster Star Trek II: The Wrath of Khan. The other two games went to proven lone-wolf designer/programmers, last of a slowly dying breed, and were outlined in much broader strokes. King of Chicago, given to a programmer named Doug Sharp who had earlier written a game called ChipWits, an interesting spiritual successor to Silas Warner’s classic Robot War, was to be an homage to gangster movies. And Sinbad and the Throne of the Falcon was given to one Bill Williams, who had earlier written such Atari 8-bit hits as Necromancer and Alley Cat and had just finished the first commercial game ever released for the Amiga, Mind Walker. His game would be an homage to Hollywood’s various takes on the Arabian Nights. Excited though he was by the Amiga, Jacob hedged his bets on his platforms just as he did on his developers, planning to get at least one title onto every antagonist in the 68000 Wars before 1986 was out. Only Defender of the Crown and Sinbad were to be developed and released first on the Amiga; King of Chicago would be written on the Macintosh, SDI on the Atari ST. If all went well, ports could follow.
All of this first wave of Cinemaware games as well as the ones that would follow will get their greater or lesser due around here in articles to come. Today, though, I want to concentrate on the most historically important if certainly not the best of Cinemaware’s works, Defender of the Crown.
Defender of the Crown, then, takes place in a version of medieval England that owes far more to cinema than it does to history. As in romantic depictions of Merry Olde England dating back at least to Walter Scott’s Ivanhoe, the stolid English Saxons are the heroes here, the effete French Normans — despite being the historical victors in the struggle for control of England — the villains. Thus you play a brave Saxon lord struggling against his Norman oppressors. Defender of the Crown really doesn’t make a whole lot of sense as history, fiction, or legend. A number of its characters are drawn from Ivanhoe, which might lead one to conclude that it’s meant to be a sequel to that book, taking place after Richard I’s death has thrown his kingdom into turmoil once again. But if that’s the case then why is Reginald Front-de-Boeuf, who was killed in Ivanhoe, running around alive and well again? Should you win Defender of the Crown, you’ll be creating what amounts to an alternate history in which the Saxons throw off the Norman yoke and regain control of England. Suffice to say that the only history that Defender of the Crown is really interested in is the history of Hollywood. What it wants to evoke is not the England of myth or reality, but the England of the movies so lovingly described in its manual. It has no idea where it stands in relation to Ivanhoe or much of anything else beyond the confines of a Hollywood sound stage, nor does it care. Given that, why should we? So, let’s agree to just go with it.
Defender of the Crown is essentially Risk played on a map of England. The other players in the game include three of the hated Normans and two other Saxon lords, who generally try to avoid attacking their ethnic fellows unless space starts getting really tight. Your goal is of course to wipe the Normans from the map and make of England a Saxon kingdom again. Woven into the simple Risk-like strategy game are a handful of action-oriented minigames that can be triggered by your own actions or those of the other lords: a grand jousting tournament, a midnight raid on an enemy castle, a full-on siege complete with a catapult that you use to knock down a beleaguered castle’s walls. In keeping with Jacob’s vision of Cinemaware games as engaging but light entertainments, a full game usually takes well under an hour to play, and there is no provision for saving or restoring.
From the beginning, it was Jacob’s intention to really pull out all the stops for Defender of the Crown in particular amongst his launch titles, to make of it an audiovisual showcase the likes of which had never been seen before. Shortly after signing Sculptured Software to do the programming, he therefore signed Jim Sachs to work with them, giving him a title familiar to Hollywood but new to the world of games: Art Director.
A self-taught artist from childhood and a programmer since he’d purchased a Commodore 64 just a few years before, Sachs had made quite a name for himself in quite a short time in Commodore circles. He’d written and released a game of his own for the Commodore 64, Saucer Attack, that mixed spectacular graphics with questionable gameplay (an accusation soon to be leveled against Defender of the Crown as well). He’d then spent a year working on another game, to be called Time Crystal, that never got beyond a jawdropping demo that made the rounds of Commodore 64 BBSs for years. He’d been able to use this demo and Saucer Attack to convince Commodore to give him developer’s status for the Amiga, allowing him access to pre-release hardware. Sach’s lovely early pictures were amongst the first to be widely distributed amongst Amiga users, making him the most well-known of the Amiga’s early hacker artists prior to Eric Graham flooring everyone with his Juggler animation in mid-1986. Indeed, Sachs was quite possibly the best Amiga painter in the world when Jacob signed him up to do Defender of the Crown — Andy Warhol included. He would become the most important single individual to work on the game. If it was unusual for an artist to become the key figure behind a game, that itself was an illustration of what made Cinemaware — and particularly Defender of the Crown — so different from what had come before. As he himself was always quick to point out, Sachs by no means personally drew every single one of the many lush scenes that make up the game. At least seven others contributed art, an absolutely huge number by the standards of the time, and another sign of what made Defender of the Crown so different from everything that had come before. It is fair to say, however, that Sachs’s virtual brush swept over every single one of the game’s scenes, tweaking a shadow here, harmonizing differing styles there. His title of Art Director was very well-earned.
By June of 1986 Sachs and company had provided Sculptured Software with a big pile of mouth-watering art, but Sculptured had yet to demonstrate to Jacob even the smallest piece of a game incorporating any of it. Growing concerned, Jacob flew out to Salt Lake City to check on their progress. What he found was a disaster: “Those guys were like nowhere. Literally nowhere.” Their other game for Cinemaware, SDI, was relatively speaking further along, but also far behind schedule. It seemed that this new generation of 68000-based computers had proved to be more than Sculptured had bargained for.
Desperate to meet his deadline with Mindscape, Jacob took the first steps toward his eventual abandonment of his original concept of Cinemaware as little more than a creative director and broker between developer and publisher. He hired his first actual employee beyond himself and Phyllis, a fellow named John Cutter who had just been laid off following Activision’s acquisition of his previous employer Gamestar, a specialist in sports games. Cutter, more technical and more analytical than Jacob, would become his right-hand man and organizer-in-chief for Cinemaware’s many projects to come. His first task was to remove Sculptured Software entirely from Defender of the Crown; S.D.I. they were allowed to keep, but from now on they’d work on it under close supervision from Cutter. Realizing he needed someone who knew the Amiga intimately to have a prayer of completing Defender of the Crown by October 15, Jacob called up none other than R.J. Mical, developer of Intuition and GraphiCraft, and made him an offer: $26,000 if he could take Sachs’s pile of art and Jacob and Beeck’s design, plus a bunch of music Jacob had commissioned from a composer named Jim Cuomo, and turn it all into a finished game within three months. Mical simply said — according to Jacob — “I’m your man.”
He got it done, even if it did nearly kill him. Mical insists to this day that Jacob wasn’t straight with him about the project, that the amount of work it ended up demanding of him was far greater than what he had been led to expect when he agreed to do the job. He was left so unhappy by his rushed final product that he purged his own name from the in-game credits. Sachs also is left with what he calls a “bitter taste,” feeling Jacob ended up demanding far, far more work from him than was really fair for the money he was paid. Many extra graphical flourishes and entire additional scenes that Mical simply didn’t have time or space to incorporate into the finished product were left on the cutting-room floor. Countless 20-hour days put in by Sachs and his artists thus went to infuriating waste in the name of meeting an arbitrary deadline. Sachs claims that five man-weeks work worth of graphics were thrown out for the jousting scenes alone. Neither Sachs nor Mical would ever work with Cinemaware again.
Many gameplay elements were also cut, while even much of what did make it in has an unfinished feel about it. Defender of the Crown manages the neat trick of being both too hard and too easy. What happens on the screen in the various action minigames feels peculiarly disconnected from what you actually do with the mouse. I’m not sure anyone has ever entirely figured out how the jousting or swordfighting games are even supposed to work; random mouse twiddling and praying would seem to be the only viable tactics. And yet the Risk-style strategic game is almost absurdly easy. Most players win it — and thus Defender of the Crown as a whole — on their second if not their first try, and then never lose again.
Given this, it would be very easy to dismiss Defender of the Crown entirely. And indeed, plenty of critics have done just that, whilst often tossing the rest of Cinemaware’s considerable catalog into the trash can of history alongside it. But, as the length of this article would imply, I’m not quite willing to do that. I recognize that Defender of the Crown isn’t really up to much as a piece of game design, yet even today that doesn’t seem to matter quite as much as it ought to. Simplistic and kind of broken as it is, it’s still a more entertaining experience today than it ought to be — certainly enough so to be worth a play or two. And back in 1986… well, I united England under the Saxon banner a ridiculous number of times as a kid, long after doing so became rote. In thinking about Defender of the Crown‘s appeal, I’ve come to see it as representing an important shift not just in the way that games are made but also in the way that we experience them. To explain what I mean I need to get a bit theoretical with you, just for a moment.
Whilst indulging in a bit of theory in an earlier article, I broke down a game into three component parts: its system of rules and mechanics, its “surface” or user interface, and its fictional context. I want to set aside the middle entry in that trio and just think about rules and context today. As I also wrote in that earlier article, the rise in earnest of what I call “experiential games” from the 1950s onward is marked by an increased interest in the latter in comparison to the former, as games became coherent fictional experiences to be lived rather than mere abstract systems to be manipulated in pursuit of a favorable outcome. I see Defender of the Crown and the other Cinemaware games as the logical endpoint of that tendency. In designing the game, Bob Jacob and Kellyn Beeck started not with a mechanical concept — grand strategy, text adventure, arcade action, etc. — but with a fictional context: a recreation of those swashbuckling Hollywood epics of yore. That the mechanical system they came up with to underlie that fiction — a simplified game of Risk peppered by equally simplistic action games — is loaded with imperfections is too bad but also almost ancillary to Defender of the Crown the experience. The mechanics do the job just well enough to make themselves irrelevant. No one comes to Defender of the Crown to play a great strategy game. They come to immerse themselves in the Merry Olde England of bygone Hollywood.
For many years now there have been voices stridently opposed to the emphasis a game like Defender of the Crown places on its its fictional context, with the accompanying emphasis on foreground aesthetics necessary to bring that context to life. Chris Crawford, for instance, dismisses not just this game but Cinemaware as a whole in one paragraph in On Game Design as “lots of pretty pictures and animated sequences” coupled to “weak” gameplay. Gameplay is king, we’re told, and graphics and music and all the rest don’t — or shouldn’t — matter a whit. Crawford all but critically ranks games based entirely on what he calls their “process intensity”: their ratio of dynamic, interactive code — i.e., gameplay — to static art, sound, music, even text. If one accepts this point of view in whole or in part, as many of the more prominent voices in game design and criticism tend to do, it does indeed become very easy to dismiss the entire oeuvre of Cinemaware as a fundamentally flawed concept and, worse, a dangerous one, a harbinger of further design degradations to come.
Speaking here as someone with an unusual tolerance for ugly graphics — how else could I have written for years now about all those ugly 8-bit games? — I find that point of view needlessly reductive and rather unfair. Leaving aside that beauty for its own sake, whether found in a game or in an art museum, is hardly worthy of our scorn, the reality is that very few modern games are strictly about their mechanics. Many have joined Defender of the Crown as embodied fictional experiences. This is the main reason that many people play them today. If beautiful graphics help us to feel embodied in a ludic world, bully for them. I’d argue that the rich graphics in Defender of the Crown carry much the same water as the rich prose in, say, Mindwheel or Trinity. Personally — and I understand that mileages vary here — I’m more interested in becoming someone else or experiencing — there’s that word again! — something new to me for a while than I am in puzzles, strategy, or reflex responses in the abstract. I’d venture to guess that most gamers are similar. In some sense modern games have transcended games — i.e., a system of rules and mechanics — as we used to know them. Commercial and kind of crass as it sometimes is, we can see Defender of the Crown straining toward becoming an embodied, interactive, moving, beautiful, fictional experience rather than being just the really bad take on Risk it unquestionably also is.
A good illustration of Defender of the Crown‘s appeal as an experiential fiction as well as perhaps a bit of that aforementioned crassness is provided by the game’s much-discussed romantic angle. No Hollywood epic being complete without a love interest for the dashing hero, you’ll likely at some point during your personal epic get the opportunity to rescue a Saxon damsel in distress from the clutches of a dastardly Norman. We all know what’s bound to happen next: “During the weeks that follow, gratitude turns to love. Then, late one night…”
After the affair is consummated, your new gal accompanies you through the rest of the game. It’s important to note here that she has no effect one way or the other on your actual success in reconquering England, and that rescuing her is actually one of the more difficult things to do in Defender of the Crown, as it requires that you engage with the pretty terrible swordfighting game; I can only pull it off if I pick as my character Geoffrey Longsword, appropriately enough the hero with “Strong” swordfighting skills. Yet your game — your story — somehow feels incomplete if you don’t manage it. What good is a hero without a damsel to walk off into the sunset with him? There are several different versions of the virgin (sorry!) that show up, just to add a bit of replay value for the lovelorn.
As I’ve written earlier, 1986 was something of a banner year for sex in videogames. The love scene in Defender of the Crown, being much more, um, graphic than the others, attracted particular attention. Many a youngster over the years to come would have his dreams delightfully haunted by those damsels. Shortly after the game’s release, Amazing Computing published an unconfirmed report from an “insider” that the love scene was originally intended to be interactive, requiring “certain mouse actions to coax the fair woman, who reacted accordingly. After consulting with game designers and project management, the programmer supposedly destroyed all copies of the source code to that scene.” Take that with what grains of salt you will. At any rate, a sultry love interest would soon become a staple of Cinemaware games, for the very good reason that the customers loved them. And anyway, Jacob himself, as he later admitted in a revelation bordering on Too Much Information, “always liked chesty women.” It was all horribly sexist, of course, something Amazing Computing pointed out by declaring Defender of the Crown the “most anti-woman game of the year.” On the other hand, it really wasn’t any more sexist than its cinematic inspirations, so I suppose it’s fair enough when taken in the spirit of homage.
The buzz about Defender of the Crown started inside Amiga circles even before the game was done. An early build was demonstrated publicly for the first time at the Los Angeles Commodore Show in September of 1986; it attracted a huge, rapt crowd. Released right on schedule that November through Mindscape, Defender of the Crown caused a sensation. Amiga owners treated it as something like a prophecy fulfilled; this was the game they’d all known the Amiga was capable of, the one they’d been waiting for, tangible proof of their chosen platform’s superiority over all others. And it became an object of lust — literally, when the gorgeously rendered Saxon maidens showed up — for those who weren’t lucky enough to own Commodore’s wunderkind. You could spend lots of time talking about all of the Amiga’s revolutionary capabilities — or you could just pop Defender of the Crown in the drive, sit back, and watch the jaws drop. The game sold 20,000 copies before the end of 1986 alone, astounding numbers considering that the total pool of Amiga owners at that point probably didn’t number much more than 100,000. I feel pretty confident in saying that just about every one of those 80,000 or so Amiga owners who didn’t buy the game right away probably had a pirated copy soon enough. It would go on to sell 250,000 copies, the “gift that kept on giving” for Jacob and Cinemaware for years to come. While later Cinemaware games would be almost as beautiful and usually much better designed — not to mention having the virtue of actually being finished — no other would come close to matching Defender of the Crown‘s sales numbers or its public impact.
Cinemaware ported Defender of the Crown to a plethora of other platforms over the next couple of years. Ironically, virtually all of the ports were much better game games than the Amiga version, fixing the minigames to make them comprehensible and reasonably entertaining and tightening up the design to make it at least somewhat more difficult to sleepwalk to victory. In a sense, it was Atari ST users who got the last laugh. That, anyway, is the version that some aficionados name as the best overall: the graphics and sound aren’t quite as good, but the game behind them has been reworked with considerable aplomb. Even so, it remained and remains the Amiga version that most people find most alluring. Without those beautiful graphics, there just doesn’t seem to be all that much point to Defender of the Crown. Does this make it a gorgeous atmospheric experience that transcends its game mechanics or just a broken, shallow game gussied up with lots of pretty pictures? Perhaps it’s both, or neither. Artistic truth is always in the eye of the beholder. But one thing is clear: we’ll be having these sorts of discussions a lot as we look at games to come. That’s the real legacy of Defender of the Crown — for better or for worse.
(Sources: On the Edge by Brian Bagnall; Computer Gaming World of January/February 1985, March 1987 and August/September 1987; Amazing Computing #1.9, February 1987, April 1987, and July 1987; Commodore Magazine of October 1987 and November 1988; AmigaWorld of November/December 1986. Jim Sachs has been interviewed in more recent years by Kamil Niescioruk and The Personal Computer Museum. Matt Barton and Tristan Donovan have each interviewed Bob Jacob for Gamasutra.
Defender of the Crown is available for purchase for Windows and Mac from GOG.com, in the Apple Store for iOS, and on Google Play for Android for those of you wanting to visit Merry Olde England for yourselves. All emulate the historically definitive if somewhat broken Amiga version, featuring the original Amiga graphics and sound.)