On the other hand, the graphics in Diablo II are disappointing, especially when compared with those in the original game. When Diablo was released at the end of 1996, its SVGA graphics were amazing. More than three years later, those low-resolution graphics no longer look impressive and barely look adequate, and yet that's all Diablo II offers. There are some notable graphical improvements, such as the game's lighting and translucency effects and the new parallax scrolling that gives a 3D gloss to otherwise flat objects, but the game's 2D graphics are generally disappointing and look pixelated and lack sharpness on larger monitors.

The graphics are also almost constantly obscured by the game's automap function. You can turn the map off or dim its brightness, but the game's outdoor environments make the map even more necessary for navigation than it was previously, so most of the time it'll be blocking your view of the game world. There should have at least been an option to display a smaller version of the automap in a corner of the screen where it wouldn't intrude as noticeably. Fortunately, the developers made some tweaks to the game's design and interface, and the resulting improvements are noticeable, even though they may not go far enough. For one thing, the game has no discernible loading-time transitions between areas - only between acts. In addition, instead of having to constantly mouse-click to initiate attacks, you can now just hold the mouse button down to continuously attack a creature, which limits the amount of tedious mouse-clicking that was required in the original. There are also additional hotkeys available for skills or spells, but there still aren't enough available to give quick access to all of a character's useful abilities. Surprisingly, Westwood's Nox did a better job of granting you quick access to an area map and your character's abilities, spells, and items, even though accessibility was a key strength of the original Diablo.

While Diablo's cooperative multiplayer mode was undeniably addictive and included a variety of difficulty levels unavailable in the single-player game, players still complained about the fact that most of the game's quests were only accessible in the game's single-player mode. In Diablo II, the single-player and multiplayer modes are almost identical, and all of the quests and difficulty levels are available in both versions of the game. Multiplayer Diablo didn't permit you to save the game whenever you wanted, and a character's death resulted in a hazardous and ill-equipped trip back to the same dangerous area to retrieve the character's valuables. The designers of Diablo II apparently believed the resulting tension generated by the multiplayer mode of the original game was worth porting to the single-player mode, because that's the only way to save your game in the sequel. You can no longer save the game whenever you want, and when a game is saved (either automatically or when you exit a session), new monsters are generated to populate the gaming world. There are waypoints that can be activated so you can get back relatively close to where your character was last exploring, but creatures will have respawned in that area, even if it was previously cleared out. Leaving a game without using the "save and exit" option in the main menu could result in the loss of recently acquired booty. While the new system does prevent you from constantly reverting to saved games and robbing yourself of the thrill of danger while exploring a new area, it's a design decision that's bound to frustrate some players.

The most significant problem with multiplayer Diablo was that it was too easy for hackers to create powerful magic items and alter character attributes and other data files, since all of the game data was stored locally, on players' hard drives. Within a couple of weeks of Diablo's release, it was virtually impossible to play a non-password-protected game on Blizzard's free Internet Battle.net server without being harassed by players solely intent on ruining other players' games with their unnaturally overpowered characters. Battle.net now has an optional archive to store character data, which should finally cure the hacking problems that plagued the original game, since would-be cheaters won't be able to alter that data anymore.

Blizzard's Battle.net Internet servers, which were initially launched concurrently with the release of the original Diablo, have proven to be unable to cope with the number of players currently trying to play Diablo II online. Gameplay has so far proven to be laggy, which is surprising considering Diablo II played well during beta testing and the original game played smoothly online. Once additional capacity is added, Battle.net should be a more accessible and enjoyable option, which is particularly relevant since features such as worldwide rankings and the game's hard-core mode are only available online. Blizzard does deserve credit for adding the hard-core version of the game, which prevents you from resurrecting slain characters no matter how many hours have been devoted to developing them. This feature makes for a truly tense and exciting gaming experience - it's an option that many won't dare try, but death for a character in Diablo's spiritual predecessors, Nethack and Rogue, could have similarly brutal consequences, and those games proved to have enduring appeal.

The development team for Diablo II clearly made it a priority to respond to all of the perceived problems with the original game, and players will likely appreciate most, if not all, of the resulting design changes. Diablo II offers a larger gaming world, the opportunity to play an open multiplayer game without being intruded upon by cheating players, and a more complex and interesting character development system. While its graphics appear somewhat dated, Diablo II has incredible replay value, and most importantly, it offers a lot of addictive gameplay in either the single-player or the multiplayer mode.