Interrupts help

[muffin man]

hay i need some help with Interrupts spells been trying to get them work in a order

	{ "Storm Bolt", {
	"!target.state.silence",
	"!target.immune.melee",
	"!target.immune.silence",
	"!target.state.stun",
	"target.interruptAt(50)",
	"modifier.interrupts" 
	}},	
	{ "Pummel", {
	"!target.immune.melee",
	"!target.immune.silence",
	"!target.state.stun",
	"target.interruptAt(50)",
	"player.spell(Storm Bolt).cooldown < 25",
	"modifier.interrupts" 
  }},
	{ "Arcane Torrent",{ 
   "player.spell(Arcane Torrent).exists",
	"!target.immune.melee",
	"!target.immune.silence",
	"target.interruptAt(50)",
	--"player.spell(Storm Bolt).cooldown = 0",
	--"player.spell(6552).cooldown = 0",
    "modifier.interrupts",
	"target.range < 7"
	}},

I had this working back when warriors had Disruption shout. I don't know if I'm doing this wrong but the condition "player.sell(storm bolt).cooldown " doesn't seem to be working, I'v tried different variations but I still can not get this to work anymore.

can anyone help ?

[akeon1]

I am not sure why you need that at all.

If stormbolt is on cool down, PE will naturally proceed to the next spell.

[muffin man]

i need this to interrupt spells?, kinda why i need it . PE cast all of them at the same time, before back in patch 5.4 it work flawlessly. now i can't not get it to work again, any useful input?

[akeon1]

I got the fact you want to interrupt spells. That much was clear. But in order to help you, I need to understand the issue you face.


PE casts top to bottom. So if you have:
Storm Bolt
Pummel
Arcane Torrent
It will cast those, one at a time and in that order as the spells become available.. (without conditions).

The only time you should see things appear like they happen at the same time is if they are not on the GCD table.

So in the scenario, I target you, and you are casting frostbolt @ 50% Storm Bolt will fire.
Then next cast you do would be interrupted by pummel As stormbolt is on cool down and pummel is next in order with an interruptat condition..

Try it without all the !target.silence and stun extras. They are pointless and just confuse the rotation, if the target is silenced, it won't be casting... So no point adding it in as a condition.

I have not checked as it's not really needed but you could also use a target.casting function.

If you need more in depth help I suggest you come on the irc where we can help further