Lol - i was playing Russian roulette, because there was only a 1 in 6 chanche i would get shot. But I got shot first time.
So now im gonna sue the event co-ordinator.
That makes more sense than the opening to this thread.
I also took time off work, and i knew it would be a 50/50 that there would be bugs.
Not blizzards fault, yours for expecting too much. and dont go on about " it should have worked day 1 blah blah" even if it is true - YOU are responsible for your action, not blizzard. They didnt ruin your day, you did.
i was peeved as well, but damn, i took it as things that happen launch day, in fact there is a hilarious chain email at work that I am going to have to reply to when i get the courage, detailing the fail of me taking a day off on Diablo 3 opening week. It is quite humerous.
If a man is offered a sandwich, and when he reaches out for it, the sandwich is taken away, whose fault is it that he doesn't have the sandwich, his for reaching for it, or the people who pulled the sandwich away by taking down the sandwich servers for emergency sandwich maintenance?
see what i did there?
Yes I do, you made a strawman argument.
I won't deny that cuz obviously its true, i was just messin around (hence sandwiches) but you can't honestly believe that none of the fault for today lies with blizzard... I expected them to do what they said they would do. is that expecting too much?
Lol - i was playing Russian roulette, because there was only a 1 in 6 chanche i would get shot. But I got shot first time.
So now im gonna sue the event co-ordinator.
That makes more sense than the opening to this thread.
I also took time off work, and i knew it would be a 50/50 that there would be bugs.
Not blizzards fault, yours for expecting too much. and dont go on about " it should have worked day 1 blah blah" even if it is true - YOU are responsible for your action, not blizzard. They didnt ruin your day, you did.
i was peeved as well, but damn, i took it as things that happen launch day, in fact there is a hilarious chain email at work that I am going to have to reply to when i get the courage, detailing the fail of me taking a day off on Diablo 3 opening week. It is quite humerous.
If a man is offered a sandwich, and when he reaches out for it, the sandwich is taken away, whose fault is it that he doesn't have the sandwich, his for reaching for it, or the people who pulled the sandwich away by taking down the sandwich servers for emergency sandwich maintenance?
Same story all the time. People shove all the responsibility over to someone else and then start whining. Instead you should have been smart and you could have known shit would hit the fan. Try another afternoon off, next week. Things will have settled down.
Blizzard has been advertising for WEEKS "Play at 12:01am on May 15!"
not "play an afternoon in june like the troll says"
by choosing to make the game exclusively online, and require players to play via their servers and not their own computers, Blizzard is committing to providing us with reliable service. And that service was scheduled to start at 12:01, a point that blizzard publicized greatly. They were very proud of the whole "you'll be able to play the second servers go live" thing.
anyone with an ounce of sense knew there would be problems in the first couple of days.
Those issues should have been dealt with (and blizzard said they dealt with them) during the open beta weekend. The only purpose for that weekend was to stress test the system, so at launch THERE WOULDNT BE ANY F**KIN PROBLEMS
Blizzard had (apparently) taken all the necessary steps to prevent these problems. God only knows how much time they've had to prepare for this launch... AND experience in MMO launches are NOT unfamiliar to Blizzard... their success has been largely due to the MMO market, and they are experts at what they do. Nobody is denying that. But after a 9 month (ish, im estimating) closed beta, a hugely successful open beta stress test weekend, it's really disappointing that today has been over half downtime.
Blizzard wants players to be able to fight each other, but they DON'T want there to be repercussions for losing. As they've said, d3 is first and foremost a cooperative game, and they want the focus on killing monsters with your friends, not beating other people.
but they're adding pvp because people like fighting each other. They dont want the focus of gamers to be "step 1, beat the game, step 2, gear up for arena." They want it to remain "step 1, beat normal with friends. step 2, beat nightmare with friends. step 3, beat hell with friends. step 4, spend eternity trying to clear inferno. and if you get bored, step 5, mess around in a free-play (or team play), gurubashi-arena style pvp"
1
I won't deny that cuz obviously its true, i was just messin around (hence sandwiches) but you can't honestly believe that none of the fault for today lies with blizzard... I expected them to do what they said they would do. is that expecting too much?
1
If a man is offered a sandwich, and when he reaches out for it, the sandwich is taken away, whose fault is it that he doesn't have the sandwich, his for reaching for it, or the people who pulled the sandwich away by taking down the sandwich servers for emergency sandwich maintenance?
see what i did there?
2
Blizzard has been advertising for WEEKS "Play at 12:01am on May 15!"
not "play an afternoon in june like the troll says"
by choosing to make the game exclusively online, and require players to play via their servers and not their own computers, Blizzard is committing to providing us with reliable service. And that service was scheduled to start at 12:01, a point that blizzard publicized greatly. They were very proud of the whole "you'll be able to play the second servers go live" thing.
Those issues should have been dealt with (and blizzard said they dealt with them) during the open beta weekend. The only purpose for that weekend was to stress test the system, so at launch THERE WOULDNT BE ANY F**KIN PROBLEMS
Blizzard had (apparently) taken all the necessary steps to prevent these problems. God only knows how much time they've had to prepare for this launch... AND experience in MMO launches are NOT unfamiliar to Blizzard... their success has been largely due to the MMO market, and they are experts at what they do. Nobody is denying that. But after a 9 month (ish, im estimating) closed beta, a hugely successful open beta stress test weekend, it's really disappointing that today has been over half downtime.
1
Blizzard wants players to be able to fight each other, but they DON'T want there to be repercussions for losing. As they've said, d3 is first and foremost a cooperative game, and they want the focus on killing monsters with your friends, not beating other people.
but they're adding pvp because people like fighting each other. They dont want the focus of gamers to be "step 1, beat the game, step 2, gear up for arena." They want it to remain "step 1, beat normal with friends. step 2, beat nightmare with friends. step 3, beat hell with friends. step 4, spend eternity trying to clear inferno. and if you get bored, step 5, mess around in a free-play (or team play), gurubashi-arena style pvp"
if you disagree, feel free to say why
1