Diablo 3 Screenshots and Images - Mac

Diablo 3
Game Description:Diablo III picks up the story twenty years after the events of Diablo II. Mephisto, Diablo, and Baal have been defeated, but the Worldstone, which once shielded the inhabitants of the world of Sanctuary from the forces of both Heaven and Hell, has been destroyed, and evil once again stirs in Tristram. Playing as a hero from one of five distinct character classes, players will acquire powerful items, spells, and abilities as they explore new and familiar areas of Sanctuary and battle hordes of demons to safeguard the world from the horrors that have arisen.
G4TV Rating
4.5 / 5
  • Avg User Rating
    (5 Ratings)
    3.2 / 5
  • Rate This Game

Diablo 3 Screenshot & Image Galleries

  • Sessler's Soapbox: Diablo III's Flaming Fanboys

    Posted: August 13, 2008

    33,068 Views | 03:01 | 36 Comments

  • X-Play Gaming Update 08.08.08

    Posted: August 8, 2008

    2,333 Views | 01:24 | 2 Comments

  • Diablo Retrospective

    Posted: July 10, 2008

    14,370 Views | 02:35 | 3 Comments

  • X-Play Gaming Update 07.03.08

    Posted: July 3, 2008

    4,872 Views | 02:28 | 2 Comments

  • Preview: Diablo III

    Posted: July 1, 2008

    29,453 Views | 02:28 | 15 Comments


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"/>