Cheat Engine

[Lordpete]

Hello everyone,

I'm currently working on a project that involves real-time analysis of game data from Hollow Knight, but I'm having trouble locating specific memory addresses that control character movement, death states, and boss positions. Despite using Cheat Engine's scanning features extensively, I've been unable to pinpoint the relevant addresses that would allow me to track and modify these game behaviors effectively.

For example, I was trying to find out the address(value) of my character
current position. Since I know nothing about this value, I chose the Unknow value for my first scan. As I changed my position, I switch the scan into changed value. It did eliminate an considerably amount of addresses but still left around 500 of them that won't change no matter how I tried.

I'm wondering how to handle a situation like this: I can access real-time information from the game, but it does not offer a simple way to read data, such as a log file. Additionally, I feel that using screen capture to analyze the current game state in real time would be too cumbersome, and I doubt my computer could handle the subsequent processing.So, I've considered using memory reading techniques, but I'm not sure if it's the appropriate approach. Is there a simpler and more convenient method available?

I would greatly appreciate any guidance or tips from those who have tackled similar challenges. If anyone has scripts or pointers relevant to Hollow Knight that they're willing to share, or can offer advice on advanced scanning techniques that might be more effective, it would be incredibly helpful.

Thank you very much for your time and assistance. I look forward to any suggestions you might have!

Best regards,

[ParkourPenguin]

Hollow Knight seems to be made using Unity. Try CE's mono features. If you search "cheat engine mono" I'm sure you'll find lots of videos.

There are probably more appropriate tools for reverse engineering Unity games, but I'm not familiar with any.

Regarding scanning for position, the value type is probably float or double to simulate "continuous" movement. Have "Simple values only" checked. The value probably isn't 0- I'd filter out the plurality of valid values by only scanning for nonzero values for at least the first scan. Check "Lua formula" and use "value~=0" (no quotes) for the scan query. "Separate Lua state" can be used with this query to speed up the scan significantly. That can't be used for all Lua queries, and don't forget to uncheck these after the first scan is done.

For next scans, increased/decreased can give you better results faster than changed/unchanged. There's no way to know which way is positive, so worst case you'd need to try both. I'd still try changed/unchanged first to try to avoid possibly doing this more than once (sometimes I'm my own worst enemy when I forget which way was which after 10+ scans). "Compare to first scan" w/ "unchanged value" can also help a lot if you remember to normalize your position for the first scan. "Value between %" using "99.999" and "100.001" may be better than "unchanged value" when the physics engine isn't exactly deterministic.

Beyond that, it's fine to randomly change values you think might be correct and hope it doesn't crash. Always have backups of your saves.

[Csimbi]

Somewhere in HeroController: