Pain Suppression Fix - When?

#0 - July 9, 2007, 2:25 p.m.
Blizzard Post
As seen and acknowledged in this post:

http://forums.worldofwarcraft.com/thread.html?topicId=106616871&postId=1080810941&sid=1#66

Pain Suppression is currently not working as intended.

Q u o t e:
I just wanted to stop into this thread again and confirm that Pain Suppression is not gaining the benefit of Silent Resolve and this is now listed as a bug to be fixed in a future patch.

Pain Suppression itself is also not giving it's proper resist bonus as it should be and this is slated to be fixed at the same time.


Q u o t e:
It's being fixed as soon as possible, and while we do our best to hotfix high priority issues as often as possible, it isn't always possible to hotfix. This is something that needs to be fixed client side.


The above is a quote from the above linked thread that was made on June 1, 2007.

Since then, the issue with the PvP trinket breaking (dispelling) Warlock's unstable affliction has been fixed. It was fixed within days of being reported. However, the issue with Pain Suppressions dispell mechanics has gone unfixed since it was originally reported over a month ago. So, why dispell mechanics for one 41 point talent can be fixed in a matter of days, but another 41 point talent cannot be fixed for well over a month, I have no idea.

Can we please get an update on this issue? It seems a little out-of-sorts for it to take this long to fix a (flat out broken) 41 point talent.
#6 - July 9, 2007, 4:16 p.m.
Blizzard Post
The fix is scheduled for an upcoming patch and should correct the chance to resist dispels like it is intended to. Unfortunately, not everything can be put into a hotfix.
#32 - July 9, 2007, 8:12 p.m.
Blizzard Post
Q u o t e:
Then why ever put anything other than shwostoppers and dups in hotfixes.


Some things require a client side change such as this particular bug. It requires more than just a simple hotfix push sent out to correct it and have it work as intended. What may seem simple to you may be much more complex than you realize and take a little extra work. We've acknowledged the bug and also acknowledged that the fix is in the works. There isn't anything more that we can do at this point in time in that regard.