|
People tend to screw up and create code-caves in the main .exe or some other module other than the one which contains the code to 'hack'. This will result in jump's that alter in distance (as they are intermodular), so the jumps end up pointing to the wrong place once the module(s) shift around.
If you can find a decent spot, that is always empty, inside the same module you are wanting to intercept code, then you can get away with it quite easily. And you won't have to do anything more difficult then find the module base each time you want to inject (or poke) the code.
In some games, this is just not possible, and caves need to be allocated for the stuff.
|