this post was submitted on 31 Oct 2024
410 points (99.8% liked)
Linux Gaming
15291 readers
17 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME
away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Servers often don't send player data that is outside of the immediate area of the player, but they have to for enemies that are nearby. If they walk around the corner and your client didn't know about it, then you'll be waiting for your ping time to even render the enemy. I.e. they walk around the corner and already shot you, then you see them suddenly appear a full players width away from the corner, and you die. Aka peekers advantage amplified.
Same deal with footstep sounds, bullet tracers, a player's shadow, etc. Your client needs to know where all this is coming from and it can't do that if it doesn't know the enemy exists and where. And that is a buffer zone for hackers to derive wall hacks from.
So basically, the overwhelming majority of servers do do all those things, since the late 90's. Hacks tend to work within those bounds. The most common, impactful and hard to detect cheats are based on providing perfect mechanical inputs. Aka aim hacks. Nothing about limiting info from the server can prevent that unless you also want the legitimate player to be unable to see their enemies.
The obvious solution is to make wall hacks an intended game mechanic.
You joke but blops 6 is out rn and did this on tiny maps
Its horrible and amazing at the same time