Calculating distance to melee

[bad6oy30]

I'm trying to determine minimum distance to melee, which appears to vary depending on the unit... most of the time it's 5.00yds, but a raid target dummy is 5.33yds (and bosses much more). UNIT_FIELD_BOUNDINGRADIUS and UNIT_FIELD_COMBATREACH don't seem to factor into it at all.

Normal Target Dummy:
UNIT_FIELD_BOUNDINGRADIUS: 0.525
UNIT_FIELD_COMBATREACH: 1.75
Melee distance: 5.00

Raid Target Dummy:
UNIT_FIELD_BOUNDINGRADIUS: 0.75
UNIT_FIELD_COMBATREACH: 2.5
Melee distance: 5.33

Critter:
UNIT_FIELD_BOUNDINGRADIUS: 0.2
UNIT_FIELD_COMBATREACH: 1
Melee distance: 5.00

OBJECT_FIELD_SCALE_X was 1 in all cases. I realize I could check IsSpellInRange for a melee spell, but I'd like to know the distance at any given point.

[evil2]

thanks for bringin this up.
i have the same problem, especially with raid bosses with a big hit box radius.

anyone found a useful unit value for this?

[zys924]

Any god can give a hand on this? Im also having the same trouble....

[ostapus]

second that, anyone ?

[ostapus]

well, visually training dummy is smaller than raiding training dummy but model is the same. wonder how to get that scale factor (getScale VT returns 1 for both)
and check if distance scaled/depends for the same number.

[evil2]

bump.

anyone found a solution?

[bad6oy30]

If I were still playing, and had any degree of debugging skill, I would reverse Lua's IsSpellInRange with a melee-range spell, and see how it gets figured out. Neither of those prerequisites apply to me unfortunately

[amadmonk]

Okay, I've confirmed; 0x8163C0 seems to correctly get the min/max ranges for any spell against any target. This is important because, for instance, Corruption says that it has a 40yd range, but in reality its 40+/- about 5yds. I don't know where this +/- comes from, but it's definitely there, and can definitely f*ck up your bot's distance routines. 0x8163C0 seems to always return the *real* results that match up with a pos1->pos2 vector length calculation when compared w/IsSpellInRange.

AND it takes into account the different sized melee hit-boxes. So 0x8163C0 is basically your one-stop shop for spell ranges.

IsSpellInRange is mostly just a shim around 0x819900.

int __cdecl sub_819900(void *pCaster, struct SpellEntry *pSpellRow, WGUID guid, bool *bInRange, int, int)

The problem is that 0x819900 is a HUGE function with >100 switch cases. This is probably why nobody has reversed it; there's not (AFAIK) a simple "get the range of this spell" function; instead, the range is calculated in giant switch block, meaning that reversing it is a major pain in the ass.

I feel your pain because right now I don't have a good, deterministic way to find out the spell range for a given spell (the DBC's just give you base ranges, unadjusted for buffs/talents/etc., and of course IsSpellInRange just gives you a yes/no answer, not the ACTUAL range). So I end up hard-coding spell ranges in my bot, which sucks.

---------- Post added at 11:36 AM ---------- Previous post was at 10:16 AM ----------

Okay, I *think* this is it:

void *__cdecl sub_8163C0(void *pCaster, SpellEntry *pSpellEntry, float *pfMinRange, float *pfMaxRange, bool bIsHelpful, void *pTarget)

Not sure what (if anything) the return value is, yet, but it pokes a min range and max range into those float pointers.

[Ssateneth]

Okay, I've confirmed; 0x8163C0 seems to correctly get the min/max ranges for any spell against any target. This is important because, for instance, Corruption says that it has a 40yd range, but in reality its 40+/- about 5yds. I don't know where this +/- comes from, but it's definitely there, and can definitely f*ck up your bot's distance routines. 0x8163C0 seems to always return the *real* results that match up with a pos1->pos2 vector length calculation when compared w/IsSpellInRange.

AND it takes into account the different sized melee hit-boxes. So 0x8163C0 is basically your one-stop shop for spell ranges.

IsSpellInRange is mostly just a shim around 0x819900.

int __cdecl sub_819900(void *pCaster, struct SpellEntry *pSpellRow, WGUID guid, bool *bInRange, int, int)

The problem is that 0x819900 is a HUGE function with >100 switch cases. This is probably why nobody has reversed it; there's not (AFAIK) a simple "get the range of this spell" function; instead, the range is calculated in giant switch block, meaning that reversing it is a major pain in the ass.

I feel your pain because right now I don't have a good, deterministic way to find out the spell range for a given spell (the DBC's just give you base ranges, unadjusted for buffs/talents/etc., and of course IsSpellInRange just gives you a yes/no answer, not the ACTUAL range). So I end up hard-coding spell ranges in my bot, which sucks.

---------- Post added at 11:36 AM ---------- Previous post was at 10:16 AM ----------

Okay, I *think* this is it:

void *__cdecl sub_8163C0(void *pCaster, SpellEntry *pSpellEntry, float *pfMinRange, float *pfMaxRange, bool bIsHelpful, void *pTarget)

Not sure what (if anything) the return value is, yet, but it pokes a min range and max range into those float pointers.

Sorry to necro this thread, but I've been looking through all the dump threads and simply cannot figure out what version wow you got 0x8163C0 from so I can look up to see where it is for the current version of wow. Would someone enlighten me? I too am looking for the size of the hitbox and I'm banging my head reading all these dump threads trying to find what version this magic address was for.

[Jadd]

Sorry to necro this thread, but I've been looking through all the dump threads and simply cannot figure out what version wow you got 0x8163C0 from so I can look up to see where it is for the current version of wow. Would someone enlighten me? I too am looking for the size of the hitbox and I'm banging my head reading all these dump threads trying to find what version this magic address was for.

It was for 4.0.6.13623 (have a look at the date of the post, then look on Patches - WoWWiki - Your guide to the World of Warcraft to see what version was out at that time).

In 4.1.0.14007 it's 0x00821DE0

[bad6oy30]

It's sub_8B1CB0 for build 15050

[zys924]

Mind me asking How "SpellEntry" comes from?

[miceiken]

SpellEntry is found in the internal WoW database (DBCs)