stutterstep/slidecasting nerf?

[Risvertasashi]

From the 4.3 patchnotes:

The following issues have been addressed.
-snip-
An issue wherein moving after beginning to cast a spell would not correctly interrupt casting.

Is this what it sounds like?

[Rongway]

Maybe, but it could also be talking about the times when you try to interrupt your cast immediately after you start casting, and you keep casting anyway; that is also a thing sometimes. It's not usually a big deal, except when a Verslowspell starts long casting instead of consuming Dualcast, or Flare ignores Swiftcast.

[Exiled_Tonberry]

I wonder...It specifically says when beginning to cast a spell, not when the spell is almost finished.
It would feel pretty awful to fix this now when people are so used to slidecasting for mobility.

[Risvertasashi]

I wonder...It specifically says when beginning to cast a spell, not when the spell is almost finished.

Well, not exactly... it says "after". But even were that true... people got caught up reading specifics into specific wording at the expac release too and well, quite a lot of turned out to be reading too much into the phrasings.

Still, I'll hope you're right.

[HyoMinPark]

Mmm, I don’t think it means slidecasting... because slidecasting results from client-to-server latency, where as you move your character at the very last second of a cast and the server hasn’t registered the movement yet and the cast still goes through even though you moved... Makes me think they’d have to actually fix infrastructure for that... I’m not an IT expert so I can’t say for certain, but I don’t think it’s slidecasting. It would be really crappy if it was though.

[Alma_karma]

I am guessing that at the beginning of the cast is a bug/glitch rather than near or at the end where latency and lag come into play. I know with my connection i tend to be able to start moving again at about 90% of the cast. This timing gets worse with lag.

Rather than at the beginning which could easily be exploited in raid and such. So the wording might make sense. Can't really fix a lag issue but if its exploit that's completely different.

[Risvertasashi]

because slidecasting results from client-to-server latency, where as you move your character at the very last second of a cast and the server hasn’t registered the movement yet and the cast still goes through even though you moved...

Well... supposing SE did want to "fix" this... couldn't they add an interrupt-on-movement mechanism to the client?

I suppose this will be something to test once the servers are back...

[Ghishlain]

It was possible to have 0.5s cast time spells be casted while the caster was moving (IE, casting Gravity which has a 0.5s cast time while under the effect of Lightspeed). I feel like this actually prevents that in order to assist with the fluidity of game play perhaps. However this would also be a minor and indirect nerf to Lightspeed just due to Gravity + Lightspeed if the caster has to move.

...this might also explain why Aspected Helios was reduced to 2.5s for this patch - so the combination of Aspect Helios + Lightspeed wouldn't cause this issue.

[miraidensetsu]

Maybe, but it could also be talking about the times when you try to interrupt your cast immediately after you start casting, and you keep casting anyway; that is also a thing sometimes. It's not usually a big deal, except when a Verslowspell starts long casting instead of consuming Dualcast, or Flare ignores Swiftcast.

That's VERy annoying. And when Holy ignores swiftcast is annoying as well.

[HyoMinPark]

Well... supposing SE did want to "fix" this... couldn't they add an interrupt-on-movement mechanism to the client?

I suppose this will be something to test once the servers are back...

They probably could have configured something to download client-side with the new patch... But hopefully that isn’t the case. I like to take advantage of slidecasting on healers, and I would be pretty salty if they took that away from me. >.>