Server Cheat Detection Script

[Garrett]

Would it be possible to make a script for a server that will automatically catch aim-bots and/ or other hacks? 
Possible idea, the script will continuously calculate each player's kill - death ratio and compare it to all of the other players playing in the server.  If there is a drastic difference in ratios, the script will automatically demo that player. 
Another idea, the server will take a screen shot ever 'X' amount of minutes and analyze the screen shot for wall hacks, ESP, etc.  If any screen shots are out of the ordinary, the script will make a log of the screen shot and other needed info.

Are any of these ideas even feasible?

[Eiii]

You know what works better than that? The current cheat detection.

How do you suggest that the server analyze the player's screenshot for something 'out of the ordinary'? And your first idea implies that hackers will do considerably better than normal players, which isn't always the case.

[T3RR0R15T]

And your first idea implies that hackers will do considerably better than normal players, which isn't always the case.

^^

[Garrett]

Another detection system wouldn't hurt.

[Eiii]

But in this case, it'd be a pain to implement and maintain-- and honestly, who cares if there's a speedhacker running around in a pub? It's just waaay to much work for just about zero benefit.

[Garrett]

The more hackers you catch, less people will attempt to hack later down the road.

[i_am_a_pirate]

That's not the point. I dont really care too much about pubs. Even if someone cheats in a match, its so bleedin obvious by the second map that they are and if they are (correct me if i'm wrong) then the match will be overlooked and the player banned for however long AND HAVE YE BLACK SPOT. sorry

[Garrett]

That's not the point. I dont really care too much about pubs. Even if someone cheats in a match, its so bleedin obvious by the second map that they are and if they are (correct me if i'm wrong) then the match will be overlooked and the player banned for however long AND HAVE YE BLACK SPOT. sorry

Cheating starts in the pubs.  If you can get away with it in a pub, you will try to in a match.  I would reply the the second part of your response but I can't understand what exactly your saying.
A primitive server detection script could also act like a ban reinforcer too.  Checks a person's global login account, IP, and other information against the current global ban list.
When this game starts even more popular, the extra help for finding cheaters would only help the cause.

[i_am_a_pirate]

sorry, to retype the second part:
In a match, its best of 3 maps. When they cheat with an aimbot, it's so obvious that by the end of the first map that they're cheating anyway, so you can just take a demo of the second map focusing in on the cheater, post in the forums, the guy gets the black spot and end of cheater. It might even be quicker than the proposed scheme.

[Garrett]

sorry, to retype the second part:
In a match, its best of 3 maps. When they cheat with an aimbot, it's so obvious that by the end of the first map that they're cheating anyway, so you can just take a demo of the second map focusing in on the cheater, post in the forums, the guy gets the black spot and end of cheater. It might even be quicker than the proposed scheme.

As of now it will be but what about in the future when there are another 1000- 2000 actively playing and talking on the forums?  Jitspoe will be flooded with demos and proof of hacking that he will not be able to do anything else but the losers who have to download their skill.  I am not disagreeing with you, just looking into the future. 

[y00tz]

Hmm, how soon is 'the future'?

[Cameron]

Gore loses?

[ViciouZ]

Gore loses?

The al variety.

[Eiii]

Heh, if this game ever gets to 1000 active community members, I doubt jits will be the only one dealing with things.

[Loser]

Hmm script eh

so you mean

//
Uint Overly_Precise;
Uint Limit;
void function Check_If_Aimbotting()
{
// analyse whether the cursor is over a target too precisely
// If true add one to Overly_precise
// if false then set a timer before setting Overly_Precise to 0
}
void function Play_Is_Aimbotting()
{
 If (Overly_Precise > Limit );
{
//Call a vote whether or not to ban the person
}
else;
{
//Do nothing
}
}

// end

That would require a lot of input from jitspoe though....

[ViciouZ]

And how do you determine "too precise"?

[i_am_a_pirate]

locking on to the person.

Ever thought of tose aimbots that lock in in the direction of movement to compensate for the non-instant shooting?!?

[Deranged]

What if someone just has really good aim. This idea is full of fail and possibilities for more fail >.> It only takes one shot to kill someone anyways, so all you could really detect is drastic mouse movements (paintball is instagib if you forgot since you never play it, Garrett ).. which would get anyone spinning around in circles in trouble lmao. Even if you added in a detection for snapping, a few good twitch shots would get someone banned. The only viable detection is detecting whether or not the ACTUAL botting program is running on the client side, which is what we already have.

Idea, pseudocode this out in its entirity and tell me if you still think it's worth jitspoe's time

[Eiii]

Here, to simplify that further--

Code: [Select]

if (hacking) {
  ban;
}

Yeah, it's not as simple as you propose. Definitely not worth the effort of putting a whole build into further hack detection.

[Garrett]

[...]
Idea, pseudocode this out in its entirity and tell me if you still think it's worth jitspoe's time

I will start on that soon.  What code structure should I use?  C?