How To Use Offset Dump?

[Cooldude]

How do you use the offset dumps that are publicly posted? For example I am on 3.3.5a 12340 warmane.

In the public dump threads such as here (https://www.ownedcore.com/forums/wor...0-offsets.html (3.3.5a 12340 Offsets))

It says that player xp is at 0x00AC66D8 + offset 0x9E8

When I manually find the current playerXP pointer using CE I get 0x006EEDD0 + 0x14, 0x20, 0x4, 0x34, 0x24, 0xC, 0x984 and can read the value with an internal DLL successfully.

How do you use those public dumps? If i try to read 0x00AC66D8 + offset 0x9E8 it just returns random bogus in memory.

[NoxiaZ]

It would be easier to help you if you showed your code for reading.
Anyways, if you want to use the pointer 0x00AC66D8 with an offset on 0x9E8 then you have to take baseaddress of wow like "Wow.exe+0x00AC66D8" read the address there and add 0x9E8, and then you get to the location.

Or in CE it would be: Capture.PNG

Hope this helps you a bit.

[Cooldude]

Thanks for the reply, I tried that first but no luck, here is how I am reading:

        uintptr_t moduleBase = (uintptr_t)GetModuleHandle(L"wow.exe");
    moduleBase = (uintptr_t)GetModuleHandle(NULL);
    uintptr_t playerXPDump = mem::FindDMAAddy(moduleBase + 0x00AC66D8, { 0x9E8 });
    uintptr_t playerXPPointer = mem::FindDMAAddy(moduleBase + 0x006EEDD0, { 0x14, 0x20, 0x4, 0x34, 0x24, 0xC, 0x984 });

uintptr_t mem::FindDMAAddy(uintptr_t ptr, std::vector<unsigned int> offsets)
{
    uintptr_t addr = ptr;
    for (unsigned int i = 0; i < offsets.size(); ++i)
    {
        addr = *(uintptr_t*)addr;
        addr += offsets[i];
    }
    return addr;
}

Edit:
When I open cheat engine and put the wow.exe + address and then add the offset I don't get anything either, see screenshot.
Screenshot: Screenshot by Lightshot

[NoxiaZ]

Seems you are using the wrong pointer - Are you sure that these offsets are for this version ? - I am not playing that version, so i can't test it my self.

[sanyle]

I use CE to see the offset, but it often crashes the game. Changing keywords as suggested still happens frequently. Is there any other good way? thank.