The launch of Diablo 3 was about to happen, but then something strange happened, instead. Turns out, even us lucky few would eventually find that it was only a matter of time before the ERROR?monster conquered us, too.
So the long awaited moment arrived –– we chosen few who have been anticipating this moment were glued to our chairs with heightened caffeine levels coursing through our veins.
This May 15th was going to be awesome, a proverbial early Christmas for Geeks from the folks at Blizzard Entertainment.
After over 12 years of waiting and hoping, the moment had finally arrived: The launch of Diablo 3 was about to happen, but then something strange happened, instead –– No one could log in, at least no one I?knew of.
Well, we all know what happened, at least us that cared. The servers that Blizzard had delegated for the launch couldn’t keep up with the amount of traffic that bombarded it.
I guess they weren’t ready after all. But, to be honest, could anyone have been ready for that amount of traffic all at one time??
Luckily, for me, I had decided to forgo the “staying up until 12:01 am PDT”?(that is 2:01 a.m. for us in the Midwest) part of the launch and decided that sleep was more important than being one of the first (Americans) into the game.
I count myself blessed, for had I been up at 2 a.m. and the darn thing hadn’t worked for me, I might have thrown my keyboard through the window and screamed out into the cold, black night. Much like some of the characters in the game.
A few of my friends did, indeed, stay up late for the game. Their disappointment was evident as they expressed to me their loss of faith in the Blizzard crew.
Of course, at least they didn’t take off work to play the game, right? For those who did, they were in for an even more frustrating day as Blizzard kept shutting down the servers as more and more issues with game play came to light.
I was one of the few lucky ones. Every time I logged in yesterday, which wasn’t a lot, I was greeted with many moments of game play, including some co-op play with friends.
Well, that was until last night after my wife made her way to bed, freeing me for many hours of uninterrupted game play.
Wife in bed - check!
Kids sound asleep - check!
Dog walked - check!
Comfy chair with plenty of water on hand - check!
Time to log in!
After about 15 minutes of intense game play, I?experienced the frustration of millions upon millions of hardcore gaming fans in world. My game suddenly quit on me, and I was logged off the battle.net server right in the middle of an intense battle.
Turns out, even us lucky few would eventually find that it was only a matter of time before the ERROR?monster conquered us, too.
But be patient my fellow gamers, Blizzard will get it all figured out and, in a few weeks, this will all be nothing more than a bad memory we will all find hilarious.
I?do find one fact about this whole situation a bit ironic. All you computer savvy types remember all the warnings you give your less tech savvy friends??To not buy something technology-based brand new. That there will be bugs that need to be worked out on launch, and to wait would be in their best interest.
Well that applies to Diablo 3, too.
Gary Darling is the geekiest employee at the Maryville (Mo.) Daily Forum. His online blog address is: justanewdad.blogspot.com & his email is: email@example.com. Drop him a line sometime!