Both server and client do reply with NETMSG_PING_REPLY if they receive a NETMSG_PING But the server never does send a NETMSG_PING. So technically the client never replys with NETMSG_PING_REPLY but at least it could. There is no way to make the server send NETMSG_PING

The client measures the time difference between ping send and ping reply receive. Without MSGFLAG_FLUSH the server keeps the chunk until the next flush which makes the ping dependend on when the next flush happens. Ping on localhost without flush flag: ``` [2023-01-25 20:51:47][client/network]: latency 45.84 [2023-01-25 20:51:4...