RSS

Tag Archives: GEnie

The Rise of POMG, Part 1: It Takes a Village…

No one on their deathbed ever said, “I wish I had spent more time alone with my computer!”

— Dani Bunten Berry

If you ever want to feel old, just talk to the younger generation.

A few years ago now, I met the kids of a good friend of mine for the very first time: four boys between the ages of four and twelve, all more or less crazy about videogames. As someone who spends a lot of his time and earns a lot of his income writing about games, I arrived at their house with high expectations attached.

Alas, I’m afraid I proved a bit of a disappointment to them. The distance between the musty old games that I knew and the shiny modern ones that they played was just too far to bridge; shared frames of reference were tough to come up with. This was more or less what I had anticipated, given how painfully limited I already knew my knowledge of modern gaming to be. But one thing did genuinely surprise me: it was tough for these youngsters to wrap their heads around the very notion of a game that you played to completion by yourself and then put on the shelf, much as you might a book. The games they knew, from Roblox to Fortnite, were all social affairs that you played online with friends or strangers, that ended only when you got sick of them or your peer group moved on to something else. Games that you played alone, without at the very least leader boards and achievements on-hand to measure yourself against others, were utterly alien to them. It was quite a reality check for me.

So, I immediately started to wonder how we had gotten to this point — a point not necessarily better or worse than the sort of gaming that I knew growing up and am still most comfortable with, just very different. This series of articles should serve as the beginning of an answer to that complicated question. Their primary focus is not so much how computer games went multiplayer, nor even how they first went online; those things are in some ways the easy, obvious parts of the equation. It’s rather how games did those things persistently — i.e., permanently, so that each session became part of a larger meta-game, if you will, embedded in a virtual community. Or perhaps the virtual community is embedded in the game. It all depends on how you look at it, and which precise game you happen to be talking about. Whichever way, it has left folks like me, whose natural tendency is still to read games like books with distinct beginnings, middles, and ends, anachronistic iconoclasts in the eyes of the youthful mainstream.

Which, I hasten to add, is perfectly okay; I’ve always found the ditch more fun than the middle of the road anyway. Still, sometimes it’s good to know how the other 90 percent lives, especially if you claim to be a gaming historian…



“Persistent online multiplayer gaming” (POMG, shall we say?) is a mouthful to be sure, but it will have to do for lack of a better descriptor of the phenomenon that has created such a divide between myself and my friend’s children.  It’s actually older than you might expect, having first come to be in the 1970s on PLATO, a non-profit computer network run out of the University of Illinois but encompassing several other American educational institutions as well. Much has been written about this pioneering network, which uncannily presaged in so many of its particulars what the Internet would become for the world writ large two decades later. (I recommend Brian Dear’s The Friendly Orange Glow for a book-length treatment.) It should suffice for our purposes today to say that PLATO became host to, among other online communities of interest, an extraordinarily vibrant gaming culture. Thanks to the fact that PLATO games lived on a multi-user network rather than standalone single-user personal computers, they could do stuff that most gamers who were not lucky enough to be affiliated with a PLATO-connected university would have to wait many more years to experience.

The first recognizable single-player CRPGs were born on PLATO in the mid-1970s, inspired by the revolutionary new tabletop game known as Dungeons & Dragons. They were followed by the first multiplayer ones in amazingly short order. Already in 1975’s Moria,[1]The PLATO Moria was a completely different game from the 1983 single-player roguelike that bore the same name. players met up with their peers online to chat, brag, and sell or trade loot to one another. When they were ready to venture forth to kill monsters, they could do so in groups of up to ten, pooling their resources and sharing the rewards. A slightly later PLATO game called Oubliette implemented the same basic concept in an even more sophisticated way. The degree of persistence of these games was limited by a lack of storage capacity — the only data that was saved between sessions were the statistics and inventory of each player’s character, with the rest of the environment being generated randomly each time out — but they were miles ahead of anything available for the early personal computers that were beginning to appear at the same time. Indeed, Wizardry, the game that cemented the CRPG’s status as a staple genre on personal computers in 1981, was in many ways simply a scaled-down version of Oubliette, with the multiplayer party replaced by a party of characters that were all controlled by the same player.

Chester Bolingbroke, better known online as The CRPG Addict, plays Moria. Note the “Group Members” field at bottom right. Chester is alone here, but he could be adventuring with up to nine others.

A more comprehensive sort of persistence arrived with the first Multi-User Dungeon (MUD), developed by Roy Trubshaw and Richard Bartle, two students at the University of Essex in Britain, and first deployed there in a nascent form in late 1978 or 1979. A MUD borrowed the text-only interface and presentation of Will Crowther and Don Woods’s seminal game of Adventure, but the world it presented was a shared, fully persistent one between its periodic resets to a virgin state, chockablock with other real humans to interact with and perhaps fight. “The Land,” as Bartle dubbed his game’s environs, expanded to more than 600 rooms by the early 1980s, even as its ideas and a good portion of its code were used to set up other, similar environments at many more universities.

In the meanwhile, the first commercial online services were starting up in the United States. By 1984, you could, for the price of a substantial hourly fee, dial into the big mainframes of services like CompuServe using your home computer. Once logged in there, you could socialize, shop, bank, make travel reservations, read newspapers, and do much else that most people wouldn’t begin to do online until more than a decade later — including gaming. For example, CompuServe offered MegaWars, a persistent grand-strategy game of galactic conquest whose campaigns took groups of up to 100 players four to six weeks to complete. (Woe betide the ones who couldn’t log in for some reason of an evening in the midst of that marathon!) You could also find various MUDs, as well as Island of Kesmai, a multiplayer CRPG boasting most of the same features as PLATO’s Oubliette in a genuinely persistent world rather than a perpetually regenerated one. CompuServe’s competitor GEnie had Air Warrior, a multiplayer flight simulator with bitmapped 3D graphics and sound effects to rival any of the contemporaneous single-player simulators on personal computers. For the price of $11 per hour, you could participate in grand Air Warrior campaigns that lasted three weeks each and involved hundreds of other subscribers, organizing and flying bombing raids and defending against the enemy’s attacks on their own lines. In 1991, America Online put up Neverwinter Nights,[2]Not the same game as the 2002 Bioware CRPG of the same name. which did for the “Gold Box” line of licensed Dungeons & Dragons CRPGs what MUD had done for Adventure and Air Warrior had done for flight simulators, transporting the single-player game into a persistent multiplayer space.

All of this stuff was more or less incredible in the context of the times. At the same time, though, we mustn’t forget that it was strictly the purview of a privileged elite, made up of those with login credentials for institutional-computing networks or money in their pockets to pay fairly exorbitant hourly fees to feed their gaming habits. So, I’d like to back up now and tell a different story of POMG — one with more of a populist thrust, focusing on what was actually attainable by the majority of people out there, the ones who neither had access to a university’s mainframe nor could afford to spend hundreds of dollars per month on a hobby. Rest assured that the two narratives will meet before all is said and done.



POMG came to everyday digital gaming in the reverse order of the words that make up the acronym: first games were multiplayer, then they went online, and then these online games became persistent. Let’s try to unpack how that happened.

From the very start, many digital games were multiplayer, optionally if not unavoidably so. Spacewar!, the program generally considered the first fully developed graphical videogame, was exclusively multiplayer from its inception in the early 1960s. Ditto Pong, the game that launched Atari a decade later, and with it a slow-building popular craze for electronic games, first in public arcades and later in living rooms. Multiplayer here was not so much down to design intention as technological affordances. Pong was an elaborate analog state machine rather than a full-blown digital computer, relying on decentralized resistors and potentiometers and the like to do its “thinking.” It was more than hard enough just to get a couple of paddles and a ball moving around on the screen of a gadget like this; a computerized opponent was a bridge too far.

Very quickly, however, programmable microprocessors entered the field, changing everyone’s cost-benefit analyses. Building dual controls into an arcade cabinet was expensive, and the end result tended to take up a lot of space. The designers of arcade classics like Asteroids and Galaxian soon realized that they could replace the complications of a human opponent with hordes of computer-controlled enemies, flying in rudimentary, partially randomized patterns. Bulky multiplayer machines thus became rarer and rarer in arcades, replaced by slimmer, more standardized single-player cabinets. After all, if you wanted to compete with your friends in such games, there was still a way to do so: you could each play a round against the computerized enemies and compare your scores afterward.

While all of this was taking shape, the Trinity of 1977 — the Radio Shack TRS-80, Apple II, and Commodore PET — had ushered in the personal-computing era. The games these early microcomputers played were sometimes ports or clones of popular arcade hits, but just as often they were more cerebral, conceptually ambitious affairs where reflexes didn’t play as big — or any — role: flight simulations, adventure games, war and other strategy games. The last were often designed to be played optimally or even exclusively against another human, largely for the same reason Pong had been made that way: artificial intelligence was a hard thing to implement under any circumstances on an 8-bit computer with as little as 16 K of memory, and it only got harder when you were asking said artificial intelligence to formulate a strategy for Operation Barbarossa rather than to move a tennis racket around in front of a bouncing ball. Many strategy-game designers in these early days saw multiplayer options almost as a necessary evil, a stopgap until the computer could fully replace the human player, thus alleviating that eternal problem of the war-gaming hobby on the tabletop: the difficulty of finding other people in one’s neighborhood who were able and willing to play such weighty, complex games.

At least one designer, however, saw multiplayer as a positive advantage rather than a kludge — in fact, as the way the games of the future by all rights ought to be. “When I was a kid, the only times my family spent together that weren’t totally dysfunctional were when we were playing games,” remembered Dani Bunten Berry. From the beginning of her design career in 1979, when she made an auction game called Wheeler Dealers for the Apple II,[3]Wheeler Dealers and all of her other games that are mentioned in this article were credited to Dan Bunten, the name under which she lived until 1992. multiplayer was her priority. In fact, she was willing to go to extreme lengths to make it possible; in addition to a cassette tape containing the software, Wheeler Dealers shipped with a custom-made hardware add-on, the only method she could come up with to let four players bid at once. Such experiments culminated in M.U.L.E., one of the first four games ever published by Electronic Arts, a deeply, determinedly social game of economics and, yes, auctions for Atari and Commodore personal computers that many people, myself included, still consider her unimpeachable masterpiece.

A M.U.L.E. auction in progress.

And yet it was Seven Cities of Gold, her second game for Electronic Arts, that became a big hit. Ironically, it was also the first she had ever made with no multiplayer option whatsoever. She was learning to her chagrin that games meant to be played together on a single personal computer were a hard sell; such machines were typically found in offices and bedrooms, places where people went to isolate themselves, not in living rooms or other spaces where they went to be together. She decided to try another tack, thereby injecting the “online” part of POMG into our discussion.

In 1988, Electronic Arts published Berry’s Modem Wars, a game that seems almost eerily prescient in retrospect, anticipating the ludic zeitgeist of more than a decade later with remarkable accuracy. It was a strategy game played in real time (although not quite a real-time strategy of the resource-gathering and army-building stripe that would later be invented by Dune II and popularized by Warcraft and Command & Conquer). And it was intended to be played online against another human sitting at another computer, connected to yours by the gossamer thread of a peer-to-peer modem hookup over an ordinary telephone line. Like most of Berry’s games, it didn’t sell all that well, being a little too far out in front of the state of her nation’s telecommunications infrastructure.

Nevertheless, she continued to push her agenda of computer games as ways of being entertained together rather than alone over the years that followed. She never did achieve the breakout hit she craved, but she inspired countless other designers with her passion. She died far too young in 1998, just as the world was on the cusp of embracing her vision on a scale that even she could scarcely have imagined. “It is no exaggeration to characterize her as the world’s foremost authority on multiplayer computer games,” said Brian Moriarty when he presented Dani Bunten Berry with the first ever Game Developers Conference Lifetime Achievement Award two months before her death. “Nobody has worked harder to demonstrate how technology can be used to realize one of the noblest of human endeavors: bringing people together. Historians of electronic gaming will find in these eleven boxes [representing her eleven published games] the prototypes of the defining art form of the 21st century.” Let this article and the ones that will follow it, written well into said century, serve as partial proof of the truth of his words.

Danielle Bunten Berry, 1949-1998.

For by the time Moriarty spoke them, other designers had been following the trails she had blazed for quite some time, often with much more commercial success. A good early example is Populous, Peter Molyneux’s strategy game in real time (although, again, not quite a real-time strategy) that was for most of its development cycle strictly a peer-to-peer online multiplayer game, its offline single-player mode being added only during the last few months. An even better, slightly later one is DOOM, John Carmack and John Romero’s game of first-person 3D mayhem, whose star attraction, even more so than its sadistic single-player levels, was the “deathmatch” over a local-area network. Granted, these testosterone-fueled, relentlessly zero-sum contests weren’t quite the same as what Berry was envisioning for gaming’s multiplayer future near the end of her life; she wished passionately for games with a “people orientation,” directed toward “the more mainstream, casual players who are currently coming into the PC market.” Still, as the saying goes, you have to start somewhere.

But there is once more a caveat to state here about access, or rather the lack thereof. Being built for local networks only — i.e., networks that lived entirely within a single building or at most a small complex of them — DOOM deathmatches were out of reach on a day-to-day basis for those who didn’t happen to be students or employees at institutions with well-developed data-processing departments and permissive or oblivious authority figures. Outside of those ivory towers, this was the era of the “LAN party,” when groups of gamers would all lug their computers over to someone’s house, wire them together, and go at it over the course of a day or a weekend. These occasions went on to become treasured memories for many of their participants, but they achieved that status precisely because they were so sporadic and therefore special.

And yet DOOM‘s rise corresponded with the transformation of the Internet from an esoteric tool for the technological elite to the most flexible medium of communication ever placed at the disposal of the great unwashed, thanks to a little invention out of Switzerland called the World Wide Web. What if there was a way to move DOOM and other games like it from a local network onto this one, the mother of all wide-area networks? Instead of deathmatching only with your buddy in the next cubicle, you would be able to play against somebody on another continent if you liked. Now wouldn’t that be cool?

The problem was that local-area networks ran over a protocol known as IPX, while the Internet ran on a completely different one called TCP/IP. Whoever could bridge that gap in a reasonably reliable, user-friendly way stood to become a hero to gamers all over the world.



Jay Cotton discovered DOOM in the same way as many another data-processing professional: when it brought down his network. He was employed at the University of Georgia at the time, and was assigned to figure out why the university’s network kept buckling under unprecedented amounts of spurious traffic. He tracked the cause down to DOOM, the game that half the students on campus seemed to be playing more than half the time. More specifically, the problem was caused by a bug, which was patched out of existence by John Carmack as soon as he was informed. Problem solved. But Cotton stuck around to play, the warden seduced by the inmates of the asylum.

He was soon so much better at the game than anyone else on campus that he was getting a bit bored. Looking for worthier opponents, he stumbled across a program called TCPSetup, written by one Jake Page, which was designed to translate IPX packets into TCP/IP ones and vice versa on the fly, “tricking” DOOM into communicating across the vast Internet. It was cumbersome to use and extremely unreliable, but on a good day it would let you play DOOM over the Internet for brief periods of time at least, an amazing feat by any standard. Cotton would meet other players on an Internet chat channel dedicated to the game, they’d exchange IP addresses, and then they’d have at it — or try to, depending on the whims of the Technology Gods that day.

On August 22, 1994, Cotton received an email from a fellow out of the University of Illinois — yes, PLATO’s old home — whom he’d met and played in this way (and beaten, he was always careful to add). His name was Scott Coleman. “I have some ideas for hacking TCPSetup to make it a little easier. Care to do some testing later?” Coleman wrote. “I’ve already emailed Jake [Page] on this, but he hasn’t responded (might be on vacation or something). If he approves, I’m hoping some of these ideas might make it into the next release of TCPSetup. In the meantime, I want to do some experimenting to see what’s feasible.”

Jake Page never did respond to their queries, so Cotton and Coleman just kept beavering away on their own, eventually rewriting TCPSetup entirely to create iDOOM, a more reliable and far less fiddly implementation of the same concept, with support for three- or four-player deathmatches instead of just one-on-one duels. It took off like a rocket; the pair were bombarded with feature requests, most notably to make iDOOM work with other IPX-only games as well. In January of 1995, they added support for Heretic, one of the most popular of the first wave of so-called “DOOM clones.” They changed their program’s name to “iFrag” to reflect the fact that it was now about more than just DOOM.

Having come this far, Cotton and Coleman soon made the conceptual leap that would transform their software from a useful tool to a way of life for a time for many, many thousands of gamers. Why not add support for more games, they asked themselves, not in a bespoke way as they had been doing to date, but in a more sustainable one, by turning their program into a general-purpose IPX-to-TCP/IP bridge, suitable for use with the dozens of other multiplayer games out there that supported only local-area networks out of the box. And why not make their tool into a community while they were at it, by adding an integrated chat service? In addition to its other functions, the program could offer a list of “servers” hosting games, which you could join at the click of a button; no more trolling for opponents elsewhere on the Internet, then laboriously exchanging IP addresses and meeting times and hoping the other guy followed through. This would be instant-gratification online gaming. It would also provide a foretaste at least of persistent online multiplayer gaming; as people won matches, they would become known commodities in the community, setting up a meta-game, a sporting culture of heroes and zeroes where folks kept track of win-loss records and where everybody clamored to hear the results when two big wheels faced off against one another.

Cotton and Coleman renamed their software for the third time in less than nine months, calling it Kali, a name suggested by Coleman’s Indian-American girlfriend (later his wife). “The Kali avatar is usually depicted with swords in her hands and a necklace of skulls from those she has killed,” says Coleman, “which seemed appropriate for a deathmatch game.” Largely at the behest of Cotton, always the more commercially-minded of the pair, they decided to make Kali shareware, just like DOOM itself: multiplayer sessions would be limited to fifteen minutes at a time until you coughed up a $20 registration fee. Cotton went through the logistics of setting up and running a business in Georgia while Coleman did most of the coding in Illinois. (Rather astonishingly, Cotton and Coleman had still never met one another face to face in 2013, when gaming historian David L. Craddock conducted an interview with them that has been an invaluable source of quotes and information for this article.)

Kali certainly wasn’t the only solution in this space; a commercial service called DWANGO had existed since December of 1994, with the direct backing of John Carmack and John Romero, whose company id Software collected 20 percent of its revenue in return for the endorsement. But DWANGO ran over old-fashioned direct-dial-up connections rather than the Internet, meaning you had to pay long-distance charges to use it if you weren’t lucky enough to live close to one of its host computers. On top of that, it charged $9 for just five hours of access per month, with the fees escalating from there. Kali, by contrast, was available to you forever for as many hours per month as you liked after you plunked down your one-time fee of $20.

So, Kali was popular right from its first release on April 26, 1995. Yet it was still an awkward piece of software for the casual user despite the duo’s best efforts, being tied to MS-DOS, whose support for TCP/IP relied on a creaky edifice of third-party tools. The arrival of Windows 95 was a godsend for Kali, as it was for computer gaming in general, making the hobby accessible in a way it had never been before. The so-called “Kali95” was available by early 1996, and things exploded from there. Kali struck countless gamers with all the force of a revelation; who would have dreamed that it could be so easy to play against another human online? Lloyd Case, for example, wrote in Computer Gaming World magazine that using Kali for the first time was “one of the most profound gaming experiences I’ve had in a long time.” Reminiscing seventeen years later, David L. Craddock described how “using Kali for the first time was like magic. Jumping into a game and playing with other people. It blew my fourteen-year-old mind.” In late 1996, the number of registered Kali users ticked past 50,000, even as quite possibly just as many or more were playing with cracked versions that bypassed the simplistic serial-number-registration process. First-person-shooter deathmatches abounded, but you could also play real-time strategies like Command & Conquer and Warcraft, or even the Links golf simulation. Computer Gaming World gave Kali a special year-end award for “Online-Enabling Technology.”

Kali for Windows 95.

Competitors were rushing in at a breakneck pace by this time, some of them far more conventionally “professional” than Kali, whose origin story was, as we’ve seen, as underground and organic as that of DOOM itself. The most prominent of the venture-capital-funded startups were MPlayer (co-founded by Brian Moriarty of Infocom and LucasArts fame, and employing Dani Bunten Berry as a consultant during the last months of her life) and the Total Entertainment Network, better known as simply TEN. In contrast to Kali’s one-time fee, they, like DWANGO before them, relied on subscription billing: $20 per month for MPlayer, $15 per month for TEN. Despite slick advertising and countless other advantages that Kali lacked, neither would ever come close to overtaking its scruffy older rival, which had price as well as oodles of grass-roots goodwill on its side. Jay Cotton:

It was always my belief that Kali would continue to be successful as long as I never got greedy. I wanted everyone to be so happy with their purchase that they would never hesitate to recommend it to a friend. [I would] never charge more than someone would be readily willing to pay. It also became a selling point that Kali only charged a one-time fee, with free upgrades forever. People really liked this, and it prevented newcomers (TEN, Heat [a service launched in 1997 by Sega of America], MPlayer, etc.) from being able to charge enough to pay for their expensive overheads.

Kali was able to compete with TEN, MPlayer, and Heat because it already had a large established user base (more users equals more fun) and because it was much, much cheaper. These new services wanted to charge a subscription fee, but didn’t provide enough added benefit to justify the added expense.

It was a heady rush indeed, although it would also prove a short-lived one; Kali’s competitors would all be out of business within a year or so of the turn of the millennium. Kali itself stuck around after that, but as a shadow of what it had been, strictly a place for old-timers to reminisce and play the old hits. “I keep it running just out of habit,” said Jay Cotton in 2013. “I make just enough money on website ads to pay for the server.” It still exists today, presumably as a result of the same force of habit.

One half of what Kali and its peers offered was all too obviously ephemeral from the start: as the Internet went mainstream, developers inevitably began building TCP/IP support right into their games, eliminating the need for an external IPX-to-TCP/IP bridge. (For example, Quake, id Software’s much-anticipated follow-up to DOOM, did just this when it finally arrived in 1996.) But the other half of what they offered was community, which may have seemed a more durable sort of benefit. As it happened, though, one clever studio did an end-run around them here as well.



The folks at Blizzard Entertainment, the small studio and publisher that was fast coming to rival id Software for the title of the hottest name in gaming, were enthusiastic supporters of Kali in the beginning, to the point of hand-tweaking Warcraft II, their mega-hit real-time strategy, to run optimally over the service. They were rewarded by seeing it surpass even DOOM to become the most popular game there of all. But as they were polishing their new action-CRPG Diablo for release in 1996, Mike O’Brien, a Blizzard programmer, suggested that they launch their own service that would do everything Kali did in terms of community, albeit for Blizzard’s games alone. And then he additionally suggested that they make it free, gambling that knowledge of its existence would sell enough games for them at retail to offset its maintenance costs. Blizzard’s unofficial motto had long been “Let’s be awesome,” reflecting their determination to sell exactly the games that real hardcore gamers were craving, honed to a perfect finish, and to always give them that little bit extra. What better way to be awesome than by letting their customers effortlessly play and socialize online, and to do so for free?

The idea was given an extra dollop of urgency by the fact that Westwood Games, the maker of Warcraft‘s chief competitor Command & Conquer, had introduced a service called Westwood Chat that could launch people directly into a licensed version of Monopoly. (Shades of Dani Bunten Berry’s cherished childhood memories…) At the moment it supported only Monopoly, a title that appealed to a very different demographic from the hardcore crowd who favored Blizzard’s games, but who knew how long that would last?[4]Westwood Chat would indeed evolve eventually into Westwood Online, with full support for Command & Conquer, but that would happen only after Blizzard had rolled out their own service.

So, when Diablo shipped in the last week of 1996, it included something called Battle.net, a one-click chat and matchmaking service and multiplayer facilitator. Battle.net made everything easier than it had ever been before. It would even automatically patch your copy of the game to the latest version when you logged on, pioneering the “software as a service” model in gaming that has become everyday life in our current age of Steam. “It was so natural,” says Blizzard executive Max Schaefer. “You didn’t think about the fact that you were playing with a dude in Korea and a guy in Israel. It’s really a remarkable thing when you think about it. How often are people casually matched up in different parts of the world?” The answer to that question, of course, was “not very often” in the context of 1997. Today, it’s as normal as computers themselves, thanks to groundbreaking initiatives like this one. Blizzard programmer Jeff Strain:

We believed that in order for it [Battle.net] to really be embraced and adopted, that accessibility had to be there. The real catch for Battle.net was that it was inside-out rather than outside-in. You jumped right into the game. You connected players from within the game experience. You did not alt-tab off into a Web browser to set up your games and have the Web browser try to pass off information or something like that. It was a service designed from Day One to be built into actual games.

The combination of Diablo and Battle.net brought a new, more palpable sort of persistence to online gaming. Players of DOOM or Warcraft II might become known as hotshots on services like Kali, but their reputation conferred no tangible benefit once they entered a game session. A DOOM deathmatch or a Warcraft II battle was a one-and-done event, which everyone started on an equal footing, which everyone would exit again within an hour or so, with nothing but memories and perhaps bragging rights to show for what had transpired.

Diablo, however, was different. Although less narratively and systemically ambitious than many of its recent brethren, it was nevertheless a CRPG, a genre all about building up a character over many gaming sessions. Multiplayer Diablo retained this aspect: the first time you went online, you had to pick one of the three pre-made first-level characters to play, but after that you could keep bringing the same character back to session after session, with all of the skills and loot she had already collected. Suddenly the link between the real people in the chat rooms and their avatars that lived in the game proper was much more concrete. Many found it incredibly compelling. People started to assume the roles of their characters even when they were just hanging out in the chat rooms, started in some very real sense to live the game.

But it wasn’t all sunshine and roses. Battle.net became a breeding ground of the toxic behaviors that have continued to dog online gaming to this day, a social laboratory demonstrating what happens when you take a bunch of hyper-competitive, rambunctious young men and give them carte blanche to have at it any way they wish with virtual swords and spells. The service was soon awash with “griefers,” players who would join others on their adventures, ostensibly as their allies in the dungeon, then literally stab them in the back when they least expected it, killing their characters and running off with all of their hard-won loot. The experience could be downright traumatizing for the victims, who had thought they were joining up with friendly strangers simply to have fun together in a cool new game. “Going online and getting killed was so scarring,” acknowledges David Brevick, Diablo‘s original creator. “Those players are still feeling a little bit apprehensive.”

To make matters worse, many of the griefers were also cheaters. Diablo had been born and bred a single-player game; multiplayer had been a very late addition. This had major ramifications. Diablo stored all the information about the character you played online on your local hard drive rather than the Battle.net server. Learn how to modify this file, and you could create a veritable god for yourself in about ten minutes, instead of the dozens of hours it would take playing the honest way. “Trainers” — programs that could automatically do the necessary hacking for you — spread like wildfire across the Internet. Other folks learned to hack the game’s executable files themselves. Most infamously, they figured out ways to attack other players while they were still in the game’s above-ground town, supposedly a safe space reserved for shopping and healing. Battle.net as a whole took on a siege mentality, as people who wanted to play honorably and honestly learned to lock the masses out with passwords that they exchanged only with trusted friends. This worked after a fashion, but it was also a betrayal of the core premise and advantage of Battle.net, the ability to find a quick pick-up game anytime you wanted one. Yet there was nothing Blizzard could do about it without rewriting the whole game from the ground up. They would eventually do this — but they would call the end result Diablo II. In the meanwhile, it was a case of player beware.

It’s important to understand that, for all that it resembled what would come later all too much from a sociological perspective, multiplayer Diablo was still no more persistent than Moria and Oubliette had been on the old PLATO network: each player’s character was retained from session to session, but nothing about the state of the world. Each world, or instance of the game, could contain a maximum of four human players, and disappeared as soon as the last player left it, leaving as its legacy only the experience points and items its inhabitants had collected from it while it existed. Players could and did kill the demon Diablo, the sole goal of the single-player game, one that usually required ten hours or more of questing to achieve, over and over again in the online version. In this sense, multiplayer Diablo was a completely different game from single-player Diablo, replacing the simple quest narrative of the latter with a social meta-game of character-building and player-versus-player combat.

For lots and lots of people, this was lots and lots of fun; Diablo was hugely popular despite all of the exploits it permitted — indeed, for some players perchance, because of them. It became one of the biggest computer games of the 1990s, bringing online gaming to the masses in a way that even Kali had never managed. Yet there was still a ways to go to reach total persistence, to bring a permanent virtual world to life. Next time, then, we’ll see how mainstream commercial games of the 1990s sought to achieve a degree of persistence that the first MUD could boast of already in 1979. These latest virtual worlds, however, would attempt to do so with all the bells and whistles and audiovisual niceties that a new generation of gamers raised on multimedia and 3D graphics demanded. An old dog in the CRPG space was about to learn a new trick, creating in the process a new gaming acronym that’s even more of a mouthful than POMG.



Did you enjoy this article? If so, please think about pitching in to help me make many more like it. You can pledge any amount you like.


Sources: the books Stay Awhile and Listen Volumes 1 and 2 by David L. Craddock, Masters of Doom by David Kushner, and The Friendly Orange Glow by Brian Dear; Retro Gamer 43, 90, and 103; Computer Gaming World of September 1996 and May 1997; Next Generation of March 1997. Online sources include “The Story of Battle.net” by Wes Fenlon at PC Gamer, Dan Griliopoulos’s collection of interviews about Command & Conquer, Brian Moriarty’s speech honoring Dani Bunten Berry from the 1998 Game Developers Conference, and Jay Cotton’s history of Kali on the DOOM II fan site. Plus some posts on The CRPG Addict, to which I’ve linked in the article proper.

Footnotes

Footnotes
1 The PLATO Moria was a completely different game from the 1983 single-player roguelike that bore the same name.
2 Not the same game as the 2002 Bioware CRPG of the same name.
3 Wheeler Dealers and all of her other games that are mentioned in this article were credited to Dan Bunten, the name under which she lived until 1992.
4 Westwood Chat would indeed evolve eventually into Westwood Online, with full support for Command & Conquer, but that would happen only after Blizzard had rolled out their own service.
 
 

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

Games on the Net Before the Web, Part 1: Strategy and Simulation

Right from the beginning, games were a component of the commercial online services that predated the World Wide Web; both The Source and CompuServe included them among their offerings from the moment those services first went online. In the early years, such online games were mostly refugees from 1970s institutional computing. Classics like Star Trek, Adventure, and Hammurabi had the advantage of being in the public domain and already running without modification on the time-shared computer systems which hosted the services, and could thus be made available to subscribers with a minimum of investment. Eventually even some text-only microcomputer games made the transition. By 1984, CompuServe, now well-established at the vanguard of the burgeoning online-services industry, had a catalog that included the original Adventure along with an expanded version, nine Scott Adams games, and the original PDP-10 Zork (renamed for some reason to The House of Banshi). And those were just the text adventures. There were also the dungeon crawls Dungeons of Kesmai and Castle Telengard and the war games Civil WarFantasy, and Command Decision, while for the less hardcore there were the CompuServe Casino, board games like Reversi, and curiosities like a biorhythm charter and an astrology calculator.

The fact that so many games were on offer so quickly indicates that they must have paid their way, at least to some extent. The hard reality remained, though, that these single-player games which happened to be played online were a hard sell to many subscribers. Paying $6 or more per hour to play a text-only game didn’t make a whole lot of sense to many of them when they could buy or even type in something just as satisfying for their local machines.

Group discussion about games, on the other hand, was something only the online services could offer with any degree of convenience or regularity, and it absolutely thrived in consequence almost from Day One. Adventure games were an especially popular topic, and for very good reason; given the non-sequiturial puzzles those early adventures were so rife with, outside help was about the only way most players had a reasonable chance of solving many of them. When Sierra in 1982 released perhaps the most absurdly unfair early adventure of them all in the form of Time Zone — twelve disk sides and more than a thousand rooms of complete inscrutability — The Source’s users mounted a pioneering crowdsourced effort to solve it. Its home was called The Vault of Ages:

Welcome to the Vault of Ages. Here we are coordinating the greatest group effort in adventure-solving: the complete mapping of On-Line’s Time Zone.

Herein we are gathering, verifying, and correlating information about each time zone. Feel free to visit here anytime, but remember that for the Vault to fill, we need your contributions of information. Any time you have new information about mapping, puzzle solutions, traps overcome, items found, email this info to me. After verification, your contributed jigsaw-puzzle piece will be added to the Vault file, and your name will be entered upon the rolls as a master solver.

Unsurprisingly, the first person known to have solved Time Zone, a tireless adventure fanatic and gaming journalist named Roe R. Adams III, was a Source and Vault of Ages regular.

The online services would continue to be a vital meeting point for gamers, gaming journalists, and, increasingly, the developers that made the games for many years to come, right up until they were superseded by the modern World Wide Web. Countless gamers who weren’t subscribers nevertheless benefited from the walkthroughs and strategy guides that filtered down from the likes of CompuServe onto the network of local bulletin-board systems and into the halls that hosted users-group meetings, to eventually be passed from hand to hand on playgrounds and in lunch rooms as smudged printouts whose unassuming appearance belied the precious information they contained.

But, while it’s certainly noteworthy in itself, our main concern today isn’t with this far-reaching game-solving grapevine. We’re rather concerned with the games that subscribers were actually playing online in increasing numbers by the middle of the 1980s — games which by and large weren’t the roll call of golden oldies that opened this article. We’re interested, in other words, in how the online services learned to take advantage of their uniqueness as interconnected real-time communities of tens or hundreds of thousands of people to offer players something they couldn’t get from an offline game. In doing so, they would give the world a sneak preview of its online future in yet one more way.


One of the executives who worked under Jeff Wilkins at CompuServe in the early 1980s was named Bill Louden. He was an unusual character there in several ways, not least in being a living embodiment of where computing was going as opposed to where it had been. Unlike most of CompuServe’s management, who had been raised at the bosom of institutional computing, Louden had come to his current job through microcomputers. He had been working as a Radio Shack store manager in CompuServe’s hometown of Columbus, Ohio, when the TRS-80 arrived in 1977, and he became such an instant home-computing zealot that he founded the Central Ohio TRS-80 Users Group shortly thereafter. He joined CompuServe in 1979, hired by Wilkins to be a bridge between the hobbyist-oriented personal-computing community which he knew so well and the dominant culture of business-oriented big-iron computing inside CompuServe.

Among the many things which Louden understood but CompuServe’s other managers largely did not was the appeal of games. He became the foremost advocate for them inside the company — an advocate for, that is, going beyond just scooping up the low-hanging fruit of Adventure and Hammurabi and calling it a day. He believed that games, if given the proper priority, could become not just an occasional distraction for the service’s subscribers but the primary reason some of them chose to sign up in the first place. By acting upon that belief, he would become another forgotten pioneer, one of the most important architects of online gaming’s future.

The first of Bill Louden’s pet projects to hint at the true potential for online gaming was at first glance just another tired institutional refugee. Back in 1978, a new game had appeared on the DEC PDP-10s that lived at the University of Texas at Austin. DECWAR was at bottom yet another variation on the tried-and-true Star Trek strategy game, but some of its embellishments to the formula were very significant. Instead of a single player hunting computer-controlled Klingons and Romulans, DECWAR had room for up to eight players, who faced off against one another in two teams of four, with the balance of the teams filled up by the computer when fewer than eight humans could be rounded up. Just as significantly, the game was played in real time.

DECWAR first came to Bill Louden’s attention in 1982; he saw the potential it held for CompuServe immediately. Making inquiries with the university, he found the game’s developers were willing to sell him its source code for $50. When his superiors refused to part with that princely sum, he bought the source himself using his own money. Louden then did much of the work that was required to adapt the game to CompuServe himself, excising in the process the last vestigial remnants of the Star Trek intellectual property. (Out of similar legal concerns, the original Star Trek game had itself become the thinly veiled Space Trek on CompuServe by this point.) Louden also added innovations like a leader board which saw players progress in rank from cadet to admiral as they won games and blew up other players’ ships, adding at least a dollop of long-term persistence to tempt them to keep playing. And he gave DECWAR a new name: MegaWars.

CompuServe advertised MegaWars widely for the first year or two, even as their marketers ignored other pioneering initiatives like CB Simulator. Garish MegaWars depictions like these contrasted strangely with the company’s usual staid image. (One can only imagine what those members of the board who had been against launching the consumer service from the start thought of this sort of thing.) As was par for the course during this time period, the imagery of the advertising had almost nothing to do with the game, which featured neither interpersonal combat nor scantily-clad warriors of either sex.

MegaWars went up on CompuServe circa August of 1982, much to the dismay of the University of Texas’s student coders, who had neglected to copyright or attach any legal restrictions whatsoever to the source code they had given to Louden for $50. Playing it was a daunting proposition: it usually required about two to three hours — meaning as much as $20 in connection fees — to finish a complete match, and the player had to learn 32 separate textual commands, which had to be typed in real time as the galaxy exploded in battle all around her. Yet, despite or because of its challenging nature, it proved enduringly popular, spawning a cult of hardcore players who stuck with it for years and years. In fact, it would become CompuServe’s most durable single game of all, remaining on the service for the next fifteen years. “The people that play MegaWars are extremely serious,” CompuServe’s communications director was soon warning. “The expertise level is very high.”

It didn’t take long for MegaWars players to form themselves into consistent teams that themselves sometimes stayed together for years. Intra- and inter-team politics could come to fill as much space as actually playing the game. Team Dune, for instance, was made up of fans of Frank Herbert’s iconic series of science-fiction novels; everyone on the team was expected to take the name of a Dune character as a handle. “Dictators” were selected from among the team’s members for three-month terms in hotly contested elections that could sometimes turn violent. It was all a part of the fantasy. A Team Dune member named Martin Maners, better known on CompuServe as “Leto II,” had this to say:

I’ve always had a vivid imagination. I like science fiction and Star Wars. When you sit down in front of your computer and play MegaWars, you really leave the earth, you’re really out there. It helps me relax, especially with the way MegaWars lets me talk to other players on my team. It’s nice to be able to sit back and do something completely different for a change.

With MegaWars, Bill Louden had put his finger on the real strength of gaming on a service like CompuServe: the opportunity for subscribers to play against one another rather than alone with the computer. “MegaWars is a challenge and is entertaining as well, but the real enjoyment comes from the multiplayer aspect of the game,” said one subscriber. “Interacting with other human players is what makes it interesting in a way that a ‘man vs. computer’ game just can’t match.” Another subscriber noted that it was “not like a game you would run on your personal computer. Here you get to pit yourself against a real person who could be across the street or the country. A much more formidable foe! It’s both entertaining and challenging, and at the same time it’s a great way to meet people and make new friends.”

If CompuServe was to continue to develop their games in this direction, however, they would need to move beyond public-domain institutional refugees like DECWAR/MegaWars. Luckily, Louden had recently been fielding inquiries from a pair of outside programmers with aspirations to do just that. They called themselves Kesmai.

Kelton Flinn and John Taylor, a duo better known as Kesmai.

Kesmai weren’t your stereotypical teenage bedroom coders. John Taylor, who had a masters degree in computer science, worked for General Electric’s High Performance Division, writing software for industrial robots, while Kelton Flinn was working on a PhD in applied mathematics at the University of Virginia. They picked their company’s name as their favorite from a long list of random ones that had been spit out by a name-generating program.

Several years before, while still an undergraduate, Flinn had written a very ambitious game on his university’s computer which combined Star Trek-like space combat — played in real time, no less! — with a conquer-the-universe strategic layer of economics and politics. He called it simply S. He remembers one particular incident as the turning point in its development: “One person’s favorite planet was taken, and he picked up a chair and stalked across the room with it to clobber the culprit. ‘Bob, put the chair down, it’s only a game…’ I guess I should have known then we had a potential hit!”

After much lobbying on Kesmai’s part for a development contract, Bill Louden agreed to let them bring S to CompuServe as a sort of trial project, renaming it in the process to MegaWars III. (MegaWars II had been an ill-fated attempt to add graphics and sound, at least of a sort, to the first MegaWars using the character graphics and simple bells and whistles allowed by some otherwise textual communications protocols. Dismissed by Louden himself as “poorly done and abysmally slow,” it didn’t last very long.) Kesmai greatly expanded on the already ambitious S template for CompuServe, making the universe much larger, adding more diplomatic options, and adding a veritable sub-game all its own of starship design. It seems safe to say that, by the time they were done, there was nothing of comparable complexity available even in single-player form on the microcomputers of the time. Indeed, the end result can’t help but remind one of the so-called “4X” games — “explore, expand, exploit, exterminate” — that wouldn’t become really practical on PCs until the early 1990s, when the steady march of technology would lead to strategic epics like Civilization and Master of Orion. In contrast to most of those later games, though, MegaWars III offered all the unpredictability of dozens of human opponents, with whom one could communicate at any time using “hyperspace radio,” whether to make or break trade deals and military alliances or just to shoot the breeze.

A single game of MegaWars III could host up to 100 players, and ran for four to six weeks. At the end of that time, the player who had earned the most points through conquest and the economic development of her colonies would be crowned emperor (this system would later be cheerfully nicked by Master of Orion as one of its own victory conditions, thus further cementing the similarities between the two games). With a victor thus declared, it would be time to wipe the slate clean. A brand new universe would be generated, and players who had been disappointed by their performance last time could try their luck on this new playing field. Some modern online games could perhaps take a lesson from this constant rolling-over of the virtual universe, which was done with conscious intent: Louden notes that it “kept newbies from feeling they had no way to catch up and were just meat for the slaughter.”

That said, little else about MegaWars III was forgiving; it was even more demanding than the game to which it had been billed a sequel. Eight hours of real time corresponded to about a month of game time. Those who hoped to have a shot at the winner’s circle knew that they had to sign on every night, sometimes for hours at a time, to maintain their empires. The subscriber known as “L’Eagle,” a self-described “corporate lawyer” in real life, became something of a community legend for winning the very first game of MegaWars III, which ran from January 19 until March 15 of 1984. He was already a veteran grognard at that time, with a history with war games which dated back well into the previous decade. For someone like him, MegaWars III provided an experience that could only have been approached in the past by some of the more elaborate play-by-mail campaigns run by companies like Flying Buffalo. The CompuServe version, however, had the added allure of instant feedback, along with the instant gratification of real-time chat — always useful for taunting a vanquished foe.

Just as with the first MegaWars, interactions with other players in MegaWars III were, even more so than all of the complicated rules, the heart of the game’s appeal. L’Eagle described the game, with its delicate tissue of alliances, in terms that actually smack as much or more of Diplomacy as Master of Orion. Such is the effect of adding the human element to the 4X equation.

The game has very few limitations. That’s part of the charm. But everyone has to work to keep the game good-spirited. At one point, the game’s authors thought that team members would turn on one another, that friends would become enemies. But after six weeks of planning together, the last thing you would do is back-stab.

L’Eagle is perhaps overstating the case just a bit. Back-stabbing was hardly unknown in MegaWars III; in fact, just as in Diplomacy, it was a virtual necessity for those with serious aspirations to win. Still, MegaWars III co-creator Kelton Flinn wasn’t wrong when he noted that “it’s a social game, as well as a competitive one.” Already in 1984, the year of MegaWars III‘s debut, CompuServe hosted a gathering of players in Columbus that attracted several dozen attendees. It was only the first of many.

Journalists, conditioned to think of computer games as strictly kids’ stuff, frequently expressed surprise when they were informed that the average age of a hardcore MegaWars I or III player was somewhere north of thirty. Really, though, it couldn’t have been any other way. The great disadvantage of these early online services, the necessary temper to any nostalgia for the era of the net before the Web, was how expensive they were. The whole time you were playing, the meter was running. Just as with CB Simulator, some people got addicted to the games, often to the detriment of the rest of their lives. Regulars soon noticed cyclical patterns to some of their comrades’ comings and goings. L’Eagle:

You can tell when the MasterCard bills come. People disappear. Later, they come back and say, “Yeah, I just had to cut down a bit.” Teenagers, you might never see them again. Fortunately, I make a lot of money.

As always, digital utopianism only got you so far in a world that at the end of the day still ran on money.

By mid-decade, then, multiplayer gaming — as opposed to the older species of single-player games that happened to be played online — was establishing itself as a staple of online life, not only on CompuServe but also on services like PlayNet and QuantumLink. As we saw in an earlier article, the latter pair offered a variety of simple board games that more casual players could enjoy with the added benefit of graphics, an area CompuServe would soon push into as well. The potential of online games remained sharply limited, however, by the fact that the vast majority of subscribers to the various services were still using 300-baud modems, which transferred data at the glacial pace of approximately 30 to 35 bytes per second — or a little over 2 K per minute.

When that logjam finally broke, it did so, as so often happens in technology, with head-snapping speed. The breakthrough was helped along by GEnie, the new online service which launched in October of 1985 to become the most serious challenger yet to CompuServe’s dominance. A big drag on the adoption of faster modems had actually been CompuServe itself, which charged $6 per hour for 300-baud access but a well-nigh absurd $12 per hour for 1200-baud connections. GEnie, on the other hand, launched at $5 per hour for both 300 and 1200 baud, soon forcing even the industry leader to adjust their own rates in response. With a new standard pricing model thus established, subscribers rushed out to buy the new, faster modems that were also coming down rapidly in price. GEnie reported at the beginning of 1986 that less than 40 percent of their subscribers had upgraded to 1200 baud; by the end of the year, that number had topped 90 percent. And 1200 baud was itself only a beginning rather than an end: 2400 baud was coming on strong, with 9600 baud out there on the not-too-distant horizon. What might developers of online games be able to do with those sorts of connection speeds? Bill Louden and the boys at Kesmai had some ideas.

Louden had left CompuServe in 1984, disaffected by what he saw as too many “corporate people” encroaching on his domain. After some misadventures trying to set up a regional online service of his own called Georgia Online, he was tapped by General Electric to run GEnie. Like any good manager of an upstart, he surveyed the leading company in his industry — i.e., his recent employer CompuServe — for weak spots where GEnie could offer something more to customers. As we’ve just seen, one of these was making higher-speed connections affordable. Another, unsurprisingly given Louden’s reputation as the “games guy” even while he was still at CompuServe, was games. Louden strove to make GEnie a haven for gamers, both for talking about offline games — the service would verge on displacing CompuServe in the years to come as the foremost source for walkthroughs and strategy guides — and for playing online games.

For their part, Kesmai were happy to work for any service willing to pay them. The fact that John Taylor was still going to work every day at GEnie’s corporate parent General Electric, not to mention Kesmai’s established relationship with Louden, made a development contract with the new service a natural step. MegaWars III therefore soon came to GEnie as well in thinly disguised form as Stellar Emperor. But that was merely an old CompuServe glory being revisited. GEnie’s crowning gaming glory would be a radical departure from anything seen online to date.

Air Warrior, a multiplayer air-combat simulator using aircraft from both of the world wars, was first offered to owners of the Apple Macintosh in late 1986. Although the game ran through GEnie, it was provided as a standalone application which handled all of the minutiae of logging in and communications for itself, in lieu of the text-only terminal programs subscribers normally used to access the service. This approach allowed it to make use of cutting-edge 3D graphics, the likes of which had never before been seen in an online context. It was nothing short of revolutionary, the very first game of its kind, and those who wished to play it had to pay for their spot at the bleeding edge — to the tune of no less than $11 per hour, more than twice GEnie’s normal going rate. Luckily for Kesmai, who had expanded greatly and invested a lot of money in the project, a fair number of well-heeled users proved willing to pony up.

Choosing a plane to fly — or, alternately, a vehicle to drive — in Air Warrior.

Ported to the Commodore Amiga and Atari ST in 1987, Air Warrior used what we today would call the “software as a service” model to perpetually evolve throughout its long lifespan, with players expected to download the updates which appeared almost monthly on GEnie and merge them into their local disks. By 1988, this process had brought the game to a certain maturity. Three “theaters” — one for World War I, two for the more popular World War II — were kept in constant operation, complete with leader-board tallies of aircraft shot down and ground targets destroyed. Similarly to MegaWars III, a winner of each campaign was declared every three weeks and the theater reset to keep anyone from running away with things for too long.

During a campaign, players could cast their lot with any of three opposing militaries. Some players preferred to be lone wolves, Red Barons lurking in the cloud cover to swoop down on their prey, but most took it upon themselves to further organize into squadrons, with all the resultant social interaction you might expect. Indeed, Air Warrior became more and more team-oriented as time went on. Lumbering B-17 bombers took off on strike missions with not only a pilot but no fewer than six other players filling the various gun turrets, escorted by more players in single-seater Mustangs and Spitfires. Meanwhile still other players would be mounting a coordinated ground assault in jeeps and tanks. All were bound together by the magic of chat — or, in in-game terms, by their multi-band radios. And on the other side, of course, was a similarly well-coordinated group of defenders hoping to add to their point tallies by taking down some of those juicy B-17s.

The Air Warrior application incorporated a terminal layer for handling logging into GEnie and other command-oriented tasks. Here a player is checking out his personal history.

The obvious forerunner to modern multiplayer wargasms like the Battlefield series, Air Warrior was distinguished, like so many of these early online games, by a devotion to the game’s fiction that would be very foreign to most of today’s eager gibbers and fraggers. Air Warrior billed itself as a flight simulator the equal of the ones being made by companies like subLogic and MicroProse, and many players took it very seriously indeed on those terms, implementing historical tactics and even radio protocols. Inevitably, some new players tried to single-handedly run roughshod over the place, but such respectless cretins usually didn’t live very long; one sign of the game’s worth as a simulation was the fact that the historically accurate tactics were mostly the ones that worked. And of course the fact that you were paying $11 per hour for the privilege had a way of driving up the average participant’s age and assuring that only those who really, really hankered after a vintage air-combat experience stuck around.

In the air in Air Warrior. Note the chat window, vital to squadron coordination, that’s open to the right.

Newbie pilots wishing to find acceptance within a squadron’s ranks had to contend with the realistic flight mechanics while tranquilly accepting their designated role in each operation; true to history, new pilots were usually given sheltered positions as wingmen to more experienced fliers which gave them little opportunity to run up their personal kill tallies. Still, greenhorns quickly learned to appreciate the extra cover, as nothing about Air Warrior was forgiving. Woe betide the pilot who forgot that the escape key was meant literally in this game: it led to an instant, no-questions-asked bailout.

Death meant that you had to start over with a new character, so all serious players practiced their wheels-up landings and their water ditchings extensively using the game’s weapons-less offline practice mode. Even the effects of fuel usage were modeled accurately; planes became faster and more maneuverable as they got lighter. But this too, of course, was a double-edged sword: many an Air Warrior pilot wound up dead because of inattention to the fuel gauge. To help the youngsters out, the experienced pilots instituted a flying-and-tactics clinic which ran every Thursday night for years. The life saved, they reasoned, might just be their own if they got saddled with one of these greenhorns on their wing.

Lining up on a bridge, one of the ground targets which players got points for destroying.

In marked contrast to the Kesmai games that had preceded it, Air Warrior remained always on the cutting edge of audiovisual technology. It shone most of all on the Amiga when that machine was the audiovisual class of the industry; it wasn’t even ported to MS-DOS until 1989. Once there, though, it continued to evolve apace, becoming in early 1993 one of the first games of any stripe to support the new generation of “Super VGA” graphics cards. The Air Warrior community would always remain a relatively small one; a 1993 magazine report describes about thirty players active in each theater most evenings, the very same number cited by another report from 1989. But despite such limited numbers of active players, Air Warrior became, like the MegaWars games, rather astonishingly long-lived, actually managing to outlast its original host service GEnie to make it all the way to 2001. For those seeking a certain kind of historically grounded multi-player combat experience, emphasizing real-world tactics, it was in many ways a better take on online gaming than most of what’s available today. And even for those who didn’t know the difference between a Hellcat and Zero, it remained a living example of the potential for online gaming, an aspirational ideal at the vanguard of the field for many years.

While it may be a little hard to recognize today, the SVGA Air Warrior looked spectacular in its day — not just spectacular for an online game, but spectacular, period.

This survey, sketchy though it’s been, has hopefully been enough to demonstrate both how influential the online services of the 1980s really were on online gaming as we know it today and how compelling the games they offered could be even when taken entirely on their own terms. Yet the creations we’ve seen so far, groundbreaking though they’ve been in their various ways, have all been relatively short-form experiences: games with beginnings, middles, and ends that spanned no more than a handful of weeks. What persistence these games did possess was thanks to players like the desert rats of Team Dune, who found ways to make the fiction last even when the game proper was over. But what of games which truly have no ending? What of games which aren’t so much games at all as virtual worlds, even virtual societies — real Second Lifes for their inhabitants, one might say. Today such virtual worlds consume the free time of millions of rabid players, and stand as the most complex virtual spaces ever created. Next time, then, we’ll find out how game developers discovered the power of persistence, many years before Warcraft — much less World of Warcraft — was a twinkle in its creators’ eyes.

(Sources: the books On the Way to the Web: The Secret History of the Internet and its Founders by Michael A. Banks and Hackers: Heroes of the Computer Revolution by Steven Levy; Softline of May 1982; Online Today of June 1987, January 1988, and February 1989; Byte of September 1982; Antic of November 1984; Compute!’s Gazette of May 1985; Family Computing of June 1986; InfoWorld of October 21 1985 and December 2 1985; Compute! of July 1987; Amazing Computing of August 1987 and March 1989; the STart “games issue” for 1988; Computer Gaming World of January 1990 and May 1993; CompuServe’s games catalog/brochure from 1984; the Games of Fame online articles on MegaWars and MegaWars III; the history page from a recent MegaWars revival.)

 
 

Tags: , , , ,