How will we multibox after /click ,,,,,, is removed in 4.0

[valkry]

So I actually tried out a /click macro for my 10 boxing team though I may have done it slightly wrong, not sure. I found it to be about the same dps as pressing 4-5 different buttons for a fight.

/click spell order
Shaman: FS, LvB, CL, LB
Pally: consecration, hor, holy shield, pally's shield slam, jol
Priest: vampiric touch, mind blast, devouring plague, shadow word pain (reset=target), shadow fiend, mind flay
druid: insect swarm, moonfire, wrath, starfire

I found that when the first spells had beeen cast and it came to just having lightning bolt spam while waiting for lvb and cl to get off cd there would actually be a delay between LB casts which lowers the actual dps of the macro.

Not using a /click macro I have;
4 = (flame shock, devouring plague, moonfire, HoR),
3 = (frost shock, insect swarm, sw pain, pally execute),
5 = (lvb, mind blast, starfire, pally shield slam),
1 = (chain lightning, vampiric touch, starfire, vampiric touch, taunt),
2 = (lightning bolt, mind flay, wrath, pally cast sequence macro)

The above is my order of use at the start of a fight with me not being scared to stay on 2 and mash it quite a bit as well. I find it is just about discovering which spells synch with spells from other classes.

You don't always have to run at max output, a lot of the time 90% and even 70% is fine. After all, the most important part of any raid/dungeon is to stay out of the bloody fire.

[moosejaw]

For Khat, I think BindPad may still be a macro option in 4.0 live.

Click isn't going away, correct? Only the pause effect of multiple comma's. I would be very disappointed if my /click smartbuff_button went away as well as my eat/drink /click's.

No quiting threats from me. I just want to be viable in 5-mans, thats it. I am the only one that will complain about my low dps. I don't give a crap about dps as long as sh!t dies.

[Khatovar]

From what I saw when I tested /click, the actual /click part still works, but it only ever will hit the first button in the action. So a macro with one /click action, like

/jamba-team invite
/click [nomounted] SmartBuff_KeyButton
/jamba-follow strobeoff all

Should work, but one with multiple /click actions like

/click [target=vehicle,exists] VehicleMenuBarActionButton1
/click [target=vehicle,exists] VehicleMenuBarActionButton2
/click [target=vehicle,exists] VehicleMenuBarActionButton3

was only ever hitting the first one. But I didn't get to test too much since there was like 300 people at the dummies and it was like the 4th of July going off in my face.

[ElectronDF]

Then a question might be if only one /click per macro, what about one /click in multiple macros. What if the first macro does a /click on macro 2, then macro 2 does a /click on macro 3? Does that get around at least the one /click part?

[Zub]

seems like it's changing every day.
i think i'll wait for the rollout before starting to think on it ;-)

[suicidesspyder]

Well tbh i lo0ved click but castseq is fine for me. Ive tried with a pally tank shaman healer druid mage shadow priest yea dps was lacking but now with the new jamba its easy. Im lazy to set up a modifier cause i might get confused whos who in the heat of the battle am i right.

But with jamba proc you can set it so each toon has their spam this key right for dps. Then if they proc they have their own button on th action bar they can spam while your spamming dps on the rest. You could do this for all.

Just a thought with click being a no go anymore. I see the only thing that will hurt is if they find a way to get rid of the mouse repeater regions that isboxer uses. To me that makes healing effortless and easy.

[confusedtx5]

Using a couple of ISboxer 'step' functions, a couple of bar buttons and some castsequence null macros it should be possible to get reasonably good dps.
Should that fail, I might have to experiment with 1 button for dots and 1 for nuke/filler spells. With the oceanic latency I run, castsequences have about half a second per cast of dps loss.

As someone else posted earlier, I'm still under the impression that automation is 1 button press to more than 1 action. Going by 1 button press to 1 action, using isboxer steps to determine the order of buttons getting pressed might be ok.

[naPS]

Using a couple of ISboxer 'step' functions, a couple of bar buttons and some castsequence null macros it should be possible to get reasonably good dps.

Yeah, this is exactly what I was thinking. There's effectively no difference in stepping through a castsequence using ISBoxer steps or steps in a macro. It's still 1 button press, 1 action.

However, the only real reason to use the different /click's was to insert the delays possible by using commas. Now that we're losing that functionality, I'm having a difficult time coming up with a reason to even use the /click function. I've almost completed switching all my toons over to a straight /castsequence macro that's getting me very close to the performance I was getting with /click macros.

Gotta love the arcane mages, they couldn't be easier. Warlocks aren't horrible. And, I'm pretty sure I've got the boomkins down as well. Tanking /castsequences are simple as hell, and healing is pretty simple as well. I'm sure we'll all get this sorted once the 4.0.1 patch drops.

[Kalyse]

But with jamba proc you can set it so each toon has their spam this key right for dps. Then if they proc they have their own button on th action bar they can spam while your spamming dps on the rest. You could do this for all.

.

I think I will be using Healbot for this with repeater regions.
When I need to force a particular spell to one of my toons, I will run a macro... I just need to find an efficient way to make sure that the spell gets cast.

What do you guys thing of this solution? Healbot for DPS. Only for the individual procs mind you.

[franco]

I tried yesterday to replace my mage /click macros with castsequence, macro itself seems to work just fine, but I'm losing about 1000 DPS.

I believe that the difference is because of lag and the fact rgar castsequence waits for previous spell to finish before doing the next, where as /click will do the spells "faster"

macro I was using is something like:

/stopmacro [channeling]
/use 13
/use 14
/cast icy veins
/cast arcane power
/cast presence of mind
/castsequence [] Arcane Blast,Arcane Blast,Arcane Blast,Arcane Blast,arcane missiles

I was trying to search another way to avoid the lag issue with castsequence, but /click seemed to be the prefered fix :-/

--franco