Address Logger for CA ?
Address Logger for CA ?
Is it possible to do an address logger for CA ? It's like more easier to find addy ^^ and you have all of them you insert in the code. Undetected because it doesn't need to run the game, it's like a Hack. I were able to do it for WR 
but I'm not for CA :s 
Can
help me ?
but I'm not for CA :s Can
help me ?You need bytes and a mask... bytes can i get but not mask
Yeah bytes are not really difficult to get. But it's not really the samething as WR so :s
well i have the source to a searcher and sig creator but it is not giving me the 2nd line of the sig so i cant use it till i fix it
but i use the sig maker to create the sig then use the sig to find the addie
it will log both the sig and addies to txt files once found
u inject the sigcreater and then hit numpad 0 then it will log the sigs
u inject the addie finder and hit numpad 0 and it logs the addies
if u think u can help me fix it, please do then we can have addies found faster and even use the sigs in our hacks instead of a dam addie
but i use the sig maker to create the sig then use the sig to find the addie
it will log both the sig and addies to txt files once found
u inject the sigcreater and then hit numpad 0 then it will log the sigs
u inject the addie finder and hit numpad 0 and it logs the addies
if u think u can help me fix it, please do then we can have addies found faster and even use the sigs in our hacks instead of a dam addie
Originally Posted by tahha
well i have the source to a searcher and sig creator but it is not giving me the 2nd line of the sig so i cant use it till i fix it
but i use the sig maker to create the sig then use the sig to find the addie
it will log both the sig and addies to txt files once found
u inject the sigcreater and then hit numpad 0 then it will log the sigs
u inject the addie finder and hit numpad 0 and it logs the addies
if u think u can help me fix it, please do then we can have addies found faster and even use the sigs in our hacks instead of a dam addie
but i use the sig maker to create the sig then use the sig to find the addie
it will log both the sig and addies to txt files once found
u inject the sigcreater and then hit numpad 0 then it will log the sigs
u inject the addie finder and hit numpad 0 and it logs the addies
if u think u can help me fix it, please do then we can have addies found faster and even use the sigs in our hacks instead of a dam addie
this is for CA not here CA dosent have any sigs Originally Posted by wizzerkin
wat the hell are you talking about tht has nothing to do for this a sig creator????? this is for CA not here CA dosent have any sigs
this is for CA not here CA dosent have any sigs A sig isa What where basically taken bout...
Yep you can do an addie logger.
I made one =)
Just google how to do them
I made one =)
Just google how to do them
Originally Posted by ~GodLike~
Yep you can do an addie logger.
I made one =)
Just google how to do them
I made one =)
Just google how to do them
Alot of sources out there.
Im still confused on how to find the mask. Anyone wanna tell me how?
Originally Posted by ac1d_buRn
Yes, There pretty simple.
Alot of sources out there.
Im still confused on how to find the mask. Anyone wanna tell me how?
For example:
Code:
x ? ? ? ? B9 56 28 10 37 mov eax, 0x37102856 x x 6A 05 push 0x05
Originally Posted by mmbob
If the byte is an address or something that might easily change in the next patch, youll want to have the mask be a '?'.
For example:
So the mask would be "x????xx"
For example:
Code:
x ? ? ? ? B9 56 28 10 37 mov eax, 0x37102856 x x 6A 05 push 0x05
Originally Posted by ac1d_buRn
How would i know what bytes would be ? and wat bytes that would be x
Code:
E9 00 11 22 33 jmp | memory adress (dword)
Everything, what is not constant (memoryaddys and so on), has to be flagged with a "?", the other bytes with "x"
I did an Addy-Dumper for WoW, it easiely reads out all interesting things from the PE-Header, serches the patterns in the binary file and than calculates the correct memory address from the raw one.
Greetings,
Ende
Originally Posted by Ende!
Just think about what is constant and what is changed with a patch. If there is a E9-Jmp, the fist byte is constant and the other 4 not, because it's an address to a memory location.
So the mask would be: x????
Everything, what is not constant (memoryaddys and so on), has to be flagged with a "?", the other bytes with "x"
I did an Addy-Dumper for WoW, it easiely reads out all interesting things from the PE-Header, serches the patterns in the binary file and than calculates the correct memory address from the raw one.
Greetings,
Ende
Code:
E9 00 11 22 33 jmp | memory adress (dword)
Everything, what is not constant (memoryaddys and so on), has to be flagged with a "?", the other bytes with "x"
I did an Addy-Dumper for WoW, it easiely reads out all interesting things from the PE-Header, serches the patterns in the binary file and than calculates the correct memory address from the raw one.
Greetings,
Ende
This thread is closed for replies.
