From 8c748936ce2d9999ebd91b14cb56956d84fc7384 Mon Sep 17 00:00:00 2001 From: Shay Date: Wed, 7 Jun 2023 09:32:05 -0700 Subject: [PATCH] fix docs --- docs/Change_Log.md | 23 +++++++++++++++-------- docs/Reference.md | 4 ++-- 2 files changed, 17 insertions(+), 10 deletions(-) diff --git a/docs/Change_Log.md b/docs/Change_Log.md index fa3234b13d..9790821367 100644 --- a/docs/Change_Log.md +++ b/docs/Change_Log.md @@ -1,13 +1,13 @@ # Change Log -#### May 3, 2023 - ## Unique usernames on Discord +#### May 3, 2023 + > warn -> This change also impacts bot usernames. The impact on apps, and how the migration to the new username system will happen, is detailed on the [Developer Help Center article](https://dis.gd/app-usernames). Dates around migration to the new system will be communicated soon. +> Bot users will stay on the legacy username system for now. More details can be found on the [Developer Help Center article](https://dis.gd/app-usernames). -Discord’s username system is changing. Discriminators are being removed and new, unique usernames (`@name`) and display names are being introduced. You can read more details about how changes to the username system affects non-bot users in the [general Help Center article](https://dis.gd/usernames). To learn how it impacts bot users specifically, you can read the [Developer Help Center article](https://dis.gd/app-usernames). +Discord’s username system is changing. Discriminators are being removed and new, unique usernames and display names are being introduced. You can read more details about how changes to the username system affects non-bot users in the [general Help Center article](https://dis.gd/usernames). To learn how it impacts bot users specifically, you can read the [Developer Help Center article](https://dis.gd/app-usernames). This changelog focuses only on the technical changes to be aware of to update your app's code. @@ -44,20 +44,27 @@ For bot users, the display name will be the same as the application's name (defi ### Default avatars -For users with migrated accounts, default avatar URLs will be based on the user ID instead of the discriminator. The URL can now be calculated using `(user_id >> 22) % 5`. +For users with migrated accounts, default avatar URLs will be based on the user ID instead of the discriminator. The URL can now be calculated using `(user_id >> 22) % 6`. -#### April 14, 2023 +## Add Join Raid and Mention Raid fields + +#### May 05, 2023 + +- Add Auto Moderation `mention_raid_protection_enabled` [trigger_metadata](#DOCS_RESOURCES_AUTO_MODERATION/auto-moderation-rule-object-trigger-metadata) field for the `MENTION_SPAM` [trigger_type](#DOCS_RESOURCES_AUTO_MODERATION/auto-moderation-rule-object-trigger-types). If this field and its parent `MENTION_SPAM` rule are enabled, Auto Moderation provides baseline detection against sudden spikes in mention activity that are normally indicative of mention raids. +- Add `safety_alerts_channel_id` [guild](#DOCS_RESOURCES_GUILD/guild-object) field and [`RAID_ALERTS_DISABLED` guild feature flag](#DOCS_RESOURCES_GUILD/guild-object-guild-features) which are associated with join raid protection ## Bot users added to all new apps +#### April 14, 2023 + Starting today, [bot users](#DOCS_TOPICS_OAUTH2/bot-vs-user-accounts) will be added to all newly-created apps. Settings and configuration options for bot users remain the same, and can still be accessed on the **Bot** page within your [app's settings](https://discord.com/developers/applications). If your app doesn't need or want a bot user associated with it, you can refrain from adding the [`bot` scope](#DOCS_TOPICS_OAUTH2/shared-resources-oauth2-scopes) when installing your app. -#### April 6, 2023 - ## Interaction Channel Data +#### April 6, 2023 + Interactions now contain a `channel` field which is a partial channel object and guaranteed to contain `id` and `type`. We recommend that you begin using this channel field to identify the source channel of the interaction, and may deprecate the existing `channel_id` field in the future. See the [interaction documentation](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/interaction-object) for more details. ## Add Auto Moderation custom_message Action Metadata Field diff --git a/docs/Reference.md b/docs/Reference.md index f9954bda45..aa1dfe2ba2 100644 --- a/docs/Reference.md +++ b/docs/Reference.md @@ -318,7 +318,7 @@ Discord uses ids and hashes to render images in the client. These hashes can be | Guild Discovery Splash | discovery-splashes/[guild_id](#DOCS_RESOURCES_GUILD/guild-object)/[guild_discovery_splash](#DOCS_RESOURCES_GUILD/guild-object).png | PNG, JPEG, WebP | | Guild Banner | banners/[guild_id](#DOCS_RESOURCES_GUILD/guild-object)/[guild_banner](#DOCS_RESOURCES_GUILD/guild-object).png \* | PNG, JPEG, WebP, GIF | | User Banner | banners/[user_id](#DOCS_RESOURCES_USER/user-object)/[user_banner](#DOCS_RESOURCES_USER/user-object).png \* | PNG, JPEG, WebP, GIF | -| Default User Avatar | embed/avatars/[user_id](#DOCS_RESOURCES_USER/user-object).png \*\* \*\*\* | PNG | +| Default User Avatar | embed/avatars/[index](#DOCS_RESOURCES_USER/user-object).png \*\* \*\*\* | PNG | | User Avatar | avatars/[user_id](#DOCS_RESOURCES_USER/user-object)/[user_avatar](#DOCS_RESOURCES_USER/user-object).png \* | PNG, JPEG, WebP, GIF | | Guild Member Avatar | guilds/[guild_id](#DOCS_RESOURCES_GUILD/guild-object)/users/[user_id](#DOCS_RESOURCES_USER/user-object)/avatars/[member_avatar](#DOCS_RESOURCES_GUILD/guild-member-object).png \* | PNG, JPEG, WebP, GIF | | Application Icon | app-icons/[application_id](#DOCS_RESOURCES_APPLICATION/application-object)/[icon](#DOCS_RESOURCES_APPLICATION/application-object).png | PNG, JPEG, WebP | @@ -335,7 +335,7 @@ Discord uses ids and hashes to render images in the client. These hashes can be \* In the case of endpoints that support GIFs, the hash will begin with `a_` if it is available in GIF format. (example: `a_1269e74af4df7417b13759eae50c83dc`) -\*\* In the case of the Default User Avatar endpoint, the value for `user_id` in the path should be `(user_id >> 22) % 5` +\*\* In the case of the Default User Avatar endpoint, the value for `index` in the path should be `(user_id >> 22) % 6` \*\*\* In the case of the Default User Avatar and Sticker endpoints, the size of images returned is constant with the "size" querystring parameter being ignored.