WoW 2.0 macro design intent

Q u o t e:

Old macro, won't work in 2.0:
/cast Shield Slam
/cast Sunder Armor

New macro, will work in 2.0:
/castsequence Shield Slam, Sunder Armor

A different macro, will work in 2.0:
/cast [stealth] Ambush
/castsequence [nostealth] reset=target/combat Sinister Strike, Sinister Strike, Eviscerate

Q u o t e:

Question by Kenco:
How can you say one kind of automation is fine and one kind of automation is not?

Normally I don't respond to these, but I think I understand the design intent fairly well now.
The difference is one macro is using the state of the game to dictate what spell to cast, and the other macro is using the state of your input to dictate what spell to cast. The difference is subtle, but important. It means that as a player, if something dynamically changes in the world, you are responding to it, not the macro. For example, if one of my sinister strikes is dodged, I have to make a decision whether I want to continue the sequence or whether I want to get an additional sinister strike in before I eviscerate. Which choice I make is highly dependent upon who I'm fighting with, how close I am to finishing off the opponent, etc. etc.

Q u o t e:
/castsequence?

Does this cast one thing on first button press then the next thing on the second buttonpress? If so i love you slouk.

That's exactly what it does. :)

Q u o t e:
these changes dont affect spells that dont trigger the global cooldown right?

such as PoM, NS, Judgement, etc?

Right.

I agree, visual feedback would be very helpful. I'll see what I can do.

The macro is reset as soon as the target changes.

Q u o t e:


How about this macro: (excuse the butchered syntax)
/cleartarget
/target Ouro
/stopmacro[notarget]
/cast Intercept

Is this not using the state of the game to dictate whether to cast Intercept?

Yes, but it's not (generally) dynamically changing state.

Thanks. :)