Cheat Engine

hhhuut · Posted: Fri Feb 13, 2015 3:27 pm Post subject:

If I understand you right, a regular Code Injection should work just well here...

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

hhhuut · Posted: Fri Feb 13, 2015 3:42 pm Post subject:

I'd recommend you to do the injection where the game gets the xmm0 value...

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

hhhuut · Posted: Sat Feb 14, 2015 5:02 am Post subject:

push #30000

Put this before your own code

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

++METHOS · Posted: Sat Feb 14, 2015 12:53 pm Post subject:

Don't use a timer. Instead, try to find something that you can compare against, that will tell you when the enemy has spawned (such as a health value or something). I would start by looking in the data structure for hostility...surely, you will find something in there that changes after the enemy spawns.

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

++METHOS · Posted: Sat Feb 14, 2015 9:14 pm Post subject:

You don't have to use any other injection point/instruction. Study the last step of the CE tutorial covering data structure dissection.

hhhuut · Posted: Sun Feb 15, 2015 10:20 am Post subject:

Yeah, perhaps you'll find a zero-pointer within the structure that will get a valid value as soon as the npc has spawned correctly...

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

hhhuut · Posted: Sun Feb 15, 2015 1:42 pm Post subject:

Do you know about the "Dissect Data"-Option in CE? That one should solve your problem ...

Darcon2k · Cheater Reputation: 0 Joined: 13 Feb 2015 Posts: 48

hhhuut · Posted: Sun Feb 15, 2015 7:47 pm Post subject:

He just subtracts the offset. In your case you have to add -20 after the address.

To the dissect: You mentioned that the npc address shows up in the debugger shortly before the npc really spawns, right?
So when you get an address in the debugger then pause the game before the npc spawns. Dissect the address (think about the -20) and i.e. save a Screenshot.
Then return to the game and resume it. When the npc now is spawned pause the game again and now compare the values in the dissect Window (they update themselves automatically, so you don't need a second dissect window) to the ones you saved in the Screenshot.
If you find changes (e.g. A value that changed from 0 to 1 or a pointer which was 00000000 before and now points to a structure) then repeat this procedure until you can be sure that the value changes at every npc spawned. Later on you can put this as a compare into your script...