Scheduled Maintenance and Patch 1.0.2c

It looks like the next round of patch fixes are abound with the incoming DiabloWikiRMAH. This list of changes are also extremely short, only affecting a couple of things. With this patch, however, it comes with a heavy heart to say that we will see the death of Error 37. We’ve lived it, we’ve loved it, but the Error will no longer be.

In addition, we’ll no longer see Diablo’s Claw or related Cuddlebear items being linked in chat.

We will be performing scheduled maintenance on Diablo III starting tomorrow (6/12) at 5:00 a.m. PDT in order to deploy patch 1.0.2c. We anticipate that maintenance will conclude and that all services will be available at approximately 11:00 a.m. PDT. Patch notes are available below.

Important: Please note that you will not be prompted to download patch 1.0.2c until the patch is live in your home region. If you are logging in from a European or Asian client, you will need to wait for this patch to release in that region before it can be installed. Additionally, if your home region is the Americas, you will be unable to log into Europe or Asia using Global Play after patch 1.0.2c is live until those regions have also patched.

For reference, here are the scheduled maintenance times for each region:

The Americas: 5:00 a.m. PDT to 11:00 a.m. PDT
Asia: 1:00 p.m. PDT to 4:00 p.m. PDT
Europe: 6:00 p.m. PDT to 12:00 a.m. PDT

Please note that these times are subject to change. For time zone assistance, please visit:

Patch notes are as follows:

Diablo III Patch 1.0.2c – v.

The latest client patch notes can be found here.
Visit our Bug Report forum for a list of known issues.
Hotfixes made in addition to changes in patch 1.0.2c can be found here.


  • If the authentication service is busy, the login checkbox will now wait at “Authenticating Credentials” until a player’s login attempt can be processed. As a result, players should no longer encounter Error 37 when logging in.
  • Achievements have been granted to players who previously completed their objectives, but were not correctly awarded completion credit.

Bug Fixes

  • Fixed several crashes which occurred when clicking on player-generated item links in the game client

All Patch notes are archived in DiabloWiki.Net for future reference.

Related to this article
You're not logged in. Register or login to post a comment.

19 thoughts on “Scheduled Maintenance and Patch 1.0.2c

  1. Since the cash out procedure can be traced with ease (each individual sale needs to be confirmed with a cell phone code) AND the control mechanism includes a 3 day waiting time to further trace/confirm it, I hope Blizzard will confiscate all gold/money from known Crook accounts.

    Rather easy to trace actually. Simplest would be to put their accounts on hold and delete when found involved in massive gold transfers.

    I think the next few days we will see a massive amount of banned and locked accounts by Blizzard. My guess is around 200 k 🙂 deleted accounts.

    The control mechanism in place is – for the cash out procedure – rock solid. Finally.

    • On the contrary. To cash out every crook can be traced by Blizzard. These maffia guys have one problem: they have gold they cant sell or cash out out without approval by Blizzard :

      This step is what these bandits are afraid of and they did everything to postpone the RMAH. Glad their reign of terror is almost over in game.

  2. You know what would be awesome to see in one of these bug fix patches? The Attack Speed bug fixed. Why are they waiting until a major patch to do this?

    Every time I touch a Frenzy shrine I cry because I get the damage output Inna’s Pants is supposed to be giving me right now.

      • I figured something like the RMAH being made available would be listed in the patch notes, but it isn’t… I kind of expect a ton of banned accounts just before the RMAH release.

  3. and i seriously just went back through with a second character this weekend and searched out all the lore books i got on the first day and didnt get credit for…. ahhh well! 🙂

  4. Was hoping for some mention of getting kicked back to the Siegebreaker quest after joining a friend’s Act 1 game. I have moved several steps past that quest a half a dozen times now and every time after joining any Act 1 game it moves me back to “kill the Siegebreaker” step.

    • It would kick you back if you haven’t completed any quest after that. Your progress gets wiped if you’re mid-quest and you join another game. I’m not sure if that’s the case for you, but there’s a LONG stretch after siegebreaker before the game actually completes another segment of the quest.

  5. It may be petty, but stating everything in PTD and telling your clients to just “look it up” is….Not all that client-friendly. Putting the US servers in CMT/PTD, the E uropean in CET/GMT (or CET/EET) and the Asian in…whatever time zones are most prevalent there, would be 5 seconds of work for them, and would be 10x as client friendly to all E uropean and Asian players.

    • Agreed. It only takes 30 seconds of work for the one person making the post, to save 30 seconds of work for thousands of people. Efficiency, man.

  6. “In addition, we’ll no longer see Diablo’s Claw or related Cuddlebear items being linked in chat.”

    That’s not at all what the patch note says:

    “Fixed several crashes which occurred when clicking on player-generated item links in the game client”

  7. I’m not sure which is correct, but in-game the Breaking News doesn’t say 5am-11am for The Americas, but actually 5am-8am.

  8. It doesn’t say that they’ve stopped players from making custom links. It just says that they’ve stopped them from crashing the game.

Comments are closed.