Casting while "out of range"

[Critical]

Simple

Spells allow you to cast when it lands, says "You are out of range".

This poses a problem for pve and more importantly pvp.

[Vermicelli]

The way I am reading your bug report is that if you start casting a spell while the target is in range, but the mob or player moves out of range while you are casting, your spell is interrupted. If so, this is working as intended. On Blue 99, clicking a spell will not allow you to cast when you are out of range.

[Lazortag]

Sometimes the original LOS check is passed, but even though the target doesn't move, you get a "target is out of range" message when the spell finishes. This often happens with targets that are close on the x-y axis but far away on the z axis.

[Renk]

Yeah, I played around with it a little bit and it seems to be a z-axis issue.

On a flat area, I inched in and out of range and got proper range functioning. But, when a mob was up on a hill, when first inching into range it will attempt to cast but give a range error at the end of cast, on both red and blue. So perhaps the initial range check is only on the horizontal plane.

Similar to how, even if a mob is blocked by a hill, it will still try to cast if they are in horizontal range, and only give a los error at the end of the cast.

No idea if this is accurate to classic or timeline, or is unique to EQ Emu code.

Anyone know how this works on EQMac?

[uygi]

My understanding: The initial range check to start the cast is done client side. At the end of the cast it's sent server side, and the server will check it then. If you're lagged or your client misreports the target location (there are a number of issues that can cause this), you'll end up with this problem. Of course this also happens if the target simply moves out of range during cast. And your sig is great.

[Critical]

It happens when the mob is not moving, and yes I think it's a Z axis issue because I noticed this while pulling mobs on Seafury island.

[Wyrdo]

Get this with Bloodgills all the time

[Lubian]

It probably means the range check the client uses does not match the range check the server uses. Whether that's because we're not using the Kunark client, or if the server is using the wrong formula is up for debate.

[Dullah]

Definitely seen this bug as well.

[uygi]

It happens when the mob is not moving, and yes I think it's a Z axis issue because I noticed this while pulling mobs on Seafury island.

If you're quadding, that would explain it. I never played a quadding class on Live so I cant say if it correct or not, but for quadding nukes the server will report out of range due to Z axis even though the client allows you to "cast".

[Orruar]

I posted on this long ago as I was sure (and still am) that the second server side distance check should not be there, at least for beneficial spells. I used to cast heals in velks on my warrior up near the top while sitting my cleric at the bottom.