[hhh]

Kernel anti-cheat (KMAC) is an effective tool when used effectively and invested in (see Vanguard), but it only works when you are consistent and the team working on it are interested and capable. Creating terrible KMAC happens all the time, and gets treated as a one-and-done thing which will always be defeated. You have to continually watch the cheat market and work actively against it.

It works, and Valorant with Vanguard is the highest quality example we have. Competitive games deserve to be taken seriously and should have the best attempt at ensuring integrity, and not written off as a wasteful effort to keep Linux users out.

https://playvalorant.com/en-us/news/dev/vanguard-hits-new-ba...

[sylware]

You are very mistaken: what "works" (see below) here is an invested and permanent team, not a kernel anti-cheat.

Effectiveness, yes, at giving hackers easy kernel an...access.

And trying to spot cheaters using external AI based hardware: you may have a chance with data collection on servers (no need of kernel access).

It is so much obvious, I am even wondering all that is made-up to give easy kernel access to some "services", seriously.

And it seems such games are still rid of cheaters.

[hhh]

Valorant reports ~1% of games having a cheater. Apex Legends self-reported over 10x that.

[sylware]

It is not related to th kernel anti-cheat: it is to have permanet and dedicated team to deal with that.

My english is so bad?

[teravor]

if you are actively engaged why do you need kernel level access? you can always sneak a subtle remote execution pathway into your game so you can reliably run userland code at will. kernel level cheats will escape direct detection but you can always hot patch your game engine in such a way that their memory reading patterns will give them away through cache timings.