• @Evotech
    link
    English
    22 days ago

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

    • @[email protected]
      link
      fedilink
      English
      22 days ago

      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
        link
        English
        12 days ago

        how else should it inform the client of enemy players

        • @Mojave
          link
          English
          24 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]
          link
          fedilink
          English
          -4
          edit-2
          2 days ago

          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.