The First Four

Maybe it’s the holidays, but I was recently hit by a random streak of nostalgia around my family’s first ever computer, the Commodore VIC-20. I’m guessing it was sometime around 1985 or 1986 that my dad, almost certainly inspired by another family that we became friends with, the father being a huge Commodore 64 nerd, brought us home a VIC-20. We quickly amassed some game cartridges, a tape deck and a couple of tapes filled with demos and games, a joystick, and soon enough a Zenith ZVM-123 monochrome monitor so my brother and I weren’t tying up the family TV. I thought it would be fun to go back and revisit those first four cartridge-based games. This is where it all started for me!

Fast Eddie plays exactly how you might imagine from this screen.
“Fast Eddie plays exactly how you might imagine from this screen.”

Fast Eddie is a single screen side-perspective platformer similar to more well-known titles like Lode Runner, Jumpman, and Donkey Kong. Your objective is to avoid these little mushroom looking “Sneaker” dudes while you climb ladders up and down multiple levels collecting “prizes” that appear at random. There’s a really tall Sneaker on the top level (called the “High-Top”) who will shrink in height with each prize you collect, eventually getting short enough for Eddie to jump over, which completes the stage. It’s pretty simple, but even on the VIC-20 it feels reasonably fast and responsive. The challenge is in timing your movements with the fast moving Sneakers, which is easy to do, but the faster you try to clear a level, the more likely you are to make a mistake and lose a life. I also checked out the Commodore 64 version while I was at it, which despite being more colorful with higher resolution, well, everything, doesn’t have quite the same charm as the VIC-20 version to me. Still, the more responsive and smoother feeling controls make it the superior version.

Despite the fact that I recall liking Fast Eddie as a kid, it wasn’t my favorite, nor did it get a ton of playtime in my house. I think that’s likely because, like so many early arcade style games, the formula is almost immediately obvious and doesn’t deviate much from what is established at the start in anything but difficulty. Once you “figure it out” the only real drive to keep playing is to push yourself to further levels and higher scores. That said, it is fairly addictive, and when I replayed it for the first time in preparation for writing this article, I ended up playing it for a lot longer than originally planned. Not bad!

Despite the clown car colors, killing Klingons is serious business.
“Despite the clown car colors, killing Klingons is serious business.”

I never got into this next game as a kid, likely confused by its multiple perspectives and chaotic action, but I have fond memories of my brother camping out in front of this game for hours, filling little notepads up with diagrams and drawings. Having put a fair amount of time into the game while revisiting it for this post, I’m guessing these were simply sketches of ships and maybe a log of how far he made it and his scores, because an RPG or adventure game this is not; there’s really nothing to map nor clues to jot down.

Despite its title, Star Trek: Strategic Operations Simulator is purely an arcade action game, but one that crams a fair amount of ingenuity into its simple concept. On the top left of the screen you have indicators showing your health, photon torpedoes, and warp power. On the top right, you see an overhead view of your ship and the space around it in a style very similar to Asteroids. On the bottom of the screen, you see a first person perspective from the viewscreen of your ship (I assume the USS Enterprise?) which is synchronized with the action in the top down view. Pretty nifty. You fly around these little “sectors” shooting Klingon battlecruisers who are either attacking you, or focused on attacking your starbases. You can fly to a starbase to get a small bump in health, torpedoes, and warp. Your normal attack is an unlimited, rapid fire blast that is supposed to represent your ship’s phasers, but you can also launch a torpedo which has a devastating area of effect, and warping is simply a speed boost which I actually never found all that much use for. Once you dispatch all of the enemies, hopefully saving your starbases in the process, your score is tallied up and you move to the next sector map. There are some simple boss stages every 4 or 5 sectors as well. All in all, it didn’t really hook me, but it was fun, and I can imagine some people really enjoying it.

I tried out the Commodore 64 port of the game as well, and as with most games that exist on both platforms, while the gameplay is more or less identical, the graphics and sound are greatly improved (you can actually tell what the ships are supposed to be!) and control is a little more responsive, although it’s not bad in the VIC-20 port. The experience was so much more enjoyable that I ended up playing for quite awhile, far surpassing my previous high score on the VIC-20 version. Interestingly, the original game both of these ports are based on is a 1982 Sega arcade game. The arcade game looks vaguely familiar, but I don’t think I ever played growing up. Boasting impressive hi-res vector graphics and some digitized sound samples, it looks damn cool, although the gameplay is basically the same as what is presented in the home computer versions.

Frogger with a weird perspective and terrible controls? Sign me up!
“Frogger with a weird perspective and terrible controls? Sign me up!”

Out of the four of these games, there’s only one I had almost zero recollection of and that’s because, well, we barely played it, and we barely played it because it fucking sucked. Congo Bongo is a platformer that plays like a sloppy combination of Donkey Kong, Pitfall!, and Frogger, depending on which level you play. That is, the first level has much more of a Donkey Kong vibe, while the second brings in those Frogger elements. The key difference is that the levels are shown from something of a skewed isometric perspective. Different enough to keep the lawyers away, I guess. The wacky perspective, terrible, jumpy animations which make dodging coconuts and hopping onto moving platforms feel excruciatingly inaccurate, and the less than responsive joystick controls made a game that probably already relied a bit too much on memorization just one big bum out. I ended up beating the first stage (a feat I don’t recall if I ever managed as a kid) after about a billion tries but, running out of patience, abused TheC64’s save states to get through the second. That was it though, that’s the game! In theory, those two levels repeat with a higher difficulty 4 more times, but there’s no way I was going to go any further, at least not with this version.

This game was ported all over the place, however, and morbidly curious, I decided to check out the very similar Commodore 64 version of the game. I’m happy to report that while it looks quite close, it has more colors, better sprites, better animations, slightly better sound, and vastly superior controls. The monkeys even properly harass you in this version! Still only two levels though. Interestingly, the Commodore 64 actually had a second port released a couple of years later in 1985 which had much nicer graphics sporting a much better take on the arcade version’s isometric perspective, all 4 levels from arcade, and a lot of other original elements intact. Unfortunately the cracked dump I played glitched out on the last level so I couldn’t legitimately beat it, but hey, not too shabby! In either case, I’d have been a lot more satisfied with the Commodore 64 versions of the game than I was with this awful VIC-20 one. Honestly, the best part was the awesome box with its colorful cartoony characters and massive Sega logo.

Oh, and yes, believe it or not this game was based on an arcade game. The arcade Congo Bongo actually had beautiful graphics for the time and, while I’m sure it was still a quarter sucking kick in the balls, the gameplay looks a lot smoother. As a kid I had no idea it was ever in the arcade, and I didn’t know until researching the game for this replay that there’s actually an interesting story behind the game being something of a troll of Nintendo over a lawsuit related to Donkey Kong. I’ve never seen that event referenced before, but I wonder if that’s where the Sega and Nintendo beef all started?

Actually, Spider City doesn't look half bad.
“Actually, Spider City doesn’t look half bad.”

My favorite of these games as a kid was Spider City, AKA Flash Gordon. Spider City was a side-scrolling shooter, likely influenced by the arcade classic Defender. On the top half of the screen is a view of your ship, and on the bottom a sort of mini-map showing you the tunnel system you’re navigating. The map was crucial for locating your objective, the hordes of hatching spider warriors you needed to murder. Of course, you also need to avoid debris, patrol ships, and other hazards, as well as rescue captured spacemen. I remember thinking the game looked good as a kid, but… eh? Still, of these four games it does the most with the VIC’s meager sound capabilities by a longshot.

In retrospect, dazzling graphics aside, I don’t know why it appealed to me quite so much back then, other than I remember wanting to ape my brother’s deep fascination with Star Trek: Strategic Operations Simulator by diving deep into and mastering a game of my own. That said, like Star Trek: SOS, there wasn’t actually all that much to master. Fly through the map avoiding and/or shooting everything on the screen (except for spacemen, which you could fly over to rescue) and seek out the hatching pods, mow down the hatching spiders which would hopefully grant your ship a temporary shield, then rinse and repeat until the entire map is clear. There were also these “disruptor” zones which moved around the map and would fill your screen with debris when you entered one, though you could shoot the generator inside of them to freeze them temporarily if you couldn’t simply avoid them. Of course, all of these details are fairly obtuse and unintuitive, and I’m mostly only able to talk about them clearly because I read the manual.

Unlike the rest of these games, Spider City didn’t have a Commodore 64 port. In fact, the only other place it appeared was the Atari 8-bit computers. Odd, given that it’s actually fairly fun.

These days I think I probably prefer Fast Eddie to Spider City, but I still have to give Spider City major credit for being the first video game I ever loved. Additional takeaways? While I’m endlessly grateful to my dad for bringing home my first ever personal computer, I mean, I have multiple hobbies and a career to thank for my interest in computers, I definitely wish it was a Commodore 64 instead of a VIC-20. Oh well. As an aside, I’d love to make a part two to this if I can ever figure out exactly what those cassette tapes I mentioned having were. I have no idea if they were commercial releases or otherwise widely distributed, or if some dude at whatever local computer shop my dad got this stuff from cobbled them together himself. A mystery for another day. *shrug*

Apologies for the poor quality pictures – there are some major color inaccuracies, for instance. These were photos from my TV (usually at night, even) rather than actual screenshots. Box art stolen from LaunchBox’s games database.

Diabolic

While StarCraft: Remastered seems to be pretty well regarded, not all of Blizzard’s efforts to rejuvenate their older games have been so successful. With that in mind, I was highly skeptical of Diablo II: Resurrected. It was only after hearing great things about the title from some trusted podcasters that I decided to check it out, and even then it was kind of a random, impulsive install. Regardless, I found myself getting hooked by the gameplay and story despite having played through it so many times before.

Playing a fire build was a good choice with this new lighting engine.
“Playing a fire build was a good choice with this new lighting engine.”

In short, this remastered version looks, sounds, and plays exactly how you probably remember it from back in 2000 and 2001, but the ability to dynamically toggle the graphics between the old and the new really shows just how faulty our memories can be. Knowing that the game was remastered had me engaged, trying to spot little changes and differences, and likely mistaking a lot of things I’d simply long forgotten as enhancements. I got so hooked, I ended up buying it for my Xbox Series X as well to give playing with with a controller a spin, utilizing the cross-save feature to swap between platforms whenever my mood demanded it. I didn’t play much further than the first act, but I was very impressed by the craftsmanship put into this new version, and while most of the potential to modernize some of the more dated features was skipped in favor of staying faithful to the original game, it’s hard to fault that. I’ll return to Diablo II: Resurrected one of these days, but the main reason I bailed so early was because I knew more exciting things were on the horizon.

I didn’t pay much attention to Diablo IV until relatively close to its release, when I started hearing positive things from those lucky enough to try the game during preview events. Blizzard had a couple of “server slam” stress test weekends a few months before release, and I managed to get into the very last one and try the game out for a few hours myself. I preordered the game shortly after that. That’s how much I enjoyed it.

Fending off a horde of skeletons.
“Fending off a horde of skeletons.”

Diablo IV feels, in many ways, like a love letter to Diablo II. Something of a “what if” scenario where Diablo III never happened, and the team that made Diablo II and Lord of Destruction immediately dove into developing a sequel, only after the entire studio was somehow transported 20 years into the future. This has positive and negative connotations. On the positive side, the game is an absolute return to the dark, moody tone of Diablo II. While maybe slightly less bleak, it pulls no punches in terms of showing the grim and gory world of a Sanctuary under the influence of evil: you’ll find far more corpses laying around randomly, piled in stacks, hanging from trees, and impaled on spikes than living NPCs, for example. This is also reflected in the graphical style, which resembles the 2D pixel art of Diablo II far more than the more stylized, simpler 3D models of Diablo III. The series’ sound design and particularly its music has always been consistent with what was established with the original Diablo, and Diablo IV feels continues this trend with a lot of direct throwbacks to those classic sound effects and compositions.

While I have seen the odd accusation of the game looking dated, I suspect that this is largely a side effect of trying to translate Diablo II’s look into 3D. I’m a fan. Besides the underwhelming character creator, my only nitpick is that I wish I could zoom the camera out just a tiny bit more, and we know it’s possible as many of the game’s cool in-engine cutscenes play with the camera, sometimes leaving it zoomed out further than normal. The prerendered cutscenes are absolutely amazing too, but we expect nothing less from Blizzard at this point. The aforementioned sound and especially music are masterfully executed as well. One of my telltale signs that a game has good music is when I actually notice it and stop to enjoy it, which I did more than once during my playthrough of Diablo IV’s campaign. So, that’s all good then, what about the story?

I admit it, I kind of love Lilith.
“I admit it, I kind of love Lilith.”

As a random wanderer, your character stumbles across a village that has been recently taken over by the influence of the demon Lilith. You soon meet up with some allies and the investigation of Lilith’s plot, with the eventual goal of stopping her entirely, guides the rest of your adventure. Lilith is very interesting antagonist in that, unlike your usual demonic invaders, while sure, there’s definitely an evil corruption at play, her charisma and the dogma she imparts seems to do just as much of the heavy lifting as she builds a following of humans rather than the usual shtick of simply wanting to wipe them out. In fact, she claims to want to save Sanctuary from further destruction by the machinations of and conflict between Heaven and Hell. Of course, that would mean her coming out on top, and who knows at what cost, so perhaps she’s actually just full of shit, but I like that she always comes across as a little sympathetic, and her true nature is always left at least a little ambiguous. I also loved the concept of the angel Inarius, banished to Sanctuary where a religion forms around him. In a twist to fans of the previous games, Inarius is not really an ally to your character in any real sense, and while he’s an important part of the story (particularly the backstory) he’s barely featured. Neat stuff, though the way it all wraps up comes about as close to begging for an expansion or at least a proper sequel as you can get without the story feeling unfinished.

Diablo IV also all but pretends that many of the revelations that came from Diablo III’s story didn’t happen. I don’t believe there was a single mention of Nephalem, for instance. In fact, the only real connections I picked up on (although, it has been quite a few years since playing Diablo III) were the now rather old Horadrim Lorath, and the fact that the Horadrim (and Sanctuary at large) feels particularly devastated, which makes sense after the events of Diablo III’s Reaper of Souls expansion. I could imagine this confusing if not disappointing a lot of Diablo III fans, though I for one prefer the much more serious tone of Diablo II and Diablo IV to the more fantastical, and at times flat out silly, writing of Diablo III.

Lightning Sorcs can make quite a mess.
“Lightning Sorcs can make quite a mess.”

Mechanically, Diablo IV does very little to build off of the systems that appeared in Diablo III, feeling in some ways like a bit of a step backwards. Your character feels a bit weaker and the action tends to feel a bit slower than the utter murder fests that fights in Diablo III would turn into. Skill progression is similarly old school, as you pick a number of abilities, both active and passive, from a fairly large tree, versus Diablo III’s much more stripped down progression system where you’d pick from a small selection of active abilities and apply a single modifier to them. The endgame “paragon” system does make a return from Diablo III, but is similarly much more complex. Naturally, some people will prefer Diablo III after so many years of live iteration, and some will be taken aback by Diablo IV’s slightly regressive mechanics. Personally, thanks to giving us just enough quality of life enhancements and overall polish, I think it works well. My only real gripe is that progression tends to be a bit front loaded, and by the time you near level 50, you’ll mostly be spending all of your points on relatively boring passive abilities, and after that you’ll progress to the aforementioned similarly boring and definitely more than a little convoluted paragon system.

Gear progression is in a similar boat. Diablo IV’s legendary items have “aspects” which can often have a major impact on the behavior of core class abilities, but I find myself missing some of Diablo III’s wacky, sometimes overpowered legendary weapon effects. There are a thousand other differences, as well as some Diablo II mechanics that didn’t make it in (like runes and rune words, despite there being a gem socketing system) but I suspect there’s a good chance of many of them showing up in the inevitable expansion. Not being one of those hardcore players who has sunk thousands of hours into the endgames of previous Diablo games, I don’t think I want to go too much more in-depth about the mechanics. That is to say, there are definitely better qualified people than me to provide this kind of analysis.

Welcome to the Burning Hells.
“Welcome to the Burning Hells.”

Perhaps the biggest change a casual player will notice is that Diablo’s world map is now completely open, sprawling, and filled with side content. The size and openness of the world doesn’t actually impact things too much, as the campaign questline will inevitably lead you through various regions and some of their sub-zones in a similar, albeit less linear fashion as the previous games did, and traveling isn’t too much of a chore thanks to the all too familiar system of waypoints (and when you get a horse later on, even less so.) No, the biggest issue I have with the open-world is the huge amount of side quests, dungeons, and other distractions you’ll run into in your journey. On one hand, I appreciate the content, but on the other hand, trying to complete every quest you come across and clear every dungeon you see is going to seriously derail your campaign progress. I started playing the campaign at the same time as a few colleagues of mine, and even when our playtimes were similar, I noticed I was well behind them in the campaign. It was the damn side quests! Once I started totally ignoring them and focusing exclusively on campaign quests, the game stopped feeling like so much of a slog, and I was able to dig myself out of the burnout that was setting in.

I should make a quick mention of another major change while talking about Diablo IV’s more open-world nature. The game is now something of an MMO in that you’ll run across other players in the world while playing. If you’re asocial, you shouldn’t let this concern you, as I rarely ran across anyone outside of the major cities, and even when I did, we’d almost always ignore each other and go our separate ways. There are “events” across the map (more or less the “public quest” system introduced in Warhammer Online) which work best when tackled cooperatively, but these are the only times I really played with random players. Even still though, I personally enjoy seeing other players in the world, and the opportunity for casual co-op play, random chat, and the like is pretty cool, never mind being able to fairly seamlessly play with your actual friends when you want to. I just wish this was an optional feature for those who’d rather (or can’t) always play online.

Lorath and I unloading.
“Lorath and I unloading.”

I’ve personally never been even a little enamored by Diablo’s endgame. In the original game, it was grinding for better items, sometimes with friends, and of course PKing and otherwise griefing other players. In Diablo II, it meant running through the campaign multiple times with increasing difficulty until focusing on that brutally repetitive Act V item grind, trying to find the best unique equipment, set items, and runes. Diablo III did a good job of trying to make this less of a repetitive grind by introducing “Adventure Mode” which would give players random quests to go slap a series of enemies, and rifts, which were randomly generated dungeons. Diablo IV leverages its open-world for its endgame. Since enemies are always scaled, all of that content you may have skimmed over while playing the campaign is available to grind through, as are the Tree of Whispers random quests, Helltide events, world bosses, and a number of other challenges and collect-a-thons. There’s a lot to do, although it’s a tiny bit of a bummer that so much less of the game is randomized now given that it was such a notable element of Diablo’s roguelike origins. Regardless, at the end of the day, all of these iterations come down to one thing: fairly pointless grinding. No offense to anyone who enjoys it, of course, but It’s amazing to me that Blizzard would focus so much on an endgame which is going to be so unappealing to most people. *shrug*

That’s worth mentioning, because it seems that certain types of games are judged largely by a hardcore, vocal minority of endgame players, and yet I can really like a World of Warcraft expansion, for example, based solely on its campaign and the gameplay changes I experienced therein, regardless of the raiding community thinking it’s the worst expansion to date. Diablo IV’s endgame is just one of the many popular topics that commonly pops up in criticisms of the game. It’s bizarre to me how divisive of a title Diablo IV is. Some of it, like the ridiculous cosmetics store, ham-fisted nerfs around the season 1 patch, and how slow Blizzard has been to address certain things, is legitimate, but pop into any comment or discussion thread about the game, and you’ll see a lot of people spouting absolutely ludicrous, objectively untrue nonsense about it. I guess there are tons of people always primed and ready to hate on anything Blizzard produces these days. Shame that, because while I certainly don’t believe it succeeds in taking Diablo II’s crown, I really did enjoy my time with it and will definitely be dusting it off again in the future.

Sierra On-line Books

I read and listen to a lot of books related to computer and video games, and having just finished one such book, I figured I’d make a post devoted strictly to books about the history of one of the most fondly remembered classic game companies, Sierra On-line. Fondly enough for me to talk about three different books, at least!

I’ve posted several reviews of vintage computer games over the years, and often gone into my personal history of some of these games. Sierra On-line is one particularly big component of that, as during their heyday they were without question one of my favorite developers (and when you throw in another of my all time favorites, Dynamix, one of my favorite publishers too!) Sure, LucasArts is widely agreed upon to be the victor when it comes to the fanboy favorite argument of which of the two companies made the best adventure games, but in the 90s Sierra held much more territory in the diskette and CD-ROM boxes of my personal game collection; the Space Quest series in particular being an all time favorite.

Three Books about Sierra On-line

Hackers: Heroes of the Computer Revolution by Steven Leary is surely one of my favorite non-fiction books; when I eventually stumbled upon it I honestly couldn’t believe I hadn’t read it much, much earlier in life. It covers a lot more than gaming, but of relevance here is the last third or so of the book which focuses on the shift of personal computer software development, while still somewhat rooted in enthusiast hacker culture, to a more commercial direction in the early 1980s. In particular, it mostly focuses on Ken Williams and Sierra On-line. Keeping in mind that this book was first published in 1984, this was a very contemporary look at what was then a fairly young version of Sierra, having only just released the original King’s Quest.

Of course the story of the founding of On-line Systems and the development of Mystery House is covered, but then Hackers moves into chapters devoted to Sierra’s close bonds with their peers, such as Brøderbund and Sirius Software, its “summer camp” like culture, and its gradual shift away from that and “hacker” ethics in general, along with all kinds of now legendary stories including the deal with IBM to develop for the PCjr, Richard Garriott joining Sierra, the noncompete lawsuit against Atari, and a whole lot more. The style of these later chapters is a bit different than those earlier in the book, feeling more like embedded journalism pieces than chapters in a book about computer history. Crucially, Hackers really provides a different take on who Ken Williams was and how he ran Sierra at the time than what I was familiar with. This is extremely fascinating stuff and absolutely essential for providing some eye opening accounts of those typically skimmed-over early years of the company.

I’m sure there had to be some, but I don’t know of anything else significant outside of blurbs posted in Sierra’s own manuals, guides, and magazine until 2018, when The Sierra Adventure was published. I was stoked. At long last someone put together a book about the history of the venerable Sierra On-line! The author, Shawn Mills, is a writer for Adventure Gamers and one of the founders of Infamous Quests, a throwback adventure game developer best known for Quest for Infamy and a couple of notable Sierra remakes. Respectable bonafides!

The Sierra Adventure isn’t quite the exhaustive chronicle of the history of the Sierra On-line and every last one of its products that many might be looking for in such a book. Instead, it attempts to approach the subject almost entirely from interviews with former employees. Quite a lot of notable people contributed the quotes that make up the bulk of the book’s content, though Ken and Roberta Williams themselves, still keeping a distance from all things Sierra at this point, are rarely quoted. Even still, there is enough here and I think the author put it together with enough love to make it a worthwhile read. I have to say, I was a bit annoyed with how the book starts, devoting its first chapter to flashing just a bit forward to talk about Sierra’s first couple brushes with death and how the company survived them before going back and starting at the beginning with On-line Systems and Mystery House in the next one. This kind of literary device often works quite well, but here it just came across like some kind of a bizarre editing snafu. A relatively minor gripe, I admit.

In 2020, founder and former CEO, Ken Williams himself, wrote and published Not All Fairy Tales Have Happy Endings. Part autobiography, part industry insider insight, Not All Fairy Tales Have Happy Endings is the story of Sierra On-line from the unique perspectives of Ken, and to a lesser extent, Roberta. While I did sometimes find the writing in need of a bit more editing (for example, Ken often repeats himself, especially from chapter to chapter) I quickly started to get in tune with Ken’s “voice” and ended up really enjoying his take. By the way, I originally listened to the audiobook version, and when I later got a printed book I was surprised to find it full of interesting full color pictures. Very much an upgrade!

Without a ton of detail, the book sometimes feels like just a bunch of strung together anecdotes, though it was all strung together reasonably well despite its numerous interludes. It certainly succeeded in satisfying my biggest hope for the book by filling in a lot of gaps about Ken and Roberta and the unique company culture that produced the games I loved so much. I was perhaps most intrigued by the conflict between Ken’s cold and detached approach to business: only wanting to work with “A players” and chasing monetary success, at times to the detriment of the company, with his more personable and generous side: hiring random locals to grow into very specialized positions and running the company like a big, fun family, and how that stuff all changed as he eventually ceded more of Sierra’s management and control to others as the company grew. I don’t know that Ken sees this as a “conflict” himself but, especially given Sierra’s eventual decline, it stood out to me. Speaking of which, this book gave me far more insight into the death of Sierra than anything else I’d read, with Ken providing a version of events that no one else has ever, or could ever, fully present around the CUC takeover and subsequent loss of control. It really is, as the title suggests, a bit of a cautionary tale.

Of course, Not All Fairy Tales Have Happy Endings is all from Ken’s point of view but, despite the obvious inherent bias there, his accounts do come across as sincere to me. Regardless, I’d highly recommend reading the sometimes overlapping accounts in all three of these books for a more well-rounded perspective. I’d also recommend reading them in the order I covered here; Ken even references his chapters of Hackers in Not All Fairy Tales. When taken together, we finally have as close to a complete picture of the company as we’re likely to ever have.

There you have it! Needless to say, these are far from in-depth reviews and I’d recommend Evan Dickens’s reviews and comparison between The Sierra Adventure and Not All Fairy Tales over at Adventure Gamers if you want to dive a little deeper than I did here.

This article was actually taken from my other blog, originally posted in March of 2023. Given the subject matter, I meant for this to be more of a cross-post but, hey, I guess I got a little distracted. *shrug*