Macro Changes in MoP
Fall-thrus
The release of patch 5.0.4 didn't have quite the same devastating effect on macros that we've seen with other expansions, but it still has its share of "boxer nerfs". The most evident of which I can't even rightly call a nerf, since it's technically a mechanics fix, and that would be fallthru macros.
For some time, we as multiboxers have depended on trying to cover as much as possible with as little fuss. We're used to sacrificing a bit of effective DPS to make running our toons a little more efficient to manage. Fallthru macros filled the gap in castsequences with a predictable DPS boost by taking advantage of the difference in the way the game's servers respond to and process /castsequence vs /cast, especially when taking latency into account.
Unfortunately, it was never meant to be used this way. A happy accident for us, until Blizz finally got around to fixing it. For lack of a better explanation, it was always intended that any spell line under the main spell line be used for things off the Global Cooldown. If the spell is effected by the GCD, the servers are supposed to defer to the top line.
Vague and clumsy explanation aside, it comes down to "not intended" and "fixed now". It might still work in some cases, but it's not something to be counted on. So, if you see macros using stacked abilities and they don't work for you, {as it stands now} it's probably just dumb luck that it works for someone else.
The fix? Instead of cramming the spell into one macro and praying, break it up and put it in its own macro and either add another step if you're using Mercurio's Method or another sent key if you're using Mosq2's method.
Macro Options/Conditionals
As I keep remaking macros, I find more and more things that used to work, but suddenly don't. Options and conditionals have been a pretty big headache in this regard. It looks like it comes down to the fact that "exists" is no longer implied. This means macros like this...
or
Code:
/cast [@party1target][@target]
...weren't passing through to the empty brackets or the target in cases where there was no party1, such as phased content or in situations where player1 is mind controlled, etc.
Simply specifying "exists" in the macros is enough to fix this issue.
Code:
/cast [@party1, exists][]
/cast [@party1target, exists][@target]
{more macro changes?}
Connect With Us