Although this product has been released, it remains under active development - information may change frequently and could be outdated or irrelevant.

Warnings

This game requires a constant internet connection for all game modes.

Key points

Continues to receive frequent content, balance, and quality-of-life updates, including live service features like Seasons. Earlier physical copies of the game advertise an Auction House; this was permanently closed in early 2014 due to negative player feedback and developer review.[1]

General information

Availability [ edit ]

All versions require Battle.net DRM and a constant internet connection for all game modes.

DLC and expansion packs

Some regions have in-game micro-transactions (not listed below).[2] Name Notes Diablo III: Reaper of Souls Can be bought from the Battle.net store. Diablo III: Necromancer DLC Can be bought from the Battle.net store.

Version differences [ edit ]

Starter Edition [ edit ]

The Diablo III Starter Edition provides players the ability to try out a free version of Diablo III, with several limitations:

Players cannot progress past the Skeleton King, midway through Act I.

The level cap is 13 as opposed to 60 (70 in the expansion).

Matchmaking is available only with other Starter Edition players, including public matching and private invitations. [3]

Global Play is not available. Players attempting to connect to the Starter Edition in a region other than their Battle.net account's home region will receive an Error 12.

Game data [ edit ]

Configuration file(s) location [ edit ]

System Location Windows %USERPROFILE% \ Documents \Diablo III\D3Prefs.txt \Diablo III\D3Prefs.txt macOS (OS X) ~/Library/Application Support/Blizzard/Diablo III/D3Prefs.txt

Save games are stored on the Battle.net servers.

Video [ edit ]

Video settings.

Input [ edit ]

Audio [ edit ]

Audio feature State Notes Separate volume controls Master, SFX, voice, ambience, music Surround sound 4.0-7.1, Pro Logic Subtitles Available for cinematic and quest dialogues. Closed captions Mute on focus lost Can be toggled in options menu.

Localizations

Language UI Audio Sub Notes English US, EU, and SEA Traditional Chinese Simplified Chinese Not available outside of Mainland China. French German Italian Korean Polish Brazilian Portuguese Russian Spanish Latin American Spanish

Network [ edit ]

Multiplayer types

Type Native Players Notes Local play Console versions only. LAN play Online play 4 Co-op



Connection types

Ports

Protocol Port(s) and/or port range(s) TCP 80, 1119, 6881-6999 UDP 1119, 6120, 6881-6999

Universal Plug and Play (UPnP) support status is unknown.

VR support [ edit ]

Issues unresolved [ edit ]

Window Unresponsive [ edit ]

Game client window becomes unresponsive when a dialog box is opened in the background.

Issues fixed [ edit ]

Video Card Not Supported [ edit ]

Unsupported video card error.

Demo version of Swiftshader, on Intel G41.

You may receive the error message:

We have detected that your video card is not supported by Diablo III.

Diablo III will block certain systems running the game if it does not detect a certain spec of video card. However, it is possible to force the game to run on any video card (even if it does not meet the minimum specification of the game).[6]

This fix has been acknowledged by Blizzard, but comes with its own warning from Omrakos:

...if you decide to do this and have terrible performance as expected, please do not contact us reporting it. We know the unsupported cards aren't going to perform well and there's nothing we'll be able to do to remedy it.[7]

Method 1 - Press Escape [ edit ]

Method 1 - Press Escape [citation needed] Method 1 - Press Escape Pressing Esc instead of cancel will make one's computer attempt to load the client. Pressing cancel will load up a list of unsupported video cards on Blizzard's website.

Method 2 - Edit D3Prefs.txt [ edit ]

Method 2 - Edit D3Prefs.txt [citation needed] Method 2 - Edit D3Prefs.txt Go to %USERPROFILE% \ Documents \Diablo III\ Open D3Prefs.txt . Change HardwareClass "0" to HardwareClass "1" Change DisableTrilinearFiltering "0" to DisableTrilinearFiltering "1" Save your changes.

Method 3 - Swiftshader [ edit ]

Method - Swiftshader [citation needed] Method - Swiftshader Using the program Swiftshader can successfully load the game even on extremely low powered machines. For example, the game can be run on integrated graphics as low powered as the Intel G41, albeit at extremely low frame rate.[8]

High DPI Setting [ edit ]

Disable DPI scaling settings.

By default, it appears as if Diablo III has a number of issues with high or custom DPI settings in Windows.

This can result in:

Mouse cursor not being moveable whilst in fullscreen mode.

Mouse being imprecise on the screen.

Taskbar showing over the game window.

High DPI Setting fix[9] High DPI Setting fix Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab. Select, 'Disable display scaling on high DPI settings'.

Login Errors [ edit ]

These messages may appear when trying to log in.

Error 12 [ edit ]

This means that no license is attached to the Battle.net account, a problem with many users in Asia. Check this thread for more information.

Error 37 [ edit ]

This message means that the login servers are at full capacity. Official advice is to try logging in later when the servers are less busy.[10]

Error 37 workaround[11] Error 37 workaround Enter password. press ↵ Enter . Press cancel before anything happens. Log back in straight away. Notes This might be considered an exploit of the way that the client is reporting Error 37 to indicate that servers are too busy. However, this does not seem to have any particular consequences, except that Blizzard's servers will be busy.

Error 75 [ edit ]

Error 75 means that Blizzard servers are down. Check Diablo III Server Status page for updates.

Can't Move Mouse In Fullscreen [ edit ]

Disable DPI scaling settings.

This is most likely caused by high or custom DPI settings in Windows.

Method 1 - Compatibility [ edit ]

Method 1 - Compatibility[12] Method 1 - Compatibility Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab. Select, 'Disable display scaling on high DPI settings'.

Method 2 - Edit D3Prefs.txt To Windowed [ edit ]

Method - Edit D3Prefs.txt To Windowed [citation needed] Method - Edit D3Prefs.txt To Windowed If one is stuck in fullscreen mode, one can change the D3Prefs.txt settings to force a windowed mode. Open %USERPROFILE% \ Documents \Diablo III\D3Prefs.txt Make sure that this line is adjusted: DisplayModeWindowMode "0" to DisplayModeWindowMode "1"

No Diablo III License Attached [ edit ]

Method - No Diablo III License Attached [citation needed] Method - No Diablo III License Attached This error message may appear: |This Battle.net account does not have a Diablo III License attached to it. A possible fix is to correctly set the region within the game settings, within the Options > Account > Server Region settings.[13]

Overlays [ edit ]

Running programs that put an overlay over Diablo III (such as Mumble and MSI Afterburner) can cause Diablo III to crash. Use these overlays at your own risk.[14]

Problems with Steam overlay [ edit ]

Problems with Steam overlay [citation needed] Problems with Steam overlay Add DiabloIII.exe with the + Add a game on the bottom left

with the + Add a game on the bottom left Right click Diablo III in the library and choose Properties

Add -launch to the end of the target.

to the end of the target. If the game doesn't launch correctly, make sure the Battle.net Launcher application is already running before starting the game from Steam.

Cinematics not playing or are missing from cinematics menu [ edit ]

Cinematics not playing or are missing from cinematics menu [citation needed] Cinematics not playing or are missing from cinematics menu 1. Go to %USERPROFILE% \ Documents \Diablo III\ 2. Open D3Prefs.txt . 3. find the PlayedCutscene lines, and edit them to read as follows: PlayedCutscene0 "15" PlayedCutscene1 "15" PlayedCutscene2 "15" PlayedCutscene3 "15" 4. Save and exit the file, and try again.[15]

Installation Issues [ edit ]

Change Client Language [ edit ]

Update 8 June 2012: Blizzard appear to have restricted client language switching.[16] Errors 81, 82 or 84 displays: "The client does not match the accounts native language. Please, use the game native client." There is no known fix as of yet, as Blizzard controls the language restrictions from their servers.

Language change menu.

Client language files can be adjusted from the options menu. Once the change is applied, a patch of approximately 3 GB is downloaded. Client language cannot be changed back until this download reaches the 'playable' state, and one re-enters the client to change the language option again.[17]

Available languages are:

English (United States)

Spanish (Latin American)

Korean

Chinese (Traditional)

German

Spanish

French

Italian

Polish

"Updating game files" Issue [ edit ]

Some players are reporting the game getting stuck at installation in the "Updating game files" part.

Method 1 - Disable Anti-Virus Software [ edit ]

Method - Disable Anti-Virus Software [citation needed] Method - Disable Anti-Virus Software Turn off your anti-virus software and firewall. Loading the setup file again. Running the launcher as administrator.

Method 2 - Connect Using Different Network Adapter [ edit ]

Method - Connect Using Different Network Adapter [citation needed] Method - Connect Using Different Network Adapter The Blizzard Agent may be attempting to connect over the wrong network adaptor. The following steps may resolve your issue: Open the Control Panel. Select "View network status and tasks". Select "Change adapter settings". Right click on each adapter and select "Disable". Leave your primary adapter (the one that provides your internet connection) enabled. You should now have only one enabled adapter. Check that you are still connected to the internet. Go to %PROGRAMDATA% and delete the Battle.net folder (if it exists). Retry the installer/launcher.

Method 3 - Delete/Modify Agent Files [ edit ]

Method - Delete/Modify Agent Files [citation needed] Method - Delete/Modify Agent Files Go to %PROGRAMDATA% \Battle.net\Agent\ Delete or rename Agent.exe . Edit Agent.db . Change p2penable : true to p2penable : false

Installation Stuck At 10% [ edit ]

If the user has any connections configured in "Dial-up and Virtual Private Network settings" and they're set to "Dial whenever a network connection is not present," the install won't proceed past 10%.[18]

Installation Not Doing Anything [ edit ]

If the installation has yet to do anything you might need to make sure your secondary logon has been enabled. Do so by going through - Control Panel/Administrative Tools/Services, right click Secondary Logon and proceed to enable it by setting the start up type to automatic.

Low frame rate (OS X) [ edit ]

Low Frame Rate [citation needed] Low Frame Rate Using settings in the D3Prefs.txt mentioned below one can achieve a reasonable frame rate on e.g. the MacBook Pro Mid 2010 with the Nvidia GeForce 330M. Open the D3Prefs.txt and set the following to options to 1: DisableTrilinearFiltering

HardwareClass

Can't ⌘ + Tab (OS X) [ edit ]

Check that you haven't enabled Caps Lock as that disables ⌘ + Tab ↹ , although ⌘ + M still functions correctly.

Game freezes after entering the gameworld [ edit ]

Nvidia's Multi-Frame Sampled Anti-Aliasing (MFAA) can cause this issue. MFAA is enabled if you "optimize" the game using Nvidia Geforce Experience.

Disable MFAA [ edit ]

Disable MFAA in Nvidia Control Panel Disable MFAA in Nvidia Control Panel Open Nvidia Control Panel. Click "Manage 3D Settings", then "Program Settings". Select Diablo III from the dropdown menu. Scroll through the options and set "Multi-Frame Sampled AA (MFAA)" to "Off". Click "Apply".

Other information [ edit ]

API [ edit ]

Technical specs Supported Notes Direct3D 9, 11 DirectX 11 added in Patch 2.4.3.[19]

Executable 32-bit 64-bit Notes Windows The 32-bit client is still available.[19] macOS (OS X)

System requirements [ edit ]

Windows macOS (OS X)

Windows Minimum Recommended Operating system (OS) 7 8.1, 10 Processor (CPU) Intel Pentium D 2.8 GHz

AMD Athlon 64 X2 4400+ Intel Core 2 Duo 2.4 GHz

AMD Athlon 64 X2 5600+ 2.8 GHz System memory (RAM) 2 GB 4 GB Hard disk drive (HDD) 25 GB Video card (GPU) Nvidia GeForce 7800 GT

ATI Radeon X1950 Pro Nvidia GeForce GTX 260

ATI Radeon HD 4870 Support for Windows XP and Windows Vista was dropped at the end of 2017. The game no longer runs on these versions after this change.[20] However some legacy versions still exist for these users.

macOS (OS X) Minimum Recommended Operating system (OS) 10.8.x 10.9 Processor (CPU) Intel Core 2 Duo Intel Core i3 System memory (RAM) 4 GB Hard disk drive (HDD) 25 GB Video card (GPU) Nvidia GeForce 8600M GT

ATI Radeon HD 2600 Pro Nvidia GeForce GT 330M

ATI Radeon HD 5670 The game does not support FileVault and FileVault 2 on OS X