Stop Cast

[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.

[Lyrica_Ashtine]

I'm still confused why you'd want to purposely cancel a cast so you can cast something else. But if you want a single button press to "stop" a cast, try pressing escape (or whatever button it is for console players). This forcefully stops your current cast as long it's within the range where it can be interrupted.

As for losing procs as a bard, there are actually intervals for river of blood between each procs. You could easily finish your current cast to use whatever proc you have after that aside from Straight Shot.

Even if you consider the chances of losing procs:
River of Blood has a 2x 10% chance to proc, assuming 20% crit rate
Straighter shot 20% chance to proc

Odds are much higher that you don't get a proc in comparison to wasting a proc. Where in most casts you may interrupt your cast for a proc and don't get a proc after your next cast; You simply lose GCD time like this.

It's a bit more complicated for Machinist where reaction speed's a much bigger factor

[RiceisNice]

As for losing procs as a bard, there are actually intervals for river of blood between each procs. You could easily finish your current cast to use whatever proc you have after that aside from Straight Shot.

It's a bit more complicated for Machinist where reaction speed's a much bigger factor

Just to add clarification; Bloodletter can still overlap if you're multi-dotting. While it's not a problem on it's own (multi-dotting or not), it does become a problem when you have a cast time on top of reseting oGCDs, as well as the entirety of the moveset which also includes an oGCD with cast time.

On MCH, it's entirely on their reaction time. If you ever have to stop cast because you got a proc, that's your own fault (or latency, but that's an outside factor that should never be considered).

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.

It actually is a dps loss since you're delaying the use of your weapon skill by half a GCD if you have to cancel it. Getting back to back procs is more of an annoyance which still shouldn't exist due to the circumstances (until you actually hit SS the same time you get the proc, which is a different issue all together)

While it's nice to have some more expansive macros (including stopacst, other features like cancelaura or casting AoE on your cursor without a recitle), I don't think it'll help that much due to the gameflow of FFXIV (and the less-than-ideal serverside-detection)

[Shirobi]

It actually is a dps loss since you're delaying the use of your weapon skill by half a GCD if you have to cancel it.

AN in exchange for that half a gcd you're gaining another shot fired. its just not gonna be a dps loss. Its not like that half a GCD just passes without getting anything out of it. You're still gaining a shot fired.

[Lyrica_Ashtine]

AN in exchange for that half a gcd you're gaining another shot fired. its just not gonna be a dps loss. Its not like that half a GCD just passes without getting anything out of it. You're still gaining a shot fired.

You don't seem to comprehend why it's a DPS loss for wasting a GCD. Canceling a cast in general means you've been standing still for the time you've been channeling up to the point where you have been casting. If you were to split this down into 3 GCDs with 1 bloodletter proc inbetween, you'll finish 3 casts + the bloodletter faster than doing 3 casts, canceling one, using that bloodletter and re-casting that canceled cast. If you're betting on that one chance to get that re-proc within the next GCD, you're betting on the low chances as I've explained to you in my other post:

As for losing procs as a bard, there are actually intervals for river of blood between each procs. You could easily finish your current cast to use whatever proc you have after that aside from Straight Shot.

Even if you consider the chances of losing procs:
River of Blood has a 2x 10% chance to proc, assuming 20% crit rate
Straighter shot 20% chance to proc

Odds are much higher that you don't get a proc in comparison to wasting a proc. Where in most casts you may interrupt your cast for a proc and don't get a proc after your next cast; You simply lose GCD time like this.

For every cast you cancel in favor for a proc, you'll waste time in the long run. On average you'll waste your time spend casting by canceling it four times out of five.

And yes, you most certainly can get back to back bloodletter procs. It is not always a 3 second wait between procs.

River of blood can only be activated when damage is actually dealt from your DoTs. Apply it on a dummy and look at the numbers. You'll realise they appear at a timed interval and are not continuous. Ergo: Bloodletter can't proc faster than 3 seconds. If it's happening it's because the DoT damage happened shortly after you use bloodletter.

Sources for you to read up about that confirms this:
https://www.reddit.com/r/ffxiv/comme...ots_explained/
http://www.bluegartr.com/threads/117...=1#post6154837

If you don't want to read those, here is a video:
https://www.youtube.com/watch?v=aQGGTKgL8-g

In particular this bit of that video:
https://youtu.be/aQGGTKgL8-g?t=5m

[MrCookTM]

AN in exchange for that half a gcd you're gaining another shot fired. its just not gonna be a dps loss. Its not like that half a GCD just passes without getting anything out of it. You're still gaining a shot fired.

No. No, you don't gain anything. Since a proc can only happen every 3 seconds and a weaponskill is on a 1,5 second cast, you will ALWAYS be able to use all your procs while finishing all your weapon skills, without ever having to interrupt anything. I don't get what's so difficult to understand about that.

And yes, you most certainly can get back to back bloodletter procs. It is not always a 3 second wait between procs.

No, it can't. See post above me. Just stop pretending this bs already, it's seriously dumb.

[Malevicton]

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.

I know what stutterstepping is. The point of it is to be able to move while finishing your cast; it gives you more movement, not less casting. Your movement is the ends, not the means. Stopcast would straight up interrupt your cast.

It sounds like what you want is to overlap casts, which is not at all how stutterstepping works. The game still q's the abilities.

[Shirobi]

In the time you are moving, you can already be taking another action. Its like how you could use stopcast in a macro in early WoW to "interrupt" a cast and start a whole new cast while the od one continued to go off. You could do the same in FFXI, except no macro there made it less efficient (Essentially the same thing here.).