I spent yesterday writing a proof-of-concept “cheat” “detection” “mechanism”.
It’s basically collecting input packet deltas over time (which degrade), tracing against line-of-sight players only when shooting and evaluating accuracy. It’s testing the results against some really-high-up-there values I’ve collected from actual pro-player matches and of course the cheater from last week. It seems to work okay and the only false positives come from people using teleporters which mess with the camera angle deltas occasionally (which can be fixed)
At the very least, the mechanism will let the admin know that something unusual is going on, it does detect really obvious cases immediately (and we should probably tally those up and just automatically call dropclient() on them if it happens too much within a short period of time to deal with spinbots)
I don’t think that such a system should punish by itself, but perhaps the “sus-tally” can be transparent to other players so they can make an educated decision. The system could also be tweaked as to detect high-skill players and to apply handicaps to them. That way “server cleaners” have more of a challenge and everyone else keeps having fun.
What do you all think? Or am I opening Pandora’s Box with this?
#programming #admin #gameserver #quakeworld #anticheat
eukara /
npub1pn…8vegv
2023-08-07 22:19:12
Author Public Key
npub1pnyejvwjgcpcsarvhgjh32l9lu02pxxfr3n2fqfa39ukgkt79t3s38vegvPublished at
2023-08-07 22:19:12Event JSON
{
"id": "670a3e35a4c59331d846af551bf11be06e93d6b69f27c04f3b7870e5ffaa8a39",
"pubkey": "0cc99931d2460388746cba2578abe5ff1ea098c91c66a4813d897964597e2ae3",
"created_at": 1691446752,
"kind": 1,
"tags": [
[
"t",
"admin"
],
[
"t",
"anticheat"
],
[
"t",
"gameserver"
],
[
"t",
"programming"
],
[
"t",
"quakeworld"
],
[
"proxy",
"https://idtech.space/objects/db10d5f4-3e75-4d75-9c09-389840e8c171",
"activitypub"
]
],
"content": "I spent yesterday writing a proof-of-concept “cheat” “detection” “mechanism”.\n\nIt’s basically collecting input packet deltas over time (which degrade), tracing against line-of-sight players only when shooting and evaluating accuracy. It’s testing the results against some really-high-up-there values I’ve collected from actual pro-player matches and of course the cheater from last week. It seems to work okay and the only false positives come from people using teleporters which mess with the camera angle deltas occasionally (which can be fixed)\n\nAt the very least, the mechanism will let the admin know that something unusual is going on, it does detect really obvious cases immediately (and we should probably tally those up and just automatically call dropclient() on them if it happens too much within a short period of time to deal with spinbots)\n\nI don’t think that such a system should punish by itself, but perhaps the “sus-tally” can be transparent to other players so they can make an educated decision. The system could also be tweaked as to detect high-skill players and to apply handicaps to them. That way “server cleaners” have more of a challenge and everyone else keeps having fun.\n\nWhat do you all think? Or am I opening Pandora’s Box with this?\n\n#programming #admin #gameserver #quakeworld #anticheat",
"sig": "f18003cace78ddb1184b886091786ad309ae574cc04268d4d0a3df068ac859f8f802eeaed4cf35b69dd3041cea1eb9420f7a979ade279d131796b0a777b57d19"
}