Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Identify the source of latency issue in-game #15834
It would be useful to identify where the source of a slowdown comes from, while being in-game.
Maybe a ping value for each player and spectator could be an indicator here ? Or the already existing latency values ("Good", "Moderate", "Bad" IIRC).
Also, should work with "In-game kicking" #3516
changed the title from
Identify connection performance (ping) in-game
Identify the source of connection issue in-game (ping)
Nov 18, 2018
Not sure about it tbh. It won't help in the affected game unless you identify a specator as the "lagger" you could ask to leave.
My concern is that if you happen to "lag" once and people identify you, they could convince others that you are a terrible "lagger" and people should kick you from lobbies...
That is true.
There is still some kind of identification nowadays, and filtering.
And in any case, kicking often happens before the start with latency values / colors.
I'd argue that sometimes, a game can go well even if players appear to lag before starting. And vice versa.
It is punishing for the players, and the potential spectators, not to be able to know where the problem comes from. And after deciding a re-make due to lag, it results in kicking a lot of spectators to avoid potential lag.
Actually, we already have the server messages that identify players with connection problems so this wouldn't make any big difference. Instead, we would know if for example a spectator is "lagging" and could ask this person to leave. At the moment it is common to ask all spectators to leave in the hope that one might be the "lagger".