You will go to bj using this or lats clients it doesn't matter. There is no nulling there doing to client that will prevent the way TQ is detecting cooperative because there detecting the bot itself not the bot thru the client. And no reshacker bs that people are using on cooperative claiming will stop it from being detected will matter either lol there not detecting cooperative by it's name and i'm kinda surprised nobody else has figured that out yet and how tq is really detecting it lol.
Using these so called nulled clients might prevent bj from autoclickers and pixelbots and such but using cooperative ya might as well just live with the fact it's going to be detected everytime until hawt figures out the obvious on why coop is being detected.
LoL....
With mine or lats multi the TQ/CO2 scanner is REMOVED
1) There is a code that call tq scanner (e.g. Call.blablabla)
2) There is code (opcode) that can MAKE the conquer.exe to JUMP that call (conquer.exe will think that the scan is made succefully)
And that JUMP code is MADE in ours (mine and lateralus) MULTI CLIENTS...
You will go to bj using this or lats clients it doesn't matter. There is no nulling there doing to client that will prevent the way TQ is detecting cooperative because there detecting the bot itself not the bot thru the client. And no reshacker bs that people are using on cooperative claiming will stop it from being detected will matter either lol there not detecting cooperative by it's name and i'm kinda surprised nobody else has figured that out yet and how tq is really detecting it lol.
Using these so called nulled clients might prevent bj from autoclickers and pixelbots and such but using cooperative ya might as well just live with the fact it's going to be detected everytime until hawt figures out the obvious on why coop is being detected.
I believe you're right; it's a problem in COoperative itself, because not only is no information about your processes, accounts, etc. sent, but this information isn't even collected in my client. Plus, the only reports I've gotten from botjailing are from users of COoperative.
Although these clients are *somewhat* trial and error... I may have messed up.
Edit: Yes, Martin has assured me that information IS sent with my client. He also helped me discover a new anti-bot dll, which I'll work on fully cracking ASAP.
Quote:
Originally Posted by vecko12
LoL....
With mine or lats multi the TQ/CO2 scanner is REMOVED
1) There is a code that call tq scanner (e.g. Call.blablabla)
2) There is code (opcode) that can MAKE the conquer.exe to JUMP that call (conquer.exe will think that the scan is made succefully)
And that JUMP code is MADE in ours (mine and lateralus) MULTI CLIENTS...
Understood?
Oh how you're so very wrong. More proof that you stole my client. There is no such scan. Instead, there are many (100 or so?) anti-bot functions that you have to individually detect and work around, by rigorously searching for called "suspicious" functions, text strings, and a few known constants, that would take even the people who know exactly what to look for attempting this at LEAST 4 hours to pull off successfully without debugging (yes, this is why I'm so anal about people stealing my client; if you would truly understand how much work this is, you'd respect it and NOT STEAL MY WORK). Also, to "nullify" these functions most of the time requires much more than changing a jump if xxx instruction to a jump always. You don't know what you're talking about. Stop giving wrong information.
You will go to bj using this or lats clients it doesn't matter. There is no nulling there doing to client that will prevent the way TQ is detecting cooperative because there detecting the bot itself not the bot thru the client. And no reshacker bs that people are using on cooperative claiming will stop it from being detected will matter either lol there not detecting cooperative by it's name and i'm kinda surprised nobody else has figured that out yet and how tq is really detecting it lol.
Using these so called nulled clients might prevent bj from autoclickers and pixelbots and such but using cooperative ya might as well just live with the fact it's going to be detected everytime until hawt figures out the obvious on why coop is being detected.
I've been running my bot for the last week through Visual Studio (= no obfuscating = completely different executable), and I haven't been botjailed yet. And if what you're saying is true, how come people are getting botjailed just by using the FPS unlocker and nothing else? The bot doesn't interact with packets at all, except for when using the botting functions such as auto hunter/miner/whatever.
Edit:
@vecko12:
I don't recall you asking me permission to release my bot in your hack-pack. Could you please at least ask next time?
I believe you're right; it's a problem in COoperative itself, because not only is no information about your processes, accounts, etc. sent, but this information isn't even collected in my client. Plus, the only reports I've gotten from botjailing are from users of COoperative.
Although these clients are *somewhat* trial and error... I may have messed up.
Edit: Yes, Martin has assured me that information IS sent with my client. He also helped me discover a new anti-bot dll, which I'll work on fully cracking ASAP.
Oh how you're so very wrong. More proof that you stole my client. There is no such scan. Instead, there are many (100 or so?) anti-bot functions that you have to individually detect and work around, by rigorously searching for called "suspicious" functions, text strings, and a few known constants, that would take even the people who know exactly what to look for attempting this at LEAST 4 hours to pull off successfully without debugging (yes, this is why I'm so **** about people stealing my client; if you would truly understand how much work this is, you'd respect it and NOT STEAL MY WORK). Also, to "nullify" these functions most of the time requires much more than changing a jump if *** instruction to a jump always. You don't know what you're talking about. Stop giving wrong information.
There are only 3 opcodes that call TQ/CO2 scanner... 1 is for 91 game check (TQ scanner) other is for the trojan checker and the last one is for Background check which is very easy to remove... IDK what have u done with ur multi, what jumps u have made and I don't care.
There are only 3 opcodes that call TQ/CO2 scanner... 1 is for 91 game check (TQ scanner) other is for the trojan checker and the last one is for Background check which is very easy to remove... IDK what have u done with ur multi, what jumps u have made and I don't care.
No, I've done a full binary compare with your client and mine and the only thing that's different is that you added horse wall jumping, which is useless if you can't wall jump normally. Therefore, you stole, and you're bullshitting to make yourself sound legit. It's cool though. I just released something amazing. Keep up the pace buddy. Only 1 word - have fun!
You will go to bj using this or lats clients it doesn't matter. There is no nulling there doing to client that will prevent the way TQ is detecting cooperative because there detecting the bot itself not the bot thru the client. And no reshacker bs that people are using on cooperative claiming will stop it from being detected will matter either lol there not detecting cooperative by it's name and i'm kinda surprised nobody else has figured that out yet and how tq is really detecting it lol.
Using these so called nulled clients might prevent bj from autoclickers and pixelbots and such but using cooperative ya might as well just live with the fact it's going to be detected everytime until hawt figures out the obvious on why coop is being detected.
Quote:
Originally Posted by IAmHawtness
I've been running my bot for the last week through Visual Studio (= no obfuscating = completely different executable), and I haven't been botjailed yet. And if what you're saying is true, how come people are getting botjailed just by using the FPS unlocker and nothing else? The bot doesn't interact with packets at all, except for when using the botting functions such as auto hunter/miner/whatever.
UzN-Conquer 2.0 - Back Online :) 08/16/2012 - CO2 PServer Archive - 7 Replies Hello, Everyone just found out UzN-Conquer Is back online all same stuff as Last time, personally i loved this server, its amazing so am helping out by adevtising letting it get back to where is was come Join :P
::UzN-CO 2.0 ToS::
Thanks, UZN-GAMING FTW, EME FTW
LoL....
