i doubt they'll take it away. all /click gave you was more macro space for one button click.
Printable View
i doubt they'll take it away. all /click gave you was more macro space for one button click.
It seems to me that rather than depending on clicking something 5 times a second you should just be doing something like what Yo-Yo has in his tanking Macro. Set your reset to whatever that spell requires.
Druid
/castsequence reset=8 Moonfire,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=13 Insect Swarm,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/cast Wrath
Shaman
/castsequence reset=13 Flame shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=8 Lava Burst ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/casts Lightning Bolt
reset parameter only works if you don't press the button for X seconds.
Thanks, that's what I was missing.
This seems like a great way to optimize dk rotations. Macro length is not long enough to do a full rotation.
Plague Strike -> Icy Touch -> Blood Strike 2x -> Scourge Strike -> Unholy Blight -> Scourge Strike 3x -> Death Coil
So you can make a macro to put plague strike and icy touch. Then make a bloodstrike macro then scourge strike macro. Insert unholy blight in the scourge strike macro then just death coil manual when you have extra rp.
Have to test on the dummy to figure the comma amounts to do. But this gives me a start for testing. I need to edit this for the other half of the rotation.. Now if I can only find the post on what the full rotation is suppose to look like.
Bah.. forget this post. I need to get the attacks required for rotations before I can even start testing this.
== Macro 1 ==
/click MultiBarLeftButton7
/click MultiBarLeftButton8
/click MultiBarLeftButton9
== Macro 2 ==
/assist focus
/castsequence reset=target Plague Strike, Icy touch,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
== Macro 3 ==
/assist focus
/castsequence reset=target ,,Blood Strike, Blood Strike,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,
== Macro 4 ==
/assist focus
/castsequence reset=target ,,,,Scourge Strike, Unholy Blight, Scourge Strike, Scourge Strike, Scourge Strike,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Note to everyone wondering about rate of button pressing and button spam.
As said earlier in the thread, the macros with the castsequences with long lines of commas at the end all assume that you repeatedly hit the button at a constant, set rate.
Personally, my button spamming does not have a set speed, and usually is at a rate that is too fast to fit enough commas in a macro, so I would have to change my buttonmashing style if I were to be able to utilize such a macro.
Actually you don't, depending on your class. For example if you use 3 buttons and one of them is castsequence reset=combat Flameshock,,,,, then your macro will eventually grind to a stop when it reaches that Flameshock. It will wait until the C/D on FS is up before proceeding. Sometimes this can be very bad of course, but for the most part I'd rather wait 4 secs until FS is back up and let it continue its spam than try to work around this.
Ok I've read the bigfish posts a bunch of times and I am still lost on something. Are you saying that this:
# mac1
/click but1
/click but2
# mac2 on but1
/cs foo,,,,,,,,,,,
#mac3 on but2
/cs a,b,c,d
is better than this:
#mac0
/cs foo,,,,,,,,,,,,,,,,,
/cs a,b,c,d
I am currently using the latter and it seems to work. Is the click one supposed to be faster because of latency? I don't get it.
Thanks,
-K
It really depends on what spells you are casting, which ones are instant, and what you are trying to accomplish. Some things you can include all in one macro, others become so complex you run out of characters before being half way done with what you are trying to do. If you can get what you want done in one macro, by far that is simpler. On the other hand, juggling a half-dozen Dots on something like an affliction lock is an extreme headache.
you can certainly use multiple lines in one macro as effectivlely as /click in many situations, but /click has the following advantages:
- Allows you to break up a very long macro into mulitple macros to bypass the macro length limitations
- Allows you to modularize macros and swap in different sequences by changin what macro resides on a specific button
- Allows you to break up a macro into sections that have their own unique scope for clever use of /stopmacro
For example:
Button 1:
/click Button2
/click Button3
Button2:
/stopmacro [target=target,harm,nodead]
/target Astral Flare
/stopmacro [target=target,harm,nodead]
/assist focus
/stopmacro [target=target,harm,nodead]
/targetenemy [combat]
Button3:
/castsequence XXX, YYY, ZZZ
Alternate Button3:
/castrandom XXX, YYY, ZZZ
My Shadow Priest will have your babies now....
THANK YOU!
The Shadow Priest Do Stuff Setup
Couple of notes here...Code:== Macro 1 ==
/click MacaroonButton35
/click MacaroonButton36
/click MacaroonButton37
/click MacaroonButton38
/click MacaroonButton39
== Macro 2 ==
#showtooltip Devouring Plague
/assist focus
/castsequence reset=alt Devouring Plague,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,,
== Macro 3 ==
#showtooltip Shadow Word: Pain
/assist focus
/castsequence reset=alt Shadow Word: Pain,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,,
== Macro 4 ==
#showtooltip Vampiric Touch
/assist focus
/castsequence reset=alt Vampiric Touch,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,,
== Macro 5 ==
#showtooltip Mind Blast
/assist focus
/castsequence reset=alt Mind Blast,,,,, ,,,,, ,,,,, ,,,,, ,,,,, ,,,,,
== Macro 6 ==
/assist focus
/cast [nochanneling] Mind Flay
- Due to the filler effect of Mind Flay, I find that there are a whole lot of incomplete channeling of Mind Flay. If we include the [nochanneling] in the DoTs or Mind Blast, they will never get cast after the first passes. Since Mind Flay is channeling 100% after your first Mind Blast, the /castsequence wont follow through.
- Because of said issue, mana=0 quickly.
- If you spend some time to adapt the commas too your tap tap taping speed, youll have nearly 100% dot uptime and will usually use your Mind Blast CD within one second of it cooling.
Much love to the OP and those involved in smoothing this over.
if you have 3 Points in to Pain and Suffering you can modify this since you only need to put up SWP 1 time due the the 100% refresh of SWP with MFQuote:
Originally Posted by 'Ferrea',index.php?page=Thread&postID=199702#post1 99702
I really like this type of Macro
== Macro 1 ==
/click MultiBarLeftButton7
/click MultiBarLeftButton8
/click MultiBarLeftButton9
can you put modifiers in the /click such as..
/click [modifier:shift] MultiBarLeftButton7
/click [modifier:alt] MultiBarLeftButton8
/click [modifier:ctrl] MultiBarLeftButton9
*EDIT 2* OH I Really like this :D Modifiers work. Now i can set up some nice lil potions when one of my alts need it or a quick healing pot for emergencies.. or a specific spell ... Very nice :D Dis multiboxin stuff so addicting ;P
that way could put dead macros or nothing on your alts and have a specific alt to perform a specific spell like say for example Earth shock... instead of having all the alts casting ES at the same time....
But then after the next patch will be a Mooht (cow shamans cheesey jokes ftw luv em) point as ES will no longer interupt casting :(
*EDIT 1* Oh the benefit being instead of three buttons would have one with a modifier to save me from having to memorize too many key bindings :D
[align=justify][*]Damn think i just hijacked this thread and going on tangent... eeep anyways Thought be some way to modify the nifty /click macro. ;P
- All Shocks now have a default range of 25 yards, up from 20 yards.
- Base health increased by approximately 7% to correct for shamans having lower health than other classes.
- Chain Heal: Jump distance increased by 25% to 12.5 yards. In addition, the amount of healing now decreases by 40% as it jumps to each new target, instead of 50%.
- Earth Shock: Redesigned. This spell no longer interrupts spell casting, but rather reduces melee attack speed by 10% for 8 seconds (exclusive with similar effects such as Thunder Clap).
[/align]
So why doesn't this work:
What I'd expect is for the Button1 macro to fire if the next spell in the castsequence isn't on cooldown, otherwise it'd fall through to the Button2 macro instead. The intention is for Flame Shock to cast, followed by Lava Burst, and then Lightning Bolts to fill in until the Lava Burst cooldown has expired and the second one is ready.Code:"/click" macro:
/click ActionButton1
/click ActionButton2
Button1 macro:
/castsequence Flame Shock,Lava Burst,Lava Burst
Button2 macro:
/cast Lightning Bolt
I get Flame Shock, Lava Burst, one Lightning Bolt, and then nothing until Lava Burst has cooled down. Why isn't the Lightning Bolt firing more than once?
thats the same as putting them in the same macro, both are clicked at the same time and the first failed cast (/castsequence) blocks the rest of the macro from firing
that is why there are castsequences with "holes" in them in all the previous examples.
The only reason that "/click" is used with multiple castsequences is to surpass the built in character limit. Personally I use bindpad so can have multiple large castsequences in one macro.
edit: It is also used for modularization I guess, but the main reason is the small character limit.
This is absolutely beautiful and I can't thank you enough!
I'm dualboxing druids, and before, one of my druids' DPS would always be off (they're currently level 36, not RAF'd, and leveling balance). Now they're almost identical unless I try to pick a fight without enough mana (oops).
Since they're still in the leveling process, I added another step to perfect the "root 'n' nuke" sequence.
Macro 1 (main only):
Macro 2 (main and slave):Code:#showtooltip Entangling Roots
/castsequence reset=combat Entangling Roots,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Macro 3 (main and slave):Code:#showtooltip Insect Swarm
/castsequence reset=target ,,,Insect Swarm,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Macro 4 (main and slave):Code:#showtooltip Moonfire
/castsequence reset=target ,,,,,,Moonfire,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
I have ER set to reset on combat instead of target because if I'm already in combat, and something's hitting me, I might as well just nuke it down instead of trying to root and reposition (though I do have ER bound separately in case that's needed).Code:#showtooltip Wrath
/castsequence reset=target ,,,,,,,,,Starfire,Wrath,Wrath,Wrath
I'm using Starfire because it's a bit more mana efficient, and at this particular level, having both my druids use that sequence usually drops the mob before I even finish casting the first Wrath. :D
The only change I made to the main "click" macro was to add a line to /target focustarget, since I was having trouble trying to use [target=focustarget] on my slave's macros. Basically, the macros above were set to reset on combat/target, and I had [target=focustarget] in the slave's macros, but the sequence wouldn't reset for the slave even though it targeted the main's target at the start of combat... any suggestions on how to fix this would be much appreciated, as I'd like to keep my slave's target free.
Edited to add: I also used Macaroon for this, along with a macro to get the name of the frame I was moused over to get the exact button names.
I have gotten this to work and it has greatly inscreased my dps! However it doesn't seem to work with my mage ae spells. I made a macro for arcane explosion, then another for blast wave and frost instant AE( forgot the name of it). It appears like this click function only works when one spell with actual casting time in one of the macros is there to work. In this situation it just spams arcane explosion. Is there any recommendations? What I want it to do is drop either blast wave right before I drop frost instant AE/root then arcane explosion, to buy me a few extra seconds of AE damage while mobs aren't able to reach me. Any ideas?
Not sure which Frost spell you're refering to.
Cone of Cold is AoE snare, instant cast.
Frost Nova is the root spell.
If you'd post what your current macro looks like, it would help to understand why its not working and how it can be changed.
I saw someone got this to work with macaroon but how do you know what bar/button variable you need to call?
Bind this macro to a key:
/run DEFAULT_CHAT_FRAME:AddMessage(GetMouseFocus():GetN ame())
Hover your mouse over the button that you need to know the name of, press the key you've bound the macro to and the name of the button will appear in the chat window.
One more question (for now!)... Has anyone gotten click to work with FTL setup? I started to shiver a bit when I thought about that aspect. I would need to create several hotstrings (which I hate to do but might be worth it!). I did get a gear upgrade for conquest emblems and tweaked my castsequence and actually got my DPS back (but with the gear upgrade and a new weapon enchant on RET pallies) I should have even higher DPS.
I've been using this method in combination with FTL for almost a year now, what do you mean with "need to create several hotstrings"?
Maybe I am not understanding how it would work with FTL. Currently any button I need to push has it's own hostrings. So if I have a main (mash mash) button I will have hotstrings to send '2' when I hit the button '1'. Will I have to create separate buttons for each spell I need to use with /click?
If you copy and pasted that, it will not work. There is an extra space between GetName:
/run DEFAULT_CHAT_FRAME:AddMessage(GetMouseFocus():GetN ame())
This is what it should be:
/run DEFAULT_CHAT_FRAME:AddMessage(GetMouseFocus():GetN ame())
edit: that space between GetN and ame() was added after I posted it for some reason.
However, I haven't tried it since 3.2, so it might be broken.
does work in 3.2Code:/run local f = GetMouseFocus(); if f then DEFAULT_CHAT_FRAME:AddMessage(f:GetName()) end
Greetings all,
one of my chars is a Death Knight which I essentially played using a /castrandom macro to use, Scourge Strike, Blood Strike, Rune Strike, Death Coil and put up Bone Shield.
Now that Blizz has killed /castrandom this of course doesn't work. So I find myself here reading about /click.
Now I could have misunderstood but my understanding is that if I set up one macro as follows, ALL buttons would be pressed at the same time.
Mine reads:
/click ActionButton3 <-------- Button 3 = Blood Strike
/click ActionButton4 <-------- Button 4 = Scourge Strike
/click ActionButton5 <-------- Button 5 = Obliterate
/click ActionButton6 <-------- Button 6 = Death Coil
Now I run this macro every .05 seconds but the only action that triggers is Button 3. Swap around the skills and that skill triggers.
So am I totally missing the point?
My only thought is may I have and I need the /castsequence "skill" ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, AS the buttons 3 4 5 6 and the /click as the main macro sitting say in Button 1.
Would very much appreciate any help with this.
Thank you.
The "Click" functionality is essentially saying, press all of these things at once.
It is the same thing as making a macro with every spell in one line.
Normally this will work up until you have a 2nd spell which also incurs a global cooldown.
So:
/Use Icon of the Silver Crescent
/Cast Elemental Mastery
/Cast Lightning Bolt
/Cast Flame Shock
/Cast Lava Burst
This functions up until Lightning Bolt.
Anything past that point fails, because LB incurs a GCD, which FS and LvB also incur.
By having the Clicks call castsequences we get around this.
A castsequence will do one thing and then the next.
With two castsequences running at once, the first to be called runs first.
The second one tries to run, and like Flame Shock or Lava Burst fails to do anything.
However, unlike just Clicking abilities or running my above macro, they are a sequence.
Part of the sequence are comma's which function as "Nulls", which means nothing happens.
So we have click one activating the Lightning Bolt.
And nothing else happening.
Click two activates "Null" on the first sequence, which means no GCD is incurred.
This allows the second castsequence to do something. So Flame Shock will fire off.
The Lava Burst fails because Flame Shock used the GCD it needs.
The 3rd click gets a null on both the LB and FS castsequences, which allows LvB to fire off in the 3rd sequence.
Generally when you're building these sequences, you'd like to follow these steps.
Go to a target dummy, and figure out your DPS sequence.
You'll generally have several abilities you wish to use.
In your case it was Blood Strike, Scourge Strike, Obliterate and Death Coil.
I don't know exactly how a Death Knight works, having not played one since the Beta.
I do know abilities use Runic Power, which you need to have enough of to do them.
I also know an ability generally costs a rune type, and you have two of each.
So you could not do a Frost power, another Frost power and a third Frost power, until a Frost Rune refreshed.
That's about the limit of my knowledge of DK powers.
I don't know which of these powers you want incur which rune types or how much runic power they require.
To build a strong DK rotation, you'd probably want:
a) a Blood Ability.
b) a Frost Ability.
c) an Unholy Ability.
d) a 2nd Blood Ability.
e) a 2nd Frost Ability.
f) a 2nd Unholy Ability.
g) a Runic Power dump or an attack which doesn't use any rune type.
You then need to know how fast you mash your click sequence key.
Get a stopwatch or watch the clock for 15 seconds.
While watching, spam something like P or R; anything where several in a row are easy to read ( PPPP has several down strokes which are easier to count then say XXXX ).
Spam away, and then after 15 seconds count how many you typed.
Divide that by 15, and you have your clicks per second, or thereabouts.
Now you want to take your first ability.
Figure out the recast delay or how long until you'd like to cast it again.
Something like Chimera Shot for a hunter would be nice to cast often.
Something like Flame Shock for a shaman would be better to cast just as it expires.
Figure out how long after you cast it the first time, until you'd like to cast it a second time.
I personally click at 2 clicks per second.
If I'd like to do a Flame Shock every 18 seconds (12 seconds duration, but +6 seconds duration glyphed...)
In the first second I click the spell and a null, so 18 - 1 = 17 seconds of delay, plus my null.
So my first sequence is Flame Shock plus one comma plus [ 17 (my desired delay) x2 (my click speed) ] = 34 comma's.
So I go with /Castsequence reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
That's a total of 35 comma's for my click speed.
One comma for the second click in the second that the spell fires off.
34 additional clicks for the 17 seconds of delay, given my 2 clicks per second.
Now that you have your first ability done, you'll want to choose a 2nd.
Once that's done, choose a 3rd.
Repeat for as many spells/abilities as you wish to include in your sequence.
Ideally put an ability you can spam at the end for your fall through.
The "Fall Through" will trigger when all the other sequences are on a "null".
This way, you'll always be doing something if your toon can (is not waiting for a GCD).
Pretty easy to test if it clicks everything at once, or one thing after another.
Make a macro, which reads:
/Castsequence Curse of Agony
/Castsequence Corruption
/Castsequence Immolate
/Castsequence Haunt
/Castsequence Unstable Affliction
/Castsequence Shadow Bolt
Don't include any comma's in the sequences.
If all buttons are clicked at once, then the later spells should not fire.
I could see server latency possibly letting a Corruption go off, but probably not anything later in the macro.
Personally, it makes sense that it tries to do everything at once.
On click #1, the first sequence fires off.
However the 2nd and subsequent macro's fail, because the first has incurred a GCD.
We know a castsequence will not skip a spell, so these later sequences are still on the first cast.
On click #2, the first sequence is a null, which allows the second sequence to act.
Etc.
I could easily be wrong, but that makes logical sense, and seems to be true to my observations.
Hi all,
Here's my one button spam for Ret pallies:
Macro 1:
/assist focus
/startattack
/stopcasting
/click MultiBarLeftButton1
/click MultiBarLeftButton2
/click MultiBarLeftButton3
/click MultiBarLeftButton4
/click MultiBarLeftButton5
I'm using a focus setup, but you can easily change it for an FTL setup. Note you can use different click commands depending on where you are putting the other 5 macros:
ActionButton# = Main Bar
BonusActionButton# = Dynamic bar that switches actions based on Druid Forms, Warrior Stances, and Rogue Stealth
MultiBarBottomLeftButton# = Bottom Left Bar
MultiBarBottomRightButton# = Bottom Right Bar
MultiBarRightButton# = Right Bar
MultiBarLeftButton# = Right Bar 2 (to the left of "Right Bar")
PetActionButton# = Pet Bar
ShapeshiftButton# = Druid Forms, Paladin Auras, Warrior Stances, Death Knight Presences, Rogue Stealth
The /stopcasting is there for exorcism and art of war procs...since excorcism now has a cast time, if the macro is called it starts to cast it, and art of war hasn't proc'd, the next button press will stop the cast. If art of war has proc'd however, it will be instant cast and the macro will go ahead. This macro will also cast Hammer of Wrath when the mob falls below 20% health. You can sub in Flash of Light for Exorcism if you want heals instead of dps. You can also macro in Consecration if facing multiple mobs (although this tends to chew through mana).
Here are the rest of the macros that get called from the /click functions:
Macro 2:
#showtooltip
/assist focus
/castsequence reset=8/combat judgement of wisdom,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Insert whatever judgement is appropriate.
Macro 3:
#showtooltip
/assist focus
/castsequence reset=10/combat Divine Storm,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,
Macro 4:
#showtooltip
/assist focus
/castsequence reset=4/combat Crusader Strike,,,,,,,,,,,,,,,,,,,,
Macro 5:
#showtooltip
/assist focus
/castsequence reset=15/combat Exorcism,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,
Macro 6:
#showtooltip
/assist focus
/castsequence reset=6/combat Hammer of Wrath,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Note - there aren't supposed to be spaces inbetween the commas, it just 'appears' that way in my posts. ;)
I'll post my prot pally macro when I get home (at work now).
Let me know if you have any questions...
Cheers,
S.
Thanks for that one Stealthy, will play around with this tonight!
BTW, I got my /click setup pretty good and it made such a huge difference I was able to clear UK today! I also downed that crazy spit monster Erk in Gundrak yesterday. Looks like I am going to be able to start getting more emblems a day. Can't wait to finish pve gearing so I can start working on the pvp sets.
Thanks!
Do we still need /click?
I remember the reason for it originally was multiple castsequences in one macro would bug out, and not remember their positions correctly. Has this been fixed since then?
I just built a macro for my shammies based on the one Fursphere posted that involves something like this (all in one macro using macaroon):
/castsequence [harm] reset=combat/3 flame shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,
/castsequence [harm] reset=combat/3 lava burst,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence [harm] reset=combat/3 chain lightning,,,,,,,,
/cast [harm] lightning bolt; [help] lesser healing wave
This seems to work fine, without needing /clicks to call separate macros.