Cheat Engine Looking for string in memory

[lokatylokacz]

Hey!

I wanna make little anti-afk script at one of private servers of Tibia, my problem is that I can't find (even regular) address of string I need.

Here is 20 secs YT vid that shows my problem.




I can't find pointer to random sum (marked in red on screen) I can't even find normal address to this value...

But I found pointer to title of this window (marked in blue).

Each time I try to "Rescan memory - Removes pointers not pointing to the right address" it shows me 0 results.

Kind regards,
LoK

[HappyMajor]

if u dont get anything you can use Tesseract for image search should be easier that way

[lokatylokacz]

Originally Posted by HappyMajor

if u dont get anything you can use Tesseract for image search should be easier that way

I made script in AutoIT that works but I want to use more instances of that script at once on let say 4 game clients or sometimes on 2 or even on 8 + I would love to have my screen for other stuff than just that, so I prefer to minimize game clients and work just on memory.

[HappyMajor]

Originally Posted by lokatylokacz

I made script in AutoIT that works but I want to use more instances of that script at once on let say 4 game clients or sometimes on 2 or even on 8 + I would love to have my screen for other stuff than just that, so I prefer to minimize game clients and work just on memory.

i may have a solution add me on discord and we can talk abit HappyMajor
#9305

[lokatylokacz]

Still need any kind of help much appreciated !
Teach me master ! XD

[lokatylokacz]

Still looking for help ;/

[lokatylokacz]

BUMP

Ok now just for knowledge xD I don't need this anymore but I'm still thinking how to deal with it xD

[slide9595]

You need to read the number of characters that contains the string as bytes, then you must convert the result (byte by byte) in ASCII or Unicode.

[IZensersky]

Okay since no one helped you, I will. You can't find a pointer to it because the string seems to be reallocated every time. What you should try is open any of these addresses in memory view and look for any past string references there. If you manage to find them, count how many bytes they are apart. Then use that amount to predict the next allocation location and attach a debugger to that address on "Find out what accesses this Address".
That will only work if any past references aren't removed. You could also try, attaching a debugger("Find out what accesses this address") to any of these addresses and look what accesses it and try to make sense of it or find where it gets deallocated then work your way back until you find the location of where the string gets put together. Then you could just hook that function and that would be it.