Stop Cast

[Malevicton]

It lets you hit procs and clip your cast times, in the case of a macro command, a TON more efficiently than by stutter stepping too. It basically allows you to add a built in, effortless stutter step to every ability.

In the case of Straighter Shot and Firestarter you don't wanna interrupt your ability to get them off. Even well timed it's a dps loss.

How is it a stutterstep if it breaks your cast? Stutterstepping is about not breaking your casts. If you stop casting that doesn't "clip" that would just straight up cancel your cast.

[MrCookTM]

In the case of Straighter Shot and Firestarter you don't wanna interrupt your ability to get them off. Even well timed it's a dps loss.

How is it a stutterstep if it breaks your cast? Stutterstepping is about not breaking your casts. If you stop casting that doesn't "clip" that would just straight up cancel your cast.

Pretty much this. There is not a single instance where the use of a 'stopcast' macro will not result in a dps loss.

[Shirobi]

Pretty much this. There is not a single instance where the use of a 'stopcast' macro will not result in a dps loss.

Bard with WM would benefit by no longer having to delay hitting a proc, and in doing so may gain a proc they would otherwise have lost, all more efficiently than by hitting a cancel button or moving. Its like Prya said, it would allow you to effective cut out a lot of the penalty of WM and play bard much more like it originally played.

[MrCookTM]

Bard with WM would benefit by no longer having to delay hitting a proc, and in doing so may gain a proc they would otherwise have lost, all more efficiently than by hitting a cancel button or moving. Its like Prya said, it would allow you to effective cut out a lot of the penalty of WM and play bard much more like it originally played.

But... cancelling a weaponskill in order to cast a proc is a dps loss... o.O

Also, no, the way it is now, you don't lose potential procs, since you can only get one proc every 3 seconds/server tick.

[Shirobi]

But... cancelling a weaponskill in order to cast a proc is a dps loss... o.O

Also, no, the way it is now, you don't lose potential procs, since you can only get one proc every 3 seconds/server tick.

Not for bard. You can easily get two procs back to back. If you could stop a hard cast, fire off a proc then go right back into hardcasting, its not gonna be a dps loss. Not to sound like a broke record, but since I keep getting the same replies, look at how things worked in 2.3 or earlier WoW. Thats the same system we have going here, and there is a reason people used stopcast and addons to give them a view of when the cast had areached the "point of no return" as it were so they could stop cast and begin another one.

[Lyrica_Ashtine]

It allows you to quickly start casting another ability without waiting for a prior cast to finish. Example: I'm casting Stone II on my white mage. Suddenly, the tank gets hit with a big attack because he didn't dodge far enough. I could stopcast the Stone II and start casting a Cure II on the tank, getting the healing spell to the tank around two seconds faster.

You're using the wrong comparison, though. Healers switch from one priority to another: From maiming to mending. In case of Bards and Machinists, they don't switch at all. They just create an unnecessary pause between their attacks to cancel their attack in favor for another.

Not to sound like a broke record, but since I keep getting the same replies, look at how things worked in 2.3 or earlier WoW.

Have you read my previous post about this?

[Kacho_Nacho]

You're using the wrong comparison, though. Healers switch from one priority to another: From maiming to mending. In case of Bards and Machinists, they don't switch at all. They just create an unnecessary pause between their attacks to cancel their attack in favor for another.

I stand corrected.

[MrCookTM]

Not for bard. You can easily get two procs back to back. If you could stop a hard cast, fire off a proc then go right back into hardcasting, its not gonna be a dps loss. Not to sound like a broke record, but since I keep getting the same replies, look at how things worked in 2.3 or earlier WoW. Thats the same system we have going here, and there is a reason people used stopcast and addons to give them a view of when the cast had areached the "point of no return" as it were so they could stop cast and begin another one.

No, you just can't. BL can reset every 3 seconds at most, this has been the case since 2.0 and there is no room for argument here tbh.

And cancelling a WS in order to use proc IS a dps loss, the math for this has been done as early as Brd got minuet. If you still disagree, you might want to have a discussion with some of the in depth theorycrafters for the class like Krietor or Aurily.

[Tsilyi]

Not for bard. You can easily get two procs back to back. If you could stop a hard cast, fire off a proc then go right back into hardcasting, its not gonna be a dps loss. Not to sound like a broke record, but since I keep getting the same replies, look at how things worked in 2.3 or earlier WoW. Thats the same system we have going here, and there is a reason people used stopcast and addons to give them a view of when the cast had areached the "point of no return" as it were so they could stop cast and begin another one.

Even for bard, the chances of you getting a back to back proc is extremely rare. When you do, if you stopcast macro assuming it exists, to hit your BL proc and it procs again, the mental recognition time to realize you have gotten a proc while your next ability is casting, interrupt it and then recognize the second proc and hit it again would delay your next on-gcd attack anyway, resulting in a loss.

In wow, no good dps player interrupted casts for procs unless it was something that would refresh a very, very important buff. Every guide I ever read and every advice I ever got from stellar players in that game was if you have started a cast and didn't notice your proc, or if a proc happened in the middle of your cast, just let the cast finish. Stopcast macros were basically used for CS/shear or other ranged interrupts. That I could see being useful, a stopcast macro for say head graze/blunt arrow. Don't use a stopcast for procs.

[Shirobi]

In the case of Straighter Shot and Firestarter you don't wanna interrupt your ability to get them off. Even well timed it's a dps loss.

How is it a stutterstep if it breaks your cast? Stutterstepping is about not breaking your casts. If you stop casting that doesn't "clip" that would just straight up cancel your cast.

Stutterstepping is about moving before your finished going through the full cast / animation sequences as soon as your ability has been registered as cast by the server. In FFXIV, much like pre 2.3 WoW, there is an amount of time between the server actually registering your cast and when you can move. Same way you can cast a spell and then start moving and still have that spell go off if you time it right. Stopcast would just make it easier by eliminating the need to move. Do you see what we're talking about now?

FFXI had this as well, wherein a blm could begin casting a spell and, if they timed it right, cancel out and already be moving or readying another spell while the first one is still casting.

If you are dealing with a game that doesnt track casts and movement in real time like 14, 11, or old pre 2.3 WoW, stopcast lets you game the system. Or least it makes it much easier to.