Diablo II Screenshots and Images - PC

Diablo II
Game Description:The story unfolds in four Acts, one for each major town. From the ruined town of Tristam, you venture forth to vanquish the evil presence of Andariel in the Monastery of the Sisters of the Sightless Eye, nestled in the frozen steppes. From there you travel across deserts and jungles to defeat the devils Mephisto and Baal until you face Diablo, the ultimate evil. Diablo II is four times larger than the original, includes five character classes, addition of 3D graphics support, day/night cycles, weather effects, hordes of enemies, as well as tons more weapons, armor, spells, items, and more. Did we mention Diablo is back?
G4TV Rating
  • Avg User Rating
    (9 Ratings)
    5 / 5
  • Rate This Game
  • Top 100 Video Games of All Time #19 - Diablo 2

    Posted: June 15, 2012

    10,174 Views | 01:23

  • BlizzCon 2011 Cosplay Contest

    Posted: November 8, 2011

    19,119 Views | 02:42

  • Diablo Retrospective

    Posted: July 10, 2008

    14,370 Views | 02:35 | 3 Comments

  • X-List: Top 5 Blizzard Games

    Posted: June 30, 2008

    5,724 Views | 01:13 | 9 Comments

  • Diablo II Cinematic Trailer

    Posted: June 29, 2000

    8,510 Views | 01:41


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>