Diablo III's Error 37: "Don't Call It A Comeback!"

Last Night, Diablo III's Error 3003 may have been hot, but tonight, it looks like Error 37 is making a comeback!

Like Derek Zoolander himself, Error 37 has risen from the ashes of last night's failed walkoff with so-hot-right-now upstart Error 3003 and emerged once more as the dominant Diablo III error. The original and best, as it were.

At least now, Blizzard has set up a helpful server-status page so you can know for sure that you really and truly can't play the game right now.

Which you can't. For the third night in a row.


Comments

    This comment has been reported for inappropriate content and is awaiting review.

      Don't reply to him, just hit that handy report flag.

    Thanks Ian, your comment was so informative.

    Where is the report article button?

      just to the left of the reply button. little flag icon. dont think it appears on the mobile site though...

        I dont think #35 saw the word 'article' in your post.

        so congratulations! with the addition of one word, your post has gone from being a valid question to a pointless waste of time! thanks for playing!

    Ok this is getting a bit lame.

    Yes everyone is aware of the issues with D3. Do we really need another update on what error are YOU getting again? "for the third night in a row"

      +1, its getting pretty old pretty quick - yea its frustrating , we all get it - but I guarantee it will get better.

    played fine Tuesday night, played fine all night last night and i'm having a blast in D3.... "its not me its you"

    Eh, as much as some people might find this annoying, there is a good underlying point here.

    If it's really been three days of massive peak-use issues on a SP game, given that the company behind it has had a decade's worth of experience hosting an MMO with many, many more players and millions of dollars to rent short-term server farm capacity to solve this issue after day one....this is valid.

    They did do the stress test before launch and found issues, and it seems to still be a big issue.

    And again, this is a SP game - or at least, a lot of people are unable to secure a viable SP experience because of the server issues.

      I think it's nothing more than Kirk trying to grind an axe about his disgruntled opinions of always online. The fact that this message is telling you the server is full speaks volumes about the unexpected demand for Diablo 3 imo, and not bugs in the game per se.

        The fact that we are talking about server volumes for a single-player game speaks volumes for the stupidity of always on DRM.

        How can it be described as unexpected? It was break all sort of preorder records!

        I'm interested in this, because Blizzard, with ten years of experience in mmo's wasn't able to make "always-online" work. Speaks volumes about what this will do to gaming if it becomes the norm.

          Just because pre-orders were high doesn't necessarily mean they were able to anticipate the day 1 volume of players. I'm sure they knew it would be massive but maybe they didnt anticipate the number of people who would download it digitally over the days leading to launch?

          Not saying this is definitely the reason but it does seem strange that a company that prides itself on its brand so much would not already have at least some measures in place to avoid this.

          Just because pre-orders were high doesn't necessarily mean they were able to anticipate the day 1 volume of players. I'm sure they knew it would be massive but maybe they didnt anticipate the number of people who would download it digitally over the days leading to launch?

          Not saying this is definitely the reason but it does seem strange that a company that prides itself on its brand so much would not already have at least some measures in place to avoid this.

        Unexpected my arse. They are avoiding excess spend on servers that they might not need in a month if the population decreases.

        Thing is they are avoiding spending money on an issue they created, Most likely in order to force people to use RMAH in order to make money.

      Can we stop calling Diablo 3 a single player game?

      It's a "sequel to a game that used to let you play offline single and multiplayer modes, but had that mode surgically removed for largely cynical reasons, under the thin facade of 'improving user experience'"

      There's a difference.

    Yeah come on Kotaku, calm down, we know there are issues, but not everyone is suffering them. My mate has been playing straight all day and yesterday except for the server restarts =/

    It's been pathetic - keep reporting it.

    "At least now, Blizzard has set up a helpful server-status page so you can know for sure that you really and truly can’t play the game right now." That's actually been there since before the launch.

    Well here's hoping that by the time I get home from work I'll be able to log in no probes.
    It's time like these when I'm glad we live in a different time zone & with a low population :D

      I'm glad that with D3 we still have the option of logging in with no probes.

      That will probably come as part of D4 authentication.

        Eeek... Yeah here's hoping no games feature 'probes'.
        hahaha

    Yeah we're not concerned about your problems. Who cares if Blizzard can ship a single player game and people can't play it through no fault of their own. It's not like they paid for it or anything.

    C'mon guys- we all know that there are D3 connection issues. Yes, it's a pain in the arse. How about instead of posting an article every 3 hours reminding us that it's still broken, you could just tell us when it's working instead?

    Still amazes me that you people are not kicking up a stink about this the same way folks cracked it over Ubisofts constant online rubbish. It just amazes me. "Oh no not another post about what error message". Your kidding me right?

    Blizzard really has outdone them selves this time.

      People aren't kicking up a stink, because for the most part it's been fine. It's a vocal minority having these ongoing issues. My anecdotal experience - 6 friends and myself have the game, and we've been playing without a hitch since release. The servers were down for maintenance for 2 hours a while ago, which is STILL a shorter time than the same maintenance for SWTOR or WoW.

    Ok so Kotaku has metaphorically beaten Diablo III and it lays on the ground.

    Issues with "permanent online connection required" aside, is it really necessary to kick it in the balls?

      I just don't understand why so many gamers are willing to lie down and spread their legs so Blizzard can ball-kick them.

      If Ubisoft had pulled this, they'd be crucified. Blizzard has screwed the pooch with D3's DRM and it's biting them on the arse. If a mega-release won't let you play your single player game, then yes, it deserves beating.

        Blizzard's had a purpose, Ubisoft's didn't. With real money transactions going to take place on this game, ANY instance of people being able to exploit a part of the game won't just be people saying "oh well", Blizzard would be weathering a veritable barrage of lawsuits. They need to control any access to the game, hence most of the game assets being on internal Blizzard servers. This is the way they chose to control access. Will it be rocky at first? Sure. Is there any online launch of a massive game that went smoothly? No.

          Oh thank you. A voice of reason. A shining beacon in the wilderness. Why don't people get precisely this?

        But at the end of the day, how many Ubisoft games are still played a decade after their release? It might be shitty DRM, but the game is still great.

    I have been able to play the game fine every time I have logged in. Want to stop flogging the same dead joke over and over again?
    We get that some people are having errors, doesn't need 20 articles for each time it happens.

    Frankly, the people saying that this is a 'single-player game' are trolling as bad as that guy who keeps posting "5 hour campaign hahahhahah". They announced how the game would run MONTHS, if not YEARS ago. By pony'ing up your money, you have decided that it is not an issue big enough to not get this game for. Since Global Play was released (well over 24 hours ago now), I have not been in a situation where I have been unable to connect to at least 1 of the 3 servers.

    Do you ever write about anything else Kirk? This makes what, 5 articles in the last 3 days - or is it 6?
    Top notch journalism.

      Also, I got home and installed Diablo 3 and was online about 2.5 hours after servers went up.

      ... and have never had problems logging in/staying in/with lag/with joining friends. I've literally been bug/error free this whole time. Personally I hope Diablo 3's bugs are just targeting you through some miracle of Karma. But that seems (unfortunately) unlikely.

Join the discussion!

Trending Stories Right Now