Slash Commands Global Permissions

[vertex-admin]

Description

We need a "GuildOnly" option for global slash commands, which would disable global slash commands from being used in DM channels.

Why This is Needed

Many developers want to be able to disable global slash commands in DM channels, but keep them open for @everyone in guilds. Currently, if you want achieve this, you have to:

i) Set DefaultPermission to false when creating your slash command
ii) Loop over all of your guilds and edit the command permissions to enable it for the @everyone role

There needs to be an easier way to do this, because you get ratelimited when doing the above. A "GuildOnly" option when creating a slash command would make life so much easier and decrease API traffic by tons from people who are trying to do this.

[DyDestroyer1027]

i) Set DefaultPermission to false when creating your slash command
ii) Loop over all of your guilds and edit the command permissions to enable it for the @everyone role

This is not the only ways to prevent slash commands from being used in DMs. You can just check the raw interaction object to see if it contains a guild_id, if it doesn't, it probably got used in DMs. (some libraries also have methods to check if the command is used in a dm. DiscordJS has interaction.inGuild() for example.)

[vertex-admin]

Yes, but it's confusing to the user if you just reject slash commands without a guild ID. You can respond to these interactions with an error message, something like "Please use this command in a guild", but again, it's more intuitive to have them greyed out altogether.

[ckohen]

as a good to know, that loop won't even catch all guilds, so the correct way to do it is the second method. You can have your commands in a guild without your bot, meaning there is no way to tell they exist there.