Here's a version of the non-glyphed Horn of Winter macro that checks to see if it's actually usable so you don't accidentally click off the buff if you have twitchy fingers and mash buttons many times (possibly in futile attempts to defy latency issues or because of high caffeine consumption, or because of some other personal issue.)
/script local start, duration, enabled = GetSpellCooldown("Horn of Winter"); if duration == 0 then CancelUnitBuff("player", "Horn of Winter") end;
/cast Horn of Winter
/cast Icy Touch
/script local start, duration, enabled = GetSpellCooldown("Icy Touch"); if (GetTime()-start)<0.01 then EquipItemByName("Sigil of Awareness") end;
/cast !Rune Strike
/script local start, duration, enabled = GetSpellCooldown("Obliterate"); if (GetTime()-start)<0.01 then EquipItemByName("Sigil of the Unfaltering Knight") end;
/cast !Rune Strike
The lua code simply makes sure the Sigil doesn't push back your GCD by more than 10 milliseconds and that you've actually used something to trigger a cooldown on the current ability, else it won't switch (allowing for more button mashing and facerolling without undesirable effects).
I replace Icy Touch with the macro altogether and use the Obliterate one with a key modifier on the last Obliterate in my rotation. Because of the consistency and predictability of most rotations, it's appearing to work out quite well. And since all of the abilities we'd want to macro a Sigil switch to are instant, there are really no drawbacks I can think of.
Last edited by Magic : 02/26/09 at 1:34 PM.
Reason: Redundant adjective in first sentence. I accidentally put the word "accidentally" in there twice, accidentally.
/macro <casts death grip>
wait 30 seconds
/macro <casts dark command>
wait 5 seconds
<macro cast sequence resets>
/macro <casts death grip>
After all that is the point of the reset command, is it not?
No, if you use castsequence reset=35, the reset counts down from 35 and starts over every time you cast (or try to cast) the castsequence. If you are mashing a castsequence with a reset=1 three times a second, it will never reset. It has always been this way (otherwise, it could be used to automate many things).
/cast Death Grip
/cast Dark Command
/cast Death Grip
/cast [mod] Dark Command
But as there is no mod in the Macro LUA I know that checks if targettarget=player. As this won't function we need get back to /run (/script). Preposter Magic gave the basics anyway so credit goes to him pointing in that direction. What I will be testing looks like this:
#showtooltip Death Grip
/script local start, duration, enabled = GetSpellCooldown("Death Grip"); if duration == 0 then CastSpellByName("Death Grip") else CastSpellByName("Dark Command"); end
I thought they had removed the ability to "if x then cast". Let us know if you found something, but I highly suspect that macro won't work right.
That is correct, lua functions that modify spell behavior (namely CastSpell() and CastSpellByName()) are protected and have been unusable by macros since 2.0. Accessors of certain spell information, however, are still usable and while you can't entirely automate your character with lua code, you can still find out important information regarding a spell/ability to use in conditionals.
And then use the results of those conditionals to do things that don't involve casting a spell... like equipping an item... or clicking off a buff.
Heal the ghoul
/cast [target=pet] Death Coil
Heal yourself with death coil (requires Lichborne T3 Frost)
/castsequence [target=<put your nick here>]Lichborne, Death Coil, Death Coil, Death Coil
Pestilence then Blood Boil - wrote recently as the lack of cooldown on Pestilence causes me to not notice that it's been triggered and I could Blood Boil. It should be noted that I got a strange response when I triggered this the first time and may need to tinker with it further.
/castsequence reset=9 Pestilence, Blood Boil
There may be typos.
EDIT: Pestilence then Blood Boil works fine. Reset was lengthened to the maximum I thought needed (if you DnD then Pestilence on a pull). However, you should set it for less if you can.
Last edited by rei-gouki : 03/06/09 at 9:14 AM.
My understanding is that macros under modifiers will cast everything inside the modifier, then nothing outside the modifier.
Essentially a /cast deathchill /cast HB works. When you add the modifier to deathchill, the HB needs a modifier as well. With your example, to do deathchill AND hb (assuming keybind 1):
(shift)1 1. You need to hit the key twice, once with and once without modifier.
With my macro, it will cast BOTH with 1 press. since deathchill has no gcd.
Onto the Death Grip/Dark Command Macro. I found a way that works for me (addon wise) but running a single button macro is not available as every function I knew from my scripting days is now protected or not running the needed modifier. I will still see if I find something in my days off WoW but seem I have a lot to lookup what is still available.
Would not [target=player] be enough instead of [target=<name>]
/castsequence reset=35 Death Grip, Dark Command, Dark Command, Dark Command, Dark Command
I realize that it's not perfect, but it comes pretty close to what I was after. Death Grip works, then Dark Command works, and after awhile, Death Grip starts working again. lol
Just a warning, for me that macro sometimes made taunt not work somehow. Ie. DG would be on cd, taunt off cd, and still if I pressed it nothing would happen (no taunt as opposed to what you would expect). Maybe I spammed it too much, dunno /shrug
if you're not a troll, remove Berserking from the macro. you might want to consider rerolling too.
raise dead is usually on cooldown when i use this macro, but I put it at the end just in case it's not. I typically cast Raise Dead around 66% on a boss, then spam this macro at 40% (or whenever I get bloodlust)
Yep, that should work perfectly. I wrote it without consulting a variables list and tried "self" and "me" before falling back on just the name of the 'toon. I had the same problem with my warlock pets before stumbling on the "pet" variable.
One thing of note that I found with macros using the "?" icon, which means it cycles to whatever spell is next and hides the rest, it helps to have an action bar reserved for all the spells you have a cooldown on for you to look at so you know how much time is left on CD. Running OmniCC or similar addon that displays a number instead of the standard CD sweep helps further.
Update about the Pestilence > Blood Boil macro I have above, it works fine. Appears to have just been the way my action bar add on, Dominos, handled the display.
Rune Tapping before Berserking seems like a poor idea.
really the only reason i start with Rune Tap is because it has the shortest cooldown and the macro was behaving weirdly when longer cooldown abilites were in front. i'm kindof a newb at macros so i just hacked it that way. my health is very rarely low enough that i would gain anything greater than the base 10% from berserking, so i'm ok with it.