/stopcasting

[Pantalaimon]

Hmm how would it be an issue? Walk me through it, cause I don't see it.

You cast smite, you cast smite again with /stopcasting, the first one hits, and the second one right after your latency is up. When the GCD is up you hit smite again. Is that how it goes? How is this a problem?

I'm fairly certain that this is what happens:

You cast smite
Start casting again with /stopcast; note this smite has a casttime
1st Smite lands - triggers a proc

When your 2nd cast completes, it "uses" the charge even though it wasn't instant. Basically your charge is completely wasted.

One can infer from this that the SoL functionality is server side (oh, wow, imagine the exploiting if it was client side and people could figure out how to get at it:P) yet the casting animation is client side - so your client goes into its casting before it's been informed that your next smite should be instant. Some funky stuff going on to be sure, though.

Edit: Removed a bit of faulty logic.