This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.5
PTR
10.2.6
Petition anyone?
Post Reply
Return to board index
Post by
631580
This post was from a user who has deleted their account.
Post by
DraconisAerius
Where I have to say I agree with you all about Blizzard and extended maintenance there is something you may not know. We all agree to the terms that Blizzard has when we "Accept" to play, in the fine print of what we "Accept" scheduled maintenance is in the agreement. Unfortunately we all have to "Accept" to be able to play, so Blizzard gives us no choice unless we choose not to play. I don't think there is anyway to get around this. We all just have to accept the conditions and terms that Blizzard has, we may not like it, but thats the way it is.
Yes... sheduled maintenance is in it. unshedulded extensions are not.
Post by
Pwntiff
Yes... sheduled maintenance is in it. unshedulded extensions are not.
Yes, they are.
THE GAME AND THE SERVICE ARE PROVIDED "AS IS" AND BLIZZARD DOES NOT WARRANT THAT THE GAME OR THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE
Post by
Kelborn
Ok I'm just going to point out that these servers probably have a million or more of lines of code. Going though code is like trying to read the entire Encyclopedia Britannica in 8 hours. Granted that they have multiple people on each server, but it's still a lot of stuff to go through. Not to mention that
fixing
code is just as hard as writing it in the first place.
I would really love to see all the people complaining about the maintenance create, run, and maintain their own game servers. I'd give it about two hours before you all say it's too hard and start QQing again like spoiled the spoiled children you are.
So you can't play WoW for one day of the week.... holy crap the world is ending. It's not like there's
anything
to do outside, or heaven forbid other games to play.
Post by
177096
This post was from a user who has deleted their account.
Post by
118081
This post was from a user who has deleted their account.
Post by
118081
This post was from a user who has deleted their account.
Post by
631580
This post was from a user who has deleted their account.
Post by
558249
This post was from a user who has deleted their account.
Post by
631580
This post was from a user who has deleted their account.
Post by
581897
This post was from a user who has deleted their account.
Post by
kasuturo
Get 50k pages on this thread and your argument is valid.
Post by
631580
This post was from a user who has deleted their account.
Post by
631514
This post was from a user who has deleted their account.
Post by
631580
This post was from a user who has deleted their account.
Post by
334295
This post was from a user who has deleted their account.
Post by
631514
This post was from a user who has deleted their account.
Post by
631580
This post was from a user who has deleted their account.
Post by
dimichan
*applauds*
I loved reading this thread. Can I vote it ++ for posterity's sake?
Obviously some of you have *never* worked in anything service or IT related. It shows.
I have taken a computer from a pile of parts on a table, assembled it, and had it running UT in less than 10 minutes. (Really, it was timed. It was a stupid challenge at a LAN party. I'm a nerd, ok? But so are you since you're reading this.)
I've also had days where I spent 4, 8 or even longer hours trying to figure out why I couldn't get the computer to run right after putting things together. Everything was right, but nothing worked correctly.
^&*! happens. Get a shovel.
SO much this.
Not to mention, you can run something on a test server and it performs flawlessly.
Put the same code into the real world with the real stressers, not the sim'd ones - and it fails horribly at times.
There's only so much you can do to test coding before making it :"live" before it becomes more intensive to run exhaustive tests than just to test, fix any obvious problems, retest, performs as expected, and toss it out. Most test servers just can't perfectly replicate real environments - and sometimes, as the poster above mentions, what SHOULD work beautifully fails.
I'm sure, as frustrated as we are, the people who built said code and tested it, had it work, and watched it crash down are beating their heads against the wall while they track through everything to pinpoint the issue - while their supervisors are breathing down their necks saying "I thought you tested this?"
Post by
631514
This post was from a user who has deleted their account.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.