Fellow team mate in CS caught hacking, PLEASE READ

[Trunks]

Ok, on our servers stats page (Stats it says a fellow plater was caught hacking (click on the Cheaters tab). This is what he said in response to it.

If you guys look under the cheaters section it lists me having two cheats. Remember when I was talking about the currupt memory deal Ryan? Well that happened to me twice yesterday again. So I restarted and it didn't give me the message anymore. So what's the dealeo? You guys know I don't hack. Even ask Dom about yesterday. We were at Pro Speedball and it kicked me for the currupt memory. So what do I do?

Now my questions are these...

1) How does Psychostats catch cheaters? What logs does it check, if any at all? What exactly does it catch?

2) Is it possible that his "memory errors" could have tricked Psychostats into thinking that has was actively hacking? Or is it some lame excuse? He wasn't picked up by HLG, but he WAS automatically kicked by the server twice I believe.

What exactly is going on? I need serious answers here please. Cheating is not tolerated by our clan, and we sure as hell don't want to harbor these ****************************************** if you know what I mean.

[Mancora]

Well if he was kicked twice do you guys do enough logging to be able to find when he was kicked and what for?

[Paladyr]

Sounds like BS. Did he give an exact error message relating to his memory problems?

[Trunks]

He wasn't logged in any of the logs that we saw. I think we looked through all of them. I'm not sure what memory error he had, but I do believe him as I don't think he hacks.

[Doomah]

Well supposedly there was a problem with the VAC's, and one of the things that may trigger a cheat detection is having corrupt RAM. That was a little while ago and since then new VAC's came out, so I'm not too keen about it now.

As for the situation, it does sound fishy. But the only way to verify 100% is to watch them over the shoulder. If that can't happen, then it's a judgement call.


Decisions decisions.

[Mancora]

Ok if i remember correctly the logs log everyone by their unique user ID and their current player name, copy all the log files in question into one folder and if you have something like the admin mod that brodcasts a message out to the server, and your logging amount is turned on so it will record this, then

if your in windows you can do the serach function and look for text in side the files, specifically his wonID.

or you can open up the files and do a serch for his wonid on each file.



Then again that might take a while if he plays there a lot and you have a lot of logs to look over, you might try seraching for the string (the exact words, exact letters, commas, exactly what admin mod says) that the adminmod brodcasts when it kicks someone for cheating.

[sublim21]

if he stands accused of cheating, then find out what his average kill:death ration is. Then, make him demo playing a couple of rounds, if there is a sharp decrease in the ratio, then hes cheating. Basically a put up, or shut up kind of thing.

[Mancora]

mmmm, i dont know about that quick of a test, moral has a lot to do with how someone, or at least i play, doing a demo can put a stab in the confidence thus lowering the K ratio


One other thing you could do is go in under an assumed name and be a spectator on him in first person.