Servers go down on the first day of Blizzard games, it has been that way for several years, get over it, if you didn't expect it with Diablo III you are clearly blind.
Maybe we thought by now Blizzard figured out how many people play at launch, etc, and actually planned ahead this time. I mean, I'm not surprised AT ALL that they didn't and this is happening, and mostly I am laughing at THEM for how epic a disaster this was so far... but I can't blame people who are mad. This *shouldn't* happen.
The people that have critiques and complaints make threads about it.
And as sure is the sky is blue, someone HAS to make a "quit crying" thread.
I am amused.
Rollback Post to RevisionRollBack
"I want to say something but I'll keep it to myself I guess and leave this useless post behind to make you aware that there WAS something... "
-Equinox
"We're like the downtown of the Diablo related internet lol"
-Winged
The people that have critiques and complaints make threads about it.
And as sure is the sky is blue, someone HAS to make a "quit crying" thread.
This.
I am amused.
But less so, this.
@OP: People, imho, have a right to expect the game they purchased to function, even if not perfectly. Sure, they shouldn't be surprised that Blizzard, like pretty much every other company with major launches, fails to meet this standard, and yes, there are technical reasons why it's very difficult to weed these sorts of bugs out before a game launches. However, if everyone just blindly accepts the status quo, what incentive do companies have to try to do better next time? While it's fair to say that people shouldn't be surprised and that avoiding downtime during launches is a difficult technical challenge, I don't think it's fair or constructive to say that customers should just "get over it" and "quit crying."
Rollback Post to RevisionRollBack
...and if you disagree with me, you're probably <insert random ad hominem attack here>.
Servers go down on the first day of Blizzard games, it has been that way for several years, get over it, if you didn't expect it with Diablo III you are clearly blind.
Serveral years? My friend, this has been happening since Diablo II launched. The only blizzard launches that have not had massive server issues were Warcraft II battle.net edition, StarCraft II. Cant remmeber starcraft I or Diablo I. But I remember having MASSIVE login, server problems with Diablo II for the first two weeks.
Easy solution: Implement a stand alone single player campaign and let players store their character data on their own hard drive. Don't allow users to have ANY multiplayer data on their hard drives.
Easy solution: Implement a stand alone single player campaign and let players store their character data on their own hard drive. Don't allow users to have ANY multiplayer data on their hard drives.
This has been debated to death, but here are the key points of why this didn't happen:
1. Hacks, dupes and bots are much easier to create when you have access to the code which generates items, random maps, etc.
2. In D2, a ridiculous number of people (myself included), started out in single-player and had to start over in order to play with friends online. Now, the only problem you have is if your friends are on one of the other two regional servers.
3. Blizzard is in business to make money and piracy takes a good chunk away from that in the PC market, so they're financially incentivized to make online-only games.
Those are the big three, but there are others as well such as Blizzard's ability to use metrics in online play to see where exploits and problems lie, achievements, the ability to balance around the AH, etc.
Rollback Post to RevisionRollBack
...and if you disagree with me, you're probably <insert random ad hominem attack here>.
Servers go down on the first day of Blizzard games, it has been that way for several years, get over it, if you didn't expect it with Diablo III you are clearly blind.
In response to "Quit crying" all I can think of to say is, "Your momma".
while i was disappointed not being able to play as soon as servers launched, not crying about it. however i do feel like blizz should have had a contingency plan in effort for this issue which has as stated happened over and over again
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
http://i.imgur.com/O7Oeo.png
I received TWO beta keys. Eat it and like it.
You REALLY think a company their size with SO much to lose didn't "figure out" how many people play...REALLY??!!?!
Of COURSE they know how many people play. They have statistics up the yazoo.
You all severely underestimate what so many people logging in to the same place can do. There is not much you can do to "be ready" for it.
The people that have critiques and complaints make threads about it.
And as sure is the sky is blue, someone HAS to make a "quit crying" thread.
I am amused.
-Equinox
"We're like the downtown of the Diablo related internet lol"
-Winged
This.
But less so, this.
@OP: People, imho, have a right to expect the game they purchased to function, even if not perfectly. Sure, they shouldn't be surprised that Blizzard, like pretty much every other company with major launches, fails to meet this standard, and yes, there are technical reasons why it's very difficult to weed these sorts of bugs out before a game launches. However, if everyone just blindly accepts the status quo, what incentive do companies have to try to do better next time? While it's fair to say that people shouldn't be surprised and that avoiding downtime during launches is a difficult technical challenge, I don't think it's fair or constructive to say that customers should just "get over it" and "quit crying."
Serveral years? My friend, this has been happening since Diablo II launched. The only blizzard launches that have not had massive server issues were Warcraft II battle.net edition, StarCraft II. Cant remmeber starcraft I or Diablo I. But I remember having MASSIVE login, server problems with Diablo II for the first two weeks.
If someone does a mistake like that over here, heads will roll.
And we are not talking about a multi billionary company.
This has been debated to death, but here are the key points of why this didn't happen:
1. Hacks, dupes and bots are much easier to create when you have access to the code which generates items, random maps, etc.
2. In D2, a ridiculous number of people (myself included), started out in single-player and had to start over in order to play with friends online. Now, the only problem you have is if your friends are on one of the other two regional servers.
3. Blizzard is in business to make money and piracy takes a good chunk away from that in the PC market, so they're financially incentivized to make online-only games.
Those are the big three, but there are others as well such as Blizzard's ability to use metrics in online play to see where exploits and problems lie, achievements, the ability to balance around the AH, etc.
In response to "Quit crying" all I can think of to say is, "Your momma".