Ok now before anyone panicks and goes all crazy this is just a discussion on possible techniques that TQ maybe trying to implement to prevent cheating.
I have heard many folks on the conquer forums talking about conquer maybe using hooking and stealthing to thrawt cheaters.
2. I also have read where a mod mentioned that a new routine was introduced to passively scan most commonly used memory addresses and used by hackers,
If this is so that might explain why some of the more popular cheats where disabled. I do believe that the anti hooking was used to disable cotobo. As i recall 4312 though cotobo ore dropper was disabled but cotobo could still be iniatilized with the conquer window. This patch though I noticed that cotobo itself failed to hook into conquer.
Also if tq is using a subroutine to passively scan game memory addresses then this could be the beginning of a series of patches that will attempt to lock out certain game functions or even be used to ban players. They have definately went just from encrypting to anti hooking. They maybe attempting to implement something similiar to vac2 maybe not something as expensive as vac2 but something along the same lines developed by their own personel. If that is the case they will probably be patching as new hacks are discovered. Which means even if you get aimbot to work there is a likelyhood that successive patches will be used in later versions of co2 to introduce newer and bolder anti cheating measures.
Yes before the flaming starts. I know i have been accused of conspiracy theories in the past. Yet I have noticed that CO2 is behaving differantly than it did before this latest patch. My firewall detected a memory report being issued to co2.t.91z earlier today which caught my attention. I checked my firewall logs and noticed that other such memory reports had originated from co2 client after patch 4334. This latest memory report though originated after patch 4335 and it was more agressive. So I will say this i'm not the one coding the hacks or developing them but i would carefully look at the client and see what they have done.
my fire wall's application monitor has noticed a high threat status communication from the conquer exec reporting memory status to 216.93.170.133:http(80) now this could be totally harmless. but this was report had generated after i had already logged into the game and was playing. i sent this to my firewall provider to find out what they had to say about it. They concluded that it was a memory usage communication between client and provider. So I dont know maybe i'm just being paranoid but someone needs to check this out that has more experience with anti cheat methods than I. this could be innocent i dont know.
I have heard many folks on the conquer forums talking about conquer maybe using hooking and stealthing to thrawt cheaters.
2. I also have read where a mod mentioned that a new routine was introduced to passively scan most commonly used memory addresses and used by hackers,
If this is so that might explain why some of the more popular cheats where disabled. I do believe that the anti hooking was used to disable cotobo. As i recall 4312 though cotobo ore dropper was disabled but cotobo could still be iniatilized with the conquer window. This patch though I noticed that cotobo itself failed to hook into conquer.
Also if tq is using a subroutine to passively scan game memory addresses then this could be the beginning of a series of patches that will attempt to lock out certain game functions or even be used to ban players. They have definately went just from encrypting to anti hooking. They maybe attempting to implement something similiar to vac2 maybe not something as expensive as vac2 but something along the same lines developed by their own personel. If that is the case they will probably be patching as new hacks are discovered. Which means even if you get aimbot to work there is a likelyhood that successive patches will be used in later versions of co2 to introduce newer and bolder anti cheating measures.
Yes before the flaming starts. I know i have been accused of conspiracy theories in the past. Yet I have noticed that CO2 is behaving differantly than it did before this latest patch. My firewall detected a memory report being issued to co2.t.91z earlier today which caught my attention. I checked my firewall logs and noticed that other such memory reports had originated from co2 client after patch 4334. This latest memory report though originated after patch 4335 and it was more agressive. So I will say this i'm not the one coding the hacks or developing them but i would carefully look at the client and see what they have done.
my fire wall's application monitor has noticed a high threat status communication from the conquer exec reporting memory status to 216.93.170.133:http(80) now this could be totally harmless. but this was report had generated after i had already logged into the game and was playing. i sent this to my firewall provider to find out what they had to say about it. They concluded that it was a memory usage communication between client and provider. So I dont know maybe i'm just being paranoid but someone needs to check this out that has more experience with anti cheat methods than I. this could be innocent i dont know.