Patch Day, the B.net App, CASC and You :)

  • Updated for Diablo III: Reaper of Souls Patch 2.4.3

    As of patch 2.4.0, Diablo 3 will not run at all on 10.8.5 or earlier. 10.10.5 or later is now required to play Diablo 3 (original and Reaper of Souls). All support prior to 10.10.5 has ended and operating systems older than this will not be addressed.

    Special Note for Mac OS X 10.6.8 (Snow Leopard) Users

    As of Diablo III patch 2.0.1, if you are running 10.6.8 (Snow Leopard), you will no longer be able to play Diablo 3. The minimum operating system is now 10.10.5. Snow Leopard is locked out of the game completely and you must update to at least 10.10.5 in order to play. 10.12.0 or later is recommended, though Mavericks (10.9.5) may still launch the game, but only for a little longer as of this update (03-08-2017). 8 GB of RAM or more is strongly recommended for optimal gameplay.

    Also, as of patch 2.0.1, the Launcher will initiate a Tools patch which will download the new Battle.net Desktop Application if you have not already installed it yourself using the Battle.net Desktop App link in your Account Summary page. Once downloaded the Battle.net Desktop Application will then launch and will be the only way to start Diablo III and Diablo III: Reaper of Souls.

    The CASC Filesystem

    Patch 2.2.0 brings with it a new filesystem called CASC (Content Addressable Storage Container) to replace the aging tech found in the MoPaQ (MPQ) filesystem. CASC enables Blizzard to perform much quicker updates (when warranted) and very importantly, eliminates the cache found in the MPQ system. The elimination of the cache means no file redundancy, faster asset loading, and generally superior performance to the current MPQ system.

    There are, however, slight changes to troubleshooting steps, which are outlined below with updated information. There is also one directory within the Diablo III folder that you do not want to touch, ever. That would be this directory:

    /Diablo III/Data/data

    Under no circumstances should you ever do anything with this folder except for the permissions reset outlined in the steps below. Failure to heed this warning will cause you to have to reinstall the game. CASC is not fault tolerant if you edit, remove, or lock any of the files in the /Data/data directory. This directory contains indexes for the Data.xxx files, and because each installation is unique, you cannot use files with the same name from anyone else's install to "fix" your install. If this directory is altered in any way by the user it will require reinstalling the game from scratch.

    Patch Day and Global Play

    On the day of a Diablo III patch, Global play is not available right away because each of the three regions, The Americas, Europe, and Asia each receive their respective client updates at different times. Generally it is The Americas first, then Europe, and finally Asia.

    If you are using a client (any language) designated as belonging to The Americas region, you will initially only be able to play in the same region, as Europe and Asia have not received their updates yet. This usually persists for approximately sixteen hours, at which point you'll usually be able to log into the Europe region. After approximately one day (twenty four hours), you should have full access to the Asia region as well.

    If you are using a client (any language) designated as belonging to the Europe region, once the patch is deployed to The Americas region, you will not be able to access Global Play for that region. You will be able to log into both the Europe and Asia regions until their respective patch update cycle begins (commonly referred to as patch day maintenance).

    If you are using a client (any language) designated as belonging to the Asia region, once the patch is deployed to The Americas, you will not be able to access Global Play for that region. You will be able to access the Europe region until its patch update cycle begins, and you will also be able to log into the Asia region until your patch update cycle also begins.

    Patch Day Update Looping and Global Play

    On patch day, under normal circumstances, for those logging into their own home region after the new patch is deployed for that region, gameplay usually starts without a problem. However, for those utilizing the Global Play option (accessing either of the two regions that is not your home region) things can become problematic.

    As noted above in each of the region examples, you can only access certain regions during the patch update cycle. If you start Diablo III after successfully updating to the new patch and attempt to access a region that has not yet received the update, your client may go into a "patch loop" where it says you need to download a new patch to play every time you log in. Your Battle.net Desktop Application will check for the update, but since you have already actually received the update, it will read "Game is up to date" and the Play button will light up as normal. In order to keep this from happening, you must log into only your home region during the course of the patch update cycle. Only when you see all three regions' service status pages indicate that the patch cycle is complete will you have full access to the Global Play feature.

    The same situation can occur if you have not yet received the patch update but the region you are attempting to access has already received the patch update. As with the previous example, you should avoid attempting to log into any region other than your own home region.

    __________________________________________

    Battle.net Desktop Application Related Issues

    Note: Before attempting to use the following troubleshooting instructions, first run the Battle.net Desktop Application (if possible) and select the Diablo III icon and then click the Options pulldown menu directly beneath the Diablo III logo in the main window and select Scan and Repair option.

    Under no circumstances should you attempt to play the game before installation and/or patching is complete. If you do so, you will corrupt the files being installed. It is safe to click Play only after the progress bar has disappeared from the Battle.net App main window.

    Stuck at Initializing: If you are attempting to patch Diablo III, but your Battle.net Desktop Application gets stuck on the "Initializing..." phase, the following instructions should remedy the situation:

    Delete the following files/folders:

    /Users/Shared/Battle.net/Agent/Agent.db
    /Users/Shared/Blizzard/Battle.net
    /Users/Shared/Blizzard/Battle.net.temp (if present)
    /Diablo III/Diablo III.mfil (if present)

    Once done deleting those files, make sure all permissions are set properly in Diablo III's main folder by doing the following:

    1) Get Info (in the Finder) on the Diablo III folder.

    2) Click the padlock icon and enter your password to authenticate yourself.

    3) For the Everyone group, set it to Read and Write.

    4) Click the cogwheel icon and select Apply to enclosed items. Select OK to confirm your action.

    5) Close the Get Info Window.

    6) Repeat steps #1-5 on the /Users/Shared/Battle.net folder.

    Now run the Battle.net Desktop Application. The Battle.net Desktop Application will then begin again at "Initializing...", but should only stay there for a few moments while it determines which files are in place and which must be downloaded. Let the Battle.net Desktop Application fully update the game. Do not click Play until the Battle.net Desktop Application window shows the word “PLAY” in the big button at the bottom of the window and there is no progress bar on the screen at all, indicating that Diablo III has fully patched and/or rebuilt its cache.

    __________________________________________

    Failed to Create/Download a Required File: If you see this message, you may have an issue with permissions or a problem with the Battle.net Tools. The solution to both problems is the same as the steps for solving the Stuck at "Initializing..." problem,. The full process is outlined as follows:

    Delete the following files/folders:

    /Users/Shared/Battle.net/Agent/Agent.db
    /Users/Shared/Blizzard/Battle.net
    /Users/Shared/Blizzard/Battle.net.temp (if present)
    /Diablo III/Diablo III.mfil (if present)

    Once done deleting those files, make sure all permissions are set properly in Diablo III's main folder by doing the following:

    1) Get Info (in the Finder) on the Diablo III folder.

    2) Click the padlock icon and enter your password to authenticate yourself.

    3) For the Everyone group, set it to Read and Write.

    4) Click the cogwheel icon and select Apply to enclosed items. Select OK to confirm your action.

    5) Close the Get Info Window.

    6) Repeat steps #1-5 on the /Users/Shared/Battle.net folder.

    Now run the Battle.net Desktop Application. The Battle.net Desktop Application should begin downloading properly at this point and you can proceed normally. Take careful note of the underlined part in the section that tells you which files and folders to delete. The /Diablo III/Update folder can be safely discarded and allowed to be rebuilt by the Battle.net Desktop Application. As with all other Battle.net Desktop Application related troubleshooting steps, do not click Play until the Battle.net Desktop Application window shows the word “PLAY” in the big button at the bottom of the window and there is no progress bar on the screen at all, indicating that Diablo III has fully patched in order to avoid file corruption.

    __________________________________________

    Diablo III Crashes due to Corrupt Files

    If you are experiencing crashing when logging in or performing certain actions in the game and this can be repeated with fair certainty, you probably have one or more corrupt files. The following instructions will show you how to delete the potentially problematic files and allow the Battle.net Desktop Application to rebuild the game's indexes.

    Delete the following files/folders:

    /Users/Shared/Battle.net/Agent/Agent.db
    /Users/Shared/Blizzard/Battle.net
    /Users/Shared/Blizzard/Battle.net.temp (if present)
    /Diablo III/Diablo III.mfil (if present)
    /Diablo III/Data/config
    /Diablo III/Data/indices

    Once done deleting those files, make sure all permissions are set properly in Diablo III's main folder by doing the following:

    1) Get Info (in the Finder) on the Diablo III folder.

    2) Click the padlock icon and enter your password to authenticate yourself.

    3) For the Everyone group, set it to Read and Write.

    4) Click the cogwheel icon and select Apply to enclosed items. Select OK to confirm your action.

    5) Close the Get Info Window.

    6) Repeat steps #1-5 on the /Users/Shared/Battle.net folder.

    Now run the Battle.net Desktop Application. Let Diablo III rebuild its cache. It can take between 15-60 minutes depending on the computer and drive being used. Do not click Play until the Battle.net Desktop Application window shows the word “PLAY” in the big button at the bottom of the window and there is no progress bar on the screen at all, indicating that Diablo III has fully patched and/or rebuilt its cache.

    Error 3006 or 3007 when attempting to log into Diablo III

    Error 3006: This error occurs when the region you are attempting to log into is either undergoing emergency maintenance or has an as of yet unresolved issue. If you receive this error, please wait a few minutes before attempting to log in again in order to give the Blizzard IT team time to resolve the issue.

    Error 3007: This error occurs when your connection to the Battle.net servers is unstable. If you are continually receiving this error, you should follow the troubleshooting instructions in the Error 3007 Support Article:

    https://us.battle.net/support/en/article/error-3007

    Error 33: If you are getting this error when attempting to log in, the Battle.net system is still undergoing scheduled maintenance and is not available for play. Please wait a few minutes before attempting to log in again. If you are still unable to log in, you should check the Service Status forum to see if Battle.net has been brought back up or not.

    Service Status Forum: http://us.battle.net/d3/en/forum/5394512/

    @BlizzardCS Twitter feed: https://twitter.com/BlizzardCS

    For any issues not specifically mentioned here, please start a thread with your specific problem, as well as your System Information. Instructions for obtaining system information are provided below:

    Obtaining and Posting System Information

    1) Click on the Apple Menu while holding down the Option key and select System Profiler (10.6.8) / System Information (10.7 and later).

    2) Copy the information from the following sections and paste them into your post. Please copy in the following order: Hardware Overview, Graphics, and Software. Do not include any serial numbers, hardware UUIDs, or account/login names or information in your post.

    Making Sure You Are Up To Date

    As of patch 2.0.1 10.6.8 is no longer capable of launching the game and 10.10.5 is the minimum supported operating system. 10.12.0 is the minimum recommended operating system and 10.11.5 is the current optimal operating system. Below are the links to get you up to date with each version of the OS.

    10.10.5 Combo Updater: https://support.apple.com/kb/DL1832?locale=en_US

    10.11.6 Combo Updater: https://support.apple.com/kb/dl1885?locale=en_US

    10.12.3 Combo Updater: https://support.apple.com/kb/DL1905?locale=en_US

    The latest Operating system is Sierra, currently at 10.12.3, found in the App Store. Its most recent associated Combo Updater is linked in this section.

    Latest nVidia Drivers (courtesy MysticalOS): https://us.battle.net/forums/en/wow/topic/18300616773

    Ignore listed restrictions. These two installers work for all Macs with nVidia hardware from the 320M up to current hardware as of this post.

    EFI and SMC Firmware Updates for Intel Macs: https://support.apple.com/en-us/HT201518

    Note: After installing any operating system update or Firmware update, it is advised that you perform an SMC Reset. Please refer to the following link for information on how to reset your computer's SMC.

    Resetting the SMC:

    https://support.apple.com/en-us/HT201295

    ________________________________________________
    Diablo III and World of Warcraft Technical Support MVP
    Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
    Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
    Caution: This cookie bites back.
  • Thanks Tia!

    /stickied