Issue With Distance /distance2d

[greeneyes137]

So, i was f'n around with the training dummy trying to up my dps and verify no new changes with scripts and I noticed that when i placed 5 training dummies away from each other my objectdef ActorCheck was failing when I was checking EQ2:CreateCustomActorArray[byDist,${range},npc] I was setting range to 30, but three training dummies set to 30 meters out were not showing. So when I targeted them, my ${Target.Distance} was reporting 33.009989and my ${Target.Distance2D} was reporting 33.029298. However, my everquest was showing 30 meters and my 30 meter spell was available for use. When I backed out to 31 meters, my spell was no longer available but my ${Target.Distance} and ${Target.Distance2D} was reporting 34.xxx meters.
When I move all the way up to the training dummy, i noticed that I hit 0 meters about 2 meters away. SOE/Everquest is showing 0 meters to mob, but distance and distance2d are showing 2.605569 and 2.602611.

It appears that isxeq2 or lavish are showing the distance to the center of the mob, not the distance to the hit box. Is this a recent development. It explains why some of my spells are not going off and my damage is lower recently that it use to be because spells that work 10 or 5 meters away are not working because it says i'm 7 or 12 meters away when i'm within range of the spell.

I'd report this as a bug, but when I tried, the report new or add new bug was not available. Anyone else experiencing this issue?

 

[greeneyes137]

Since I was in a guild hall with training dummies, i tested this again out in antonica, and then again within Nexus instance and finally High Keep [heroic]. Same results. Distance based from center of mob, not hit box.

 

[macker0407]

This has always been the case. The easy fudge is to multiply the actor .CollisionRadius and .CollisionScale members and then either add that to range of the spell/melee/etc. or subtract it from the .Distance* members. This will largely work but will still break on some models, so you'll either want to stick in some bounds checking or use it as a fallback method for checking the range of any actor that's not currently being targetted. For targetted actors use the ingame data.

 

[Amadeus]

I'd report this as a bug, but when I tried, the report new or add new bug was not available. Anyone else experiencing this issue?

I believe that macker's response is correct and has provided the information necessary to determine that this is not a bug. HOWEVER, I am concerned that the bug reports thing wouldn't work for you.

Can you elaborate upon what you're clicking and what you're seeing when you try to create a bug report? Are you "logging in" to the new Forge site or were you trying to do it without logging in? etc... (Screenshots would be great too.)