Frostnova macro's

[stingc]

I can just use
/assist <toon1>
/cast frostnova (rank1)

but i use 2 mages for dual-boxing.
i know there exist some macro that makes it able to cast Frostnova with Toon1, and Toon2 will with the same keybind not cast Frostnova untill i click it again and will not cast Frostnova untill the freezing effect lasts off.

I had it before but during the patches and inactivity i lost it.

Anyone who can give me that macro.

Greets, Stingc

[beyond-tec]

I can just use
/assist <toon1>
/cast frostnova (rank1)

but i use 2 mages for dual-boxing.
i know there exist some macro that makes it able to cast Frostnova with Toon1, and Toon2 will with the same keybind not cast Frostnova untill i click it again and will not cast Frostnova untill the freezing effect lasts off.

I had it before but during the patches and inactivity i lost it.

Anyone who can give me that macro.

Greets, Stingc


/castsequence reset=2 Frostnova,
/castsequence reset=2 ,Frostnova

[stingc]

It is not working like it should

i now they just cast Frost Nova together

[sorrowharvester]

It is not working like it should

i now they just cast Frost Nova together

The first line goes on Toon1
/castsequence reset=2 Frostnova,

The second line goes on Toon2
/castsequence reset=2 ,Frostnova

You can make the reset a tad longer if you like.
Also, if you spam it quick, they will cast together.

[amalgam]

The reset should really be 24 if you have Imp Frost Nova as a talent. Also, since FN is not a targeted spell, there's no need to /assist for it.

[Vyndree]

The reset should really be 24 if you have Imp Frost Nova as a talent. Also, since FN is not a targeted spell, there's no need to /assist for it.

Except that the reset "resets" each time you push the button.

Example
0 sec - Frost nova 1
12 sec - Frost nova 2

If frost nova 1 is on the same button, then the button will reset at 36 seconds, but the "," will iterate on the "Frost nova 2" macro. Now, your 2 frost novas are no longer staggered.

Not so cool.

[amalgam]

Hmm....I didn't play my 4 Mage team very far, but I never tested FN thoroughly. The "reset=24" worked beautifully for me. I see what you mean about the FN stagger delay.

Personally, I never found myself needing more than one FN very often, but it seems like using the method you describe, Vyndree, might have problems of its own, namely in that you will eventually have to double- (or triple- or quadruple-) tap the button to accomplish the staggered FNs unless I am missing something.

For instance, assuming a reset of 12 seconds:

Tap 1: A FNs, B's and C's macros advance one step.

If Tap 2 comes at, say, 16 seconds, now you have to tap once to advance all the macros one step (since A's FN will still be on CD) before you can access an FN. I am unsure of whether or not this consumes a GCD, but I assume it would given a failed conditional check in other macros triggering GCDs post-2.0.

Perhaps I misunderstood something.

[Vyndree]

I am unsure of whether or not this consumes a GCD

Taps on "," iterations do not trigger a GCD. The only problem you'd have is that if you're a button jammer, you'll notice that chain-tapping the macro will cause the rotation to start going out of order and eventually you'll get all your frostnova's on the same button push.

I've had complaints about the "reset" portion of macroing when I was attempting a spammable holy shield macro (to get rid of the "whoosh" sound that happens every time you press a spell that wasn't off cooldown). I couldn't find a solution, so I ended up having to turn off all of my sounds to get rid of the problem.

I'm sorry I don't really have a good solution for you. Just warning you to keep that in mind when creating your reset timers. reset shouldn't be used as a cooldown manager - it should be used as a generic reset. If you know you'll never press frost nova with more than a 10 second delay, then make your reset 10 seconds.

[amalgam]

Taps on "," iterations do not trigger a GCD.

Probably not, but in the situation I outlined, Tap 2 will cause A's FN to fail, which was what I was referencing will consume the GCD. Possibly. Maybe. I dunno. Excuse the lack of clarification.

[Vyndree]

Taps on "," iterations do not trigger a GCD.

Probably not, but in the situation I outlined, Tap 2 will cause A's FN to fail, which was what I was referencing will consume the GCD. Possibly. Maybe. I dunno. Excuse the lack of clarification.

If A's FN is on cooldown, and B is on a "," tap, then you will not trigger a GCD on either toon.

"," = no GCD
FN on cooldown = no GCD
FN = GCD

They're instant casts, so the silly fake-GCD thing that Blizz implemented to get rid of /stopcasting macros + addons like Quartz doesn't apply.

Try it. Put frost nova on your bar, click it, then spam click it over and over and over while it's on cooldown. No GCD. (I used Holy Shield for this test)

[amalgam]

It doesn't do it normally; only when present in a macro that fails to cast for whatever reason.

At least, that's what WoWWiki says. Lemme find the page.

EDIT: OK, apparently I took one bit of info and applied it elsewhere. The event I described is only listed as occurring if you have mutliple "/cast" commands in one macro.


In general, you cannot cast more than one spell with a single click of a macro. Most spells and some items trigger the global cooldown (GCD) which keeps you from taking too many actions at once. Even if a spell fails to cast, if it would trigger the GCD, it prevents subsequent /casts in the macro from running. This was not the case prior to patch 2.0 which is why you may still come across macros like the following:

/cast Overpower
/cast Execute
/cast Mortal Strike
/cast Sunder Armor

Macros like this do not work anymore.

From WoWWiki. (http://www.wowwiki.com/Making_a_macro#Conditionals)

Also, I removed the quotes from this thread. Forgot I used that button to reply.

[Vyndree]

This is true when you're trying to do 2 casts in the same macro. It also fails for some (but not all) trinkets for some weird reason.

i.e. (and I apologize for the crazyness of this macro, but this is honestly my button spam macro)

/target [target=focustarget,harm,nodead][target=party1target,harm,nodead]
/castsequence [combat] Vengeance of the Illidari, Ancient Draenei Arcane Relic
/castsequence [nocombat,harm] reset=5/combat Totem of Wrath,Lightning Bolt,null; Lightning Bolt

The code above works perfectly for me. The code below does not:

/target [target=focustarget,harm,nodead][target=party1target,harm,nodead]
/use [combat] Vengeance of the Illidari
/use [combat] Ancient Draenei Arcane Relic
/castsequence [nocombat,harm] reset=5/combat Totem of Wrath,Lightning Bolt,null; Lightning Bolt


The 2nd macro will "stick" when Ancient Draenei Arcane Relic is on cooldown (I've deduced that it's due to a "fake" GCD), and refuse to work until it comes off of cooldown.



However, the macro you showed me has one spell and one spell only in it: Frost Nova. Therefore, it will not trigger the GCD.

Another example test you can try at home: make a macro that just says /cast Frost Nova. Button mash the macro. No GCD when Frost Nova is on cooldown. (again, I used "Holy Shield" since I don't have any mages)

[amalgam]

Yes, I edited my post with the link to the page on WoWWiki I misread.

Also, curious question, but what's the "null;" for in your castseq there?

[Vyndree]

Yes, I edited my post with the link to the page on WoWWiki I misread.

Also, curious question, but what's the "null;" for in your castseq there?

Every now and then I will still be considered "out of combat" until my lightning bolt lands. I don't have an addon to increase the length of my macros, and I'm nearing 255 characters, so it's just a placeholder for a non-spell so that it waits until the lightning bolt lands and puts the character in combat, which then puts me in the second condition of my cast line (which is just "Lightning Bolt").

If that "null" weren't there, and I were spamming the button, this is what would happen if the enemy target was far away.
Cast ToW
Cast Lightning Bolt
Lightning bolt is mid-flight
Cast ToW
Lightning bolt lands, shaman enters combat
(Commence lightning bolt spam)

With the "null", this is what happens:
Cast ToW
Cast Lightning Bolt
Lightning bolt is mid-flight
Macro doesn't know how to cast the spell called "null", nothing happens
Lightning bolt lands, shaman enters combat
(Commence lightning bolt spam)

[amalgam]

Ahh, so it's to compensate for a problem with Blizzard's servers. I thought it was a special Unicode/ASCII character that carried over from WoW or the .wtf file.

[Vyndree]

Ahh, so it's to compensate for a problem with Blizzard's servers. I thought it was a special Unicode/ASCII character that carried over from WoW or the .wtf file.

It's not really lag, it's just that spells won't put you into combat until they actually land. This isn't a problem for things like shocks/chain lightning that have little to no flight time, but when you're at max range firing off a lightning bolt, it will take some time for hte lightning bolt to reach it's target (especially if it's running away from you), and I didn't want to waste mana on an extra ToW just because I was too over-eager with the button mashing.