this post was submitted on 06 Jul 2025
162 points (98.8% liked)

PC Gaming

11655 readers
574 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] andyburke@fedia.io 57 points 2 days ago (12 children)

keep your anticheat code off my cpu and on the server where it belongs.

wtf.

why is this so fucking hard for developers to understand?

[–] GreyCat@lemmy.world 9 points 2 days ago (1 children)

Nah I can't agree with this. I don't think there are many games with anti-cheats solely on the server. Even Valve has its VAC.

I agree that Kernel anti-cheats are bullshit, I don't want a rootkit on my system. But if you are already running a closed-source game, it's not a stretch to run its local anti-cheat.

And local anti-cheats make sense in and of themselves since you can't easily detect things like visual hacks from the server-side.

[–] andyburke@fedia.io 3 points 2 days ago

You misunderstand a few key things about the points I made, I think. In particular the bit about not being able to trust the client that it is running the code you think it is.

load more comments (10 replies)