Changelog - Version 5.7.18 (2026-08-20)

Version Information

• Updated version from 5.7.17 to 5.7.18
• Fix: lurk time commands now accept both DATETIME and string start_time values

Bug Fixes

• !lurking / !lurklead / timed !lurk failed when lurk_times.start_time was a DATETIME column
  • Some channel databases store start_time as DATETIME (the driver then returns a Python datetime). Others still have VARCHAR. The lurk commands always ran strptime() and expected a string, so DATETIME channels replied with “Oops, something went wrong while trying to check your lurk time.”
  • Fix: lurk commands parse start_time whether MySQL returns a datetime or a string. !lurklead skips a single unreadable row instead of failing the whole command. The per-user schema now creates and converts lurk_times.start_time to DATETIME.

Technical Details

• New helper parse_lurk_start_time() accepts datetime, date, 'YYYY-MM-DD HH:MM:SS', and ISO-8601 strings.
• Wired into lurk_command (timer refresh), lurking_command, lurklead_command, and unlurk_command.
• usr_database.php: lurk_times.start_time is DATETIME NOT NULL for new tables; existing VARCHAR columns are converted on dashboard load.

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/