This is the thing with games these days.
Moving addresses...
The CODE of the game is always in the same spot, but the addresses that the code use to store lifes, etc move around in memory..
What you need to do is find the CODE that decreases lifes or something in a game .. this code will point to a register + <a number> .. the address in the register + the number = the location in memore of the lifes.
I tend to go a bit further with this when i make a trainer, i find the code (usually an asm SUB command) and remove it :) the lifes will no longer decrease.
There's a tool out there, if it still is out there that can help with this. It's called TSearch.. it basically does the same thing as my own trainer creation tool but a little more 'difficult'.
In Tsearch, select the game process (run game first of course), use it's normal value location system to find the value you want to find, say, lifes:
Look in the game, say there's 3 lifes left.
-Go to TSearch, search for 3, with 2 bytes (doesn't always work but it will not find millions of hits this way)
-Go back to the game, loose a life
-Go to TSearch, search for 2
-Repeat until you know which address hold the amount of lifes. Add the address to the list on the right.
-Now, go to one of the menu's and "enable debugger"
-Right click on the address in the list on the right and click on "Autohack"
-Go to the game, loose a life.
-Go to TSearch, and open the autohack window (same menu as enable debugger i think)
-There should be a little machine code command in the list in that window .. click on the little box in front of the command to turn it on.. and voila..lifes will no longer decrease when you die.
-Select the machine code command and click on "TMK", and then "Button Script", a small window will appear with a little text in it .. there's the address that you need to NOP (those are the list of 90's you see in the text, 90 = NOP)..
WriteProcessMemory to this address (in decimal, not hex, like the text shows) with the 90's and your trainer will kill the CODE to decrease the lifes :)
Guess i'll code something.
Tracer
Moving addresses...
The CODE of the game is always in the same spot, but the addresses that the code use to store lifes, etc move around in memory..
What you need to do is find the CODE that decreases lifes or something in a game .. this code will point to a register + <a number> .. the address in the register + the number = the location in memore of the lifes.
I tend to go a bit further with this when i make a trainer, i find the code (usually an asm SUB command) and remove it :) the lifes will no longer decrease.
There's a tool out there, if it still is out there that can help with this. It's called TSearch.. it basically does the same thing as my own trainer creation tool but a little more 'difficult'.
In Tsearch, select the game process (run game first of course), use it's normal value location system to find the value you want to find, say, lifes:
Look in the game, say there's 3 lifes left.
-Go to TSearch, search for 3, with 2 bytes (doesn't always work but it will not find millions of hits this way)
-Go back to the game, loose a life
-Go to TSearch, search for 2
-Repeat until you know which address hold the amount of lifes. Add the address to the list on the right.
-Now, go to one of the menu's and "enable debugger"
-Right click on the address in the list on the right and click on "Autohack"
-Go to the game, loose a life.
-Go to TSearch, and open the autohack window (same menu as enable debugger i think)
-There should be a little machine code command in the list in that window .. click on the little box in front of the command to turn it on.. and voila..lifes will no longer decrease when you die.
-Select the machine code command and click on "TMK", and then "Button Script", a small window will appear with a little text in it .. there's the address that you need to NOP (those are the list of 90's you see in the text, 90 = NOP)..
WriteProcessMemory to this address (in decimal, not hex, like the text shows) with the 90's and your trainer will kill the CODE to decrease the lifes :)
Guess i'll code something.
Tracer