[Release] 2.4.3 Addresses

[Remahlól]

Don't quote your stuff, [code] it rather..

[Cypher]

Don't quote your stuff, [code] it rather..

Code tags are lame. I like taking up heaps of space. Its more fun.

I'll start using code tags when they add syntax highlighting.

[kevinr]

Would these addresses be the same for mac? Or windows only?

[Cypher]

Would these addresses be the same for mac? Or windows only?

Obviously (isn't it??) Windows only.

[chizo]

Sorry for that dumb question but im new in CE and memory editing. What is possible whit this adresses you posted here?

[Sychotix]

it doesnt matter how new you are to Cheat Engine... the pointers do exactly what they say.

[Broken Shadows]

xD This is all stuff I dun understand, sounds complex ;<!

[Sychotix]

they are complex addresses, or pointers.
ex.
[00E29D28]+0xC70

[00E29D28] is having the value inside of that address taken out of it. then it adds 0xC70 (that is hex) to that address.

[Cypher]

The addresses Sychotix are referring to are known as 'pointers' because they 'point' to another address. Offsets are used when the pointer points to a class or struct of some sort, the pointer points to the base address of the object in question, and the offset is added to access the required member.

[sebdoingbot]

hi there.

I manage to get player position/rotation from memory.

But i got problem for getting Target GUID.. in 2.4.2, target GUID offset was 0x00DDEC88 from hProcess, but value is always 0 in 2.4.3, i dont manage to find it for 2.4.3.

I see the list of addresse there but, i cant figure out how to get it in my offset coordinate.

Regards,

Seb

[kynox]

Hi, an easy way to find the offsets with each patch is to search for "Interact Target" in OllyDbg. Once you find this, you'll see 2 offsets being moved. The smaller one is the one you want. (Because its an Int64 aka 8 bytes).

However, the better method is to read the data directly from the CObject's Storage array.

[sebdoingbot]

Thanks for helping.

Well, i dt know how to use OllyDbg... but i guessusing TLS would be better.

While waiting for answer i tried to find unit target from the TLS stuff.

I thought i could get target'sGUID with objectaddress+ UNIT_FIELD_TARGET, but it's not working, i still miss something about TLS.

I manage to parse all objects, and getting :
- object GUID ( objectaddress + 0x30 )
- position/rotation ( objectaddress + 0xBF0 ),
- next object ( objectaddress + 0x3C )

but i dont manage to get the eUnitFields informations ( health or target for example ). I tried :
- health ( objectaddress + UNIT_FIELD_HEALTH )
- health ( objectaddress + 0x120 + UNIT_FIELD_HEALTH )

I read this forum since this morning , and i dont find where i'm wrong.

Thanks helping

Seb

[sebdoingbot]

Finaly i figured out myslef.

Do somebody has a link to know the type of each field? ( float,int, int64,etc... ) ?
When i get the players's target as int, sometime it's ok, sometime it can't find the object. Because GUID should be Uint64... but if i get uint64 from the UNIT_TARGET_FIELD, i dont get the right GUID.

I tried on my self and some people moving at Orgrimar, it works on me, and most of players , but for some player i can't find their GUID.

Any thought?

Cheers,

Seb

[tatakau]

thanks for the guide

[Xarg0]

typedef struct GUID
{
unsinged long A;
unsinged long B;
}TGUID, *PGUID;