Cheat Engine

[number1286]

Hello All -

I dont usually post on forums, just read. But, I've been doing lots of research on this particular problem and am unable to find any concrete literature to educate myself. I'll try to provide enough information to make my question clear, no more no less. If my questions seems too ambiguous to answer, please notify me. Without further ado ...

I have been dabbling with Cheat Engine 6.1 and feel I have a pretty strong grasp on its usage. I'm a computer science major and have plenty of programming experience. I've developed a little C-program to simply iterate through an array of offsets (which were obviously found via Cheat Engine), after the iteration is complete I arrive at the memory address which holds the score of my game (Spider Solitaire). This is no problem, finding offsets and navigating through pointers is non-issue. I go through and through the pointers untill I arrive at a pretty green colored memory address - By that I mean it's colored green by Cheat Engine meaning it's static.

That green memory address is where I start my function which successfully adds the offset, reads the value, adds the offset to that read value, reads the new value. Okay now I can state my issue: That pretty green (static) memory address, changes when I close Spider Solitaire. More specifically, when I terminate Spider Solitaire, and reopen it, I trace pointers, and I arrive at a different green memory address. I need to figure out how to make my little C-program not "break" every time Spider Solitaire is terminated and reopened.

I've seen psudocode where people write ("Spider Solitaire.exe" + Offset). How can I determine the address of "SpiderSolitaire.exe" in C? Or is that not what I need to do? Those pretty green memory addresses that I arrive at change upon termination (and subsequent reopen), so they cannot be hard coded into a little program, so what can be? I again may be wrong but, am I looking for the base address to the process? Alot of terminology is used very loosely and it creates confusion on my part.

Thanks for reading, I look forward to your assistance. The answer very well may be right underneath my nose?

[Dark Byte]

You are looking for the base address of the module
You can use the psapi library to get it, or use toolhelp32snapshot followed by module32first/module32next to find tha base address (which coincidentally matches the hmodule value)

[number1286]

Short, accurate, and best of all - helpfull!

Thanks Dark Byte!