Thumbs upNo Recoil

Posts 1–15 of 44 · Page 1 of 3
alterIW No Recoil
Code:
const DWORD mw2_pid = 0; // <<< INSERT MW2 PID HERE
HANDLE h = OpenProcess(PROCESS_ALL_ACCESS, false, mw2_pid);
float norecoil[3] = {0};
for(;;){
if(false){// check if the program should close
break;
}
WriteProcessMemory(h, (PVOID)(0xB35980), norecoil, sizeof(norecoil), NULL);
}
CloseHandle(h);
Fix this code, combine with LMG = lol
Moved to Source Code.
Why keep writing to that address? Just NOP the function or write once, and then use VirtualProtectEx() to protect that?
I did that, but I don't want to give away my real code. I gave away this code because it's shit.

But doesn't VirtualProtectEx result in an access violation?
My PRIVATE no recoil only needs to overwrite two bytes.
it's memory writing it will get yo ass banned in....3 seconds?
I used both the posted method and my private method all day yesterday. There was no (automatic) ban. The admins still ban me though.

Over 12 hours seems quite more than 3 seconds...
No youre lying. RJ or gtfo.
If you don't believe me, try this code out for yourself. It's undetected right now. It will be undetected until they move the offset.
Quote Originally Posted by alteriw-norecoil View Post
If you don't believe me, try this code out for yourself. It's undetected right now. It will be undetected until they move the offset.
Considering the aIW staff browse this forum daily, it won't be undetected for long though.
It's for aIW, or Steam, and in both of cases it would be detected. Since when you write to a address in the process they will detected that. Plus I've tried a code like that on mw2 aiw, and it was detected.
If this code is detected, firing your weapon would be detected too. This just nulls the recoil vector and that address gets written to anyways when you shoot.
Quote Originally Posted by alteriw-norecoil View Post
If this code is detected, firing your weapon would be detected too. This just nulls the recoil vector and that address gets written to anyways when you shoot.
Code:
PBYTE _data = 0x90;
memcpy((LPVOID)_data, (LPVOID)<addy>, sizeof(_data));
if(_data == NULL)
{
      return CheatDetectedBooom;
}
but since _data != NULL, the function does not return CheatDetectedBooom!

And why would you write <addy> to 0x90? What's so important about that address?

Revised your code for you (consider it a favor)
Code:
memcpy((LPVOID)0x90, (LPVOID)<addy>, sizeof(PBYTE));
I bet you're just some alteriw admin troll who doesn't even know how memcpy works.

This is probably what you meant:
Code:
BYTE _data = 0x90;
memcpy((LPVOID)<addy>, &_data, sizeof(_data));
/*
// 0x90 != 0, so why not comment out this section?
if(_data == NULL)
{
      return CheatDetectedBooom;
}
*/
Posts 1–15 of 44 · Page 1 of 3
This thread is closed for replies.

Similar Threads

Tags for this Thread

None

Need help?