
The aggressively Satanic imagery of the Diablo series — “Diablo” means “Devil” in Latin, Spanish, and Italian — would have contributed to a moral panic ten or fifteen years earlier. In the late 1990s and early 2000s, everybody just went on with their day.
[Diablo II] is a progression with a character where you go and defeat enemies and get rewarded. There’s overriding goals as well as lots of sub-goals. There’s many things to do, yet it’s very simple. It’s very straightforward. There’s no, “What am I supposed to do now?” It’s pretty much in your face as to what you’re supposed to be doing. It’s very easy to click, and it does things automatically…
— David Brevik
There’s never enough blood and fire.
— Max Schaefer
Within a few weeks of the release of Diablo, it was clear that Blizzard Entertainment had a hit on their hands. Within a few months, it was clear that this was more than a hit: that it was another era-defining game from the company that had given the world Warcraft II only a year and a half earlier. Not to make a sequel once that realization had dawned would have been to leave a dump truck full of money parked on the curb.
Fortunately, it wasn’t hard for Blizzard’s upper management to convince David Brevik, Max and Erich Schaefer, and the rest of their team at Blizzard North to throw themselves into such a project. They saw Diablo II as a chance to implement all of the things they hadn’t had the time or resources for back when the first game was an unproven shot in the dark, as well as to fix the infelicities that had cropped up once players had gotten their hands on it in the wild. In their minds, this was to be Diablo 2.0 as much as it was Diablo II.
Yet they knew that they had to tread carefully as they made their improvements, lest they lose the qualities that had made the first game so popular. Diablo I had homed in relentlessly on a simple gameplay loop of (minimal) effort and (maximal) reward: go into dungeons, kill monsters, collect loot, and level up. Rinse and repeat, until you reached the sixteenth dungeon level out of sixteen, beat the last boss, and won the game. Story and setting, strategic and tactical nuance, and all of the other complexities that normally went into the CRPG genre were curtailed or eliminated entirely in homage to the loop, Brevik having intuited — correctly, as the sales figures showed — that a lot of gamers didn’t actually care about that stuff. A sequel which reintroduced too many of the very elaborations that Diablo had pared away risked no longer feeling like Diablo at all, a danger of which the team was well aware.
Thus the three years it took them to make Diablo II were filled with a lot of hang-wringing and second-guessing about how much additional complexity was too much. “In hindsight it feels like it was all fine, we got to where we got, why were we ever worried about it?” says character artist and dialog writer Phil Shenk. “But in the middle of it, yeah, there were times that we felt like we were messing with the formula or that we were ruining it.” They learned to evaluate every mooted change through the lens of a single mission statement: “We aren’t making a CRPG. We’re making a Diablo.”
Shenk was one of about 40 people who joined Brevik and his 20 or so colleagues who had helped to create Diablo I. Despite the tripling of manpower, it took them far, far longer than anticipated to finish the sequel. Those three years were a period of rapid change in the games industry, marked by consolidation in terms of both publishers and gameplay formulas. It is a measure of Blizzard’s enormous success and influence that two of the three most popular such formulas could be traced back to that company: there was a flood of real-time-strategy titles seeking to duplicate the sales figures of Warcraft II, and a flood of so-called “action RPGs” trying to do the same for Diablo. As the turn of the millennium approached, the industry as a whole was increasingly the one that Blizzard and id Software — the inventor of the first-person shooter, the third hugely popular gameplay formula — had made in their image. The new heart of the market was fast-paced, violent, action-oriented in every sense of the phrase, and readily amenable to the online multiplayer matches that were becoming more and more of a priority for hardcore gamers as the state of Internet connectivity steadily improved.
Yet even Blizzard wasn’t entirely insulated from the more worrisome aspects of change and consolidation. Rather oddly in light of the company’s outsized influence as the most successful single studio and publisher of the age, Blizzard was not an independent entity. From 1994 until 1996, it had been owned by Davidson and Associates, a staid specialist in educational software. In June of 1996, it had been acquired along with its parent company by CUC, a strange and voracious shopping-club empire reigned over by a snazzily attired gentleman named Walter Forbes. Along with Blizzard, CUC had also picked up the venerable Sierra On-Line, thus capturing a prodigious chunk of where gaming was going and where it had been in one fell scoop. In December of 1997, CUC merged with an administrator of hotel, rental-car, and real-estate franchises called HFS to form a new conglomerate called Cendant Corporation. Just a few months later, the wheels came off.
Much of Blizzard North was on a junket to Las Vegas when the news broke in April of 1998 that something was rotten in the state of Cendant. “We’re in this hotel room, and all these panicked calls start coming in,” says David Brevik. “We turn on the news, and the number-one story is the Cendant scam. It was ridiculous. We were just watching the stock drop. It was painful.” It turned out that Walter Forbes had had a better knack for accounting fraud than he had for running shopping clubs.
The collapse of Cendant became the biggest American business scandal of the decade, with Blizzard, Sierra, and the rest of the conglomerate’s thoroughly misplaced games division dragged through the mud as unwilling hostages. Ironically, the scandal broke at virtually the same instant that Starcraft, Blizzard’s next mega-hit, was shipping from the publisher’s more southerly offices.
For Sierra, a traditional specialist in adventure games whose products had fallen badly out of favor, the stakes were existential, and in the long run extinctionary. For Blizzard, the hot new whizz kids of the industry, they would prove less serious, for all that you might have had difficulty explaining that to the many Blizzard employees who had dutifully invested a portion of their paychecks into now-worthless Cendant stock. On November 20, 1998, the entirety of the spiraling Cendant games division was picked up by the French conglomerate Vivendi. Everyone understood that Blizzard was the real prize, the once-mighty Sierra merely the baggage that went along with the deal. And indeed, Sierra’s operations would soon be shuttered, the name allowed to live on as a brand only — and soon enough not even that. Blizzard, however, was permitted to continue with business as usual. For even the officious executives at Vivendi knew better than to kill the goose that just kept on laying golden eggs. Not only was Starcraft well on its way to becoming Blizzard’s best-selling game yet, but Diablo I and Warcraft II continued to sell better every single month than the vast majority of brand-new titles from other publishers, their appeal extended indefinitely by Blizzard’s pioneering Battle.net online matchmaking service, which meant that a quick pickup game with a real human was never more than a few mouse clicks away.
Over and above even Battle.net, the not-so-secret recipe for Blizzard’s commercial winning streak was the combination of a laser-sharp attunement to the desires and priorities of the typical young male gamer with an uncompromising commitment to execution and polish in service to those priorities. Blizzard’s staff, both in the North and the South, understood their customers so well because they were their customers, even as they worked so hard to make their games as good as they could possibly be for the same reason. Business itself was a kind of grand multiplayer game to them; the last thing they wanted to do was release a bad and/or poor-selling product that would spoil their winning streak. Thus their willingness to tear everything up and go back to the drawing board on a project, as they did early in the development of Starcraft, or to abandon entirely projects that had begun to seem out of tune with the gamer zeitgeist, as they did a Warcraft adventure game when it became clear that that dog just wasn’t hunting anymore. (Witness: the fate of their Cendant stablemate Sierra.)
Still, the wiggle room that the ongoing success of Diablo I gave Blizzard North as they worked on the sequel only extended so far. The last eighteen months of its development — fully half of the project’s total duration — was one brutal, endless crunch that became a bit much even for these hardcore souls. “It was, to this day, the worst crunch I’ve ever experienced on any project,” says programmer and sound designer Jonathan Stone. “It’s not something you want to keep doing into your thirties.” “You just don’t tell people to work twelve hours a day. It’s really taxing,” says programmer Peter Kemmer. “It drove me out of the company, and I’m sure it drove other people out, because there’s only so much of that you can take.”
The relatively small minority of the Blizzard staff who were married or in serious romantic relationships suffered particularly. Several divorces and breakups resulted from the crunch; among these casualties was David Brevik’s marriage. An older and wiser version of Diablo’s primary mastermind is now all too aware of what his brainchild cost him as well as what it gave him, especially when it came to his relationship with his two daughters: “It scarred me for a long time. It had huge ramifications on my life, most of them pretty negative. It was extremely costly.” Even Max Schaefer, who as a member of the Blizzard North management team was one of the primary drivers of the crunch, has come to recognize that he may not have done his employees’ physical and mental health any favors: “Six months into this crunch period, you’re still going, and you’re not really close to being done, although it always seemed like you were two or three months out. You start to physically and mentally burn out.”
In such circumstances, the colleagues with whom you were spending upwards of 80 hours per week became the sum total of your social life. “Everyone I knew at Blizzard became my circle,” says tester Josh Kurtz. “It became my support structure, my family. I did everything with them.” It was the ultimate recipe for instilling the very same hardcore monoculture, all but impenetrable to outsiders, that Blizzard was making such hay out of serving. Although David Brevik had famously told the team who worked on Diablo I that it should be straightforward enough for their moms to pick up and play, it’s safe to say that not too many mothers were playing Blizzard games out there in the real world. Meanwhile the crunch cycles that made a job in the games industry incompatible with a balanced family and social life did indeed serve to drive most people out of it by the time they reached the end of their twenties, further reinforcing the sense of stultifying sameness that so marked the values and aesthetics of computer gaming during this period. The so-called “casual revolution” of the aughts was partially a response to the “gamerdark” vibe of outfits like Blizzard, offering up a vision of gaming that was at least markedly different, if not always more broadminded, in its own values and aesthetics.
In the here and now of Y2K, however, the hardcore monoculture was capable of generating outsized amounts of money if you hit it just right, as Blizzard had a better aptitude for doing than anyone else. By the time Diablo II was finally pronounced done in June of 2000, its predecessor had sold a cool 2.5 million units and was still prominent on the shelves of every games store in the country, despite its age of three and a half years — donkey’s years in gaming terms. Other action RPGs like Darkstone, Revenant, and Nox — everyone seemed to searching for punchy one-word titles like Diablo — had shifted their fair share of units as well, although none had come close to matching their primary inspiration’s numbers. Blizzard was so confident in the sequel’s prospects that they shelled out for an initial production run of 2 million copies before they ever shipped the first box to a store.
That decision proved not to have been overconfident. Far from it. Diablo II didn’t just perpetuate Blizzard’s winning streak; it amplified it. That 2-million-copy run sold through in just six weeks; 184,000 copies were sold in the first 24 hours alone, leading the Guinness Book of World Records to crown Diablo II the fastest-selling computer game of all time. (This record would eventually be broken by — wouldn’t you know it? — another Blizzard game.)
One of the few areas where Diablo II did depart from the established code of hardcore gaming was ironically one of the keys to its sales. In a milieu where young men competed with one another to put together the hottest gaming “rig” in much the same way that their fathers might have competed to own the fastest car, Blizzard kept the system requirements of their games counterintuitively modest. Diablo II ran at a fixed screen resolution of just 640 X 480, the same as its predecessor, and used a fancy 3D graphics card as an optional visual enhancer rather than a baseline requirement. It could run acceptably well on a 233 MHz Pentium I with just 32 MB of memory, specs which some widely available laptops exceeded with ease by the year of its release. If you wanted to feel up with the times in gaming but you couldn’t afford to buy or build an expensive wundermachine, Diablo II was the answer to your prayers. You could jump on Battle.net and make a name for yourself without anyone having to know you were borrowing your mom’s work computer. Suffice to say that there are always great rewards to be reaped in casting as wide a net as possible — even if “dated” graphics did become one of the few points that Diablo II’s reviewers could find to grumble about in their otherwise glowing testimonials.
Such complaints were sour drops in a tidal wave. Diablo II became the rare computer game capable of withstanding commercial comparisons with older, more widely adopted forms of media; for a while there, it was outselling The Goblet of Fire, the much-anticipated fourth book in the Harry Potter series. It would still be capable of sneaking onto top-ten games charts as late as 2010, even as Battle.net would swarm with more Diablo II players at that late date than it ever had before. The game’s lifetime sales, which are still being added to in a significant way to this day via digital storefronts, must surely number well into the tens of millions, dwarfing even the enormous success of Diablo I by an order of magnitude and a whole lot more.

Diablo II’s four acts are separated by the most elaborate and extended cutscenes Blizzard had created to this point. They may have little to do with the rest of the game, but they’re certainly impressive to watch, easily the most visually impressive part of the whole experience.
Of course, low system requirements were far from the only reason for Diablo II’s mind-boggling success. Blizzard North really did find ways of making the notoriously addictive Diablo I even more so, whilst making sure that their game continued to feel every inch a Diablo. They figured out where they could build on what had come before and where they had best leave well enough alone.
The first game had sprung a deliciously twisted surprise ending on you, by promoting the character you had been playing all along to the position of the inheritor of the throne of the evil demon Diablo, the Big Bad he had just vanquished. This means that when you, as a Diablo I veteran, create another character to do battle against the Big Bad in Diablo II, you’re going to war in a sense against your own former self. This series is hardly noted for its thematic ambitions, but props where they are due for the Freudian audacity of this conceit.
Much more important to the large majority of players then and now, however, is the nature of the environments and the gameplay that you find yourself cast into. And here the most obvious change is that Diablo II is bigger than what came before — much, much bigger. The game is divided into four acts, the first three of which are easily as large as the original Diablo. Only the climax, which takes place in Hell itself, is a little shorter, both because the developers were running out of time and energy by that point and because a more abbreviated endgame just felt right to them in terms of pacing. Each act revolves around a home base much like the afflicted town of Tristram in Diablo I, a safe space to which to return to buy and sell items and treasure and heal up for the next expedition into danger.
But while the basic gameplay rhythm within each act is the same as that of Diablo I, there’s another massive difference in the details. Instead of exploring a linear series of randomly-generated dungeon levels that open up one by one as you progress, in the mold of the roguelike games that were Diablo I’s first and most important influence, here you get to wander the countryside in search of less linear adventure, guided only by a series of broad quests which you are given to fulfill and the waypoints that are placed on the map to guide you to and through them. The terrain encompasses everything from swamps to deserts, forests to mountains, culminating in the aforementioned infernal realms. Most of it too is randomly generated, with only occasional pre-crafted set-pieces, usually marking the conclusions of the quests. You’ll still spend plenty of time underground before all is said and done, in the various caves and dungeons you find scattered about the landscapes, but the open-world design does as much as the sheer added length to make the sequel feel epic in comparison to the first game. This does not uniformly delight everyone; there is an argument to be made that Diablo I is actually the purer, tighter game design of the two. But the reality is that relatively few gamers in 2000 or at any point afterward were going to complain about trading a 12-hour game for a 40-hour one.

Unlike Diablo I, which presented you with a randomized subset of a list of possible quests on each play-through, the quests in Diablo II are always the same. There are six of them in the first three acts, three in the last one. Like everything else about the game, they’re kept simple and straightforward.
Almost as impactful is the new approach to character-building. David Brevik understood well how intrinsic the bond between player and avatar is to the appeal of games like this one. In fact, he felt that Diablo I didn’t go as far as it ought to have in that area. In that game, you could choose from one of three archetypal character classes, the Warrior, the Rogue, and the Sorcerer. Each had its distinct area of strength — for the Warrior it was melee combat, for the Rogue it was ranged combat, for the Sorcerer it was magic — but all could to some extent cross the borders of their archetypes to acquire talents associated with the other classes. As a result, characters tended to grow less rather than more unique as the game went on. What was the point in having classes at all if each one was destined to end up in roughly the same place, wondered Brevik and his team as they embarked upon the sequel. In this do-over, they were determined to make sure that the player, having chosen a class at the beginning of Diablo II, would still be reckoning with the consequences of that choice 40 hours later at the climax.
Their first change to the class system was in keeping with many of the other changes they made to the sequel: to give you more classes to choose from, five instead of three, known this time as the Necromancer, the Amazon, the Paladin, the Sorceress, and the Barbarian. But that alone would do nothing to solve the problem of the classes blurring together over time. To address that issue, Brevik found inspiration in an unlikely source: the classic 4X grand-strategy game Master of Orion.
In that game and many others of its ilk, you need to increase your civilization’s level of technology via research, trade, or espionage, so that you can build faster and more fearsome spaceships, colonize inhospitable planets which you otherwise couldn’t, etc. But Master of Orion is ingeniously designed to make it practically impossible to acquire all of the technologies on the tech tree (or at least not before the question has become moot). Choice and happenstance dictate that you will be forced to work with a different mix of technological strengths and weaknesses every time you start a new game, forced to adapt your strategy appropriately; this is one of the keys to Master of Orion’s uncanny longevity, one of the reasons it is considered such a classic.
Brevik imported a system much like that one into Diablo II’s character building. As your character levels up, he receives points which you can invest into skills — 150 skills in all, 30 for each character class, with absolutely no crossover from class to class. This alone serves to ensure that each class stays unique from first to last. But Diablo II then goes much further than this, in order to ensure that not just each character class but each character remains unique. In the course of a typical play-through, you can expect to earn about 35 skill points. This is nowhere near enough to cover all of the 30 skills your character can theoretically learn, meaning that you have to choose areas of specialization within a class. Thus one person’s Necromancer is all but guaranteed to play very differently from another’s. Maybe the one concentrates on building golems from mud and clay, while the other prefers to raise up hordes of skeletons from the corpses of enemies. The same principle applies to all of the other classes.

The Paladin’s skill tree. Skills are grouped into three broad categories. Within each category, they become more expensive as you move from left to right. So, another choice that confronts you is whether to buy a wide variety of less powerful skills or to save up your points for one or two really devastating ones.
As a matter of personal preference, I’m lukewarm at best on Diablo II, but I don’t hesitate to admit that this character-building system is absolutely brilliant. In my opinion, it’s the best, most innovative single design choice that was made for the game. Needless to say, it lends enormous replayability for those who are buying the core experience which Diablo II is selling. To further encourage you to start all over again as soon as you finish the game the first time, an advanced difficulty level, known as Nightmare, opens up only once you’ve triumphed at the standard difficulty. And then an even more advanced one, known as simply Hell, opens once you’ve finished on Nightmare. You can tackle these with a new character or keep playing with the old one, trying to get him all the way to the level cap of 99. Blizzard did not build their games in the expectation that they would be played through once and then set aside.
The definitive expression of that ideology was the online multiplayer modes that had been included in every Blizzard game since Warcraft I, and greatly enhanced since the release of Diablo I by the Battle.net service. Despite its pioneering status, multiplayer had actually been something of a last-minute addition to the first Diablo, implemented by a team that was helicoptered in from Blizzard South while Blizzard North was trying to get the rest of the game finished. The end results displayed that in some unfortunate ways. All of the data pertaining to one’s character was stored locally on one’s own computer — an open invitation to break out the old hex editor and start cheating. And this players most definitely did, until online Diablo had become a preposterous circus of tricksters, grifters, and griefers.
Blizzard fixed most of those problems for Diablo II, by the simple expedient of storing Battle.net characters on their own servers instead of on their players’ hard drives. Knowing well how important online play had been to the stunning uptake of Starcraft, Blizzard was a good, careful steward of this aspect of Diablo II. Up to eight players could roam simultaneously through the landscapes from any of the game’s four acts, where they could choose to join together to defeat the monsters, engage in free-for-all battle with one another, or divide up into teams to do a little of both. Like single-player Diablo II, it wasn’t the deepest experience to be had in the world of gaming, but plenty of people found it plenty compelling, especially at Battle.net’s asking price of completely free to anyone who had gone out and bought the game. (Blizzard was able to offer this free service largely because the game sessions themselves still employed a client-to-client architecture once the characters being played had been downloaded from the official servers; this kept bandwidth costs to a minimum.) Blizzard encouraged guilds and other forms of socializing to keep people coming back and ran ladder boards and the like to keep the competitive fires burning, all of it for literal decades after Diablo II first hit stores. Throughout the aughts and beyond, hundreds of thousands of players could regularly be found on Battle.net enjoying their host’s largesse.

Diablo II isn’t the sort of game that looks all that nice in screenshots. In practice, however, its special effects convey palpably your character’s increasing powers as you climb the skill tree.
So, for a certain kind of commercially focused games studio — exactly the kind that Blizzard happened to be — Diablo II was the veritable Platonic ideal of a sequel. It fixed its predecessor’s few flaws whilst being dramatically bigger, plus deeper in the handful of places where it could get away with it without losing its fundamental Diablo-ness. And somehow Blizzard North managed to make the interface through which all of this happened even more elegantly intuitive than before; this was the element that the many people who made “Diablo clones” never could quite figure out how to match. Small wonder that Diablo II sold like $1 ice-cream cones on the hottest day of the year.
As for me: my own reservations about Diablo II echo those I already expressed in my article on Diablo I. Even with the modicum of extra depth that the revamped class system in particular lends to the sequel, it’s still a game where you spend most of your time roaming over algorithmically generated terrain and clicking on monsters fairly mindlessly until they die. The folks at Blizzard North made no secret that they were consciously trying to make their game as addictive as crack cocaine, by appealing directly to the lizard brain’s pleasure centers: kill ever bigger monsters, find ever better stuff, grow ever stronger, all without having to expend too much mental energy on the endeavor. Blizzard programmer Peter Kemmer describes Diablo II as “basically slot machines inside of slot machines inside of slot machines,” a meticulously engineered dopamine-delivery system. For me, Diablo II is gaming’s equivalent of junk food: it feels really good to eat at first, then becomes hard to stop eating, even after it has begun to feel less good. Much though I have to admire Diablo I and II alike for their their real achievements in design and implementation, I do prefer to play games that don’t feel quite so calculating, ones that are able to engage me in the more — for lack of a better word — humanistic ways that they never even attempt.
But then again, as I’ve said a million times before: I’m just one guy on the Internet. You do you, my friends. Even the most health-conscious of us sometimes just want to open a big bag of chips and go to town.

Another addition to Diablo II was mercenaries who could be hired to help you with tough fights. The Lord of Destruction expansion pack made it possible for them to accompany you through the whole game, gaining levels just like your main character. This effectively turned Diablo II into a party-based game, if you chose to play it that way. (And note also what a distinct difference the expansion pack’s resolution bump makes…)
Blizzard’s crowning achievement in the context of Diablo II came precisely one year after it was first released, when they shipped the Lord of Destruction expansion pack. Unlike Hellfire, the disowned stepchild of an expansion to Diablo I, this pack was developed in-house by the same people who had made the base game to which it was attached. They added another slate of fit-and-finish improvements to an already ridiculously polished game, including an optional bump in the graphics resolution to 800 X 600. (Cue the sarcastic comments from hardcore gamers to whom this was still a stone-age figure.) There were also two new character classes with new skill trees, while the heart of the matter was a fifth act to play through once the first four had been finished. Lord of Destruction sold predictably well, until it was integrated into the Diablo II Battle Chest that would remain a fixture on store shelves until the very idea of buying computer games on physical media began to seem anachronistic.
Diablo III wouldn’t arrive until 2012. Partly this was down to the departure of a burnt-out David Brevik from Blizzard, partly to the distraction of running World of Warcraft, the most popular MMORPG of all time. (In other words, Blizzard’s winning streak continued.) But I suspect that the biggest stumbling block may have been that it just wasn’t clear where to go with a third Diablo. The second game had mastered the brief to such a degree of refined perfection that the prospects for further improvements seemed only marginal. That did still leave the possibility of doing something daringly different — except that the Diablo brand had become so closely identified with a specific gameplay model that the reception of any such departure would be doubtful in the extreme, even if Blizzard had been the type of studio to indulge in such conceptual leaps. So, all that was left was to wait for enough time to pass and for computing technology to improve enough that the old formula could seem fresh again inside a new suit of audiovisual clothing. After a couple of false starts, this is exactly what Blizzard wound up doing.
Even today, when not only a third but a fourth game have joined it in the series, Diablo II remains a monument in its own right. Earlier in the very year that I find myself writing these words, Blizzard released a remastered version of the game, creating in the process new bosses to fight, a quarter-century after the last new Diablo II content. It shot up the bestseller charts all over again, winning fans who hadn’t yet been born when Diablo II was new on store shelves. Clearly its algorithmic, friction-free approach holds up for many people today as well as ever. Yes, it does leave me with mixed feelings in some ways — and yet I would be the last person to deny that Diablo II knows what it wants to do and pulls it off with stupendous aplomb. The slot machines continue to whir as enticingly as ever.
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 Games That Sell! by Mark H. Walker, Play Nice: The Rise, Fall, and Future of Blizzard Entertainment by Jason Schreier, Stay Awhile and Listen, Book II: Heaven, Hell, and Secret Cow Levels by David L. Craddock, and Postmortems from Game Developer, edited by Austin Grossman.. Computer Gaming World of February 1998, September 2000, and October 2001. Retro Gamer 43, 103, 163, and 255.
Where to Get It: The aforementioned Diablo II: Resurrected is available on Steam as a digital purchase. There are options included to “downgrade” the game to play like the one I played for this article. Note, however, that you must have an active Battle.net account in order to play, even in single-player mode.


















































