The `yaw` value of non-client-players is constraint to [0; 360), so when that boundary is crossed, the `renderYaw` starts interpolating to its goal the incorrect way round (instead of crossing the 360 boundary as well). Instead we now use the `headYaw` value, which does not wrap around and as such does not have this issue.