Seperate Manage Roles and Manage Permissions permissions

[BrammyS]

Recently I came across a weird issue with where my bot was saying it was missing the Manage Roles permission even though it had it on the role. After some digging it turned out that the channel where the interaction was used in had denied the Manage Permissions. This caused the app_permissions field to exclude the Manage Roles permission. Because they use the same value.

I will have to calculate the permission myself with the roles that the bot has to avoid this, resulting in an unnecessary API call. This could be avoided if the Manage Permissions permission had a different value.

[MinnDevelopment]

I think what you really want here is a separate field for role permissions in addition to the app_permissions field. A lot of permissions can be denied at channel level by overwrites, which is by design and important for permission management (see muted roles).

[BrammyS]

I think what you really want here is a separate field for role permissions in addition to the app_permissions field. A lot of permissions can be denied at channel level by overwrites, which is by design and important for permission management (see muted roles).

Yes that would solve this issue as well. But I still think that the Manage Roles and Manage Permissions permissions are too different for them to have the same value. Because right now the app_permissions field is telling me that I can not create roles and that I can't edit the permissions of the current channel. Even though only the latter part is valid.