Knowledge Base

/

Release Notes

Fix

v2.5.21 Release Notes

An emergency fix for ticket panels failing to deploy — `/ticket panel` failed every single time. We also fixed `/ticket create` showing an error immediately after reporting success, and settings in the ticket panel that didn't refresh until you pressed "Refresh".

BotShade Team
BotShade Team

|

3 min read

|

Published: August 2, 2026

BotShade has been updated to v2.5.21. This is an emergency fix for a bug in the ticket feature.

Deploying a panel with /ticket panel was failing every time. We’re sorry for the disruption this caused to everyone using tickets.

Table of contents:

Highlights

  • Fixed /ticket panel failing every time, making it impossible to deploy a ticket panel.
  • Fixed /ticket create showing an error immediately after reporting that the configuration was created. The configuration itself was created successfully, so it’s still there even if you saw the error.
  • Fixed the ticket settings panel where limit inputs and embed changes didn’t appear until you pressed “Refresh”.

Ticket panels can be deployed again

Running /ticket panel produced an error instead of deploying the panel. This happened unconditionally, every time — so if you were unable to deploy a ticket panel, please try /ticket panel again.

/ticket create was affected too: the ticket configuration was created correctly, but an error message appeared right after the success notice. That’s fixed as well.

Both came from an incorrect internal reference — an earlier refactor rewrote more than it should have. We’ve added an automated code check to prevent the same class of mistake from slipping in again.

Ticket settings panel improvements

In the ticket settings panel, changing a dropdown or an AI setting updates the panel in place. Limit inputs and embed changes, however, only returned a separate message — you had to press the “Refresh” button to see the new values.

As of v2.5.21, both of these update the panel in place like everything else. Embeds can’t be rendered inside the panel itself, so the preview still arrives as a separate message.

Compatibility

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

Nothing in v2.5.2 has changed.

Support and community

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

Thank you for using BotShade.