Vikings Hall โ v1.15.25
Changelog, rendered from CHANGELOG.md. The version above always comes from package.json; every entry below comes from the changelog file. New to the bot? Start with the wiki.
v1.15.25 โ 2026-11-15 ยท current version
Fixed
- FAQ/autoresponder double replies (1.15.25). Root cause: three separate `MessageCreate` listeners can all reply to one message โ `src/events/customCommands.js`, `src/events/faqResponder.js`, and `src/events/messageCreate.js` (which calls `src/utils/autoresponders.js` `handleMessage`). Each one checked the shared `isHandled(message.id)` marker BEFORE its async database lookup and only marked the message handled AFTER a match. Discord.js invokes all three listeners on the same event and each runs synchronously only until its first `await`, so all three passed the `isHandled` check before any of them had marked the message โ a message matching two systems (e.g. an FAQ entry AND an autoresponder trigger, or a custom command AND an FAQ) got TWO replies. The marker as written only worked inside a single sequential chain, not across concurrent listeners. The event loader registers each file once, so this was not a double-registration bug. Fix: new atomic `tryClaim(messageId)` in `src/utils/messageHandled.js` โ the check and the add are adjacent synchronous statements with no await between them, so the claim is atomic on Node's single thread (returns false if already claimed, true if this caller won). Each handler now claims synchronously immediately before its reply, after the match is found: `faqResponder.js` and `customCommands.js` (`if (!tryClaim(message.id)) return;`), `autoresponders.js` `handleMessage` (`if (!tryClaim(message.id)) return false;`). The early `isHandled` fast-path checks are kept. Also fixed the second double-reply path in `messageCreate.js`: the AI-chat block replied in the AI channel with NO handled check, so a message in the AI channel that also matched an autoresponder/FAQ/custom command got the auto-reply AND an AI answer โ the AI reply is now skipped when `isHandled(message.id)` is true at that point (checked right before the AI call, after the autoresponder has run). No change to what any system matches, reply content, XP, automod, sticky, or translate behavior; the event loader was not restructured and the listeners were not merged. Verified by `tmp/verify-1.15.25.js` (30/30: the OLD check-then-mark logic reproduced the bug against the same mocks โ 3 replies for a message matching all three systems, 2 for FAQ + autoresponder โ while the fixed handlers give exactly one reply in every matching combination (FAQ + autoresponder, custom + FAQ, all three, custom + autoresponder, FAQ only, autoresponder only), zero when nothing matches, and the AI-channel cases (auto-reply with no AI call when an autoresponder matches, AI answer once when nothing matches); plus source checks that the claim sits immediately before each reply and the AI guard is in place) and `check-deploy.js` (38 top-level, 0 problems). Note: a second bot process running the same token would ALSO double every auto-reply โ this code fix does not cover that case; if doubles persist after this lands, check `ps aux | grep node` for a stale bot process. Server needs `git pull` + bot restart only โ no `npm run deploy`, no `npm install`, no dashboard restart.
v1.15.24 โ 2026-11-15
Added
- Dashboard Streams live-announcement preview (1.15.24). Each streamer row now has a Preview button that shows exactly what Discord will display when that streamer goes live โ the message content line plus the embed (platform color bar, title, description, inline Category/Viewers fields, thumbnail image, latest clip/video field, timestamp) rendered Discord-style in a panel under the streamers list, with a "Preview โ nothing was sent to Discord" note and a Close button. Preview only: it never posts to Discord, sends any announcement, or touches the notify channel. The preview goes through the exact same code path as the real announcement: the embed is built by the shared `liveEmbed` in `src/utils/streamNotifier.js`, and the clip field now comes from a new shared `addClipField(embed, clip)` helper used by both the live notifier (`checkAllStreams`) and the preview route, so the preview cannot drift from the real message. New route `GET /api/guilds/:id/streamers/:streamerId/preview` (requireAuth + requireGuildAccess, row scoped by id + guild_id, 404 when not found, 503 when the DB is down) returns the embed JSON plus the content line with the ping role rendered as its name (e.g. `@Raven's Herald`), built from clearly-marked sample data (title "Test stream โ preview only", game "Just Chatting", 123 viewers, sample clip) and the row's real platform + streamer name. The clip field appears only where the real notifier would ever add one โ Twitch (latest clip) and YouTube (latest video) with clips enabled; Kick/Facebook/TikTok never get one, and the preview is honest about that. The sample thumbnail is a small SVG served by the dashboard itself (`/img/stream-preview-thumbnail.svg`) โ a `data:` URI is not an option because discord.js only accepts http(s)/attachment image URLs, and `trust proxy` is already on so the URL's protocol is right behind nginx/Cloudflare. Verified by `tmp/verify-1.15.24.js` (40/40: preview route 200 with the exact content/embed for Twitch/YouTube/Kick rows, 404 for an unknown id and another guild's row, 503 with the DB down; the route's embed JSON is byte-identical to a direct `liveEmbed` + `addClipField` build with the same inputs; the handler source contains no send/checker/fetch call and the sample data is clearly fake; Streams table renders with its 1.15.23 classes, a Preview button per row, and the panel container; add/edit/delete/refresh/clip controls and the Staff Errors page verified unchanged) and a live dashboard boot in wizard mode (GET / โ 302, GET /style.css โ 200 serving the new preview rules, GET /app.js and /js/settings.js โ 200, GET /img/stream-preview-thumbnail.svg โ 200); `check-deploy.js` reports 38 top-level, 0 problems. No live MySQL was reachable in the sandbox, so the preview was verified against a mocked db layer, not a real database. Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.23 โ 2026-11-15
Fixed
- Dashboard streamer delete silently did nothing + Streams table layout (1.15.23). The DELETE `/api/guilds/:id/streamers/:streamerId` route already existed (since the initial commit) and the Remove button already called it โ the break was elsewhere: `requireAuth` answered every signed-out request with a redirect to `/login`, and `fetch` follows that redirect as a GET, so a delete from an expired session got a 200 HTML login page back, `AceBot.del()` read it as success, the row vanished from the page with a "Streamer removed" toast, and the streamer came back on refresh. Fix: `requireAuth` now returns 401 JSON (`Not signed in โ log in again.`) for `/api/*` requests while page routes keep the redirect to `/login`; the shared `AceBot` fetch helpers (`postJSON`/`getJSON`/`del`) now refuse any non-JSON 200 via a new `assertJson` guard, so an HTML page can never again read as a successful API call; and the streamers DELETE route is now honest about its result โ 503 when the query itself fails, 404 `Streamer not found.` when nothing matched, 200 `{ok:true}` only when a row was actually deleted (still scoped by both id and guild_id). The delete handler also removes the row's hidden edit `<tr>`, which previously lingered in the DOM. Streams table gets the same treatment the Staff Errors table got in 1.15.14 (CSS/markup only): `table-layout: fixed` with a `<colgroup>` (live 26px, streamer 19%, platform 88px, announcements 14%, ping role 10%, live channel 10%, clips 52px, actions 190px) inside the shared `.table-scroll` wrapper so the table can never push the page wider; platform is now a badge (Twitch purple, YouTube red, Kick green, Facebook blue, TikTok cyan); streamer/announcement/ping-role/live-channel cells ellipsize with the full text in a `title` tooltip; rows are compact (6px padding, middle-aligned); the edit-row `colspan` is corrected 7 โ 8. Verified by `tmp/verify-1.15.23.js` (43/43: DELETE handler exercised with a mocked db โ matching row deletes with both id+guild params, missing row 404s, failed query 503s; requireAuth 401-JSON for /api/*, redirect kept for pages, next() when signed in; assertJson guard in all three fetch helpers; Streams table renders with the new classes/badges/tooltips and the add/edit/refresh/clip controls intact; Staff Errors table and its CSS verified unchanged) and a live dashboard boot in wizard mode (GET / โ 302, GET /style.css โ 200 serving the new rules, GET /app.js and /js/settings.js โ 200); `check-deploy.js` reports 38 top-level, 0 problems. No live MySQL was reachable in the sandbox, so the delete was verified against a mocked db layer, not a real database. Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.22 โ 2026-11-15
Added
- Voice debug logging + connection error guard (1.15.22). Live diagnosis: `/music join` fails deterministically with the same pattern on every attempt, across two voice regions (US East โ US Central), after killing duplicate bot processes, after forcing IPv4-first DNS, with outbound UDP proven working and GuildVoiceStates present. The 1.15.20 logs show signalling -> connecting -> connecting -> signalling (~30ms) -> 10s timeout stuck in signalling -> destroyed. Read against the installed `@discordjs/voice` source, the connecting->connecting transition is the networking advancing to Identifying (WS opened, identify sent) and the connecting->signalling 31ms later is `onNetworkingClose` with a non-4014 code โ so the voice WebSocket OPENS, sends IDENTIFY, and dies ~30ms later, before any READY. What was still invisible: whether the server sent HELLO back (identify accepted) or nothing (identify rejected / network kill), and whether a networking error fired. Fix (musicQueue.js `createQueue` only, diagnostics only, no behavior change): `joinVoiceChannel` is now called with `debug: true`, and a `connection.on('debug')` handler logs each debug line at warn level to the error logs โ incoming packets (`<< {...}`: HELLO op 8, READY op 2) and networking state changes. Outgoing packets (`>>`) are dropped outright: the identify carries the voice session token. Incoming packets carry no token (verified against the installed lib source: HELLO/READY contain heartbeat interval, ssrc, ip, port and modes only), and every line still passes through the 1.15.19 scrubText() inside errorLogger.log(); each line is capped at 500 chars so the logs don't balloon. Also a `connection.on('error')` handler: the connection re-emits networking errors as 'error', and an EventEmitter 'error' with no listener throws โ currently nothing listened for it. The handler logs the error at error level with its `code` in the message (ECONNRESET/EPIPE/ETIMEDOUT), so a network RST is distinguishable from a clean server close (a clean close emits no error event at all). Same 10s timeout, same user-facing messages, same queue/destroy logic, same 1.15.20 stateChange logging. Verified by `tmp/verify-1.15.22.js` (16/16 mock cases: HELLO + READY debug lines logged at warn with packet content; ECONNRESET error logged at error with the code in the message and the stack attached; clean close logs no error entry, only the warn transition; long debug lines capped at prefix + 500 chars; outgoing identify line dropped and no logged entry contains the fake token or mentions a token at all; join success path unchanged and joinVoiceChannel called with debug:true) and `check-deploy.js` (38 top-level, 269 flat, 0 problems). How to read the next attempt's logs: HELLO present in the debug lines = identify accepted (close came later, likely network/UDP stage); no HELLO + no error event = identify rejected by the voice server (4004/4006, session/token problem); an error event with ECONNRESET/EPIPE = the network/middlebox killed the connection. Server needs `git pull` + bot restart only โ no `npm run deploy`, no `npm install`, no dashboard restart.
v1.15.21 โ 2026-11-15
Fixed
- Force IPv4-first DNS for the bot process (1.15.21). Live diagnosis: Ace's server has broken IPv6 DNS โ `curl -6 https://discord.com` fails with exit 6 (could not resolve host) while `curl -4` returns HTTP/2 200 โ and `/music join` fails deterministically: the voice connection reaches Connecting, the voice WebSocket opens then closes ~30ms later (connecting -> signalling), it sits in Signalling for the 10s timeout and is destroyed, identical across attempts including after killing two duplicate bot processes. Node's default DNS order is `verbatim` (OS order), so a Discord voice endpoint that resolves IPv6-first can hand the voice WebSocket an unreachable IPv6 address and die exactly like this, while the main gateway (which resolves IPv4-first) works fine. Fix (index.js only, first statement before any other require): `require('node:dns').setDefaultResultOrder('ipv4first')` with a comment explaining why. `src/shardManager.js` spawns repo-root `index.js` as the shard file, so the setting covers the sharded bot process; the dashboard is untouched (bot-only change). No new dependency, no other behavior change. Verified by `tmp/verify-1.15.21.js` (5/5: call present in index.js before the first discord.js require; fresh process reports default order `ipv4first` after the exact line from the file; `localhost` lookup returns IPv4 first) and `check-deploy.js` (38 top-level, 0 problems). Honest caveat: broken IPv6 DNS is proven; that it is the voice cause is not yet proven โ the retry after this lands is the test. If voice still fails, the next step is the voice-region change. Server needs `git pull` + bot restart only โ no `npm run deploy`, no `npm install`, no dashboard restart.
v1.15.20 โ 2026-11-15
Added
- Voice-connection state diagnostics (1.15.20). Live report from Ace: `/music join` on 1.15.18 showed the bot in the voice channel for exactly ~10 seconds, then it left with the "Could not join" error and nothing in the console. 10s is exactly the `entersState(Ready, 10_000)` timeout โ the gateway join works but the connection never reaches Ready, so the UDP handshake with Discord's voice servers never completes (likely environmental, e.g. outbound UDP blocked) โ but the code logged nothing about where it stalled. Fix (musicQueue.js only, diagnostics only, no behavior change): `createQueue` now attaches a `connection.on('stateChange')` handler that logs every transition at warn level to the error logs (`Voice signalling -> connecting in #<channelId>`, etc., with guildId + commandName 'play'), including the disconnect reason name and close code on Disconnected (`reason=WebSocketClose, closeCode=4014`; reasons per @discordjs/voice: 0 WebSocketClose, 1 AdapterUnavailable, 2 EndpointRemoved, 3 Manual); the 10s timeout now logs `Voice join timed out after 10s โ stuck in <status>` with the final connection status; and the existing "Voice connection not ready" log in `playNext` also names the stuck status. Status + reason codes only โ `joinConfig.token` and the voice server endpoint token are never logged (the 1.15.19 scrubber is a backstop, not a reason to log secrets). Same 10s timeout, same user-facing messages, same queue/destroy logic. Verified by `tmp/verify-1.15.20.js` (18/18 mock cases: successful join logs signalling -> connecting -> ready at warn with no error; stuck-in-Connecting timeout logs the stuck status; Disconnected logs WebSocketClose + close code, Manual/EndpointRemoved/AdapterUnavailable reason names with no close code when absent; no logged entry contains the fake joinConfig token or mentions a token at all; playNext not-ready branch names the stuck status; successful play still posts Now playing once) and `check-deploy.js` (38 top-level, 269 flat, 0 problems). After this lands, the next `/music join` attempt records the exact stall point in /staff/errors: stuck in Connecting = UDP/firewall; instant Disconnected with a close code = gateway/permission. Server needs `git pull` + bot restart only โ no `npm run deploy`, no `npm install`, no dashboard restart.
v1.15.19 โ 2026-11-15
Fixed
- Error-log secret scrubbing (1.15.19). `redact()` only applied to the `context` field โ `message` and `stack` were stored raw in the MySQL `error_logs` table and `logs/bot-errors.log`, so a secret embedded in an error message or stack trace (a URL carrying `?token=...`, an Authorization header in an HTTP error, a pasted token) would have landed in plain text. Nothing in the current call sites logs a secret today, so this closes the hole before it bites rather than cleaning up a leak. Fix (errorLogger.js only): `log()` now runs `message` and `stack` through a new `scrubText()` before the length caps โ first every configured secret VALUE (bot token, Discord client secret, dashboard session secret, MySQL password, Twitch client secret, YouTube/Steam/OpenAI API keys, read lazily from config and used only as match strings, never logged; values under 8 chars are skipped), then tight shape patterns (Discord bot-token shape, `Authorization: Bearer/Basic` headers, `sk-`/`sk-proj-` keys, and `key=value` / `key: value` pairs including JSON and `%3D`-encoded params). Normal log content is untouched: YouTube URLs, Discord snowflake IDs, usernames/tags, channel names, and prose like "invalid token type" survive unchanged. The existing `context` redaction works as before, and the retry queue, file fallback, and purge behavior are untouched. Verified by `tmp/verify-1.15.19.js` (32/32: all eight configured fake values scrubbed from message/stack including raw pastes, Bearer/Basic/`?token=`/JSON/`%3D` cases, Discord-token and `sk-proj-` shapes, normal-content survival, context redaction intact, 4000/8000 caps intact, file line matches the returned entry), and `check-deploy.js` (38 top-level, 0 problems). This only affects NEW log entries โ rows already in `error_logs` / `bot-errors.log` are NOT retroactively scrubbed; dashboard purge-all clears them. Server needs `git pull` + bot restart only โ no `npm run deploy`, no `npm install`, no dashboard restart.
v1.15.18 โ 2026-11-15
Fixed
- Music voice-join failure (1.15.18). `/music play <URL>` replied "Now playing" twice but the bot never joined the voice channel, so nothing was audible. Root cause: `createQueue()` called `joinVoiceChannel()` and never awaited `entersState(connection, VoiceConnectionStatus.Ready)` or checked Connect/Speak permissions, and `playNext()` only awaited the audio PLAYER reaching Playing โ which it can do on a dead connection โ before posting "Now playing" and counting the song. Fix (musicQueue.js): Connect + Speak are checked before joining (missing either returns a clear permission error, no queue created); the join awaits Ready with a 10s timeout and fails cleanly otherwise; `playNext()` gates the "Now playing" announcement and the songs-played count on the connection being Ready both before streaming and after the player starts; a join failure clears the phantom playing entry, posts a plain "Could not join the voice channel" error, and destroys the dead queue instead of trying the next track; and a mid-play disconnect now posts a "Left voice" message to the text channel instead of silently destroying the queue (silent when idle). `addTrack()` awaits the start, so a failed join is reported to the caller instead of a phantom "Now playing" โ only a voice failure flips the result; a normal stream failure still returns added (the track was queued, it just couldn't play). The fix also covers the race where the connection drops mid-resolution and the Disconnected handler destroys the queue under `addTrack` (the queue-gone check returns the join error instead of crashing on a lost queue).
Added
- New `/music join` subcommand (1.15.18). Joins the invoker's voice channel without playing anything, so a later `/music play` has somewhere to play. Reuses the same fixed join path (Connect + Speak check, await Ready, clear error on failure); replies "Joined #channel" only after Ready. If the bot is already in that channel it says so (no duplicate connection); if it is connected elsewhere it moves (same connection object reused, player stays subscribed). Same DJ rule as `/play` (open to everyone while djOnlySkip is on, the default). Counts: 269 commands, 38 top-level; `check-deploy.js` hardcoded expectations updated 266โ267 chat children / 268โ269 flat, and `tmp/verify-help.js` + help.js comments updated 268โ269 (the help count itself is computed, not hardcoded). Verified by `tmp/verify-1.15.17.js` (36/36 mock cases: missing Connect/Speak, join timeout, dead connection, drop mid-resolution, successful play, stream-failure-not-join-failure, mid-play + idle disconnects, join success/perms/already/move/timeout, command file loads), `tmp/verify-help.js` (ALL HELP CHECKS PASSED โ Music group now 21 lines across 3 pages), and `check-deploy.js` (38 top-level, 0 problems). A live Discord voice join cannot be tested from this sandbox, so the join paths are mock-verified, not live-verified. Server needs `git pull` + `npm run deploy` + bot restart โ no `npm install`, no DB work, no dashboard restart.
v1.15.17 โ 2026-11-15
Changed
- Header profile picture + Add to Server button (1.15.17). The top-right header now shows the signed-in user's real Discord profile picture (`https://cdn.discordapp.com/avatars/{user_id}/{avatar}.png?size=64`, built from the avatar hash already stored in the session at login โ no session/auth changes) in a 28px circle with the same blurple ring as the sidebar server icon; users without a custom avatar get a blurple initial-letter circle instead, and a broken image swaps to the initial-letter fallback via `onerror` so a broken-image icon never shows. The "Add to Server" button is now compact (new `.btn-sm`: 5px 10px, 13px) and sits beside the "Vikings Hall Dashboard" brand at the top left instead of in the right-hand nav. Scope is the shared header partial only, so all pages pick it up โ no route, auth, or bot changes. Verified by `tmp/verify-header-avatar.js` (27/27: CDN URL + onerror fallback, no-avatar initial fallback, logged-out state, button placement/size, CSS rules + balance, full home-page render, dashboard boot in wizard mode with GET / โ 302 and GET /style.css โ 200 serving the new rules) and `check-deploy.js` (38 top-level; the 2 reported count problems are the music agent's uncommitted `/music join` command โ 269/267 vs the hardcoded 268/266 โ not this change; no bot code was touched here). Code-verified, not screenshot-verified โ no headless browser was available in the sandbox. Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.16 โ 2026-11-15
Changed
- Dashboard visual polish pass (1.15.16). Whole-dashboard CSS refresh, same dark + blurple identity, no new dependencies/images/fonts and no behavior or route changes (pure CSS plus minimal class hooks in the views). Cards & panels: subtler layered shadows with a faint top highlight, new `.card-block` utility for stacked content cards (changelog entries, wiki sections, confession/reaction-role cards) replacing repeated inline styles, first-heading margin reset inside cards. Buttons: keyboard `:focus-visible` rings, a press-down `:active` state, and matching hover glows for green/danger (the 1.15.12/1.15.14 disabled styling is untouched). Inputs: the form selector now covers `password`/`search`/`email`/`url`/`date`/`time` too โ the setup wizard's password fields and the wiki search box were unstyled before this pass โ plus placeholder color, disabled-input styling, blurple `accent-color` checkboxes, and a custom chevron on selects. Sidebar & header: active nav item gets a blurple left indicator, server icon gets a soft ring, header gets a subtle shadow and pill hover states on its links. Typography: section headings inside settings content get dividers (`h2` with a bottom border), tighter `h1` size on settings pages, list spacing, `strong` pops in muted text, and a blurple text-selection color. Tables (all pages): row hover highlight, compact 9px cell padding (errors table keeps its own tighter 1.15.14 padding). Micro-polish: thin dark scrollbars, toast shadow plus `.toast.warn`/`.toast.error` variants (setup page toasts now use classes instead of inline styles), toggle focus rings, and `.badge.ok`/`.badge.muted` variants; error-detail stack traces move from inline styles to a shared `.code-block` class. Stylesheet grew from ~7.5 KB to ~12.5 KB and stays dependency-free. Verified by `tmp/verify-dashboard-polish.js` (46/46: CSS balance/parse check, all new rules present, full EJS renders of home/staff/setup/version/docs plus a settings compile + general-module render, dashboard boot in wizard mode with GET / โ 302 and GET /style.css โ 200 serving the new rules) and `check-deploy.js` (38 top-level, 0 problems โ the extra parent is the 1.15.15 sticky command; no bot code was touched here). Code-verified, not screenshot-verified โ no headless browser was available in the sandbox. Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.15 โ 2026-11-15
Added
- Sticky messages (1.15.15). New `/sticky set <text> [channel]` and `/sticky remove [channel]` (Manage Messages only, new `sticky` parent โ 268 commands, 38 top-level). One sticky per channel: setting a new one replaces the old (its message is deleted), and the sticky is re-posted at the bottom whenever a new message pushes it up. The re-stick only fires when the sticky is actually not the channel's last message (one fetch per message, only in channels that have one); a manually deleted sticky is re-posted on the next message, and missing Send/Manage Messages permission fails silently with a warn log instead of spamming the channel. The sticky is plain text exactly as typed (2000-char limit enforced by the option); the set confirmation is deferred first, then the sticky is posted, then the reply is edited, so the confirmation sits above the sticky and the sticky ends up last โ no ephemeral flag (keeps the 1.15.7 keep-list intact). Storage is a new `sticky_messages` table (guild_id, channel_id, message_id, content, created_by, created_at; unique per channel) in `sql/schema.sql` plus the startup self-heal CREATE in `src/utils/database.js`, so existing installs get it on pull + restart with no manual SQL. One necessary deviation from the brief: /help's 25 groups are a static map capped by Discord's select-menu limit, so a brand-new parent is unreachable from /help unless it joins a group โ `sticky` joins the Moderation group (its blurb now reads "Bans, timeouts, warnings, sticky & automod"); `tmp/verify-help.js` ยง7 (every parent in exactly one group) validates this. Verified by `tmp/verify-sticky.js` (53/53: load counts, router permission denial, set/set-replace/remove flows, re-stick/not-last/already-last/manually-deleted/no-permission cases, thread + cross-channel guards, schema + self-heal presence, help listing) plus `check-deploy.js` (38 top-level, 0 problems), `tmp/verify-help.js` (ALL HELP CHECKS PASSED), and `tmp/verify-ephemeral-removal.js` (ALL PASSED โ also fixed two stale assertions in it: grouped-child count 261โ263, and the help collector check now accepts the unified `(i)` filter from 1.15.8). The set-replace test caught a real bug: the old message id was read from the row object after the upsert had mutated it, so the old sticky was never deleted โ the command now snapshots the old id before saving. Server needs `git pull` + `npm run deploy` + bot restart โ no `npm install`, no DB work, no dashboard restart.
v1.15.14 โ 2026-11-15
Fixed
- Staff Errors table layout on the dashboard (1.15.14). The `/staff/errors` table was unreadable at desktop widths: timestamps wrapped onto ~7 lines, messages were hard-cut at 120 chars mid-word, severity was plain grey text, the disabled "Purge selected" button looked identical to the active one, and the table forced a page-level horizontal scrollbar. Fix (CSS/markup only, no behavior change): the table now uses `table-layout: fixed` with a `<colgroup>` (checkbox 34px, ID 52px, Level 78px, Shard 52px, Command 15%, When 132px, Details 86px, Message takes the rest) inside an `overflow-x: auto` wrapper so the table can never push the page wider; timestamps render compact as `YYYY-MM-DD HH:MM` with the full timestamp in a `title` tooltip and never wrap; messages are no longer sliced in the template โ the full text is in the cell and ellipsizes with the full text in a `title` tooltip, with the resolved โ kept as a separate visible element; rows are compact (6px padding) with all cells middle-aligned; Level is now a badge (red for error, amber for warn, blurple for info, neutral grey fallback); `:disabled` buttons are visibly greyed out (45% opacity, `not-allowed` cursor, no hover lift); and the Shard filter field is narrowed to 110px to match the Level dropdown. Verified by `tmp/verify-1.15.14.js` (25/25: EJS renders with sample rows + empty state, all new classes/attributes present, purge hooks and Details links intact) and a live dashboard boot in wizard mode (GET / โ 302, GET /style.css โ 200 serving the new rules); `check-deploy.js` reports 37 top-level, 0 problems. No headless browser was available in the sandbox, so this is code-verified, not screenshot-verified โ column widths were checked arithmetically against the 758px content width (fixed columns 434px + Command 15% โ 114px, leaving ~210px for Message). Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.13 โ 2026-11-15
Fixed
- Music deploy crashed on Ace's server with `ERR_REQUIRE_ESM` (1.15.13). Root cause: 1.15.11 migrated YouTube extraction to `@distube/ytdl-core` v5, which is ESM-only, and `src/utils/youtube.js` used a static `require()` of it โ Node v20.5.1 (Ace's server) does not allow `require()` of ES modules, so `npm run deploy` (and `npm start`) died at load time. The 1.15.11 verification missed it because the sandbox runs Node 24, where `require(esm)` is enabled by default. Fix: `youtube.js` now loads ytdl-core lazily with a dynamic `import()` on first use and caches the client (a failed load clears the cache so a later call can retry). The file still loads synchronously at require-time โ no top-level await, no `require()` of the ESM package โ and the exported surface (`search`, `videoInfo`, `stream`) and behavior are unchanged. No new dependency; no Node upgrade needed. Verified by `tmp/verify-1.15.13.js` (ALL CHECKS PASSED under `node --no-experimental-require-module`, which restores Node-20 behavior: plain `require()` of youtube.js succeeds, Seven Nation Army + Get Lucky stream real audio through the lazy import) and `check-deploy.js` under the same flag (37 top-level, 0 problems). Server needs `git pull` + `npm run deploy` + bot restart โ no `npm install`, no DB work, no dashboard restart.
v1.15.12 โ 2026-11-15
Added
- Error-log purge on the dashboard (1.15.12). The staff Errors page (`/staff/errors`) now has per-row checkboxes with a select-all toggle, a "๐งน Purge selected" button, and a "๐๏ธ Purge all error logs" button โ both behind a `confirm()` step, staff-only (`requireStaff`). Purge selected deletes only the checked rows from the `error_logs` table and reports how many were deleted; the log file is untouched (it is append-only JSON lines with no per-row id to match against, so per-row file removal would be guesswork) and the page says so next to the buttons. Purge all deletes every row and truncates `logs/bot-errors.log`. One route serves both: `POST /api/staff/errors/purge` with `{ ids: [...] }` for selected, `{}` for all (an empty/invalid id list is a 400, never a silent purge-all). The purge logic lives in a shared `purgeErrorLogs()` in `src/utils/errorLogger.js`, so a future slash command can reuse it. Retry-queue trap, handled: the bot and dashboard run as separate processes with separate in-memory retry queues, so a dashboard purge cannot clear the bot's queue directly. Purge-all stamps a marker file (`logs/.error-logs-purged-at`) with the purge instant, and `flushQueue()` now drops any queued entry logged before the marker instead of re-inserting it โ a purge can never be undone by a queued backfill, and no bot restart is needed for a complete purge. Entries logged after the purge are unaffected. Verified by `tmp/verify-1.15.12.js` (23/23: purge-all and purge-selected against a fake in-memory `error_logs` table with the real log/marker files, flushQueue drop/keep behavior, invalid-id safety, DB-down purge, EJS renders, dashboard boot with the purge route staff-gated over HTTP, check-deploy 0 problems). Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.11 โ 2026-11-15
Fixed
- Music playback was broken on every YouTube video (1.15.11). Root cause: play-dl 1.9.7 is unmaintained and its extraction no longer works against current YouTube โ `video_info()` returns 22 formats but every one has `url`/`codec`/`container` undefined (only the itag is populated), so `stream_from_info()` feeds `undefined` to `new URL()` and throws `TypeError [ERR_INVALID_URL]: Invalid URL` (the exact stack trace Ace pasted from the live bot, at `musicQueue.js:74`). `video_info()` also intermittently fails with "socket hang up". Reproduced locally on Seven Nation Army + 2 controls; the failure is the extractor, not a voice-connection or ffmpeg problem. Fix: migrated YouTube search + streaming from play-dl to `@distube/ytdl-core` v5 (new dep, play-dl removed) behind a new `src/utils/youtube.js` adapter with the same small surface musicQueue.js used (`search`, `videoInfo`, `stream`), so the command interface, queue behavior, and error messages are unchanged. The adapter picks the highest-bitrate opus audio-only format (itag 251) for native WebmOpus playback, falling back to the highest-bitrate audio-only format (transcoded via ffmpeg) when no opus format exists, and tells the filter path the container to demux (`matroska` for webm). Verified by `tmp/verify-1.15.11.js` (3/3: Seven Nation Army, Never Gonna Give You Up, Get Lucky โ search, videoInfo, and real audio bytes flowing through the adapter) and the full load (266 commands, 37 top-level, 0 problems). Server needs `git pull` + `npm install` (new dependency) + `npm run deploy` + bot restart.
v1.15.10 โ 2026-11-15
Fixed
- Dashboard login was rejected by Discord with "invalid scope :offline" (1.15.10). Root cause: 1.15.4 added `offline` to the OAuth scope (`identify guilds offline`) on the theory it was needed for refresh tokens โ Discord OAuth2 has no `offline` scope, so the authorize URL was rejected outright and nobody could log in. The scope is back to exactly `identify guilds` (the pre-1.15.4 value, confirmed from git history). The 1.15.4 refresh-token machinery is untouched: Discord returns a refresh token on the authorization-code exchange with no special scope needed, so `refreshAccessToken()`, the stored refresh token, renewal on expiry/401, and the "expired connection" notice all keep working. The two comments that credited the `offline` scope for refresh tokens are corrected, and `tmp/verify-session-store.js` now asserts the corrected scope (including a live check of the real /login redirect). Verified by `tmp/verify-1.15.10.js` (20/20: rebuilt authorize URL has scope exactly `identify guilds`, no `offline` anywhere, same client_id/redirect_uri/response_type=code as before; refresh flow intact) and `tmp/verify-session-store.js` (all checks pass). Dashboard boots and serves in wizard mode; bot load unchanged (266 commands, 37 top-level, 0 problems). Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.9 โ 2026-11-15
Fixed
- Dashboard `/servers` crash โ `authExpired is not defined` (1.15.9). Root cause: the 1.15.4 template references `authExpired`, but a dashboard process started before 1.15.4 renders the new `home.ejs` from disk without passing it (EJS reads templates fresh per render). Fixed in depth: `home.ejs` now guards the reference (`typeof authExpired !== 'undefined' && authExpired`, the same defensive pattern the header partial already uses), so the template can never throw for a missing variable no matter which code renders it; and a middleware defaults `res.locals.authExpired = false` for every request (the explicit `authExpired: true` on the expired-connection branch is unchanged, so the 1.15.4 notice still shows). The two redundant `authExpired: false` passes were removed โ the default covers them.
- Same audit found four more pages of the same class, all live: the Threads, Confessions, and Roles settings tabs threw "`threadOverrides` / `pendingConfessions` / `tempRoles` / `xpShopItems` is not defined" because the settings route declared those variables but never fetched them or passed them to the render. They are now fetched per module (thread-archive overrides, pending confessions, active temp roles via `getActiveTempRoles`, XP shop items via `getShopItems`) and passed to the render, so those tabs load with real data.
- Latent instance of the same pattern: `setup.ejs` referenced bare `botUsername`, which the GET `/setup/finish` render never passes (only reachable when `saved` is true, so it never fired). Now guarded with the same `typeof` check. A new audit script (`tmp/audit-template-locals.js`) now checks every dashboard view's bare references against every render of that view, `res.locals` defaults, and `typeof` guards โ it reports clean. Verified by `tmp/verify-1.15.9.js` (21/21: home renders with `authExpired` absent, notice shown when true, empty/logged-out states; setup renders with `botUsername` absent; settings renders for the threads/confessions/roles modules; middleware present before all routes). Dashboard boots and serves in wizard mode; bot load unchanged (266 commands, 37 top-level, 0 problems). Dashboard restart only โ no deploy, no bot restart, no npm install.
v1.15.8 โ 2026-11-15
Changed
- Paginated /help (1.15.8) โ the opening view now lists the 25 categories only (one line each: group name, short description, command count), instead of one giant list of all 266 commands. Picking a group shows its commands 10 per page, each line keeping its real path and description, with a "Page X/Y" indicator in the embed title. Group pages have โ Previous / Next โถ buttons (disabled at the first/last page) and a "Back to categories" button, and the group select menu stays on group pages so users can switch groups without going back first. The invoker-only collector filter from 1.15.7 covers the menu and all new buttons; the reply stays public. No command content, names, or groupings changed. Verified by `tmp/verify-help.js` (full load: 266 commands, 37 top-level, 0 failures; check-deploy: 0 problems; navigation flow driven end-to-end with mock interactions).
v1.15.7 โ 2026-11-15
Changed
- Public replies (1.15.7) โ every slash-command reply, followUp, and deferReply is now PUBLIC (visible to everyone in the channel) instead of ephemeral. `ephemeral: true` was removed from 1,095 call sites across 272 files by a scripted codemod (`tmp/remove-ephemeral-codemod.py`); bare `deferReply({ ephemeral: true })` calls became `deferReply()`. This also removes the `ephemeral` deprecation warnings. Kept ephemeral in 74 audited sites only: replies showing private data (birthday DOB, verification/captcha flows, modmail, reports, personal bookmark/reminder lists, application submission, confessions, ticket ratings, owner-command output) and per-click confirmations that would spam the channel or spoil a game (giveaway/reaction-role/role-menu/RSVP/heist/suggestion-vote/wordle/daily-trivia). /help and /trivia are public now but their menu/buttons are invoker-only via a collector filter (non-invokers get Discord's "This interaction failed"). Verified by `tmp/verify-ephemeral-removal.js` (full load: 266 commands, 37 top-level, 0 failures; check-deploy: 0 problems). README and AGENTS.md conventions updated to the new default.
v1.15.6 โ 2026-11-15
Changed
- Rebrand "Ace Bot" โ "Vikings Hall" (1.15.6) โ pure string rename, no behavior changes. The shared embed footer is now `Vikings Hall โข /utility help` (the `/help` pointer was stale since the 1.15.0 consolidation โ help is now `/utility help`), the help title is `๐ค Vikings Hall โ Help`, suggestion and announcement footers, and the dashboard title/brand/footer/home/version/setup/docs pages all read "Vikings Hall (Dashboard)". README, the dashboard preview page, and the nginx config comments updated to match. The npm package name, repo name, config keys, and the bot's Discord account username are unchanged (the account name is a Developer Portal change, not code).
v1.15.5 โ 2026-11-15
Fixed
- /help group listings (1.15.5) โ every category showed "No commands in this group" after the 1.15.0 consolidation, because help looked up flat command names in client.commands, which now holds consolidated parents. Groups are now defined by parent (all 32 parents covered, merged into 25 categories to fit Discord's 25-option select-menu limit), each listing its real paths (`/mod ban`, `/mod warn add`, `/economy job set`, โฆ) with descriptions. Standalone commands (giveaway, serverbackup, mediathreads) and the two message context-menu commands are listed under "Other" / "Giveaways" instead of being hidden. The opening embed now shows the real total of 266 commands (was 37, the parent count).
v1.15.4 โ 2026-11-15
Changed
- Persistent dashboard logins (1.15.4) โ login sessions are now stored in MySQL (`sessions` table, auto-created by express-mysql-session) instead of in-process MemoryStore, so users stay logged in across dashboard restarts. The login cookie is 30 days (was 24 hours) with `rolling: true`, so active users stay logged in. The new `src/utils/sessionStore.js` lazily picks its backend on first use: MySQL when the database is up, MemoryStore with a console warning when it isn't (the dashboard still boots; sessions just don't persist). The Discord OAuth flow now requests the `offline` scope, so the callback stores a refresh token alongside the access token; the server picker refreshes the access token on 401 (and proactively when it is known-expired) and retries once. If the refresh fails, the user stays logged in โ the server picker shows a "Your Discord connection expired โ log in again" notice instead of forcing a login, and per-server pages redirect to the picker instead of 500ing. Sessions from before 1.15.4 have no refresh token and take the notice path on their next guilds call. The setup wizard's one-time link is unchanged (the token is still single-use; only the resulting authorized session persists).
v1.15.3 โ 2026-11-15
Changed
- Analytics leaderboards (1.15.3) โ the "Top users by XP" and "Top users by commands used" tables on the dashboard analytics page now show "Name (ID)" instead of literal `<@user_id>` mention text, which the browser rendered as plain text, not a mention. Both lists are resolved with a single `resolveUserLabels` call (same helper as the staff list in 1.15.1; de-duplicated, unresolvable IDs fall back to "ID (unknown user)"). Top channels and daily stats are untouched.
v1.15.2 โ 2026-11-15
Fixed
- Auto-translate crash (1.15.2) โ `settings.channels.includes is not a function` on every message when translate was enabled. The `channels_json` column is MySQL JSON, so mysql2 already returns a parsed value, but the reader ran `JSON.parse` on it anyway: a correct array coerced to `"123,456"`, threw, and silently fell back to `[]` (auto-translate never matched), while a bare stored value came back as a number and `.includes` threw. `getTranslateSettings` now normalizes every shape to an array of string channel IDs (parsed array, JSON string, bare number/string, object, null/invalid โ `[]`); bare numeric strings are never JSON-parsed, so snowflake IDs past 2^53 keep full precision. `saveTranslateSettings` normalizes before writing, so a bad shape can never be stored again. No schema change.
- Deprecation warnings (1.15.2) โ replaced `fetchReply: true` with `withResponse: true` in the only three call sites (`/ping`, `/help`, `/trivia`), reading the sent message from `response.resource.message`. No behavior change. The `ephemeral` deprecation (1,171 sites) is a separate sweep and is untouched.
v1.15.1 โ 2026-11-15
Changed
- Staff management page (1.15.1) โ /staff/manage rows now show names as well as IDs: the staff member column shows "Name (ID)" and the added-by column shows "Name (ID)" of whoever added them, instead of raw IDs only. Names resolve via the bot REST API (GET /users/{id}; the dashboard is a separate process with no discord.js client), de-duplicated per page render. Unresolvable IDs fall back to "ID (unknown user)" and never crash the page; rows with a NULL added_by (added outside the dashboard) show "System / config". No schema change โ staff_users is untouched.
v1.15.0 โ 2026-11-15
Changed
- Consolidated all 266 slash commands into 37 top-level commands (1.15.0, BREAKING CHANGE โ every command name users type changes). Discord caps an app at 100 top-level CHAT_INPUT commands per scope, and single-command deploy failed on command #101 with error 30032, so the 266 flat commands are now grouped by folder into subcommands: one parent per folder (e.g. /ban โ /mod ban, /play โ /music play, /ticket-setup โ /ticket setup), utility split into /utility (21) and /tools (25). Children that already define subcommands became subcommand groups (e.g. /mod warn add, /economy job set). serverbackup, giveaway, and mediathreads stay standalone, as do the two message context-menu commands. The 266 command files were not edited โ grouping happens in the new loader src/handlers/consolidate.js at the JSON level, and a parent router looks up the original child module. Permissions are preserved: parents with uniform permissions carry them (/custom, /faq, /starboard, /welcome), and mixed parents enforce each child's original permission at runtime. Feature toggles, mod logging, and command logging keep using flat child names. Autocomplete is now routed too (previously nothing handled it, so /economy job autocomplete was dead). A bulk deploy replaces the whole command list, so the old flat names disappear and the new grouped ones appear.
v1.14.17 โ 2026-11-15
Fixed
- Deploy single-mode reporting (1.14.17) โ a failure in `DEPLOY_MODE=single` used to blame `commands[0]` instead of the command that actually failed; it now names the failing command and how many registered before it. Bulk mode also warns that a bulk deploy replaces the whole list and would remove commands previously registered one-at-a-time.
v1.14.16 โ 2026-11-15
Fixed
- Leveling SQL crash (1.14.16) โ `Unknown column 'messages' in 'field list'`: the leveling code counts every message in `user_levels.messages`, but that column was only ever added by an ALTER note in `sql/schema.sql` โ the CREATE TABLE never had it, so even a fresh install was missing it. An audit found 5 such columns; all 5 are now in the CREATE TABLEs (`user_levels.messages`, `user_levels.prestige`, `tickets.panel_id`, `giveaways.bonus_role_id`/`bonus_entries`, `polls.final_counts`), and the bot now self-heals on startup: `initDatabase()` checks INFORMATION_SCHEMA and adds any missing column (plus recreates the `autoresponders` table if the wizard ran before the `trigger` fix), so existing installs are fixed by restarting โ no manual SQL needed.
v1.14.15 โ 2026-11-15
Changed
- Deploy limit (1.14.15) โ `npm run deploy` now caps at 100 commands by default (Discord rejects a bulk request much above that, and 100 is the per-scope command cap). The script logs every skipped command by name so it is clear what is not registered. Override with `DEPLOY_LIMIT=0` (no limit) or another number, e.g. `DEPLOY_LIMIT=129 npm run deploy`.
v1.14.14 โ 2026-11-15
Fixed
- Deploy bisect (1.14.14) โ 50 commands deploy fine, 100 deploy fine, 130 fail, so the wall is between 100 and 130 commands in one bulk request, not any command's fields. Added `DEPLOY_MODE=single` to the deploy script: registers commands one at a time (POST each, Discord upserts by name), bypassing the per-request bulk array limit. It still counts toward Discord's 200 new-command creates per day and the 100 CHAT_INPUT per scope, and it stops at the first failure naming the command. Next test: `DEPLOY_LIMIT=129 npm run deploy` โ if 129 works, the app cap is not 100 and single-mode can register all 266; if it fails with error 30032, the 100-command cap is real and consolidation into subcommand groups is required.
v1.14.13 โ 2026-11-15
Fixed
- Deploy still failing with the same `0[BASE_TYPE_MAX_LENGTH]: Must be 130 or fewer in length` after 1.14.12 โ the two option-ordering fixes did not change the error, and a full local validation of the payload (every description โค97 chars, names, options โค25, choices โค25, no duplicates, no ordering issues) finds nothing over any documented limit, so the cause is not a command field. The deploy script now prints the raw Discord error and the exact command at index 0 of the sent array, and supports `DEPLOY_LIMIT`/`DEPLOY_OFFSET` to bisect (e.g. `DEPLOY_LIMIT=50 npm run deploy`): if a 50-command slice deploys cleanly, the payload fields are fine and the wall is the request size/count (266 commands vs Discord's 100 global CHAT_INPUT cap); if the slice still fails, the printed index-0 command names the culprit.
v1.14.12 โ 2026-11-15
Fixed
- Autoresponder SQL crash (1.14.12) โ `trigger` is a reserved word in MySQL, so every autoresponder query failed with a syntax error near 'trigger' (and the wizard's auto-run had swallowed the matching CREATE TABLE failure, so the table may not exist yet). The column and all queries now use backticks: `` `trigger` `` in `sql/schema.sql`, `src/commands/utility/autoresponder.js` (INSERT/DELETE/UPDATE) and `src/utils/autoresponders.js` (ORDER BY). If the table is missing, re-run the `autoresponders` CREATE TABLE from `sql/schema.sql`.
- Deploy failures (1.14.12) โ two commands had a required option after an optional one, which Discord rejects: `/invite-reset` (`confirm` after `user`) and `/reactionroles-setup` (`title` after `channel`). Required options now come first in both. Added a pre-flight checker (`check-deploy.js`, run with `node check-deploy.js`) and full Discord error output on deploy failure.
- Known deploy limit (1.14.12) โ the bot now has 264 slash commands, but Discord allows at most 100 global CHAT_INPUT commands per app, so a global deploy cannot register all of them. Consolidating related commands into subcommand groups is the real fix and is still to be done.
v1.14.11 โ 2026-11-15
Fixed
- Startup warning (1.14.11) โ silenced the `ready` DeprecationWarning: `index.js` listened for the literal `'ready'` client event, which discord.js renamed to `clientReady` (it stops working entirely in v15). Now listens for `Events.ClientReady`. Note: `shard.on('ready')` in `shardManager.js` is intentionally untouched โ that is the shard-process event, not the client event.
v1.14.10 โ 2026-11-15
Fixed
- Setup wizard (1.14.10) โ the finish page was unreachable: the `/setup/:step` routes were registered before `/setup/finish`, so Express matched "finish" as a step name, failed to parse it as a number, and bounced the user back to step 1. The finish routes now register first, so step 8 actually reaches the review page and its Save button.
v1.14.9 โ 2026-11-15
Fixed
- Setup wizard (1.14.9) โ step 8 "Review & finish" rendered an empty page with no finish button. The template only shows the review table and "Save config & finish" button on GET /setup/finish, but the wizard sent users to /setup/8, which has no matching template branch. Step 8 now redirects to /setup/finish.
v1.14.8 โ 2026-11-15
Fixed
- Setup wizard (1.14.8) โ removed the setup-only rate limit (10 requests per 15 minutes). It counted every step load and submit, so normal setup use tripped "Too many setup attempts" โ including on the MySQL step. The wizard is still gated by its one-time setup token, and the dashboard's general limit (300 requests per 15 minutes) still applies.
v1.14.7 โ 2026-11-15
Fixed
- Setup wizard (1.14.7) โ step forms submitted via `fetch` with `FormData` (multipart), but the server only parses URL-encoded/JSON bodies, so `req.body` arrived empty and every step failed with "required" even when the fields were filled. Steps now submit as URL-encoded. Also fixed the misleading "Step saved" toast firing on failed steps โ it only shows when the step actually saved.
v1.14.6 โ 2026-11-15
Added
- Safety status (1.14.6) โ admin-only `/safety-status` shows the server's whole protection state in one read-only embed: Automod + antispam state, content-filter rule counts, member-logging setup, autoresponder count, reaction-role mappings, stream watchers, and Automod actions in the last 24h broken down by action.
v1.14.5 โ 2026-11-15
Added
- Content filter (1.14.5) โ admin-only `/content-filter add|remove|list` blocks words (word-boundary match) and harmful-link domains (hostname + subdomains), each rule with its own action (`delete`/`warn`/`timeout`/`delete_warn`/`delete_timeout`) and severity (`low`/`medium`/`high`) in the new `content_filter_rules` table. Enforced in Automod after the spam detectors, before the legacy banned-words list. No built-in word list ships with the bot โ each server defines its own entries. This merges the harmful-content filtering and keyword-protection asks into one system instead of two overlapping lists.
v1.14.4 โ 2026-11-15
Added
- Antispam detectors (1.14.4) โ admin-only `/antispam` adds duplicate-message (same text 3ร in 60s, default), ALL-CAPS (70%+ uppercase over 10+ letters, defaults), mention-spam (max 5 mentions, default), and link-count (max links per message, off by default) detection on top of Automod's rate limit. Each detector has its own toggle and thresholds, sharing one `antispam_action` (new columns on `automod_settings`); running `/antispam` with no options shows the current settings. Detectors are pure functions (`detectDuplicate` / `detectCaps` / `countMentions` / `countLinks`) exported from `src/utils/automod.js`.
v1.14.3 โ 2026-11-15
Added
- Autoresponder (1.14.3) โ admin-only `/autoresponder add <trigger> <response> [match] | remove | toggle | list` (`autoresponders` table). Fires when a phrase appears anywhere in a message (`contains`, default) or only when the whole message is the trigger (`exact`) โ different from `/custom-add`, which only fires on a single trigger word at the start. Replies run after Automod in `messageCreate` and respect the shared "handled" marker, so a message gets at most one auto reply.
v1.14.2 โ 2026-11-15
Added
- Member + moderation logging (1.14.2) โ admin-only `/logging setup <channel> [joins] [leaves] [bans] [kicks] [timeouts] [roles]` and `/logging status` (`logging_settings` table). Logs joins, leaves, bans/unbans, kicks (told apart from leaves via the audit log โ needs View Audit Log), timeouts, and role changes to one log channel. Message deletes/edits stay on the modlog and Automod actions on the Automod log channel.
v1.14.1 โ 2026-11-15
Added
- Reaction-role pause/resume (1.14.1) โ admin-only `/reactionroles-toggle <message_id> <enabled>` pauses or resumes all buttons on one reaction-role message (`reaction_roles.enabled` column). While paused the buttons render disabled and stale clicks get an ephemeral refusal; mappings and requirements are untouched.
v1.14.0 โ 2026-11-15
Added
- Stream check (1.14.0) โ admin-only `/stream-check <platform> <channel>` forces an immediate live check for a watched streamer instead of waiting for the next poll interval. A fresh offline โ live transition posts the announcement to the notify channel (embed + latest clip/video, same as the poller); an already-live streamer reports its status without a duplicate post. TikTok/Facebook return the manual-only note โ there is no public live API for them, and the bot does not fake one with scraping.
v1.13.15 โ 2026-11-13
Added
- Emoji steal (1.13.15) โ `/steal-emoji <emoji> [name]` copies a custom emoji from another server (or an image URL) into this server, with an optional new name. Requires Manage Emojis; same validation as `/emoji-add` (PNG/JPG/GIF under 256KB, name 2โ32 letters/numbers/underscores, emoji slot limit checked first) and logged to `emoji_logs`.
v1.13.14 โ 2026-11-13
Added
- Temp VC setup command (1.13.14) โ admin-only `/tempvc-setup` configures temporary voice channels in Discord (create channel, optional category, on/off) instead of only via the dashboard. Saves the existing `tempvcCreateChannelId` / `tempvcCategoryId` settings; disabling clears the create channel (there is no separate enabled flag).
v1.13.13 โ 2026-11-13
Added
- Translate context menu (1.13.13) โ a "Translate message" message context menu command translates any message into the server's configured auto-translate target language (English by default) and replies ephemerally with the original text and the translation. Uses the same free, no-key Google translate helper as `/translate`; messages already in the target language (or with no text) get a clear ephemeral note instead.
v1.13.12 โ 2026-11-13
Added
- Weather home location (1.13.12) โ `/weather-home set <location>` / `clear` / `view` saves a personal home location per user per server (`user_weather` table). `/weather` with no location now uses your home location first, then the server default from `/weather-set`.
v1.13.11 โ 2026-11-13
Added
- Custom color roles (1.13.11) โ `/color custom <hex>` sets any `#RRGGBB` color: it creates (or recolors) a personal color role named `color-<your user id>`, positioned below the bot's highest role, and wears it like any other color role โ one color at a time, so your old color role comes off. Your personal role shows in `/color list`, and `/color remove` deletes it entirely instead of leaving a dead role behind. Personal roles are tracked in the `user_color_roles` table.
v1.13.10 โ 2026-11-13
Added
- Role shop (1.13.10) โ `/roleshop list` shows roles for sale with prices; `/roleshop buy <role>` spends wallet coins for a one-time purchase (refused if you already have the role or already bought it once). `/roleshop add <role> <price>` and `/roleshop remove <role>` are admin-only. The role must sit below the bot's highest role, and it is granted before any coins are taken so a failed grant never charges you; if the purchase record cannot be written, the charge is refunded and the role removed. Listings in `roleshop_items`, purchases in `roleshop_purchases`.
v1.13.9 โ 2026-11-13
Added
- Daily quests (1.13.9) โ `/quest list` shows today's 5 quests with done/claimed state; `/quest claim [quest]` claims one by ID, or all completed ones if omitted. Quests: claim `/daily`, work a shift, use 5 slash commands, spend 10 minutes in voice, play a casino game โ each verified at claim time from tables the bot already writes, and each paying coins + XP (50โ100 coins, 20โ30 XP). One claim per quest per day, tracked in the `user_quests` table.
v1.13.8 โ 2026-11-13
Added
- Social actions (1.13.8) โ `/ship @user [@user2]` (second user defaults to you) gives a deterministic compatibility % โ same pair, same score every time (FNV-1a hash of the two user IDs) โ as a public embed with a percentage bar and a playful label. `/hug`, `/kiss`, and `/slap @user [message]` fetch a GIF from the free, no-key nekos.best API and post it as a public embed naming actor and target; if the GIF service is down you get a clear error embed instead of a crash. No database use.
v1.13.7 โ 2026-11-13
Added
- Confessions setup command (1.13.7) โ admin-only `/confess-setup` sets the confessions channel, whether staff approval is required (default true), and whether confessions are enabled (default true), and replies with the current setup. Previously these settings could only be changed on the dashboard. Saves via the existing `confessionsEnabled` / `confessionsChannelId` / `confessionsRequireApproval` settings; `/confess` itself (modal submission, approval queue) is unchanged.
v1.13.6 โ 2026-11-13
Added
- Counting leaderboard (1.13.6) โ `/counting-leaderboard` shows the current count, the highest count, and the top 10 counters by correct counts. Per-user correct counts are now tracked on every valid count in the `counting_counts` table (counts start at 0 for everyone โ no backfill from past counting history). The counting rules themselves are unchanged.
v1.13.5 โ 2026-11-13
Added
- Birthday today/next (1.13.5) โ `/birthday today` lists members with a birthday today, and `/birthday next` shows the next upcoming birthday in the server and how many days away it is. Reuses the existing `birthdays` table and the Feb 29 handling from the daily checker; set/remove/list, setup, and the birthday role are unchanged.
v1.13.4 โ 2026-11-13
Added
- Channel lockdown (1.13.4) โ `/lockdown lock [channel] [reason]` (moderators, Manage Channels) locks a channel so @everyone cannot send messages โ the previous @everyone overwrite is stored and restored exactly on `/lockdown release`, which posts a public unlock notice; `/lockdown status` lists currently locked channels. Lock state lives in the `lockdowns` table. Separate from the anti-nuke system's automatic lockdown action.
v1.13.3 โ 2026-11-13
Added
- Verify from anywhere (1.13.3) โ `/verify` lets a member verify without finding the panel: it reports if they are already verified, otherwise sends them a working Verify button (captcha mode opens the math-question modal, same as the panel), or points them to `/verify-setup` if verification is not enabled. Reuses the existing verification gate and `verificationInteraction` handler; no new table.
v1.13.2 โ 2026-11-13
Added
- User reports (1.13.2) โ `/report submit @user <reason> [evidence]` files a report with the moderators: it is stored in the `reports` table and posted as an embed to the modlog channel configured with `/modlog-setup` (falling back to the core log channel). `/report list` (Manage Messages) shows open reports. Self-reports and bot reports are refused.
v1.13.1 โ 2026-11-13
Added
- AFK list (1.13.1) โ `/afk-list` shows an ephemeral embed of everyone currently AFK in the server, with their reason and how long they have been away. Reads the existing `afk_users` table written by `/afk`; the mention notices, auto-clear on return, and nickname prefix are unchanged.
v1.13.0 โ 2026-11-13
Added
- Reminder management (1.13.0) โ `/remind` with `set`, `list`, and `cancel` subcommands: set a personal reminder (same time formats as `/remindme`), list your pending reminders with IDs and relative due times, or cancel one of your own pending reminders. Delivery still goes through the existing 1-minute scheduler loop (DM, falling back to the channel where it was set); reuses the `reminders` table, no new table.
v1.12.6 โ 2026-11-13
Added
- Economy robbery (1.12.6) โ `/rob @user` steals from another member's **wallet** (never the bank) at a flat 35% success chance; success takes 10โ30% of the victim's wallet (min 10, max 1,000 coins), failure costs the robber a fine of up to 100 coins paid to the victim, capped at what the robber can afford (never a debt). Cooldowns: 30 minutes after a success, 1 hour after a failure (`rob_attempts` table). Guards: no robbing bots or yourself, victim needs 50+ wallet coins; the victim gets a DM when possible. Per-server toggle (`guild_settings.robbery_enabled`, default on) plus a recent-robs list on the dashboard Economy tab. Logged as `rob_win` / `rob_loss` / `rob_fine` in `economy_transactions`.
v1.12.5 โ 2026-11-13
Added
- New-member link block (1.12.5) โ members who joined less than N days ago (default 7) cannot post links: the message is deleted, they get a warning that deletes itself after 10 seconds, and the block is logged to Automod actions. Runs independently of the main Automod toggle; staff roles and Automod-exempt roles/channels bypass it. `/newmemberlinks-setup` (admin) and the dashboard Automod tab. Settings in `guild_settings` (`new_member_link_enabled`, `new_member_link_days`).
v1.12.4 โ 2026-11-13
Added
- Giveaway bonus entries (1.12.4) โ `/giveaway start` takes optional `bonus_role` + `bonus_entries` (default 1, max 10); holders of that role get +N entries, and Nitro boosters get +1 automatically when the guild has a booster role configured. The draw is now **weighted** by total entries (`pickWeightedWinners`), and a winner's tickets are removed after winning so nobody wins twice in one draw. Entry confirmations show `Entries: N (includes X bonus)` with the reasons. Bonus entries live in the `giveaway_bonus` table; the giveaway embed, `/giveaway list`, and the dashboard Giveaways tab show the bonus rules.
v1.12.3 โ 2026-11-13
Added
- Work job upgrades (1.12.3) โ per-server job catalog (`work_jobs` table, chosen job in `user_jobs`): Dishwasher (30โ80 coins, free, level 0), Barista (50โ120, 200 coins, level 2), Mechanic (80โ200, 500 coins, level 5), Developer (150โ400, 1,500 coins, level 10), seeded on first use. `/jobs` lists them, `/job buy <name>` unlocks one (wallet coins + level requirement), `/job set <name>` picks an unlocked job. `/work` pays from your job's payout range with that job's flavor text (no job = the old 50โ250 range). Dashboard Economy tab lists the server's jobs.
v1.12.2 โ 2026-11-13
Added
- Nitro booster role (1.12.2) โ `/boosterrole set <role>` (admin) picks the role Nitro boosters get automatically: granted when a member starts boosting, removed when they stop, with a one-time sweep granting it to current boosters on setup. `/boosterrole view` / `/boosterrole remove`. Guard: the role must sit below the bot's highest role. Stored in `guild_settings.booster_role_id`; dashboard Roles tab has the dropdown.
v1.12.1 โ 2026-11-13
Added
- 24/7 music mode (1.12.1) โ `/247 enable <voice channel>` (admin) keeps the bot in that voice channel around the clock: it stays connected even with an empty queue and rejoins if disconnected or kicked. `/247 disable` turns it off (the bot leaves); `/247 status` shows the state. A per-minute checker rejoins dropped connections. Settings in `guild_settings` (`music247_enabled`, `music247_channel_id`); dashboard Music tab has the toggle + channel dropdown. Rejoins are logged via the error logger (info level).
v1.11.6 โ 2026-11-13
Added
- Invite-based auto-roles (1.11.6) โ extends the invite tracker: `/inviterole add <invite_code> <role>` (admin) maps an invite code to a role, and members who join through that invite get the role automatically. The role is based on the code used, not the inviter. Guards: the code must be a real active invite in the guild (validated on add) and the role must sit below the bot's highest role. `/inviterole list` and `/inviterole remove <invite_code>` manage the rules (`invite_role_rules` table). Dashboard Invites tab has the code โ role rules list with add/remove.
v1.11.5 โ 2026-11-13
Added
- Multi-ticket panels (1.11.5) โ multiple ticket panels per guild, each with its own category, staff role, and topic. `/ticket-panel create <title> <category> [staff_role] [channel] [description]` (admin) posts a new panel; `/ticket-panel list` (admin) shows every panel with its category; `/ticket-panel delete <id>` (admin) removes one. The existing `/ticket-setup` stays as the default/first panel. Tickets opened from any panel record which panel they came from (`tickets.panel_id`, added by migration; the bot falls back to the default panel if the column doesn't exist yet). Dashboard Tickets tab lists panels with create/delete.
v1.11.4 โ 2026-11-13
Added
- Prestige levels (1.11.4) โ extends leveling: at the max level (`config.json leveling.maxLevel`, default 100) a member can run `/prestige` โ a confirm-button flow, since it resets level to 1 and XP to 0 โ and gains +1 prestige. Each prestige grants a permanent +10% XP multiplier, capped at +100% (prestige 10): `multiplier = 1 + min(prestige, 10) ร 0.1`. Prestige count is stored in `user_levels.prestige`, a โญ prestige badge shows on `/rank` and the rank card, and a configured prestige role (`guild_settings.prestige_role_id`) is granted permanently. `/prestige-leaderboard` shows the top prestige users. Dashboard Leveling tab has the prestige role setting and the prestige leaderboard.
v1.11.3 โ 2026-11-13
Added
- Countdowns (1.11.3) โ `/countdown create <title> <when> [channel]` (admin/staff) posts a countdown embed that updates itself every minute once under 24h is left, every 5 minutes before that. When it hits zero the message is edited to "๐ \<title\> is here!" and the channel is pinged once. Times accept `in 2h30m`, `in 3d`, or an absolute date like `2026-12-25 18:00`. `/countdown list` shows active countdowns; `/countdown cancel <id>` (admin) cancels one and deletes its message. Stored in the `countdowns` table. Dashboard Events tab (Scheduled) has the list + create/cancel.
v1.11.2 โ 2026-11-13
Added
- Emoji manager (1.11.2) โ `/emoji-add <name> <image_url or attachment>` (admin with Manage Emojis) uploads a custom emoji โ validated: PNG/JPG/GIF under 256KB, name 2โ32 letters/numbers/underscores, and the server's emoji slot limit is checked first. `/emoji-remove <name>` (admin) and `/emoji-list` (ephemeral, paginated) round it out. Dashboard Emojis tab lists the server's emoji with add (URL field) + remove. Additions and removals are logged to the database (`emoji_logs` table).
v1.11.1 โ 2026-11-13
Added
- DJ mode for music (1.11.1) โ `/dj-setup <role> [enabled] [only_skip]` (admin) turns DJ mode on and picks the DJ role; `/dj` (admin) shows the current settings. When DJ mode is on, only the DJ role + admins can use the control commands (`/skip`, `/stop`, `/pause`, `/resume`, `/filter`, `/queue-clear`); everyone else gets an ephemeral error naming the DJ role. With `only_skip` on (the default), `/play`, `/lyrics`, `/queue` and `/nowplaying` stay open to everyone; with it off, every music command needs the DJ role. DJ mode can't be enabled without a DJ role set. Dashboard Music tab has the role dropdown, the toggle, and a read-only list of which commands are DJ-only.
v1.10.6 โ 2026-11-13
Added
- Auto-translate (1.10.6) โ messages in watched channels are detected and translated into the server's target language (default English) via Google's free unofficial translate endpoint (no API key; unofficial, no SLA, may rate-limit โ failures are skipped and logged, never fatal). Language detection is a built-in heuristic (script + common-word matching), no extra dependency. `/translate <text> [to]` for on-demand translation, `/translate-setup` (admin) for channels + target language. Dashboard General tab has the translate settings. Bot messages and commands are never translated.
v1.10.5 โ 2026-11-13
Added
- Button role menus (1.10.5) โ select-menu role pickers, no reactions needed. `/rolemenu create|add|remove|list|delete` (admin, max 25 options per menu โ Discord's select limit). Selecting an option toggles the role; the reaction-role requirements (required role / min days in server / min leveling level, 1.2.6) apply here too, with an ephemeral embed naming the missed requirement. Dashboard Roles tab lists menus and their options.
v1.10.4 โ 2026-11-13
Added
- Member milestones (1.10.4) โ round member counts (100, 250, 500, 1000, 2000, 5000, 10000 โ configurable in `config.json milestones`) get a celebration embed in a configured channel, and the member who triggers one earns a 100-coin economy bonus. Each milestone fires once per guild (`milestones_hit` table). `/milestones` shows the next milestone with a progress bar; `/milestone-setup` (admin) sets the channel. Dashboard General tab shows milestone settings and the next milestone.
v1.10.3 โ 2026-11-13
Added
- Economy heist (1.10.3) โ group gamble. `/heist <bet>` opens a 60-second lobby (public message with a Join button); success chance is 40% + 10% per extra crew member (cap 90%). Success pays everyone their bet back x2; failure loses the bet. Bets use the wallet balance, min 50 / max 5000 coins (`config.json economy.heistMinBet/heistMaxBet`), 1-hour cooldown per user, all flows logged in `economy_transactions` (`heist_bet` / `heist_win`).
v1.10.2 โ 2026-11-13
Added
- Daily trivia challenge (1.10.2) โ one server-wide question per day, posted automatically at a configured hour (default 12:00 UTC) in a configured channel. Same question for the whole server (seeded by date + guild id), first correct answer wins 50 coins + a trivia point. Reuses the existing `src/data/trivia.json` bank โ no second question bank. `/trivia-daily play` (answer today's), `/trivia-daily setup` (admin: channel + hour), `/trivia-leaderboard`. Dashboard Games tab has the settings and leaderboard.
v1.10.1 โ 2026-11-13
Added
- Saved music playlists (1.10.1) โ `/playlist save <name>` saves the current queue (playing track + queued tracks) as a named playlist, `/playlist load <name>` queues it back (voice channel required), `/playlist list [user]`, `/playlist delete`, `/playlist rename`. Per-user, per-server; max 10 playlists per user per server, max 50 tracks each. Dashboard Music tab lists playlists with delete.
v1.9.6 โ 2026-11-13
Added
- Anti-nuke protection (1.9.6) โ rolling-60s destructive-action counting (channel/role deletes, channel-create bursts, bans, kicks) with configurable threshold (default 5) and kick/ban/lockdown actions, role whitelist, owner DM + log-channel alerts, and audit records in `antinuke_events`. Detection is best-effort via the guild audit log, which can lag โ the bot acts after the fact and cannot prevent the first deletions. New guild settings `antinuke_enabled`, `antinuke_action`, `antinuke_threshold`, `antinuke_log_channel_id`, `antinuke_whitelist_roles`. Dashboard Staff โ Anti-Nuke page: per-server settings, whitelist, recent-events table.
v1.9.5 โ 2026-11-13
Added
- Server rules embed (1.9.5) โ `/rules-setup <channel>` (admin) opens a modal for a rules title and rules text and posts a single rules embed in the chosen channel; `/rules` (anyone) shows the current rules in an ephemeral embed; `/rules-edit` (admin) opens a prefilled modal and edits the posted message in place. Re-running setup edits the existing message instead of posting a duplicate โ one rules message per guild, stored in the new `server_rules` table (`guild_id`, `title`, `content`, `channel_id`, `message_id`, `updated_at`). Dashboard General tab: rules editor with title, rules text, channel picker, and live preview.
v1.9.4 โ 2026-11-13
Added
- Weekly economy lottery (1.9.4) โ `/lottery buy [n1 n2 n3]`, `/lottery status`, `/lottery winners`: one ticket per user per week (default 100 coins from the wallet, 3 numbers 1โ30 or random), jackpot = 50% of weekly ticket sales split between 3-match winners, 100-coin consolation for 2 matches. Draws run Sundays at 20:00 server time with results posted to the configured lottery channel and winners DM'd. New tables `lottery_tickets` / `lottery_draws`; new guild settings `lottery_ticket_price`, `lottery_channel_id`. Dashboard Economy tab: lottery status + recent draws.
v1.9.3 โ 2026-11-13
Added
- Welcome DM (1.9.3) โ new members can now also receive a private welcome DM. `/welcome-dm set <message>` (admin) sets the DM template (placeholders `{user}` `{username}` `{server}`) and enables DMs; `/welcome-dm toggle <enabled>` turns them on/off. Both replies are ephemeral and show a rendered preview. Settings live in new `guild_settings` columns (`welcome_dm_enabled`, `welcome_dm_message`). If a member's DMs are closed the DM is skipped silently and logged โ the join flow never breaks. Dashboard Welcome tab: DM message field, toggle, and a test button that DMs the admin a preview.
v1.9.2 โ 2026-11-13
Added
- Purge by user / purge contains (1.9.2) โ `/purge <amount> [user] [contains]` โ filtered message deletion (by user, by text, or both), on top of the existing unfiltered `/clear`. Pinned messages are skipped, messages older than 14 days are skipped (Discord bulk-delete limit) and counted separately in the reply, and every purge is audit-logged to the new `purge_logs` table.
v1.9.1 โ 2026-11-13
Added
- Tempban (1.9.1) โ `/tempban @user <duration> [reason] [delete_days]` โ temporary bans with durations like `12h`, `7d`, `2w`, `30d`, auto-unbanned by a 5-minute expiry timer (plus once at startup). `/tempban-list` (active tempbans with banned-by, reason, and expiry) and `/tempban-cancel` (admin-only early unban). New `temp_bans` table; expiry processing only unbans users who are still banned and logs failures instead of crashing. Guards against tempbanning the server owner, yourself, or anyone with a higher/equal top role. Dashboard Moderation tab: active tempbans with cancel buttons.
v1.8.9 โ 2026-11-13
Added
- Rank card image (1.8.9) โ `/rank` now posts a 900ร300 rank card image (avatar, username, level, XP progress bar, leaderboard rank, total messages) in the same theme as the welcome card, reusing the canvas setup; the text embed is the fallback if canvas fails. Total messages counts every message since this feature was added (`user_levels.messages` โ add the column on existing installs: `ALTER TABLE user_levels ADD COLUMN messages INT UNSIGNED NOT NULL DEFAULT 0;`). Dashboard Leveling tab: rank card preview with sample data.
v1.8.8 โ 2026-11-13
Added
- Inactive-member re-engagement (1.8.8) โ `/reengage-setup enable [days] [channel]` (admin) turns on a daily job (10:00) that DMs members inactive for N days (default 30) a friendly "we miss you" message โ at most once per member per 30 days, never bots, never members who joined less than N days ago, never members who opted out with `/reengage-optout` (anyone). `/reengage-preview` (admin) shows who would be messaged without sending anything. Activity is read from the data the bot actually records: `user_levels.last_xp_at` (last message that earned XP), `voice_sessions` (last voice session), `user_stats.last_seen` (last slash-command use). Logs in `reengage_logs`, opt-outs in `reengage_optouts`; dashboard Analytics page shows the inactive count and last-run summary.
v1.8.7 โ 2026-11-13
Added
- Auto-publish announcements (1.8.7) โ `/autopublish add|remove|list` (admin) manages announcement channels that auto-publish. Messages posted in a configured announcement channel (type GUILD_ANNOUNCEMENT) are crossposted automatically. Bot messages and already-published messages are skipped; failures go to the error log. Channels in `guild_settings.autopublish_channels` (JSON); dashboard Announcements tab.
v1.8.6 โ 2026-11-13
Added
- Message bookmarks (1.8.6) โ `/bookmark add <message_id or link> [note]` saves a message to your own list (only messages in channels you can read); `/bookmark list` shows yours (ephemeral, with jump links); `/bookmark remove <id>` removes one. A message context-menu command "Bookmark message" is also registered. Only a 500-character excerpt is stored โ never the full message body. Bookmarks in `bookmarks`.
v1.8.5 โ 2026-11-13
Added
- AFK voice channel auto-create (1.8.5) โ `/afkchannel-setup` (admin) sets the primary AFK channel and the max users (default 10). When the primary AFK channel reaches max users, the bot creates a second AFK voice channel ("AFK 2") in the same category; when it empties, it's deleted. If the primary is empty for 10 minutes and a secondary exists and is also empty, the secondary is deleted. Settings in `guild_settings` (`afk_autocreate_enabled`, `afk_channel_id`, `afk_max_users`); dashboard Temp VC tab.
v1.8.4 โ 2026-11-13
Added
- Invite rewards (1.8.4) โ `/invitereward add <invites> <role|coins> <value>` (admin), `/invitereward list`, `/invitereward remove <invites>`. When a member's valid invite count reaches a configured milestone, the reward (role or coins to their economy wallet) grants automatically โ once per milestone โ and they're DM'd, plus a post in the invite log channel if set. Fake joins never count. `/myinviterewards` shows progress to the next reward. Milestones in `invite_rewards`, grants in `invite_reward_grants`; dashboard Invites tab lists them with add/remove.
v1.8.3 โ 2026-11-13
Added
- Auto-role on level โ announcement side (1.8.3) โ level role rewards already auto-grant on level-up (1.3.5); this version adds the announcement channel. `/levelup-channel set <channel>` (admin) picks where the bot posts an embed when someone levels up AND gains a role; `/levelup-channel view` / `clear` manage it. `/levelrewards` already shows which roles auto-grant at which levels. Channel in `guild_settings.levelup_channel_id`; dashboard Leveling tab has the dropdown + reward roles list.
v1.8.2 โ 2026-11-13
Added
- Ticket ratings (1.8.2) โ when a ticket closes, the creator is DM'd a 1โ5 star prompt (buttons) with an optional comment modal. If their DMs are closed the prompt is skipped silently and the skip is logged. `/ticket-ratings` (staff) shows the average rating, count, and recent ratings with comments; dashboard Staff โ Tickets page has the average card + ratings table. Ratings in `ticket_ratings`.
v1.8.1 โ 2026-11-13
Added
- Poll results chart (1.8.1) โ when a poll ends, the results message includes a bar chart (node-canvas, already installed for the welcome cards) with each option's vote count and percentage. `/poll-results <message_id or link>` shows any poll's results with the chart, live or ended. Final tallies are stored in `polls.final_counts` so results survive restarts (add the column on existing installs: `ALTER TABLE polls ADD COLUMN final_counts JSON NULL;`). Dashboard Polls tab shows past polls with charts.
v1.7.8 โ 2026-11-13
Added
- Embed builder (1.7.8) โ `/embed create` (admin) โ modal (title, description, color), then a second modal for image/footer/channel โ posts the finished embed to the chosen channel. `/embed edit <message_id or link>` (admin) edits an existing bot-posted embed in place. Built embeds stored in the `embeds` table; dashboard Embeds tab lists them with edit (form) and delete.
v1.7.7 โ 2026-11-13
Added
- Snipe (1.7.7) โ `/snipe [channel]` and `/editsnipe [channel]` (staff only) show the last deleted message / last edited message's before-and-after as an embed. In-memory only โ deleted message content is never written to the database or the error log โ kept per channel for 10 minutes. If nothing recent, the bot says so.
v1.7.6 โ 2026-11-13
Added
- Custom status roles (1.7.6) โ `/statusrole add <text> <role>` (admin), `/statusrole remove <text>`, `/statusrole list`. On presence update, if a member's custom status contains the trigger text (case-insensitive) the role is granted; when it stops containing it, the role is removed. A 10-minute sweep catches missed updates. Guards: the role must sit below the bot's highest role; bots never get status roles. Honest note: custom statuses only update when Discord sends a presence update, so there can be a delay. Rules in `status_roles`; dashboard Roles tab lists them with add/remove.
v1.7.5 โ 2026-11-13
Added
- Image-only starboard (1.7.5) โ `/starboard-image-setup` (admin) sets a separate image channel + threshold (default 3). Same star-reaction flow as the main starboard, but only messages with image/video attachments qualify โ they post as a large-image embed in the image channel. If no image channel is set, image posts go to the main starboard as before. Settings in `guild_settings` (`image_starboard_channel_id`, `image_starboard_threshold`); dashboard Starboard tab.
v1.7.4 โ 2026-11-13
Added
- AFK voice kick (1.7.4) โ `/afkvoice-setup` (admin) enables it, sets the minutes threshold (default 30) and the AFK channel (blank = disconnect instead). On voice state changes the bot tracks when a member goes mute/deafened; a 5-minute timer moves members muted/deafened continuously longer than the threshold to the AFK channel. Never moves bots, members already in the AFK channel, or holders of a configurable exempt role. Moves logged to `afk_voice_moves` + modlog if set. Dashboard Moderation tab has the settings.
v1.7.3 โ 2026-11-13
Added
- Slowmode presets (1.7.3) โ `/slowmode set <seconds> [channel]` (admin) applies immediately; `/slowmode-schedule <channel> <day_seconds> <night_seconds> <night_start> <night_end>` (admin) sets a day/night schedule โ a 15-minute timer applies the right value for the current hour. `/slowmode-schedule-remove <channel>` (admin). Schedules in `slowmode_schedules`; dashboard Moderation tab lists and edits them.
v1.7.2 โ 2026-11-13
Added
- Event scheduler (1.7.2) โ `/event create <title> <date/time> [description] [channel]` (staff) posts an embed with Going / Maybe / Can't go buttons; `/event list`, `/event cancel <id>` (admin). A 1-minute timer sends RSVP'd members (Going/Maybe) a DM reminder 1 hour before โ channel mention if their DMs are closed โ and posts a "starting now" message in the channel. Events in `scheduled_events`, RSVPs in `event_rsvps`. Dashboard Events tab lists upcoming events with RSVP counts and can create/cancel them.
v1.7.1 โ 2026-11-13
Added
- Wordle / daily games (1.7.1) โ `/wordle` โ one game per user per day, same word for everyone in the server (seeded from date + guild id, like daily trivia). Guess via modal (5 letters, 6 guesses), green/yellow/grey-square feedback, win/lose embed, streak tracked (consecutive winning days; a loss or missed day resets to 0). `/wordle-leaderboard` shows top streaks/wins. The word list is `src/data/words.json`: 1,200 common answers + 14,855 allowed guesses, from the open tabatkins/wordle-list and first20hours/google-10000-english lists โ not hand-written. Games in `wordle_games`. Dashboard Games tab shows today's word (staff only) and the leaderboard.
v1.6.6 โ 2026-11-13
Added
- Voice leaderboard (1.6.6) โ `/voicelb` ranks members by total voice time, from `voice_sessions`; `/voicetime [user]` shows your (or their) total voice time. Voice time only counts when not muted/deafened and at least one other non-bot user is in the channel (the same rules as voice XP, 1.4.3).
v1.6.5 โ 2026-11-13
Added
- Birthday role (1.6.5) โ `/birthday-role` (admin) picks a role that is granted to a member on their birthday and removed the next day. The daily birthday checker handles both the grant and the removal; grants are tracked in `birthday_roles_granted` so a role is never double-granted or left behind.
v1.6.4 โ 2026-11-13
Added
- Confessions (1.6.4) โ `/confess <text>` posts an anonymous confession; the author is never shown publicly (posts show only "Anonymous" + a number). A staff approval queue is on by default: confessions wait in a review channel until staff approve or deny them, and denied confessions are never posted. Approval can be turned off per server. Authors are visible to staff only in the review queue (`confessions` table).
v1.6.3 โ 2026-11-13
Added
- Daily streaks (1.6.3) โ `/daily` now builds a streak: +25 XP per streak day, with the streak bonus capped at +500, tracked in the `streaks` table. Milestone crates are awarded at 7/30/100-day streaks. `/streak` shows your current streak and `/streak-leaderboard` ranks the longest streaks. Missing a day resets the streak to 0.
v1.6.2 โ 2026-11-13
Added
- XP role shop (1.6.2) โ per-server configurable: each guild has its own `xp_shop_items` catalog and prices, no global catalog. `/xpshop` lists your server's items, `/xpshop-add <role> <xp_price>` (admin) adds one, `/xpshop-remove <role>` (admin) removes one. Buying spends leveling XP (not coins) and grants the role.
v1.6.1 โ 2026-11-13
Added
- Thread auto-archive control (1.6.1) โ per-channel archive-duration overrides in `thread_archive_settings`: `/threadarchive set <channel> <duration>` (admin) sets 1h/24h/3d/1w or off. Threads in overridden channels are auto-archived after the chosen inactivity, skipping pinned threads and threads with recent staff activity. Dashboard Moderation tab lists the overrides.
v1.5.5 โ 2026-11-13
Added
- Quote system (1.5.5) โ `/quote <text> [author]` saves a quote, `/quotes [user]` lists saved quotes, `/quote-random` posts a random one, and `/quote-leaderboard` ranks who has the most saved quotes (`quotes` table). Quote embeds are public posts.
v1.5.4 โ 2026-11-13
Added
- Server backup/restore (1.5.4) โ `/serverbackup create` (admin) exports roles, channels, and bot settings to a JSON file in `backups/`; `/serverbackup restore <file>` (admin) restores them with a two-step confirm. Non-destructive by default: nothing existing is deleted unless explicitly confirmed. Message history is NOT backed up (stated in the README).
v1.5.3 โ 2026-11-13
Added
- Anti-ghost-ping (1.5.3) โ when a message that pinged someone is deleted, the bot posts a callout naming who was ghost-pinged and by whom (plus the modlog, if set). Bot and automod deletions are excluded, and at most 1 callout is posted per user per minute. `/ghostping-setup` (admin) sets the callout channel and toggle.
v1.5.2 โ 2026-11-13
Added
- Temp roles (1.5.2) โ `/temprole give <user> <role> <duration>` (mod) grants a role that expires automatically on a minute timer (`temp_roles` table); expiry is logged to the modlog. `/temprole list` shows active temp roles and `/temprole remove` ends one early.
v1.5.1 โ 2026-11-13
Added
- Media auto-threads (1.5.1) โ when a message with an image/video attachment is posted in a configured media channel, the bot creates a thread on it for discussion. `/mediathreads set <channel>` (admin) toggles a channel; `/mediathreads list` shows the configured channels.
v1.4.6 โ 2026-11-13
Added
- Modmail (1.4.6) โ members DM the bot to open a modmail thread in a staff channel; staff replies relay back to the member's DMs and member DMs relay into the thread (`modmail_threads` / `modmail_messages` tables). `/modmail-setup` (admin) picks the staff channel, `/modmail-close` (staff) closes a thread, `/modmail-block` (staff) blocks a user from modmail (`modmail_blocks`).
v1.4.5 โ 2026-11-13
Added
- Clips with live announcements (1.4.5) โ when a streamer goes live, the announcement can include their latest Twitch clip (Helix) or, for YouTube streamers, their latest video (YouTube has no clips API). `/stream-clip-toggle <streamer>` (admin) turns the clip on or off per streamer. If the clip fetch fails, the live announcement still goes out โ a clip failure never blocks it.
v1.4.4 โ 2026-11-13
Added
- Self-assignable color roles (1.4.4) โ `/color list` shows the server's color roles, `/color set <role>` gives you one color role at a time (your old one is removed), `/color remove` clears it. `/color-add` and `/color-remove-role` (admin) manage the catalog (`color_roles` table). The bot checks role hierarchy before granting.
v1.4.3 โ 2026-11-13
Added
- Voice XP (1.4.3) โ members earn leveling XP for time in voice channels (default 2 XP/min), using the same `user_levels` table as message XP. Only counts when not muted/deafened and at least one other non-bot user is present. `/voicexp` (admin) shows the setting; voice sessions are recorded in `voice_sessions`.
v1.4.2 โ 2026-11-13
Added
- Minecraft live status widget (1.4.2) โ `/mcstatus-setup <server> [channel]` (admin) posts an embed showing a Minecraft server's live status (online players, version, MOTD) that refreshes every 5 minutes (`mc_widgets` table). Reuses the existing Minecraft ping provider.
v1.4.1 โ 2026-11-13
Added
- AI chat/Q&A (1.4.1) โ `/ask <question>` plus an AI channel, answered from the owner's own OpenAI-compatible API key in the `config.json` `ai` section (get a key at platform.openai.com/api-keys; see `_whereToGetKeys`). 10-second per-user rate limit, daily per-guild cap default 100, usage logged in `ai_usage`. If no key is configured, the feature replies with a clear disabled message instead of failing.
v1.3.6 โ 2026-11-13
Added
- Custom welcome images (1.3.6) โ new-member welcome posts can use a 900x300 canvas card with the member's avatar, name, and member count (`welcomeCard.js`, node-canvas). Falls back to a plain embed if canvas fails to load (missing native build deps โ documented in the README). Toggle in the welcome settings / dashboard Welcome tab.
v1.3.5 โ 2026-11-13
Added
- Level-up reward reminders (1.3.5) โ `/levelrewards` lists the level roles and the level at which each is granted, plus any reminders you have set. A "Remind me" button on a reward you haven't reached stores a reminder (`level_reminders` table) and the bot DMs you when you hit that level. If the guild has no level rewards configured, the command says so.
v1.3.4 โ 2026-11-13
Added
- Server analytics page (1.3.4) โ dashboard Analytics page with joins/leaves over time, messages per day, top channels, and top users, drawn from real MySQL data (`guild_daily_stats`, `message_logs`, `user_stats`) with vanilla-JS charts. No made-up numbers.
v1.3.3 โ 2026-11-13
Added
- XP boosts (1.3.3) โ `/xpboost start <multiplier> <duration>` (admin) starts a server-wide XP boost, `/xpboost stop` ends it early, `/xpboost status` shows the active boost and time left (`xp_boosts` table). Boosts multiply message (and voice) XP while active.
v1.3.2 โ 2026-11-13
Added
- Ticket transcripts in dashboard (1.3.2) โ Staff โ Transcripts lists every closed ticket's HTML transcript with search, view, and download (`ticket_transcripts` index table; the list backfills from transcript files on disk so older transcripts show up too).
v1.3.1 โ 2026-11-13
Added
- Giveaway requirements (1.3.1) โ `/giveaway start` now takes optional `required_role`, `min_days`, and `min_level`; members who don't meet them can't enter and get an ephemeral embed naming exactly what they missed (role, days in server, or leveling level). Requirements are stored on the giveaway and shown on the giveaway embed.
v1.2.7 โ 2026-11-13
Added
- Weather commands (1.2.7) โ `/weather <location>` (temperature, feels-like, condition, humidity, wind, pressure, visibility, sunrise/sunset) and `/forecast <location> [days 1-7]` (high/low, condition, precipitation chance per day), powered by Open-Meteo โ free, no API key. Locations accept a city name, ZIP code, or "latitude,longitude". `/weather-set` (admin) stores a per-server default location and units (`guild_settings.default_weather_location`, `weather_units`); imperial (ยฐF/mph) by default, metric (ยฐC/km/h) via an option or the server default. Unknown places and API outages get clear error embeds (failures logged via the error logger, never a crash).
v1.2.6 โ 2026-11-13
Added
- Reaction roles with requirements (1.2.6) โ `/reactionroles-add` now takes optional `required_role`, `min_days`, and `min_level`; members who miss a requirement get an ephemeral embed naming exactly what they missed (required role, days in server, or leveling level). `/reactionroles-list` and the dashboard Reaction Roles tab show each mapping's requirements. Requirements live in new `reaction_roles` columns (`required_role_id`, `min_days_in_server`, `min_level`).
v1.2.5 โ 2026-11-13
Added
- Birthday system (1.2.5) โ `/birthday set <month> <day> [year]` (real-date validation, Feb 29 handled), `/birthday remove`, `/birthday list` (upcoming, with ages); `/birthday-setup` sets the announcement channel and hour (default 9 AM, bot host local time). A daily/hourly checker posts a birthday embed once per user per year (`birthdays` table, `announced_last_year`). Dashboard Birthdays tab with channel/hour settings and the upcoming list.
v1.2.4 โ 2026-11-13
Added
- Music extras (1.2.4) โ `/filter bassboost|nightcore|vaporwave|8d|off` (FFmpeg re-encoding via prism-media; applying a filter restarts the current track with the filter on). `/lyrics [song]` from the free lyrics.ovh API (no key). `/nowplaying` rich embed with progress bar, requester, queue position, and filter status. `/play` now accepts Spotify track links โ the track is matched on YouTube via Spotify's public oEmbed endpoint; Spotify audio is never streamed directly, and playlist/album links only match their top YouTube result (documented in the README and wiki).
v1.2.3 โ 2026-11-13
Added
- Temporary voice channels (1.2.3) โ joining a designated "create" voice channel spins up a personal voice channel named after the member (in a chosen category) and moves them in; it is deleted when empty (`temp_channels` table). Owner controls with `/tempvc limit|lock|unlock|rename|kick|claim`. Dashboard Temp VC tab for the create channel and category.
v1.2.2 โ 2026-11-13
Added
- Counting + bump reminders (1.2.2) โ counting game in a configured channel: messages must start with the next number, same user twice in a row or a wrong number deletes the message and resets the count to 0 (`counting_settings` table, `current_count`/`highest_count`). `/counting-setup`, `/counting-reset`. Bump reminders: `!d bump` and DISBOARD bump confirmations are recorded; 2 hours later the bot posts a "Time to bump!" reminder in the configured channel (`bump_settings` table). `/bump-setup`, `/bump` (timer / record a manual bump). Dashboard Counting tab.
v1.2.1 โ 2026-11-13
Added
- Verification gate (1.2.1) โ new members verify before getting the member role. Button mode (click Verify) or captcha mode (click Verify, then answer a quick math question in a modal โ image-free captcha, no image generation). `/verify-setup` (channel, role, mode โ posts the Verify panel), `/verify-toggle`. New members are DM'd where to verify; grants are logged to `verification_logs`. Dashboard Verification tab.
v1.1.2 โ 2026-11-13
Added
- Fancy dashboard redesign โ glassmorphism cards, sidebar layout, Inter font, toggle switches, hover-lift server cards.
- Staff area on the dashboard โ bot overview, global command/feature toggles, staff management, owner broadcast, errors page, backups page.
- Streams management on the dashboard โ add/edit/remove/refresh watched streamers; live-channel name that renames to say a streamer is live and restores the original name when they go offline; per-server live-channel name template stored in MySQL (`{name}`, `{game}`, `{title}`), editable on the dashboard or with `/stream-template`.
- Applications (Appy-style) โ `/application-create`, `/apply`, review channel with Accept/Deny buttons, role grant + DM on decision, dashboard review queue.
- Invite tracker โ who invited who, leaves, fake-account flagging, vanity URL joins, leaderboard, dashboard tab.
- Error logging for staff โ every error/warn into the `error_logs` table (backfilled from file if MySQL is down), `/errors`, `/error <id>`, dashboard Staff โ Errors page.
- Daily database backups โ 3 AM, 30-day retention, `/backup`, dashboard Staff โ Backups page with downloads, restore script.
- Config key links โ every API key in `config.json` has its official "get it here" link next to it.
- First-run setup wizard (NamelessMC-style) โ 8 steps with test-connection buttons, reachable through a domain via a one-time setup token, plus Nginx reverse-proxy support (`deploy/nginx/`).
- GitHub repo โ private `Acebennett22/discord-bot`.
- `/hostinfo` (owner-only) โ host OS/CPU/memory/disk/runtime specs.
- `/announce` (admin) โ announcement embeds with color, image, footer, role ping, and plain-text mode.
- Welcome & goodbye messages โ templated join/leave embeds (`{user}`, `{username}`, `{server}`, `{membercount}`), dashboard Welcome tab.
- Automod โ spam detection, banned-words filter, link/invite blocking, exempt roles/channels, dashboard Automod tab.
- Suggestions โ `/suggest` with ๐/๐ voting (one vote per user), staff Approve/Deny/Implement, dashboard Suggestions tab.
- Economy โ `/balance`, `/daily`, `/work`, `/pay`, `/eco-leaderboard`, `/shop`, `/shop-add`, `/deposit`, `/withdraw`; wallet + bank in MySQL, shop roles, dashboard Economy tab.
- Casino โ `/slots`, `/blackjack` (Hit/Stand buttons, 3:2 blackjack), `/roulette`, `/gamble-coinflip`, `/gamble-dice` on the same wallet balance; min bet 10 / max 10,000, 5s cooldown, wins/losses in `economy_transactions`.
- Starboard โ starred messages posted to a starboard channel with live counts, dashboard Starboard tab.
- Custom commands โ per-server trigger words with stored replies, dashboard Custom Commands tab.
- Message logging (modlog) โ deleted/edited messages stored in MySQL and posted to a modlog channel (secrets redacted).
- AFK โ `/afk` / `/afk-remove`, mention notices, auto-clear on return, optional `[AFK]` nickname prefix.
- Polls โ `/poll` / `/poll-end`, reaction voting with one vote per user and a live tally.
- Auto-role + sticky roles โ `/autorole set|remove|view|sticky`, roles saved on leave and restored on rejoin, dashboard Roles tab.
- Scheduled messages & reminders โ `/schedule`, `/schedule-list`, `/schedule-cancel`, `/remindme`; stored in MySQL so they survive restarts, dashboard Scheduled tab.
- FAQ auto-responder โ trigger phrases (exact or contains) answered in-channel, `/faq-add` / `/faq-remove` / `/faq-list`, dashboard FAQ tab.
- Presence โ rotating Discord status with live stats (`{guilds}`, `{users}`, `{commands}`, `{uptime}`, `{version}`), `/presence set|reset|list` (owner), dashboard Staff โ Presence section.
- Bot version in `/botstats` and `/status` (read from `package.json`).
- Version/Changelog page on the dashboard (`/version`), rendered from this file.
- Inventory, crates & trading โ `/buy`, `/sell`, `/inventory`, `/open-crate`, `/use`, `/trade`, `/trade-cancel`; Common/Rare/Legendary crates with weighted loot, daily item rewards on `/daily`, a 25%-off daily deal per guild, and atomic player-to-player trades (one DB transaction).
- Bot tracking โ join scoring (account age, avatar, username patterns, join bursts, creation clustering), flag/kick/ban auto-actions (flag-only by default), `/botflags`, `/botflag`, `/botflag-clear`, `/bottrack`, and a Staff โ Bot Tracking dashboard page.
- Wiki/docs page on the dashboard (`/docs`) โ getting started, a command reference generated live from the bot's command files, feature guides, FAQ, and client-side search.
- Dashboard JavaScript layer โ `dashboard/public/app.js` + per-page modules (`js/settings.js`, `js/staff.js`, `js/setup.js`, `js/docs.js`): fetch-based saves with toasts, immediate toggles, live list refresh, DOM row removal on delete, 30s staff-overview auto-refresh, client-side wizard navigation, live previews, and docs search. EJS server render + plain-POST fallback remain for no-JS browsers.
Changed
- All slash-command replies are ephemeral โ only the public posts a command is meant to make in a channel (polls, announcements, suggestions, FAQ replies) stay public.
- The first-run setup wizard now auto-runs both `sql/schema.sql` and `sql/premium.sql`.
- Premium features (economy, starboard, custom commands, message logs, AFK, polls, auto-role/sticky roles, scheduled messages, FAQ, presence) live in `sql/premium.sql`, separate from `sql/schema.sql`.
- Bot version bumped to 1.1.2.
- Dashboard default port is now 3010 (was 3000) โ `config.json` `dashboard.port`, redirect URI, Nginx config, and README updated.
Fixed
- Setup wizard SQL runner no longer drops the first `CREATE TABLE` in a schema file when the file starts with a header comment.
v1.0.0 โ 2026-11-12
Added
- Initial release: moderation (`/kick`, `/ban`, `/unban`, `/timeout`, `/warn`, `/clear`), music (`/play`, `/skip`, `/stop`, `/queue`, `/pause`, `/resume` via YouTube), tickets with HTML transcripts, leveling/XP with rank and leaderboard, giveaways, reaction roles, game server status with pluggable providers, stream notifications (Twitch, YouTube, Kick), Steam account linking, server stats channels, multi-server support with sharding, MySQL logging/stats, and a Dyno-style web dashboard with Discord OAuth2.