this post was submitted on 18 Dec 2024
76 points (98.7% liked)

PC Gaming

8770 readers
510 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
[–] [email protected] 0 points 3 days ago (2 children)

Why impossible? Server-authoritative programming is common in PVP gaming, even high-performance recent games. I don't think anyone is suggesting lazily loading chunks of player data like wandering into a new chunk in Minecraft. Just write efficient, clean code that anonymizes or encrypts player data so it can't be read client-side.

[–] Mojave 9 points 3 days ago* (last edited 3 days ago)

Okay, now the player data is encrypted and unreadable by clients.

How will the client display where the players are without data....

Why are you bothering to spend cycles sending this useless, encrypted data......

If you mean to decrypt the player data once it reaches the client, then you have solved no issues.............

[–] Evotech 2 points 2 days ago (1 children)

Show me one multiplayer fps that does not trust the client with anything.

[–] [email protected] 2 points 2 days ago (1 children)

The issue here was that fortnite broadcasts locations of enemy players in packet data, not that it trusts clients "with anything".. where did you get that from?

[–] Custodian1623 1 points 2 days ago (2 children)

how else should it inform the client of enemy players

[–] Mojave 2 points 12 hours ago

Work arounds are for devs to solve, not schmucks on lemmy. CS:GO used to use something similar to occlusion culling to prevent this exact problem. Don't send the client all of the enemy locations/data unless the client is within roughly the right distance/sight to see that enemy. This is not a full fix, but dramatically nerfs wall hacking.

I've seen community plugins for TF2 and other source engine games that will add "ghost" players. Generate ai characters, turn them invisible, and send their data to clients. If someone keeps shooting at the ghosts, they can easily get caught and banned.

There are entire industries dedicated to finding solutions to this problem, check out this research paper about this exact subject if you want.

[–] [email protected] -4 points 2 days ago* (last edited 2 days ago) (1 children)

That's an excellent issue for you to research on your own time! If you know anyone on the OverWatch development team you could ask for their input as well. Please report back to this thread with your findings, we're all very interested in the results.

[–] Custodian1623 1 points 2 days ago (1 children)
[–] [email protected] -4 points 2 days ago (1 children)

Sorry to hear that. Best of luck with your future projects though.

[–] Custodian1623 1 points 2 days ago

be nicer to people