Cheat Engine

J3RRY · How do I cheat? Reputation: 0 Joined: 09 Jul 2013 Posts: 6

I'm trying to modify an old script of mine to be more robust. Someone tried to use it, and found that the addresses I reference in the scripts don't correspond to the same code/memory locations in his game. We have the same updated version of the game; and we're both using Win7 64-bit. I've been able to use this cheat table on both my Windows 7 and Windows Technical Preview partitions. I've even reloaded my computer once or twice since I last touched the cheat table. I'm not sure why his computer is mapping the game offsets differently.

The game is Jedi Outcast. In my scripts, I use offsets for the corresponding DLLs, such as: "jk2gamex86.dll"+F7107. I figured this would be a reliable way to find that address. But for this guy, these same offsets point to different areas of code/memory. To solve this, I've been modifying my scripts to use AOB scans to find the address. Things were going along smoothly until I hit some of my more in-depth scripts, which have instructions that reference addresses directly in game.

For example:

Dark Byte · Posted: Sat Nov 15, 2014 6:19 am Post subject:

That means he did not have the same version as you(he's either wrong or lying)

Anyhow, try an aobscan to find it and then use the reassemble(originaladrress) aa command i, the new memory block

J3RRY · How do I cheat? Reputation: 0 Joined: 09 Jul 2013 Posts: 6

Hmm, I'll consider that possibility Confused

Does reassemble() restore the original code to that memory location? I mean, is CE saving the original bytes and simply putting them back? If so, that'd be perfect since I have no idea which addresses this guy is seeing.

Dark Byte · Posted: Sat Nov 15, 2014 1:04 pm Post subject:

Readmem(address,size) will read those bytes and put them at the place of readmem
Reassemble is like that but will adjust the bytes if they are dependant on the position of the instruction