${Target.MaxRangeTo} with door targetted

[tonio]

Code: Select all

/doortarget
/echo ${Target.MaxRangeTo}

Causes a crash to desktop.

Debug output:

Code: Select all

First-chance exception at 0x00451e3d in eqgame.exe: 0xC0000005: Access violation reading location 0x00000000.

Call Stack:

Code: Select all

 	eqgame.exe!00451e3d() 	
 	MQ2Main.dll!MQ2SpawnType::GetMember(MQ2Internal::_MQ2VarPtr VarPtr={...}, char * Member=0x0307d5f0, char * Index=0x001295cf, MQ2Internal::_MQ2TypeVar & Dest={...})  Line 383 + 0x8	C++
>	MQ2Main.dll!MQ2SpawnType::GetMember(MQ2Internal::_MQ2VarPtr VarPtr={...}, char * Member=0x0012b620, char * Index=0x0000001c, MQ2Internal::_MQ2TypeVar & Dest={...})  Line 233 + 0xa	C++
 	eqgame.exe!004e368f() 	

Offending code appears to be within EQ, but last MQ2 call was:

Code: Select all

	case MaxRange:
		Dest.Float=get_melee_range((EQPlayer*)pSpawn,(EQPlayer*)pSpawn); 
		Dest.Type=pFloatType;
		return true;

specifically the call to get_melee_range().

[Lax]

yeah... that would be bad
assuming it's in your UI i'll have to work around it eh

[tonio]

No, not in my UI, still haven't gotten around to using fun custom UIs... ran into it while working on my /stick plugin... tried to /stick on a door. =)

Worked around it by checking spawn type and only calling get_melee_range() if spawn type was PC or NPC.

[tonio]

I take that back... doors' type shows up as NPC...

Gonna use State, which shows up at UNKNOWN... anybody know whether PCs or NPCs (real ones, not doors!) ever return an UNKNOWN state?