A Decade in the Shadow of Error 37

What was going on ten years ago?  I mean, I guess you’ll get a full run down in a couple of days with my inevitable May in Review post, but work with me here for a bit.  But today we have a special anniversary to talk about.

Back in May 2012 people were trying to play the newly launched Diablo III and complaining about the dreaded error 37 that plagued the early days of the game.

Oh, I remember that

That was just the first of many issues Diablo III faced.  For example, there was error 75.

Once we could all log the game wasn’t bad, but there were the problems the itemization and the auction house, both the in game money version and the RMT version.

Wyatt “don’t you guys have phones” Cheng, the principle game designer on the Diablo team, gets irked if you suggest that the itemization was designed to force players to use the auction house (I’m too lazy to find his rant from a few months ago on Twitter), but it sure seemed like the simplest explanation.  If you take that out of the equation, then the team just messed up on itemization horribly because at-level drops were badly under powered for the content and the only way around it was to got to the auction house.

Still, even with that, it wasn’t a bad game.  The most controversial post I wrote in 2012 was probably the one where I said there wasn’t much of a gap between it and Torchlight II, which raised the hackles of a few Torchlight supporters.  A post with 38 comments is what passes for controversy around here.

That was, in part, because there was some rivalry between who would carry inherit the mantle of successor from Diablo II, the official next in the series, Diablo III, or something in the same spirit from a few of the same people who made Diablo II, which was the Torchlight story.

And then there was the dark horse, Path of Exile, the late entry in the race.

In the end, none of them really captured all of Diablo II.

Diablo III got story, Torchlight II got mods, and Path of Exile got atmosphere, but none were really a substitute for the original.  And then Blizzard gave us Diablo II Resurrected, after which nobody was really the successor because the original was alive and well again.

Meanwhile, over the last decade Blizzard spent a lot more time with Diablo III than its predecessor.  It got the Reaper of Souls expansion, which on the PC side of the house fixed itemization and got rid of the auction houses, both gold and RMT based.  That was a HUGE improvement for the game.  Then they did seasons and updates and a mini-expansion.

They did a lot better by it than they did Diablo II… at least until Diablo II Resurrected.

I even named Diablo III my ARPG of the decade, based primarily on play time.  I found it more engaging and playable than either of it rivals… and the Diablo II revival didn’t arrive until last year.

Now we’re about due for another Diablo title.  It took almost a dozen years to go from Diablo II to Diablo III, and we look to be about on the same time track as we wait for Diablo IV.

2 thoughts on “A Decade in the Shadow of Error 37

  1. SynCaine

    Grim Dawn for me is the ARPG I have the most time with in the last 10 years, and feel it captured what I remember of D2 best. PoE was good, Torchlight I could never get into, and D3 never grabbed me enough to actually go beyond the demo.

    Liked by 2 people

  2. Wilhelm Arcturus Post author

    @SynCaine – Grim Dawn is a title I really haven’t been able to play enough. When I bought it our group was doing something else, so I played a few hours and it seemed pretty good. But when I went back to try it again a while back it ended up being one of the titles that would not run on the 34″ monitor.

    Liked by 1 person

Voice your opinion... but be nice about it...

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s