WhatPulse Forums » Feature requests » Client software v » Redesign the cheating prevention system Welcome back, Guest.


Post Reply 
 
Thread Rating:
  • 3 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Redesign the cheating prevention system
12-20-2006, 09:35 AM
Post: #1
Redesign the cheating prevention system
Currently, one cheating prevention(ignoring other preventions) is simply not allowing someone to pulse keys if the keycount is over a certain kps?

This is easily avoided by not typing any further for a period of time, before pulsing. The flaw here would be that the whatpulse client simply takes the entire length of time into consideration, and not specific intervals.
A person could easily cheat a few million keys within a minute, and then wait it out until the kps averages down to an acceptable number before pulsing to the server, therefore bypassing this weak prevention method.

Rather than to monitor the kps over the entire length of time, I suggest a new method of detection is put into place, whereby the kps is counted in time intervals(possibly hours or minutes). This would be a more foolproof method of detecting cheaters.

The monitored time intervals would then have a keycount limit (eg 1000 keys max per min, or something high)
The client could then monitor the incoming keys per minute, and each time the key limit is breached, an infraction is marked agaisnt the user.

Eg, A cheater decides to hack 1mil keys into his client, and with bots and such he achieves it over a period of 10 mins. He would then leave his computer idle so that his kps averages out to look legit when he pulses to the server.

The current client would then pass it off without suspicion, and the only way that cheater would be caught is if other users monitored him regularly, or if he slipped up somewhere and made a mistake.

So, with my idea into place, as he bots his 1mil keys, the client goes through the interval checks, monitoring individual minutes. During the 5 minutes he is botting, each of those minutes breach the limit because there is an amazing 200k keys a minute. Each minute that has a breach in the kps limit would mark up an infraction. (Note these infractions would not be visible to the user)
When he finally pulses his keys, information would be sent to the server regarding the number of infractions done in the pulse.

Users with high numbers of infractions could them be banned accordingly, rather than to have users waste their time looking through user profiles for high key counts.

Meh, I think my idea is badly worded in this post, but at least I'm trying to improve whatpulse... oh well, if I was unclear of anything, please ask. Or if the idea is unable to be implemented, just say so straight away.
Find all posts by this user
Quote this message in a reply
12-20-2006, 01:19 PM
Post: #2
Redesign the cheating prevention system
My Possible rebuttal to this idea would be complaints of extra CPU usage. Ye Gods, i've lost a minute percentage of my CPU power. Small to some, but others may complain.

The other issue is that this essentially only solves the issue in relation to high KPS. What if a cheater sets up a bot that regularly types characters over a long period of time. Theres nothing to say that they cant keep up a high KPS this way, but the WhatPulse Client would not detect this.

This would then bring in the idea of time based checks, such as people typing for days straight would be noted and suspended. But this would be rather hard to code and manage. How do you determine how long is too long? If you set a hard limit, then the cheaters will sit on it. Set the limit too low however, and real users will be affected.

Heuristics based detection is possible, but that is an area that a) i have not much knowledge of, and b) of the small part I do know, it is processor intensive, and hard to code!
Find all posts by this user
Quote this message in a reply
12-21-2006, 08:44 AM
Post: #3
Redesign the cheating prevention system
The fact is that we cannot detect ALL cheating that takes place. However, I do agree that this is an interesting way of handing things. If you were to have it check once per hour, or heck, even once per day, that would help to detect the hardcore cheaters, and those are the ones that interest me the most.

The idea of many of these anti-cheat measures is to help reduce the number of cheaters, and also to help us tell who is cheating and who is simply pulsing from multiple computers. All we need is something fairly light to take care of that.

[Image: XKalSig1.png]
Visit this user's website Find all posts by this user
Quote this message in a reply
03-27-2007, 08:39 PM
Post: #4
Redesign the cheating prevention system
Checking intervals isn't going to fix anything. How hard is it going to be to have a program output a number of keystrokes just under the limit? If someone is lame enough to cheat this, they are lame enough to do that.
Quote this message in a reply
03-31-2007, 08:28 PM
Post: #5
Redesign the cheating prevention system
Sure, we can increase security and reduce cheating more and more. But at some point, the security we could install into the program will turn the simple keystroke counter into a program that eats away half your system resources. Where do we draw the lines?

In my opinion, cheating can never be 100% stopped, but we can put in place efforts that significantly reduce users' abilities to cheat. I think that's the best we can do without having to produce a system drain.

[Image: XKalSig1.png]
Visit this user's website Find all posts by this user
Quote this message in a reply
04-01-2007, 12:12 AM
Post: #6
Redesign the cheating prevention system
And also ways to point them out more (whether it was intentional or not, miles and Profiles are great at catching out cheaters).

What we seem to need though is a more active anti-cheat group since everyone seems very busy and no one is getting removed now-days..

Agreed, however, X-Kal. Nice to have you back!
Find all posts by this user
Quote this message in a reply
04-01-2007, 09:47 PM
Post: #7
Redesign the cheating prevention system
*bows*

There is also the whole issue of implementing the new anti-cheat program that'll take time. Wasted & PF'll have to do that bit.

[Image: XKalSig1.png]
Visit this user's website Find all posts by this user
Quote this message in a reply
04-12-2007, 08:14 PM
Post: #8
Redesign the cheating prevention system
Whatever mechanism you build in the program can be easely circumvented.

You only need a network monitor(linux router will suffice, less /dev/eth0) and filter out all network traffic.

Figure out what the whatpulse program sends out, write a little program dat sends that exact bulk of code and response fromt he server, and that sends the specific info up to the server.
Have the program go in a loop and you can be up to a zillion zillion keystrokes in a few minutes.

The only safe bet is server side protection, counting an average keystrokes per day.

What would be a safe bet for whatpulse:

Take averages from all users: total keystrokes / (days they are member - time since last pulse) = the average keystrokes they have per day.

Add up all averages / number of members = average keystrokes per day for a normal person

By doing this calculation by all members you get a reliable statistic which you can use to check against cheating.

If anyone breaks the statistical average per day by his last 3 pulses raise a red flag and keep the user monitored to see if it's a good typist, or a cheater.

but building in a checking mechanism in the program is pure folly. Cheaters don't need the program.

Michael
Quote this message in a reply
04-13-2007, 06:14 PM
Post: #9
Redesign the cheating prevention system
Tsunim Wrote:Whatever mechanism you build in the program can be easely circumvented.

You only need a network monitor(linux router will suffice, less /dev/eth0) and filter out all network traffic.

Figure out what the whatpulse program sends out, write a little program dat sends that exact bulk of code and response fromt he server, and that sends the specific info up to the server.
Have the program go in a loop and you can be up to a zillion zillion keystrokes in a few minutes.

The only safe bet is server side protection, counting an average keystrokes per day.

What would be a safe bet for whatpulse:

Take averages from all users: total keystrokes / (days they are member - time since last pulse) = the average keystrokes they have per day.

Add up all averages / number of members = average keystrokes per day for a normal person

By doing this calculation by all members you get a reliable statistic which you can use to check against cheating.

If anyone breaks the statistical average per day by his last 3 pulses raise a red flag and keep the user monitored to see if it's a good typist, or a cheater.

but building in a checking mechanism in the program is pure folly. Cheaters don't need the program.

Michael


and that's what the token is for?

There are 10 sorts of people, those who know binary, and those who don't.
[Image: 2604687.png]
Find all posts by this user
Quote this message in a reply
04-14-2007, 04:22 PM
Post: #10
Redesign the cheating prevention system
Exactly!
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Disable "pulsed!" popup bubble in Windows system tray laundryanto 5 6,308 02-23-2017 01:49 AM
Last Post: laundryanto
Thumbs Up System Tray Stats Xander641 3 4,657 11-18-2013 02:42 PM
Last Post: SearchBuzz

Forum Jump:


User(s) browsing this thread: 1 Guest(s)