Memory Value keeps changing

**Ungara** · 11-11-2014

Hello!

After seeing how easy these hacks are to make, I decided to try it out for myself.
Well, didn't turn out that bad.

I found a nice thread: /showthread.php?t=298510
Started Visual C# 2008 (yeah, should probably update), MW3, Cheat Engine and let's go!

First thing i tried to find out, was the Address of the FoV. I figured out, that I couldn't really find it.
So i cheated a little and used an existing FoV Changer to change the FoV so that I can find the address with CheatEngine :x
Since I already had started MW3, I decided to find the address for the ammo of the weapons. Alright, MP7, MSR and Desert Eagle.
When I had the adresses, I went to C# and wrote some code :P

Well, now to my problem.
My App changes the value, which is nice. But the problem is, I set the FoV to 95 and then, when the game is over, and a new one starts, the FoV is back to 65.
With the ammo on the weapon its the same thing. It is set to e.g. 100 but then it won't stay at 100.

Is there any way how I can lock the value like in CheatEngine?

I mean, I could still use a timer which updates the values every 100ms, but there has to be a better way, right?

**tykath1234** · 11-11-2014

Originally Posted by Ungara

Hello!

After seeing how easy these hacks are to make, I decided to try it out for myself.
Well, didn't turn out that bad.

I found a nice thread: /showthread.php?t=298510
Started Visual C# 2008 (yeah, should probably update), MW3, Cheat Engine and let's go!

First thing i tried to find out, was the Address of the FoV. I figured out, that I couldn't really find it.
So i cheated a little and used an existing FoV Changer to change the FoV so that I can find the address with CheatEngine :x
Since I already had started MW3, I decided to find the address for the ammo of the weapons. Alright, MP7, MSR and Desert Eagle.
When I had the adresses, I went to C# and wrote some code :P

Well, now to my problem.
My App changes the value, which is nice. But the problem is, I set the FoV to 95 and then, when the game is over, and a new one starts, the FoV is back to 65.
With the ammo on the weapon its the same thing. It is set to e.g. 100 but then it won't stay at 100.

Is there any way how I can lock the value like in CheatEngine?

I mean, I could still use a timer which updates the values every 100ms, but there has to be a better way, right?

Yo i had the same problem but i fixed it, hit me up on skype! tykath.tykath will discuss and help

**AuT03x3C** · 12-02-2014

Originally Posted by Ungara

Hello!

After seeing how easy these hacks are to make, I decided to try it out for myself.
Well, didn't turn out that bad.

I found a nice thread: /showthread.php?t=298510
Started Visual C# 2008 (yeah, should probably update), MW3, Cheat Engine and let's go!

First thing i tried to find out, was the Address of the FoV. I figured out, that I couldn't really find it.
So i cheated a little and used an existing FoV Changer to change the FoV so that I can find the address with CheatEngine :x
Since I already had started MW3, I decided to find the address for the ammo of the weapons. Alright, MP7, MSR and Desert Eagle.
When I had the adresses, I went to C# and wrote some code :P

Well, now to my problem.
My App changes the value, which is nice. But the problem is, I set the FoV to 95 and then, when the game is over, and a new one starts, the FoV is back to 65.
With the ammo on the weapon its the same thing. It is set to e.g. 100 but then it won't stay at 100.

Is there any way how I can lock the value like in CheatEngine?

I mean, I could still use a timer which updates the values every 100ms, but there has to be a better way, right?

You can freeze an address in CE or you can create a Timer in C# so the value would be also freezed.

**szczyurcio** · 12-02-2014

Originally Posted by AuT03x3C

You can freeze an address in CE or you can create a Timer in C# so the value would be also freezed.

If I'm not mistaken all CE does is actually repeatedly write your value to the address. Anyway yeah, that'd work. Depending on the situation, you could also try NOPing the instructions that write to your memory location.

**81|DrizZle** · 08-03-2015

Originally Posted by szczyurcio

If I'm not mistaken all CE does is actually repeatedly write your value to the address. Anyway yeah, that'd work. Depending on the situation, you could also try NOPing the instructions that write to your memory location.

And that's how it gets freezed.