TimeLogger

Crash recovery (temp_logout)

• If the client exits without firing PLAYER_LOGOUT (crash, force quit, etc.), the last row in events can be a login with no matching logout.
• The addon stores TimeLoggerDB.temp_logout: the same shape as a logout row, updated: - once immediately after each successful PLAYER_LOGIN (while in world), and - every 5 minutes while you remain logged in.
• On the next PLAYER_LOGIN, if the last stored event is still login, the addon appends a synthetic logout using the last temp_logout snapshot, marked with recovery = true

Limitation

• Saved variables are usually written on logout or /reload, not continuously.
• If the client dies before a save that included a recent temp_logout, recovery may not run; you can still see login → login with no logout.
• When recovery does apply, the logout time can be up to ~5 minutes after the real exit (or sooner thanks to the immediate update on login).
• On a clean PLAYER_LOGOUT, the heartbeat ticker stops and temp_logout is cleared.