| View previous topic :: View next topic |
| Author |
Message |
Misteraaargh
Newbie cheater
![]() Reputation: 0
Joined: 20 Dec 2012
Posts: 14
|
 Posted: Sat Dec 22, 2012 1:49 am Post subject: Coord values change back immediately :( |
 |
|
After putting a lot of effort into searching for the coords of ball in a game. I have managed to find the addresses. Each coords has about 9 addresses that show exactly the same value.
First , I dont know which is the correct one. Perhaps all of them are.
The real issue though is that the value immediately reverts back to what it was before changing.The new value just flickers and dissapears and the old value comes back. I've tried freezing it. Setting freeze time to 10ms. I have tried changing every single one of them
I understand that freeze is simply the automation of putting a certain value, so its not actually a real freeze.
I would really appreciate your guidance from here.
|
|
| Back to top |
|
 |
Dark Byte
Site Admin
 Reputation: 471
Joined: 09 May 2003
Posts: 25864
Location: The netherlands
|
| Posted: Sat Dec 22, 2012 2:30 am Post subject: |
|
|
If they revert back immediately that means you only found a temp/display var.
Try a different valuetype, or the value doesn't change as often as you think (eg. It might draw the ball at a specific spot, but that might just be a calculated position based on the real position and the vector and speed
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
|
Misteraaargh
Newbie cheater
![]() Reputation: 0
Joined: 20 Dec 2012
Posts: 14
|
| Posted: Sat Dec 22, 2012 6:02 am Post subject: |
|
|
Hmm. let me understand this. So what you are saying is that the value I am seeing is a calculated one i.e a product of several factors. And if it is so, then changing the value i have has no effect upon the 'base factors', And the value immediately gets recalculated and replaced. Right?
| Quote: | | Try a different valuetype, or the value doesn't change as often as you think |
I've tried it with float. Should I go for double this time?. how do I know what to try? Is there a logic behind it or simple trial and error?
And, Is there any usefulness to the permanent pointers I have found to the XYZ values? I mean, may be they can help me get to the 'factors' easily...
I'll try again now. Would love to have your say on the questions asked above..
Thanks for the reply. I never thought of other factors being involved to calculate the XYZ values ( which may just be 'display' values). Thanks for opening my eyes to this part. And sorry for so many quesitons 
Update: Update:
Among the 9 addresses that showed the same values, I filtered out one. This one was the only address that actually made the ball leave its place even if for a millisecond. I am pretty sure now that what I have in my hands is just a display value as changing the ball position has no effect on AI. So AI is not seeing the ball where it appears to be for a milisecond but where it actually is.
I clicked what acceses this address and there were about 8-9 entries. I used the NOP on them. Two of them crashed the game. The rest except one did nothing visible. One that did was that it made all the players and ball disappear. Only the shadows were there. Injecting the code back made the players and ball re-appear.
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
