v2.5.4 Release Notes

BotShade has been updated to v2.5.4. This release has two centres of gravity.

The first is a complete rebuild of the settings panels you see on Discord. Every feature that has a settings panel now uses the same cards, the same colour coding, and the same button positions.

The second is fixing “I saved it and nothing happened”. Across several features, changing a setting redrew the panel with the value from before the change, making it look as though the button hadn’t worked. It wasn’t only a display problem — in some places edits were lost outright. We’re sorry for the trouble this caused.

Table of contents:

• Highlights
• Every settings panel has been rebuilt
• Saved changes now show up immediately
• Minigame fixes
• Turning the economy off now turns it off
• Dashboard improvements
• Reliability
• Compatibility
• Support and community

Highlights

• Every settings panel has been rebuilt. Settings are separated into cards, a card’s colour tells you whether that feature is on, and Reload / Back / Close always sit at the very bottom.
• Paged lists now have ⏮ / ⏭ and a jump-to-page control.
• Fixed panels showing the value from before your change across many features — including cases that lost embed edits or rolled a published role panel back to older content.
• Fixed minigame odds and payouts that didn’t match what actually happens, along with a problem where button presses could settle a game in an unintended way.
• Fixed the economy toggle leaving all of its commands running when set to off.
• The builder’s log panel has been rebuilt: it now filters to the command or event you’re editing, and groups each run into a single card.
• Bots being updated on our side now show a dedicated “updating” state.

Every settings panel has been rebuilt

The panels you open with /protection settings, /ticket settings and the rest were each built separately, which meant the same Back button sat in a different place depending on the feature. It was also hard to tell where one setting ended and the next began.

In v2.5.4 they are all assembled the same way.

• Settings are separated into cards. Different subjects get different cards, and anything you can’t undo (deletions and the like) gets a red one.
• A card’s colour shows its state. Green when the feature is on, grey when it’s off — so you can read the state of every feature at a glance.
• Reload, Back and Close always sit at the very bottom. These act on the message as a whole, so they’ve been lifted out of the cards they used to be buried in.
• Long lists get filter tabs. Giveaway management and the reminder list now show “Running / Ended / All” style switches along the top.
• Paging is much better. Where you previously had only Previous and Next, there are now ⏮ / ⏭ buttons, and pressing the page number in the middle lets you jump straight to a page. This applies to the Fortnite shop and cosmetics search, the auto-responder rule list, and the reminder list.

The features covered are verification, server protection, tickets, welcome messages, join/leave logs, sticky messages, levelling, role retention, auto-responder, AI auto-reply, AI usage, role panels, boards, embeds, polls, backups, giveaways, reminders and the Fortnite integration.

Nothing about your settings changes. Everything you’ve saved is carried over and works the same way. Only the layout and button positions are different.

Doing this also meant pulling the panel layout itself out into a reusable component. If you’re curious about how that went — and where that component has since ended up — we’ve written it up in Rebuilding our settings panels.

Saved changes now show up immediately

When a panel redrew itself right after you changed a setting, it could come back showing the value from before the change. The change had been saved, but the screen didn’t move — so it looked like the button hadn’t worked. Pressing Reload a little later would show it correctly, which made the whole thing hard to pin down.

A panel that snaps back is annoying but survivable. In a few places, though, it actually cost you something.

• Embed edits could be lost. Change the title, then change the description, and the title change disappeared. The editor reloads the current content every time it saves, so if that reload returned stale content, it got written back over your change. This affected the welcome message, join/leave log, sticky message and embed editors.
• “Publish to panel” on a role panel could roll the published message back, dropping roles you had just added. /rolepanel send could place a panel missing those roles for the same reason.
• Editing an auto-responder rule could leave the bot replying with the old rule. Not just the panel display — the actual matching ran on the pre-change version.
• Lifting a protection lockdown could leave some channels locked.
• Sticky messages could end up posted twice.
• Settings saved in the dashboard might not reach the bot until the next reload. The same applied to custom commands, custom events and the variable list.

In v2.5.4, any read that happens right after a write is guaranteed to see the newest content. This covers welcome messages, role panels, tickets, reminders, the auto-responder, server protection, giveaways, backups, the gaming integration, role retention, polls, sticky messages, levelling, the embed editor, and everything saved from the dashboard.

Opening a panel for the first time works exactly as before, so nothing gets slower.

Minigame fixes

Several minigames displayed something other than what they actually did.

• Hi-Lo’s odds display didn’t reflect reality. It showed figures like “High 84.6% / Low 23.1%”, adding up to more than 100% and looking like an arithmetic error. The overlap came from how ties are counted on both sides. v2.5.4 now states the winning range explicitly — “3 or higher” / “3 or lower” — with the payout and a note alongside. For A and K, where a tie loses, it reads “higher than A” / “lower than K”.
• Blackjack’s natural blackjack payout setting was never used. It was configurable and documented, but a natural 21 paid out at the ordinary win rate. It now pays what you’ve configured.
• Ultimate Luck’s confirmation screen showed stale odds and multipliers even after you changed them. It now shows your actual settings.
• The Nibuichi command description didn’t match its payout. The description said “2× or nothing”, while the default is actually 1.9×. The board now shows the real multiplier and win rate.
• Slot and Mines multipliers could render as x2.5000000000000004.

We also fixed a problem where pressing buttons could settle a game in an unintended way, in Hi-Lo, Blackjack, Ultimate Luck, Slot, Nibuichi and the all-in confirmation. A related case where your bet was taken but no result appeared has been fixed too.

Finally, Mines could take your bet and lose it when the balance system was momentarily unavailable; it now checks first.

Turning the economy off now turns it off

Setting the economy feature to off left all eleven of its commands running. The toggle existed in the settings, but there was no working way to actually stop the feature.

In v2.5.4, balance, work, deposit, withdraw, send, daily, ranking, status, borrow, repay and bankruptcy all respect the setting. The “work again” button left over in older messages stops responding too.

Dashboard improvements

The builder’s log panel has been rebuilt

The log panel in the command and event builder showed every log from the whole bot, which made it hard to tell whether the thing you were editing had run at all.

• It now filters to the command or event you’re editing by default, so your logs aren’t buried under everything else.
• Each run is grouped into a single card, with the outcome, duration and step count in the header. Failed runs open expanded.
• Logs stream in live while the panel is open, and stop when you close it.
• Failures are marked on the canvas. The block that failed gets a badge; press it to filter the log to that block. You can also jump from a log line to the block it came from.
• The reason for a failure, and a hint for fixing it, are readable inline without opening another screen.
• Even with the panel closed, the log icon carries a badge with the failure count.

An “updating” state for bots

While we’re updating a bot on our side, it used to show up as “failed” or “starting”, neither of which was true. v2.5.4 adds a dedicated state and an explanatory banner, and returns to the normal display automatically once the update finishes.

Start, stop and restart are unavailable during an update, because they wouldn’t be carried out. The wording when an update takes a while now says we haven’t confirmed completion yet, rather than reporting a failure.

You can now confirm a save took effect from the logs

There’s now a log entry for the moment a change you saved in the dashboard is actually applied by the bot. Previously, a successful apply logged nothing at all, which left us with no way to answer “I saved it, has it applied?” A failure to apply is logged too.

Reliability

• Some bots could fail to start. An internal connection could drop without being noticed, and work would continue against it — this showed up around maintenance windows. Affected bots all recovered automatically, but they didn’t start on that pass. Connections are now checked, and failed attempts retried.
• The same cause could let Blackhole let a message through without evaluating it. Blackhole shipped in v2.5.3, and this failure was silent, which made it hard to spot. It’s fixed.
• Deleting a bot now deletes its data more reliably. v2.5.3 introduced deleting a bot’s data along with the bot; that guarantee is now enforced in a way that can’t be missed.

The first two of these were already deployed shortly after v2.5.3 went out. They weren’t covered in a release note at the time, so we’re reporting them here.

Compatibility

Bots and command definitions you already use keep working in v2.5.4. No migration is required.

• Panel layouts and button positions change. Back, Reload and Close have moved to the bottom of the message. The settings themselves — options, values, permissions — are untouched.
• Minigame multiplier and odds displays change. These were corrected to match your actual configuration; the underlying probabilities and payouts have not been altered. One exception: Blackjack’s natural blackjack payout was previously ignored, so if you had configured it, it now takes effect.
• If you have the economy feature set to off, its commands will actually stop now. Since the toggle wasn’t working before, this may stop something you’re still using. Please check the setting if so.

Support and community

Questions, bug reports and feature requests are always welcome:

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

Thank you for using BotShade.