v2.5.6 Release Notes

BotShade has been updated to v2.5.6. In this release, we moved bot runtime servers to Tokyo. We also fixed a bug in the earthquake early warning feature we launched in v2.5.5, improved reliability around bot startup and restarts, and reworked how AI auto-response usage is tracked.

Table of contents:

• Highlights
• Moved bot runtime servers to Tokyo
• Fixed the earthquake early warning settings panel
• Fixed a timestamp issue in server protection logs
• Improved reliability of bot startup and restarts
• Reworked AI auto-response usage tracking
• Performance
• Compatibility
• Support and community

Highlights

• Moved bot runtime servers from a data center near Washington, D.C. to one in Shinagawa, Tokyo.
• Fixed the mention panel not opening in the earthquake early warning settings (/eew settings).
• Fixed a timestamp mismatch in server protection feature logs.
• Fixed several bugs around bot startup and restarts, improving reliability.
• The dashboard now shows more accurately whether a bot stopped because the owner stopped it or because the system did.
• Fixed an issue where a transient bug could cause AI auto-response usage records to not carry over correctly.
• Changed the reset timing for AI auto-response usage to align with your billing renewal date.
• Changed how custom command limits are counted, from saved items to enabled items.

Moved bot runtime servers to Tokyo

Bot runtime servers — where your bots actually run — used to be hosted in a data center near Washington, D.C. Starting with v2.5.6, they’re hosted in a data center in Shinagawa, Tokyo.

• Since most usage comes from within Japan, this shortens the round trip between Discord and the runtime server, so commands and other responses should feel snappier.
• No configuration changes or migration are needed on your end. Your existing bots, commands, and custom settings continue to work as-is.
• Bots restarted briefly during the migration window.

Fixed the earthquake early warning settings panel

The mention panel in /eew settings — part of the earthquake early warning feature we launched in v2.5.5 — wouldn’t open. This was caught shortly after launch and is now fixed. Existing settings are unaffected.

Fixed a timestamp issue in server protection logs

Some timestamps shown in server protection logs (member join/leave records, etc.) weren’t timezone-aware and could be off from the actual time. This is now fixed.

Improved reliability of bot startup and restarts

We found and fixed several bugs affecting bot startup, shutdown, and restarts.

• Fixed cases where a bot could fail to start, or fail to start again after a restart, under certain conditions.
• Fixed a race where a bot’s place in the startup queue could be taken during periods of high load.
• Reworked the internal logic around bot stop/resume, reducing unintended stops.

The dashboard also now more accurately reflects why a bot stopped — whether the owner stopped it, or the system did.

Reworked AI auto-response usage tracking

Made usage tracking more resilient to transient issues

A transient system issue could occasionally cause AI auto-response usage records to not carry over correctly. We’ve reworked how usage is recorded so it recovers correctly even when this happens.

Aligned the reset date with your billing renewal date

AI auto-response usage previously reset on the calendar month (the 1st). Starting with v2.5.6, it resets on a one-month cycle starting from your billing renewal date. You can check your next reset date from /ai usage on the dashboard.

Changed how limits on custom commands are counted

Limits on custom commands, custom command groups, and custom events used to be counted by how many you had saved. Starting with v2.5.6, they’re counted by how many are enabled. Items you’ve disabled no longer count toward the limit.

Performance

• Database connection attempts that fail during the connection stage are now retried automatically, making bots less likely to become unstable during brief database hiccups.

Compatibility

Your existing bots and command definitions continue to work in v2.5.6.

• Bot runtime servers are now hosted in a data center in Shinagawa, Tokyo. No action is needed on your end.
• AI auto-response usage now resets on your billing renewal date. Check /ai usage for your next reset date.
• Custom command limits are now counted by how many are enabled. If you have many saved but disabled items, the number you can newly enable may change.

Support and community

For questions, bug reports, or feature requests, please reach us at any of the following:

• Support page — contact form
• status.botshade.com — service status

Thank you for using BotShade.