Cheat Engine

ralfonat · Newbie cheater Reputation: 0 Joined: 03 Nov 2022 Posts: 11

hey there,

so the basic AOBScan template fails because the address is not unique. I know however that there are only 3 exactly identical results and it is always the first one.

So since I cannot find a good documentation on AA:aobScan I found the Lua:aobScan where I can simply check the number of results and use the first one in the return array.

Now I am having difficulty incorporating this into the regular aob AA template.

Can someone give me a pointer? Basically I am just trying to put the correct found address into the INJECT symbol, but there seems to be some sort of magic going on in the AA:aobScan symbol registering that I cant seem to replicate.

This is what I have so far and it won't work:

ParkourPenguin · Posted: Sun Dec 10, 2023 12:31 pm Post subject:

You don't need all of that. You aren't calling a CE Lua function from within the game's process- you're just executing a bit of Lua code when the script is enabled.

ralfonat · Newbie cheater Reputation: 0 Joined: 03 Nov 2022 Posts: 11

Hey ParkourPenguin,

thank you so much for your reply. That made it work right away. Help me understand this please, as I would have never come up with it.

What does the "return" in a root lua block actually mean? I mean there is really nothing to return to as we are not in a function?

Is that documented somewhere?

So of course now the program decided to shuffle things up and now it's not the first anymore. How would I go on about injecting *ALL* found memory locations with being able to revert the injects on disable?

Since the return statement will end the call right there?

I tried to emulate the "return" with:

ParkourPenguin · Posted: Sun Dec 10, 2023 4:21 pm Post subject:

A {$lua} block basically contains a Lua function that gets called when the script is run. The string it returns gets substituted back into the script. If it doesn't return anything, nothing gets substituted.

AA scripts, and by extension {$lua} blocks, get executed twice when the AA script is run. The first time is to check the syntax of the AA script- this doesn't really do anything significant other than complain if you did something wrong. If that's successful, the script runs a second time where it actually allocates memory, writes instructions/values, registers symbols, etc.
{$lua} blocks need to account for this. CE sets a local variable "syntaxcheck" before the first line in {$lua} blocks for this purpose.
In the case of the script I posted, it just defines the symbol of the injection point to be wherever for the syntax check stage. It's not important what exactly the symbol is- the only important matter is that it's defined. When it's not doing a syntax check, it actually needs to do the aobscan.

ralfonat · Newbie cheater Reputation: 0 Joined: 03 Nov 2022 Posts: 11

thank you *so* much for the detailed explanation, that really helped me cross the bridge here Wink

There is just one unanswered thing for me:

ending the ${lua} block, are these 2 "identical" ?

ParkourPenguin · Posted: Mon Dec 11, 2023 1:21 pm Post subject:

No. The Lua function `autoAssemble` runs a new auto assembler script. It's like when you click the "Execute" button at the bottom of a new AA script window. Calling `autoAssemble` from within a {$lua} block has nothing to do with the AA script that the {$lua} block is in- it's an entirely new AA script that's being executed.

ralfonat · Newbie cheater Reputation: 0 Joined: 03 Nov 2022 Posts: 11

OK, I'm still not 100% sure I understand the purpose of autoAssemble then.

Anyways, back to the question that drags on me:

the

ParkourPenguin · Posted: Tue Dec 12, 2023 12:36 pm Post subject:

ralfonat · Newbie cheater Reputation: 0 Joined: 03 Nov 2022 Posts: 11

now everything is clear. thanks again SO much for helping out. much appreciated!