Deviceptr - CA - MPGH - MultiPlayer Game Hacking & Cheats

Deviceptr - CA

Ok, I am kinda of a newb at this so dont bash me too hard..

I try to find the the deviceptr for Direct3DDevice in which i may be in sorta of the right direction, im not gonna post on here asking for help without trying on my own the best i can first, in which i did i have come to this in olly with engine.exe

Code:

0051F957   . 5E             POP ESI
0051F958   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
0051F95D   . 8B88 FC060000  MOV ECX,DWORD PTR DS:[EAX+6FC]
0051F963   . 894C24 04      MOV DWORD PTR SS:[ESP+4],ECX
0051F967   .^E9 9438F4FF    JMP Engine.00463200
0051F96C   > 68 70507600    PUSH Engine.00765070      ;  ASCII "d3ddevice"   <--- Which jumps from 0051F955

Code:

0051F931   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
0051F936   . 8B88 F8060000  MOV ECX,DWORD PTR DS:[EAX+6F8]
0051F93C   . 894C24 04      MOV DWORD PTR SS:[ESP+4],ECX
0051F940   .^E9 BB38F4FF    JMP Engine.00463200
0051F945   > 68 7C507600    PUSH Engine.0076507C                     ;  ASCII "cshell_hinstance"
0051F94A   . 56             PUSH ESI
0051F94B   . E8 D1761B00    CALL Engine.006D7021
0051F950   . 83C4 08        ADD ESP,8
0051F953   . 85C0           TEST EAX,EAX
0051F955   . 75 15          JNZ SHORT Engine.0051F96C

__________________________________________________________
0051F931   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
__________________________________________________________

Which led me to think that 7DFB14 would be the deviceptr but i may be wrong CA still crashes... Any ideas?

looks more like its pushing the value at this address onto the stack: 0x00765070 (not saying that that is it)

Originally Posted by why06jz

looks more like its pushing the value at this address onto the stack: 0x00765070 (not saying that that is it)

wow man this damn thing is actually hard to find lmao

Originally Posted by iownmhckn

Ok, I am kinda of a newb at this so dont bash me too hard..

I try to find the the deviceptr for Direct3DDevice in which i may be in sorta of the right direction, im not gonna post on here asking for help without trying on my own the best i can first, in which i did i have come to this in olly with engine.exe

Code:

0051F957   . 5E             POP ESI
0051F958   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
0051F95D   . 8B88 FC060000  MOV ECX,DWORD PTR DS:[EAX+6FC]
0051F963   . 894C24 04      MOV DWORD PTR SS:[ESP+4],ECX
0051F967   .^E9 9438F4FF    JMP Engine.00463200
0051F96C   > 68 70507600    PUSH Engine.00765070      ;  ASCII "d3ddevice"   <--- Which jumps from 0051F955

Code:

0051F931   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
0051F936   . 8B88 F8060000  MOV ECX,DWORD PTR DS:[EAX+6F8]
0051F93C   . 894C24 04      MOV DWORD PTR SS:[ESP+4],ECX
0051F940   .^E9 BB38F4FF    JMP Engine.00463200
0051F945   > 68 7C507600    PUSH Engine.0076507C                     ;  ASCII "cshell_hinstance"
0051F94A   . 56             PUSH ESI
0051F94B   . E8 D1761B00    CALL Engine.006D7021
0051F950   . 83C4 08        ADD ESP,8
0051F953   . 85C0           TEST EAX,EAX
0051F955   . 75 15          JNZ SHORT Engine.0051F96C

__________________________________________________________
0051F931   . A1 14FB7D00    MOV EAX,DWORD PTR DS:[7DFB14]
__________________________________________________________

Which led me to think that 7DFB14 would be the deviceptr but i may be wrong CA still crashes... Any ideas?

7DFB14 is the device pointer. EAX is the device.

O i guess i need a diffrent hook i guess still crashes thanks for the help

Originally Posted by iownmhckn

O i guess i need a diffrent hook i guess still crashes thanks for the help

I made a thread on how to hook Direct3DDevice9 functions if you have the device pointer. It might help.

Originally Posted by Void

7DFB14 is the device pointer. EAX is the device.

Actly now that I look at it that makes since, but who is to say that is the device pointer. how do we know for sure? It's just an address from the data segment. =/

Originally Posted by why06

Actly now that I look at it that makes since, but who is to say that is the device pointer. how do we know for sure? It's just an address from the data segment. =/

Check if EAX is being used as the operand for call. Or you might find something like this.

Code:

mov ebx,[eax]
mov ecx,[ebx+number]
call ecx

Deviceptr - CA

Similar Threads

Tags for this Thread