|
Cheat Engine The Official Site of Cheat Engine
|
View previous topic :: View next topic |
Author |
Message |
Golokopitenko Newbie cheater Reputation: 0
Joined: 29 Jan 2018 Posts: 18
|
Posted: Fri Mar 02, 2018 10:39 am Post subject: Only a few steps away from removing FoW |
|
|
So far I have found the address responsible for unit's sight range, and the region of the memory associated to the map grid that is, the state of each tile in the map (and by state I mean whether it's explored/unexplored/visible, if it's passable and what terrain 2D image is displayed).
I first thought I'd just turn the sight range to a very high number, but for some reason it seems to be capped. While the in-game stat will go to very high numbers, the actual sight radius won't become bigger after it reaches a certain size.
Then I thought about checking what accessed the sight range address (it's a green one). One of the addresses that accessed it, when changed into a code that did nothing made all explored terrain become permanently visible, which is good, but not good enough.
I am out of ideas. Finding the memory region associated to the map isn't much help, as I don't really know what to do from there. Also, it's a bit weird, since sometimes, making a tile become explored means changing a value to 130, but sometimes it's 131, or 132. In some tiles, 130 means changing the 2D image that shows in the map's floor, not making it visible at all.
What can I do from here?
|
|
Back to top |
|
|
jgoemat Master Cheater Reputation: 22
Joined: 25 Sep 2011 Posts: 252
|
Posted: Fri Mar 09, 2018 2:18 pm Post subject: |
|
|
You might be able to find the cap by looking for code that accesses the sight range you found. You might find some code that compares your value to a another value that could be a constant or loaded from a global memory address and that uses the lesser value, that would be the distance cap.
|
|
Back to top |
|
|
Golokopitenko Newbie cheater Reputation: 0
Joined: 29 Jan 2018 Posts: 18
|
Posted: Thu Mar 15, 2018 2:59 pm Post subject: |
|
|
jgoemat wrote: | You might be able to find the cap by looking for code that accesses the sight range you found. You might find some code that compares your value to a another value that could be a constant or loaded from a global memory address and that uses the lesser value, that would be the distance cap. |
Hey, thanks! Sadly it's only movzx and a single mov instructions. What could those mean?
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
|