Battle.net
We are currently have many problems with the Public Games feature of Beta. We will be disabling this feature in a coming Beta patch.
It looks like public games are so horribly broken that Blizzard has to completely disable it so people don't bother using it right now. For such a major element to fail so badly, this isn't going to help any release dates.
Battle.net
We are currently have many problems with the Public Games feature of Beta. We will be disabling this feature in a coming Beta patch.
It looks like public games are so horribly broken that Blizzard has to completely disable it so people don't bother using it right now. For such a major element to fail so badly, this isn't going to help any release dates.
Man, Blizzard's grammar is once again awful. Who is this from?
This is the one thing I am praying for them not to screw up. Server/client stability is the most important thing for me if they're not even going to allow offline play.
Yes, we all know it's a beta. But Blizzard is known for having very stable and bugless betas, and when Diablo is the first to break that mold it obviously will get people really worried about it.
Man, Blizzard's grammar is once again awful. Who is this from?
It's from Vasadan. Maybe he was going to write "We currently have many problems" but instead opted for the gerund approach "We are currently having many problems", because the beta is ongoing.
This thread is going to end badly because people are only going to read the OP's bad judgment on the situation and then not read any of the other posts...
Blizzard is known to have bugless betas ?? Wtf are you talking about. Anyway stop flipping shit people, there is a reason it's in beta stage.
I beg your pardon good sir, but i'll flip whatever i want! / (╯°□°)╯︵ ┻━┻
My opinion on the OP: The sky isn't falling, this is what betas are for. Dont think the world is ending because a bug was found in the beta. That's what beta's for... to find bugs and fix them.
Blizzard is known to have bugless betas ?? Wtf are you talking about.
I phrased that badly. Allow me to explain.
I played Starcraft 2 and not once did we have dozens of threads created with people saying they couldn't even start a game or create a profile. The bugs we had were purely regarding unit behaviour, specific driver versions, not major feature failure.
I'll give an example.
Most of this (http://us.battle.net/d3/en/forum/topic/3123365428) is perfectly fine and ok for a beta.
This (http://us.battle.net/d3/en/forum/topic/3123246440) is not (81 replies on a single issue, 2 pages with hundreds of people having the same problems), in my humble opinion. Specially when all that happened was a small simple patch focused only on bug fixing instead of major revamping of anything.
What worries me also is they supposedly internally beta tested a lot of this, and there's still a LOT of bugs (take into account that's just 2 days of F&F beta testing) on 1/3 of the first Act.
Can you really trust their internal beta testers to find what they should in the 90% of the game that's not going to be beta tested in mass? Can we expect a "clean" game at release?
Let's just think about it for a second, instead of instantly shutting it down with something as simple as "it's beta, deal with it". The OP has a legitimate concern, and I share part of it.
I agree, it seems that there's a lot of stuff not working that should have been caught. Some of these bugs are pretty obvious, or seem like they should have been.
Hopefully any bugs in the rest of the game will be patched rapidly.
Zero... what does haven 81 replies have to do with anything? if you read about the 1008 beta..its solved it was due to people be re-locked out of the beta... aka it was not a problem at all with the game.
Replies/lots of people haven issues means nothing. Its all about what the issue itself is.
Internal testers have access to the full game for beta testing, we do not, therefore we will get bugs they do not.
Do you really believe that?
While I can't be 100% sure, I'm under the impression that we're not getting bugs on Act 1 because the client doesn't have the whole Act 5 in its folder. I'd assume, if bug finding is one of their objectives in the beta, that they wouldn't give us a "purposely" broken client.
In house testing of all acts is going on...But its amazing how quick people are to flip out over an issue with games, this was the point of the beta. They said they didn't need the game tested, they had enough in house to do that. But they needed the systems and severs tested.
Zero... what does haven 81 replies have to do with anything?
Well, it's just the sheer amount of people having issues that scares me. It wasn't an issue with the game itself, but it was an issue with the battle.net server, was it not?
I guess I just put Blizzard on a pedestal after playing the Starcraft 2 beta and thinking "man, this is (bug-wise) 100 times better than most games out there" - Yes, I'm looking at you Dawn of War II!! And seeing D3 off to what feels like a bad start to me scares the shit out of me.
Zero... what does haven 81 replies have to do with anything?
Well, it's just the sheer amount of people having issues that scares me. It wasn't an issue with the game itself, but it was an issue with the battle.net server, was it not?
I guess I just put Blizzard on a pedestal after playing the Starcraft 2 beta and thinking "man, this is (bug-wise) 100 times better than most games out there" - Yes, I'm looking at you Dawn of War II!! And seeing D3 off to what feels like a bad start to me scares the shit out of me.
Yeah dont be scared by the number of people that have an issue... its what the issue is... If they messed up (obvioulsy exaggerating here as this wouldnt make it to a build) a var for the login. Thus 1,000 people couldnt login... its not a big bug...as its a simple var that needs fixing... Like Is said obviously something that small wouldnt happen, but thats the idea.. wait to see what the issue really is before we get scared.
And from what I understand, it wasnt the server, more of the database... seems they just locked their betas... it must have happend when they reset all the accounts.
So far, not a single "big" bug other than one seems to be an issue.. and even that may end up being small as soon as they find what the issue is.
Zero... what does haven 81 replies have to do with anything?
Well, it's just the sheer amount of people having issues that scares me. It wasn't an issue with the game itself, but it was an issue with the battle.net server, was it not?
I guess I just put Blizzard on a pedestal after playing the Starcraft 2 beta and thinking "man, this is (bug-wise) 100 times better than most games out there" - Yes, I'm looking at you Dawn of War II!! And seeing D3 off to what feels like a bad start to me scares the shit out of me.
The way D3 servers work, are a lot more diffrent than the way SC2 match making and public games work though.
Rollback Post to RevisionRollBack
Hardcore is the only way to play
To post a comment, please login or register a new account.
Official Blizzard Quote:
Battle.net
We are currently have many problems with the Public Games feature of Beta. We will be disabling this feature in a coming Beta patch.
It looks like public games are so horribly broken that Blizzard has to completely disable it so people don't bother using it right now. For such a major element to fail so badly, this isn't going to help any release dates.
Plus I dont see that in the blue tracker...
edit: http://us.battle.net/d3/en/forum/topic/3123365428
yeah not a big deal at all.
Man, Blizzard's grammar is once again awful. Who is this from?
Yes, we all know it's a beta. But Blizzard is known for having very stable and bugless betas, and when Diablo is the first to break that mold it obviously will get people really worried about it.
It's from Vasadan. Maybe he was going to write "We currently have many problems" but instead opted for the gerund approach "We are currently having many problems", because the beta is ongoing.
Trying to correct himself broke his sentence =]
Exactly, the purpose of the beta was to test these types of things, I believe.
Server stability, online features. bnet 2.0, ect...
My opinion on the OP: The sky isn't falling, this is what betas are for. Dont think the world is ending because a bug was found in the beta. That's what beta's for... to find bugs and fix them.
Lol ..I love ppl like you..always brighten my day.
BUT seriously this isn't a big deal, easy fix
I played Starcraft 2 and not once did we have dozens of threads created with people saying they couldn't even start a game or create a profile. The bugs we had were purely regarding unit behaviour, specific driver versions, not major feature failure.
I'll give an example.
Most of this (http://us.battle.net/d3/en/forum/topic/3123365428) is perfectly fine and ok for a beta.
This (http://us.battle.net/d3/en/forum/topic/3123246440) is not (81 replies on a single issue, 2 pages with hundreds of people having the same problems), in my humble opinion. Specially when all that happened was a small simple patch focused only on bug fixing instead of major revamping of anything.
What worries me also is they supposedly internally beta tested a lot of this, and there's still a LOT of bugs (take into account that's just 2 days of F&F beta testing) on 1/3 of the first Act.
Can you really trust their internal beta testers to find what they should in the 90% of the game that's not going to be beta tested in mass? Can we expect a "clean" game at release?
Let's just think about it for a second, instead of instantly shutting it down with something as simple as "it's beta, deal with it". The OP has a legitimate concern, and I share part of it.
Hopefully any bugs in the rest of the game will be patched rapidly.
Replies/lots of people haven issues means nothing. Its all about what the issue itself is.
While I can't be 100% sure, I'm under the impression that we're not getting bugs on Act 1 because the client doesn't have the whole Act 5 in its folder. I'd assume, if bug finding is one of their objectives in the beta, that they wouldn't give us a "purposely" broken client.
I guess I just put Blizzard on a pedestal after playing the Starcraft 2 beta and thinking "man, this is (bug-wise) 100 times better than most games out there" - Yes, I'm looking at you Dawn of War II!! And seeing D3 off to what feels like a bad start to me scares the shit out of me.
Yeah dont be scared by the number of people that have an issue... its what the issue is... If they messed up (obvioulsy exaggerating here as this wouldnt make it to a build) a var for the login. Thus 1,000 people couldnt login... its not a big bug...as its a simple var that needs fixing... Like Is said obviously something that small wouldnt happen, but thats the idea.. wait to see what the issue really is before we get scared.
And from what I understand, it wasnt the server, more of the database... seems they just locked their betas... it must have happend when they reset all the accounts.
So far, not a single "big" bug other than one seems to be an issue.. and even that may end up being small as soon as they find what the issue is.
The way D3 servers work, are a lot more diffrent than the way SC2 match making and public games work though.