if you resort to implementing anticheat, you’ve already lost
like there is no worse outcome, its literally no more effective than a votekick system, gets circumvented in weeks, is a huge privacy and security risk for the user and doesnt even run on non-windows platforms a lot of the time, locking your userbase to a dead-end operating system
like just admit youve failed at building a healthy community
@atlrvrse @OrangeCatCatBoys oh yea they removed it in favor of vacnet
@coolbean what you’re talking about is client side anticheat. what you need is server side anticheat.
osu! has server-side anticheat and it’s probably the most solid form of anti-cheat in a game.
@Joseph you see, serverside anticheat can have some of the same problems (see faceit anticheat, which still locks you to windows and isnt all that effective either)
i do agree osu pulls it off incredibly well though
@coolbean osu also has a really good community that is primed to hackusate when it’s needed. that and all plays are automatically saved in the server.
it’s like imagining if every single demo file from csgo is automatically uploaded and inspected for cheating.
(also yes valve can do this they have demo files built into the client and you can save them)
@OrangeCatCatBoys @atlrvrse im gonna be honest
vac was never supposed to be the be-all end-all solution to cheating, it was supposed to keep out script kiddies and lessen the effect of cheating early on as communities build (this was literally said in a developer interview if memory serves)
but after that, it rapidly becomes reliant on community moderation, like community servers manually identifying and banning cheaters, or merely kicking them when no admin/moderator is around
case in point, the only games where vac is genuinely inadequate, are those with centralised matchmaking (csgo and post 2016 tf2)
@coolbean there is a custom TF2 Anti-cheat being developed that uses AI to analyze demo files uploaded by it’s users and basically what it does is auto-votekick any confirmed cheaters
@coolbean I’ve had pulse crash the entire bluetooth stack by having misreporting APTx and selecting it.
requiring a reboot to get functioning again iirc