Actions
Bug #22
openReconnect after lost connection causes client to have incorrect time
Status:
New
Priority:
Normal
Assignee:
-
Start date:
06/11/2026
Due date:
% Done:
0%
Estimated time:
Description
Client needs to spend N seconds catching up to server time, where N is (suspected to be) time since last packet from previous session.
No data to display
Actions