So I've got some C++ code running that lets me access the object manager. I grab the localplayer GUID real quick then scan through the object manager until the current object that I'm looking at has the same GUID. Hence, I arrive at the localplayer base address.
(Credits: Apoc) From the 3.2.2 Info Dump thread, it indicated:
So I read the value at [[localplayerbase] + PLAYER_TRACK_RESOURCES] and I get "55485c43" which does not really resemble anything close to (credits: Robske):
/* offsets:[d:0x03E5]:[b:0x0F94] */ unsigned long PLAYER_TRACK_RESOURCES;
My guy in game is currently tracking minerals so I would sort of expect the value that I read to come out as 0x04...
TRACK_OBJECT_HERBS = 0x02,
TRACK_OBJECT_MINERALS = 0x04,
TRACK_OBJECT_TREASURE = 0x20,
-1 if you whish to track everything.
Anything that I'm obviously doing wrong here? I realize that the offset for PLAYER_TRACK_RESOURCES was only in the 3.2.2 dump and that it may not be the same as in the current version (3.2.2a). Though, I wouldn't really be able to find the new offset myself as there is nothing for me to work off of. I tried running through 0x4 increments from the localplayer base address to see what I could find that matches the TRACK_OBJECT_MINERALS value but I really didn't get too far. There were like 3 offsets or something that matched but when I set my in-game tracking to nothing, their values didn't change to something like 0 which to me seems like the logical value for nothing being tracked.
Any advice/help is appreciated. This is currently my 3rd step in writing anything related to WoW memory editing so be gentle =X...first two steps were mostly just a few lines here and there in AutoIt.