PDA

View Full Version : Please Confirm


UnrealD
22nd July, 2007, 08:25 PM
ScriptLog: ### -------------------------------------------------------------
ScriptLog: ### ANTHCHECKER - PLAYER KICK
ScriptLog: ### -------------------------------------------------------------
ScriptLog: ### - Player name :
ScriptLog: ### - Player IP :
ScriptLog: ### - Player OS : Windows
ScriptLog: ### - EngineVer : 451
ScriptLog: ### - RenderDev : Unrecognized class ini:Engine.dll
ScriptLog: ### - RenderVer : Unknown Renderer
ScriptLog: ### - RenderChksm : D41D8CD98F00B204E9800998ECF8427E
ScriptLog: ### - RenderSize : 0 bytes
ScriptLog: ### - TimeStamp : 22-07-2007 15:00:06
ScriptLog: ### ----------------- Additional information -----------------
ScriptLog: ### - GUID : feX]pEJDCpCA>AH>CAAHpCAKEJKFCpI1029_-188445553
ScriptLog: ### - GUID Valid : True
ScriptLog: ### - KickType : 3
ScriptLog: ### - AnthChecker : v1.37 (Build 3)
ScriptLog: ### - Reason : Client failed to generate checksum
ScriptLog: ### - File : Renderdevice
ScriptLog: ### - Status : F / F / F
ScriptLog: ### -------------------------------------------------------------
Even after it said he was kicked, he was still able to play in the server, and use his aimbot.

I am using AnthCheckerS_v137.

oofki1
23rd July, 2007, 02:09 PM
I believe if a person uses a cracked copy of anthchecker it will display they are kicked but will not actually kick them. I suggest using utdc to check the md5 of anthchecker files and anthchecker to check utdc files.

I always feel that the more checks and mods you have the more lag you get so I actually do not run anything other then utpure on the server i rent for some friends. Its not hard to spot and ban a botter and I know I can trust the people who play there anyways. I think in 2 months there has only been 1 botter show up.

AnthraX
23rd July, 2007, 02:26 PM
This log usually means that _something_ has tampered with the engine. I've researched it at some point (a long long time ago) and I believe that this was not necessarily a cheat. As for the "not being kicked" problem. This is indeed possible with AC v1.37, I've fixed this problem in v1.38 but it seems that I didn't add the fix to the latest v1.37 build. I'll include it in v1.37 build 4

UnrealD
23rd July, 2007, 08:14 PM
ah k. Ya cuz it was weird, he wasnt kicked. And he was actually using an aimbot.

oofki1
24th July, 2007, 03:10 AM
Thats what i saying... I believe the only thing the cracked version does it makes it so you dont get kicked. It still logs you and everything.

AnthraX
24th July, 2007, 01:03 PM
Thats what i saying... I believe the only thing the cracked version does it makes it so you dont get kicked. It still logs you and everything.

The cracked version that I know of does this indeed.