WoW Current Statics and Offsets

[tttommeke]

Actually, finding your coordinates is one of the easier aspects, a decent navigation system though is hard to write from scratch. (I'm not talking about a waypoint system I'm talking about something more like LavNav, a dynamic nav system that uses a mesh rather than waypoints). Object avoidance is a PITA too.

Also, without injection it's hard to reliably interact with the client and manage your inventory, interact with NPCs, cast spells, watch for important events using WoW's event system, etc.



A quick way to fix targetting would be to enumerate the mob struct, find a suitable target (by searching for which mob has the closest coords) then setting your 'Target' offset in the player struct to the GUID of the mob you want to target in the mob struct. That should work.

it would only work when you have targetted another mob, when you change it it wouldn't port your targetscreen to him, you need to let WoW update it (so change your targetscreen).

[hypnodok]

Say Ive got the following C# Code to read the memory based on offsets, why does it return 0000 (should be maximum health) , what am I doing wrong?
Reading static offsets works just fine, my memory reading class is not the problem.

        private void button1_Click(object sender, EventArgs e)
        {
            Process[] m_p = Process.GetProcessesByName("WoW");
            if (m_p[0] != null)
            {
                ProcessMemoryReader pmr = new ProcessMemoryReader();
                
                pmr.ReadProcess = m_p[0];
                pmr.OpenProcess();
                long offset = 0xA560;
                richTextBox1.AppendText("Base adress: "+pmr.ReadProcess.MainModule.BaseAddress.ToInt64().ToString("x")+"n");
                richTextBox1.AppendText("Offset :" + offset.ToString("x") + "n");
                
                long id = pmr.ReadProcess.MainModule.BaseAddress.ToInt64() + offset;
                richTextBox1.AppendText("Offset+Base: " + id.ToString("x")+"n");
                int readb;
                byte[] bytes = pmr.ReadProcessMemory((IntPtr)id, 4,out readb);
                string str = "";
                foreach (byte b in bytes)
                    str += b;
                richTextBox1.AppendText("Bytes read: "+readb.ToString("x")+"nData read:    "+str+"n");
                richTextBox1.ScrollToCaret();
                pmr.CloseHandle();   
            }
        }

[localhostage]

Could anyone find the target X,Y,Z,health,mana etc.. offsets? If not could someone point me in the direction so I can find them and share?

This would be crucial information when writing a bot.

Thanks!


p.s. I'm not great with memory offsets but I'm one hell of a coder

[tttommeke]

Scan scan scan for them...

[dragospt]

i am getting: pmr.ReadProcess.MainModule.BaseAddress = 'pmr.ReadProcess.MainModule' threw an exception of type 'System.ComponentModel.Win32Exception' - Access is denied

any idea what's wrong?

[tttommeke]

Your program isn't allowed to read in memory ?

[dragospt]

I also tried something like this, but always gett 0 results.. I'm using visual studio 2008

            uint bytes = Convert.ToUInt32(tx_bytes.Text.Trim(),10);
            int address = Convert.ToInt32(tx_address.Text.Trim(), 16);
            String processName = tx_process.Text.Trim();

            ProcessMemoryReader pReader = new ProcessMemoryReader();

            System.Diagnostics.Process[] myProcesses = System.Diagnostics.Process.GetProcessesByName(processName);

            if (myProcesses.Length == 0)
            {
                MessageBox.Show("Process " + processName + " found!");
                return;
            }
            pReader.ReadProcess = myProcesses[0];

            // open process in read memory mode
            pReader.OpenProcess();

            byte[] memory;
            int bytesReaded;

            memory     = pReader.ReadProcessMemory((IntPtr)address, bytes, out bytesReaded);
            int value  = memory[0];
            tx_value.Text = value.ToString();

[dragospt]

@tttommeke: I tried using hypnodok code for winmine (minesweepr windows game) and i didnt got any error, but when swishing to WoW, denied appeared. i don't understand why..

Is getting very frustrating, because i want to work on a bot and fail read data from memory

[hypnodok]

You really should not use my code because I have absolutely no clue what Im doing.
It works fine for reading static pointers but the way I calculate offsets is probably just straight up rubbish.
If anyone could point me and the others in this thread to the right direction I would very much appreciate it.

[localhostage]

i found Dynamic Z using TSearch @ A698BF0, next found dynamic health @ A69A548.

so i located base address by doing dynamic z - 0xBF0 which yields A698000 but to get to the dynamic health offset it wasn't 0xA548 it was 0x2548. has this changed or am i doing some wrong math here?

[tttommeke]

It could be changed, not tested myself.

[localhostage]

Just tested on 2 clients, looks like health, mana and the other offsets beginging with A have changed into 2.

Also found 0x3268 which is Experience.

Still on the hunt for target base offset, target level, target health, etc..

[tttommeke]

Target base, from target base -0x8 + 0x{HPOffset}, you can't find trough the player his target hp, you need to do it from the mob itself.

[Froogle]

i found Dynamic Z using TSearch @ A698BF0, next found dynamic health @ A69A548.

so i located base address by doing dynamic z - 0xBF0 which yields A698000 but to get to the dynamic health offset it wasn't 0xA548 it was 0x2548. has this changed or am i doing some wrong math here?

I think you failed to see how offsets work, it is the offset added to the base address, not the last 4 or 3 digits.

A698000+0xA548=A6A2548 <--- you must have been mistaken, offsets are added to the base address. (woops did some bad math earlier :0 fixed)

[localhostage]

I think you failed to see how offsets work, it is the offset added to the base address, not the last 4 or 3 digits.

A698000+0xA548=A692548 <--- you must have been mistaken, offsets are added to the base address.

Hey Froogle, thanks for the reply! I see my error now and what I did was just one of those coding.. gotchas!

I was doing 0xA698000 + 0xA548 which came out totally wrong.

Just want to note to anyone else who ran into this issue that 0xA698000 is not the same as A698000. lol, thanks!