Disconnected client entities trigger entity update once

[markatk]

When a client disconnects (or timeouts, doesn't matter) from the server there is one entity update event triggered after the disconnect event.

...
Update entity 1 for client 1773685128
Update entity 0 for client 647576079
Update entity 1 for client 1773685128
Update entity 0 for client 647576079
Update entity 1 for client 1773685128
Update entity 0 for client 647576079
Update entity 1 for client 1773685128
Update entity 0 for client 647576079
client 647576079 disconnected
Update entity 1 for client 1773685128
Update entity 0 for client 647576079

[inlife]

interesting
i'm assuming that is happening because of entity destruction on the server-side is not immediate, but rather it allows for one last tick to happen before entity destroy will be sent, however in this case, i'm not sure if that is the reason

[inlife]

hey @markatk
could you try the lastest version from master, to see if it the solves issue for you?

[markatk]

As far as my testing goes it seems to be fixed

[inlife]

oh, that is great news