Hello people, i just started using cheat engine and im having a hard time when i try to find the base address of a cheat im trying to make, the thing is that i can find the address and edit the value but everytime i close and open the game again the address just change and i have to find it again so i guess i need to find the base address to be able to edit the numbres when i want (the values goes from 0 to 3) i tryed the option "pointer scan for this address" but i couldn't find the base address with that method i dont know if i did something wrong but i found 184 results with the first scan so i decided to try them all after all it wasn't too much but no one of them shared the same value of the address i originaly found so i guess none of those results where the base address.
If anyone could tell me if i did something wrong or if there is another way to find the base address i would greatly appreciate the help
Base address
Re: Base address
one of the another way is to use the debugger to trace the codes, you can "create" a pointer by injecting your own aa codes to the game.
do some of the tutorials that came with CE first is recommended, and/or visit the CE forum if you're stuck, you should be able to find a solution very soon.
do some of the tutorials that came with CE first is recommended, and/or visit the CE forum if you're stuck, you should be able to find a solution very soon.
-
- Novice Cheater
- Posts: 23
- Joined: Fri Sep 01, 2017 5:41 am
- Reputation: 0
Re: Base address
I have found the Best way to find a base address is to look for something common on the game ammo, health, supplies depending on what you need, once you narrow it down right click and choose what accesses this address, and look at the instructions that are accessing it.
say the offset is +3c5 of ammo
if you see a lot of [rax+3c5] for example you shoot something or pick up ammo
sub [rax+3c5],edi
add [rax+3c5],edi
so its safe to assume that [rax+3c5] is the ammo
now we want to use the base address
we start an autoassembly script
add 2 llines to it globalalloc(ammo, 4 if its 32 bit and 8 if its 64 bit
globalalloc(ammo,8)
we now before the actual injection add
mov [ammo],rax
this moves the base address rax into our variable ammo
Once I get my screenshot app working again I can show pictures of it working, some reason its not working at the moment.
Now any address you add you can use ammo as the address and add the offset like [ammo]+offset or as a pointer use ammo and then the offset in the offset input box
say the offset is +3c5 of ammo
if you see a lot of [rax+3c5] for example you shoot something or pick up ammo
sub [rax+3c5],edi
add [rax+3c5],edi
so its safe to assume that [rax+3c5] is the ammo
now we want to use the base address
we start an autoassembly script
add 2 llines to it globalalloc(ammo, 4 if its 32 bit and 8 if its 64 bit
globalalloc(ammo,8)
we now before the actual injection add
mov [ammo],rax
this moves the base address rax into our variable ammo
Once I get my screenshot app working again I can show pictures of it working, some reason its not working at the moment.
Now any address you add you can use ammo as the address and add the offset like [ammo]+offset or as a pointer use ammo and then the offset in the offset input box
Re: Base address
If injection is made on shared instruction, -
globalalloc will work like mess without separating values out with cmp.
globalalloc will work like mess without separating values out with cmp.
-
- Novice Cheater
- Posts: 23
- Joined: Fri Sep 01, 2017 5:41 am
- Reputation: 0
Re: Base address
yes true but he just was asking about base address, didnt mention anything about dissecting and seperating from shared values. I know thats when you have to start using cmp to compare and jump or proceed.
Who is online
Users browsing this forum: No registered users