Cheat Engine

[exile]

Hello all, I'm new to this forum and the ASM language. Anyway.. I was just wondering.. As you all know, CE has a useful Change Register feature and I usually use this to set the EIP of certain addresses so that I can jump into my codecave easily..

The game is MapleSEA and I have to change the EIP thingy because apparently the game calls an API to check that particular portion of its memory for any modifications.

My question is : I can easily make a trainer to insert the required data into the codecave, however I need to jump to it and I can't add my own code (JMP) because it is protected, so.. is it possible to integrate the Change EIP feature into a trainer? I need it to automate this part because I'm planning to distribute it among some other friends which are far worst off than me in using CE.

Forgive me if I sound noobish or this has already been asked, but I really need to know.

[Dark Byte]

This has been asked often, and I keep saying it's not worth it.

Just get the cheat engine source and change the userinterface with the layout of your trainer. Then add some automation like selecting the right process, activating the debugger, enabling the kernelmode routines, registerng the data types, monitoring data, getting the modules, setting reg changing breakpoints at the same spot, let the disassembler code the scripts for you and let the auto assembler inject those autogenerated scripts.

You're going to need a lot of the functions of cheat engine, so this is the best solution.


in case you're wondering what happens when using the change register option:
The debugger gets enabled
It gets all the threads and modules and keep a list of it
Then it sets the hardware breakpoint in each thread and each newly created thread
Then it waits for the game to hit one of those breakpoints.
Then it confirms if the breakpoint is what it was waiting for, gets the context of the thread, edits the registers to what you want.
Then removes the breakpoint, sets the thread to single stepping mode, do 1 step, wait for the step to complete, set the breakpoint back, and continue and wait again

And then i'm not even talking about the stuff that happens when using the kernel debugger

[exile]

Lol alright thanks alot, I'll try it out