Ok, clientside protection will never work unless closed source and heavily obfuscated, then it has to be server-side. But what possible solutions could be offered from server-side protection that isn't already implemented?
Server already analyzes abnormal packets and messages (Prevents things like rapid rapid fire and large increments)
Then deterrence is my solution... What else?
- MOTD a warning message
- Ban time greater than 20 minutes maybe a day/week or even customizable by server admins
- Kick time 20 minutes to 1/2 hour
- Server analyzes the isp's DNS and compare with repeat/suspect cheaters from different IPs
- Detect client version if not updated server tells 'em to update <-- like what valve does
If you're not updated, wouldn't the client break because of missing features?
- Isolate Edit mode into another application
Server already analyzes abnormal packets and messages (Prevents things like rapid rapid fire and large increments)
Then deterrence is my solution... What else?
- MOTD a warning message
- Ban time greater than 20 minutes maybe a day/week or even customizable by server admins
- Kick time 20 minutes to 1/2 hour
- Server analyzes the isp's DNS and compare with repeat/suspect cheaters from different IPs
- Detect client version if not updated server tells 'em to update <-- like what valve does
If you're not updated, wouldn't the client break because of missing features?
- Isolate Edit mode into another application