Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Jitter (the ownership handover)
When a zombie's simulation moves from one player's machine to another's, the two views of it have to be reconciled. On a clean, even connection that is invisible. On an uneven one it is the moment the zombie jumps backwards, re-stands, or attacks from a position it was not in. This is the single most characteristic network symptom in the game.
Packet loss (hits that never happened)
Melee combat is a sequence of discrete events - a swing, a connection, a stagger, a death. There is nothing to interpolate a missing one from. A lost packet does not make your swing land late, it makes it not land, and you find out when a zombie you were certain you killed keeps walking.
Ping (to a community box)
There are no official servers with regions to pick from. You join a specific community server on a specific machine, so your ping is a property of which server you chose. Under 100 ms keeps melee timing workable; the servers people complain about are usually ones hosted a continent away.
What you see in game, and which number on this page explains it.
A city block of zombies is a lot of simulation. Every one of them has a position, a state, a target and a path, and running all of that centrally for dozens of players spread across a large map is far more than a typical community server can afford. Project Zomboid's answer is to give the work to the machines that are already nearby: the zombies around you are simulated by your client, and the server's job is to keep everyone's picture roughly consistent.
The gain is real - it is why servers with substantial player counts and enormous hordes exist at all. The cost is that authority is constantly moving. As you walk down a street, zombies become yours; as another player approaches, some of them become theirs. Each of those transfers is a small negotiation, and every negotiation depends on packets arriving in a timely and orderly way.
This is what players are actually seeing when they describe rubber-banding. The zombie is not being teleported by a bug; two machines briefly disagreed about where it was and something had to give. On a clean line the correction is small enough to be imperceptible. On a line with jitter or loss it is a full step, a re-stand, or a hit registering from a position the zombie had already left.
The same model explains the game's reputation in player-versus- player fights. When a client has meaningful say over combat outcomes, the player whose packets are believed first has an advantage, and the result is disagreements about who hit whom that no amount of personal connection tuning fully resolves. Measuring your own line is still worth doing - it removes your contribution to the problem - but it is honest to say that it does not remove the model.
If the chart above shows packet loss or high jitter, work through
these in order.
Why do zombies rubber-band in Project Zomboid multiplayer?
Because zombies near you are simulated by your machine rather than by the server, and that responsibility hands over between players as everyone moves. Each handover has to reconcile two views of the same zombie, and an uneven connection makes that reconciliation visible.
Is PvP reliable in Project Zomboid?
It is inherently less reliable than in a server-authoritative game, because of the same distributed simulation that makes large hordes possible. Many community servers limit or disable it for that reason. A clean connection helps but does not change the underlying model.
Does packet loss cause the double-hit problem?
It causes the related one. Melee events are discrete, so a lost packet removes a swing or a death rather than delaying it - which is what a zombie you killed getting back up actually is. Look for red lines on this chart when it happens.
Which Project Zomboid server should I join?
One geographically near you, before anything else. There are no official regional servers, so the server list is where your latency is decided, and distance is the one part of it that no setting on your end can undo.