Normalize T6 hexadecimal RCON GUIDs for ping matching

This commit is contained in:
2026-10-06 21:29:05 -04:00
parent 1779ae583b
commit a9059754fb
4 changed files with 69 additions and 12 deletions
+3 -1
View File
@@ -38,7 +38,9 @@ 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. Name matching
matching players by GUID first, then by name when no GUID matches. 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.