Enabling/Disabling global commands per guild

[Zoddo]

A nice addition in parallel to Application Commands Permissions v2 would be the ability to completely disable a global command per guild.

Why is this needed?

I see a few cases where applications would want to control commands availability in a guild:

• Premium commands: You may want to be able to hide these commands unless the guild has subscribed to a premium plan.
• Multipurpose bots: These bots usually provide switches in their own dashboard to enable or disable a whole feature. For example, if such a bot has moderation features but the guild doesn't use them and has disabled this feature, you will want to hide all commands related to moderation.

Why not use commands permissions?

Application Commands permissions aren't the optimal solutions for these use cases, because :

• With the current v2 implementation, applications may not be able to update the permissions when needed, as this is currently locked behind a user OAuth2 scope (the user may revoke the application's access in its settings or may lose the required permissions to update commands permissions in the guild; this is going to be a pain to handle)
• Owners and administrators always have permission to run any command. So, setting permissions to deny everyone to execute the command is not enough.

Why not use guild commands for commands that need to be disabled?

Guild commands may sound like a solution at first glance, but this won't scale. If you need to update a command (which may happen even more often than currently with the upcoming release of commands localization), you will now have to iterate over potentially thousands of guilds, if not more, to make this update. This defeats the purpose of global commands.

How this may be implemented?

A simple boolean is probably enough.
For example, PATCH /applications/{application.id}/guilds/{guild.id}/commands/{command.id} may accept an enabled: false property when provided a global command ID. A default_enabled property on the global command definition may also be nice to register commands that should be disabled by default.

This should be accessible with a bot token (or client credential token with applications.commands.update scope), like for creating and deleting application commands.

UI-wise, a disabled command should be hidden from the "selector" in the chat input. I believe it should also be hidden from the Integrations page in the server settings (like if the command didn't exist). This would help to declutter the list of commands, especially with multipurpose bots.