Changelog - Version 5.7.13 (2026-06-26)

Version Information

• Updated version from 5.7.12 to 5.7.13
• Fix: the !checktimer command now works again instead of always erroring out

Bug Fixes

• Fixed !checktimer always failing with a datetime error
  • When a viewer ran !checktimer to see how long was left on their !timer, the command always failed and replied “An unexpected error occurred. Please try again later.” instead of reporting the time remaining. The same broken comparison existed in the beta and v6 bots and was fixed there too.
  • Root cause: when a timer is started, its end time is saved to the database as a timezone-aware UTC value. MySQL DATETIME columns don’t store timezone information, so when !checktimer read the end time back it came back timezone-naive. Subtracting the current timezone-aware UTC time from that naive value raised can't subtract offset-naive and offset-aware datetimes, which aborted the command every time it was used.
  • Fix: the end time read back from the database is now re-stamped as UTC (the timezone it was originally saved in) before the remaining-time calculation, so both sides of the subtraction are timezone-aware. !checktimer once again correctly reports the minutes and seconds left on an active timer.

Technical Details

• In the checktimer command, the end_time read from active_timers.end_time is coerced to UTC when it has no tzinfo (end_time = end_time.replace(tzinfo=timezone.utc)) before computing remaining_time = end_time - time_right_now(timezone.utc). The same one-line guard was applied to beta.py and beta-v6.py.

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/