As many have pointed out, this isnt really a big deal Software bugs normally don't take long to iron out, even if they look quite severe at first glance.
The things that do take a long time is balancing things out like they had to do with starcraft 2 and other competitive Player vs Player games, but afaik thats not a priority with d3 and therefore shouldnt be a concern when it comes to finalizing the game and getting it out on the market.
As many have pointed out, this isnt really a big deal Software bugs normally don't take long to iron out, even if they look quite severe at first glance.
The things that do take a long time is balancing things out like they had to do with starcraft 2 and other competitive Player vs Player games, but afaik thats not a priority with d3 and therefore shouldnt be a concern when it comes to finalizing the game and getting it out on the market.
IMO, if anything is to delay the release of the game, it will be the RMAH.
I have a couple of thoughts that I don't see posted here (or at least they were not clear to me)
1 I believe they said that D3 was going to have a rough beta compared to their other games. I don't recall what reason was given if any but it might be related to any of the following...
2 They have a bunch of in house testers, true, but If I were in their situation and new that the public was going to get their hands on everything up to the skele king I would rush past that and focus on the rest of the game.
3 How close to the most recent iteration is the beta? For all we know the beta is something they built before they got to the current build which has some sweeping changes that someone forgot had an effect on the early game (This idea comes from the hydra of Arcane-affixed monsters bug) they may have already submitted the game to production so that they have discs and boxes for release. Not likely but something to consider
4 The most common problems I have seen were related to permissions, hardware and drivers or small foul-ups (leather caps and Witchdoctors etc). Exactly the kinds of thing that they wanted to be debugging for, and therefor nothing to get anxious about.
Anyway I could be completely wrong these were just some things that popped into my head while contemplating this topic
Rollback Post to RevisionRollBack
If that made sense to you, Bravo! I think I even confused myself...
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.
lmfao awesome. I am sorry sir, I was unaware you were the exemption to shit flinging. my apologies =D
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.
Guess what the beta is for?
Do you think it will take them over 3 months to fix this issue?
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.
Diablo is a brand new game from the ground up, nothing ported from D2 besides the lore. BRAND NEW servers, BRAND NEW hardware. They have nothing to build on like SC2, this shit is brand spankin your moms ass new.
Also, um hi, yea if there is an issue, I fully expect more than 1 person to notice and post, and having a lot of people post about it is common, because well, the issue is happening to them. Also, all these issues are systems and hardware related, therefore that 90% of the game you are talking about, we ARE testing as beta testers. In the game, 90% is systems and hardware, 10% is different locations. its not like acts 2-4 have completely different systems, it's all the same, just different textures and mobs. So yes I do fully trust their internal alpha that's been going on for over a year. If you notice, a lot of the problems are stemming from having a ton of people on the servers, which is what they are testing for.
In conclusion, I AM shutting down and saying that this is what happens in betas that don't have architecture to be built upon and are brand new games.
I think I wrote this somewhere already, but I write it again. IMO since this is a beta build with beta client, there may be bugs internal test builds dont have, because stuff needed to be taken out, and that can cause unexpected shit. And as long as the main problems are with the server stability, Bnet, etc.. then we dont have to freak out.
Trust me I am a games programming student and bugs are very common. At first they may seem like they're really bad, but may only be slight errors in the code and can be easily fixed, I wouldn't think that there would be any major bugs that delay a release. The whole point of this Beta is to test and find these bugs so they can be ironed out. It shouldn't take 4 months to fix all the bugs that are spotted within 1/3 of Act 1.
As they said the major thing they want to test is the Client/Server side of things, so no need to panic.
The things that do take a long time is balancing things out like they had to do with starcraft 2 and other competitive Player vs Player games, but afaik thats not a priority with d3 and therefore shouldnt be a concern when it comes to finalizing the game and getting it out on the market.
IMO, if anything is to delay the release of the game, it will be the RMAH.
1 I believe they said that D3 was going to have a rough beta compared to their other games. I don't recall what reason was given if any but it might be related to any of the following...
2 They have a bunch of in house testers, true, but If I were in their situation and new that the public was going to get their hands on everything up to the skele king I would rush past that and focus on the rest of the game.
3 How close to the most recent iteration is the beta? For all we know the beta is something they built before they got to the current build which has some sweeping changes that someone forgot had an effect on the early game (This idea comes from the hydra of Arcane-affixed monsters bug) they may have already submitted the game to production so that they have discs and boxes for release. Not likely but something to consider
4 The most common problems I have seen were related to permissions, hardware and drivers or small foul-ups (leather caps and Witchdoctors etc). Exactly the kinds of thing that they wanted to be debugging for, and therefor nothing to get anxious about.
Anyway I could be completely wrong these were just some things that popped into my head while contemplating this topic
lmfao awesome. I am sorry sir, I was unaware you were the exemption to shit flinging. my apologies =D
Thanks for the update cpt. obvious.
Do you think it will take them over 3 months to fix this issue?
Diablo is a brand new game from the ground up, nothing ported from D2 besides the lore. BRAND NEW servers, BRAND NEW hardware. They have nothing to build on like SC2, this shit is brand spankin your moms ass new.
Also, um hi, yea if there is an issue, I fully expect more than 1 person to notice and post, and having a lot of people post about it is common, because well, the issue is happening to them. Also, all these issues are systems and hardware related, therefore that 90% of the game you are talking about, we ARE testing as beta testers. In the game, 90% is systems and hardware, 10% is different locations. its not like acts 2-4 have completely different systems, it's all the same, just different textures and mobs. So yes I do fully trust their internal alpha that's been going on for over a year. If you notice, a lot of the problems are stemming from having a ton of people on the servers, which is what they are testing for.
In conclusion, I AM shutting down and saying that this is what happens in betas that don't have architecture to be built upon and are brand new games.
Is that the same issue, though?
As they said the major thing they want to test is the Client/Server side of things, so no need to panic.
I imagine when closed beta starts then they'll switch over.
Proof?
They even call it Public Games feature, instead of battle.net.
If it was battle.net they'd have said battle.net features in the beta. Or if it was some permanent thing they wouldn't have said "of Beta".