Skip to main content
ChangelogOne entry per dayChanges explained by their impact

A timeline of changes — what changed and when

Entries come from the repository’s actual history. All changes from a day are grouped together, regardless of how many deployments took place. There are no promised features or unverifiable figures. We deploy continuously, so entries use dates rather than version numbers. The current bot version is shown on the service status page.
26days with recorded changes
144documented changes
  • security
  • new
  • fix
  • improvement
  1. latest new · 4

    The public leaderboard as a reward: tabs, a podium stage and account stats

    The public leaderboard celebrates the top three with an animated podium stage, and every member gets a tab with detailed statistics about their activity on the server.

    • newThe leaderboard is split into Ranking, Account stats and Server tabs, and the period podium greets the champions with confetti, a crown, light rays behind first place and steps rising under the cards.
    • newThe Account stats tab shows the level with an XP bar, positions for the day, week, month and all time, a 12-week activity calendar, favourite weekdays, the active-day streak, the best day, medals and prestige.
    • newThe Server tab shows how points split between the podium, places 4–10 and everyone else, the average and median score, and the record holders in chat and voice channels.
    • newThe /leaderboard activity command shows the period podium in Discord as an image — champions with a crown, points and position changes — with a period switcher and a button to the full results on the website. The existing XP, message and voice rankings moved to /leaderboard levels.
  2. new · 5fix · 8improvement · 3

    A complete English version and weekly summaries with real data

    The bot, the dashboard and the public site now work entirely in Polish and in English, and a single server setting chooses the language. We also fixed both weekly summaries, which showed placeholder names and zeros.

    • newServer presets, seasonal greeting templates, profile card styles, FACEIT errors and bot alerts are created in the server's language instead of always in Polish.
    • newThe privacy policy, terms of service, DPA, changelog, roadmap, demo, partners, servers, badge and the /uprawnienia and /porownanie-botow-discord pages now have English versions.
    • newPage titles and descriptions in search results and link previews follow the visitor's language; without a saved choice, the site uses the browser's language settings.
    • newThe profile card shows monthly podium medals as shiny honours, a profile prestige rank from Bronze to Server legend, and your place in the current month with how far you are from the podium.
    • newThe public leaderboard has a new look: day, week, month and all time, the top of three periods at once, climbs and drops, a server pulse chart, a personal progress panel and animated numbers — in the dashboard's colours.
    • fixThe weekly leaderboard announcement showed “User 1” and “User 2” instead of nicknames. It now names the real members together with their level.
    • fixThe weekly direct-message report showed zero messages and zero minutes. It now counts them from the same data as the leaderboard and adds the level with progress and the member's place on the server.
    • fixOlder VenonSec modules read the language from a separate field that could drift from the server setting; that field now mirrors the single setting.
    • fixThe esports server preset pointed its ticket panel at a tryouts channel it never created; the channel is now part of the preset, with a description.
    • fixEnglish bot replies, the dashboard, the guides and the documentation used Polish command names such as /graj or /zglos; they now give the names an English Discord client shows: /play, /report, /profile.
    • fixA failed server configuration save rolled back to the previous write, which might also have failed; it now returns to the last confirmed state.
    • fixOn a fresh installation, the Polish daily preset greetings had no holidays or themed days, because their catalogue never reached the repository. The catalogue now ships with the bot, and a missing catalogue logs a warning.
    • fixThe message after restoring a backup was always in Polish, with wrong number agreement; it now arrives in the server's language, for example “Restored 4 roles, 2 categories, 7 channels and 3 settings”.
    • improvementThe change log and API messages now use correct Polish characters and number agreement, for example “1 pozycja” instead of “1 pozycji”.
    • improvementAfter the server language changes, the dashboard immediately fetches data in the new language instead of showing text loaded earlier.
    • improvementThe dashboard runs on Next.js 16.3.5 with security fixes, including a critical flaw in image optimisation, and the bot and dashboard dependencies pass the audit with no findings.
  3. new · 4improvement · 1

    The public site in English: commands, status, help and the Trust Center

    The last large sections of the public site got English versions, and the command catalogue now teaches the syntax the Discord client actually shows in each language.

    • newThe command catalogue shows English command and option names, such as /profile and /ban user: reason:, because that is the syntax an English-language Discord client expects.
    • newThe /status page, the incident history and the diagram of an event's path through the bot are in English, and monitoring failure reasons are translated instead of arriving from the API in Polish.
    • newHelp, the quick troubleshooting tool and the pre-installation FAQ have English versions with the same URL anchors, so a shared link works in both languages.
    • newThe Trust Center has an English version with the same tables and source files, and legal references are given as Article 6(1)(b) GDPR instead of the Polish notation.
    • improvementThe home page widgets — live telemetry, the protection demo, the dashboard preview and the protection console — speak the visitor's language.
  4. new · 4

    Module pages, guides and documentation in English

    The most extensive content on the public site — the module pages, the guides and the documentation — now has a complete English version.

    • newTwelve module pages have their full content in English, including defaults, limitations and questions.
    • newThe in-depth AntiRaid, AutoMod, Verify, LinkShield and Dashboard pages have English versions, FAQ included.
    • newEleven guides, together with their search and step-by-step plan, work in English.
    • newThe /opis, /funkcje and /dokumentacja pages have English versions, and module categories stay shared, so filters behave the same in both languages.
  5. new · 4improvement · 1

    The bot answers in English, and so does the home page

    A server set to English gets the bot's replies, games, logs, the VenonSec panel, applications and API messages in English. The home page and the command catalogue got English versions too.

    • newChannel games — Counting, Word chain, Wordle, Hangman, Guess the Number, Anagrams and Quiz — and the reaction and voice logs answer in the server's language.
    • newThe VenonSec panel on Discord, the public application flow, the weekly report, captcha verification and the level-up message speak the server's language.
    • newError and confirmation messages from the bot's API reach the dashboard in the server's language.
    • newThe venon-sec.xyz home page, the navigation, the footer, the public /l/ leaderboard and the /komendy page have English versions.
    • improvementThe sign-in screen, the dashboard 3.0 tabs, the channel and role pickers and the incident card read their text from the dictionary in both languages.
  6. new · 4improvement · 1

    More dashboard centres in both languages

    Automation, the server centre, the MSIoU network, the setup wizard, analytics, applications, and levels and games all work in the dashboard in Polish and in English.

    • newThe automation centre — self-service roles, temporary roles, temporary channels, presets and schedules — is bilingual.
    • newThe server centre, with commands, backups, operator access and the change log, and the MSIoU network with its dossier speak the server's language.
    • newThe setup wizard, the analytics centre with voice counters and CSV export, and applications with the form builder are available in English.
    • newXP levels with paths and circles, the Game Center with seven minigames, and suggestions and quotes work in both languages.
    • improvementNumbers, dates and CSV export headers are formatted according to the server's language.
  7. security · 2new · 3fix · 1improvement · 1

    The dashboard speaks the server's language, and protection toggles really work

    The dashboard language now comes from the server setting, the same one the bot uses. We also fixed two protection toggles that saved without having any effect.

    • securityThe RaidWatch toggle reverted to off after a refresh, so raid alerts did not work despite the save being confirmed. The setting now persists.
    • securityThe “Log protection actions” option was never read by the bot; it now actually records VenonSec actions in the logs.
    • newThe dashboard switches language with the server: an English server shows the dashboard in English, and moving to a Polish server switches it to Polish without reloading the page.
    • newThe security centre, moderation with Ticket CRM, onboarding with greetings, and engagement with levels and reputation are available in English.
    • newThe raid protection and content protection screens explain what each shield does and let you pick a channel from a list instead of typing an ID.
    • fixThe configuration change log showed the HTTP request body with field names and raw IDs; it now describes the change in terms an administrator understands.
    • improvementThe dictionary check catches missing keys, variables lost in translation and leftover Polish in the English version.
  8. new · 2fix · 3

    Incidents described in plain sentences, and a server language that no longer resets

    The security incident history explains what happened instead of showing codes, and the chosen server language no longer reverts to Polish.

    • newThe incident history describes events in sentences — what happened and whether action is needed — instead of showing levels, codes and raw JSON.
    • newProtection screens describe the effect of their settings in words and let you choose channels from a list.
    • fixThe VenonSec panel overwrote the server language with Polish on every visit; a chosen English setting is now kept.
    • fixHighlighted messages on the starboard showed translation key names instead of text.
    • fixAn unusual response from the data layer crashed the incident history with a 500 error; the screen now handles it.
  9. new · 3fix · 1

    Human-readable incident alerts and the first screens in English

    Security incident alerts describe the situation in a sentence, and the slash commands, the role panel, the starboard and the language switch have English versions.

    • newThe security incident alert describes what is happening in a sentence instead of a string of codes and counters.
    • newSlash commands have English names, descriptions and options for Discord clients set to English.
    • newThe role panel, the starboard and the server language switch work in English.
    • fixThe incident timeline showed a wall of validation errors instead of data because it did not recognise the signal types the bot uses.
  10. fix · 3

    Publishing the role panel without cryptic errors

    Publishing the role panel could end in a 500 error or reject valid roles. Administrators now get a specific reason, and it stays on the screen.

    • fixPublishing and repairing the role panel ended in a 500 error without naming a field or category; the save now goes through, or the message says what to fix.
    • fixValidation rejected roles missing from the bot's cache, including freshly created ones; roles are now checked directly on the server.
    • fixA refusal with instructions, such as “move the bot's role above Admin”, disappeared with a short notification; it now stays on the screen.
  11. new · 5fix · 3improvement · 1

    Daily challenges, attendance streaks and a new module page

    Every counter previously measured volume: messages, minutes or points. They all rewarded the same people — those who were already the most active.

    • newAttendance streaks count consecutive days spent on the server, treating messages and voice activity equally. Four milestones, at 7, 30, 100 and 365 days, can be announced in a chosen channel. Personal records remain on the profile after a streak ends.
    • newThe challenges command offers three daily tasks shared by the whole server, with progress bars and an XP reward claimed by clicking. Progress uses today’s recorded activity instead of separate counters that could drift out of sync.
    • newThe leaderboard command now includes the longest active streaks. Broken streaks leave the ranking, while personal records remain on profiles.
    • newThe Streaks tab in the Engagement centre includes an announcement toggle, channel and minimum milestone. The streak counter itself always runs and needs no configuration.
    • newA module page explains both features, their defaults, limitations and frequently asked questions. It is available from the Features menu.
    • fixVoice activity previously did not count towards streaks, preventing voice-only members from building one. Streaks were also disabled with leveling, even though they measure attendance rather than points.
    • fixCommand sync ended in a 504 error when there were many commands; it now runs in the background and the dashboard waits for the result instead of reporting a failure.
    • fixEvery visit to the dashboard sent a malformed background request that ended in a 404 error.
    • improvementAll bot embeds share one colour palette, put the title in the title field and carry the bot version in the footer.
  12. new · 3fix · 2

    Customisable profile cards and visual FACEIT statistics

    Profiles previously showed everyone the same sections in the same order. Owners can now choose which sections appear, their order and their colours.

    • newProfile cards now have sections for roles and server support, levels, reputation, FACEIT, links and dates. Levels show overall progress with leaderboard position, activity tracks and minigame results separately; minigame results were previously missing.
    • newThe Card appearance button lets members choose colours, visible sections and their order. Preferences are saved separately for each server, reflecting each server’s different achievements.
    • newFACEIT CS2 statistics are rendered as graphics: rating with progress towards the next level, wins, kill/death ratio and headshots. Reference markers on the bars put the figures in context.
    • fixProfile banners previously disappeared after every bot restart because they existed only in memory. They are now stored persistently.
    • fixBirthdays entered with dots, such as a shortened 20 November date, appeared on cards as raw input instead of a readable date.
  13. new · 4fix · 1improvement · 2

    Monthly podium trophies, weekly leaderboard announcements and a new board

    Weekly rankings used to disappear from memory by Monday. Monthly podium trophies now remain permanently on profiles and can be counted.

    • newOn the first day of each month, the bot awards trophies to the previous month’s top three members. Profiles and public leaderboard names show the trophies and the number earned for each place.
    • newWeekly podium announcements can be sent to a chosen channel and are disabled by default. They name the top three members without pinging anyone.
    • newThe public board shows movement since the previous week. First-time entries are marked as new rather than unchanged.
    • newA link containing a member’s identifier highlights their position and remembers it for later visits. The board has no login, so this provides a way to identify the reader’s row.
    • fixThe backup restore command silently stopped restoring roles after the scope selector changed. It reported success even though the roles were not restored.
    • improvementThe leaderboard gained ranks relative to the leader, a server summary and the number of points needed to overtake the person above.
    • improvementProfile cards now give level progress its own place as the figure that changes daily. Previously, reputation appeared twice and trophies three times.
  14. new · 3fix · 1improvement · 2

    Emoji preservation, editable role panels and backups with scope selection

    Emoji entered in the dashboard disappeared on save, including in role names, categories and messages. The cause was text sanitisation before database writes.

    • newBackups are now one feature with a scope selector: bot settings alone or settings with the server’s channels and roles. The dashboard explains each scope and what restoring it will do.
    • newSelf-service role panels can now edit saved roles: emoji, name, description, order and message colour. A preview shows the result before posting.
    • newWelcome messages can link to a rules channel on the server, as well as an external website. Not every community hosts its rules outside Discord.
    • fixDatabase sanitisation was removing parts of the character pairs used by most emoji. This affected every saved text field, not just role panels.
    • improvementRole selection messages now use columns, category colours and a server thumbnail instead of a plain grey list.
    • improvementThe dashboard sidebar now shows the server icon and a custom caption editable in settings.
  15. new · 1fix · 4improvement · 1

    Thirty-two seasonal welcomes, memory diagnostics and account protection fixes

    New members previously received one fixed welcome message. The bot now offers seasonal and occasion-specific templates, with a dashboard gallery.

    • newThere are 32 seasonal welcome templates, eight per season, covering occasions such as holidays and the start of the school year. The dashboard gallery provides previews and lets administrators pin a template.
    • fixSix templates never appeared because long occasions occupied the entire period instead of joining the selection pool. A full-year audit also found an occasion lasting 69 days.
    • fixTemplate selection used the host’s time zone instead of the server’s. On a UTC host, Polish occasions began late.
    • fixWelcome test messages reported success even when nothing was sent. They now explain what prevented delivery.
    • fixAccount details in the anti-fake module failed to open, and unique-join history showed incomplete data.
    • improvementThe dashboard Health centre now shows memory usage, the limit and a cache breakdown by servers, channels and members.
  16. fix · 2improvement · 2

    Reputation settings save again and module panels explain their features

    Reputation settings showed an error and could not be saved through the website. The dependency tree was also reviewed.

    • fixThe reputation panel displayed an error and prevented saving, making the module impossible to configure from the website.
    • fixThe browser tab showed the original template’s default icon instead of Venon’s logo.
    • improvementModule panels now explain what each module does and requires, alongside their settings.
    • improvementUnused dependencies, external assets and obsolete documentation code were removed after checking that nothing relied on them. The dependency security audit reports zero vulnerabilities.
  17. fix · 1improvement · 1

    The Add bot button now adds the bot

    The website’s primary button opened the support server invite instead of bot installation, taking people who wanted to add Venon to the wrong place.

    • fixThe homepage Add bot button led to the support server invite instead of installing the bot on the visitor’s own server.
    • improvementRemoved 21 unreferenced source files and temporary artefacts left in the repository.
  18. new · 2fix · 1

    A welcome after installation, level progress reset and safer settings

    After adding Venon, administrators received no guidance about where to start or configure the bot. The bot now welcomes them and links to the dashboard.

    • newAfter installation, administrators receive a message explaining how to configure the bot through the website.
    • newThe leveling panel can erase all progress on a server. It requires a reason and explicit confirmation because the action cannot be undone.
    • fixThe dashboard no longer silently substitutes defaults when a backend field is missing. Previously, missing data looked like a disabled setting, and saving could overwrite configuration with zeros.
  19. improvement · 1

    Consistent commands that match the dashboard

    Commands built at different times used different layouts and error handling, and some lacked translations. They now follow the same conventions as the dashboard.

    • improvementThirty-seven commands now share consistent reply layouts and error handling, with complete Polish and English translations.
  20. security · 1fix · 4improvement · 1

    Correct installation permissions and clearer service status

    Reviewing the production install link revealed a missing scope required for commands — the same problem already described in the site’s FAQ.

    • securityThe install link requested 14 unused permissions, including permission to mention everyone, which the protection module itself flags as higher risk. The requested scope now matches the bot’s actual operations.
    • fixThe install link lacked the scope needed to register commands. The bot could join a server without any commands appearing, exactly as described in the first FAQ entry.
    • fixTwenty-two retired command URLs returned empty pages instead of permanent redirects. Redirects were also shortened from two hops to one.
    • fixWhen data was unavailable, the status page showed a technical fetch error instead of explaining what was unavailable and why.
    • fixDisabling the dashboard in bot configuration gave no visible explanation: the bot kept running while the status page had no data.
    • improvementThe website stopped showing unfinished-field markers, and the dashboard preview now presents eight actual screens instead of a single screenshot.
  21. fix · 1improvement · 3

    Temporary voice channels keep working and the server catalogue is complete

    The voice room generator stopped creating channels after a while. Each room created its own category until Discord’s limit was exhausted.

    • fixAll temporary rooms can now use one chosen category. Previously, each room created a category, and Discord allows only 50 per server. Reaching that limit stopped the generator without an explanation.
    • improvementThe temporary channel panel explains the module, shows the generator state and presents cleanup periods in readable terms.
    • improvementThe server catalogue shows communities using the bot with their logos, names and member counts, without server invites or links.
    • improvementUnavailable member counts are labelled explicitly instead of being shown as zero.
  22. security · 1new · 2fix · 2improvement · 2

    Six-hour bot restarts fixed and complete website navigation

    The day’s most serious issue appeared in no log: a failed database maintenance task shut down the entire bot every six hours.

    • securityA failed automatic database backup could terminate the bot. Maintenance failures are now logged without stopping the service.
    • newNavigation now covers the whole site. Around 20 pages, including modules, guides, the Trust Center, demo and changelog, were previously unreachable from the menu.
    • newTen step-by-step guides cover raid protection, AutoMod, verification, phishing, spam, tickets, roles after verification, moderation logs and preparing for attacks.
    • fixThe bot’s memory limit was restored. An earlier change had lowered it below actual requirements, risking restarts.
    • fixDatabase repair tools appeared to work but did not: one failed to read configuration, while another refused backups exactly when they were most needed.
    • improvementEight module pages explain how protection works, how to enable it and what it does not cover.
    • improvementFailed database integrity checks now include ready-to-run repair commands, starting with non-destructive options.
  23. security · 2new · 4fix · 2improvement · 2

    The Trust Center and separate public and dashboard layouts

    Legal documents now describe retention, data categories and MSIoU scope based on the implementation. The landing site and dashboard use separate layouts.

    • securitySession context now covers authenticated screens only. Anonymous homepage visits no longer query the API for identity.
    • securityQuoted message content in moderation logs can no longer trigger mass notifications.
    • newThe Trust Center documents data categories, retention periods, subprocessors, safeguards and vulnerability reporting.
    • newThe privacy policy explains the cross-server MSIoU dossier, reciprocity, opt-out and the consent-based passport.
    • newAccess, rectification and erasure request procedures are documented with their review statuses.
    • newA demonstration page shows the path from a server join to an incident and recovery using fictional data.
    • fixDashboard module links open the intended tab, including timeouts, logs, contests, birthdays, quotes and games.
    • fixTab lists scroll on narrow screens, keeping later tabs reachable on mobile.
    • improvementThe Skip to content link bypasses navigation, and closed mobile menus leave the keyboard tab order.
    • improvementFields requiring service owner information are marked explicitly instead of filled with sample details.
  24. security · 2new · 1fix · 1

    Server boundaries in the MSIoU network

    Access to one server previously allowed reading data across the network. Reciprocity is now required.

    • securityDossiers read only from servers that publish to the network, and only when the requesting server has receiving enabled.
    • securityA policy read failure restricts access to the current server instead of expanding access.
    • newA public list shows communities using the bot with logos and member counts.
    • fixRemoved dashboard actions that reported success without making any server-side change.
  25. new · 3fix · 3improvement · 1

    MSIoU dossiers show a clear lookup flow

    Lookup results now show the process and network trace instead of a flat list of figures.

    • newDossiers open in a separate window with a constellation-style network trace.
    • newThe dashboard now includes settings for level-up announcements.
    • newThe public website has a voice leaderboard podium linked from the dashboard.
    • fixHourly statistics reads and writes diverged between local midnight and UTC midnight.
    • fixAccount cards displayed raw “undefined” and “Invalid Date” values.
    • fixSaving was repaired across three screens that errored and two forms that saved nothing.
    • improvementChannels and roles can be selected from lists instead of requiring pasted identifiers.
  26. new · 3fix · 1improvement · 1

    Dashboard 3.0 — complete feature parity

    Dashboard 3.0 supports all modules. The previous version has been retired.

    • newAll modules are available in the new dashboard with shared layouts and navigation.
    • newRhythm and Autopilot let the server respond to its own activity patterns.
    • newThe level-up card editor configures backgrounds, colours and layout in the dashboard, with a preview before saving.
    • fixFour dashboard screens failed in the browser.
    • improvementHourly activity now uses one source instead of two diverging aggregations.