reset= combar or target or both?

[zenga]

I currently use combat=reset in my shammy click macro's. This has served me very well in most HC's. Using reset=target has a negative influence on my dps during the 60-100k hp trash mobs. However against the 200-300k hp mobs in icc instances reset combat means that flameshock is often not on the next mob while it's off the cooldown. Having a modifier could do the trick, but i'm not sure what the best practice is or what the other boxers are using?

I've seen reset=combat/target but unsure about the priority here either.

Any advice?

edit: ouch typo in title but can't fix that :)

[Maxion]

Should be able to fix the title if you go into advanced editing mode.

Anyway, modifier, or switching to a macro that also resets with target in icc would work. Problem with recasting a spell with a cooldown whenever you switch target is that it can get stuck if it is still on cooldown.

Personally I just made my macro recast flame shock every other lava burst, and the overall result was good enough for me to save the hassle of setting something better up. (granted, i'm not using /click atm)
But reset=target only works if the toon in question is actually assisting the main on each target instead of just casting on focustarget. (I like to keep my targets clean / open for use with cc targeting.)

[Ualaa]

I'd go with reset=combat, for the Flame Shock.

Because, it has a fixed cooldown (even if its relatively quick), which can cause the macro or click sequence to get stuck until the spell is able to cast.

Something like Moonfire/Insect Swarm or Corruption/Immolate/Agony or the like, can be spammed over and over, as often as you'd like until you run out of mana.

But any spell with a cooldown, can get stuck and unable to cast until the cooldown ends. And that means nothing happens with the dps, until the spell goes off.

[howster]

I have reset=combat/27 for flame shock. This will reset my macro when I need to reapply flameshock (27 sec from t9 set bonus and glyph). This works quite well for me.

[Ughmahedhurtz]

I use combat/target only for my hunters and druids as they're on such short cooldown spells (stings and faerie fire). For your shams, I'd probably set up two buttons/macros; one for weak trash (no target reset) and one for bosses or ICC+ trash (with target reset). Or just flip your binding back and forth as needed between the two macros.

[zenga]

Allright but how works target/combat out? As in how it behaves and what prioroty.

Assume my macro is of this format (without tuned comma's obv)

/castsequence reset=combat flame shock ...
/castsequence reset=combat lava burst ...
/castsequence reset=combat chain lightening ...
/cast light bolt

The macro would just continue when switching targets.

If i was to replace flame shock with reset=target the macro would start over (as it's in the first line) and try to cast flameshock, and then proceed where it was with lava burst, if all are on cooldown it just casts light bolt. Is that correct? I.e. reset=target in 1 castsequence does not affect the 'loop' of other castsequences?

Now what would reset=combat/target do when just applying that to flameshock (just for the theory, i would reset my other sequences as well).

[Ughmahedhurtz]

If i was to replace flame shock with reset=target the macro would start over (as it's in the first line) and try to cast flameshock, and then proceed where it was with lava burst, if all are on cooldown it just casts light bolt. Is that correct? I.e. reset=target in 1 castsequence does not affect the 'loop' of other castsequences?
Basically, yes, except that if you switched targets before the Flameshock cooldown was up, it would hang on that and not cast anything until flameshock went off.


Now what would reset=combat/target do when just applying that to flameshock (just for the theory, i would reset my other sequences as well).Well, reset=combat/target is redundant. You will almost always change targets when you drop combat assuming you are targeting the enemy, so just reset=target should be sufficient.

[Ualaa]

If i was to replace flame shock with reset=target the macro would start over (as it's in the first line) and try to cast flameshock, and then proceed where it was with lava burst, if all are on cooldown it just casts light bolt. Is that correct? I.e. reset=target in 1 castsequence does not affect the 'loop' of other castsequences?

Unfortunately, it is not correct.
Flame Shock (or any shock) can only be used once every 6 seconds, unless you talent it.

If you were to switch to a new target, immediately after having cast a Flame Shock on the initial target.
And you had reset=target (or reset=target/combat, which resets on either condition)...
Then Flame Shock is the next spell to cast, but is on cooldown.
So the entire macro locks up, until you can cast it.
Meaning, no matter how you spam the macro, nothing is cast until the Flame Shock comes off of cooldown.

[zenga]

So basically a clickmacro is on lock until the first castsequence is executed i.e. it does not jump to a 2nd castsequence or the last cast that is available at that time when the first is on cooldown.

That's clear. Thanks.

[Ualaa]

If the first/earlier castsequences successfully execute.
And you are on the comma's of the castsequence.

Then the next spell can activate fine.
But when you're on a spell and that spell cannot execute, nothing after it fires up either.

[RobinGBrown]

My general rule is:

cooldown less than 3 seconds? use reset=target/combat
cooldown less than 6 seconds? use reset=target/combat/6
cooldown more than 6 seconds? use reset=combat

I make the final decision based on other spells in the sequence

Note that I don't use clicksequences or single button spamming either and often run mixed groups - so I customise the macros based on group makeup, target type, etc.

[Dorffo]

for my click macro I have it set to reset=combat/3 with a modifier on the flameshock macro like so:


#showtooltip flame shock
/cast [mod] flame shock
/castsequence reset=combat/3 flame shock , , , , , , ,, , , , , ,, , , , , ,, , , , , , , , , , , ,, , , , , , ,, , , , ,, , , , ,, , , ,

^^ not a cut and paste so the commas aren't counted out