3.1.3 info dump

[Robske]

like this ?

$PlayerBase = _MemoryRead(0x010BD5F4,$mo,'ptr')
$hp = _MemoryRead(0x17*4, +_MemoryRead($playerbase+0x8, $mo, "int"))

still getting 0 ;/

Why so ugly

Here we go again, for the 3th billionth time...

To get the base address of the local player's object you'll have to do 3 reads. [[[0x010BD5F4]+0x34]+0x24], which in your crappy language would translate to:

$pBasePointer01 = _MemoryRead(0x010BD5F4,$mo,'ptr')
$pBasePointer02 = _MemoryRead($pBasePointer01 + 0x34,$mo,'ptr')
$pBasePointer = _MemoryRead($pBasePointer02 + 0x24,$mo,'ptr')

Now, there's a pointer to an array-like structure at 0x8 from the localplayer's base address. [pBase + 0x8] will be the base address of that array-like structure. This contains all descriptors such as health and mana and is usually named "the descriptor array" or "storage array", whatever floats your boat...

$pStorage = _MemoryRead($pBasePointer + 0x8,$mo,'ptr')

Cypher and others posted a dump with the indices of all decriptors such as health and mana, Health for example has index 0x17. So we want to read from [pStorage+0x17*4]

$Health = _MemoryRead($pStorage + 0x17*4,$mo,'ptr')

[natt_]

Sorry but auto-it cought me :'(. Im sad for that to. But i CBA to learn any new lang! ;(. Anyway. Big thanks for the help. i will try to search "BETTER" next time +2rep<3

[lanman92]

It's the same damn thing. You read the offset from [[obj+0x8]+0xwhatever]. Jesus...

[natt_]

It's the same damn thing. You read the offset from [[obj+0x8]+0xwhatever]. Jesus...

than why doesn't

_MemoryRead($pStorage + 0xB * 4,$mo,'float')

return my x coordinate instead of 0... I tried different types and they all returned 0

[lanman92]

It's the wrong object type. That's for dynamic objects. You have to use the movementfields at [obj+0xD8]. Search here for the struct. It has changed slightly though.

[natt_]

Hmm okay. i already have em: '3.1.3'

[WowDynamicObjectFields]

DYNAMICOBJECT_CASTER=0x6
DYNAMICOBJECT_BYTES=0x8
DYNAMICOBJECT_SPELLID=0x9
DYNAMICOBJECT_RADIUS=0xA
DYNAMICOBJECT_POS_X=0xB
DYNAMICOBJECT_POS_Y=0xC
DYNAMICOBJECT_POS_Z=0xD
DYNAMICOBJECT_FACING=0xE
DYNAMICOBJECT_CASTTIME=0xF
TOTAL_DYNAMICOBJECT_FIELDS=0x9

anyways i recived an float with e-59 in it so its horribly wrong i guess, since the coords only have like 15-20 decimals or so.

Where do you get those [obj+???] information from?. I am really curious about that.

[boredevil]

baseadress +
X=0x798
Y=0x79C
Z=0x7A0
Pitch = 0x7A4 // not shure about this one
Rotation = 0x7A8

[lanman92]

The structure above me is pointed to by [obj+0xD8].

[natt_]

no damn still 0. Wth?

baseadress = [obj+0xD8]
x = baseadress+0x798 >>>>FLOAT<<<<
return: 0.

[boredevil]

you seem to be a bit confused by the different names, mentioned

considering what robske wrote a few posts ago, the baseadress mentioned by me is what he refers to as basePointer.

so, get the basepointer, as robske does it, and then read

x = basePointer + 0x798

[natt_]

now that made things more* clear for me. edyt

[neph4]

Cheers !

[lanman92]

You have it wrong, mate. The [obj+0x0xD8] is a pointer to movementfields. X, Y, Z, and rotation start at 0x10 from the base of movementfields.

[Thongs]

Can anyone share what the offset for NextObject is? Searched several times and haven't found the offset for 3.1.3

[Robske]

Can anyone share what the offset for NextObject is? Searched several times and haven't found the offset for 3.1.3

Object struct layout hasn't changed in a while, it's still the same...

Do you people even try your crap before you ask questions here?