/ac "Tri-Disaster" <t>
/ac "Fester" <t>
/ac "Bane" <t> or /ac "Energy Drain" <t>
/ac "Painflare" <t>
/ac "Dreadwyrm Trance" <me>
/ac "Deathflare" <t>
I though of this while playing Seal Rock.
The idea is that you can keep pressing a single button/key and it will cast them all in order.
Please know that you'll need to use Aetherflow and gain 3 stacks beforehand.
You could add in /ac "Aetherflow" <me> at the top if you wanted (I haven't tested it out)
Also, Fester, Bane, and Painflare's order can be re-arranged.
If you don't know this macro works, let me tell you.
All these actions in the macro have "long" cooldown timers.
When you first press the macro button, the game will perform the first action "Tri-Disaster". "Tri-Disaster" will then go to cooldown state.
When you press the macro button again, the game will try to use "Tri-Disaster" once more; but since "Tri-Disaster" is still in cooldown, the game cannot use "Tri-Disaster" and will execute the next line of text.
When you press the macro button for the third time, the game will skip the first and second line of text and execute the third line of text.
This process will repeat every time you press the same macro button until the game reaches the last line of text /ac "Deathflare" <t>
Just remember that all those actions in the macro have fairly long cooldowns and that's how the game "skips" lines of text.
If one of those actions in the middle of the macro were to complete its cooldown and if you haven't reached the last line of text, then the whole macro will fail out of order when you press the macro button again. That is something to consider.
Thanks for reading!
Edits:
Originally, I had the macro cast Swiftcast at the start and then work its way down the line and cast Ruin III after Dreadwyrm Trance. After testing that Macro in Seal Rock, I found that Swiftcast and Ruin III isn't a good idea to have in the Macro.
I erased Swiftcast and Ruin III lines due to high macro failure rate.

Reply With Quote







