Cheat Engine

[Verontier]

So, I was using CE earlier today for infinite health and stamina. After testing it for about an hour, I saved and shut everything down. A little later on I started it back up and added vigor with no problems, I tested, saved, and shut everything down again. About a half hour ago, I decided to add gold to the list (which worked) and, before I could save properly, my 3 year old decided to hit the "X" at the top, prompting the warning and asking if I wanted to save before exiting. I checked to make sure everything was still as it should be, which it was, so I hit yes to save and exit. I started CE back up to create a trainer but what loaded for my game was not what was supposed to be saved. The 4 address and values are totally wrong and the descriptions are gone, as well. Is this a known bug?

CE v6.6
Kingdoms v17.2
Windows 10 Pro x64

[rog9001]

☆ I think this post should be moved to "Cheat engine" section sins this is more related to CE itself rather then AA scripts and finding addresses and all that stuff. ☆

¤ Never had that happen to me. If i by accident press the "X" and then click save & exit it would just well... save what i had and exit. ¤

[Kavvman]

Kingdoms is a unity game so the code moves around. Maybe thats what happened.

[Verontier]

@rog9001 Yeah, I guess I did post this in the wrong place. My bad.

@viZZion It saved and loaded everything just fine for most of the day (started at around 11am or so) until the "X" at the top was hit and I went ahead and saved through it.

[rog9001]

What addresses did you have saved? Normal ones which you found with ce? Or were they: static, pointers or scripts?

[Verontier]

Pointers. That is why I even bothered to post about it, lol. So much work for 6 little cheats, gone.

On a side note: I redid everything and the problem has not occurred again I wasn't even able to reproduce the problem. I'll just chalk it up to human error.

[mgr.inz.Player]

Pointers. How many pointerlist rescans you made?

[Verontier]

I have absolutely no idea how many times I performed rescans, it was a LOT.

If I had to make a guess I would say 300+ total scans (address, pointers, and rescans) for both times, the majority going to the first attempt. And that was getting the pointer rescans down to 150-300 pointers (from tens of millions each initial scan) for the final results. Luckily it saves rescans. . .

[mgr.inz.Player]

I think your pointers were saved fine. They just weren't stable.

To clear things up. Did you:

1 Found address of something. Started pointerscanner. Let's say you saved pointerlist as "something.ptr"

2 restarted the game. Found new address of something.
3 opened pointerscanner window, loaded "something.ptr"
4 you clicked "rescan" and filled in new address. Saved it as "something rescan 1.ptr"

5 restarted the game. Found new address of something.
6 opened pointerscanner window, loaded "something rescan 1.ptr"
7 you clicked "rescan", and saved it under "something rescan 2.ptr

8 restarted the game. Found new address of something.
9 opened pointerscanner window, loaded "something rescan 2.ptr"
10 you clicked "rescan", and saved it under "something rescan 3.ptr
(repeat this procedure)

11 after several rescans (5, 10, 20 or more) you chose one and added it to the list.


First scan usually has many pointers. Thousand, tens of millions, tens of billions. It doesn't matter. Rescanning is the most important part. And you won't get 100% guarantee that pointers which have left will be 100% stable, even after 50th rescan (or more).


In your case, pointers you choose just stopped to work. It happens.

[Verontier]

Yeah, I did it exactly as you instructed.

My problem was when I loaded my .CT file the pointer numbers changed vastly (had a txt doc with originals but deleted it) from what they originally were and the description, such as health, stamina, etc., was completely blank.

I used the above mentioned txt to select the same pointers and am now able to run the cheats with no problems. I even generated a successfully working trainer for others to use with no complaints, so far. . .

[rog9001]

when looking for pointers did you set the last offset ("pointers must end with specific offsets")?
If no then you should. You might be able to find more stable pointers. To get the offset just press F5 on the address you find and then see what appears in the small window. If you get instructions which have 1 exactly same register e.g. [eax+000000F4] then you take the offset in the brackets in the example it would be "F4" and then input it and only then start scanning.

[mgr.inz.Player]

@Verontier, do you use any "Lua extensions" ?



@rog9001, you are right. About "last offset" thing, you are right too. But, there are exceptions.

Some time ago I found an address which keeps data I want. I could find it in 3 minutes (few memory scans, value must be between [a,b], changed/unchaged, ..., value must be between [c,d], ...)

All level5 pointers (and lower) weren't stable. For 5level pointer scanning we do not need ending offset, scanning is still quick. Especially when we use "first element of pointerstruct must point to module", a very nice feature (I think it should be ticked by default). I use it most of the time.

This address was accessed by only two instructions (and those also accessed other addresses):

fstp dword ptr [eax+14]
and
ucomiss xmm0,[ecx-08] ( this ECX-8 was equal to otherReg+14)


I tried level6 with ending offset: 14, without success, and: -8, also without success.
I tried level7 with above ending offsets, without success.

So I made full level6 pointer scan ("must point to module" enabled), then 5 rescans on my machine, 6th rescan on brother machine, and 7th rescan was made on CEF member machine. Pointers which have left, all of them, had ending offset 1BC.

[Verontier]

@rog9001: Yeah, I set the last offset during first pointer scan of each cheat I was going for.

@mgr.inz.Player: No. I really haven't had the urge to use any Lua extensions, so far. I really want to expand on my knowledge of CE 'as it is' before moving on to user *written* scripts.

[rog9001]

@mgr.inz.Player oh...

Why not just make a script with the lines

[mgr.inz.Player]

@rog9001

I wrote: