Right now there’s no way to read an individual connected client’s ping or packet loss through the ServerQuery / Query API.
clientinfo returns plenty of per-client connection data — bytes and packets sent/received, current bandwidth, connected time, etc. — but it has no field for that client’s ping to the server or their packet loss. The only network-quality numbers available through Query are the server-wide aggregates in serverinfo (virtualserver_total_ping, virtualserver_total_packetloss_*), which are averaged across every connected client.
The data plainly exists: any regular client can open Connection Info and see another user’s ping and packet loss in real time. It simply isn’t surfaced anywhere in the Query API, so a tool connected via ServerQuery can only see the server-wide average and never tell which client is having a bad connection.
Request: add per-client ping and packet-loss fields to the clientinfo output (e.g. connection_ping, connection_packetloss_total), so admins and monitoring tools can identify individual clients with connection problems instead of only seeing the server-wide mean.
Why it’s useful:
-
Diagnosing a specific user’s lag/dropout complaints without asking them to read numbers off their own client.
-
Monitoring dashboards and health tooling that currently can’t attribute poor network quality to a particular client.
-
Proactively spotting a degrading connection before the user notices.
Thanks for considering it.