Address Logger?
Address Logger?
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Now here is how to use this code
now i will explain a bit.
signature mask is a "x" for the bytes that dont change,and a "?" for the bytes that do change.
Here is some ******* scan codes for you to use that i made myself.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
I FOUND THIS INFORMATION ON A SITE, ABOUT HOW TO CREATE AN ADDRESS LOGGER, I DONT GET IT BUT MAYBE SOMEONE ELSE CAN?
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
{
for(;*szMask;++szMask,++pData,++bMask)
if(*szMask=='x' && *pData!=*bMask )
return false;
return (*szMask) == NULL;
}
DWORD FindPattern(DWORD dwAddress,DWORD dwLen,BYTE *bMask,char * szMask)
{
for(DWORD i=0; i < dwLen; i++)
if( bCompare( (BYTE*)( dwAddress+i ),bMask,szMask) )
return (DWORD)(dwAddress+i);
return 0;
}
Code:
DWORD Your Address = FindPattern( 0x400000, 0x5000, ( PBYTE ) "\xA1\x00\x00\x00\x00\x83\xEC\x00\x80\x78\x00\x00", "x????xx?xx??" );
Code:
FindPattern( start address, + so many to the start address, ( PBYTE ) "bytes to scan for", "signature mask" );
Here is some ******* scan codes for you to use that i made myself.
Code:
m_dwAKick = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x8B\x85\xFC\xE2\x04\x00\x39\x44\x24\x10\x75\x76\x8D\x8D\x70","xx??xxxxxxxxxx?"); m_dwUAmmo1 = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x89\x7E\x24\x7E\x15\x6A\x40\x6A\x01\xE8\x6C\x0A\x17\x00\x83","xxxxxxxxxx???xx"); m_dwUAmmo2 = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x89\x46\x20\x0F\xAF\xC7\x89\x46\x24\x5F\xB8\x01\x00\x00\x00","xxxxxxxxxxxxxxx");//// m_dwUAmmo3 = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x89\x46\x24\x5F\xB8\x01\x00\x00\x00\x5E\xC2\x04\x00\xCC\xCC","xxxxxxxxxxxxxxx"); m_dwProne = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x84\xC0\x74\x0C\x8B\x8E\x78\x02\x00\x00\x8B\x01\x56\xFF\x50\x2C\x5E\xC3\x83","xxx?xx??xxxxxxxxxxx"); m_dwNameEsp = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x75\x23\x8B\xCB\x69\xC9\x28\x1A\x00\x00\x8B\x81\xD8\x66\xBD","x?x?xx?xxxxx???"); m_dwInvis = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x2C\x8B\x56\x10\x89\x57\x34\x66\x89\x2F\x8A\x86\x18\x02\x00","xx?xx?xxx?x??xx"); /// m_dwHeal = FindPattern(0x400000, 0x01400000,(unsigned char*)"\x0F\x85\xA6\x00\x00\x00\x85\xC9\xC7\x05\x30\x1D\xB1\x00\x00\x00\x00\x40","xx????xxxx????xxxx");
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
I FOUND THIS INFORMATION ON A SITE, ABOUT HOW TO CREATE AN ADDRESS LOGGER, I DONT GET IT BUT MAYBE SOMEONE ELSE CAN?
Been to the site that you got that from, can't remember the name ATM. IPawn, and Killer were working on this for a while, i wonder what they are up to. Either way i'm too lazy to think about this. Also because i've never gotten a bypass to work for me thus it's pretty useless >_<.
edit: oh right its naeron's address logger;
edit edit: you know you've been coding for too long when you end your sentences with semicolons;
edit: oh right its naeron's address logger;
edit edit: you know you've been coding for too long when you end your sentences with semicolons;
Use Neo I.I.I's NSearch.
Originally Posted by Longevity
Use Neo I.I.I's NSearch.
Originally Posted by Longevity
Use Neo I.I.I's NSearch.
Well the first two lines confuse me. The guy who coded this must be a fkin genius or either have a lot of experienced:
Originally Posted by Zhhot
Look at that he used a for loop and incremented 3 pointers at the same time. D: ffs! I didn't even know you could do that :{. And if that's not enough he puts the increment things on the left. I forget what side does what. I'm going to have to look that back up in my book. Plus accessing addresses confuse me a little.
All I really know about addresses is this is a hex literal "0x....." and this is an oct literal "0..". I'm not sure what kind of literal just an "x..." is ??? I don't like jumping to far ahead, once I learn about classes and namespaces, and ASM. Then I'll try something like this. Goodluck though to whoever is attempting this.
BTW: Anyway I'm with zeco. Where is this tutorial at?
Originally Posted by Zhhot
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
{
for(;*szMask;++szMask,++pData,++bMask)
All I really know about addresses is this is a hex literal "0x....." and this is an oct literal "0..". I'm not sure what kind of literal just an "x..." is ??? I don't like jumping to far ahead, once I learn about classes and namespaces, and ASM. Then I'll try something like this. Goodluck though to whoever is attempting this.
BTW: Anyway I'm with zeco. Where is this tutorial at?
++x = pre-increment
x++ = post increment;
(same of course goes for decrement with '--');
say: x = 1;
y = ++x;
Now Y == 2 and X == 2;
if you say:
x = 1; y = x++;
then you'll have
Y==1 and X == 2;
x++ = post increment;
(same of course goes for decrement with '--');
say: x = 1;
y = ++x;
Now Y == 2 and X == 2;
if you say:
x = 1; y = x++;
then you'll have
Y==1 and X == 2;
I understand everything except one part
Well starting with :
if(*szMask=='x' && *pData!=*bMask )
return false;
Does it mean, If blah blah is true, just return false, ignoring the rest of the function.
and for return (*szMask) == NULL;, does that mean, return the value if it is null? Or something to that effect.
And if my guess is true, then what if the value isn't null, and doesn't comply with the previous if statement? Then the function that is supposed to return a bool won't be able to return anything. However this is assuming my guess was correct which it likely wasn't
And upon thinking about that last part, am i right in thinking that a function ends whenever a value is returned, except for void functions where it just ends at a break(?), or when there is no more code?
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
{
for(;*szMask;++szMask,++pData,++bMask)
if(*szMask=='x' && *pData!=*bMask )
return false;
return (*szMask) == NULL;
}
Well starting with :
if(*szMask=='x' && *pData!=*bMask )
return false;
Does it mean, If blah blah is true, just return false, ignoring the rest of the function.
and for return (*szMask) == NULL;, does that mean, return the value if it is null? Or something to that effect.
And if my guess is true, then what if the value isn't null, and doesn't comply with the previous if statement? Then the function that is supposed to return a bool won't be able to return anything. However this is assuming my guess was correct which it likely wasn't
And upon thinking about that last part, am i right in thinking that a function ends whenever a value is returned, except for void functions where it just ends at a break(?), or when there is no more code?
man, i totally forgot the site name, and i delete history and cookies every day, so probably not gunna be there, u can try googling it o.0?!
Originally Posted by Zhhot
man, i totally forgot the site name, and i delete history and cookies every day, so probably not gunna be there, u can try googling it o.0?!
It is naeron, apparently I've had a tab with it open, rather i forgot about this poor lonesome tab. So googling Naeron's address logger tutorial, should bring you to it.
Originally Posted by zeco
It is naeron, apparently I've had a tab with it open, rather i forgot about this poor lonesome tab. So googling Naeron's address logger tutorial, should bring you to it.
Originally Posted by Zhhot
"lonesome tab" rofl
Originally Posted by zeco
I understand everything except one part
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
{
for(;*szMask;++szMask,++pData,++bMask)
if(*szMask=='x' && *pData!=*bMask )
return false;
return (*szMask) == NULL;
}
Originally Posted by zeco
Well starting with :
if(*szMask=='x' && *pData!=*bMask )
return false;
Does it mean, If blah blah is true, just return false, ignoring the rest of the function.
if(*szMask=='x' && *pData!=*bMask )
return false;
Does it mean, If blah blah is true, just return false, ignoring the rest of the function.
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
{
for(;*szMask;++szMask,++pData,++bMask)
if(*szMask=='x' && *pData!=*bMask )
return false;
Code:
bool bCompare(const BYTE* pData, const BYTE* bMask, const char* szMask)
Code:
bool bCompare(const BYTE *pData, const BYTE *bMask, const char *szMask)
Code:
for(;*szMask;++szMask,++pData,++bMask) if(*szMask=='x' && *pData!=*bMask ) return false;
Code:
for(;*szMask;++szMask,++pData,++bMask)
Remember Everytime it executes szMask, pData, and bMask all get incremented.
Code:
if(*szMask=='x' && *pData!=*bMask ) return false;
then this boolean funtion will return false
Next question?
Originally Posted by zeco
and for return (*szMask) == NULL;, does that mean, return the value if it is null? Or something to that effect.
Code:
return (*szMask) == NULL;
Code:
return (*szMask) == NULL;
Code:
return (*szMask) == NULL;
NULL is the character that marks the end of a string. I'm unsure if its zero but basically...
This whole express will evaluate to true or false depending if (*szMask) == NULL
sorry I couldn't explain further got to get to class. xD
xD i just Meant the tiny parts that Bolded. I understood everything else. But eitherway, what i really didn't understand is having the two returns. But based on the way you worded it i think i know my answer. Thanks for the part about return (*szMask) == NULL;. This alone made me fully understand.
I would have caught on faster though, if he had
return ((*szMask) == NULL);
P.S. I put my pointer thingy beside the type too >_>. It just makes more sense in my head. Well while initializing anyway. If i'm getting the pointed to value, i put it beside the variable.
So yeah i forgot that i knew how to code(kinda), and just did some tests of my own. Now everything makes sense
I would have caught on faster though, if he had
return ((*szMask) == NULL);
P.S. I put my pointer thingy beside the type too >_>. It just makes more sense in my head. Well while initializing anyway. If i'm getting the pointed to value, i put it beside the variable.
So yeah i forgot that i knew how to code(kinda), and just did some tests of my own. Now everything makes sense
Originally Posted by zeco
xD i just Meant the tiny parts that Bolded. I understood everything else. But eitherway, what i really didn't understand is having the two returns.
.... actually 
that took a long time.Anyway the return sort of acts like a break statement. Since a function can only return once the first return that executes ends the code.
And yeh I lot of people put the * on the type, but its a little misleading because C++ doesn't recognize the type as pointers only specific variables. Say if you wanted to declare multiple pointer variables at once:
Code:
int* a, b, c; // This would not work.
Code:
int *a, *b, *c; // This would.
Similar Threads
- 3Last post
- 7Last post
- 1Last post
- 5Last post
- 30Last post