v2.5.31 Release Notes

BotShade has been updated to v2.5.31. This is an emergency fix for a bug in the dashboard.

If you hadn’t yet accepted the new Terms of Service, opening the dashboard sent it into an endless reload loop — you could reach neither the consent screen nor your bots. If you were affected, the dashboard was completely unusable for you, and we’re sorry for the disruption.

Your bots themselves were not affected. They kept running on Discord as usual throughout.

Table of contents:

• Highlights
• The dashboard no longer reloads in a loop
• The bug now leaves a usable record
• Compatibility
• Support and community

Highlights

• Fixed the dashboard reloading in a loop and becoming unusable when opened before the new Terms of Service had been accepted.
• The consent screen now appears as intended, and accepting it takes you straight into the dashboard.
• Fixed the reporting problem that left this bug logged as an error with no identifiable cause, so we can catch bugs like it sooner.

The dashboard no longer reloads in a loop

When we revise the Terms of Service, BotShade shows a consent screen over the dashboard and asks you to accept before continuing.

That mechanism reloaded the page once when the server reported that consent was required, so it could read a clean state. The problem: the reload cut off the request needed to render the consent screen. The screen never appeared, the server reported “consent required” again, and the cycle repeated.

There was a guard meant to limit this to a single reload — but the guard itself was wiped by every reload, so it never actually held.

In v2.5.31, the guard is stored in the browser tab and survives across reloads. The loop can no longer occur, and the consent screen reliably appears. The guard is cleared once you accept, so the same mechanism works correctly for future revisions of the Terms.

The fix is already live. If you still have a tab stuck in the loop, please close and reopen it, or reload the page.

The bug now leaves a usable record

For as long as this bug was occurring, it reached our logs only as an error with no identifiable cause or location. We were recording the error converted to plain text, which discarded exactly the information that would have told us where and what went wrong.

v2.5.31 preserves that information. We also stopped reporting the network requests that get cut off while the dashboard is deliberately reloading itself — those aren’t failures, and logging them buried the real bug under the noise it generated.

Compatibility

Bots and command definitions you already use continue to work in v2.5.31. No migration or reconfiguration is needed on your side.

Nothing in v2.5.3 has changed.

Support and community

For questions, bug reports, or feature requests, please reach out through any of the following:

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

Thank you for using BotShade.