|
We have a repair utility in testing internally right now and we're also going to shut the beta down for a few days. With luck, it'll be in the next time the Beta is brought up. 6. Re: Patch issue 05/23/2010 01:45:10 PM PD Source: http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=1#6
Currently it's planned to be ended on June 1 to give people time to play during Memorial Day. It may change if we have to take the servers down earlier but if things stay up, that chance is there.
Source: http://forums.battle.net/thread.html?topicId=25026324408&sid=5000&pageNo=1
at least the repair will get done? no word if on if they are extending phase one. Edit: added another quote on a separate thread. Edit2: seems as though blizzard was trolling us..
...Kinda makes this thread useless.. Wow, what a quality post. hint, hint? lol
|
|
|
i wonder if that will postpone the end of the beta pahse one as well or if they just keep it down from now on. not sure if it will be worth for them to get it up fpr only 2 or 3 days. iknow it would be for me though^^
|
For such a big announcement it sounds pretty casual.
|
Nobody is taking the beta seriously anymore
|
A few days that sounds like firing people or atleast some sort of you fucked up words to me imo.
|
On May 24 2010 08:54 semantics wrote: A few days that sounds like firing people or atleast some sort of you fucked up words to me imo.
lol pretty much, hope activision doesnt get a hold of this project, lololol
|
wait, does that mean they will take down the servers prematurely and and. NO TURNAMENTS? NOOOOOOOOOOOOOOOOOOOO xd
|
Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing.
|
.... But the Altitude TL Invitational....
|
On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing.
My best guess as to what the problem is (and your analogy is wrong for a bunch of reasons which I can't really explain because I'm not smart enough) is that they changed the protocol from TCP to UDP, which people think was a good change, but somewhere in that code they screwed something up.
|
On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing. You erased the part you wanted to change and instead of pressing the black ink on your pen you used pink, glitter ink to communicate.
|
All this downtime is totally worth it for Facebook integration!
|
On May 24 2010 08:54 Gamer0ne wrote:Nobody is taking the beta seriously anymore 
IT'S BETA!!!!! omg what is wrong with you people! seriously the replies in this thread seem like a bunch of babies crying
A) THE GAME IS NOT EVEN OUT YET B) be happy bliz let you play it in the first place C) you have not paid a dime yet for this game
so sick of people cussing Blizzard when really you should be thanking them for the opportunity to play "the next big competitive game"
User was warned for this post
|
Maybe they are going to completely get rid of bnet 2.0 and put in some chat channels and start "bnet 2.0" from scratch as a good online service?
One can hope.
|
On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing.
It happens a lot in programming. Your analogy isn't too bad, but a more accurate analogy would be taking a paper and modifying it. By modifying paragraph 8, it changes several of the words in paragraph 2, and the changes in paragraph 2 caused several words to become misspelled in paragraph 1. Then you try to fix the changes in paragraph 1 and 2, but those caused paragraph 5 and 9 to start messing up as well.
99% of bugs in code are caused that way. You change one thing which usually ends up breaking something else. Patch 13 was intended to make the game performance better, but it's obvious that whatever improvements they made caused problems in some of the older code, which is why Bnet is having so much trouble.
|
I guess their UDP code was tested internally (obviously) and it worked. However, in the real world scenario on live servers it became apparent there is some rare (I think it is rare in a global scale) bug that causes the freezes/disconnects. There can be multitude of reasons for that and it's not easy to debug if I may speak from my experience.
|
Can't they just like.. completely go back to Patch 10, before the roach nerf, the start of all these major fuckups??
And then hire some fucking COMPETENT balance designers?? for fuck sakes, the game was going fine until the roach nerf, every patch since then has been significantly worse, and patch 13 just shit the bed so bad now the bnet servers dont even work.
|
On May 24 2010 09:03 johnlee wrote: .... But the Altitude TL Invitational....
Word. Ima be a sad panda if Blizzard fucks over another Tournamnet ):
|
On May 24 2010 09:03 Sc1pio wrote:Show nested quote +On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing. My best guess as to what the problem is (and your analogy is wrong for a bunch of reasons which I can't really explain because I'm not smart enough) is that they changed the protocol from TCP to UDP, which people think was a good change, but somewhere in that code they screwed something up.
So I'm an ECE student that's going to focus on networking/security. But I'm still a student, so what would I know. Here's my guess:
Essentially, they tried to implement UDP. Probably involved a small amount of code. Shouldn't really mess things up that badly.
For those that don't know, UDP is actually pretty good for games. TCP: reliable internet connection. If I send the integers 1, 2, 3, 4 over the internet to you, you WILL receive them in the exact same order.
UDP: an unreliable connection. Packets can be lost, or sent out of order. Imagine if you were running a clock on a server. I wouldn't care about a packet that got lost 5 seconds ago because that's not the current time anymore.
So for something like Starcraft 2, obviously TCP is nice, so that there's less syncing between clients. The problem is that this contributes lag to the game (Think SC:BW with setting to extra high latency, etc,)
From a programming perspective, implementing UDP must be simple, right?
Not really. I assume they're writing everything with multi-threading. Networking with multi-threading is a nightmare. I only have a bit of experience (I did a multi-threaded web proxy with a cache in C. This is nowhere near SC2's complexity, and it had tons of bugs). Factor that in with trying to sync both clients, and syncing the TCP/UDP among multiple threads, and you have a nightmare that has tons of hidden bugs.
As to why their server has been crashing like mad, well it's Blizzard.
my 2 cents.
|
|
|
|
|
|