We do have a fix for this ready, however, it will require a client-side patch to address. We're in the process of building a small patch to fix this and a few other issues which also need client updates. You're likely to see what we call a fast patch in the near future (a la patch 4.1.0A in recent past: http://us.battle.net/wow/en/game/patch-notes/4-1-0a).
Sorry, it's been a while since we've communicated anything about this. Our team has been very busy lately working on a lot of cool things, as well as finalizing plans for BlizzCon, but we're trying to keep our eyes on the forums as much as possible in the process. :) |
|
Having a textual conversation really doesn't have to work this way. I specifically said "my team" in my post to ensure there was no confusion -- but even then I can't ensure anyone correctly understands the meaning of what they're reading. My team doesn't build patches. And the people working to develop, test, and deploy fixes, and create new patch builds, aren't preoccupied with BlizzCon right now. The process of documenting, troubleshooting, and testing bug fixes is complicated and constant. We've made many fixes since day one of patch 4.2's release, most of which could be done server-side. All the while we've been working on fixes for bugs that can't be addressed without a client-side patch. But the process for creating a stable new patch build to address any known issues is certainly not as easy as I think you're implying. |
|
To be clear, we know it's an annoying issue and it's unfortunate that it went live. But as I spoke in another thread a while back (a portion of which someone quoted earlier in this thread), this is a relatively complicated issue. We haven't just been sitting on it all this time. We want to make sure the fix is good, while also avoiding throwing together a quick patch to address it at the risk of breaking other things.
|
|
It's not that simple though, especially when you consider all of the other things players feel we could/should be saying on these forums. That said, my original point was that we know we need to push harder to keep the level of communication up. |
|
Well, I do appreciate that you have this level of respect for us, Madbro, and also hold us to high expectations. All's I can say is I completely understand where you're coming from. :) |
|
Noted. |
|
There are some really cynical people on this forum. The player to which I responded stated a date for when he expects this issue to be fixed. I publicly made a note of that deadline. Was his feedback stated in a constructive way? No, but that doesn't mean my response must be interpreted as sarcastic. I'm actually surprised by the amount of drama that's spawned from a one-word post of mine. People are reading words in blue through so many lenses of preconceived notions, feelings, and sensibilities. There was additional meaning implied in my post, but not the meaning you think. |
|
... I guess I'll spell this one out. It was more of a hint at our estimated timeline for releasing such a thing. |
|
I was at home when I wrote that, but I kind of like this idea. :) |