Changelog - Version 5.7.9 (2026-05-21)

Version Information

• Updated version from 5.7.8 to 5.7.9
• Fix for the Stable bot: subathon timer now auto-ends, no longer loses time on pause/resume, and the overlay countdown no longer drifts

Bug Fixes

• Fixed subathon timer never auto-ending when time ran out
  • The subathon_countdown background task had a break statement placed outside the end-time check, so the loop exited after a single iteration regardless of whether the subathon had actually finished.
  • The task is now scoped correctly: it only breaks when the subathon has reached its end time (and gets paused + the chat message announced), or when no active subathon exists. While the subathon is still running, the task re-checks every 30 seconds.
  • Without this fix, a subathon’s database row stayed paused = False past end_time indefinitely until a moderator manually ran !subathon stop.
• Fixed up-to-59-seconds being lost every time a subathon was paused
  • pause_subathon was flooring the remaining time with // 60, so any sub-minute remainder at the moment of pause was silently discarded. A subathon paused at 1h 23m 47s would resume at 1h 23m 0s.
  • The bot now stores the precise remaining time in seconds (new remaining_seconds column on the subathon table) and uses it on resume.
• Fixed subathon overlay drifting and only displaying whole minutes
  • The overlay was ticking with setInterval(60000) and decrementing a local minute counter, which drifts under browser/OBS browser-source throttling and only ever showed 0 second(s) regardless of true remaining time.
  • The bot now sends an absolute end_timestamp_ms (Unix milliseconds) in the SUBATHON_START, SUBATHON_RESUME, and SUBATHON_ADD_TIME websocket payloads, so the overlay can tick against a fixed target and display real seconds.

Technical Details

• subathon_countdown(): moved the break statement inside the end-time conditional, added an explicit early break for paused/missing subathon state, and reduced the poll interval from 60 seconds to 30 seconds so the auto-end announcement fires closer to the true end time. The auto-end path now also emits a SUBATHON_STOP websocket notice so overlays react.
• pause_subathon(): dropped the // 60 floor. Computes remaining_seconds directly from total_seconds(), stores it to the new remaining_seconds column, and includes it in the SUBATHON_PAUSE websocket payload alongside the legacy remaining_minutes field.
• resume_subathon(): reads remaining_seconds from the database when available, falls back to remaining_minutes * 60 for any row that paused before the column existed, and computes end_time = now + timedelta(seconds=stored_seconds). The SUBATHON_RESUME websocket payload now includes end_timestamp_ms.
• start_subathon() and addtime_subathon(): websocket payloads now include end_timestamp_ms (Unix milliseconds) so the overlay can tick against an absolute target.
• Schema migration: a new remaining_seconds INT NOT NULL DEFAULT 0 column was added to the subathon table via the existing column-diff migration logic in usr_database.php.

Thank you for your feedback and support!

As always, your feedback is appreciated. Please report any issues, bugs, or suggestions in the #ticket-info channel on our Discord server. You can also submit feedback and bug reports directly on our support website: https://support.botofthespecter.com/