Casting behind LoS

[Evolvee]

If you cast something(root/cyclone/whatever) and the target gets behind LoS(arena pillar) in like 80-100% of that cast time, you will still get that root/cyclone/whatever even tho u LoSed it. Probably the similar mechanics which allows you to cast slightly behind the spell cast range?(casting frostbolt, target run away from range, still gets fb --> this is correct but idk if it should be that big range as it is on test server atm)

[TurtleOSP]

Sounds like latency. It's like this in retail and will always be like this. It might be more apparent if your playing from NA as I believe the server is in EU so latency will be higher.

[Evolvee]

22 ms, nice try but no banana :(

(my bet is that its cuz of that custom delay)

btw this is not just my problem, i wouldnt even type it here but guys i played with yesterday told me this many times in game.

[Klimpb]

I've never experienced this from either casters or receivers perspective.

I've sometimes felt the opposite while trying to cast drain life on targets who are just about to run behind a pillar

[Evolvee]

I did couple of dots behind pillar, but i wouldnt type it here, mia asked me for it cuz he said he cycloned like that several times. I may find a VOD.

[somnu]

I remember this happening on retail servers back in TBC quite a lot, a lot of people notice stuff like this since they're not used to it anymore on private servers, due to other servers not implementing a custom delay.

[Schaka]

I think this may be related to leeway-range on spells ignoring LoS, which it shouldn't. If you get out of LoS before the castbar is finished (and not around the same time) AND you don't jump, you shouldn't get hit by the spell.

This is also different with spells that fly, which if finished around the time you move out of LoS, will visually follow the target.

Edit: To elaborate, I noticed this for sure (I never jump behind a pillar anymore, learned my lesson from retail) and think it's a bug.