When It Comes To Diablo III, Error 3003 Is The New Error 37


Oh aren’t you cute, over there making fun of Diablo III‘s Error 37. So old-fashioned! Haven’t you been following the latest trends? Everyone knows that Error 37 is yesterday’s news. Today, the hot new error is Error 3003!

Oooh, just look at it there, strutting onto your computer screen. So fierce, so present.

I bet you thought you’d be able to play your game today! I bet you thought that stupid, constant Error 37 you got yesterday had been resolved, and that maybe the idea of an always-on internet requirement for a single-player game wasn’t acutally flawed in a fundamental way.

Shows what you know! Time to get with the hippest fashions, my friend. Go ahead. Boot up Diablo III and try to log in. You’ll get an up-close look at our fashionable new friend Error 3003 posthaste.

If you’re lucky, you may even see his cousin, Little Miss Error 75. She’s shy, but mark my words: She may just be the Next Big Thing.


The Cheapest NBN 1000 Plans

Looking to bump up your internet connection and save a few bucks? Here are the cheapest plans available.

At Kotaku, we independently select and write about stuff we love and think you'll like too. We have affiliate and advertising partnerships, which means we may collect a share of sales or other compensation from the links on this page. BTW – prices are accurate and items in stock at the time of posting.

Comments


109 responses to “When It Comes To Diablo III, Error 3003 Is The New Error 37”

Leave a Reply

Your email address will not be published. Required fields are marked *