diff --git a/guide/.vuepress/sidebar.ts b/guide/.vuepress/sidebar.ts
index f90da926b..bd6e43e0f 100644
--- a/guide/.vuepress/sidebar.ts
+++ b/guide/.vuepress/sidebar.ts
@@ -5,7 +5,6 @@ export default {
children: [
'/',
'/requesting-more-content.md',
- '/whats-new.md',
],
},
{
@@ -30,7 +29,6 @@ export default {
children: [
'/',
'/requesting-more-content.md',
- '/whats-new.md',
],
},
{
@@ -150,8 +148,7 @@ export default {
'/additional-info/collections.md',
'/additional-info/async-await.md',
'/additional-info/rest-api.md',
- '/additional-info/changes-in-v13.md',
- '/additional-info/changes-in-v14.md',
+ '/additional-info/updating-from-v14.md',
],
},
],
diff --git a/guide/.vuepress/theme/layouts/Layout.vue b/guide/.vuepress/theme/layouts/Layout.vue
index 1e163c7dd..094e5ce9f 100644
--- a/guide/.vuepress/theme/layouts/Layout.vue
+++ b/guide/.vuepress/theme/layouts/Layout.vue
@@ -18,8 +18,8 @@
- You're browsing the guide for discord.js v14.
- Check out what's new, or browse the discord.js v13 guide.
+ You're browsing the in-development guide for discord.js v15.
+ Browse the v14 guide.
diff --git a/guide/additional-info/changes-in-v13.md b/guide/additional-info/changes-in-v13.md
deleted file mode 100644
index 6036a0b88..000000000
--- a/guide/additional-info/changes-in-v13.md
+++ /dev/null
@@ -1,1412 +0,0 @@
-# Updating from v12 to v13
-
-## Before you start
-
-v13 requires Node 16.6 or higher to use, so make sure you're up to date. To check your Node version, use `node -v` in your terminal or command prompt, and if it's not high enough, update it! There are many resources online to help you with this step based on your host system.
-
-Once you've got Node up-to-date, you can install v13 by running the appropriate command in your terminal or command prompt.
-
-:::: code-group
-::: code-group-item npm
-```sh:no-line-numbers
-npm install discord.js # text-only
-npm install discord.js @discordjs/voice # voice support
-```
-:::
-::: code-group-item yarn
-```sh:no-line-numbers
-yarn add discord.js # text-only
-yarn add discord.js @discordjs/voice # voice support
-```
-:::
-::: code-group-item pnpm
-```sh:no-line-numbers
-pnpm add discord.js # text-only
-pnpm add discord.js @discordjs/voice # voice support
-```
-:::
-::::
-
-You can check your discord.js version with the `list` command. Should it still show v12.x, uninstall and re-install discord.js and make sure the entry in your package.json does not prevent a major version update. Please refer to the [npm documentation](https://docs.npmjs.com/files/package.json#dependencies) for this.
-
-:::: code-group
-::: code-group-item npm
-```sh:no-line-numbers
-# check version
-npm list discord.js
-# uninstall and re-install
-npm uninstall discord.js
-npm install discord.js
-```
-:::
-::: code-group-item yarn
-```sh:no-line-numbers
-# check version
-yarn list discord.js
-# uninstall and re-install
-yarn remove discord.js
-yarn add discord.js
-```
-:::
-::: code-group-item pnpm
-```sh:no-line-numbers
-# check version
-pnpm list discord.js
-# uninstall and re-install
-pnpm remove discord.js
-pnpm add discord.js
-```
-:::
-::::
-
-## API version
-
-discord.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.
-
-## Slash commands
-
-discord.js now has support for slash commands!
-Refer to the [slash commands](/interactions/slash-commands.html) section of this guide to get started.
-
-In addition to the `interactionCreate` event covered in the above guide, this release also includes the new Client events `applicationCommandCreate`, `applicationCommandDelete`, and `applicationCommandUpdate`.
-
-## Message components
-
-discord.js now has support for message components!
-This introduces the `MessageActionRow`, `MessageButton`, and `MessageSelectMenu` classes, as well as associated interactions and collectors.
-
-Refer to the [message components](/message-components/buttons.md) section of this guide to get started.
-
-## Threads
-
-discord.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.
-
-This introduces the `ThreadManager` class, which can be found as `TextChannel#threads`, in addition to `ThreadChannel`, `ThreadMemberManager`, and `ThreadMember`. There are also five new events: `threadCreate`, `threadUpdate`, `threadDelete`, `threadListSync`, `threadMemberUpdate`, and `threadMembersUpdate`.
-
-Refer to the [threads](/popular-topics/threads.html) section of this guide to get started.
-
-## Voice
-
-Support for voice has been separated into its own module. You now need to install and use [@discordjs/voice](https://github.com/discordjs/discord.js/tree/main/packages/voice) for interacting with the Discord Voice API.
-
-Refer to the [voice](/voice/) section of this guide to get started.
-
-## Customizable Manager caches
-
-A popular request that has finally been heard - the `Client` class now has a new option, `makeCache`. It accepts a `CacheFactory`.
-
-By combining this with the helper function `Options.cacheWithLimits`, users can define limits on each Manager's cache and let discord.js handle the rest.
-
-```js
-const client = new Client({
- makeCache: Options.cacheWithLimits({
- MessageManager: 200, // This is default
- PresenceManager: 0,
- // Add more class names here
- }),
-});
-```
-
-Additional flexibility can be gained by providing a function which returns a custom cache implementation. Keep in mind this should still maintain the `Collection`/`Map`-like interface for internal compatibility.
-
-```js
-const client = new Client({
- makeCache: manager => {
- if (manager.name === 'MessageManager') return new LimitedCollection({ maxSize: 0 });
- return new Collection();
- },
-});
-```
-
-## Commonly used methods that changed
-
-### Sending messages, embeds, files, etc.
-
-With the introduction of Interactions and it becoming far common for users to want to send an embed with MessageOptions, methods that send messages now enforce a single param.
-This can be either a string, a `MessagePayload`, or that method's variant of `MessageOptions`.
-
-Additionally, all messages sent by bots now support up to 10 embeds. As a result, the `embed` option was removed and replaced with an `embeds` array, which must be in the options object.
-
-```diff
-- channel.send(embed);
-+ channel.send({ embeds: [embed, embed2] });
-
-- channel.send('Hello!', { embed });
-+ channel.send({ content: 'Hello!', embeds: [embed, embed2] });
-
-- interaction.reply('Hello!', { ephemeral: true });
-+ interaction.reply({ content: 'Hello!', ephemeral: true });
-```
-
-`MessageEmbed#attachFiles` has been removed; files should now be attached directly to the message instead of the embed.
-
-```diff
-- const embed = new Discord.MessageEmbed().setTitle('Attachments').attachFiles(['./image1.png', './image2.jpg']);
-- channel.send(embed);
-+ const embed = new Discord.MessageEmbed().setTitle('Attachments');
-+ channel.send({ embeds: [embed], files: ['./image1.png', './image2.jpg'] });
-```
-
-The `code` and `split` options have also been removed. This functionality will now have to be handled manually, such as via the `Formatters.codeBlock` and `Util.splitMessage` helpers.
-
-### Strings
-
-Many methods in discord.js that were documented as accepting strings would also accept other types and resolve this into a string on your behalf. The results of this behavior were often undesirable, producing output such as `[object Object]`.
-
-discord.js now enforces and validates string input on all methods that expect it. Users will need to manually call `toString()` or utilize template literals for all string inputs as appropriate.
-
-The most common areas you will encounter this change in are: `MessageOptions#content`, the properties of a `MessageEmbed`, and passing objects such as users or roles, expecting them to be stringified.
-
-```diff
-- message.channel.send(user);
-+ message.channel.send(user.toString());
-
-let count = 5;
-- embed.addField('Count', count);
-+ embed.addField('Count', count.toString());
-```
-
-### Intents
-
-As v13 makes the switch to Discord API v9, it is now **required** to specify all intents your bot uses in the Client constructor. The `intents` option has also moved from `ClientOptions#ws#intents` to `ClientOptions#intents`.
-
-The shortcuts `Intents.ALL`, `Intents.NON_PRIVILEGED`, and `Intents.PRIVILEGED` have all been removed to discourage bad practices of enabling unused intents.
-
-Refer to our more [detailed article about this topic](/popular-topics/intents.html).
-
-```diff
-- const client = new Client({ ws: { intents: [Intents.FLAGS.GUILDS] } });
-+ const client = new Client({ intents: [Intents.FLAGS.GUILDS] });
-```
-
-### Structures#extend
-
-The concept of extendable Structures has been completely removed from discord.js.
-For more information on why this decision was made, refer to [this pull request](https://github.com/discordjs/discord.js/pull/6027).
-
-There is no swap-in replacement for this, as the intention is to change the code design rather than enable something equally bad.
-
-For some real-world example of the alternatives provided in the PR, you may have been extending the `Guild` class with guild-specific settings:
-
-```js
-Structures.extend('Guild', Guild => {
- return class MyGuild extends Guild {
- constructor(client, data) {
- super(client, data);
- this.settings = {
- prefix: '!',
- };
- }
- };
-});
-```
-
-This functionality can be replicated using the `WeakMap` or `Collection` example, even attaching it to the Client if necessary:
-
-```js
-client.guildSettings = new Collection();
-client.guildSettings.set(guildId, { prefix: '!' });
-// In practice, you would populate this Collection with data fetched from a database
-
-const { prefix } = message.client.guildSettings.get(message.guild.id);
-```
-
-### Collectors
-
-All Collector related classes and methods (both `.create*()` and `.await*()`) now take a single object parameter which also includes the filter.
-
-```diff
-- const collector = message.createReactionCollector(collectorFilter, { time: 15_000 });
-+ const collector = message.createReactionCollector({ filter: collectorFilter, time: 15_000 });
-
-- const reactions = await message.awaitReactions(collectorFilter, { time: 15_000 });
-+ const reactions = await message.awaitReactions({ filter: collectorFilter, time: 15_000 });
-```
-
-### Naming conventions
-
-Some commonly used naming conventions in discord.js have changed.
-
-#### Thing#thingId
-
-The casing of `thingID` properties has changed to `thingId`. This is a more-correct casing for the camelCase used by discord.js as `Id` is an abbreviation of Identifier, not an acronym.
-
-This includes: `afkChannelId`, `applicationId`, `channelId`, `creatorId`, `guildId`, `lastMessageId`, `ownerId`, `parentId`, `partyId`, `processId`, `publicUpdatesChannelId`, `resolveId`, `rulesChannelId`, `sessionId`, `shardId`, `systemChannelId`, `webhookId`, `widgetChannelId`, and `workerId`.
-
-```diff
-- console.log(guild.ownerID);
-+ console.log(guild.ownerId);
-
-- console.log(interaction.channelID);
-+ console.log(interaction.channelId);
-```
-
-#### Client#message
-
-The `message` event has been renamed to `messageCreate`, to bring the library in line with Discord's naming conventions.
-Using `message` will still work, but you'll receive a deprecation warning until you switch over.
-
-```diff
-- client.on("message", message => { ... });
-+ client.on("messageCreate", message => { ... });
-```
-
-### Allowed Mentions
-
-`clientOptions.disableMentions` has been removed and replaced with `clientOptions.allowedMentions`!
-The Discord API now allows bots much more granular control over mention parsing, down to the specific id.
-
-Refer to the [Discord API documentation](https://discord.com/developers/docs/resources/channel#allowed-mentions-object) for more information.
-
-```diff
-- const client = new Discord.Client({ disableMentions: 'everyone' });
-+ const client = new Discord.Client({ allowedMentions: { parse: ['users', 'roles'], repliedUser: true } });
-```
-
-### Replies / Message#reply
-
-`Message#reply` will no longer result in the bot prepending a user mention to the content, replacing the behavior with Discord's reply feature.
-
-`MessageOptions#reply` no longer takes a user id. It has been replaced with a `ReplyOptions` type, expecting `MessageOptions#reply#messageReference` as a Message id.
-
-```diff
-- channel.send('content', { reply: '123456789012345678' }); // User id
-+ channel.send({ content: 'content', reply: { messageReference: '765432109876543219' }}); // Message id
-```
-
-The new `MessageOptions.allowedMentions.repliedUser` boolean option determines if the reply will notify the author of the original message.
-
-```diff
-- message.reply('content')
-+ message.reply({ content: 'content', allowedMentions: { repliedUser: false }})
-```
-Note that this will disable all other mentions in this message. To enable other mentions, you will need to include other `allowedMentions` fields. See the above "Allowed Mentions" section for more.
-
-### Bitfields / Permissions
-
-Bitfields are now `BigInt`s instead of `Number`s. This can be handled using the `BigInt()` class, or the n-suffixed [BigInt literal](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt).
-
-```diff
-- const p = new Permissions(104_324_673);
-+ const p = new Permissions(BigInt(104_324_673));
-+ const p = new Permissions(104_324_673n);
-```
-In addition, the usage of string literals for bitfield flags such as `Permissions` and `UserFlags` is discouraged; you should use the flag instead.
-
-```diff
-- permissions.has('SEND_MESSAGES')
-+ permissions.has(Permissions.FLAGS.SEND_MESSAGES)
-```
-
-### DM Channels
-
-On Discord API v8 and later, DM Channels do not emit the `CHANNEL_CREATE` event, which means discord.js is unable to cache them automatically. In order for your bot to receive DMs, the `CHANNEL` partial must be enabled.
-
-### Webpack
-
-Webpack builds are no longer supported.
-
-## Changes and deletions
-
-### ActivityType
-
-The `CUSTOM_STATUS` type has been renamed to `CUSTOM`.
-
-### APIMessage
-
-The `APIMessage` class has been renamed to `MessagePayload`, resolving a naming clash with an interface in the `discord-api-types` library which represents raw message data objects.
-
-### Channel
-
-#### Channel#type
-
-Channel types are now uppercase and align with Discord's naming conventions.
-
-```diff
-- if(channel.type === 'text') channel.send('Content');
-+ if(channel.type === 'GUILD_TEXT') channel.send('Content');
-```
-
-### Client
-
-#### Client#emojis
-
-The Client Emoji manager is now a `BaseGuildEmojiManager`, providing cache resolution only and removing methods that would fail to create emojis as there was no Guild context.
-
-#### Client#fetchApplication
-
-The `Client#fetchApplication` method has been removed and replaced with the `Client#application` property.
-
-```diff
-- client.fetchApplication().then(application => console.log(application.name))
-+ console.log(client.application.name);
-```
-
-#### Client#fetchWidget
-
-This method has been renamed to `fetchGuildWidget` to better represent its functionality.
-
-#### Client#generateInvite
-
-`Client#generateInvite` no longer supports `PermissionsResolvable` as its argument, requiring `InviteGenerationOptions` instead.
-This also requires that at least one of either `bot` or `applications.commands` is provided in `scopes` to generate a valid invite URL.
-
-To generate an invite link with slash commands permissions:
-
-```js
-client.generateInvite({ scopes: ['applications.commands'] });
-```
-
-To generate an invite link for a bot and define required permissions:
-
-```diff
-- client.generateInvite([Permissions.FLAGS.SEND_MESSAGES]);
-+ client.generateInvite({ scopes: ['bot'], permissions: [Permissions.FLAGS.SEND_MESSAGES] })
-```
-
-#### Client#login
-
-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.
-This will now instead cause an error to be thrown.
-
-#### Client#typingStart
-
-The `Client#typingStart` event now only emits a `Typing` structure. Previously, `Channel` and `User` were emitted.
-
-#### Client#setInterval
-#### Client#setTimeout
-
-The Client timeout methods have all been removed. These methods existed for the purpose of caching timeouts internally so they could be cleared when the Client is destroyed.
-Since timers now have an `unref` method in Node, this is no longer required.
-
-### ClientOptions
-
-#### ClientOptions#fetchAllMembers
-
-The `ClientOptions#fetchAllMembers` option 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.
-As its purpose is contradictory to Discord's intentions to reduce scraping of user and presence data, it has been removed.
-
-#### ClientOptions#messageCacheMaxSize
-
-The `ClientOptions#messageCacheMaxSize` option has been removed. Instead, use [`ClientOptions#makeCache`](#customizable-manager-caches) to customize the `MessageManager` cache.
-
-#### ClientOptions#messageEditHistoryMaxSize
-
-The `ClientOptions#messageEditHistoryMaxSize` option has been removed.
-
-To reduce caching, discord.js will no longer store an edit history. You will need to implement this yourself if required.
-
-### ClientUser
-
-#### ClientUser#setActivity
-
-The `ClientUser#setActivity` method no longer returns a Promise.
-
-#### ClientUser#setAFK
-
-The `ClientUser#setAFK` method no longer returns a Promise.
-
-#### ClientUser#setPresence
-
-The `ClientUser#setPresence` method no longer returns a Promise.
-
-`PresenceData#activity` was replaced with `PresenceData#activities`, which now requires an `Array`.
-
-```diff
-- client.user.setPresence({ activity: { name: 'with discord.js' } });
-+ client.user.setPresence({ activities: [{ name: 'with discord.js' }] });
-```
-
-#### ClientUser#setStatus
-
-The `ClientUser#setStatus` method no longer returns a Promise.
-
-### Collection
-
-#### Collection#array()
-
-#### Collection#keyArray()
-
-These methods existed to provide access to a cached array of Collection values and keys respectively, which other Collection methods relied on internally.
-Those other methods have been refactored to no longer rely on cache, so those arrays and these methods have been removed.
-
-You should instead construct an array by spreading the iterators returned by the base Map class methods:
-
-```diff
-- collection.array();
-+ [...collection.values()];
-
-- collection.keyArray();
-+ [...collection.keys()];
-```
-
-### ColorResolvable
-
-Colors have been updated to align with the new Discord branding.
-
-### Guild
-
-#### Guild#addMember
-
-This method has been removed, with functionality replaced by the new `GuildMemberManager#add`.
-
-```diff
-- guild.addMember(user, { accessToken: token });
-+ guild.members.add(user, { accessToken: token });
-```
-
-#### Guild#fetchBan
-
-#### Guild#fetchBans
-
-These methods have been removed, with functionality replaced by the new `GuildBanManager`.
-
-```diff
-- guild.fetchBan(user);
-+ guild.bans.fetch(user);
-
-- guild.fetchBans();
-+ guild.bans.fetch();
-```
-
-#### Guild#fetchInvites
-
-This method has been removed, with functionality replaced by the new `GuildInviteManager`.
-
-```diff
-- guild.fetchInvites();
-+ guild.invites.fetch();
-```
-
-#### Guild#fetchVanityCode
-
-The `Guild#fetchVanityCode` method has been removed.
-
-```diff
-- Guild.fetchVanityCode().then(code => console.log(`Vanity URL: https://discord.gg/${code}`));
-+ Guild.fetchVanityData().then(res => console.log(`Vanity URL: https://discord.gg/${res.code} with ${res.uses} uses`));
-```
-
-#### Guild#fetchWidget
-
-The `Guild#fetchWidget()` method now retrieves the widget data for the guild instead of the widget settings. See `Client#fetchGuildWidget()`.
-The original functionality has moved to the new method `Guild#fetchWidgetSettings()`.
-
-#### Guild#member
-
-The `Guild#member()` helper/shortcut method has been removed.
-
-```diff
-- guild.member(user);
-+ guild.members.cache.get(user.id)
-```
-
-### Guild#mfaLevel
-
-The `Guild#mfaLevel` property is now an enum.
-
-### Guild#nsfw
-
-The `Guild#nsfw` property has been removed, replaced by `Guild#nsfwLevel`.
-
-#### Guild#owner
-
-The `Guild#owner` property has been removed as it was unreliable due to caching, replaced with `Guild#fetchOwner`.
-
-```diff
-- console.log(guild.owner);
-+ guild.fetchOwner().then(console.log);
-```
-
-#### Guild#setWidget
-
-The `Guild#setWidget()` method has been renamed to `Guild#setWidgetSettings()`.
-
-#### Guild#voice
-
-The `Guild#voice` getter has been removed.
-
-```diff
-- guild.voice
-+ guild.me.voice
-```
-
-### GuildChannel
-
-#### GuildChannel#createOverwrite
-
-This method has been removed, with functionality replaced by the new `PermissionOverwriteManager`.
-
-```diff
-- channel.createOverwrite(user, { VIEW_CHANNEL: false });
-+ channel.permissionOverwrites.create(user, { VIEW_CHANNEL: false });
-```
-
-#### GuildChannel#createInvite
-
-#### GuildChannel#fetchInvites
-
-These methods have been removed from `GuildChannel` and placed only on subclasses for which invites can be created. These are `TextChannel`, `NewsChannel`, `VoiceChannel`, `StageChannel`, and `StoreChannel`.
-
-On these subclasses, the method now supports additional options:
-
-- `targetUser` to target the invite to join a particular streaming user
-- `targetApplication` to target the invite to a particular Discord activity
-- `targetType` defines the type of the target for this invite; user or application
-
-#### GuildChannel#overwritePermissions
-
-This method has been removed, with functionality replaced by the new `PermissionOverwriteManager`.
-
-```diff
-- channel.overwritePermissions([{ id: user.id , allow: ['VIEW_CHANNEL'], deny: ['SEND_MESSAGES'] }]);
-+ channel.permissionOverwrites.set([{ id: user.id , allow: ['VIEW_CHANNEL'], deny: ['SEND_MESSAGES'] }]);
-```
-
-#### GuildChannel#permissionOverwrites
-
-This method no longer returns a Collection of PermissionOverwrites, instead providing access to the `PermissionOverwriteManager`.
-
-#### GuildChannel#setTopic
-
-The `GuildChannel#setTopic` method has been removed and placed only on subclasses for which topics can be set. These are `TextChannel`, `NewsChannel`, and `StageChannel`.
-
-#### GuildChannel#updateOverwrite
-
-This method has been removed, with functionality replaced by the new `PermissionOverwriteManager`.
-
-```diff
-- channel.updateOverwrite(user, { VIEW_CHANNEL: false });
-+ channel.permissionOverwrites.edit(user, { VIEW_CHANNEL: false });
-```
-
-### GuildMember
-
-#### GuildMember#ban
-
-`GuildMember#ban()` will throw a TypeError when a string is provided instead of an options object.
-
-```diff
-- member.ban('reason')
-+ member.ban({ reason: 'reason' })
-```
-
-#### GuildMember#hasPermission
-
-The `GuildMember#hasPermission` shortcut/helper method has been removed.
-
-```diff
-- member.hasPermission(Permissions.FLAGS.SEND_MESSAGES);
-+ member.permissions.has(Permissions.FLAGS.SEND_MESSAGES);
-```
-
-#### GuildMember#lastMessage
-
-#### GuildMember#lastMessageId
-
-#### GuildMember#lastMessageChannelId
-
-None of these properties were actually provided by Discord, instead relying on potentially inaccurate client cache, and have been removed.
-
-#### GuildMember#presence
-
-The `GuildMember#presence` property can now be null, rather than a generic offline presence, such as when the `GUILD_PRESENCES` intent is not enabled.
-
-### GuildMemberManager
-
-#### GuildMemberManager#ban
-
-The `GuildMemberManager#ban` method will throw a TypeError when a string is provided instead of an options object.
-
-```diff
-- guild.members.ban('123456789012345678', 'reason')
-+ guild.members.ban('123456789012345678', { reason: 'reason' })
-```
-
-### Message / MessageManager
-
-#### Message#delete
-
-The `Message.delete()` method no longer accepts any options, requiring a timed-delete to be performed manually.
-
-```diff
-- message.delete({ timeout: 10_000 });
-+ setTimeout(() => message.delete(), 10_000);
-```
-
-`reason` is no longer a parameter as it is not used by the API.
-
-#### MessageManager#delete
-
-The `MessageManager.delete()` method no longer accepts any additional options, requiring a timed-delete to be performed manually.
-
-```diff
-- channel.messages.delete('123456789012345678', { timeout: 10_000 });
-+ setTimeout(() => channel.messages.delete('123456789012345678'), 10_000);
-```
-
-`reason` is no longer a parameter as it is not used by the API.
-
-#### Message#edits
-
-The `Message#edits` property has been removed.
-
-### MessageEmbed
-
-#### MessageEmbed#attachFiles
-
-The `MessageEmbed#attachFiles` method has been removed. Instead, files should be attached to the Message directly via `MessageOptions`.
-
-```diff
-- channel.send({ embeds: [new MessageEmbed().setTitle("Files").attachFiles(file)] })
-+ channel.send({ embeds: [new MessageEmbed().setTitle("Files")], files: [file] })
-```
-
-### Permissions
-
-#### Permissions#FLAGS.MANAGE_EMOJIS
-
-`Permissions.FLAGS.MANAGE_EMOJIS` is now `Permissions.FLAGS.MANAGE_EMOJIS_AND_STICKERS`.
-
-### ReactionUserManager
-
-#### ReactionUserManager#fetch
-
-The `before` option has been removed as it was not supported by the API.
-
-### RoleManager
-
-#### RoleManager#create
-
-The options passed to `RoleManager#create` no longer need to be nested in a `data` object.
-Additionally, `reason` is now part of the options, not a second parameter.
-
-```diff
-- guild.roles.create({ data: { name: "New role" } }, "Creating new role");
-+ guild.roles.create({ name: "New role", reason: "Creating new role" })
-```
-
-#### RoleManager#fetch
-
-The `RoleManager#fetch()` method will now return a Collection instead of a RoleManager when called without params.
-
-### Shard
-
-#### Shard#respawn
-
-The options for the `Shard#respawn` method are now an object instead of separate params.
-In addition, the `spawnTimeout` param has been renamed to `timeout`.
-This means the user no longer needs to pass defaults to fill each positional param.
-
-```diff
-- shard.respawn(500, 30_000);
-+ shard.respawn({ delay: 500, timeout: 30_000 });
-```
-
-#### Shard#spawn
-
-The `spawnTimeout` param has been renamed to `timeout`.
-
-### ShardClientUtil
-
-#### ShardClientUtil#broadcastEval
-
-The `ShardClientUtil#broadcastEval` method no longer accepts a string, instead expecting a function.
-
-```diff
-- client.shard.broadcastEval('this.guilds.cache.size')
-+ client.shard.broadcastEval(client => client.guilds.cache.size)
- .then(results => console.log(`${results.reduce((prev, val) => prev + val, 0)} total guilds`))
- .catch(console.error);
-```
-
-#### ShardClientUtil#respawnAll
-
-The options for the `ShardClientUtil#respawnAll` method are now an object instead of separate params.
-In addition, the `spawnTimeout` param has been renamed to `timeout`.
-This means the user no longer needs to pass defaults to fill each positional param.
-
-```diff
-- client.shard.respawnAll(5_000, 500, 30_000);
-+ client.shard.respawnAll({ shardDelay: 5_000, respawnDelay: 500, timeout: 30_000 });
-```
-
-### ShardingManager
-
-#### ShardingManager#broadcastEval
-
-The `ShardingManager#broadcastEval` method no longer accepts a string, instead expecting a function. See `ShardClientUtil#broadcastEval`.
-
-#### ShardingManager#spawn
-
-The options for the `ShardingManager#spawn` method are now an object instead of separate params.
-In addition, the `spawnTimeout` param has been renamed to `timeout`.
-This means the user no longer needs to pass defaults to fill each positional param.
-
-```diff
-- manager.spawn('auto', 5_500, 30_000);
-+ manager.spawn({ amount: 'auto', delay: 5_500, timeout: 30_000 });
-```
-
-#### ShardingManager#respawnAll
-
-The options for the `ShardingManager#respawnAll` method are now an object instead of separate params.
-In addition, the `spawnTimeout` param has been renamed to `timeout`.
-This means the user no longer needs to pass defaults to fill each positional param.
-
-```diff
-- manager.respawnAll(5_000, 500, 30_000);
-+ manager.respawnAll({ shardDelay: 5_000, respawnDelay: 500, timeout: 30_000 });
-```
-
-### TextChannel
-
-#### TextChannel#startTyping
-
-#### TextChannel#stopTyping
-
-These methods have both been replaced by a singular `TextChannel.sendTyping()`. This method automatically stops typing after 10 seconds, or when a message is sent.
-
-### User
-
-#### User#lastMessage
-
-#### User#lastMessageId
-
-Neither of these properties were actually provided by Discord, instead relying on potentially inaccurate client cache, and have been removed.
-
-#### User#locale
-
-The `User.locale` property has been removed, as this property is not exposed to bots.
-
-#### User#presence
-
-The `User.presence` property has been removed. Presences are now only found on `GuildMember`.
-
-#### User#typingIn
-
-As discord.js no longer caches typing event data, the `User.typingIn()` method has been removed.
-
-#### User#typingSinceIn
-
-As discord.js no longer caches typing event data, the `User.typingSinceIn()` method has been removed.
-
-#### User#typingDurationIn
-
-As discord.js no longer caches typing event data, the `User.typingDurationIn()` method has been removed.
-
-### UserFlags
-
-The deprecated UserFlags `DISCORD_PARTNER` and `VERIFIED_DEVELOPER` / `EARLY_VERIFIED_DEVELOPER` have been removed in favor of their renamed versions.
-
-```diff
-- user.flags.has(UserFlags.FLAGS.DISCORD_PARTNER)
-+ user.flags.has(UserFlags.FLAGS.PARTNERED_SERVER_OWNER)
-
-- user.flags.has(UserFlags.FLAGS.VERIFIED_DEVELOPER)
-+ user.flags.has(UserFlags.FLAGS.EARLY_VERIFIED_BOT_DEVELOPER)
-```
-
-The new flag `DISCORD_CERTIFIED_MODERATOR` has been added.
-
-### Util
-
-Shortcuts to Util methods which were previously exported at the top level have been removed.
-
-#### Util#convertToBuffer
-
-#### Util#str2ab
-
-Both were removed in favor of Node's built-in Buffer methods.
-
-#### Util#fetchRecommendedShards
-
-The `Util#fetchRecommendedShards()` method now supports an additional option `multipleOf` to calculate the number to round up to, e.g. a multiple of 16 for large bot sharding.
-
-#### Util#resolveString
-
-The `Util#resolveString` method has been removed. discord.js now enforces that users provide strings where expected rather than resolving one on their behalf.
-
-### VoiceState
-
-#### VoiceState#kick
-
-The `VoiceState#kick` method has been renamed to `VoiceState#disconnect`.
-
-### WebhookClient
-
-The `WebhookClient` constructor no longer accepts `id, token` as the first two parameters, instead taking a `data` object. This object supports an additional option `url`, allowing creation of a `WebhookClient` from a webhook URL.
-
-```diff
-- new WebhookClient(id, token, options);
-+ new WebhookClient({ id, token }, options);
-
-+ new WebhookClient({ url }, options);
-```
-
-## Additions
-
-### ActivityTypes
-
-A new activity type `COMPETING` has been added.
-
-### ApplicationCommand
-
-Provides API support for slash commands.
-
-### ApplicationCommandManager
-
-Provides API support for creating, editing and deleting slash commands.
-
-### ApplicationCommandPermissionsManager
-
-Provides API support for creating, editing, and deleting permission overwrites on slash commands.
-
-### ApplicationFlags
-
-Provides an enumerated bitfield for `ClientApplication` flags.
-
-### BaseGuild
-
-The new `BaseGuild` class is extended by both `Guild` and `OAuth2Guild`.
-
-### BaseGuildTextChannel
-
-The new `BaseGuildTextChannel` class is extended by both `TextChannel` and `NewsChannel`.
-
-### BaseGuildVoiceChannel
-
-The new `BaseGuildVoiceChannel` class is extended by both `VoiceChannel` and `StageChannel`.
-
-### ButtonInteraction
-
-Provides gateway support for a `MessageComponentInteraction` coming from a button component.
-
-### Channel
-
-#### Channel#isText()
-
-Checks and typeguards if a channel is Text-Based; one of `TextChannel`, `DMChannel`, `NewsChannel` or `ThreadChannel`.
-
-#### Channel#isThread()
-
-Checks and typeguards if a channel is a `ThreadChannel`.
-
-#### Channel#isVoice()
-
-Checks and typeguards if a channel is Voice-Based; `VoiceChannel` or `StageChannel`.
-
-### Client
-
-#### Client#applicationCommandCreate
-
-Emitted when a guild application command is created.
-
-#### Client#applicationCommandDelete
-
-Emitted when a guild application command is deleted.
-
-#### Client#applicationCommandUpdate
-
-Emitted when a guild application command is updated.
-
-#### Client#interactionCreate
-
-Emitted when an interaction is created.
-
-#### Client#stageInstanceCreate
-
-Emitted when a stage instance is created.
-
-#### Client#stageInstanceDelete
-
-Emitted when a stage instance is deleted.
-
-#### Client#stageInstanceUpdate
-
-Emitted when a stage instance gets updated, e.g. change in topic or privacy level.
-
-#### Client#stickerCreate
-
-Emitted when a custom sticker is created in a guild.
-
-#### Client#stickerDelete
-
-Emitted when a custom sticker is deleted in a guild.
-
-#### Client#stickerUpdate
-
-Emitted when a custom sticker is updated in a guild.
-
-#### Client#threadCreate
-
-Emitted when a thread is created or when the client user is added to a thread.
-
-#### Client#threadDelete
-
-Emitted when a thread is deleted.
-
-#### Client#threadListSync
-
-Emitted when the client user gains access to a text or news channel that contains threads.
-
-#### Client#threadMembersUpdate
-
-Emitted when members are added or removed from a thread. Requires the `GUILD_MEMBERS` privileged intent.
-
-#### Client#threadMemberUpdate
-
-Emitted when the client user's thread member is updated.
-
-#### Client#threadUpdate
-
-Emitted when a thread is updated, e.g. name change, archive state change, locked state change.
-
-### ClientOptions
-
-#### ClientOptions#failIfNotExists
-
-This parameter sets the default behavior for `ReplyMessageOptions#failIfNotExists`, allowing or preventing an error when replying to an unknown Message.
-
-### CollectorOptions
-
-#### CollectorOptions#filter
-
-This parameter is now optional and will fall back to a function that always returns true if not provided.
-
-### CommandInteraction
-
-Provides gateway support for slash command interactions.
-For more information refer to the [slash commands](/interactions/registering-slash-commands.html) section of the guide.
-
-### Guild
-
-#### Guild#bans
-
-Provides access to the Guild's `GuildBanManager`.
-
-#### Guild#create
-
-`Guild#systemChannelFlags` can now be set in the `Guild#create` method.
-
-#### Guild#edit
-
-The `Guild#description` and `Guild#features` properties can now be edited.
-
-#### Guild#editWelcomeScreen
-
-Provides API support for bots to edit the Guild's `WelcomeScreen`.
-
-#### Guild#emojis
-
-The `GuildEmojiManager` class now extends `BaseGuildEmojiManager`.
-In addition to the existing methods, it now supports `GuildEmojiManager#fetch`.
-
-#### Guild#fetchWelcomeScreen
-
-Provides API support for fetching the Guild's `WelcomeScreen`.
-
-#### Guild#fetchWidget
-
-Provides API support for the Guild's Widget, containing information about the guild and its members.
-
-#### Guild#invites
-
-Provides access to the new `GuildInviteManager`.
-
-#### Guild#nsfwLevel
-
-The `Guild#nsfwLevel` property is now represented by the `NSFWLevel` enum.
-
-#### Guild#premiumTier
-
-The `Guild#premiumTier` property is now represented by the `PremiumTier` enum.
-
-#### Guild#setChannelPositions
-
-Now supports setting the parent of multiple channels, and locking their permissions via the `ChannelPosition#parent` and `ChannelPosition#lockPermissions` options.
-
-### GuildBanManager
-
-Provides improved API support for handling and caching bans.
-
-Starting from 13.11, developers should utilise `deleteMessageSeconds` instead of `days`:
-
-```diff
-.create('123456789', {
-- days: 3
-+ deleteMessageSeconds: 3 * 24 * 60 * 60
-});
-```
-
-`days` is deprecated and will be removed in the future.
-
-### GuildChannel
-
-#### GuildChannel#clone
-
-Now supports setting the `position` property.
-
-### GuildChannelManager
-
-#### GuildChannelManager#fetch
-
-Now supports fetching the channels of a Guild.
-
-#### GuildChannelManager#fetchActiveThreads
-
-Retrieves a list of the active threads in a Guild.
-
-### GuildInviteManager
-
-Aligns support for creating and fetching invites with the managers design.
-This replaces `Guild#fetchInvites`.
-
-### GuildManager
-
-#### GuildManager#create
-
-Now supports specifying the AFK and system channels when creating a new guild.
-
-#### GuildManager#fetch
-
-Now supports fetching multiple guilds, returning a `Promise>` if used in this way.
-
-### GuildEmojiManager
-
-#### GuildEmojiManager#fetch
-
-Provides API support for the `GET /guilds/{guild.id}/emojis` endpoint.
-
-### GuildMember
-
-#### GuildMember#pending
-
-Flags whether a member has passed the guild's membership gate.
-The flag is `true` before accepting and fires `guildMemberUpdate` when the member accepts.
-
-### GuildMemberManager
-
-Several methods were added to `GuildMemberManager` to provide API support for uncached members.
-
-#### GuildMemberManager#edit
-
-`guild.members.edit('123456789012345678', data, reason)` is equivalent to `GuildMember#edit(data, reason)`.
-
-#### GuildMemberManager#kick
-
-`guild.members.kick('123456789012345678', reason)` is equivalent to `GuildMember#kick(reason)`.
-
-#### GuildMemberManager#search
-
-Provides API support for querying GuildMembers via the REST API endpoint.
-`GuildMemberManager#fetch` uses the websocket gateway to receive data.
-
-### GuildMemberRoleManager
-
-#### GuildMemberRoleManager#botRole
-
-Gets the managed role this member created when joining the guild if any.
-
-#### GuildMemberRoleManager#premiumSubscriberRole
-
-Gets the premium subscriber (booster) role if present on the member.
-
-### GuildPreview
-
-#### GuildPreview#createdAt
-
-#### GuildPreview#createdTimestamp
-
-The datetime at which the GuildPreview was created.
-
-### GuildTemplate
-
-Provides API support for [server templates](https://discord.com/developers/docs/resources/guild-template).
-
-### Integration
-
-#### Integration#roles
-
-A Collection of Roles which are managed by the integration.
-
-### Interaction
-
-Provides gateway support for slash command and message component interactions.
-
-For more information refer to the [slash commands](/interactions/slash-commands.md#replying-to-slash-commands) and [message components](/message-components/buttons) sections of the guide.
-
-### InteractionCollector
-
-Provides a way for users to collect any type of Interaction.
-This class has a more flexible design than other Collectors, able to be bound to any Guild, Channel, or Message as appropriate.
-TypeScript developers can also leverage generics to define the subclass of Interaction that will be returned.
-
-### InteractionWebhook
-
-Provides webhook support specifically for interactions, due to their unique qualities.
-
-### InviteGuild
-
-Provides API support for the partial Guild data available from an `Invite`.
-
-### InviteStageInstance
-
-Provides API support for bots to inviting users to stage instances.
-
-### Message
-
-#### Message#awaitMessageComponent
-
-A shortcut method to create a promisified `InteractionCollector` which resolves to a single `MessageComponentInteraction`.
-
-#### Message#createMessageComponentCollector
-
-A shortcut method to create an `InteractionCollector` for components on a specific message.
-
-#### Message#crosspostable
-
-Checks permissions to see if a Message can be crossposted.
-
-#### Message#edit
-
-Editing and/or removing attachments when editing a Message is now supported.
-
-#### Message#fetchReference
-
-Provides support for fetching the Message referenced by `Message#reference`, if the client has access to do so.
-
-#### Message#react
-
-Now supports both `<:name:id>` and `` as valid inputs.
-
-#### Message#removeAttachments
-
-Removes the attachments from a message. Requires `MANAGE_MESSAGES` to remove attachments from messages authored by other users.
-
-#### Message#startThread
-
-Starts a `ThreadChannel` using this message as the starter message.
-
-#### Message#stickers
-
-A Collection of Stickers in the message.
-
-### MessageActionRow
-
-A builder class which makes constructing action row type message components easier.
-
-### MessageAttachment
-
-#### MessageAttachment#contentType
-
-The media type of a MessageAttachment.
-
-### MessageButton
-
-A builder class which makes constructing button type message components easier.
-
-### MessageComponentInteraction
-
-Provides gateway support for receiving interactions from message components. Subclass of `Interaction`.
-
-### MessageEmbed
-
-#### MessageEmbed#setFields
-
-Replaces all fields in the embed with the new array of fields provided.
-
-`embed.setFields(newFields)` is equivalent to `embed.spliceFields(0, embed.fields.length, newFields)`.
-
-### MessageManager
-
-Methods were added to `MessageManager` to provide API support for uncached messages.
-
-#### MessageManager#crosspost
-
-`channel.messages.crosspost('876543210987654321')` is equivalent to `message.crosspost()`.
-
-#### MessageManager#edit
-
-`channel.messages.edit('876543210987654321', content, options)` is equivalent to `message.edit(content, options)`.
-
-#### MessageManager#pin
-
-`channel.messages.pin('876543210987654321', options)` is approximately equivalent to `message.pin(options)` but does not resolve to a Message.
-
-#### MessageManager#react
-
-`channel.messages.react('876543210987654321', emoji)` is approximately equivalent to `message.react(emoji)` but does not resolve to a MessageReaction.
-
-#### MessageManager#unpin
-
-`channel.messages.unpin('876543210987654321', options)` is approximately equivalent to `message.unpin(options)` but does not resolve to a Message.
-
-### MessageMentions
-
-#### MessageMentions#repliedUser
-
-Checks if the author of a message being replied to has been mentioned.
-
-### MessagePayload
-
-This class has been renamed from APIMessage.
-Global headers can now be set in the HTTP options.
-
-### MessageSelectMenu
-
-A builder class which makes constructing select menu type message components easier.
-
-### NewsChannel
-
-#### NewsChannel#addFollower
-
-Provides API support for bots to follow announcements in other channels.
-
-#### NewsChannel#setType
-
-Allows conversion between NewsChannel and TextChannel.
-
-### Permissions
-
-#### Permissions#STAGE_MODERATOR
-
-Static bitfield representing the permissions required to moderate a stage channel.
-
-### PermissionOverwriteManager
-
-Replaces the `createOverwrite`, `updateOverwrite`, and `overwritePermissions` methods of `GuildChannel`, aligning the design with other Managers.
-
-### Role
-
-#### Role#tags
-
-Tags for roles belonging to bots, integrations, or premium subscribers.
-
-### RoleManager
-
-#### RoleManager#botRoleFor
-
-Gets the managed role a bot created when joining the guild, if any.
-
-#### RoleManager#edit
-
-`guild.roles.edit('123456789098765432', options)` is equivalent to `role.edit(options)`.
-
-#### RoleManager#premiumSubscriberRole
-
-Gets the premium subscriber (booster) role for the Guild, if any.
-
-### SelectMenuInteraction
-
-Provides gateway support for a `MessageComponentInteraction` coming from a select menu component.
-
-### StageChannel
-
-Provides API support for stage channels.
-
-### StageInstance
-
-Provides API support for stage instances. Stage instances contain information about live stages.
-
-### StageInstanceManager
-
-Provides API support for the bot to create, edit, and delete live stage instances, and stores a cache of stage instances.
-
-### Sticker
-
-Provides API support for Discord Stickers.
-
-### StickerPack
-
-Provides API support for Discord Sticker packs.
-
-### TextChannel
-
-#### TextChannel#awaitMessageComponent
-
-A shortcut method to create a promisified `InteractionCollector` which resolves to a single `MessageComponentInteraction`.
-
-#### TextChannel#createMessageComponentCollector
-
-A shortcut method to create an `InteractionCollector` for components on a specific channel.
-
-#### TextChannel#setType
-
-Allows conversion between `TextChannel` and `NewsChannel`.
-
-#### TextChannel#threads
-
-Provides access to the `ThreadManager` for this channel.
-
-### ThreadChannel
-
-Provides API support for thread channels.
-
-### ThreadChannelManager
-
-Provides API support for the bot to create, edit, and delete threads, and stores a cache of `ThreadChannels`.
-
-### ThreadMember
-
-Represent a member of a thread and their thread-specific metadata.
-
-### ThreadMemberManager
-
-Provides API support for the bot to add and remove members from threads, and stores a cache of `ThreadMembers`.
-
-### Typing
-
-Represents a typing state for a user in a channel.
-
-### Webhook
-
-#### Webhook#deleteMessage
-
-Webhooks can now delete messages that were sent by the Webhook.
-
-#### Webhook#editMessage
-
-Webhooks can now edit messages that were sent by the Webhook.
-
-#### Webhook#fetchMessage
-
-Webhooks can now fetch messages that were sent by the Webhook.
-
-#### Webhook#sourceChannel
-
-#### Webhook#sourceGuild
-
-Webhooks can now have a `sourceGuild` and `sourceChannel` if the message is being crossposted.
-
-### WelcomeChannel
-
-Represents the channels that can be seen in a Guild's `WelcomeScreen`.
-
-### WelcomeScreen
-
-Provides API support for a Guild's welcome screen.
-
-### Widget
-
-Represents a Guild's widget.
-
-### WidgetMember
-
-Partial information about a guild's members stored in a widget.
-
-### Util
-
-#### Formatters
-
-A number of new formatter functions are provided in the Util class, to easily handle adding markdown to strings.
-
-#### Util#resolvePartialEmoji
-
-A helper method that attempts to resolve properties for a raw emoji object from input data, without the use of the discord.js Client class or its EmojiManager.
-
-#### Util#verifyString
-
-A helper method which is used to internally validate string arguments provided to methods in discord.js.
diff --git a/guide/additional-info/changes-in-v14.md b/guide/additional-info/changes-in-v14.md
deleted file mode 100644
index de12368db..000000000
--- a/guide/additional-info/changes-in-v14.md
+++ /dev/null
@@ -1,687 +0,0 @@
-# Updating from v13 to v14
-
-## Before you start
-
-Make sure you're using the latest LTS version of Node. To check your Node version, use `node -v` in your terminal or command prompt, and if it's not high enough, update it! There are many resources online to help you with this step based on your host system.
-
-### Various packages are now included in v14
-
-If you previously had `@discordjs/builders`, `@discordjs/formatters`, `@discordjs/rest`, or `discord-api-types` manually installed, it's _highly_ recommended that you uninstall the packages to avoid package version conflicts.
-
-:::: code-group
-::: code-group-item npm
-
-```sh:no-line-numbers
-npm uninstall @discordjs/builders @discordjs/formatters @discordjs/rest discord-api-types
-```
-
-:::
-::: code-group-item yarn
-
-```sh:no-line-numbers
-yarn remove @discordjs/builders @discordjs/formatters @discordjs/rest discord-api-types
-```
-
-:::
-::: code-group-item pnpm
-
-```sh:no-line-numbers
-pnpm remove @discordjs/builders @discordjs/formatters @discordjs/rest discord-api-types
-```
-
-:::
-::::
-
-## Breaking Changes
-
-### API version
-
-discord.js v14 makes the switch to Discord API v10!
-
-### Common Breakages
-
-### Enum Values
-
-Any areas that used to accept a `string` or `number` type for an enum parameter will now only accept exclusively `number`s.
-
-In addition, the old enums exported by discord.js v13 and lower are replaced with new enums from [discord-api-types](https://discord-api-types.dev/api/discord-api-types-v10).
-
-#### New enum differences
-
-Most of the difference between enums from discord.js and discord-api-types can be summarized as so:
-
-1. Enums are singular, i.e., `ApplicationCommandOptionTypes` -> `ApplicationCommandOptionType`
-2. Enums that are prefixed with `Message` no longer have the `Message` prefix, i.e., `MessageButtonStyles` -> `ButtonStyle`
-3. Enum values are `PascalCase` rather than `SCREAMING_SNAKE_CASE`, i.e., `.CHAT_INPUT` -> `.ChatInput`
-
-::: warning
-You might be inclined to use raw `number`s (most commonly referred to as [magic numbers]()) instead of enum values. This is highly discouraged. Enums provide more readability and are more resistant to changes in the API. Magic numbers can obscure the meaning of your code in many ways, check out this [blog post](https://blog.webdevsimplified.com/2020-02/magic-numbers/) if you want more context on as to why they shouldn't be used.
-:::
-
-#### Common enum breakages
-
-Areas like `Client` initialization, JSON slash commands and JSON message components will likely need to be modified to accommodate these changes:
-
-##### Common Client Initialization Changes
-
-```diff
-- const { Client, Intents } = require('discord.js');
-+ const { Client, GatewayIntentBits, Partials } = require('discord.js');
-
-- const client = new Client({ intents: [Intents.FLAGS.GUILDS], partials: ['CHANNEL'] });
-+ const client = new Client({ intents: [GatewayIntentBits.Guilds], partials: [Partials.Channel] });
-```
-
-##### Common Application Command Data changes
-
-```diff
-+ const { ApplicationCommandType, ApplicationCommandOptionType } = require('discord.js');
-
-const command = {
- name: 'ping',
-- type: 'CHAT_INPUT',
-+ type: ApplicationCommandType.ChatInput,
- options: [{
- name: 'option',
- description: 'A sample option',
-- type: 'STRING',
-+ type: ApplicationCommandOptionType.String,
- }],
-};
-```
-
-##### Common Button Data changes
-
-```diff
-+ const { ButtonStyle } = require('discord.js');
-
-const button = {
- label: 'test',
-- style: 'PRIMARY',
-+ style: ButtonStyle.Primary,
- customId: '1234'
-}
-```
-
-### Removal of method-based type guards
-
-#### Channels
-
-Some channel type guard methods that narrowed to one channel type have been removed. Instead compare the `type` property against a [ChannelType](https://discord-api-types.dev/api/discord-api-types-v10/enum/ChannelType) enum member to narrow channels.
-
-```diff
--channel.isText()
-+channel.type === ChannelType.GuildText
-
--channel.isVoice()
-+channel.type === ChannelType.GuildVoice
-
--channel.isDM()
-+channel.type === ChannelType.DM
-```
-
-### Builders
-
-Builders are no longer returned by the API like they were previously. For example you send the API an `EmbedBuilder` but you receive an `Embed` of the same data from the API. This may affect how your code handles received structures such as components. Refer to [message component changes section](#messagecomponent) for more details.
-
-Added `disableValidators()` and `enableValidators()` as top-level exports which disable or enable validation (enabled by default).
-
-### Consolidation of `create()` & `edit()` parameters
-
-Various `create()` and `edit()` methods on managers and objects have had their parameters consolidated. The changes are below:
-
-- `Guild#edit()` now takes `reason` in the `data` parameter
-- `GuildChannel#edit()` now takes `reason` in the `data` parameter
-- `GuildEmoji#edit()` now takes `reason` in the `data` parameter
-- `Role#edit()` now takes `reason` in the `data` parameter
-- `Sticker#edit()` now takes `reason` in the `data` parameter
-- `ThreadChannel#edit()` now takes `reason` in the `data` parameter
-- `GuildChannelManager#create()` now takes `name` in the `options` parameter
-- `GuildChannelManager#createWebhook()` (and other text-based channels) now takes `channel` and `name` in the `options` parameter
-- `GuildChannelManager#edit()` now takes `reason` as a part of `data`
-- `GuildEmojiManager#edit()` now takes `reason` as a part of `data`
-- `GuildManager#create()` now takes `name` as a part of `options`
-- `GuildMemberManager#edit()` now takes `reason` as a part of `data`
-- `GuildMember#edit()` now takes `reason` as a part of `data`
-- `GuildStickerManager#edit()` now takes `reason` as a part of `data`
-- `RoleManager#edit()` now takes `reason` as a part of `options`
-- `Webhook#edit()` now takes `reason` as a part of `options`
-- `GuildEmojiManager#create()` now takes `attachment` and `name` as a part of `options`
-- `GuildStickerManager#create()` now takes `file`, `name`, and `tags` as a part of `options`
-
-### Activity
-
-The following properties have been removed as they are not documented by Discord:
-
-- `Activity#id`
-- `Activity#platform`
-- `Activity#sessionId`
-- `Activity#syncId`
-
-### Application
-
-`Application#fetchAssets()` has been removed as it is no longer supported by the API.
-
-### BitField
-
-- BitField constituents now have a `BitField` suffix to avoid naming conflicts with the enum names:
-
-```diff
-- new Permissions()
-+ new PermissionsBitField()
-
-- new MessageFlags()
-+ new MessageFlagsBitField()
-
-- new ThreadMemberFlags()
-+ new ThreadMemberFlagsBitField()
-
-- new UserFlags()
-+ new UserFlagsBitField()
-
-- new SystemChannelFlags()
-+ new SystemChannelFlagsBitField()
-
-- new ApplicationFlags()
-+ new ApplicationFlagsBitField()
-
-- new Intents()
-+ new IntentsBitField()
-
-- new ActivityFlags()
-+ new ActivityFlagsBitField()
-```
-
-- `#FLAGS` has been renamed to `#Flags`
-
-### CDN
-
-The methods that return CDN URLs have changed. Here is an example on a User:
-
-```diff
-- const url = user.displayAvatarURL({ dynamic: true, format: "png", size: 1_024 });
-+ const url = user.displayAvatarURL({ extension: "png", size: 1_024 });
-```
-
-Dynamic URLs use and static URLs use . Since dynamic URLs are returned by default, this option has been renamed to `forceStatic` which forces the return of a static URL. Additionally, `format` has been renamed to `extension`.
-
-### CategoryChannel
-
-`CategoryChannel#children` is no longer a `Collection` of channels the category contains. It is now a manager (`CategoryChannelChildManager`). This also means `CategoryChannel#createChannel()` has been moved to the `CategoryChannelChildManager`.
-
-### Channel
-
-The following type guards have been removed:
-
-- `Channel#isText()`
-- `Channel#isVoice()`
-- `Channel#isDirectory()`
-- `Channel#isDM()`
-- `Channel#isGroupDM()`
-- `Channel#isCategory()`
-- `Channel#isNews()`
-
-Refer to [this section](#channels) for more context.
-
-The base channel class is now `BaseChannel`.
-
-### Client
-
-The `restWsBridgeTimeout` client option has been removed.
-
-### CommandInteractionOptionResolver
-
-`CommandInteractionOptionResolver#getMember()` no longer has a parameter for `required`. See [this pull request](https://github.com/discordjs/discord.js/pull/7188) for more information.
-
-### Constants
-
-- Many constant objects and key arrays are now top-level exports for example:
-
-```diff
-- const { Constants } = require('discord.js');
-- const { Colors } = Constants;
-+ const { Colors } = require('discord.js');
-```
-
-- The refactored constants structures have `PascalCase` member names as opposed to `SCREAMING_SNAKE_CASE` member names.
-
-- Many of the exported constants structures have been replaced and renamed:
-
-```diff
-- Opcodes
-+ GatewayOpcodes
-
-- WSEvents
-+ GatewayDispatchEvents
-
-- WSCodes
-+ GatewayCloseCodes
-
-- InviteScopes
-+ OAuth2Scopes
-```
-
-### Events
-
-The `message` and `interaction` events are now removed. Use `messageCreate` and `interactionCreate` instead.
-
-`applicationCommandCreate`, `applicationCommandDelete` and `applicationCommandUpdate` have all been removed. See [this pull request](https://github.com/discordjs/discord.js/pull/6492) for more information.
-
-The `threadMembersUpdate` event now emits the users who were added, the users who were removed, and the thread respectively.
-
-### GuildBanManager
-
-Developers should utilise `deleteMessageSeconds` instead of `days` and `deleteMessageDays`:
-
-```diff
-.create('123456789', {
-- days: 3
-- deleteMessageDays: 3
-+ deleteMessageSeconds: 3 * 24 * 60 * 60
-});
-```
-
-`deleteMessageDays` (introduced with version 14) and `days` are both deprecated and will be removed in the future.
-
-### Guild
-
-`Guild#setRolePositions()` and `Guild#setChannelPositions()` have been removed. Use `RoleManager#setPositions()` and `GuildChannelManager#setPositions()` instead respectively.
-
-`Guild#maximumPresences` no longer has a default value of 25,000.
-
-`Guild#me` has been moved to `GuildMemberManager#me`. See [this pull request](https://github.com/discordjs/discord.js/pull/7669) for more information.
-
-### GuildAuditLogs & GuildAuditLogsEntry
-
-`GuildAuditLogs.build()` has been removed as it has been deemed defunct. There is no alternative.
-
-The following properties & methods have been moved to the `GuildAuditLogsEntry` class:
-
-- `GuildAuditLogs.Targets`
-- `GuildAuditLogs.actionType()`
-- `GuildAuditLogs.targetType()`
-
-### GuildMember
-
-`GuildMember#pending` is now nullable to account for partial guild members. See [this issue](https://github.com/discordjs/discord.js/issues/6546) for more information.
-
-### IntegrationApplication
-
-`IntegrationApplication#summary` has been removed as it is no longer supported by the API.
-
-### Interaction
-
-Whenever an interaction is replied to and one fetches the reply, it could possibly give an `APIMessage` if the guild was not cached. However, interaction replies now always return an with `withResponse` set to `true`.
-
-The base interaction class is now `BaseInteraction`.
-
-### Invite
-
-`Invite#inviter` is now a getter and resolves structures from the cache.
-
-### MessageAttachment
-
-- `MessageAttachment` has now been renamed to `AttachmentBuilder`.
-
-```diff
-- new MessageAttachment(buffer, 'image.png');
-
-+ new AttachmentBuilder(buffer, { name: 'image.png' });
-```
-
-### MessageComponent
-
-- MessageComponents have been renamed as well. They no longer have the `Message` prefix, and now have a `Builder` suffix:
-
-```diff
-- const button = new MessageButton();
-+ const button = new ButtonBuilder();
-
-- const selectMenu = new MessageSelectMenu();
-+ const selectMenu = new StringSelectMenuBuilder();
-
-- const actionRow = new MessageActionRow();
-+ const actionRow = new ActionRowBuilder();
-
-- const textInput = new TextInputComponent();
-+ const textInput = new TextInputBuilder();
-```
-
-- Components received from the API are no longer directly mutable. If you wish to mutate a component from the API, use `ComponentBuilder#from`. For example, if you want to make a button mutable:
-
-```diff
-- const editedButton = receivedButton
-- .setDisabled(true);
-
-+ const { ButtonBuilder } = require('discord.js');
-+ const editedButton = ButtonBuilder.from(receivedButton)
-+ .setDisabled(true);
-```
-
-### MessageManager
-
-`MessageManager#fetch()`'s second parameter has been removed. The `BaseFetchOptions` the second parameter once was is now merged into the first parameter.
-
-```diff
-- messageManager.fetch('1234567890', { cache: false, force: true });
-+ messageManager.fetch({ message: '1234567890', cache: false, force: true });
-```
-
-### MessageSelectMenu
-
-- `MessageSelectMenu` has been renamed to `StringSelectMenuBuilder`
-
-- `StringSelectMenuBuilder#addOption()` has been removed. Use `StringSelectMenuBuilder#addOptions()` instead.
-
-### MessageEmbed
-
-- `MessageEmbed` has now been renamed to `EmbedBuilder`.
-
-- `EmbedBuilder#setAuthor()` now accepts a sole object.
-
-- `EmbedBuilder#setFooter()` now accepts a sole object.
-
-- `EmbedBuilder#addField()` has been removed. Use `EmbedBuilder#addFields()` instead.
-
-```diff
-- new MessageEmbed().addField('Inline field title', 'Some value here', true);
-
-+ new EmbedBuilder().addFields([
-+ { name: 'one', value: 'one', inline: true },
-+ { name: 'two', value: 'two', inline: true },
-+]);
-```
-
-### Modal
-
-- `Modal` has been renamed as well and now has a `Builder` suffix:
-
-```diff
-- const modal = new Modal();
-+ const modal = new ModalBuilder();
-```
-
-### PartialTypes
-
-The `PartialTypes` string array has been removed. Use the `Partials` enum instead.
-
-In addition to this, there is now a new partial: `Partials.ThreadMember`.
-
-### Permissions
-
-Thread permissions `USE_PUBLIC_THREADS` and `USE_PRIVATE_THREADS` have been removed as they are deprecated in the API. Use `CREATE_PUBLIC_THREADS` and `CREATE_PRIVATE_THREADS` respectively.
-
-`ManageEmojisAndStickers` has been deprecated due to API changes. Its replacement is `ManageGuildExpressions`. See [this pull request](https://github.com/discord/discord-api-docs/pull/6017) for more information.
-
-### PermissionOverwritesManager
-
-Overwrites are now keyed by the `PascalCase` permission key rather than the `SCREAMING_SNAKE_CASE` permission key.
-
-### REST Events
-
-#### apiRequest
-
-This REST event has been removed as discord.js now uses [Undici](https://github.com/nodejs/undici) as the underlying request handler. You must now use a [Diagnostics Channel](https://undici.nodejs.org/#/docs/api/DiagnosticsChannel). Here is a simple example:
-
-```js
-import diagnosticsChannel from 'node:diagnostics_channel';
-
-diagnosticsChannel.channel('undici:request:create').subscribe(data => {
- // If you use TypeScript, `data` may be casted as
- // `DiagnosticsChannel.RequestCreateMessage`
- // from Undici to receive type definitions.
- const { request } = data;
- console.log(request.method); // Log the method
- console.log(request.path); // Log the path
- console.log(request.headers); // Log the headers
- console.log(request); // Or just log everything!
-});
-```
-
-You can find further examples at the [Undici Diagnostics Channel documentation](https://undici.nodejs.org/#/docs/api/DiagnosticsChannel).
-
-#### apiResponse
-
-This REST event has been renamed to `response` and moved to `Client#rest`:
-
-```diff
-- client.on('apiResponse', ...);
-+ client.rest.on('response', ...);
-```
-
-#### invalidRequestWarning
-
-This REST event has been moved to `Client#rest`:
-
-```diff
-- client.on('invalidRequestWarning', ...);
-+ client.rest.on('invalidRequestWarning', ...);
-```
-
-#### rateLimit
-
-This REST event has been renamed to `rateLimited` and moved to `Client#rest`:
-
-```diff
-- client.on('rateLimit', ...);
-+ client.rest.on('rateLimited', ...);
-```
-
-### RoleManager
-
-`Role.comparePositions()` has been removed. Use `RoleManager#comparePositions()` instead.
-
-### Sticker
-
-`Sticker#tags` is now a nullable string (`string | null`). Previously, it was a nullable array of strings (`string[] | null`). See [this pull request](https://github.com/discordjs/discord.js/pull/8010) for more information.
-
-### ThreadChannel
-
-The `MAX` helper used in `ThreadAutoArchiveDuration` has been removed. Discord has since allowed any guild to use any auto archive time which makes this helper redundant.
-
-### ThreadMemberManager
-
-`ThreadMemberManager#fetch()`'s second parameter has been removed. The `BaseFetchOptions` the second parameter once was is now merged into the first parameter. In addition, the boolean helper to specify `cache` has been removed.
-
-Usage is now as follows:
-
-```diff
-// The second parameter is merged into the first parameter.
-- threadMemberManager.fetch('1234567890', { cache: false, force: true });
-+ threadMemberManager.fetch({ member: '1234567890', cache: false, force: true });
-
-// The lone boolean has been removed. One must be explicit here.
-- threadMemberManager.fetch(false);
-+ threadMemberManager.fetch({ cache: false });
-```
-
-### Util
-
-`Util.removeMentions()` has been removed. To control mentions, you should use `allowedMentions` on `BaseMessageOptions` instead.
-
-`Util.splitMessage()` has been removed. This utility method is something the developer themselves should do.
-
-`Util.resolveAutoArchiveMaxLimit()` has been removed. Discord has since allowed any guild to use any auto archive time which makes this method redundant.
-
-Other functions in `Util` have been moved to top-level exports so you can directly import them from `discord.js`.
-
-```diff
-- import { Util } from 'discord.js';
-- Util.escapeMarkdown(message);
-+ import { escapeMarkdown } from 'discord.js';
-+ escapeMarkdown(message);
-```
-
-### `.deleted` Field(s) have been removed
-
-You can no longer use the `deleted` property to check if a structure was deleted. See [this issue](https://github.com/discordjs/discord.js/issues/7091) for more information.
-
-### VoiceChannel
-
-`VoiceChannel#editable` has been removed. You should use `GuildChannel#manageable` instead.
-
-### VoiceRegion
-
-`VoiceRegion#vip` has been removed as it is no longer part of the API.
-
-### Webhook
-
-`Webhook#fetchMessage()`'s second parameter no longer allows a boolean to be passed. The `cache` option in `WebhookFetchMessageOptions` should be used instead.
-
-## Features
-
-### ApplicationCommand
-
-NFSW commands are supported.
-
-### Attachment
-
-Added support for voice message metadata fields.
-
-### AutocompleteInteraction
-
-`AutocompleteInteraction#commandGuildId` has been added which is the id of the guild the invoked application command is registered to.
-
-### BaseChannel
-
-Added support for `BaseChannel#flags`.
-
-Store channels have been removed as they are no longer part of the API.
-
-`BaseChannel#url` has been added which is a link to a channel, just like in the client.
-
-Additionally, new typeguards have been added:
-
-- `BaseChannel#isDMBased()`
-- `BaseChannel#isTextBased()`
-- `BaseChannel#isVoiceBased()`
-
-### BaseInteraction
-
-Added `BaseInteraction#isRepliable()` to check whether a given interaction can be replied to.
-
-### ClientApplication
-
-Added support for role connection metadata.
-
-### Collection
-
-- Added `Collection#merge()` and `Collection#combineEntries()`.
-- New type: `ReadonlyCollection` which indicates an immutable `Collection`.
-
-### Collector
-
-A new `ignore` event has been added which is emitted whenever an element is not collected by the collector.
-
-Component collector options now use the `ComponentType` enum values:
-
-```diff
-+ const { ComponentType } = require('discord.js');
-
-const collector = interaction.channel.createMessageComponentCollector({
- filter: collectorFilter,
-- componentType: 'BUTTON',
-+ componentType: ComponentType.Button,
- time: 20_000
-});
-```
-
-### CommandInteraction
-
-`CommandInteraction#commandGuildId` has been added which is the id of the guild the invoked application command is registered to.
-
-### CommandInteractionOptionResolver
-
-`CommandInteractionOptionResolver#getChannel()` now has a third parameter which narrows the channel type.
-
-### Events
-
-Added support for `guildAuditLogEntryCreate` event.
-
-### ForumChannel
-
-Added support for forum channels.
-
-Added support for `ForumChannel#defaultForumLayout`.
-
-### Guild
-
-Added `Guild#setMFALevel()` which sets the guild's MFA level.
-
-Added `Guild#maxVideoChannelUsers` which indicates the maximum number of video channel users.
-
-Added `Guild#maxStageVideoChannelUsers` which indicates the maximum number of video channel users for stage channels.
-
-Added `Guild#disableInvites()` which disables the guild's invites.
-
-Added support for the `after` parameter in `Guild#fetchAuditLogs()`.
-
-### GuildChannelManager
-
-`videoQualityMode` may be used whilst creating a channel to initially set the camera video quality mode.
-
-### GuildEmojiManager
-
-Added `GuildEmojiManager#delete()` and `GuildEmojiManager#edit()` for managing existing guild emojis.
-
-### GuildForumThreadManager
-
-Added `GuildForumThreadManager` as manager for threads in forum channels.
-
-### GuildMember
-
-Added support for `GuildMember#flags`.
-
-### GuildMembersChunk
-
-This object now supports the `GuildMembersChunk#notFound` property.
-
-### GuildMemberManager
-
-Added `GuildMemberManager#fetchMe()` to fetch the client user in the guild.
-
-Added `GuildMemberManager#addRole()` and `GuildMemberManager#removeRole()`. These methods allow a single addition or removal of a role respectively to a guild member, even if uncached.
-
-### GuildTextThreadManager
-
-Added `GuildTextThreadManager` as manager for threads in text channels and announcement channels.
-
-### Message
-
-`Message#position` has been added as an approximate position in a thread.
-
-Added support for role subscription data.
-
-### MessageReaction
-
-Added `MessageReaction#react()` to make the client user react with the reaction the class belongs to.
-
-### Role
-
-Added support for role subscriptions.
-
-Added support for `Role#tags#guildConnections`.
-
-### StageChannel
-
-Stage channels now allow messages to be sent in them, much like voice channels.
-
-### Sticker
-
-Added support for GIF stickers.
-
-### ThreadMemberManager
-
-The new `withMember` options returns the associated guild member with the thread member.
-
-When fetching multiple thread members alongside `withMember`, paginated results will be returned. The `after` and `limit` option are supported in this scenario.
-
-### Webhook
-
-Added `Webhook#applicationId`.
-
-Added the `threadName` property in `Webhook#send()` options which allows a webhook to create a post in a forum channel.
-
-### WebSocketManager
-
-discord.js uses internally.
diff --git a/guide/additional-info/updating-from-v14.md b/guide/additional-info/updating-from-v14.md
new file mode 100644
index 000000000..8af53836d
--- /dev/null
+++ b/guide/additional-info/updating-from-v14.md
@@ -0,0 +1,345 @@
+# Updating from v14
+
+## Before you start
+
+Make sure you're using the latest LTS version of Node. To check your Node version, use `node --version` in your terminal or command prompt, and if it's not high enough, update it! There are many resources online to help you with this step based on your host system.
+
+## Breaking Changes
+
+### ActionRow
+
+`ActionRow.from()` has been removed. Use `ActionRowBuilder.from()` instead.
+
+### ApplicationCommand
+
+`ApplicationCommand#dmPermission` and `ApplicationCommand#setDMPermission()` have been removed. This was legacy functionality for commands—use contexts instead.
+
+### ApplicationCommandManager
+
+`ApplicationCommandManager#fetch()` method has been updated for consistency with other managers. Previously, it accepted two parameters: `id` (a snowflake or an options object) and an `options` object. Now, it only accepts a single `options` argument, which can be a snowflake or an options object that may include an `id` property.
+
+### AnnouncementChannel
+
+`AnnouncementChannel#addFollower()` now returns `FollowedChannelData` instead of a snowflake. This helps to expose the created webhook id in the target channel.
+
+### BaseInteraction
+
+`BaseInteraction#isAnySelectMenu()` has been removed. Use `BaseInteraction#isSelectMenu()` instead, which has been repurposed to accept all select menu component types.
+
+### Client
+
+#### Emojis
+
+`Client#emojis` has been removed due to confusion with the introduction of application emojis and performance impact. Use the `resolveGuildEmoji()` utility function to get a cached guild emoji.
+
+#### Ping
+
+`Client#ping` has been added to replace the old `WebSocketManager#ping`. This will be `null` when the heartbeat from the gateway is yet to be received.
+
+#### Premium sticker packs
+
+`Client#fetchPremiumStickerPacks()` has been removed. Use `Client#fetchStickerPacks()` instead.
+
+#### Ready event
+
+`client.on("ready")` has been removed. `"clientReady"` is the replacement. If you used `client.on(Events.ClientReady)`, you do not need to change anything.
+
+#### Shard disconnect event
+
+`client.on("shardDisconnect")` has been removed as the WebSocket manager replaces this functionality.
+
+#### Shard error event
+
+`client.on("shardError")` has been removed as the WebSocket manager replaces this functionality.
+
+#### Shard ready event
+
+`client.on("shardReady")` has been removed as the WebSocket manager replaces this functionality.
+
+#### Shard reconnecting event
+
+`client.on("shardReconnecting")` has been removed as the WebSocket manager replaces this functionality.
+
+#### Shard resume event
+
+`client.on("shardResume")` has been removed as the WebSocket manager replaces this functionality.
+
+#### Webhook update event
+
+`client.on("webhookUpdate")` has been removed. `"webhooksUpdate"` is the replacement. If you used `client.on(Events.WebhooksUpdate)`, you do not need to change anything.
+
+#### WebSocket
+
+The underlying WebSocket behaviour has changed. In version 14, this was a non-breaking implementation of . Now, it is fully integrated. See these pull requests for more information:
+
+- [discordjs/discord.js#10420](https://github.com/discordjs/discord.js/pull/10420)
+- [discordjs/discord.js#10556](https://github.com/discordjs/discord.js/pull/10556)
+
+### ClientEvents
+
+`ClientEvents` type has been removed. Use `ClientEventTypes` instead. This change ensures consistency with the rest of the event types across the library.
+
+### ClientOptions
+
+Removed `ClientOptions#shards` and `ClientOptions#shardCount` in favor of `ClientOptions#ws#shardIds` and `ClientOptions#ws#shardCount`.
+
+### ClientUser
+
+`ClientUser#setPresence()` now returns a promise which resolves when the gateway call was sent successfully.
+
+### ClientPresence
+
+`ClientPresence#set()` now returns a promise which resolves when the gateway call was sent successfully.
+
+### CommandInteractionOptionResolver
+
+`CommandInteractionOptionResolver#getFocused()`'s parameter has been removed. `AutocompleteFocusedOption` will always be returned.
+
+### Constants
+
+`DeletableMessageTypes` has been removed. Use `UndeletableMessageTypes` instead.
+
+### DiscordjsErrorCodes
+
+The following error codes have been removed as they either have no use or are handled in another package instead:
+
+- `WSCloseRequested`
+- `WSConnectionExists`
+- `WSNotOpen`
+- `ManagerDestroyed`
+- `ShardingInvalid`
+- `ShardingRequired`
+- `InvalidIntents`
+- `DisallowedIntents`
+- `ButtonLabel`
+- `ButtonURL`
+- `ButtonCustomId`
+- `SelectMenuCustomId`
+- `SelectMenuPlaceholder`
+- `SelectOptionLabel`
+- `SelectOptionValue`
+- `SelectOptionDescription`
+- `UserBannerNotFetched`
+- `ImageFormat`
+- `ImageSize`
+- `SplitMaxLen`
+- `MissingManageEmojisAndStickersPermission`
+- `VanityURL`
+- `InteractionEphemeralReplied`
+
+### Emoji
+
+#### Image URL is now dynamic
+
+`Emoji#imageURL()` now dynamically handles the extension. Previously, you would have to do this:
+
+```js
+emoji.imageURL({ extension: emoji.animated ? 'gif' : 'webp' });
+```
+
+Now, you can simply do this:
+
+```js
+emoji.imageURL();
+```
+
+#### Emoji URL getter removal
+
+`Emoji#url` has been removed. To allow more granular control of the returned extension, Use `Emoji#imageURL()` instead.
+
+### EventEmitter
+
+`BaseClient`, `Shard`, `ShardingManager`, and `Collector` now extend `AsyncEventEmitter` instead of `EventEmitter`. This comes from [@vladfrangu/async_event_emitter](https://npmjs.com/package/@vladfrangu/async_event_emitter).
+
+### Events
+
+- `Events.ShardError` has been removed.
+- `Events.ShardReady` has been removed.
+- `Events.ShardReconnecting` has been removed.
+- `Events.ShardResume` has been removed.
+- `Events.WebhooksUpdate` now returns a string of `"webhooksUpdate"`. Previously, it returned `"webhookUpdate"`. This is to bring it in line with the name of Discord's gateway event (`WEBHOOKS_UPDATE`).
+- `Events.ClientReady` now returns a string of `"clientReady"`. Previously, it returned `"ready"`. This is to ensure there's no confusion with Discord's `READY` gateway event.
+
+### Formatters
+
+This utility has been removed. Everything in this class is redundant as all methods of the class can be imported from discord.js directly.
+
+```diff
+- import { Formatters } from "discord.js";
++ import { userMention } from "discord.js";
+
+- Formatters.userMention("123456789012345678");
++ userMention("123456789012345678");
+```
+
+### Guild
+
+Removed `Guild#shard` as WebSocket shards are now handled by @discordjs/ws.
+
+### GuildApplicationCommandManager
+
+`GuildApplicationCommandManager#fetch()` method has been updated for consistency with other managers. Previously, it accepted two parameters: `id` (a snowflake or an options object) and an `options` object. Now, it only accepts a single `options` argument, which can be a snowflake or an options object that may include an `id` property.
+
+### GuildAuditLogs
+
+`GuildAuditLogsEntry.Targets.All` has been removed. It was not being used.
+
+### GuildBanManager
+
+`GuildBanManager#create()` no longer accepts `deleteMessageDays`. This is replaced with `deleteMessageSeconds`.
+
+### GuildChannelManager
+
+`GuildChannelManager#addFollower()` now returns `FollowedChannelData` instead of a snowflake. This helps to expose the created webhook id in the target channel.
+
+### GuildMemberResolvable
+
+`GuildMemberResolvable` type has been removed. It was defined as `GuildMember | UserResolvable`, but `UserResolvable` already includes `GuildMember`. Use `UserResolvable` instead.
+
+### MessageManager
+
+`MessageManager#crosspost()` has been moved to `GuildMessageManager`. This means it will no longer be exposed in `DMMessageManager`.
+
+### IntegrationApplication
+
+`IntegrationApplication#hook` has been removed.
+
+### InteractionResponse
+
+`InteractionResponse` has been removed. This class was encountered when responding to an interaction without `fetchReply` to allow ease of creating interaction collectors. This is no longer necessary as `withResponse` exposes the message.
+
+### InteractionResponses
+
+#### Ephemeral option removal
+
+Previously, you would respond to an interaction ephemerally like so:
+
+```js
+// Way 1:
+await interaction.reply({ content: 'This is an ephemeral response.', ephemeral: true });
+
+// Way 2:
+await interaction.reply({ content: 'This is an ephemeral response.', flags: MessageFlags.Ephemeral });
+```
+
+There are two ways to achieve the same behaviour, so the "helper" option has been removed. In this case, that would be `ephemeral`, as all that did was assign `MessageFlags.Ephemeral` internally.
+
+#### Fetch reply option removal
+
+`fetchReply` has been removed in favor of `withResponse`. If you were using the `fetchReply` option or fetching the response of an interaction, it is recommended to use `withResponse` instead, as the message is exposed without an additional API call:
+
+```diff
+- const message = await interaction.reply({ content: 'Hello!', fetchReply: true });
++ const response = await interaction.reply({ content: 'Hello!', withResponse: true });
++ const { message } = response.resource;
+```
+
+#### Premium response type
+
+Discord no longer supports the `PREMIUM_REQUIRED` interaction response type. In the past, you would have done this:
+
+```js
+if (!premiumLogicCheck) {
+ // User does not have access to our premium features.
+ await interaction.sendPremiumRequired();
+ return;
+}
+
+await interaction.reply('You have access to our premium features!');
+```
+
+However, you would have already noticed that this no longer works, so this method has been removed. Sending a premium button has been the replacement ever since.
+
+### Invite
+
+`Invite#stageInstance` has been removed.
+
+### InviteStageInstance
+
+`InviteStageInstance` has been removed.
+
+### Message
+
+`Message#interaction` has been removed. Use `Message#interactionMetadata` instead.
+
+### MessagePayload
+
+`MessagePayload#isInteraction` no longer serves a purpose and has been removed.
+
+### NewsChannel
+
+`NewsChannel` has been renamed to `AnnouncementChannel`.
+
+### PermissionOverwrites
+
+`PermissionOverwrites.resolve()` previously relied on cache if a snowflake was passed. This method no longer relies on cache and instead requires an explicit `type` if supplied.
+
+### RoleManager
+
+`RoleManager#fetch()` used to return `null` when fetching a role that did not exist. This logic has been removed and will throw an error instead.
+
+### SelectMenuBuilder
+
+`SelectMenuBuilder` has been removed. Use `StringSelectMenuBuilder` instead.
+
+### SelectMenuComponent
+
+`SelectMenuComponent` has been removed. Use `StringSelectMenuComponent` instead.
+
+### SelectMenuInteraction
+
+`SelectMenuInteraction` has been removed. Use `StringSelectMenuInteraction` instead.
+
+### SelectMenuOptionBuilder
+
+`SelectMenuOptionBuilder` has been removed. Use `StringSelectMenuOptionBuilder` instead.
+
+### ShardClientUtil
+
+`ShardClientUtil#ids` and `ShardClientUtil#count` have been removed in favor of `Client#ws#getShardIds()` and `Client#ws#getShardCount()`.
+
+### StageInstance
+
+`StageInstance#discoverableDisabled` has been removed.
+
+### TeamMember
+
+`TeamMember#permissions` has been removed. Use `TeamMemberManager#role` instead.
+
+### TextBasedChannel
+
+`TextBasedChannel#bulkDelete()` could return a collection containing `undefined` values. This was because in order to return these messages, the cache must be checked, especially when only snowflakes were provided. The return type of this method has thus changed to only return an array of snowflakes that were bulk deleted.
+
+### ThreadChannel
+
+`ThreadChannel#fetchOwner()` used to return `null` when the thread owner was not present in the thread. This logic has been removed and will throw an error instead.
+
+### ThreadManager
+
+`ThreadManager#fetch()` now throws an error when the provided thread id doesn't belong to the current channel.
+
+### ThreadMember
+
+The reason parameter of `ThreadMember#add()` and `ThreadMember#remove()` have been removed. Discord did not respect this parameter, so it did not do anything.
+
+### ThreadMemberManager
+
+The reason parameter of `ThreadMemberManager#remove()` has been removed. Discord did not respect this parameter, so it did not do anything.
+
+### User
+
+#### Avatar decoration
+
+Discord no longer sends avatar decoration data via `User#avatarDecoration`, so this property has been removed. `User#avatarDecorationData` is the replacement.
+
+#### Flags
+
+`User#fetchFlags()` has been removed. All this did was fetch the user and return only its `flags` property. It was quite redundant.
+
+### UserManager
+
+`UserManager#fetchFlags()` has been removed. All this did was fetch the user and return only its `flags` property. It was quite redundant.
+
+### WebSocketShardEvents
+
+`WebSocketShardEvents` has been replaced with `WebSocketShardEvents` from @discordjs/ws.
diff --git a/guide/popular-topics/faq.md b/guide/popular-topics/faq.md
index 8c740b668..d46ff2c85 100644
--- a/guide/popular-topics/faq.md
+++ b/guide/popular-topics/faq.md
@@ -309,11 +309,11 @@ client.on(Events.GuildMemberUpdate, (oldMember, newMember) => {
There are two common measurements for bot pings. The first, **websocket heartbeat**, is the average interval of a regularly sent signal indicating the healthy operation of the websocket connection the library receives events over:
```js
-interaction.reply(`Websocket heartbeat: ${client.ws.ping}ms.`);
+interaction.reply(`Websocket heartbeat: ${client.ping}ms.`);
```
::: tip
-If you're using [sharding](/sharding/), a specific shard's heartbeat can be found on the WebSocketShard instance, accessible at `client.ws.shards.get(id).ping`.
+If you're using [sharding](/sharding/), a specific shard's heartbeat can be found on the WebSocketShard instance, accessible at `client.pings.get(id)`.
:::
The second, **Roundtrip Latency**, describes the amount of time a full API roundtrip (from the creation of the command message to the creation of the response message) takes. You then edit the response to the respective value to avoid needing to send yet another message:
diff --git a/guide/popular-topics/threads.md b/guide/popular-topics/threads.md
index 7816527b6..d988764d9 100644
--- a/guide/popular-topics/threads.md
+++ b/guide/popular-topics/threads.md
@@ -13,13 +13,13 @@ Threads introduce a number of new gateway events, which are listed below:
- : Emitted whenever a thread is created or when the client user is added to a thread.
- : Emitted whenever a thread is deleted.
- : Emitted whenever a thread is updated (e.g. name change, archive state change, locked state change).
-- : Emitted whenever the client user gains access to a text or news channel that contains threads.
+- : Emitted whenever the client user gains access to a text or announcement channel that contains threads.
- : Emitted whenever members are added or removed from a thread. Requires GuildMembers privileged intent.
- : Emitted whenever the client user's thread member is updated.
## Creating and deleting threads
-Threads are created and deleted using the of a text or news channel.
+Threads are created and deleted using the of a text or announcement channel.
To create a thread you call the method:
diff --git a/guide/slash-commands/autocomplete.md b/guide/slash-commands/autocomplete.md
index a719d723a..56e088e50 100644
--- a/guide/slash-commands/autocomplete.md
+++ b/guide/slash-commands/autocomplete.md
@@ -97,7 +97,7 @@ The class provides the method returns the currently focused option's value, which can be used to apply filtering to the choices presented. For example, to only display options starting with the focused value you can use the `Array#filter()` method, then using `Array#map()`, you can transform the array into an array of objects.
+The method returns the currently focused option, which can be used to apply filtering to the choices presented. For example, to only display options starting with the focused value, you can use the `Array#filter()` method. Then, using `Array#map()`, you can transform the array into an array of objects.
```js {10-15}
module.exports = {
@@ -109,7 +109,7 @@ module.exports = {
.setDescription('Phrase to search for')
.setAutocomplete(true)),
async autocomplete(interaction) {
- const focusedValue = interaction.options.getFocused();
+ const focusedValue = interaction.options.getFocused().value;
const choices = ['Popular Topics: Threads', 'Sharding: Getting started', 'Library: Voice Connections', 'Interactions: Replying to slash commands', 'Popular Topics: Embed preview'];
const filtered = choices.filter(choice => choice.startsWith(focusedValue));
await interaction.respond(
@@ -121,7 +121,7 @@ module.exports = {
### Handling multiple autocomplete options
-To distinguish between multiple options, you can pass `true` into , which will now return the full focused object instead of just the value. This is used to get the name of the focused option below, allowing for multiple options to each have their own set of suggestions:
+By making use of `name`, you can distinguish between multiple options and provide different suggestions for each:
```js {10-19}
module.exports = {
@@ -137,7 +137,7 @@ module.exports = {
.setDescription('Version to search in')
.setAutocomplete(true)),
async autocomplete(interaction) {
- const focusedOption = interaction.options.getFocused(true);
+ const focusedOption = interaction.options.getFocused();
let choices;
if (focusedOption.name === 'query') {
diff --git a/guide/whats-new.md b/guide/whats-new.md
deleted file mode 100644
index 43b510940..000000000
--- a/guide/whats-new.md
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-# What's new
-
-
-
-
- upgrade
-
- discord.js v14 has released and the guide has been updated!
-
- 
-
-
- This includes additions and changes made in Discord, such as slash commands and message components.
-
-
-
-## Site
-
-- Upgraded to [VuePress v2](https://v2.vuepress.vuejs.org/)
-- New theme made to match the [discord.js documentation site](https://discord.js.org/)
-- Discord message components upgraded to [@discord-message-components/vue](https://github.com/Danktuary/discord-message-components/blob/main/packages/vue/README.md)
-- Many fixes in code blocks, grammar, consistency, etc.
-
-## Pages
-
-All content has been updated to use discord.js v14 syntax. The v13 version of the guide can be found at [https://v13.discordjs.guide/](https://v13.discordjs.guide/).
-
-### New
-
-- [Updating from v13 to v14](/additional-info/changes-in-v14.md): A list of the changes from discord.js v13 to v14
-- [Slash commands](/slash-commands/advanced-creation.md): Registering, replying to slash commands and permissions
-- [Buttons](/message-components/buttons): Building, sending, and receiving buttons
-- [Select menus](/message-components/select-menus): Building, sending, and receiving select menus
-- [Threads](/popular-topics/threads.md): Creating and managing threads
-- [Formatters](/popular-topics/formatters.md): A collection of formatters to use with your bot
-
-### Updated
-
-- Commando: Replaced with [Sapphire](https://sapphirejs.dev/docs/Guide/getting-started/getting-started-with-sapphire)
-- [Voice](/voice/): Rewritten to use the [`@discordjs/voice`](https://github.com/discordjs/discord.js/tree/main/packages/voice) package
-- [Command handling](/creating-your-bot/command-handling.md/): Updated to use slash commands
- - Obsolete sections removed
-- `client.on('message')` snippets updated to `client.on('interactionCreate')`
- - [Message content will become a new privileged intent on August 31, 2022](https://support-dev.discord.com/hc/articles/4404772028055)
-
-
-
- Thank you to all of those that contributed to the development of discord.js and the guide!
-
- 
-
-
-