Super macro delay... Why?

[Tybudd]

Problem:

My slave toon, at times Hesitates to assist my main toon, making me lose alot of dps especially as a dps priest, some times the mob will be at around 80% b4 my slave gets off his first cast.

At times he (Master toon is a rogue) will target my target, but if I haven't actually attacked the mob, and have only targeted it, he won't attack until I actually get in melee range and engage, even though all my rogues abilities are macroed to /startattack.
At times my rogue will get another target after a mob has died, and my priest will just stay targeting the dead mob that i'm not even targeting anymore.
Here is my Slave's (priest) set up. Its a 1 button spammer!!

Macro button 1
/cast [nostance] Shadowform
/assist [@focus,help,nodead]
/click MultiBarLeftButton1
/click MultiBarLeftButton2
/click MultiBarLeftButton3
/click MultiBarLeftButton4
/click MultiBarLeftButton5

Click buttons
Multibar 1
#showtooltip Devouring Plague
/castsequence [harm] [target=targettarget,harm] reset=target/combat Devouring Plague,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,

Multibar 2
#showtooltip Shadow Word: Pain
/castsequence [harm] [target=targettarget,harm] reset=target/combat Shadow Word: Pain,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Multibar 3
#showtooltip Vampiric Touch
/castsequence [harm] [target=targettarget,harm] reset=target/combat Vampiric Touch,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Multibar 4
#showtooltip Mind Blast
/castsequence [harm] [target=targettarget,harm] reset=target/combat Mind Blast,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Multibar 5
#showtooltip Mind Flay
/castsequence [harm] [target=targettarget,harm] reset=target/combat Mind Flay,,,,,,,,,,,,,,,,,


Now I think my problem is in the Macro button 1, can u see what teh problem is guys, I spent days thinking I perfected this macro set up, and it is more than frustrating to see something is failing. Don't get me wrong on boss fights the 3500 GS priest can reach 4k dps with this macro setup, so when it doesn't have to retarget its great, but I'v failed the targeting some way or another.

BTW i'm Using Keyclone for software, and Jamba Addon

[Solon]

I would try ditching the assist and change the dual conditionals from [harm] [target=targettarget,harm] to [@focustarget,harm][@targettarget,harm] and see if that helps speed it up. If that does make a difference then you may have to rethink your targetting style, assist has always felt slower to me.
At least changing to [harm,nodead] should reduce the stuck targetting a dead mob. We would have to see your main's macro to know what his problems are too, it could be a combination of the two sets.

[defster]

You're using an awful lot of condition tags, and your target= command will override the assist command, making it redundant. Not sure if the error lies there though, but still worth a mention. :)

Anyway, try to use only /assist <name of rogue> without modifiers, then add a simple /stopmacro [noharm] before all your clickies. Using this, you can remove all the [harm] and [target=] conditions in your individual click macros, making it much cleaner and easier to debug.

/cast [nostance] Shadowform
/assist <rogue>
/stopmacro [noharm]
/click MultiBarLeftButton1
etc.

#1
#showtooltip
/castsequence reset=target/combat Devouring Plague,,,,,,,,,,,,,

and so on. I dont use focus myself, so maybe i'm missing the bigger picture here.

[Tybudd]

You're using an awful lot of condition tags, and your target= command will override the assist command, making it redundant. Not sure if the error lies there though, but still worth a mention. :)

Anyway, try to use only /assist <name of rogue> without modifiers, then add a simple /stopmacro [noharm] before all your clickies. Using this, you can remove all the [harm] and [target=] conditions in your individual click macros, making it much cleaner and easier to debug.

/cast [nostance] Shadowform
/assist <rogue>
/stopmacro [noharm]
/click MultiBarLeftButton1
etc.

#1
#showtooltip
/castsequence reset=target/combat Devouring Plague,,,,,,,,,,,,,

and so on. I dont use focus myself, so maybe i'm missing the bigger picture here.

Ah, I see what you are saying, the only problem I might have there is if my rogue dies, and I have to use my slave as my new master. U understand what I mean, that was why I added the [harm] brackets. I do see where the [target=] brackets are a bit much. especially if im /assisting. But how would I get around the issue with my master dying if I made this change?

[Starbuck_Jones]

assist is a little flaky. I dont quite have the problems you are stating but every once in a while my slaves will get stuck targeting a dead mob that I looted or something. No amount of /assist or spam will get them to target the mob thats beating on the tank. I have to esc out and clear the target before it will work properly.

Personally I think this is an issue with using /focus. If I use my tanks name instead of making him the focus I don't have this problem.

[defster]

Still dont see why you need [harm] :) Harmful spells wont be cast on friendly targets no matter, so it's just not needed in a dps castsequence.

If your rogue is dead, you can still pick targets with him, and the priest will aquire them through /assist. I've survived many bad pulls by controlling my dps from my tanks screen while he eats dirt.

Or do you mean that you want to change to your priests screen and control him directly when if your rogue dies? If your dead rogue has no target (it should be reset when he dies), the /assist line will just be ignored, and your priest can pick his own targets. In any case, a [nodead] in the assist line could be useful, in case you've accidently selected a target on your dead rogue :)

[Solon]

I like [harm] to keep my toons from casting on a neutral target.

[Maxion]

I like [harm] to keep my toons from casting on a neutral target.

Does it actually do that?

[alcattle]

Does it actually do that?
Yes you can hit yellow targets, which is not wanted some times.

[Tybudd]

Still dont see why you need [harm] :) Harmful spells wont be cast on friendly targets no matter, so it's just not needed in a dps castsequence.

If your rogue is dead, you can still pick targets with him, and the priest will aquire them through /assist. I've survived many bad pulls by controlling my dps from my tanks screen while he eats dirt.

Or do you mean that you want to change to your priests screen and control him directly when if your rogue dies? If your dead rogue has no target (it should be reset when he dies), the /assist line will just be ignored, and your priest can pick his own targets. In any case, a [nodead] in the assist line could be useful, in case you've accidently selected a target on your dead rogue :)

OK, i'm going to give this a shot, but yes, for teh other comment the it doesn't cast on neutrals, until your main attacks and takes them out of neutral.

BTW the way you had me set up my master click button helped as well, for some reason, the way I had it at times, if I targeted and mind Sear, it would start the sear on a group to the side that I wasn't ready to even aggro.

[Maxion]

Yes you can hit yellow targets, which is not wanted some times.

I meant if it prevents casting on yellow targets.

[jimbobobb]

Isn't this par for the course when using an /assist macro?

First you have to wait for your comp to send the new target on your main, then the slave'srequest for the /assist target's target to the server, then it has to come back, etc etc - so your delay should be 1.5 times (about) your latency.

This has always been the case with my group. I usually switch targets when something is around 10-20% depending, that way they switch just about right.

Fear and targetting dead mobs can really mess with /assist - just esc and clear out your target and reaquire - not much to do about that.

[Maxion]

Isn't this par for the course when using an /assist macro?

First you have to wait for your comp to send the new target on your main, then the slave'srequest for the /assist target's target to the server, then it has to come back, etc etc - so your delay should be 1.5 times (about) your latency.

This has always been the case with my group. I usually switch targets when something is around 10-20% depending, that way they switch just about right.

Fear and targetting dead mobs can really mess with /assist - just esc and clear out your target and reaquire - not much to do about that.

Indeed.