Required Permissions field for application commands

[VelvetToroyashi]

I just want to preface this by saying if this is a duplicate of another discussion, I apologize. The closest thing I could find was this one.

As it stands right now, application commands (Slash commands, Context menus) have a very primitive permissions system.

With slash commands (and to an extent context menus) you're limited to either setting it to be disabled globally, or updating the command retroactively to allow specific roles/users.

But for large bots, and also large servers, this is unideal for obvious and non-obvious reasons.

The lesser obvious of this is that not only does this require extra API calls, but it requires manually checking every role in a server (if you choose to support every role, though my knowledge of how default_permission works may be a bit limited), which isn't always feasible. Not to mention that the basis on which the roles are determined for to update the command with aren't concrete; granted, it's not too often that role permissions change on a server, but those roles won't always exist, and new roles could be added that also satisfy a permission-based requirement, but that requires another API call, as well as foreknowledge that the role exists/got updated.

It'd be nice to have an extra field when creating/updating application commands that specifies the required permissions for the command to be used, essentially acting as a more refined default_permission. This would allow dynamic access to application commands, based on whatever permissions the application sees fit for that context.

[VelvetToroyashi]

I forgot to mention that this is based on the fact that many pre-existing, text-based command frameworks offer some sort of permission-based restriction of commands, but with application commands, the UI presented for disallowed commands is far superior than giving the illusion a command can be used, only to send an error message when that command is attempted.

[AnotherCat]

Permissions are mentioned in the "Moderation" section of the api plan announcement. #3581
afaik that's as much detail as we have so far

[VelvetToroyashi]

Yeah I was informed on Discord that like normal I can't read