The ClientUser#setPresence method no longer returns a Promise. The ClientUser#setAFK method no longer returns a Promise. The ClientUser#setActivity method no longer returns a Promise. You will need to implement this yourself if required. To reduce caching, discord.js will no longer store an edit history. The ClientOptions#messageEditHistoryMaxSize option has been removed. # ClientOptions#messageEditHistoryMaxSize Instead, use ClientOptions#makeCache to customize the MessageManager cache. The ClientOptions#messageCacheMaxSize option has been removed. As its purpose is contradictory to Discord's intentions to reduce scraping of user and presence data, it has been removed. With the introduction of gateway intents, the fetchAllMembers Client option would often fail and causes significant delays in ready states or even cause timeout errors. The ClientOptions#fetchAllMembers option has been removed. # ClientOptions # ClientOptions#fetchAllMembers Since timers now have an unref method in Node, this is no longer required. These methods existed for the purpose of caching timeouts internally so they could be cleared when the Client is destroyed. The Client timeout methods have all been removed. Previously, Channel and User were emitted. The Client#typingStart event now only emits a Typing structure. This will now instead cause an error to be thrown. Previously when a token had reached its 1000 login limit for the day, discord.js would treat this as a rate limit and silently wait to login again, but this was not communicated to the user. It accepts a CacheFactory.īy combining this with the helper function Options.cacheWithLimits, users can define limits on each Manager's cache and let discord.js handle the rest. # Customizable Manager cachesĪ popular request that has finally been heard - the Client class now has a new option, makeCache. Refer to the voice section of this guide to get started. You now need to install and use open in new window for interacting with the Discord Voice API. Support for voice has been separated into its own module. Refer to the threads section of this guide to get started. There are also five new events: threadCreate, threadUpdate, threadDelete, threadListSync, threadMemberUpdate, and threadMembersUpdate. ![]() This introduces the ThreadManager class, which can be found as TextChannel#threads, in addition to ThreadChannel, ThreadMemberManager, and ThreadMember. # Threadsĭiscord.js now has support for threads! Threads are a new type of sub-channel that can be used to help separate conversations into a more meaningful flow. Refer to the message components section of this guide to get started. ![]() # Message componentsĭiscord.js now has support for message components! This introduces the MessageActionRow, MessageButton, and MessageSelectMenu classes, as well as associated interactions and collectors. In addition to the interactionCreate event covered in the above guide, this release also includes the new Client events applicationCommandCreate, applicationCommandDelete, and applicationCommandUpdate. # Slash commandsĭiscord.js now has support for slash commands! Refer to the slash commands section of this guide to get started. I also speak in my case, I have a multipurpose bot and it includes adequate features to manage a community, but it also includes spicy features for adults.įor example: there is no NSFW channel in my bot's support guild and displaying those names and descriptions could be out of place and annoying for guild members.# uninstall and re-install pnpm remove discord.jsĭiscord.js v13 makes the switch to Discord API v9! In addition to this, the new major version also includes a bunch of cool new features. Some might think something like " Don't add the integration if you know it contains NSFW content", I know and it would be the most logical thing, but, some bots have multiple purposes and can be really useful, but, as I indicated well it has multiple purposes and there is a high probability that it includes NSFW commands. ![]() Discord is a place where there are underage children and, although bots can verify that the channel of execution of the slash command is NSFW or not, it is possible that the descriptions of the command suggest a vocabulary or words that, perhaps are not the most suitable for his age.Įxample of two commands that should NOT be displayed outside of NSFW channels:Īs I mentioned before, Discord should continue to be a safe place, where content is suitable for underage children and having tools to hide slash commands from developers would be the perfect solution. My suggestion would be to allow marking a slash command as NSFW, such that it is hidden in channels without NSFW enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |