Startattack, stopcasting and castsequence in WotLK: when to use (and when to avoid)

Three commands, three different functions

In WotLK, a lot of macro breaks because players treatstartattack, stopcasting e castsequenceas if they were equivalent. They are not.

Each one solves a different problem:

• startattack: ensure active auto attack
• stopcasting: interrupt current cast for urgent response
• castsequence: follow fixed sequence of skills

When used in the wrong context, all three become a source of performance loss.

---

Startattack: simple and efficient

When to use

• melee in frequent target switching
• hunter to not miss auto shot/auto attack
• content opener with quick pull

Example

#showtooltip Sinister Strike
/startattack
/cast Sinister Strike

When to avoid

• in macros that can activate an attack without you wanting it (controlled CC situation)
• when the skill already guarantees flow without risk of delay

---

Stopcasting: emergency button

When to use

• critical interrupt
• Urgent CC
• defensive cooldown that needs to come off now

Example

#showtooltip Counterspell
/stopcasting
/cast Counterspell

When to avoid

• in standard rotation skills
• in every macro of a bar
• when the reaction gain is less than the current cast loss

stopcastingToo much is one of the biggest reasons for inconsistent DPS/HPS.

---

Castsequence: useful but limited

When to use

• very stable and predictable sequence
• simple preparation routine
• controlled and repetitive context

Example

#showtooltip
/castsequence reset=target Serpent Sting, Steady Shot, Steady Shot

When to avoid

• dynamic rotation with proc
• fights with constant priority switching
• classes that require adaptive decision by GCD

Castsequence doesn't think for you. If the fight goes off script, it holds you back.

---

How to combine without breaking execution

Healthy combination

• startattackin basic pressure skills
• stopcastingonly in critical utility
• castsequencein punctual and tested use

Dangerous combination

• put all three in the same main macro
• use castsequence to simulate entire rotation
• spread stopcasting by reflex, without need

---

Examples per profile

Melee PvE

Usestartattackin the core of the bar. Avoidcastsequencein quick decision rotation.

Caster PvP

Usestopcastingfor interrupt and decisive CC. Do not use it on common damage spells.

Healer

Usestopcastingonly in real emergencies. Prioritize mouseover/focus for clean reaction.

Hunter

startattackIt helps a lot with opening consistency.castsequencerequires care not to block priority.

---

Quick matrix: use or avoid

Startattack

• use: almost always for melee/hunter
• avoid: when it may break target control in a sensitive situation

Stopcasting

• use: high impact emergency
• avoid: normal rotation and widespread spam

Castsequence

• use: predictable and short context
• avoid: dynamic combat and competitive content

---

Testing routine before serious content

1. macro test on training target or light content
2. Validate behavior with target switching
3. Validate behavior in motion
4. Review fluidity logs/feeling
5. simplify if stuck

If the macro requires more attention than the normal button, it is poorly designed.

---

Final checklist

Before consolidating the macro:

• do I know why this command is here?
• does it solve a real problem?
• does it improve my execution in practice?
• does it continue to work outside of the ideal scenario?
• is there a simpler alternative?

In the end, the best macro is the one that reduces friction without robbing you of your decision-making ability.