Remove name fallback from RCON ping matching

2026-10-06 21:31:13 -04:00
parent a9059754fb
commit baee64a067
4 changed files with 12 additions and 53 deletions
@@ -38,12 +38,10 @@ latency measurement in milliseconds, as a nonnegative JSON integer (for example,
 `"ping": 42`). Send `null` or omit the field when unavailable; do not substitute
 zero for a missing measurement. Older reporters without this field remain valid.
 Fleet prefers telemetry ping and fills missing readings from fresh RCON status,
-matching players by GUID first, then by name when no GUID matches. For T6, RCON's
+matching players only by GUID. For T6, RCON's
 hexadecimal GUIDs are compared with telemetry's decimal GUIDs using exact integer
-conversion; stored GUIDs remain unchanged. T5 GUIDs are compared as reported. Name matching
-removes CoD color codes and surrounding whitespace, stays case-sensitive, and
-requires a unique name in both rosters. A player already matched by GUID cannot
-be reused by name. Occupied lobbies continue RCON polling every 30 seconds.
+conversion; stored GUIDs remain unchanged. T5 GUIDs are compared as reported.
+Occupied lobbies continue RCON polling every 30 seconds.
 RCON supplements only ping; telemetry still supplies roster membership and scores.
 RCON pings expire after 90 seconds and must match the current map and server
 lifecycle. Missing or ambiguous matches display `—`. Telemetry ping is retained