Help with mind flay in cast sequence macro please!

The channeling thing is only needed if you plan to spam the button. If you do plan to spam it, I'd suggest a separate flay macro for that.

Quote:

---

Originally Posted by 'Djarid',index.php?page=Thread&postID=58485#post58 485

[target=retitan-target,nochannelling:Mind Flay]

---

Ohhh, I didn't know you could use a char name in the condition like that. That's going to simplify a lot of my macros, since I only 2-box.
Thank you!

Thanks Djarid, i'll try that out. I dont really pvp much with these guys as a group, only in av if its av weekend.

Could it not be resetting because it is still in the middle of a channeled mind flay and not noticed that my main has changed targets. But that would not explain the fact that it is not resetting out of combat either.

I use buttons 1-4 all with the same cast sequence macro for my dps, and then i actually play my paladin tank normally, with 1-4 being judgement, sor, holy shield, consc. So i cannot really have a new mind flay as i am spamming different buttons depending on what cooldown i propose to sue next.

re mid-channeling: Perhaps but as soon as the channeling had finished it should have reset the sequence.

don't mean to patronise but you were allowing for target switch delay weren't you?

Yes i'm aware of switch delay. After it does switch from target A to B, it continues with the cast sequence rather than starting from the start of the sequence.

I experienced this last night first hand... freaky

Code:

---

/castsequence [target=focustarget] reset=target Curse of Agony, Corruption

---

This is a bog standard cast sequence, nothing fancy in it

here is what wowwiki.com has to say on the syntax of castsequence

Quote:

---

Code:

---

/castsequence reset=target Immolate, Corruption, Curse of Agony, Siphon Life
\___________/ \____________________________________________________/
              |                                        |
  command                                        parameters

---

Code:

---

/command [conditions] [more conditions] parameters; [conditions] parameters ...

---

---

so clearly the reset is in the correct position (I have loads of cast sequences and this is the only one not working)

how it fails.

1. target mob1
2. fire macro (curse of agony)
3. target mob2
4. fire macro (corruption)

that 2nd one should have been CoA again.

I wonder if the reset is being driven from the actual target the character has selected instead of the target specified in the sequence in which case it is a bug/feature introduced in 2.4 and could shaft a lot of us.

Anyone else experiencing problems

The "reset=target" only works if you /assist focus or physically retarget mobs. I don't think it works if you're using the target=focustarget or similar non-target targeting (if you'll forgive the mangled phrase :P). At least, this has been my experience, much like yours, Djarid. Mine is /assist focus based and doesn't have that problem. My experience previously was as follows:

Legend = (current target of my alt) command and context

1. Focus has target of mob A
2. (notarget) assist focus
   1. BEGIN: /castsequence [target=focustarget] reset=combat/target/10 immolate, corruption, curse of agony, incinerate, incinerate, incinerate, incinerate
3. (mob A) immolate
4. (mob A) corruption
5. (mob A) CoAgony
6. --- focus retargets mob B and I press /assist focus key ---
7. (mob B) immolate
8. (mob B) corruption
9. (mob B) CoAgony
10. (mob B) Incinerate
11. --- focus targets mob C and I press /assist focus key ---
12. (mob C) immolate
13. (mob C) corruption
14. --- focus targets mob D but I do not press my /assist focus key ---
15. (mob C) CoAgony on mob D
16. (mob C) incinerate on mob D
17. (mob C) incinerate on mob D
18. etc.

Now, at one point, the macro would forevermore reset to step one when using [target=focustarget] but I think that was fixed in 2.1 or maybe it was fixed on teh PTR pre-2.0...

Others can correct me if this works differently as I've not used a [target=focustarget] macro in many, many moons.

Thanks Ugh (or do you prefer umhh? ;) )

I sort of figured as much... but it seems like it is a bug rather than an intentional feature... why else allow options on cast sequence?

Just need to find out how to report bugs

Sorry for the bump of an old thread, but wanted to post this in case it might help someone eles.

I removed "combat" from my reset (now "reset=target/24") and now the macro resets for me when I intend it too.
With "combat" still in like "reset=target/combat/24" It never reset for me, even after the time was up.

Oh my god ....
I started with 63 and Mana Tombs tonight and finally swapped my second mage with my shadow priest and had to set up a macro for him since my elemental shaman and ice mage were played completely different without macros.

Code:

---

/castsequence [nochanneling:Mind Flay] reset=34 Vampiric Embrace, Shadow Word: Pain, Vampiric Touch, Mind Blast,  Mind Flay, Mind Flay, Mind Blast, Mind Flay, Mind Flay, Mind Blast, Vampiric Touch, Mind Flay, Mind Blast

---

Despite the fact that the sequence itself may be crap .... this doesn't matter. What matter is that adding target or combat or both totally screw up the complete macro ->

Code:

---

... reset=target/34 ...

---

or

Code:

---

... reset=34/target ...

---

or

Code:

---

... reset=combat/target/34 ...

---

or

Code:

---

... reset=target/34/combat ...

---

From a perfectly working sequence with reset=34 I come to a mentally challenged macro which "spams" Vampiric Embrace with adding target or combat.
-> Vampiric Embrace, *spamming the button*, I see the cooldown run down and the message like "can't cast that spell now", *spamming the button*, the cooldown runs out, Vampiric Embrace, *spamming the button*, I see the cooldown .....

Removing the reset-condition and just leaving the time of 34 seconds in my case helps.

So did anybody figure out why this is like it is?

Xorn