Bucket Guild | FUBU BH Forums

Alright, so with a few exceptions, my mouseover macros look something like

Now this, casts them at the mouseover target if it exists, otherwise it casts them as normal.

With this patch, this type of macro has a small bug. If you spam it, the first one will go to your mouseover but all following ones will hit you instead. The simple fix to this(some of you may already have your macros in such a way) is the following.

I made this post simply for those who might be experiencing problems with it. If your macro is a bit more complicated than that, post it here and I'l try and fix it.

The first one you are telling it try and cast the first spell, then cast the second regardless.

Druid: Meowth
« Steam »« Xfire »
Glorious Death Metal Music

That's not the point I'm making.
Yes, if there is a mouseover target, it takes priority. If there is not one, then it casts it on what it would otherwise.
What I'm saying is, using the first macro, you mouseover party3 and spam the heal. The first time it will hit party3 and all others will hit you or your target even though you still have the same mouseover.
This was never a problem before this patch.

Something with the new ability queue system doesn't like macros. I have snake trap and explosive trap macro'd together and if use trap launcher, it won't allow me to launch either one if it's on a macro.

I was simply posting this for those who might have been having a problem with this. Both macros do exactly the same thing, currently only the second works though.




If you're saying what I think you're saying then by your logic

spamming such a macro would yield Mut, Evis, Evis, Evis, Etc.

Edit: So after some testing, it does indeed Mut, Evis, Evis, Etc.
Seems to me they're just taking a step back here, I could be wrong, but didn't they break macros like that before?(lolhunter1button)

Edit: So after additional testing, it seems macros are using the first ability in a macro and if you keep spamming it, it will use the last in the macro.


^ Will cast spell 1 and then spam/alternate between 3 and 1. Depending on cooldowns and GCDs this also changes yet again.
Example:

In theory, should use Mortal Strike and then Execute, probabaly spam execute till Mortal Strike comes off cooldown.

Once again, they added this ability queue system to fix an exploit I believe, yet they only opened the way for more broken macros. This leads me to believe that unless they can get rid of the exploit in another way, they'll probabaly do something even more drastic to counter people exploiting this new macro system.

well the problem is that you should have made your macro like this in the first place

/cast [@mouseover,help,nodead][exists] Spell


the first exists in the mouseover is redundant logic, and instead of having the second line trigger you just have the second conditional trigger.

Akina: bitch I will stab you in the face

I don't get what you're saying.

Testing your macro out, it doesn't do what mine does.
Mine, prioritizes the mouseover target. If one doesn't exist, it casts it on my target or if the target is hostile, auto self cast. Yours will only cast on a mouseover. Nice try though.

I could shorten mine by doing @focus instead, which I might cause it looks way cooler.

well, then this

/cast [@mouseover,help,nodead][help,nodead][@player] Spell


it's a simple fail through. first condition fails, it goes to the second. second fails, it goes to the third.

my second conditional wasn't set to check if your target was hostile or not, just if you had one.

edit: and the reason you should use that instead is because the older macro posted worked indirectly, but not through the expected macro logic. it worked because nothing in it broke it, but it isn't how it's expected to be written.

thus, when they make api changes, mine will continue to work because it's the real version, and yours might or might not work because it just happens to work.

obviously, they changed the api so the original macro no longer ever went to the second line of code, which i don't think it would be intended to (if the first line fails, it just fails, unless the first line doesn't use the gcd).

Akina: bitch I will stab you in the face

It's acting different now because of the annoying bullshit spell queue system that has been implemented. Make macros right or gtfo!

Druid: Meowth
« Steam »« Xfire »
Glorious Death Metal Music

Well see, your recent macro works the exact same way as mine did before except it's all in one line. The first one, ONLY worked if I had a mouseover, otherwise it didn't do shit. The target being hostile or not was irrelevant.

My macros were just outdated ones that I slowly tweaked as I needed too. I made those like at least a year ago. My macro building skills have slowly improved and I updated a few of my druid's healing macros to only be one line, some I never needed to update.


and the only other's that are more complex than that were my paladin/shamans advanced focus macros.

Point is, my macros got the job done with no problem and the new ability queue system can suck my nuts!