Cheat Engine

Rawing

Hi again.
I'd like to know if there's a way to filter scan results by whether they're constantly being accessed (Think of the "find out what accessed this address" function).

The reason for this is simple:
What I'm searching for is a pointer to a value of the player model - the value affects how the player looks. This value, and therefore the pointer I'm looking for, is being accessed/read several times a second, probably because the game is busy rendering the player model.
This means that anything that points to this value, but isn't accessed 30+ times a second, is useless to me - but I can't manually add every scan result to the address list, then find out what accesses this value, for 50+ addresses.

I don't expect Cheat Engine to have a feature like this, but there might be a way to do this with a lua script, right? There doesn't seem to be a lua function to "find out what accesses this address", however.

Dark Byte · Posted: Thu Dec 26, 2013 5:58 am Post subject:

you can use

Rawing · Posted: Thu Dec 26, 2013 7:18 am Post subject:

Thanks for the quick reply.
I just tried this with the Cheat Engine Tutorial, since I figured it needed to poll some values, and it didn't work. I skipped to step 2, found the health value, and found it's being accessed about 10 times per second. My little lua script, however, was unable to detect that.

Dark Byte · Posted: Thu Dec 26, 2013 7:37 am Post subject:

bptAccess sets a data breakpoint. Without it, or using bptExecute, it would be a code breakpoint

Also don't use sleep as the debugger will wait till that sleep is done becore it calls onBreakpoint(best use a timer, or run the code in a thread and don't touch the gui)

Rawing · Posted: Thu Dec 26, 2013 8:52 am Post subject:

Yep, I just noticed the timing's weird. For some reason, onBreakpoint gets called AFTER the

Dark Byte · Posted: Thu Dec 26, 2013 9:07 am Post subject:

split this:

Rawing · Posted: Thu Dec 26, 2013 9:55 am Post subject:

Oh, I thought I needed to keep the "main thread" alive. Welp.
Anyway, I got it to work thanks to you, though there're a few racing conditions (simultaneous call of onBreakpoint and timer_tick = ouch ouch ouch), but what the hell. Thanks.

Here's the code, free to steal for anyone.

Dark Byte · Posted: Fri Dec 27, 2013 9:56 am Post subject:

1: In the onBReakpoint routine you must return 1 to indicate that you don't wish the gui to be updated.

2: That is because you have created a secondary foundlist, overriding the foundlist in cheat engine's gui. (you could also just use the foundlist of the gui instead of creating a new one)
Find out what accesses crash not sure. It depends on the game. I recommend waiting a few seconds between removing a breakpoint and adding a new one, since there may be a backlog of breaks waiting. (e.g 10 threads may have broken on that address, but so far you've only handled 1. You need to handle the 9 others before you can reuse that specific hardware breakpoint)
If you add a new one to soon, the data might be lost that a certain breakpoint should be ignored instead of emulated as unhandled (Especially since there are only 4 hardware breakpoints that can be used)

Rawing · Posted: Sat Dec 28, 2013 4:09 am Post subject:

Thanks again for your help.
I didn't change the code to wait between removing/adding breakpoints because I didn't want to mess with the timer or add a sleep, but it seems to work perfectly now regardless. Even the crash on "find out what accesses this address" seems to be gone, though I didn't test that extensively.

I also added the feature to set a minimum number of accesses per address.