Starting with 5.3.0

[Raphy]

Hi guys,

I'd to know how to starts with the version 5.3.0.

I've read a lot of documentations and the most of the time, I've seen offsets names like "ObjectManagerOffset.Tls", "ObjectManagerOffset.CurMgr", etc.
But now, when I read the dump threads, there is no offsets for "tls", "curmgr"...

So no way for me to try my own Object Manager if I have no offsets :/

So, did the names change ? Or the way of coding the Object Manager changed ?
Can you give me some links up to date ?

Thanks a lot

EDIT : If post an example, I will be able to understand

[Bananenbrot]

A few patches ago (around 5.0 I think?), they got rid of most of the TLS stuff. See http://www.ownedcore.com/forums/worl...ml#post2466242 ([WoW][5.0.4.16016] x86 Info Dump Thread) tom_rus post, especially the paste links at the end.

[Raphy]

WaW Thanks a lot for this link ! You made my day

[FinnX]

I have a repository of my ObjectManger on Github. I just published it and it doesn't has alot so far. Only NPCs as type of object are working and the NPCObject class only contains GUID + Position. It is pretty easy to add other stuff like "Name", "HP/Power(Energy, Mana)". Feel free to download it and add some stuff. If you know how Github works, feel free to send a pull-request of your changes so everyone has something of it (social coding!). I might add more stuff later in this week and commit changes, but not for now.

https://github.com/finndev/WoWObjectManager

[Raphy]

I only use Git instead of SVN
It will be a pleasure to contribute
Thanks a lot !

Is these offsets up to date ?

EDIT : Man... You are terrible ! I don't know how to thank you ! It's a "gold mine" for me

[FinnX]

I only use Git instead of SVN
It will be a pleasure to contribute
Thanks a lot !

Is these offsets up to date ?

EDIT : Man... You are terrible ! I don't know how to thank you ! It's a "gold mine" for me

Yup, offsets are up to date. Download it, run it and you'll see GUID + X + Y + Z of every NPC nearby.

[Raphy]

When I try to compile a compilation error : "Erreur 1 Impossible de trouver le fichier source 'Properties\AssemblyInfo.cs' C:\Users\Raphy\Downloads\WoWObjectManager-master\WoWObjectManager-master\WoWObjectManager\CSC WoWObjectManager"

I will try to repair by myself

EDIT : Really nice!
I wonder why this condition "while (CurObj != 0 && (CurObj & 1) == 0)"
I understand "CurObj != 0" because of the NULL pointer at the end of the linked list, but I don't for "(CurObj & 1) == 0". Can anybody exaplain me ?

[Bananenbrot]

It's the exact check the wow client employs (or employed).

[Raphy]

ok thanks for answering !

[573737534947]

(CurObj & 1) == 0 checks if it's an even address. You can cut the check and see what happens. Basically the last objects next ptr isn't always 0 (but for whatever reason odd if not so), that's what you'll probably discover.

[Bananenbrot]

(CurObj & 1) == 0 checks if it's an even address. You can cut the check and see what happens. Basically the last objects next ptr isn't always 0 (but for whatever reason odd if not so), that's what you'll probably discover.

Technically speaking, all addresses to structs are generally aligned to fit the architecture (4 byte for 32 bit, 8 for 64). That's why you could assume that valid object pointers are never odd or even that they are always congruent modulo 4 with 0. This holds true as long as you don't #pragma pack them and put them in arrays.

[573737534947]

Yes pointers are generally architecture specific aligned. So you can almost always safely exclude addr mod 4 != 0. The "for whatever reason"-part was related to the fact that they seem to assume safely that if the last objects next obj ptr is no valid object it's also no valid (read word aligned) pointer at all. In other words what the heck do they store there if not an obj ptr and no NULL ptr and why can they make assumptions about it.