From 41bbf766f568d628673ffdeed55bd3ea9473baf7 Mon Sep 17 00:00:00 2001 From: ayu Date: Fri, 1 Mar 2024 19:51:18 +0000 Subject: [PATCH] add `MANAGE_GUILD` requirement for guild prune --- docs/Change_Log.md | 10 ++++++++++ docs/resources/Guild.md | 4 ++-- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/Change_Log.md b/docs/Change_Log.md index fc41abb3e0..7fc33f3d5a 100644 --- a/docs/Change_Log.md +++ b/docs/Change_Log.md @@ -1,5 +1,15 @@ # Change Log +## Guild Prune Requiring `MANAGE_GUILD` + +#### March 15, 2024 + +> danger +> This entry includes breaking changes + +The [Get Guild Prune Count](#DOCS_RESOURCES_GUILD/get-guild-prune-count) and [Begin Guild Prune](#DOCS_RESOURCES_GUILD/begin-guild-prune) +endpoints now require the `MANAGE_GUILD` permission alongside the existing `KICK_MEMBERS` requirement ₍^ >ヮ<^₎ .ᐟ.ᐟ + ## Enforced Nonces on Create Message Endpoint #### February 12, 2024 diff --git a/docs/resources/Guild.md b/docs/resources/Guild.md index a2e98c637f..e95470ea7b 100644 --- a/docs/resources/Guild.md +++ b/docs/resources/Guild.md @@ -1165,7 +1165,7 @@ Delete a guild role. Requires the `MANAGE_ROLES` permission. Returns a 204 empty ## Get Guild Prune Count % GET /guilds/{guild.id#DOCS_RESOURCES_GUILD/guild-object}/prune -Returns an object with one `pruned` key indicating the number of members that would be removed in a prune operation. Requires the `KICK_MEMBERS` permission. +Returns an object with one `pruned` key indicating the number of members that would be removed in a prune operation. Requires the `MANAGE_GUILD` and `KICK_MEMBERS` permissions. By default, prune will not remove users with roles. You can optionally include specific roles in your prune by providing the `include_roles` parameter. Any inactive user that has a subset of the provided role(s) will be counted in the prune and users with additional roles will not. @@ -1178,7 +1178,7 @@ By default, prune will not remove users with roles. You can optionally include s ## Begin Guild Prune % POST /guilds/{guild.id#DOCS_RESOURCES_GUILD/guild-object}/prune -Begin a prune operation. Requires the `KICK_MEMBERS` permission. Returns an object with one `pruned` key indicating the number of members that were removed in the prune operation. For large guilds it's recommended to set the `compute_prune_count` option to `false`, forcing `pruned` to `null`. Fires multiple [Guild Member Remove](#DOCS_TOPICS_GATEWAY_EVENTS/guild-member-remove) Gateway events. +Begin a prune operation. Requires the `MANAGE_GUILD` and `KICK_MEMBERS` permissions. Returns an object with one `pruned` key indicating the number of members that were removed in the prune operation. For large guilds it's recommended to set the `compute_prune_count` option to `false`, forcing `pruned` to `null`. Fires multiple [Guild Member Remove](#DOCS_TOPICS_GATEWAY_EVENTS/guild-member-remove) Gateway events. By default, prune will not remove users with roles. You can optionally include specific roles in your prune by providing the `include_roles` parameter. Any inactive user that has a subset of the provided role(s) will be included in the prune and users with additional roles will not.