Seriously. Tried doing a raid? You randomly kick people, if you choose a certain person. Try /target on a specific person, you'll get a random one.
Also, the Dark Portal event doesn't make up for this, Blizzard...
Good job.
Never mind the cap flags from 40 yards bug, or the completed quests staying in your log bug.
/rant
·Theme
- Forums
- World of Warcraft
- General Discussion
- Blizzard Should Check For Bugs Before They Release A Patch..
Blizzard Should Check For Bugs Before They Release A Patch..Follow
I have to admit, because of this bug it made raiding last night a bit harder. My quest log is completely screwed up, and a couple of my bg bars were messed as well (but those are just addons that will probably have updates). I don't understand how they couldn't test this, unless it just somehow popped up on patch day. I mean they did have this in the PTR right?
Anobix wrote:
I have to admit, because of this bug it made raiding last night a bit harder. My quest log is completely screwed up, and a couple of my bg bars were messed as well (but those are just addons that will probably have updates). I don't understand how they couldn't test this, unless it just somehow popped up on patch day. I mean they did have this in the PTR right?
They had this on the LONG, LONG beta.
Also, Alt GR doesn't work for self-casting, and it is SERIOUSLY ticking me off.
God, please help Blizzard fix this bug. Thank you.
>_<
God, please help Blizzard fix this bug. Thank you.
>_<
A lot of times in BG last night my target portraits werent showing up. But I couldn't be sure if it was one of my mods or not. I was desperately trying to get enough honor to get my mageblade last night but ended up falling a couple hundred short.
Vitos wrote:
Seriously. Tried doing a raid? You randomly kick people, if you choose a certain person. Try /target on a specific person, you'll get a random one.
Not saying you're wrong and maybe it is a patch bug... but have you tried doing the same thing with all of your mods turned off? If you're running something like CTRaid Assist then maybe that is messing up with the new patch. I know we did a raid last night and I had trouble targetting through the raid window... but I figured it was more mod related than patch related.
Multiple posts on the OBoards about this. People are experiencing the targetting bug after cleaning out the Addons, WTF, WDB, etc. folders.
I am a software implementor. Frequently when I log in, I'm dumb-struck with awe that Blizzard has managed to pull this off *at *all*. When I allow myself a chance to think about what goes into the running of this game, I'm amazed it *ever* works. My company holds its collective breath each month as we release software to about a hundred people.
First rule of software development- You touch one itty bitty thing, it will cascade into a catastrophe involving 10.
I can appreciate the annoyance at targetting bug. I myself got hollered at PLENTY in AV for "Why didn't you heal me?!"
I laugh. Say perhaps the Blizzard QA team was a hundred thousand people. There are 7.5 MILLION users. A hundred thousand people cannot encounter every possible variance. On top of that, some of us have questionable knowledge of how things work, and do dumb things (like I did) and reload all their add-ons. Then wonder why things get wonky. This isn't "Curious George uses the potty" coding people. This is a MASSIVE MULTI-player.
Second rule of software development - as soon as you create an idiot proof interface, G-d will create a bigger idiot.
Take a deep breath, unload all your add-ons and be patient. Blizzard does an incredible job, let them do it.
Edited, Jan 10th 2007 3:30pm by Manza
First rule of software development- You touch one itty bitty thing, it will cascade into a catastrophe involving 10.
I can appreciate the annoyance at targetting bug. I myself got hollered at PLENTY in AV for "Why didn't you heal me?!"
I laugh. Say perhaps the Blizzard QA team was a hundred thousand people. There are 7.5 MILLION users. A hundred thousand people cannot encounter every possible variance. On top of that, some of us have questionable knowledge of how things work, and do dumb things (like I did) and reload all their add-ons. Then wonder why things get wonky. This isn't "Curious George uses the potty" coding people. This is a MASSIVE MULTI-player.
Second rule of software development - as soon as you create an idiot proof interface, G-d will create a bigger idiot.
Take a deep breath, unload all your add-ons and be patient. Blizzard does an incredible job, let them do it.
Edited, Jan 10th 2007 3:30pm by Manza
But why are they changing things that don't need to be changed? Was the way targetting was done, or targeting frames being drawn, so broken that it needed to be fixed? My action bars were screwed up last night. I had to get a new version of the mod to fix it. Why? What changed in this patch that made warrior stance changing so fundamently different that it broke something that's worked right for over two years? Why the change at all?
Blizzard keeps making these idiotic changes to things that weren't broken, and worked perfectly since the game was released. Yet they know of glaring bugs that have been around since then, and those will never be fixed.
I don't change my tires and put on snow tires when the ones I have do the job. Why does Blizzard ***** with their game and break things that either aren't broken or don't need to be changed?
Blizzard keeps making these idiotic changes to things that weren't broken, and worked perfectly since the game was released. Yet they know of glaring bugs that have been around since then, and those will never be fixed.
I don't change my tires and put on snow tires when the ones I have do the job. Why does Blizzard ***** with their game and break things that either aren't broken or don't need to be changed?
Ringthane wrote:
I don't change my tires and put on snow tires when the ones I have do the job. Why does Blizzard ***** with their game and break things that either aren't broken or don't need to be changed?
Why learn to multiply when you can just add over and over and over and over and over and....
In persuit of optimization they changed how clicking on names aquired a target. It didn't work. It's that simple.
Out of curiousity, how much testing of the patch did YOU do?
Yes, it's a trick question. If you say no, then the simple response is why are you complaining about something you had the chance to test and notice but you didn't bother with? Of course, if you say yes, the question is, how could YOU let such a bug go unnoticed and unreported?
what you need to remember is that every bug is not necessarily created from directly focusing on that frame/article/addon. It can, as Manza said, be caused from a cascade. I work in IT, so I have a similar feeling with Mazra that we know when we roll out new patches/software to our 500 employees with 4 different models of PCs that we know that something will go wrong.
We tried ZG today, but had to give up Hakkar, cause our tanks couldn't stay online for more than 2 minuttes. There where no problems in AQ20, however
When the company I work on release an update on a software or announce that we will release an update, we will get call from customers saying are you sure this will not cause problem or do you know if this release will caused problem? I'm sitting there answering them saying how we test on our end and its working as expected, but in my mind I'm thinking "Jeez, are there actually peoples this dumb out there? If we know a software release that will cause humongous problem, why would we release them?"
An example of cascade:
In the beta a while back druids were given the ability to talk to NPCs in forms. No problem you'd think, just flip them to still being considered humanoids for that respect.
The thing is, when the game was coded it wasn't expected for this to happen, so all the druid things were tied into one variable. Suddenly all procs were counting, weapon damage was included on top of attacks, and druids could drink potions in forms as well. It was chaos.
Another example, this one not directly from the game but a hypothetical.
"Gee golly there's a lot of variables coding this. When I write this one up I hope I'm not accidentally duplicating a variable from a completely different place in the game. Then a change to one place would throw the other one out of whack. Well I looked as best I could, but in something this complex humans and computers are not infallible. I should be happy it works currently."
In the beta a while back druids were given the ability to talk to NPCs in forms. No problem you'd think, just flip them to still being considered humanoids for that respect.
The thing is, when the game was coded it wasn't expected for this to happen, so all the druid things were tied into one variable. Suddenly all procs were counting, weapon damage was included on top of attacks, and druids could drink potions in forms as well. It was chaos.
Another example, this one not directly from the game but a hypothetical.
"Gee golly there's a lot of variables coding this. When I write this one up I hope I'm not accidentally duplicating a variable from a completely different place in the game. Then a change to one place would throw the other one out of whack. Well I looked as best I could, but in something this complex humans and computers are not infallible. I should be happy it works currently."
But nobody caught it? Nobody at all? Stuff like this is out there. Right now. Live. If it's a bug now, it was bugged in testing. Why didn't they fix the bugs if they were in the test realms? Somebody had to stop and say "Hey, why is my druid able to do all these cool things it never could before."
I've worked for large corporations as well. Know what most do when they roll out an update and it's as bugged up as these patches are?
They roll back to the last good backup, fix the bugs, and don't force the update again until they KNOW it's good. Anything else would be bad business practice.
I've worked for large corporations as well. Know what most do when they roll out an update and it's as bugged up as these patches are?
They roll back to the last good backup, fix the bugs, and don't force the update again until they KNOW it's good. Anything else would be bad business practice.
Scholar
38 posts
Even in just my programing classes at school I know that things like this happen. For example I had a program assignment I did, it worked fine when I tested it etc etc etc. I got turned it in thinking an easy A, and ended up getting a B because It wouldn't output like it was supposed to for the GA. Better yet if you forget a single / . or anything sometimes the debugger your using will think its right thus not catching it. And unless your able to proof read 100% over thousands and thousands of lines then chill out. Its life, and to be quite blunt.. Crap happens! (this is the main reason I swapped majors :-p)
Edited, Jan 10th 2007 4:11pm by rehevark
Edited, Jan 10th 2007 4:08pm by rehevark
Edited, Jan 10th 2007 4:11pm by rehevark
Edited, Jan 10th 2007 4:08pm by rehevark
Don't they have their private test servers? It's a glaring bug.
Recent Visitors: 376
All times are in CST
Anonymous Guests (376)
- Forums
- World of Warcraft
- General Discussion
- Blizzard Should Check For Bugs Before They Release A Patch..
© 2024 Fanbyte LLC