irwin

I play one of those games that doesn’t strongly enforce anti-cheating, and I agree with you that it’s a huge detraction compared to games with strong anti-cheat. But I strongly disagree about the use of invasive client-side anti-cheat. Server-side anti-cheat can reduce the number of cheaters to an acceptably low level. See for example how lichess detects and aids in detection of cheaters: https://github.com/clarkerubber/irwin And chess is a game where I feel like it would be relatively hard to detect cheating. An algorithm looking at games with actors moving in 3D space and responding to relative positions and actions of multiple other actors should have a great many more ways to detect cheating over the course of many games.

They seem to use two projects: Irwin: https://github.com/clarkerubber/irwin Kaladin: https://github.com/lichess-org/kaladin

There is such an open source system: https://github.com/clarkerubber/irwin. It seems that the last commit was some years ago, so it's either very stable or no longer used. At any rate, this is what powers anticheat on lichess.org.

Lichess’s cheat detection is open source (like everything else on the site) [0]. The training dataset isn’t public, though, and it’s practically undocumented. If you look in the `modules/game` directory, though, you’ll get an idea of what sort of data that goes into the model. Besides the engine analyses, it also looks at the time spent on each move (the `Emt` type is short for elapsed move time). [0] https://github.com/clarkerubber/irwin