Effectively doing that server-side would substantially increase the bandwidth requirements though.
If we take wallhacks as an example, that takes place entirely in the local rendering pipeline. In a game like Battlefield or Counter Strike, smoke and foliage are used for tactical purposes.
Aimbots read player location data sent from the server and send input commands to the OS to automate headshots.
Preventing local memory from being read and modified outright prevents (well, substantially raises the skill ceiling) for performing these kinds of hacks.
I have a hard time envisioning a server-side solution to those.
security of the client against the owner of the device on which the client runs
Effectively doing that server-side would substantially increase the bandwidth requirements though.
If we take wallhacks as an example, that takes place entirely in the local rendering pipeline. In a game like Battlefield or Counter Strike, smoke and foliage are used for tactical purposes.
Aimbots read player location data sent from the server and send input commands to the OS to automate headshots.
Preventing local memory from being read and modified outright prevents (well, substantially raises the skill ceiling) for performing these kinds of hacks. I have a hard time envisioning a server-side solution to those.
That’s exactly who a cheater is though