I’m getting accused of cheating recently these days and to prove I’m not exactly cheating, I normally tell someone to check the replay to clarify things.
The problem is, the replay isn’t helping as it looks extremely choppy and gives more the impression that I’m using some type of aimlock bind than legitimate tracking; I’ve also questioned myself if that’s more than a connection issue (since I play on wi-fi instead of ethernet) or the replay (which is server based and not client).
I don’t know if anyone made this topic already, so
Here’s the code for the replay: AQA69M
(ex. 00:20:40-00:20:43)
I know from a friend of mine that that happens when you’re on high ping.
Haven’t watched the replay nor do i suffer from this myself but I have tried convincing people on the forums in the past that some replays of players can appear snappy and suspicious while in fact this is caused by packet loss or low end computers. I would pull up the in-game network statistics to check if you have packet loss.
This won’t help with people not believing you but you’ll just have to ignore them i guess.
The replay/highlight system also does not accurately interpret the precision movements of a player’s reticle and snapping movement is extremely common when reviewing them. This is why Blizzard will not use replays or highlights as the only evidence to confirm a cheater.
If you are accused of cheating, take it as a compliment.
2 Likes
This is typically caused by networking issues like high latency or packet loss.
inconsistent ping makes the replay and potg choppy.
I have the same problem. I get a little spooked when I get potg on days when my packet loss is particularly high, lol.
Packet loss and low FPS will cause very suspicious replays. I have yet to get falsely actioned for it yet though, thankfully