 |
Cheat Engine The Official Site of Cheat Engine
|
| View previous topic :: View next topic |
| Author |
Message |
louie999 How do I cheat?
Reputation: 0
Joined: 12 Sep 2015 Posts: 8 Location: Classified
|
Posted: Sat Dec 05, 2015 4:47 am Post subject: Is there a way to find the player data structure? |
|
|
Hi, so I'm trying to find the playerbase/player data structure so I can get all the info needed, like X Y position, money, ammo etc... How exactly can I do it? I tried searching for the player's HP and I got it then I did "Find out what accesses this address" but after that I don't know what to do next How can I find that playerbase?  |
|
| Back to top |
|
 |
grtnd Newbie cheater
Reputation: 0
Joined: 29 Nov 2015 Posts: 14
|
Posted: Sat Dec 05, 2015 8:31 am Post subject: |
|
|
Hello again louie999,
you'll need to look at the various instructions that accesses the address (this is where you are now). go into memory viewer and try and trace the pointer, what offset was used in the instruction, what register manipulations were done to get to your x or y position pointer. all the pointers that comes from this structure shares one thing in common: they are derived from the same structure pointer. this means that any of the common pointers like x,y,direction,ammo,ect should be based off the same structure pointer and you should be able to verify this. this should be the same for all your instructions that uses said pointer to access the value as well (but don't try and verify it by tracing all the instructions on one pointer, it's just a waste of time) pick one instruction that accesses or writes to your pointer
and try and trace it to something that another player pointer (try the other position pointer, its the safest and most likely to be a player pointer) also is traced back to. and if that doesn't work, pick the next instruction, and work with that, and if that one doesn't work, pick the next one, and so on.
but of course there is one major problem with this, you'll need to use the debugger, and i can remember correctly, you said it closes upon attaching the debugger. there are two ways around this: Use the debugger in kernel mode, or use the VEH debugger. (i haven't tested it myself, i've just heard that they work to bypass debugger detections in CS2D and other various games)
Edit -> Settings -> Debugger Options -> Debugger method |
|
| 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
|
|