This post was flagged by the community and is temporarily hidden.
1 Like
It’s mainly a server issue,
On the client side (you), it registers that you fired a shot, and through extrapolation, shows you firing a shot
However, to the server, maybe due to just a bad connection, the round the you fired was never registered. Therefore, through extrapolation, you never fired a shot and your barrel was shot. When the server sends back the packets, it kinda just overlaps the results you saw on the client.
You see yourself firing the shell, your device tries to contact the server that you fired a shell, the server never picked up that you fired a shell, the server tells your device that you never fired a shell BUT your barrel was shot, your device working with that information believes you never fired shell because the server said so.
It’s the same thing with why a bad internet connection lawn darts ya into the ground. The server doesn’t know what you did before and has to guess with what you WERE doing before. What you were doing before was flying with variables of air resistance (or in your case, not firing a shell). Server extrapolates, guesses your position, your actions, everything, to ensure a smooth gameplay for other players as well.
I wouldn’t be surprised if this would be occuring more often, especially after such a major update, since new and additional packets of data are being sent out at a higher quantity.
1 Like
Its not a toss up, its whoever has better ping, and if its a tie you both die
3 Likes
Unavoidable characteristic of networked multiplayer games.
Why do you think we click on these threads?
3 Likes
A part of the game due to network issues, lag or bad coding.
Or could it be an intentional coded flaw to alter the outcome of a scenario.