Saints Row IV (Update 3)
Posted: Fri Jul 14, 2017 12:35 pm
Made by low_density
Hi, I've played this game for a while, and noticed that not a lot of people have created trainer for this popular game. I tried using trainers from one developer but most of his trainer don't work for me (you should know who is this Razz). I used another trainer for a while, but since the update 3 for the game came out, the trainer sort of corrupts the game, so i decided to come up with my own table. So here's my table, please help to test it out and feedback if it works for you.
*Important: Player pointer script needs to be enabled for the rest of the scripts to work. Most of the other scripts in the table have AOB scanning feature, but for the player pointer and weapon pointer script, because I can't find a unique signature for the address, I made it static (so it only works for update 3). But it is easy to update: Use the aob provided in the money script and then do an Array of Byte search (remember to uncheck the Writable option under the search), and then open the result (should be only 1) in disassembler, and find an opcode similar to "movd xmm0,[edx+00001DF8]", and then right click on it, and "Find out what addresses this instruction accesses" in the disassembler view. You will see a value, then right click and see the registers for that value. Look at the value edx holds (this is the player pointer value). Then, manually add an address and enter the value that is inside edx.
After manually adding the address of the player pointer, right click on it and select "Find out what accesses this address". There should be a few instructions that address the addresses, this will be a trial and error process. I will list them in steps:
1) Click on each of the instruction, starting from the first, and then select "Show disassembler" option
2) the memory view window should open and the disassembler portion will show the instruction
3) right click on the instruction and select "Find out what addresses this instruction accesses" again.
4) Do the above steps 1-3 until you can find an instruction that only accesses the player pointer. That will be the starting address that you need to update for the player pointer script in the case of future updates.
For now, enjoy and please provide feedback!
Hi, I've played this game for a while, and noticed that not a lot of people have created trainer for this popular game. I tried using trainers from one developer but most of his trainer don't work for me (you should know who is this Razz). I used another trainer for a while, but since the update 3 for the game came out, the trainer sort of corrupts the game, so i decided to come up with my own table. So here's my table, please help to test it out and feedback if it works for you.
*Important: Player pointer script needs to be enabled for the rest of the scripts to work. Most of the other scripts in the table have AOB scanning feature, but for the player pointer and weapon pointer script, because I can't find a unique signature for the address, I made it static (so it only works for update 3). But it is easy to update: Use the aob provided in the money script and then do an Array of Byte search (remember to uncheck the Writable option under the search), and then open the result (should be only 1) in disassembler, and find an opcode similar to "movd xmm0,[edx+00001DF8]", and then right click on it, and "Find out what addresses this instruction accesses" in the disassembler view. You will see a value, then right click and see the registers for that value. Look at the value edx holds (this is the player pointer value). Then, manually add an address and enter the value that is inside edx.
After manually adding the address of the player pointer, right click on it and select "Find out what accesses this address". There should be a few instructions that address the addresses, this will be a trial and error process. I will list them in steps:
1) Click on each of the instruction, starting from the first, and then select "Show disassembler" option
2) the memory view window should open and the disassembler portion will show the instruction
3) right click on the instruction and select "Find out what addresses this instruction accesses" again.
4) Do the above steps 1-3 until you can find an instruction that only accesses the player pointer. That will be the starting address that you need to update for the player pointer script in the case of future updates.
For now, enjoy and please provide feedback!
