I’m not going to get into this silly argument. But there are plenty of bugs that have gotten attention and still haven’t been fixed. Just because a bug or exploit got fixed shortly after a streamer or whatever made it public, doesn’t mean that blizzard wasn’t already going to fix it.
Sure making it known and even typing out the exploit so people can copy and paste it (which is dumb to do because now everyone knows how to exactly do it) might bring exposure, but it doesn’t mean that they weren’t already going to fix it or that it will get fixed. But exposing the whole macro the way it is in the OP means that some people will definitely now use it.
What it does is it turns an issue that they might know about from a low priority issue that gets kicked down the road like a can into a HOLY @#@$ WE HAVE TO FIX THIS RIGHT NOW issue.
1 Like
If you want to get it fixed, why release the info on a Saturday?
Why not wait until Monday morning when Blizzard devs are actually at work?
“Hey everyone, here’s the exploit. It’s good for at least another two days. Enjoy!”
so just because that’s how you would respond to an issue doesn’t mean that’s how others will respond.
what OP is doing is exposing an exploit. which means that this thread should be taken down.
this is the proper place for it.
I understand your concern and it is valid. I’m a bit more jaded and cynical when it comes to things like this and that it what drives my opinion on the matter.
I think this post has served it’s purpose and taking it down is fine, but the cat is already out of the bag so-to-speak.
I personally won’t use this macro and I’ll continue missing kicks to prove it.
Like who? Please show me besides simply stating something with 0 evidence.
what its done is shown half the wow pvp pop (1.3k people kek) how to use the macro. guaranteed the amount of people using it will exponentially increase. and if blizzard doesn’t fix it soon then we have an issue.
Where’s your evidence that the only people who succeed use MMO mice? You brought it up first
1 Like
Yep, this is now a high priority fix instead of a low priority fix.
One of the problems with things like this is that when it isn’t public knowledge the people who know about it will keep it to themselves to have an unfair competitive advantage for months if not years.
I’d say posting something like this is only justified when the person has tried through direct private channels to make a company like Blizzard aware of it but they do nothing to fix it for an extended period of time.
At that point, if someone posts it then blame the company and not the person posting it.
2 Likes
are you trolling me right now? are you being serious?
do you not see the contradiction?
things like this always exist. but a simple bug report would be completely fine. devs are more likely to look in there anyways.
Mhmmm shaman mains are sus now specially if there defending this bug
Can someone make a macro that blocks dps from overlapping their CDs while pained suppresioned or domed.
2 Likes
This is where you and I differ. I’ve had direct experience that it isn’t enough and that is something that has happened across several different games. This is why my position is different than yours.
2 Likes
I don’t really care about my grammar on a gaming forum sus shaman main
macro functionality has been updated repeatedly throughout the years and a lot of things are now possible that weren’t previously.
Just an easy example, but @arena1 and other such things weren’t in the old game, and were one of the first things the private server players had to get used to on TBCC as it changed how rogue comps would play vs eachother for example.
But also there were macros that broke the game back in the day, too. Another easy example is swifty having a macro that let him charge while in combat back in vanilla.
IDK if specifically this macro above is new or could’ve been done on the old client, but I think it’s worth pointing out that modern macros far exceed what was possible in older clients.
either way this macro above is freaking insane lol.
We all know that the old /castrandom macro was the most powerful macro known to humanity. Nothing could ever compete with that. 
Yeah I don’t know the specifics on it. I’m not a macro wizard, I mean I literally have 3 macros tops per char, and generally they are @focus clone/para/fear, etc…
I’m willing to bet though a macro like this was probably something post MOP functionality. But, still, the Macrowizard class is pretty neat.
who’s defending the macro. i’m making a very legitimate point that this will hurt more than it will help.
people might be making the argument that exposing this will be like ripping off a band aid, because more people will be using this then blizzard will notice and fix it. but what happens when they dont fix it and people will be complaining about it a month from now?
i also find demands like these to lack decency. people are forcing blizzard to fix something immediately like a spoiled child.
This is something that needs to be fixed yesterday. It’s not even debatable how broken this is.
Especially since it can be wildly accusable to players for having just really good timing and potentially getting future punishment because this ISN’T fixed.
4 Likes