Wild Growth Bug: Bugging Druids Since 3.1
When 3.1 came out I, along with many, many other druids, found Wild Growth to be… well… buggy. Sometimes it just didn’t work, telling me my target was dead or out of range, when the target I was clicking on on Grid was very much alive. I, being no rocket scientist, for many weeks thought that it had something to do with my own Grid/Clique setup and just worked around it, mostly by manually retargeting and clicking on Wild Growth in my hotbar. It didn’t occur to me that it was the retargeting that was fixing the problem, and not the clicking in my hotbar. /facepalm. At any rate, I eventually ran across this post that explains the bug and has a reply from Ghostcrawler saying that he “can’t imagine it’s going to be too challenging to fix.” That was April 21.
Not long after reading this post and realizing that the bugginess of this spell could not be chalked up to my own incompetence in configuring Grid/Clique, but rather was a bug straight from the Blizzard hive, I ran across this post from Lissanna at Restokin, pointing out some macros that would help to get around this bug. Thanks Lissanna! =)
My next move was to seek out this post on We Know Forums! that gives a good step by step guide as to how to go about setting up Clique to run a custom macro. I followed the directions, set it, and forgot about it.
I forgot about it, that is, until I changed servers this week. When I changed servers, random things happened to my addons. Some of them, like Dominos, stayed set up perfectly. Some of them, like XPerl, stayed mostly set how I wanted them, but got a little shaken up around the edges. Some of them, like Clique, had all of the settings wiped and I had to start from scratch. In resetting Clique assignments, I forgot all about my WG macro bug circumventing strategy and just assigned Wild Growth like any other spell. And found quickly that the bug is still flying high, stinking up the place.
I backtracked my steps looking for that post on which Ghostcrawler had foreseen an easy fix, and found that druids are still bumping it every day. I hope they get to it soon for people who don’t realize it’s a bug (as I long did not) or don’t have the resources to set up the macro that will help them around this. In the meantime, I’m thinking of sending Blizzard a gigantic crate of pesticide.
There are 7 Comments to "Wild Growth Bug: Bugging Druids Since 3.1"
Yeah I noticed this is a very annoying bug. I’ve noticed this happen a lot to Wild Growth, but some of my other spells don’t focus on the correct targets either…weird, and annoying…especially in arena!
EDIT: As mentioned on the forums, it seems to occur when you are targetting something else (e.g. you’re raid healing and you get aggro from a boss – now your healing is buggered up until you untarget…)
I am not a macro girl, so I spend a lot of time on raids hitting esc to clear my target. I thought about posting on the forums that it is still a problem but with the 25 other pages up, I figured they got the hint.
Some days, I say to myself “Feral forms can wait, right? I want my WG fixed!”
I hate this bug. It makes things extremely difficult when I’m an Ignis OT healer and my OT is out of range, and I’m trying to cast WG on myself after flame jets. So annoying to have to hit esc multiple times just to clear my target…
I didn’t update my blog’s macro lists with the “fixed” /cleartarget macro sequence for a long time, figuring the bug would be fixed, but then when I later went back to add in dual-spec macros, I added it in. It’s ridiculous that they’ve taken so long to fix the targeting error
You’re having way too much fun making these little theme images for your posts aren’t you?
I decided I would use my Wildgrowth as a “clear targets” function which suits my healing style nicely. Essentially – everytime I cast Wildgrowth, the macro wipes my target before applying WG on the selected Grid target. The spell cast, I’m left with no target which again, suits my style of play when healing with Grid.
Avoids all targeting issues.
And this is why I’m glad I don’t use mods. Never even heard of this bug before today.