Cheat Engine

[OldCheatEngineUser]

hey,

something that i never messed with is: full injection.
so i dont know how it works technically, and i dont know whats the difference between full injc' and code injc' both seems the same, well almost the same.

i hope someone can explain it in details, and in a technical way, because i searched a lot n web and didnt find a post or website explaining this little thingy and it uses.



thanks in advance

[FreeER]

Well if open both up on the same instruction and look at them both the differences are pretty simple and obvious

First the Full injection template adds some comments at the top to help you (or someone wanting to update your script later) keep track of things when the game updates a month after you created the initial hack or if it's just a random table/script someone found online. It includes the process name, a place for you to write the version, the date, and your computer's username as well as a place holder for what the script does.

Personally I tend to delete that part since I save my cheat tables with the process name and don't tend to update them... I probably shouldn't but. Ah, I should note that I pretty much exclusively use the AOB template at this point, it's pretty much the same as Full Injection but takes it one step further by scanning for the original bytes in memory instead of assuming they'll be at the same address in memory.

Next the Full injection template uses define so that you can use names instead of the address and bytes to disable the script (we'll get to that)

Next the Full injection template uses assert to make sure that if the game has updated and has different code at that address it doesn't try to change it anyways, possibly crashing the game, the script will simply fail to enable (aob scans also do this, mainly because if the bytes (that aren't wildcards) have changed then it can't find the address to write at)

Next the Full injection template does not use the exit label. No real difference here except that when writing your own code that wants to go back to the point after originalcode you have to use the returnhere label instead of exit (or create it yourself). The exit label does allow you to add some common code for all branches to run before returning though.

Next you get to the main difference between the two, the Full injection template auto generates code to disable the script by writing the original bytes back into memory and free the allocated memory. It also added the necessary framework code to assign it to a table without having to manually run the framework template.

Finally the Full Injection template includes a comment that documents the assembly code you're injecting on as well as the 10 previous and 10 following instructions. Making it much easier to come back and write an Array Of Bytes scan later (or just do a search) or fix a broken aob scan because it included a value that changed, or just find the original bytes so that you can fix the code in case you made a mistake when modifying the script...

I do leave that part in my scripts because I have often times found it quite useful

[OldCheatEngineUser]

ehm, i found your reply is useful.

it helped me, thanks you.