Yay!

/tar Zootfizzle
/cheer



/tar Malreth
/cast Shadow Word: Pain

Ow.

OW!

Oh, she's defending herself somehow!

---

Q u o t e:
The /castsequence issue first appeared just over 4 months ago now. Some players have reported a great amount of detail concerning these issues during this period and as one of those players I personally will -not- be trying out the next PTR (for what should be obvious reasons).

This issue will not be fully resolved when the patch hits Live, yet again.

Best wishes for those that still encounter the issue, albeit less frequent then those that will come to complain.

---

Translation:

"Hi, you all suck at coding. I'm having problems, but I'm not actually going to tell you if it's fixed. Instead, you're supposed to be psychic and omniscient so that you know 100% for sure that in the 4 gigabytes of code that exists in WoW, there isn't a single bug that I'm going to encounter. How dare you expect me to tell you when I'm having problems. You're supposed to read my mind.

Die."

---

Q u o t e:
The /castsequence issue first appeared just over 4 months ago now. Some players have reported a great amount of detail concerning these issues during this period and as one of those players I personally will -not- be trying out the next PTR (for what should be obvious reasons).

This issue will not be fully resolved when the patch hits Live, yet again.

Best wishes for those that still encounter the issue, albeit less frequent then those that will come to complain.

---

HUH??

Users: There's a bug
Blizz: Thanks for the reports..... think we've fixed it, can you guys please retest
You: This bug annoys me. It's been around for ages. No, I'm not going to test whether the claimed fix works before it goes live.

I completely fail at seeing your "obvious reasons" for not testing. You insist on getting a bug fixed, Blizz attempt to fix the bug, yet you refuse to test. No doubt if it's not fixed to your satisfaction, you'll be back here post 2.3.3 to yell at Blizz some more.

Troll much?

---

Q u o t e:
The /castsequence issue first appeared just over 4 months ago now. Some players have reported a great amount of detail concerning these issues during this period and as one of those players I personally will -not- be trying out the next PTR (for what should be obvious reasons).

This issue will not be fully resolved when the patch hits Live, yet again.

Best wishes for those that still encounter the issue, albeit less frequent then those that will come to complain.

---

I wouldn't be the least bit surprised if this next patch contains code that checks for any character named "Trevion" on the US-Dragonblight server, and upon finding that it is indeed that player, yells at them, and draws big pink dragons all over the screen every time you click a macro.

Just a thought.

I kind of sympathize with that attitude. I understand what the testrealms are and what they're for and all, but it is still frustrating even to someone like me who hasn't told blizzard a thing.

Its not that I'm angry that they don't want to go look up hunter shot rotations on the myriad of community sites, its more that they're not confident enough with the mechanics they're making changes to, to peg what their changes are going to do without extensive player testing and feedback. At first I told myself that they figured they had it, and just wanted some people to hop in there and prove 'em right, so to speak. But they already reset the servers to implement a fix just a couple of days ago, so the fact that their fix didn't fix things dented my confidence, enough that I'm actually posting on the forums to say so.

I just spent the last few days wrapping my head around the very bizarre changes they'd made to things, and a few days before that wondering at why my logs looked funny from the set of changes made with the patch, I'm not looking forward to trying to understand a new set of changes that might also not fix things.

On the other hand, its kept my mind more occupied than it usually is from killing random mobs for money and loot, so I guess I can't complain too much.

As has been said in my SE300 class over and over and over again... testing cannot prove the absence of bugs.

Think of the simple program which adds two 32-bit integers X and Y to come up with the 64-bit result Z.

How many test cases do you need to prove it works? 2^32 * 2^32 = 2^64 = 18,446,744,073,709,551,616 test cases.

How long will that take?

1 test per second: 18,446,744,073,709,551,616 years
1000 tests per second: 18,446,744,073,709,552 years
1,000,000 tests per second: 18,446,744,073,710 years (Yes, that's 18 trillion years still).

And that's for a simple x+y program. Obviously testing can't cover every single case; most testing is done with boundary testing which will usually pick up problems, but can't always find everything. Thus, Blizzard is going to need help, specifically from people whom are having the most trouble, so that they can ensure the problem is gone.

tested, all seems to work now, tryed about everything to break the casting besides getting stunned. macro kepted working fine

Zootfizzle, thanks for the hopeful response. I have been concerned that only /castsequence issues would be resolved though you topic title hints at maybe something more.

Guess we’ll wait another week or two and find out what is fixed and what isn’t. It truly would be disappointing if some macros NEVER worked again due to a single patch.

---

Q u o t e:
Zootfizzle, thanks for the hopeful response. I have been concerned that only /castsequence issues would be resolved though you topic title hints at maybe something more.

Guess we’ll wait another week or two and find out what is fixed and what isn’t. It truly would be disappointing if some macros NEVER worked again due to a single patch.

---

Why wait? Go test them now on the PTR and make sure they work.

---

Q u o t e:
Guess we’ll wait another week or two and find out what is fixed and what isn’t.

---

Umm... or you could just go test it on the PTR like the poster above you...

---

Q u o t e:
It truly would be disappointing if some macros NEVER worked again due to a single patch.

---

What planet are you from? This is a sticky by a blue saying they're working on a fix. What twisted, morbid logic would even make you think something like that?


<Blizzard Employee 1> Hey! I know how we can mess with our players! Let's rip one of the most used macro features right out from under their feet!
<Blizzard Employee 2> Yeah! that's a great idea. We can even tell them we're working on a fix but instead just string them along with posts of hope.
<Blizzard Employee 1> Perfect! I'll get right on it!

De we have to wait till next patch or can we just download the Ptr Patch now and it will fix it if so. Is there a link we to get the patch

The PTR is a separate instance of the game that you copy your character to. It has no effect on your actual characters on your home realm.

---

Q u o t e:


The thing is, anyone with any hint of programming experience understands that this is an all-too-common occurrence. The vast majority of the time you fix one bug, it only ends up introducing others. No matter how much testing Blizzard does internally, they'll never be able to match the rigors of actual player testing.

The nature of the now-deleted post shows a complete lack of understanding of software development in general. You can't just demand that things be fixed and expect a result. Whining doesn't help and can make it worse when (as is the case now) discussion of said whining takes up the bulk of a thread.

---

Yes, actually as the customer they can demand anything they want. It's up to Blizzard to manage expectations with results vs defects. Blizzard has allowed a culture to develop around not managing these expectations. This has allowed the the complainers to rule the software development process and the forums.

IE: AV. Blizzard changes stuff, there is no feedback method to allow for customer review or criticism. Result: Unmet customer expectations. Action is only taken when the whining reaches critical mass.

In effect the only way to see something fixed/ changed / nerf/ or buffed is to complain about it and hope enough people whine with you.