xanupox
16th August 2004, 07:14
We may not be able to hack BFV anymore. I have tried the following with no success.
1) Jumping from the ORIGINAL CODE to a code cave, hacking there and jumping back to the game later in the code. All code skipped was recreated in the code cave. = kick GAMEHACK
2) Jumping from the ORIGINAL CODE to the code cave, recreating all ORIGINAL CODE inside the code cave, WITHOUT hacking anything and jumping back to the ORIGINAL CODE. = kick GAMEHACK
3) Short Jumping from the ORIGINAL CODE to an inert area of code near the area I want to hack. Double jumping from there to the Code Cave, doing the hack inside the cave, recreating skipped code and jumping back out. =kick GAMEHACK
4) Nopping = kick GAMEHACK
5) Jumping out WAY BEFORE the breakpoint address, to code cave, recreating all code + hacked code and jumping out, = did not work, as the jump out was skipped on the memory read.
I am out of ideas, and after spending 30+ hours coding over the last 2 days.. I think it maybe safe to say BFV will be without hacks for awhile.
My overall findings have provided the following:
a) PunkBuster seems to be knowledgeable of common code cave address ranges. Possible they took all the addresses from Tsongkie's Code Cave tool.
If that is indeed the case, then any jumps out from the BFV original code that is pointing to those address ranges would be considered GAMEHACK. I sort of proved this by making a simple Jump OUT, recreated original code inside a code cave... one of the addresses provided by Tsongies. Then jumped back to the original code. I was kicked for GAMEHACK. Even though I had no real hack going. There was nothing at all enabled as far as the hacks go. Just a reroute of the original code.
So giving punkbuster the most credit possible, lets say they have now enabled thier software to be knowledgable of common code cave hex addresses. If the PB scan detects a jump to one of these offsets then it kicks you.
If PB is even more evolved than I think, then it could be actually READing the original code, and comparing it against a template of what the code is supposed to be. If ANY change at all is noted, then it is considered a GAMEHACK.
I have tried to recode with hacks in various areas of the game, I get a different GAMEHACK # for each one... that makes me think punkbuster KNOWS where it is, on the scan.. and that punkbuster KNOWS what is supposed to be there. If it reads the area for nametags and detects any deviation from the orginal code, then it kicks for GAMEHACK #80209, nametags hack.
I have gotten maybe 4-5 different numbers, so punkbuster has a good idea of where it is looking and what it is looking for at each area.
I am really tired at the moment, so I will be taking a day or two off to relax and let others gather data. Maybe we can still overcome this. But if this was the last days of hacking, then maybe BFV will be worth playing again.. based on SKILL.
1) Jumping from the ORIGINAL CODE to a code cave, hacking there and jumping back to the game later in the code. All code skipped was recreated in the code cave. = kick GAMEHACK
2) Jumping from the ORIGINAL CODE to the code cave, recreating all ORIGINAL CODE inside the code cave, WITHOUT hacking anything and jumping back to the ORIGINAL CODE. = kick GAMEHACK
3) Short Jumping from the ORIGINAL CODE to an inert area of code near the area I want to hack. Double jumping from there to the Code Cave, doing the hack inside the cave, recreating skipped code and jumping back out. =kick GAMEHACK
4) Nopping = kick GAMEHACK
5) Jumping out WAY BEFORE the breakpoint address, to code cave, recreating all code + hacked code and jumping out, = did not work, as the jump out was skipped on the memory read.
I am out of ideas, and after spending 30+ hours coding over the last 2 days.. I think it maybe safe to say BFV will be without hacks for awhile.
My overall findings have provided the following:
a) PunkBuster seems to be knowledgeable of common code cave address ranges. Possible they took all the addresses from Tsongkie's Code Cave tool.
If that is indeed the case, then any jumps out from the BFV original code that is pointing to those address ranges would be considered GAMEHACK. I sort of proved this by making a simple Jump OUT, recreated original code inside a code cave... one of the addresses provided by Tsongies. Then jumped back to the original code. I was kicked for GAMEHACK. Even though I had no real hack going. There was nothing at all enabled as far as the hacks go. Just a reroute of the original code.
So giving punkbuster the most credit possible, lets say they have now enabled thier software to be knowledgable of common code cave hex addresses. If the PB scan detects a jump to one of these offsets then it kicks you.
If PB is even more evolved than I think, then it could be actually READing the original code, and comparing it against a template of what the code is supposed to be. If ANY change at all is noted, then it is considered a GAMEHACK.
I have tried to recode with hacks in various areas of the game, I get a different GAMEHACK # for each one... that makes me think punkbuster KNOWS where it is, on the scan.. and that punkbuster KNOWS what is supposed to be there. If it reads the area for nametags and detects any deviation from the orginal code, then it kicks for GAMEHACK #80209, nametags hack.
I have gotten maybe 4-5 different numbers, so punkbuster has a good idea of where it is looking and what it is looking for at each area.
I am really tired at the moment, so I will be taking a day or two off to relax and let others gather data. Maybe we can still overcome this. But if this was the last days of hacking, then maybe BFV will be worth playing again.. based on SKILL.