Home › Forum › MultiPlayer Game Hacks & Cheats › Combat Arms Hacks & Cheats › [Need Help] Multi-Pointers
[Need Help] Multi-Pointers
[Need Help] Multi-Pointers
Well I guess alot of you know about my new trainer and that im workin to fix it i got some of them working through single pointers but the others i can't get to work cause i need to make it with multi pointers i was wondering if anyone can tell me how to make it through the multi pointers and ill give +rep and thanks!
I already know how to make level 1 pointers
I already know how to make level 1 pointers
isnt there a patch tonight >.>
Originally Posted by king.joker.9
isnt there a patch tonight >.>
Originally Posted by bartjr
Well I guess alot of you know about my new trainer and that im workin to fix it i got some of them working through single pointers but the others i can't get to work cause i need to make it with multi pointers i was wondering if anyone can tell me how to make it through the multi pointers and ill give +rep and thanks!
I already know how to make level 1 pointers
I already know how to make level 1 pointers
This step will explain how to use multi-level pointers.
In step 6 you had a simple level-1 pointer, with the first address found already being the real base address.
This step however is a level-4 pointer. It has a pointer to a pointer to a pointer to a pointer to a pointer to the health.
You basicly do the same as in step 6. Find out what accesses the value, look at the instruction and what probably is
the base pointer value, and what is the offset, and already fill that in or write it down. But in this case the address
you'll find will also be a pointer. You just have to find out the pointer to that pointer exactly the same way as you did
with the value. Find out what accesses that address you found, look at the assembler instruction, note the probable
instruction and offset, and use that.
and continue till you can't get any further (usually when the base address is a static address, shown up as green)
Click Change Value to let the tutorial access the health.
If you think you've found the pointer path click Change Register. The pointers and value will then change and you'll
have 3 seconds to freeze the address to 5000
Extra: This problem can also be solved using a auto assembler script, or using the pointer scanner
Extra2: In some situations (like this) it is recommended to change ce's codefinder settings to Access violations when
encountering instructions like mov eax,[eax] since debugregisters show it AFTER it was changed, making it hard to
find out the the value of the pointer
Extra3: If you're still reading. You might notice that when looking at the assembler instructions that the pointer is
being read and filled out in the same codeblock. This doesn't always happen, but can be really usefull in finding a
pointer when debuggng is troublesome
bull sh** i use too go on the site everynight too check on updates never said a thing.. there too lazy dude they tel you when they patch when they have the patch going on.
Originally Posted by Marsicano
Step 8: Multilevel pointers:
This step will explain how to use multi-level pointers.
In step 6 you had a simple level-1 pointer, with the first address found already being the real base address.
This step however is a level-4 pointer. It has a pointer to a pointer to a pointer to a pointer to a pointer to the health.
You basicly do the same as in step 6. Find out what accesses the value, look at the instruction and what probably is
the base pointer value, and what is the offset, and already fill that in or write it down. But in this case the address
you'll find will also be a pointer. You just have to find out the pointer to that pointer exactly the same way as you did
with the value. Find out what accesses that address you found, look at the assembler instruction, note the probable
instruction and offset, and use that.
and continue till you can't get any further (usually when the base address is a static address, shown up as green)
Click Change Value to let the tutorial access the health.
If you think you've found the pointer path click Change Register. The pointers and value will then change and you'll
have 3 seconds to freeze the address to 5000
Extra: This problem can also be solved using a auto assembler script, or using the pointer scanner
Extra2: In some situations (like this) it is recommended to change ce's codefinder settings to Access violations when
encountering instructions like mov eax,[eax] since debugregisters show it AFTER it was changed, making it hard to
find out the the value of the pointer
Extra3: If you're still reading. You might notice that when looking at the assembler instructions that the pointer is
being read and filled out in the same codeblock. This doesn't always happen, but can be really usefull in finding a
pointer when debuggng is troublesome
This step will explain how to use multi-level pointers.
In step 6 you had a simple level-1 pointer, with the first address found already being the real base address.
This step however is a level-4 pointer. It has a pointer to a pointer to a pointer to a pointer to a pointer to the health.
You basicly do the same as in step 6. Find out what accesses the value, look at the instruction and what probably is
the base pointer value, and what is the offset, and already fill that in or write it down. But in this case the address
you'll find will also be a pointer. You just have to find out the pointer to that pointer exactly the same way as you did
with the value. Find out what accesses that address you found, look at the assembler instruction, note the probable
instruction and offset, and use that.
and continue till you can't get any further (usually when the base address is a static address, shown up as green)
Click Change Value to let the tutorial access the health.
If you think you've found the pointer path click Change Register. The pointers and value will then change and you'll
have 3 seconds to freeze the address to 5000
Extra: This problem can also be solved using a auto assembler script, or using the pointer scanner
Extra2: In some situations (like this) it is recommended to change ce's codefinder settings to Access violations when
encountering instructions like mov eax,[eax] since debugregisters show it AFTER it was changed, making it hard to
find out the the value of the pointer
Extra3: If you're still reading. You might notice that when looking at the assembler instructions that the pointer is
being read and filled out in the same codeblock. This doesn't always happen, but can be really usefull in finding a
pointer when debuggng is troublesome
yeah i already read that tut on cheat engine tutorial but its kinda confusing
if you are using CE, add a pointer twice, that means press the button twice. So it will look like this:
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
Originally Posted by bartjr
yeah i already read that tut on cheat engine tutorial but its kinda confusing
Originally Posted by jerry0
if you are using CE, add a pointer twice, that means press the button twice. So it will look like this:
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
Originally Posted by jerry0
if you are using CE, add a pointer twice, that means press the button twice. So it will look like this:
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
First row, address of second row, offset
Second row, address, offset.
[greyed out] [Offset2]
[pointer ] [Offset1]
Similar Threads
- 6Last post
- 13Last post
- 8Last post
- 0Last post
- 27Last post