split the change log (#7083)

discord · Aug 19, 2024 · 029d2af · 029d2af
1 parent e3d515c
commit 029d2af
Show file tree

Hide file tree

Showing 131 changed files with 1,658 additions and 1,496 deletions.
diff --git a/docs/Change_Log.md b/docs/Change_Log.md
diff --git a/docs/Change_Log.mdx b/docs/Change_Log.mdx
@@ -0,0 +1,9 @@
+---
+showTOC: false
+---
+
+# Change Log
+
+Discover the latest updates, new features, and bug fixes on the Discord Developer Platform. To join in on the conversation, join the [Discord Developers Server](https://discord.com/invite/discord-developers).
+
+<ChangeLog />
diff --git a/docs/change_log/2017-07-19-breaking-change-version-6.md b/docs/change_log/2017-07-19-breaking-change-version-6.md
@@ -0,0 +1,14 @@
+---
+title: "Breaking Change: Version 6"
+date: "2017-07-19"
+breaking: true
+---
+
+* [Channel](#DOCS_RESOURCES_CHANNEL/channel-object) Object
+  * `is_private` removed
+  * [`type`](#DOCS_RESOURCES_CHANNEL/channel-object-channel-types) is now an integer
+  * `recipient` is now `recipients`, an array of [user](#DOCS_RESOURCES_USER/user-object) objects
+* [Message](#DOCS_RESOURCES_MESSAGE/message-object) Object
+  * [`type`](#DOCS_RESOURCES_MESSAGE/message-object-message-types) added to support system messages
+* [Status Update](#DOCS_TOPICS_GATEWAY_EVENTS/update-presence-gateway-presence-update-structure) Object
+  * `idle_since` renamed to `since`
diff --git a/docs/change_log/2017-07-24-new-feature-audit-logs.md b/docs/change_log/2017-07-24-new-feature-audit-logs.md
@@ -0,0 +1,6 @@
+---
+title: "New Feature: Audit Logs"
+date: "2017-07-24"
+---
+
+Audit logs are here! Well, they've been here all along, but now we've got [documentation](#DOCS_RESOURCES_AUDIT_LOG/) about them. Check it out, but remember: with great power comes great responsibility.
diff --git a/docs/change_log/2017-08-03-breaking-change-default-channels.md b/docs/change_log/2017-08-03-breaking-change-default-channels.md
@@ -0,0 +1,11 @@
+---
+title: "Breaking Change: Default Channels"
+date: "2017-08-03"
+breaking: true
+---
+
+After today, we are changing how default channels function. The "default" channel for a given user is now the channel with the highest position that their permissions allow them to see. New guilds will no longer have a default channel with the same id as the guild. Existing guilds will not have their #general channel id changed. It is possible, if permissions are set in such a way, that a user will not have a default channel in a guild.
+
+We saw a use case in many servers where the previously-default #general channel was being repurposed as an announcement-only, non-writable channel for new members by using bots to clear the entire message history. Now, that channel can simply be deleted and re-created with the desired permissions. This change also allows dynamic default channels for users based on permissions.
+
+We are also rolling out a change in conjunction that will allow Discord to remember your last-visited channel in a guild across sessions. Newly-joined users will be directed to the guild's default channel on first join; existing members will return to whichever channel they last visited.
diff --git a/docs/change_log/2017-08-16-breaking-change-presence-activity-objects.md b/docs/change_log/2017-08-16-breaking-change-presence-activity-objects.md
@@ -0,0 +1,7 @@
+---
+title: "Breaking Change: Presence Activity Objects"
+date: "2017-08-16"
+breaking: true
+---
+
+The `type` field in the [activity object](#DOCS_TOPICS_GATEWAY_EVENTS/activity-object) for [Gateway Status Update](#DOCS_TOPICS_GATEWAY_EVENTS/update-presence) and [Presence Update](#DOCS_TOPICS_GATEWAY_EVENTS/presence-update) payloads is no longer optional when the activity object is not null.
diff --git a/docs/change_log/2017-09-10-new-feature-emoji-endpoints.md b/docs/change_log/2017-09-10-new-feature-emoji-endpoints.md
@@ -0,0 +1,6 @@
+---
+title: "New Feature: Emoji Endpoints"
+date: "2017-09-10"
+---
+
+[Emoji endpoints](#DOCS_RESOURCES_EMOJI/emoji-resource) have been added to the API. Bots can now manage guild emojis to their robo-hearts' content!
diff --git a/docs/change_log/2017-09-20-new-feature-channel-categories.md b/docs/change_log/2017-09-20-new-feature-channel-categories.md
@@ -0,0 +1,6 @@
+---
+title: "New Feature: Channel Categories"
+date: "2017-09-20"
+---
+
+Changes have been made throughout the documentation to reflect the addition of channel categories to Discord. These includes an additional field—`parent_id`—to the base [channel](#DOCS_RESOURCES_CHANNEL/channel-object) object and a new [channel category example](#DOCS_RESOURCES_CHANNEL/channel-object-example-channel-category).
diff --git a/docs/change_log/2017-10-16-breaking-change-api-gateway-below-v6-discontinued.md b/docs/change_log/2017-10-16-breaking-change-api-gateway-below-v6-discontinued.md
@@ -0,0 +1,7 @@
+---
+title: "Breaking Change: API & Gateway Below v6 Discontinued"
+date: "2017-10-16"
+breaking: true
+---
+
+[API](#DOCS_REFERENCE/api-versioning) and Gateway versions below v6 are now discontinued after being previously deprecated. Version 6 is now the default API and Gateway version. Attempting to use a version below 6 will result in an error.
diff --git a/docs/change_log/2017-11-09-new-feature-rich-presence.md b/docs/change_log/2017-11-09-new-feature-rich-presence.md
@@ -0,0 +1,12 @@
+---
+title: "New Feature: Rich Presence"
+date: "2017-11-09"
+---
+
+Rich Presence is now live and available for all developers! Rich Presence allows developers to closely integrate with Discord in a number of new, cool ways like:
+
+* Showing more information about a user's current game in their profile
+* Allowing users to post invitations to join their party or spectate their game in chat
+* Displaying "Spectate" and "Ask to Join" buttons on users' profiles
+
+For more information, check out our [Rich Presence site](https://discord.com/rich-presence). To get started on development, [read the docs](#DOCS_RICH_PRESENCE_OVERVIEW)!
diff --git a/docs/change_log/2018-01-03-semi-breaking-change-very-large-bot-sharding.md b/docs/change_log/2018-01-03-semi-breaking-change-very-large-bot-sharding.md
@@ -0,0 +1,7 @@
+---
+title: "Semi-Breaking Change: Very Large Bot Sharding"
+date: "2018-01-03"
+breaking: true
+---
+
+Additional sharding requirements and information for bots in over 100,000 guilds has been added. This requires a small change in numbers of shards for affected bots. See the [documentation](#DOCS_TOPICS_GATEWAY/sharding-for-large-bots) for more information.
diff --git a/docs/change_log/2018-01-23-deprecation-accept-invite-endpoint.md b/docs/change_log/2018-01-23-deprecation-accept-invite-endpoint.md
@@ -0,0 +1,6 @@
+---
+title: "Deprecation: Accept Invite Endpoint"
+date: "2018-01-23"
+---
+
+The [Accept Invite](#DOCS_RESOURCES_INVITE/) endpoint is deprecated starting today, and will be discontinued on March 23, 2018. The [Add Guild Member](#DOCS_RESOURCES_GUILD/add-guild-member) endpoint should be used in its place.
diff --git a/docs/change_log/2018-01-30-enhancement-get-guild-emoji-endpoint.md b/docs/change_log/2018-01-30-enhancement-get-guild-emoji-endpoint.md
@@ -0,0 +1,6 @@
+---
+title: "Enhancement: Get Guild Emoji Endpoint"
+date: "2018-01-30"
+---
+
+The [Get Guild Emoji](#DOCS_RESOURCES_EMOJI/get-guild-emoji) response now also includes a user object if the emoji was added by a user.
diff --git a/docs/change_log/2018-02-05-enhancement-new-message-properties.md b/docs/change_log/2018-02-05-enhancement-new-message-properties.md
@@ -0,0 +1,6 @@
+---
+title: "Enhancement: New Message Properties"
+date: "2018-02-05"
+---
+
+Additional `activity` and `application` fields—as well as corresponding object documentation—have been added to the [Message](#DOCS_RESOURCES_MESSAGE/message-object) object in support of our newly-released [Spotify integration](https://support.discord.com/hc/en-us/articles/360000167212-Discord-Spotify-Connection) and previous Rich Presence enhancements.
diff --git a/docs/change_log/2018-06-11-deprecation-rpc-online-member-count-and-members-list.md b/docs/change_log/2018-06-11-deprecation-rpc-online-member-count-and-members-list.md
@@ -0,0 +1,6 @@
+---
+title: "Deprecation: RPC online member count and members list"
+date: "2018-06-11"
+---
+
+We released server changes that allow guilds to represent an incomplete state of the member list in our clients, which results in inaccurate member lists and online counts over RPC. These fields are now deprecated and will now return an empty members array and an online count of 0 moving forward.
diff --git a/...change_log/2018-06-19-documentation-fix-list-of-open-dms-in-certain-payloads.md b/...change_log/2018-06-19-documentation-fix-list-of-open-dms-in-certain-payloads.md
@@ -0,0 +1,6 @@
+---
+title: "Documentation Fix: List of Open DMS in Certain Payloads"
+date: "2018-06-19"
+---
+
+The documentation has been updated to correctly note that the `private_channels` field in the [Ready](#DOCS_TOPICS_GATEWAY_EVENTS/ready) should be an empty array, as well as the response from `/users/@me/channels` for a bot user. This change has been in effect for a long time, but the documentation was not updated.
diff --git a/docs/change_log/2018-11-30-enhancement-user-object.md b/docs/change_log/2018-11-30-enhancement-user-object.md
@@ -0,0 +1,6 @@
+---
+title: "Enhancement: User Object"
+date: "2018-11-30"
+---
+
+The [User object](#DOCS_RESOURCES_USER/user-object) now includes two new additional fields, `premium_type` and `flags`. These can be used to know the Nitro status of a user, or determine which HypeSquad house a user is in.
diff --git a/docs/change_log/2018-12-11-documentation-dispatch-store-listings.md b/docs/change_log/2018-12-11-documentation-dispatch-store-listings.md
@@ -0,0 +1,6 @@
+---
+title: "Documentation: Dispatch Store Listings"
+date: "2018-12-11"
+---
+
+Dispatch documentation around store listings has been removed. Store pages for the Discord Store are now managed entirely within the [Developer Portal](https://discord.com/developers).
diff --git a/docs/change_log/2019-01-14-ask-to-join-rich-presence-sdk.md b/docs/change_log/2019-01-14-ask-to-join-rich-presence-sdk.md
@@ -0,0 +1,8 @@
+---
+title: "Ask to Join & Rich Presence SDK"
+date: "2019-01-14"
+---
+
+Ask to Join no longer requires approval or whitelisting to use. You are welcome to create in-game UI, but all Ask to Join requests are also now handled by the Discord overlay.
+
+There have also been some small additions to the Rich Presence SDK. The previously undocumented `UpdateHandlers()` function is now documented.
diff --git a/docs/change_log/2019-04-18-new-invite-object-fields.md b/docs/change_log/2019-04-18-new-invite-object-fields.md
@@ -0,0 +1,6 @@
+---
+title: "New Invite Object Fields"
+date: "2019-04-18"
+---
+
+The [Invite Object](#DOCS_RESOURCES_INVITE/invite-object) now includes two additional fields, `target_user` and `target_user_type`.
diff --git a/docs/change_log/2019-04-29-deprecation-of-discord-rpc-rich-presence-sdk.md b/docs/change_log/2019-04-29-deprecation-of-discord-rpc-rich-presence-sdk.md
@@ -0,0 +1,6 @@
+---
+title: "Deprecation of Discord-RPC Rich Presence SDK"
+date: "2019-04-29"
+---
+
+The [Discord-RPC](https://github.com/discord/discord-rpc) implementation of Rich Presence has been deprecated in favor of Discord's new GameSDK. If you're interested in using Rich Presence, please read our [SDK Starter Guide](#DOCS_DEVELOPER_TOOLS_GAME_SDK/getting-started) and check out the relevant functions in the [Activity Manager](#DOCS_DEVELOPER_TOOLS_GAME_SDK/activities).
diff --git a/docs/change_log/2019-05-29-added-info-around-nitro-boosting-experiment.md b/docs/change_log/2019-05-29-added-info-around-nitro-boosting-experiment.md
@@ -0,0 +1,6 @@
+---
+title: "Added Info Around Nitro Boosting Experiment"
+date: "2019-05-29"
+---
+
+Additional information has been documented to support [Server Nitro Boosting](https://support.discord.com/hc/en-us/articles/360028038352-Server-Boosting). This includes the addition of a few [message types](#DOCS_RESOURCES_MESSAGE/message-object-message-types), as well as some [new fields on guilds](#DOCS_RESOURCES_GUILD/guild-object-premium-tier). Please note that this feature is currently under experimentation, and these fields may be subject to change.
diff --git a/docs/change_log/2019-06-19-additional-team-information.md b/docs/change_log/2019-06-19-additional-team-information.md
@@ -0,0 +1,6 @@
+---
+title: "Additional Team Information"
+date: "2019-06-19"
+---
+
+Additional information around Teams has been added to both the API and the documentation. The [Teams](#DOCS_TOPICS_TEAMS/teams) page now includes information about the team and team member objects. Additionally, the [Get Current Application Information](#DOCS_TOPICS_OAUTH2/get-current-bot-application-information) endpoint now returns a `team` object if that application belongs to a team. That documentation has also been updated to includes fields that were missing for applications that are games sold on Discord.
diff --git a/docs/change_log/2019-07-18-bot-tokens-for-achievements.md b/docs/change_log/2019-07-18-bot-tokens-for-achievements.md
@@ -0,0 +1,6 @@
+---
+title: "Bot Tokens for Achievements"
+date: "2019-07-18"
+---
+
+You can now use Bot tokens for authorization headers against the HTTP API for [Achievements](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Achievements.md#the-api-way).
diff --git a/docs/change_log/2019-08-12-more-precise-rate-limits.md b/docs/change_log/2019-08-12-more-precise-rate-limits.md
@@ -0,0 +1,6 @@
+---
+title: "More Precise Rate Limits"
+date: "2019-08-12"
+---
+
+You can now get more precise rate limit reset times, via a new request header. Check out the [rate limits](#DOCS_TOPICS_RATE_LIMITS/) documentation for more information.
diff --git a/docs/change_log/2019-08-22-changes-to-special-channels.md b/docs/change_log/2019-08-22-changes-to-special-channels.md
@@ -0,0 +1,6 @@
+---
+title: "Changes to Special Channels"
+date: "2019-08-22"
+---
+
+News Channels are now changed to Announcement Channels. Developer License owners will continue to get access to them (both existing and new). Underlying channel type (GUILD\_NEWS = 5) remains the same.
diff --git a/docs/change_log/2019-11-14-gamesdk-version-2.5.5.md b/docs/change_log/2019-11-14-gamesdk-version-2.5.5.md
@@ -0,0 +1,8 @@
+---
+title: "GameSDK Version 2.5.5"
+date: "2019-11-14"
+---
+
+We've shipped some updates to the GameSDK, including support for Linux as well as the IL2CPP backend system for Unity. These changes also fixed a bug in the [`SetUserAchievement()`](https://github.com/discord/discord-api-docs/blob/legacy-gamesdk/docs/game_sdk/Achievements.md#setuserachievement) method.
+
+Get the latest at the top of the [Getting Started](#DOCS_DEVELOPER_TOOLS_GAME_SDK/step-1-get-the-sdk) documentation. If you're looking for help interacting with the GameSDK or want to report a bug, join us on the [official Discord](https://discord.gg/discord-developers).
diff --git a/docs/change_log/2019-11-27-gamesdk-version-2.5.6.md b/docs/change_log/2019-11-27-gamesdk-version-2.5.6.md
@@ -0,0 +1,6 @@
+---
+title: "GameSDK Version 2.5.6"
+date: "2019-11-27"
+---
+
+Fixed a bug from the 2.5.5 release that caused network handshakes to fail, resulting in no networking data being sent. The networking manager and integrated lobby networking should be full operational again after updating.
diff --git a/docs/change_log/2019-12-06-ip-discovery-updates.md b/docs/change_log/2019-12-06-ip-discovery-updates.md
@@ -0,0 +1,6 @@
+---
+title: "IP Discovery Updates"
+date: "2019-12-06"
+---
+
+Updated our [IP discovery message](#DOCS_TOPICS_VOICE_CONNECTIONS/ip-discovery). The old message is deprecated and will be removed in the future.
diff --git a/docs/change_log/2020-02-14-gateway-intents.md b/docs/change_log/2020-02-14-gateway-intents.md
@@ -0,0 +1,16 @@
+---
+title: "Gateway Intents"
+date: "2020-02-14"
+---
+
+We've added documentation around a brand new feature: [Gateway Intents!](#DOCS_TOPICS_GATEWAY/gateway-intents) Gateway Intents are a great way to specify which events you want to receive from our gateway. Go on, save yourself some bandwidth and CPU usage.
+
+Using Intents will change the behavior of some existing events and commands, so please refer to:
+
+* [Guild Create](#DOCS_TOPICS_GATEWAY_EVENTS/guild-create)
+* [Request Guild Members](#DOCS_TOPICS_GATEWAY_EVENTS/request-guild-members)
+* [Guild Member Add](#DOCS_TOPICS_GATEWAY_EVENTS/guild-member-add)
+* [Guild Member Remove](#DOCS_TOPICS_GATEWAY_EVENTS/guild-member-remove)
+* [Guild Member Update](#DOCS_TOPICS_GATEWAY_EVENTS/guild-member-update)
+* [Presence Update](#DOCS_TOPICS_GATEWAY_EVENTS/presence-update)
+* [List Guild Members](#DOCS_RESOURCES_GUILD/list-guild-members)
diff --git a/docs/change_log/2020-02-26-rich-presence-spectate-approval.md b/docs/change_log/2020-02-26-rich-presence-spectate-approval.md
@@ -0,0 +1,6 @@
+---
+title: "Rich Presence Spectate Approval"
+date: "2020-02-26"
+---
+
+The [Spectate](#DOCS_DEVELOPER_TOOLS_GAME_SDK/onactivityspectate) functionality of Rich Presence no longer requires whitelisting or approval.
diff --git a/docs/change_log/2020-03-02-new-invite-events-and-reactions-endpoint.md b/docs/change_log/2020-03-02-new-invite-events-and-reactions-endpoint.md
@@ -0,0 +1,11 @@
+---
+title: "New Invite Events and Reactions Endpoint"
+date: "2020-03-02"
+---
+
+We've added a new endpoint for deleting all reactions of a specific emoji from a message, as well as some new invite and reaction gateway events. Read more:
+
+* [Delete All Reactions for Emoji](#DOCS_RESOURCES_MESSAGE/delete-all-reactions-for-emoji)
+* [Invite Create](#DOCS_TOPICS_GATEWAY_EVENTS/invite-create)
+* [Invite Delete](#DOCS_TOPICS_GATEWAY_EVENTS/invite-delete)
+* [Message Reaction Remove Emoji](#DOCS_TOPICS_GATEWAY_EVENTS/message-reaction-remove-emoji)
diff --git a/docs/change_log/2020-03-03-new-allowed-mentions-object.md b/docs/change_log/2020-03-03-new-allowed-mentions-object.md
@@ -0,0 +1,8 @@
+---
+title: "New Allowed Mentions Object"
+date: "2020-03-03"
+---
+
+We've added a way to specify mentions in a more granular form. This change also begins the start of a 60 day deprecation cycle on legacy mention behavior. Read more:
+
+* [Allowed mentions object](#DOCS_RESOURCES_MESSAGE/allowed-mentions-object)
diff --git a/docs/change_log/2020-04-24-new-properties-on-guild-members-chunk-event.md b/docs/change_log/2020-04-24-new-properties-on-guild-members-chunk-event.md
@@ -0,0 +1,6 @@
+---
+title: "New Properties on Guild Members Chunk Event"
+date: "2020-04-24"
+---
+
+The [Guild Members Chunk](#DOCS_TOPICS_GATEWAY_EVENTS/guild-members-chunk) gateway event now contains two properties: `chunk_index` and `chunk_count`. These values can be used to keep track of how many events you have left to receive in response to a [Request Guild Members](#DOCS_TOPICS_GATEWAY_EVENTS/request-guild-members) command.
diff --git a/docs/change_log/2020-05-11-legacy-mention-behavior-deprecation.md b/docs/change_log/2020-05-11-legacy-mention-behavior-deprecation.md
@@ -0,0 +1,6 @@
+---
+title: "Legacy Mention Behavior Deprecation"
+date: "2020-05-11"
+---
+
+The legacy mention behavior for bots is now removed, and granular control of mentions should use the [Allowed Mentions](#DOCS_RESOURCES_MESSAGE/allowed-mentions-object) API moving forwards.
diff --git a/docs/change_log/2020-07-28-new-permission-fields.md b/docs/change_log/2020-07-28-new-permission-fields.md
@@ -0,0 +1,6 @@
+---
+title: "New Permission Fields"
+date: "2020-07-28"
+---
+
+Documented `permissions_new`, `allow_new`, and `deny_new` as string-serialized permission bitfields.
diff --git a/docs/change_log/2020-09-24-api-and-gateway-v8.md b/docs/change_log/2020-09-24-api-and-gateway-v8.md
@@ -0,0 +1,47 @@
+---
+title: "API and Gateway V8"
+date: "2020-09-24"
+---
+
+We've introduced API and Gateway v8! Changes are noted throughout the documentation, and you can also read [this commit in our docs repo](https://github.com/discord/discord-api-docs/commit/545ff4a7883e5eee7ee91d19a5e5d760a0730033) for a full diff.
+
+The changes are:
+
+* API and Gateway v8 are now available. v6 is still the default for the time being.
+* [Gateway Intents](#DOCS_TOPICS_GATEWAY/gateway-intents) are now required
+* Removed `guild_subscriptions` in identify in favor of [Gateway Intents](#DOCS_TOPICS_GATEWAY/gateway-intents).
+* All permissions have been converted to strings-serialized numbers. As such, `permissions_new`, `allow_new`, and `deny_new` have been removed
+* The `game` field has been removed. If you need a direct replacement, you can instead reference the first element of `activities`
+* Channel Permission Overwrite `type`s are now numbers (0 and 1) instead of strings ("role" and "member"). However due to a current technical constraint, they are string-serialized numbers in audit log `options`.
+* `embed_enabled` and `embed_channel_id` have been removed. Use `widget_enabled` and `widget_channel_id` instead.
+* Form body errors have been improved to include more helpful messaging on validation. [See more here](#DOCS_REFERENCE/error-messages)
+* The `Retry-After` header value and `retry_after` body value is now based in seconds instead of milliseconds (e.g. `123` means 123 seconds)
+* The `X-RateLimit-Precision` header is no longer respected. `X-RateLimit-Reset` and `X-RateLimit-Reset-After` are always returned at millisecond precision (e.g. `123.456` instead of `124`)
+* Bots no longer receive [Channel Create Gateway Event](#DOCS_TOPICS_GATEWAY_EVENTS/channel-create) for DMs
+* `delete-message-days` is no longer available. Use `delete_message_days`.
+* Removed `roles`, `premium_since`, and `nick` from [Presence Update Gateway Event](#DOCS_TOPICS_GATEWAY_EVENTS/presence-update)
+* Removed some [integration object](#DOCS_RESOURCES_GUILD/integration-object) fields for Discord application integrations
+* Removed `include_applications` from [Get Guild Integrations](#DOCS_RESOURCES_GUILD/get-guild-integrations). Application integrations are always included.
+* The following deprecated routes have been removed for better naming conventions:
+
+Removed in favor of `/guilds/<guild_id>/widget`:
+
+* `/guilds/<guild_id>/embed`
+
+Removed in favor of `/guilds/<guild_id>/widget.json`:
+
+* `/servers/<guild_id>/embed.json`
+* `/servers/<guild_id>/widget.json`
+* `/guilds/<guild_id>/embed.json`
+
+Removed in favor of `/guilds/<guild_id>/widget.png`:
+
+* `/guilds/<guild_id>/embed.png`
+
+Removed in favor of `/channels/<channel_id>/messages/bulk-delete`:
+
+* `/channels/<channel_id>/messages/bulk_delete/`
+
+Removed in favor of `/invites/<code>/`:
+
+* `/invite/<code>/`
diff --git a/docs/change_log/2020-10-27-gateway-v6-intent-restrictions.md b/docs/change_log/2020-10-27-gateway-v6-intent-restrictions.md
@@ -0,0 +1,9 @@
+---
+title: "Gateway v6 Intent Restrictions"
+date: "2020-10-27"
+---
+
+The v6 gateway now applies the restrictions for gateway intents. This means the new chunking limitations are now in effect, regardless of intents being used. See [Request Guild Members](#DOCS_TOPICS_GATEWAY_EVENTS/request-guild-members) for further details.
+Additionally, if privileged intents are not enabled in the application dashboard the bot will not receive the events for those intents.
+
+All other intents are always enabled by default unless specified otherwise by the identify payload. We have made a support article to explain some of the changes and resulting issues with more details: [Gateway Update FAQ](https://dis.gd/gwupdate)
diff --git a/docs/change_log/2020-11-13-stickers.md b/docs/change_log/2020-11-13-stickers.md
@@ -0,0 +1,6 @@
+---
+title: "Stickers"
+date: "2020-11-13"
+---
+
+Stickers are now documented as part of the [message](#DOCS_RESOURCES_MESSAGE/message-object) object.
diff --git a/docs/change_log/2020-11-16-inline-replies.md b/docs/change_log/2020-11-16-inline-replies.md
@@ -0,0 +1,12 @@
+---
+title: "Inline Replies"
+date: "2020-11-16"
+---
+
+Inline Replies have been added to our documentation. They behave differently in v6 and v8, so be cautious in your implementation:
+
+* Inline replies are type `19` in v8, but remain type `0` in v6
+* You can now add a `message_reference` on message create to create a reply
+* A new field `referenced_message` has been added to the [Message Object](#DOCS_RESOURCES_MESSAGE/message-object)
+* A new field `replied_user` has been added to the [Allowed Mentions Object](#DOCS_RESOURCES_MESSAGE/allowed-mentions-object)
+* [Message Create](#DOCS_TOPICS_GATEWAY_EVENTS/message-create) gateway event is guaranteed to have a `referenced_message` if the message created is a reply. Otherwise, that field is not guaranteed.
diff --git a/docs/change_log/2020-12-15-slash-commands-and-interactions.md b/docs/change_log/2020-12-15-slash-commands-and-interactions.md
@@ -0,0 +1,12 @@
+---
+title: "Slash Commands and Interactions"
+date: "2020-12-15"
+---
+
+Slash Commands are here! There's a *lot* to cover, so go check out specific documentation under [Slash Commands](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/).
+
+Slash Commands include some new features for webhooks as well:
+
+* Webhooks can now update previously-sent messages from the same webhook using [Edit Webhook Message](#DOCS_RESOURCES_WEBHOOK/edit-webhook-message) and [Delete Webhook Message](#DOCS_RESOURCES_WEBHOOK/delete-webhook-message)
+
+This PR also documents the `application` field on the `READY` gateway event, which is a partial [application object](#DOCS_RESOURCES_APPLICATION/application-object) containing `id` and `flags`.