3 ms·
>You then have to deal with packet loss and latency spikes And fake packet loss and latency spikes introduced by cheaters. For example, when a cheater gets ki
by charcircuit 4y ago
>You then have to deal with packet loss and latency spikes
And fake packet loss and latency spikes introduced by cheaters.
For example, when a cheater gets killed they could send a packet from the "past" saying that they killed the other person first.
- hypertele-Xii 4y agoSeems entirely trivial to notice the pattern of lag spiking exactly at the moment of the kill.
- charcircuit 4y agoYou can do it with a constant offset. This allows the client to see into the future while taking actions in the past. If you learn that in 100 ms you are going to be headshot you can take actions while in the past to save yourself.
- hypertele-Xii 4y agoAnything that is "constant" is equally trivial to detect statistically. To hide the fact that you're always lag spiking 100ms when you see an enemy, you'd have to lag spike randomly all the time, quite a lot, and then you're asking for a kick for low ping.
- no_time 4y agoAh memories. This was rampant in the late 00's. Soldering a physical switch on the ethernet cable to cut the internet at the most tactical times... https://youtube.com/watch?v=5gE-ihY_EG0 https://youtube.com/watch?v=5gE-ihY_EG0