and they say for 5065 they have to upload there co.exe and its protected. Packing method?Quote:
#Anti inject, nothing can be injected to the client.
#Anti CID.
#Client name can be changed to be yours.
#Anti Debug.
#Anti MultiHack
Client 5095 ^ [ [Only registered and activated users can see links. Click Here To Register...] ] <- Protected co.exe
Nah, you have absolutely no idea. I do disabled the HybridAimbot but the diffrence between TQMultihack and HybridAimbot it's that the TQMH doesn't really need to be copied into CO root client folder, you can keep it anywhere in your PC and start it. If you want a proof, get a 5065/5095 client for a TQBin server and i'll give ya a Conquer.exe that bypasses the Ulti's Multihack. (Explanation, in other words, you start the client and when you press the Detect button, nothing happens so you cant copy the BFKey and make another Conquer.exe and start hex editing that.) 100% Protection again for TQBin servers (I should start selling this shit)Quote:
Nah, you managed to disable Hybrids aimbot and by chance it disabled this bot.
Ulti ^ :rolleyes:
I think u should just stop help binary servers.Quote:
Nah, you have absolutely no idea. I do disabled the HybridAimbot but the diffrence between TQMultihack and HybridAimbot it's that the TQMH doesn't really need to be copied into CO root client folder, you can keep it anywhere in your PC and start it. If you want a proof, get a 5065/5095 client for a TQBin server and i'll give ya a Conquer.exe that bypasses the Ulti's Multihack. (Explanation, in other words, you start the client and when you press the Detect button, nothing happens so you cant copy the BFKey and make another Conquer.exe and start hex editing that.) 100% Protection again for TQBin servers (I should start selling this shit)
i dunno i was kicking some hella shiet in xnityco now i cant =.=Quote:
This is not the only way to disable Multihack, there are so many, the one i have released is the easiest.