From c98a98a8d11f97a4f2ad57ddadf4d2bd537fab09 Mon Sep 17 00:00:00 2001 From: DevilXD Date: Sat, 27 Jul 2019 19:45:13 +0200 Subject: [PATCH 1/2] Permission hierarchy is now clearer --- docs/topics/Permissions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/Permissions.md b/docs/topics/Permissions.md index eb1dd1a85f..e7d052fdab 100644 --- a/docs/topics/Permissions.md +++ b/docs/topics/Permissions.md @@ -62,7 +62,7 @@ Note that these internal permission names may be referred to differently by the How permissions apply may at first seem intuitive, but there are some hidden restrictions that prevent bots from performing certain inappropriate actions based on a bot's highest role compared to its target's highest role. A bot's or user's highest role is its role that has the greatest position value in the guild, with the default @everyone role starting at 0. Permissions follow a hierarchy with the following rules: -* A bot can grant roles to other users that are of a lower position than their highest role. +* A bot can grant roles to other users that are of a lower position than it's own highest role. * A bot can edit roles of a lower position than its highest role, but it can only grant permissions it has to those roles. * A bot can only sort roles lower than its highest role. * A bot can only kick/ban users whose highest role is lower than the bot's highest role. From 4c3e6fc1692ef38fb54bd2ff440f38b467d1b67a Mon Sep 17 00:00:00 2001 From: DevilXD Date: Sat, 27 Jul 2019 22:27:33 +0200 Subject: [PATCH 2/2] Updated per suggestion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Florian Spieß --- docs/topics/Permissions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/Permissions.md b/docs/topics/Permissions.md index e7d052fdab..a953979b98 100644 --- a/docs/topics/Permissions.md +++ b/docs/topics/Permissions.md @@ -62,7 +62,7 @@ Note that these internal permission names may be referred to differently by the How permissions apply may at first seem intuitive, but there are some hidden restrictions that prevent bots from performing certain inappropriate actions based on a bot's highest role compared to its target's highest role. A bot's or user's highest role is its role that has the greatest position value in the guild, with the default @everyone role starting at 0. Permissions follow a hierarchy with the following rules: -* A bot can grant roles to other users that are of a lower position than it's own highest role. +* A bot can grant roles to other users that are of a lower position than its own highest role. * A bot can edit roles of a lower position than its highest role, but it can only grant permissions it has to those roles. * A bot can only sort roles lower than its highest role. * A bot can only kick/ban users whose highest role is lower than the bot's highest role.