[RELEASE][.NET] Hooking library, take two

also need the new mapinfo address if anyone can get the updated address

What else changed? Can click the checkbox to get a "autohunt enabled" message but writing it gives no message so does that mean packets changed?

And PKDemon I'm going to hazard a guess that the new mapinfopointer is "8B7CA4"? I can't see it properly on the laptop I'm using for whatever reasons BUT I was able to see parts of it and have to assume it's issues with the laptop and the screen resolutions. Been trying to get the laptop working properly since I have had the chance to use it.

Test it and let me know if it is correct, I can't properly test until I'm back at home on my own computer which isn't happening for another two weeks >.<

client will close after attaching its process to the application with the new patch.

Quote:

Originally Posted by xmen01235 client will close after attaching its process to the application with the new patch.

Yes and it will keep crashing because TQ has just added some anti-debugging tricks.. lmfao like its gonna do them any good

Have you tried hooking IsDebuggerPresent?

Quote:

Originally Posted by IAmHawtness Have you tried hooking IsDebuggerPresent?

I dont use this but couldnt u just patch the IsDebuggerPresent with mov eax,0

Quote:

Originally Posted by _fobos_ I dont use this but couldnt u just patch the IsDebuggerPresent with mov eax,0

Yeah, true :p

Quote:

Originally Posted by IAmHawtness Yeah, true :p

How?

Quote:

Originally Posted by xmen01235 How?

Seriously?? The answer is given lol...
Patch IsDebuggerPresent with mov eax,0
notice test eax,eax under IsDebuggerPresent? that's the answer it needs...
Read next time =P Of course there's more ways to do this, this is just an easy and simple fix, if you want to know more i'd suggest reading some debugging tutorials! :) Good luck!

Quote:

Originally Posted by _fobos_ Seriously?? The answer is given lol... Patch IsDebuggerPresent with mov eax,0 notice test eax,eax under IsDebuggerPresent? that's the answer it needs... Read next time =P Of course there's more ways to do this, this is just an easy and simple fix, if you want to know more i'd suggest reading some debugging tutorials! :) Good luck!

I am an assembly idiot bro sorry for that...

SendPacketAddress = 0x6C9B69 ?
RecvPacketLoopAddress = 0x6C5E85 ?

With the address above, I can see the sendpacket but the receivepacket wont show at all. Please help me check if my address is correct.

Finally I made it to run but there was a problem, it will crashed once i will press F12 for screenshot.

Quote:

Originally Posted by xmen01235 How many had been 1day banned for using this library?

"This library"shouldn't get anyone banned, as long as they use it correctly..

Quote:

Originally Posted by Zeroxelli "This library"shouldn't get anyone banned, as long as they use it correctly..

I think they have actually started detecting debuggers, and it's something other than IsDebuggerPresent/CheckRemoteDebuggerPresent.
I would advise people to not use this anymore until there's a fix.
Since there's like a thousand ways to detect a debugger, I doubt I have the patience to look into it though.

Quote:

Originally Posted by IAmHawtness I think they have actually started detecting debuggers, and it's something other than IsDebuggerPresent/CheckRemoteDebuggerPresent. I would advise people to not use this anymore until there's a fix. Since there's like a thousand ways to detect a debugger, I doubt I have the patience to look into it though.

Oh, wow.. TQ actually doing something smart, that makes sense? That's shocking. They must have hired some real coders for once.

I guess that kills memory based hacks for a bit.

Quote:

Originally Posted by Zeroxelli Oh, wow.. TQ actually doing something smart, that makes sense? That's shocking. They must have hired some real coders for once. I guess that kills memory based hacks for a bit.

I know, I couldn't believe it either :(