Cheat Engine

Dlve · Posted: Sat Mar 08, 2014 5:17 pm Post subject:

When I type in "value" in the bottom text field the pointer shows -> ??????.
So I can't get it to work. Adding the offset doesn't help.

danrevella · Posted: Sat Mar 08, 2014 5:32 pm Post subject:

Dlve · Posted: Sat Mar 08, 2014 5:39 pm Post subject:

It's the game of the year edition. Version is the most recent of course.

++METHOS · Posted: Sat Mar 08, 2014 6:51 pm Post subject:

Dlve-
Did you enable the script first? If so, and it still shows ???, then the instruction that you are using is only accessing your address at certain times (for example, only when the address is getting written to). If you can, use an instruction that accesses the address, not writes to.

Nonetheless, if the instruction handles money, spend (or gain) some money, then try again...all while the script is enabled.

It is always better, if we can, to use an instruction that accesses our targeted address several times per second, as opposed to only when something changes.

Dlve · Posted: Sat Mar 08, 2014 8:11 pm Post subject:

SORRY! I made a huge NOOB mistake. I didn't enable the script first even though you had plainly told me to do that. I should have figured it out myself, sorry.

Yeah, the script works once I've bought something.

Where can I find information on how to do that value addition there or can you tell me?

++METHOS · Posted: Sat Mar 08, 2014 8:37 pm Post subject:

Dlve · Posted: Sat Mar 08, 2014 9:01 pm Post subject:

++METHOS · Posted: Sat Mar 08, 2014 9:10 pm Post subject:

Not sure what your question is.

If you look at the script, all we are doing is moving the register (esi, I think), in to a temporary address that we create so that we can manipulate it as we see fit. Adding the offset was necessary to get to the value that we wanted in the data structure. We knew that the offset was +4, because the instruction that writes to our value is [esi+4]. The register esi holds the base address for our value's structure (probably). 'value' was just a user-defined label that I used. We could have used anything.

Dlve · Posted: Sun Mar 09, 2014 5:08 am Post subject:

I don't know the correct terms so I'm trying to explain in words that I know but since it's difficult for you to understand I'll attach a picture.

In that picture there is "VALUE" below the script right?
How is that done?

What I mean is that I would like to learn how to do that myself so I can do that in other games and other things in this game. Plus, as you said, I need to change the injection point for money. Hope I was clear enough this time...

++METHOS · Posted: Sun Mar 09, 2014 10:43 am Post subject:

That's just an address that I added manually. Click on the button that says 'add address manually'. From there, you just follow the steps that I outlined in a previous post. Of course, for that custom address to work, you have to write the script accordingly (e.g. mov [value],esi).

Dlve · Posted: Sun Mar 09, 2014 12:18 pm Post subject:

There is an instruction that accesses the money address several times but it also accesses four other addresses, so I need to filter them. The question is how can that be accomplished?

danrevella · Posted: Sun Mar 09, 2014 12:30 pm Post subject:

++METHOS · Posted: Sun Mar 09, 2014 2:02 pm Post subject:

There are several ways to do it. Look at Geri's tutorial covering data structure dissection.

Since there are only 4 addresses, I would check their registers to see if there is a unique identifier. You can do this by adding all 4 addresses to your cheat table, and individually, one-by-one, right-clicking on them to see which instructions access them. In the debugger windows, at the bottom, you can see the value of each register...there, you may find that simply comparing a register will work.

Dlve · Posted: Wed Mar 12, 2014 12:22 pm Post subject:

I'm not sure what I should be looking for in the bottom of the debugger. I mean the addresses for esi etc. are different but so what? In my humble opinion Geri says nothing about how he makes the code work for his unit only and not the enemies also. If it's there in the script, I'm in trouble because I'm no coder and that code looks nothing like I've seen so far.

++METHOS · Posted: Wed Mar 12, 2014 2:07 pm Post subject:

Checking the register values is only one way to filter out unwanted addresses. It doesn't always work. Of course esi is different, that is the register that holds the base address of your targeted value. We are interested in the other register values. Of course, if you find a unique identifier, you will have to close out the game etc. and check it again to see if it's a static value or not, because we want to ensure that whatever we use for our compare will be consistent and reliable.

Regarding the script, all I can say is learn more about assembly language and review tutorials that cover 'dissect data structures'.

Here is an excerpt from Geri's script: