Writing to memory doesn't change the value

[mathix]

Hello, I've been trying to create a "hack" for educational purposes for World of Warcraft 3.3.5a.

The problem consist of whenever I try to write memory to specific adresses it doesn't change the value with my program, which is using BlackMagic to do this. But whenever I change these values with CheatEngine it works perfectly well.

The addresses in question is:
0xAA33DC - which is the address for jump gravity. I'm trying to set it with this function:

//Jump Gravity
wow.WriteFloat(0xAA33DC, float.Parse(textBox2.Text));

And I know it parses the float correctly, so that's not the problem. I use this with fall speed aswell, but that works perfectly well, which I find weird.

The second one is for wallclimb: 0xA37F0C - using this code:

wow.WriteByte(0x00A37F0C, 0x00);
wow.WriteByte(0x00A37F0C + 0x1, 0x00);
wow.WriteByte(0x00A37F0C + 0x2, 0x00);
wow.WriteByte(0x00A37F0C + 0x3, 0x00);

I hope anyone can help me find my error - if you need any additional information, feel free to ask for it! - Thank you :-)

[R4zyel]

Search about VirtualProtectEx

[mathix]

Search about VirtualProtectEx

So what you're saying is that I should use the VirtualProtectEx function to change the access protection to something like READWRITE so I can access it and change it? If yes, how exactly would you go around doing that in C#?

[Corthezz]

pinvoke.net: virtualprotectex (kernel32)

[baldrich]

If it's for your server then hook the jump OPCode and increase the arc length and reduce the time it takes. If you do this attached to a spell then you can have it multiply to get desired effect.

[mathix]

If it's for your server then hook the jump OPCode and increase the arc length and reduce the time it takes. If you do this attached to a spell then you can have it multiply to get desired effect.

This is mostly to use on other servers.

I'm reading up on the VirtualProtectEx and trying to figure out a solution.

[mathix]

As I'm a firm believer in writing the solution to your problems I finally found mine :-)

Here it is:

//Declare this somewhere
[DllImport("kernel32.dll")]
        static extern bool VirtualProtectEx(IntPtr hProcess, IntPtr lpAddress,
           UIntPtr dwSize, uint flNewProtect, out uint lpflOldProtect);

//Call this for your address to make it writeable.
uint dwOldProtect;
VirtualProtectEx(WoWHandle, (IntPtr)0xAA33DC, (UIntPtr)4, 0x40, out dwOldProtect);

Thank you for helping me :-)

[Jadd]

Don't forget to restore the original protection.

[mathix]

Don't forget to restore the original protection.

When should I do that? After writing to the address? And why is this important, do you risk to crash your game if you keep it writable?

[R4zyel]

When should I do that? After writing to the address? And why is this important, do you risk to crash your game if you keep it writable?

Actually there's no risk but...people tends to follow this procedure, to make it cleaner.

[DarkLinux]

Actually there's no risk but...people tends to follow this procedure, to make it cleaner.

Warden is not your friend, dont give it anything if you can help it