Snapshots

📋 Summary

In this snapshot we present a major structural update of Firefighter, focused on reorganising the internal systems, expanding the administration tools and adding new customisation features.

The main changes include the implementation of a system to enable and disable features individually, the full restructuring of the economy system to allow independent settings per server, the addition of mass moderation tools and the development of auto-reply, badge and invite systems.

We also made changes to the default configuration of the modules, to command handling and to the user experience, with the aim of giving servers more administrative control, flexibility and stability.

✨ New features

• Feature enable/disable system: a centralised system was added that lets you manage the bot's features individually through >>funciones and /funciones. Each module can be enabled or disabled according to the server's needs.
• Moderation through mass role assignment: two new administrative commands were added that let you assign or remove roles for multiple members at once, simplifying server management tasks.
• Auto-reply and auto-reaction system: a fully configurable module was implemented that lets you set automatic replies and reactions to certain messages. Support for mentions of users and roles was added to widen the customisation options.
• Badge creator: a fully configurable badge generation system was added. Dynamic variables and support for customisable webhooks were included to adapt the content and presentation of the generated messages.
• Independent economy per server: a new economic architecture was developed that keeps balances, currencies and settings independent for each server. The system includes the following modules:
  • Economy management: balance, work, daily, crime, slut, rob, collect, deposit, withdraw, give-money, leaderboard and cooldowns.
  • Shop and inventory system: store, buy, sell, use, inventory and item, the latter intended for managing and creating custom items.
  • Casino system: blackjack, roulette, slots, coinflip and russian-roulette.
  • Economy administration: add-money, remove-money, reset-money and economy-settings, which includes a total of 25 configuration parameters.
• Invite tracking system: a module was added that can identify which invite each member used to join the server. It includes the following commands:
  • invites: view invite statistics.
  • inviter: identify the user who made the invitation.
  • invited: view invited members.
  • invite-leaderboard: invite leaderboard.
  • invite-bonus: management of additional rewards.
  • invite-reset: reset statistics.
  • invite-config: general configuration of the system.
  It also includes notifications in specific channels, detection of suspicious or fake accounts and role assignment as a reward.

⚙️ Improvements

• General feature configuration: the default behaviour of the modules was changed. All features are now disabled by default, except for the Anti-Raid system. This change does not affect servers that had already configured their automatic systems, whose existing settings are kept.
• Persistence of previous settings: the configuration previously set by each server is kept to avoid unintended changes to systems that were already running.
• Handling of disabled commands: when a module is disabled, its commands tell the user that the feature is not enabled on that server.
• Daily missions system: daily missions now stay disabled by default and each administrator can enable them individually. Servers that already used this feature keep their previous configuration.
• Custom banner in the help system: the >>help and /help commands now show the Firefighter image at the top of the help interface, improving the bot's visual identification.
• Support for mentions as a prefix: command recognition through a direct mention of the bot was extended. Any command can now be run using @Firefighter as a prefix, regardless of how many spaces are typed between the mention and the command.
• Economy system restructuring: the internal economy architecture was reorganised to guarantee the separation of data and settings between servers, preventing balances and economic parameters from being shared between different communities.
• Crime system customisation: /crime was expanded with ten different modes, including options related to hacking and espionage. Each mode has random reward ranges and different risk levels.
• Update of documentation and internal references: the references to the «Arcane» and «UnbelievaBoat» styles were removed from both the help messages and the source code comments.

🐛 Fixes

• Restriction of commands by direct message: access to the backup and template commands was changed, and they are no longer available through direct messages (DMs). They must be used from the enabled contexts within Discord.
• Recognition of mentions as a prefix: the command detection system was extended to support mentions of the bot with different separations and spaces.
• Handling of disabled features: an informative reply was added so that users do not interpret the lack of response from commands belonging to disabled modules as an error.

🛡️ Security and moderation

• Anti-Raid enabled by default: the Anti-Raid system is kept as the only feature enabled initially, preserving an active layer of protection from the moment the bot is added to the server.
• Individual configuration per server: administrators can control which modules remain available, reducing the exposure of unnecessary features and allowing the bot's behaviour to be adapted to each community's policies.
• Invite detection and tracking: an invite identification system was added that lets you track how members join the server, view statistics and detect patterns associated with suspicious accounts.
• Mass role management: administrative tools were added to make it easier to assign and remove roles for multiple members.
• Restricted access to administrative functions: economy configuration and invite management operations are kept within their respective administrative modules.

🧪 Features in testing

• Independent economy system: the new economic architecture is being validated, especially the separation of data between servers, inventory management, transactions and configuration parameters.
• Invite system: we need to validate the accuracy of invite tracking, the detection of suspicious accounts, the notifications and the automatic assignment of rewards.
• Auto-replies and auto-reactions: we need to check the different trigger conditions, compatibility with mentions and the correct operation of custom configurations.
• Badge creator: the processing of dynamic variables, message generation and sending through custom webhooks are under testing.
• Module activation system: we need to verify how commands behave when features are disabled, as well as the persistence of individual settings.

💬 Community feedback

We want to hear your opinion on the changes presented in this snapshot. Community participation is essential to identify problems, evaluate how the new tools work and set development priorities.

You can share:

• Errors or unexpected behaviour.
• Suggestions to improve the features that were added.
• Ideas for future updates.
• Usability problems or settings you consider necessary.
• Incompatibilities found during testing.

📩 Feedback channel: the reports and suggestions channel of FireFighter's official support server.

🚀 Next steps

• Full validation of the new modules: run functional and compatibility tests on the economy, invite, auto-reply and badge systems.
• Economy system optimisation: verify transactions, inventories, cooldowns and the independence of data between servers.
• Invite system review: check the accuracy of member tracking, the rewards and the mechanisms for detecting suspicious accounts.
• Feature system stabilisation: keep verifying the individual enabling and disabling of modules, ensuring that existing configurations are preserved.
• Slash command sync: the new application commands require restarting the bot or running >>sync to update their registration and availability on Discord.
• Review of prefix settings: a behaviour related to prefix recognition on certain servers is still pending a fix. As a workaround, administrators can run @Firefighter setprefix reset to restore the default prefix >>.

📋 Summary

In this snapshot we present a series of advances and changes made during the development of FireFighter. This update introduces new features, optimisations to existing systems and fixes aimed at improving stability, customisation and the overall server administration experience.

The main highlights are the implementation of the daily missions system, the expanded capabilities of the backup system (Backups), the addition of role management tools and per-server customisation of the command prefix.

The purpose of this publication is to document the progress made, share the new features with the community and gather feedback that helps identify possible improvements before the final release.

✨ New features

• Daily missions system: a complete missions system was implemented to encourage participation and activity among members within each server. Its main features include:
  • Generation of 3 daily missions randomly selected from a catalogue of 13 available missions.
  • Automatic tracking of mission progress.
  • Reward system using Fire_coin and XP.
  • Streak system with shield protection.
  • Private notifications through direct messages (DMs).
  • Addition of the /misiones and >>misiones commands, with the following options: reclamar, avisos, catalogo, config and stats.
  • Independent configuration for each server.
  The system was also integrated into the /help section and into the data-deletion procedure triggered when the bot leaves a server.
• Role creation command (rolcreate): a role creation tool was added through the >>rolcreate and /rolcreate commands. It lets you configure the following parameters:
  • Role name.
  • Custom colour.
  • Separate display in the member list.
  • Role mention permission.
  For security and administrative control, running it requires the Manage Roles permission.
• Per-server prefix customisation (>>setprefix): it is now possible to set an independent command prefix for each server. The configuration is stored in the database and persists over time. The >>setprefix reset option was also added, which restores the default prefix. The bot's messages and replies take into account the prefix configured in each server.

⚙️ Improvements

• Backup system (Backups): the information-capture mechanism was expanded when generating server templates. A more complete representation of the server's structure and configuration is now covered, including:
  • General information: name, description, icons and other compatible data.
  • Roles: configuration and properties of the roles.
  • Text and voice channels.
  • Categories and channel organisation.
  • Permissions associated with the different elements.
  The restoration process was also expanded to support two modes: replacing the existing configuration or adding the template's elements on top of the server's current structure. The goal of this change is to achieve restorations that are more faithful to the template's original configuration.
• AFK system: the behaviour of the automatic messages related to AFK statuses was optimised, adding time-based handling of notices to avoid unnecessary accumulation of messages in channels.

🐛 Fixes

• AFK system messages: fixed the information shown in the return summary. Previously, the message stated that the user's roles had been reassigned even when no reassignment had taken place. It now avoids reporting actions that did not happen.
• AFK notifications: the behaviour of temporary messages was adjusted so that notices are deleted according to the established times.

🛡️ Security and moderation

• Permission control in role creation: a validation of the Manage Roles administrative permission was added to restrict running rolcreate to authorised users.
• Independent configuration per server: the prefix system and the daily missions settings are managed independently for each server, preventing changes made in one community from affecting others.
• Data management per server: the daily missions system was integrated into the data-deletion procedure used when FireFighter leaves a server, covering the cleanup of the corresponding information.

🧪 Features in testing

• Backup system: template generation and restoration were tested using simulated servers. The information-capture mechanisms and the restoration modes were verified. However, no functional tests have yet been carried out on real Discord servers.
• Daily missions system: the complete system was implemented and tests were run on generation, tracking, rewards, streaks and settings.
• Slash commands: the new /misiones and /rolcreate commands require a command sync to appear and be available. This can be done by restarting the bot or by using >>sync.

💬 Community feedback

We want to hear your opinion on the changes presented in this publication. Community participation is essential to identify problems, assess the usefulness of the new tools and set priorities for future updates.

You can share:

• Errors or unexpected behaviour.
• Suggestions to improve the features that were added.
• Ideas for future updates.
• Usability problems or settings you consider necessary.
• Results of tests carried out on real servers.

📩 Feedback channel: the Tickets channel on our Discord server.

🚀 Next steps

• Validation in real environments: run functional tests of the new features directly on Discord servers, checking their behaviour and compatibility.
• Backup system optimisation: keep evaluating the fidelity of templates and restoration processes, identifying possible limitations or inconsistencies.
• Security review: review pending security and credential-management matters.
• Message fixes: fix the corrupted character detected in the message of the /backup command.
• General stability: keep running integration and compatibility tests between the new systems and FireFighter's existing features.

📋 Summary

In this snapshot we present the recent progress in Firefighter's development since our last publication, on 22/10/2026.

During this period new systems and features were added, structural changes were made in several modules of the bot, and various internal processes were optimised, related to stability, performance, resource management and communication with external services.

We also worked on expanding the translation system, adding diagnostic tools and implementing additional administration and data-retention mechanisms.

The goal of this publication is to share the project's technical progress with the community, document the changes made and gather feedback that lets us keep improving our systems before their final release.

✨ New features

• AFK system: a per-server away system was added, available through the commands >>afk [razón] and /afk. It lets you set a custom away status, notifying with embeds when other users mention or reply to the absent user. It also records the elapsed time and the mentions received, and automatically restores the original nickname when AFK is turned off. It includes the subcommands >>afk lista and >>afk quitar.
• Diagnostic system (>>diagnostico / >>diag): a technical diagnostic tool was developed, exclusive to the bot's creators. It checks the state of different components, including connectivity, resource usage, database, prefix and slash commands, extensions, scheduled tasks, help system, permissions, external APIs, recent errors and translation services. It includes an option to repeat the checks and a quick diagnostic mode.
• Translation by reactions: a feature was added that translates messages through reactions with international flags. The system automatically detects the original language and replies with embeds containing the translated content. It currently supports 37 languages and 66 flags, with support for messages of up to 12,000 characters, split across several numbered embeds when needed. It also includes configuration and lookup tools through >>traducir on, >>traducir off, >>traducir idiomas, >>traducir probar and >>traducir ultimos.

⚙️ Improvements

• ServerStats optimisation: the counter update mechanism was changed to avoid unnecessary requests to the Discord API. It now checks whether a channel already has the right name before making changes. In addition, a five-minute wait window was implemented for recently modified channels, reducing consecutive requests and possible HTTP 429, 503 and 504 responses.
• Data management and retention: a daily maintenance task was added that automatically deletes stored information older than 90 days. This process covers deleting the text content of messages logged by the Honeypot system and purging data belonging to servers that removed the bot and did not add it back during that period. The cleanup covers both the local database and the backend hosted on Railway, with automatic retries when the external service does not respond. Global blacklists, the bot's removal history, Patreon and backups are excluded from this procedure.
• Levels system: the aliases of the level-related commands were reorganised, freeing identifiers previously used by the minigames. This makes it possible to tell apart the experience earned through games, which now belongs to the global profile, from each server's individual level system.
• Multitasker system: an additional check was added to confirm that the server has the system enabled before allowing its use through direct messages. This restriction does not apply to the bot's creators.
• Patreon synchronisation: the periodic synchronisation mechanism was improved so that an error during one run no longer permanently interrupts the following checks. Errors are now logged and the process keeps running in later cycles.
• Database management: automatic retry mechanisms were implemented for transient errors related to opening files and SQLite locks, including situations such as unable to open database file and database is locked.
• Internal log system: the runtime-environment monitoring mechanisms were expanded. An alert is now logged when open-file usage exceeds 80 % of the limit set by the host. Error classification was also improved to avoid logging certain HTTP 429 errors from Google's free translation service as internal incidents.
• Diagnostic system: the available checks were expanded, adding new indicators for open files, Patreon synchronisation and availability of the free translator. Communication with external services was also optimised by using HTTP headers compatible with browser requests. Optional services that are not configured, such as Patreon, are now correctly identified as such instead of being shown as errors.
• Shutdown handling: handling was added for SIGTERM signals sent by hosting environments. This allows shutdown and restart processes to be managed correctly, preventing these operations from being classified as unexpected closures.

🐛 Fixes

• Translation by reactions: fixed the incorrect detection of messages that were supposedly already in the requested language. Previously, certain short texts could cause false positives. Validation is now done by comparing the translation result with the original content. The corresponding notices last 20 seconds.
• Reaction rate limit: the wait interval between translations was reduced from four seconds to 1.5 seconds. In addition, the restriction is now applied to each message individually, preventing one translation from needlessly interfering with others.
• Translation log: the output of >>traducir ultimos was improved, letting you check the result of each processed reaction and making it easier to identify possible issues.
• Translator error handling: temporary notices were added for when a translation cannot be completed. These messages show the reason for the failure for 30 seconds and keep the corresponding entry in the internal logs.
• ServerStats system: error handling was isolated per server so that an individual incident does not interrupt the whole run of the scheduled tasks. Additional information about the host's state was also added, including open files, number of threads and the status of the data.db file.
• File integrity: a character-encoding problem was identified in a message of the /backup system, causing text to be displayed incorrectly. Its fix is pending validation.

🛡️ Security and moderation

• Data retention and protection: an automated mechanism was implemented to purge information older than 90 days, covering the Honeypot system's logs and the data associated with servers that no longer have the bot added. Specific exclusions were set to preserve global information, administrative histories and backups.
• Host resource monitoring: internal alerts were added to detect high open-file usage, making it possible to identify potential limits of the hosting environment in advance.
• Validation of enabled systems: the access checks to the Multitasker system through direct messages were strengthened, first verifying that the corresponding server has the feature enabled.
• Infrastructure error handling: recovery mechanisms were added for transient database locks and failures of external services, reducing the chance of prolonged interruptions.

🧪 Features in testing

• Translation by reactions: we are still verifying the behaviour of the 66 available flags and compatibility with the different languages. We still need to confirm the cause of an issue in which certain reactions did not respond correctly, initially observing that it worked only with the Russian flag.
• Diagnostic system: we are still validating the accuracy of the results from the infrastructure, external service, scheduled task and internal component checks.
• AFK system: we still need to check its behaviour in different server scenarios, mentions, replies and nickname restoration.
• Maintenance and retention mechanisms: the data-deletion and external-backend synchronisation processes remain under monitoring, especially during temporary connectivity interruptions.

💬 Community feedback

We want to hear your opinion on the changes presented and receive suggestions that help us keep improving Firefighter.

You can share:

• Errors or unexpected behaviour.
• Suggestions to improve the features that were added.
• Ideas for future updates.
• Usability problems or settings you consider necessary.
• Experiences and observations related to the new systems.

📩 Feedback channel: the Tickets channel on our Discord server.

🚀 Next steps

• Validation in real environments: keep testing the new features on Discord servers to verify their behaviour outside local simulation environments.
• Translation system: investigate and fix the pending issues related to the processing of certain reactions and improve the stability of the translation methods.
• AFK system: complete the functional and compatibility validations with the different server configurations.
• Diagnostics and monitoring: keep expanding the diagnostic tools and the resource and infrastructure monitoring mechanisms.
• Internal optimisation: keep refining the database processes, synchronisation with external services and management of scheduled tasks.
• Integrity and maintenance: review the files affected by encoding problems and keep verifying the automated data-retention mechanisms.

📋 Summary

In this snapshot we present a series of structural and functional changes in Firefighter's development. The changes include a restructuring of the moderation system, expanded logging and auditing mechanisms, new administrative tools and the implementation of restricted-access commands.

We also made fixes to the log configuration and permission management systems, along with internal adjustments aimed at improving error traceability and problem diagnosis while the bot is running.

On 22 October we informed you about the security incident at Railway, our backend hosting provider. We completed our response that same day: all affected credentials have been regenerated and services are running normally. In this snapshot we explain what we did, step by step. You can read the full incident report.

✨ New features

• Moderation commands restructured: the individual commands >>ban, >>kick, >>mute, >>banid, >>kickid, >>timeoutid, >>multiban, >>multikick and >>multitimeout have been replaced by a new implementation of >>ban, >>kick and >>mute. The commands let you act on one or several users through their IDs, centralising moderation operations and making them simpler to use.
• Backups and templates with the classic prefix: the backup and template systems can now be used through commands with the >> prefix. A dedicated category for these features has also been added to the /help and >>help help systems.
• Honeypot system: we added >>honeypot with subcommands to manage this feature. The system provides a trap channel that logs the activity of users who post messages in it, making it easier to spot suspicious behaviour and analyse potential threats.
• Mentions as a prefix: Firefighter can now recognise direct mentions of the bot as a way to invoke commands, in addition to the classic >> prefix. The mention is kept as an additional trigger, without adding the /comando command format followed by a mention.
• >>botlogs: a new internal command, restricted to the bot's creators, for viewing Firefighter's technical and operational logs.
• /ownerhelp: a help system exclusive to the creators, listing internal administrative commands, development tools and features not available in the public help.
• New exclusive slash commands: the following commands were added with access restricted by user ID:
  • /hollowknight: available exclusively to users 840715759512322088 and 1452642596986814688.
  • /golpes: includes 16 types of hits with GIFs. Its use is restricted to users 840715759512322088 and 1487143857744380074.
  • /peleas: includes 16 types of fights with GIFs and uses the same access restrictions as /golpes.
• GIF management for interactive commands: tools were added to manage the media linked to actions:
  • gif_agregar: adds GIFs.
  • gif_twitter: manages GIFs from Twitter.
  • gif_quitar: removes GIFs.
  • gif_lista: lists the registered GIFs.
  • accion: manages or runs the available actions, depending on the system's implementation.

⚙️ Improvements

• Centralised log system: log classification has been reorganised to make logs easier to view, manage and analyse. The new categories are:
  • Security and antiraid protection.
  • Moderation.
  • Member activity.
  • Server events and changes.
  • Economy.
  • Sanction history.
• Deleted and edited message logging: the information collected by the log system now includes the content of the deleted message. This provides more context when reviewing incidents and auditing activity.
• Internal development logs: the technical instrumentation available to the bot's creators has been expanded. The logs cover Python errors, failed commands, permission and intent problems, API failures, reconnections, restarts, cog events, latency, memory usage and blocked tasks.
• Help system organisation: dedicated categories were added for backup and template features, improving how available commands are classified and making them easier to find from /help and >>help.
• Donations website updated: the >>donar command now points to the new official domain: https://firefighterbot.xyz/.

🐛 Fixes

• Log system configuration: fixed an issue in >>logs #canal where the channel was saved correctly but the command kept showing the status «Not configured». The reported status now matches the saved configuration.
• Permission restore with >>unlock: permission handling was fixed so that unlocking a channel previously locked with >>lock restores the original @everyone permission. Previously, the command explicitly set the permission to allowed instead of restoring its previous state.
• Internal dependencies and imports: added the missing imports of collections, contextvars, threading, traceback and yarl, required by the modules that depend on them and to avoid errors caused by unimported references.
• Command and mention resolution: reverted the implementation that combined the /comando format with a mention. Only the direct mention is kept as an additional way to invoke commands, alongside the classic >> prefix.

🛡️ Security and moderation

• Discord permissions updated: the permissions required by Firefighter were changed to support the new log system. For this reason, you need to invite the bot to your server again to apply the updated permissions. We recommend reviewing the granted permissions and keeping only those needed for the features you use.
• Activity logging and auditing: more information is now available on deleted and edited messages, along with the classification of security, moderation and member activity events. These logs make it easier to follow up on incidents and review administrative actions.
• Honeypot system: a trap channel was added to identify activity within a specific space on the server. Its effectiveness will depend on the configuration and the rules applied to the detected behaviour.
• Commands restricted by ID: the /hollowknight, /golpes and /peleas commands have specific lists of authorised users. These restrictions define who can use the corresponding features.
• Internal tools for creators: the >>botlogs and /ownerhelp commands keep internal diagnostic and administration tools separate from the general-use interface.

🔑 Security: credential rotation

Following Railway's recommendations, we revoked and replaced all the keys stored in its environment variables:

• Database: new access password and new connection string. The previous one is no longer valid.
• Support chat (Firebase): new service key. The previous key has been invalidated.
• Website sessions: new signing key. That is why you will need to log in again with Discord on the dashboard.
• Bot ↔ backend synchronisation: new shared secret, already applied on both sides.
• Admin panel: new access key for the team.
• Alert system: new webhook; the previous one has been deleted.
• Bot and Discord application: token and OAuth2 credentials regenerated.

✅ Service verification

We checked each one before closing the incident:

• Backend connection to the database ✔️
• Connection to the support chat ✔️
• Bot connected and synchronising with the dashboard ✔️
• Website status and statistics ✔️
• Login with Discord ✔️

🔍 Activity review

We reviewed the logs of the database, the support chat and the servers, and detected no unusual activity. We will keep monitoring them over the coming days.

🛡️ Measures we already had in place

Attack detection and logging, automatic blocking of repeat-offender IPs, real-time alerts to the team, end-to-end encryption in the support chat and rate limits. We will keep strengthening them as a result of this incident.

🙋 Do you need to do anything?

• Log in to the dashboard again if it asks you to.
• We will still never ask you for passwords or tokens by direct message. If someone does so on our behalf, it is a scam: tell a moderator.
• Railway deployments are available again, so website fixes will be published normally again.

🧪 Features in testing

• Centralised log system: we need to validate that logs are generated and classified correctly, that the configuration persists and how it behaves with deleted or edited messages.
• Internal development logs: we need to check that technical events are logged correctly, that errors are identifiable and that latency, memory, reconnection and blocked-task logs provide useful diagnostic information.
• Multiple moderation commands: we need to verify how several IDs are processed in a single operation, how invalid users are handled and the response to insufficient permissions or individual errors.
• Honeypot system: we need to check the trap channel configuration, message detection and the logging of the corresponding activity.
• GIF management: we need to validate adding, listing, removing and managing media, including the handling of invalid input.
• Restricted slash commands: we need to verify that ID restrictions are applied correctly and that unauthorised users cannot run the protected features.

💬 Community feedback

We want to hear your opinion on the changes presented and gather information that helps us detect problems before they make it into official Firefighter releases.

You can share:

• Errors or unexpected behaviour while using the new commands.
• Problems configuring, generating or viewing logs.
• Results of testing the moderation commands and the Honeypot system.
• Suggestions to improve how commands and help categories are organised.
• Problems related to the permissions required by the bot.
• Ideas for future features and usability improvements.

If you notice anything odd on the website or the dashboard (errors, data not loading, sessions failing), let us know through the support chat at https://firefighterbot.xyz/ or at support@firefighterbot.xyz.

📩 Feedback channel: the Tickets channel on our Discord server.

When reporting a bug, please include the command used, a description of what happened and the steps to reproduce it. Do not post tokens, credentials or other sensitive information in your reports.

🚀 Next steps

• Log system validation: check event classification, log consistency and how the different categories work.
• Moderation testing: verify single and multiple actions, including error cases and permission restrictions.
• Permission validation: check that the updated permissions are enough for the bot to work and that no unnecessary privileges are requested.
• Internal tools verification: test >>botlogs and /ownerhelp, including access restricted to the creators.
• Interactive command testing: validate ID restrictions and GIF management operations.
• Feedback collection: analyse community reports and prioritise the fixes needed for the next snapshots.
• Keep strengthening the protection measures of the backend and the website.
• Keep monitoring the logs over the coming days.
• Post updates here if anything changes.