Today I am pushing a lot of changes to Fire Beta that will soon be deployed to production. This changelog is going out early to allow users to provide feedback on these changes as they are quite major and I will not be surprised if there are users with negative opinions on the changes.
Edit - 20:12 UTC, August 24th - These changes have since been deployed to the main bot. If you have feedback you want to give, you can join the Fire Discord and leave it in the #fire-help channel or email it to [email protected] if you want to provide feedback privately
I have re-enabled the Discord experiment fetching in Aether and subsequently "fixed" showing guild experiments (this will also fix Advaith's Experiment Rollout site) I have also fixed a potential bypass for invite filtering.
After a bit of consideration, I have decided to rename the command rather than remove it due to how useful it can be f.ex for mobile users wanting to upload emojis
The command has been renamed from
emoji and now takes either an existing emoji, emoji URL, attachment URL or attached image when running the command.
Due to these changes, I had to swap the order of the arguments. The emoji name comes first and then the emoji/URL. I have tried my best to make it smart enough to figure out if you reversed them but it's not guaranteed to work. Please put the emoji name first and *then* the emoji.
The invite command no longer links to https://inv.wtf/bot but now has a button you can click to go directly to the invite. This change was made to allow for using In-App OAuth which (last time I checked) is available to 50% of users on desktop
It just didn't make sense to have something that only works for message commands, as a slash command...
autoquote command was used to toggle automatic quoting when a message link was found in a message.
This has now been replaced with a check for whether the
quote command is disabled. Disabling the quote command will now disable auto quoting.
A few commands (such as
delremind) have been updated to only use buttons rather than waiting for a message. You can no longer type
close to close a ticket or
yes to delete a reminder.
/tag list &
/tag view <tag> have been added to replicate functionality of the base tag command with slash commands as you cannot use
/tag like you can use
This is the more controversial part of this update... 32 commands in Fire (approximately 29% of all commands) are no longer usable via messages. Attempting to use these commands will prompt you to use slash commands instead. This change was made to encourage the use of slash commands amidst the upcoming message intent changes in April 2022. Fire will eventually be usable via slash commands only and this is the first step towards that. The decision to go slash commands only was already made before the whole message intent announcement but was pushed forward because of it. I understand that some of you may not like slash commands in their current state and I assure you there are improvements coming!
Today Discord has released
Context Menu Commands that allow bots to add actions to right-click menus on both users and messages (more will come) and Fire has full (hacky, but full) support for them!
Once you're on the latest version of the Discord desktop app (no mobile support for now), you should be able to right click users to see a
User option in the
Apps menu which you can use to get information about the user you right clicked (it's the same as doing
You can also right click messages and see two options,
Google It and
Remind Me with will run
/google <the message content> and
/remind <the message content> respectively, with a twist!
Remind Me option will give you a dropdown with predefined times for setting a reminder rather than you entering a time since this is all I can really do without a text input component.
$filterexcl command has been temporary disabled until I can get around to rewriting it as it seeming has many issues that were recently made apparent to me through its usage of incorrect strings. I have no clue when I will be able to rewrite it and re-enable it so I can't tell you when it will be back
All existing filter exclusions are still in effect. if anyone needs it to be changed, please join the Fire Discord and let me know in the #fire-help channel as I can manually edit it.
Fire is now using the i18n rewrite which means soon you should get more languages to choose from in the bot. I'd like to give a big thank you to everyone who has already contributed translations on Fire's Crowdin page (https://inv.wtf/i18n) and at the weekend I will be approving translations and adding them to the bot alongside giving flags and roles* One small downside of the i18n rewrite being deployed now is that I had to remove the owo "language" for now as I haven't had a chance to rework that yet. Any user/server that had been using owo will see it once it's readded, your configs haven't been changed. *Unfortunately I cannot give the 50% for Fire Premium yet as I can only do that once the new website has been launched
Fire is also using my own fork of Discord.JS which re-adds structures to prevent me having to basically rewrite Fire. This is not a permanent solution but it will do for now. I'm still trying to decide how I will approach rewriting Fire, whether it'll just be working around the lack of structures, using a different library or another full rewrite of Fire in a different language.
You can now snooze reminders! Too busy to handle a reminder the second you get it? Just click the blurple snooze button, pick a time from the dropdown and voilà, you will now be reminded at a later date! You can check out a demo video here
You can now help translate Fire into new languages by heading to https://crowdin.com/project/fire-discord-bot (shortlink: https://inv.wtf/i18n) This will help Fire be introduced to a wider range of communities. I've gone ahead and added ~30 languages to the list to be translated but if a language you want to translate isn't there, feel free to @ me and I'll get it added, same goes for if you have any questions e.g. how/where a certain string is used. To reward translators, anyone who contributes a decent amount of translations will get 50% off Fire Premium for a year and the flag for the language(s) you translated will appear next to your badges in the user command (and maybe a role here with a secret channel but I'm still unsure on whether I want to add to the already long list of roles lol) The code changes required to support the new i18n system haven't been merged yet so if one of y'all speedruns translating a language, it might be a week or two before it can be added to Fire so be patient One last thing, some strings will be ones you can take from Discord (e.g. permissions) so whenever possible please use any available Discord translations.
With the limited release of threads for bot developers (a.k.a anyone with <=5 members in a server, one of which must be a bot), I thought I should mention that Fire fully supports threads! Anyone taking advantage of the early access will see new logging events for threads and full support for quotes in/from** threads.
Thread Log Events*:
Thread Members Update
Running a message command in a thread Fire can see but is not a member off will cause Fire to try join the thread. If the thread is (somehow) archived or Fire is missing permissions (manage threads for private, view channels for public/announcement), it will not be able to join the thread and the command will not run. You will not receive any feedback if this happens. It is recommended to use slash commands in threads.
(No idea what ticket threads are? Check out this video I made showing them) As some of you may have heard, private threads have been locked behind a paywall (Boost Level 2 a.k.a $75/month) which has put that feature on pause for now. If this does not get reverted, one of two things will happen;
The code for it just gets deleted
It is available for select guilds, similar to the Minecraft logs feature
I really wanted to have this feature available for everyone on release but if it stays behind a paywall then I am unsure whether I want a public feature in Fire that requires boosts. Currently less than 50 of Fire's servers (roughly equivalent to 4% of the total servers it is in) have enough boosts to use private threads.
* Fire may need the Manage Threads permission to correctly log events from private threads, otherwise it may log creates/deletes as it is added/removed from a private thread ** Quoting from a thread will require you to be in the thread, even if it is a public/announcement thread.
Buttons are finally here!
Discord has just released the next addition to its interactions API, buttons! These allow bots to do a bunch of cool new things and in true Fire fashion, it already has support! (It's technically had support for weeks now lol)
You should start to see buttons replacing reactions in Fire, for example with any paginators. There's also buttons hanging around in a few commands to provide quick access to helpful features.
The best way to try out these brand spanking new clicky bois is with the
$tictactoe command. Find a friend and have fun playing against them in this classic game.
If you can't see buttons, make sure you update your client!
Discord seems to have fully rolled out per channel voice regions, and Fire now has support for them! It will now log changes to channel regions and display all regions in the
$guild command. It supports both normal voice channels and stage channels. Support for stage channels should also be available for voice channel roles.
Ever want to pin a message but you've hit Discord's limit of 50 pins in a channel? A good alternative to pins is a starboard, which you can now make with Fire!
With Fire you can setup a starboard channel, set the amount of stars required to be added to the starboard and premium users can even use a custom emoji!* Learn more about premium here.
/starboard to get started (get it? star-ted because star-board haha I'm hilarious)
*I am open to making custom starboard emojis available for non-premium users a little while after the release depending on some statistics and if it is requested enough.
Slash commands are finally out of beta! You should now see Fire's slash commands in all servers with the bot and new ones invited using https://inv.wtf/bot! Almost all of Fire's commands are available for use with slash commands and should function the exact same as message commands (aside from some reaction workarounds) Go ahead and hit / and start using the awesome slash commands Fire has to offer :D
Fire Beta is back online! 🎉
Unlike what I originally planned, it is running on the same VPS as the normal bot but has a separate database for everything and is starting from a completely clean slate.
It's prefix is
beta and has the same slash commands as the main bot. This bot will be used to test new & potentially breaking features in a production-like environment so do not expect the bot to be stable (but what you can expect is pretty similar uptime to normal Fire as I'll be using Fire#7414 solely for local testing from now on and Fire Beta will stay running on the VPS)
If you would like to invite Fire Beta, you can now use https://inv.wtf/betabot to invite it.
Any issues with Fire Beta should not go to #fire-help but rather https://inv.wtf/betabugreport
Permission roles allow you to set permissions for a role in a channel, run a command (in the channel with the permissions) and have them copied to all other channels, including new ones!
This is useful for roles such as a "No External Emojis" role that denies
Use External Emoji for those pesky users using NSFW emotes or a "Bad Memer" role that denies
Attach Files and
Embed Links for those who can't help but use their image perms to be disruptive.
Currently permission roles are limited to 1 permission role for non-premium servers and unlimited for premium servers, which you can learn more about here
Over the past little while I've been making a bunch of behind the scenes changes to improve existing features, reliability of the bot itself and working on the website rewrite (alongside amazing web devs, Bruno and Nystrex who have done pretty much all of the frontend work) which will include migration from Patreon to Stripe for Fire Premium. There's still a lot more behind the scenes changes coming which will make Fire even better than it already is (yes, it is indeed possible to make the best bot better 😂)
Yup, that's right, I have made Fire replace advaith's Slashtags bot!
I have enabled an experiment in a small number of guilds that gives access to the
tag slash command, allowing you to toggle slash command tags for that guild (and by providing a boolean, e.g.
$tag slash true you can change whether or not the tags will be ephemeral)
If your guild doesn't have access to slash command tags, don't fret, it will eventually be available to all guilds. I am doing a slow rollout because there's strict ratelimits on slash command stuff so I want to make sure hundreds of guilds aren't toggling slash command tags in a short period of time. If you'd like access, join the Fire Discord and let me know why you think your guild should have it in the #fire-help channel :)
Sometimes when creating a ticket, if a user managed to run the command multiple times in quick succession, they could open more tickets than the server's limit (especially if said limit is 1), causing one or more of those channels to not be considered tickets, meaning
$close would not work.
Creating tickets now uses a semaphore to ensure it is only being ran *insert server ticket limit* times or less at once, meaning these issues should cease to exist!
You can now have multiple prefixes! That's it, that's the changelog :D
"Ok, hear me out. Imagine the avatar command, but instead of showing a users avatar, it shows the guild's icon" thus the icon command was born! Wow, isn't that a great story?
You can now temporarily ban a user from your server. It's basically the mute command now except banning instead of muting (especially since the temp ban code is copied from mute lol)
$ban advaith#9121 too much blob 1 day
Sometimes the user command would say someone is banned on KSoft.Si when they're not. It no longer does this. Epic.
The guild command can now display info for public guilds, such as discoverable guilds or ones that have made their guild public with the
$anti command, you can now enable some basic message filters such as deleting messages with @everyone or @here if the user doesn't have permission to use them, messages from selfbots (users sending an embed) or "spoiler abuse"
You can now set a role that will be "alerted" (pinged) when a new ticket is opened, allowing you to f.ex. notify the staff team of a new ticket so they can have super fast response times.
You can set this the same way you set the rest of the ticket config options,
$ticket alert <role>
Another ticket related addition, any ticket where the author leaves after not saying anything at all in the ticket will now be closed automatically so people who open a ticket for no reason then leave won't waste your time.
Bots will now be ignored for join/leave messages (logs are unaffected) as they do not deserve to be welcomed smh
You can now ignore channels from logging with the
$logignore command so message edits/deletes, purges, link filter triggers etc. will not be logged from the channels you specify.
No more accidental leaks from your secret channel where you post only the spiciest of memes when you accidentally edited that one message
I'll let you figure this one out yourself. Long awaited suggestion from Noctember#6660 ;)
Previously locked to guilds with an experiment, I've just flipped the non-existent switch that enables both role update & nickname update logging for all guilds with member logs enabled. This may cause issues so if needed, the non-existent switch may be flipped again to disable them to prevent further issues.
Guilds with over 1,000 are no longer able to set multiple log types in the same channel. This is to prevent logs getting clogged up in large guilds due to the amount of logs being sent as Fire can only send 5 messages before it needs to wait a bit until it can send again. Attempting to set multiple log types in a single channel will return an error and existing large guilds with multiple log types in one channel will have those log types automatically disabled and a message sent in the log channel to explain why.
Discord has recently released the ability to use slash commands in a bot's DMs and Fire now fully supports them. I tried to prepare for this when it was announced but it still broke when it was released. If you spot any bugs with slash commands in DMs, feel free to open an issue on Fire's GitHub repo, https://inv.wtf/github
You can now "plonk" users from the bot in your guild! Just run
$plonk @User#1337 to prevent a user from running Fire commands. Run
$unplonk @User#1337 to allow them to use commands again.
Only took over a year but I have finally rewritten Fire's reaction roles and it is better than ever! You can check out the demo video I recorded during development here which basically showcases the feature as a whole in a short 30 second clip. This feature is premium only! You can learn more about premium here.
That's right, you can now use your favorite bot to generate beautiful images of your code using carbon.now.sh!
This feature was inspired by Ravy's bot Aero but is better because it has transparency and the ability to switch theme & font with flags
$carbon console.log("Hello, World") --theme nord --font firacode
Due to limitations with Akairo, the command framework Fire uses, you can't have spaces in the flag values (but it fuzzy matches so it's fine)
You can now set ticket descriptions! These will be shown in the embed sent in new ticket channels, allowing you to give a message to a user (e.g. telling them what info they should provide)
$ticket description <description> to set the description or
$ticket description to reset it
You can now use Fire to send embeds since users cannot. This command works by taking an embed object from a haste service (hastebin.com, hasteb.in or hst.sh) and send it to the current channel or any other channel!
$embed https://hst.sh/kaxesebivo.json #testing
You must have Embed Links permission to run the command and Manage Messages in a channel to send to it from a different channel.
That's right, it only took a year since it was suggested but Fire now has a color command!
Don't worry, if your language is set to en-GB it will say colour.
$color [<color>] to quickly convert colors to different types (hex, rgb, hsl or hsv) and get a preview of that color!
If you don't provide a color, a random one will be chosen.
Okay, not literally, but Fire has been fully rewritten in TypeScript (the TypeScript logo is blue haha get it) This is a MAJOR change for Fire as every aspect has been rewritten and improved. I unfortunately can't go over every single change or improvement but I'll list a few highlights below
Fire will now use replies when sending error message, the ping command and also when using tags (if you reply to a message with a tag, Fire will reply to that message with the tag content, mentioning the user. Works best with the
You can now edit tags and give them aliases! This is long overdue 😂
With autodecancer enabled, Fire will now attempt to normalise a users name if it is "cancerous" (man I hate this terminology) which means no more
John Doe 1337 for
𝖙𝖍𝖚𝖌 𝖑𝖎𝖋𝖊#1337 over there, instead they will be nicknamed
Members will also be checked for hoisted/cancerous names on message and member update meaning less hoisted/cancerous users.
Discord's long promised slash commands have finally released and Fire Beta supported them within 48 hours of release for 50 commands (which is sadly the limit) and since the rewrite has been deployed, normal Fire supports them too!
You will need to grant Fire the
applications.commands scope to access slash commands, which you can do by heading to inv.wtf/bot and reinviting Fire with the scope.
Autorole is no longer a premium feature and is available to all servers with Fire! I've also added a bit of spice to the command in the rewrite, allowing you to set a bot autorole as well as normal autorole. This also supports Discord's membership screening feature meaning users will not get the role before passing screening.
Moderation has been overhauled in the rewrite due to the flexibility of discord.js allowing me to have custom guild, member & user classes. This allows for cleaner code and easily allows me to add more moderation features. Moderator IDs are now stored so you can see who gave Billy that warning for posting a meme in general. Speaking of warnings, they will also display warning count in the success message, e.g. Geek#8405 was warned for the 69th time
Member join/leave logging is no longer included in moderation logs. You can set a dedicated channel for member related logging with
$log member #channel
Reminders have been improved with better time parsing and the ability to repeat reminders with a "step". It should no longer say you set a reminder for "59 minutes, 59.294 seconds from now" when you set a reminder for an hour and the same has been done for DMs (although DMs are a bit more finicky) Repeating reminders with a step allows you to make multiple reminders with additional reminders on an interval.
Lots of improvements, including the
These improvements include
Re-use browser & context
Moving Playwright code to Aether, allowing clusters to share the same browser & context instances
Add zlib compression to the Aether websocket, since the HTML data that Fire sends to Aether from the Google Assistant API is massive
Fire is now much more scalable through the magic of Aether! Aether was originally designed by Ravy to handle Aero's shards but I've gone ahead and made my own fork of it, rewritten it in TypeScript, added a Rest API, statistics tracking with Grafana & Influx, realtime statistics for the Fire website, Playwright (as mentioned above), reminders and more. Aether allows Fire to have multiple independent instances that link together through it via a websocket, allowing me to quickly scale Fire up if needs be. This allows each cluster to communicate with Aether and each other, powering features such as the Google command, reminders, user settings, premium, command, module, listener & inhibitor syncing and more.
Fire's status page now shows system metrics! These include both average rest & gateway latency across all clusters.
Fire's website has gotten a few updates to accommodate changes in the rewrite, such as cluster support on the stats page, realtime stats updates, and better routing meaning the page no longer refreshes when navigating to a different page and now has a seamless transition.
Somewhat major update, concerning those who use logging, autodecancer & autodehoist,
I have deployed an update that affects how members are cached, causing other features to be affected too, some in a positive way and others negatively.
Due to these changes, I have had to remove role update logging & nickname update logging. These relied on members being cached due to Discord not providing the previous state. They may return in the rewrite but it is unclear at the moment.
A positive side affect to this change is that I've made autodecancer/autodehoist function similarly to the rewrite where members don't need to be cached for them to be decancered/dehoisted. It will also attempt to run the checks on each message too.
If you encounter issues related to autodecancer or autodehoist, please let me know. I have done some testing but my one-user test may not account for all scenarios.
The only time the old HTML response will be returned is if a request is coming from Discord/Twitter/Slack so they can embed the link with the custom embed. If there's a site that embeds links using OGP tags that isn't one of the 3 listed and you would like inv.wtf URLs to embed there, let me know what the site is in the Fire Discord (and if you know the user agent they use to send requests that'll help get it changed quickly)
Sites that aren't one of the 3 listed above will still show an embed if they follow redirects but it'll be Discord's own embed. If you encounter any issues with inv.wtf please let me know in the Fire Discord too as I also changed a bit of error handling because the old error handling code looked like I was drunk while writing it o_O
Moderation Case IDs are no longer numbers and now use https://github.com/puyuan/py-nanoid since the numbers have started showing letters and symbols (oops)
There's now a search bar on Fire's commands page :D No more endlessly clicking through categories to find what you want, just type a command name and you'll be greeted with matching commands, their description, usage and aliases.
If you've encountered an issue with Vanity URLs stating an error similar to
'bool' object has no attribute 'copy' it has now been fixed, sorry for any inconvenience
The debug command can now show extra information for the
$mute command. You can see an example below. Any users/roles listed for bypassing mutes means they have been explicitly granted
Send Messages in the current channel.
Due to how Discord's permissions work, even if many roles have a permission denied, as long as one role has it allowed then they will always have that permission, meaning allowing a role Send Messages will cause that role to bypass mutes.
When editing a command message where both the old and new commands used paginators, Fire will now forget the old paginator instead of switching between the two upon reacting.
$info guild command has gotten a redesign! It now looks nicer and has many more aliases (
guild, infoguild, info guild, guildinfo, infoserver, serverinfo)
You can now choose how many days worth of messages to delete when banning a user with the
--delete flag (
-d works too)
$ban Aktimoose using deprecated regions --delete 1 to delete messages from the past day (max is 7 due to discord limits)
If the flag is omitted then no messages will be deleted.
shorteners, enable with
$linkfilter shorteners, deletes common short links, e.g. bit.ly
Moderation commands no longer respond if
--silent is used
$tips - Toggle a 10% chance of seeing a useful tip when running a command (enabled by default, see screenshot for an example)
$badname - Change the name used for auto dehoist/decancer. This will not change existing nicknames!
$autodecancer - Toggle renaming those with "cancerous" (non-ascii) names. This will not rename existing users!
$autodehoist - Toggle renaming those with hoisted names. This will not rename existing users!
Fire should no longer log role removals for deleted roles. It may still log a few before the role is actually deleted but this should prevent logs being spammed in large guilds from removing a role that everyone has
$reminders- You can now see your reminders. This really should've been a thing from the start
$delremind - You can now delete your reminders. This really should've been a thing from the start (see screenshot for more info on how to delete a reminder)
The mute command will now delete mutes before attempting to removing the role, meaning tons of mutes don't build up in my database and people don't get muted if/when they rejoin (don't you just love people who leave after getting muted) even though their mute expired
$info user command has gotten a redesign! It now looks nicer and has many more aliases (
user, infouser, info user, userinfo, whois, u)
$antispam <chance of spam>
Toggles ChatWatch spam prevention. If messages have a chance of spam greater than or equal to the chance provided in this command, they will be deleted.
THIS HAS BEEN ENABLED BY DEFAULT WITH AN 80% CHANCE OF SPAM FOR GUILDS WITH AT LEAST 1000 MEMBERS!
$slowmode <delay> [<channel/category>] - Set slowmode in the current channel, another channel or a category
$ghstatus - Check GitHub's status
$cfstatus - Check Cloudflare's status
Fire will now automatically set it's status on https://status.gaminggeek.dev/ depending on it's ping.
If you do
$debug <command> Fire will go through some common things that may prevent a command from running (global checks, permissions, whether the command is enabled or not) and give a list of issues if any are found. This should help with figuring out small issues so if some command stops working, use the debug command and if the debug command stops working, seek immediate help here
To ensure that people cannot scrape the invites from the page, you will now have to solve a captcha to get redirected to the invite. This is to prevent abuse of the page and to ensure your server is protected from potential spam bots joining.
For the past few months, Vanity URLs have been accessible through many domains, with the 2 main ones being
inv.wtf. The latter however was only available to premium guilds and also had support for custom redirects. Starting from today, inv.wtf is the only main domain for Vanity URLs and will eventually be the only domain they're accessible from
This change means that even non-premium guilds will be able to use this domain for their Vanity URLs (redirects are still premium) and the other 5 domains will eventually be phased out and no longer function.
This is for better consistency with Vanity URLs, less hassle for other bots to be keeping up with what domains Fire vanity URLs are accessible from to filter them if they choose to do so and finally as a cost saving measure. I don't have a job and the only way for me to keep Fire up and running pretty much 24/7 is the wonderful people who have supported Fire by purchasing premium <3
Fire's new website has been up for quite a while but I don't recall ever making an actual announcement about it. If you've went to https://fire.gaminggeek.dev or clicked the
Commands link in Fire's help command, you'd see Fire's wonderful "new" website which was made by (in my opinion the best web dev) Nystrex.
This website also includes a public servers page, accessible from https://fire.gaminggeek.dev/discover. Currently there's only a small handful of servers here and if you'd like your server to be shown here, use the
$public command (This requires you to have a Vanity URL set as that's where it gets the invite link from).
I'd like to thank you all for using Fire and hope you enjoy these new updates :D
First we have bug fixes, my favorite.
--remind now actually works which is nice and (not that it matters to any of you) my logs are no longer spammed with errors when starting Fire :D
Anyways, actual cool things now. Fire has been able to run commands when you edit your message for a long time now, but as of about an hour ago during the maintenance, Fire will now edit the response from the old command too! This won't work for any commands that use files due to a Discord limitation
If you have suggestions for Fire, feel free to use the
$suggest command to let me know about 'em. I will start working on suggestions in the next few days as I've sorta been neglecting them
You can now set the muted role Fire uses when muting users! Just use the command
$muterole [<role>] to set it.
If you don't provide a role, Fire will reset it and just use a role called "Muted" and if it's not found, it will create one.
Important update for those who make use of Fire's music feature! Due to many reasons (Lavalink being a piece of trash, YouTube blocking Fire's IP many times, Lavalink being a piece of trash), I ave removed Fire's music feature completely. This will free up a lot of resources on Fire's vps as Lavalink is quite resource intensive, with ram usage in excess of 1.5GB at times, which will allow for more expansion. Fire was never made to be a music oriented bot and music was always a low priority. I have not changed anything related to music since January 10th as Fire's music has been considered "deprecated" since then. If you used Fire's music feature, I'd recommend switching to Groovy (https://groovy.bot/) for all your music needs (and keep Fire for it's other features of course). As Groovy is a bot specifically for music playback, you will have a better experience with it. Thank you for using Fire and I apologize for any inconvenience caused by this removal.
hi i did the same as quotes but for snipe and esnipe and you can only snipe a message once now. once it's sniped, it get's yoinked from fire's memory ok thanks bye such a professional update changelog thing
oh hey a new fea- wait a minute, this isn't new!
That's right, I have rewritten an existing feature and made it cooler :D Fire's quote command (and auto quoting,
$quote auto to enable) now has it's own file and a new addition.
If in a channel where Fire has
Manage Webhooks permission, it will make use of this to make quotes cooler. It will show kinda like the user themselves repeated their message, except there's a BOT tag because it's a webhook. It will use an existing webhook or create one if none exist in that channel. Tip: If you want to go back to the old quotes, just remove
Manage Webhooks from Fire (and
Administrator if applicable) and it will be like nothing changed!
I hope you enjoy this new addition to quoting because I personally love it. If you encounter any issues, please let me know in #help or if you have a suggestion, use the
Today I am releasing Fire's newest feature, tickets! With this new feature, members of your Discord can create tickets for whatever reason they would need it. For tickets to be created, they must be enabled which can be done by setting a category using
$tickets category. You can see all the configuration commands for tickets by using
The main commands for tickets are;
$new - Opens a ticket
$add <user> - Adds a user to the current ticket
$remove <user> - Removes a user from the current ticket
$close - Closes the current ticket
Along with this new feature, we say goodbye to an old one. Fire's muted chat is now removed and Fire will no longer add users to it or set permissions for read messages to false in other channels. To reconfigure Fire's permissions for the Muted role, just delete it and mute someone to recreate it. This was a feature that quite a few people did not like and many did not even use so I made the decision to remove it. I don't see it ever coming back so if you liked it then I apologize for the inconvenience.
tempmention command has been removed. This is due to a recent Discord update that makes it kinda pointless. If you are unaware about the new update, anyone with
Mention Everyone permission can now mention all roles without needing to change the mention toggle. If you don't see this, make sure to update your client.
Fire will now find any image link in the message you are quoting, remove it from the message content and set it as the embed's image so that you don't need to click the link to see it
Merged parts of the rewrite into master
Fire now has reminders!
Fire can give you a reminder for anything and everything right in your DMs. There's two ways to set a reminder with Fire, a command or a flag.
With the command, you just do
$remind <your reminder here> <time> e.g.
$remind fix logging in 1 hour
The flag is an easy way to set a reminder by just adding
--remind to your message. For example, I can do
I need to clean my room --remind 1 hour and Fire will remind me to clean my room in an hour.
My favorite part of reminders is the support for message URLs. Place a message URL in your reminder and when it's time to be reminded, Fire will quote these messages along with your reminder.
Hope you all enjoy this feature as I had a lot of fun making it :)