As the Diablo 4 beta approaches, we can’t help but dread a demon from our past: Error 37

Remember Error 37? We first encountered it on May 8, 2012, one week before the launch of Diablo 3, when Blizzard gave us a heads-up that the error might pop when we tried to get into the game on launch day—but it was “no cause for concern, (opens in new tab)” they told us. Just, you know, give it a minute and try again.

Of course, it very much was a cause for concern. The Diablo 3 launch was “shaky,” as we put it (very gently) in our summary (opens in new tab) of the release day situation. Servers were crushed as people struggled for hours to get in: Our “review as it happens (opens in new tab)” reflected the mood of the moment, calling the rash of errors, disconnects, and progress resets “utter bullshit.” 

Stay in the Loop

Get the daily email from CryptoNews that makes reading the news actually enjoyable. Join our mailing list to stay in the loop to stay informed, for free.

Latest stories

- Advertisement - spot_img

You might also like...