Slash Commands Permission relies on Send Messages

[macdja38]

Description
While at least in the user facing interface Giving a user Slash Commands does not allow them to use Slash Commands in a channel where they cannot send messages.

It would be nice for command only channels to be able to restrict users to using Slash Commands but not sending messages. Especially with Ephemeral messages that never really get sent this would be super useful for large communities with roles channels that allow users to self assign roles. It would be significantly nicer if we didn't need to have a bot delete user messages.

[macdja38]

Adding to this since someone asked me a question within discord.

Users while sometimes well intention-ed likely won't discover slash commands are available on their own. I like the idea of having a #roles channel on my discord with self assignable roles users can choose from. Right now I either need to write a crappy / slightly user hostile script that deletes non slash command messages in that chat... or have a #roles chat along with a #bot-commands chat... and point users from the #roles chat to #bot-commands. It's not exactly super user friendly.

This change suggests allowing users with Use Slash Commands but not Send Messages to Use Slash Commands... but not send messages. Potentially the bar could say something like "Use Command" and bring up a picker / restricted text field that can only send slash commands.

[msciotti]

This is currently intentional, but something we can revisit once the new permissions system is deployed.

[jgoldshlag]

Now that the new permissions system is out, can this be considered? My bot would also greatly benefit from this

[AnotherCat]

Could this be revisited now permissions v2 is out? oops sorry, didn't refresh 😅

[tylovejoy]

This would be awesome to have for many reasons.
My use cases are having a channel dedicated to instruction on how to use specific command(s) and being able to use them there (with ephemeral responses) so the channel doesn't get flooded with responses.

Another case is having a specific channel used for displaying user inputted data in a specific format. This currently requires another channel to be designated as a "submission" channel.

I'd love it if this was revisited.

[Tolga1452]

i see there is still no update on that even though the new permission system has been deployed. i know this is not a big issue but i think this can be done by allowing some overrides to make the command usable. i made an entire system just for this use case and now i need to move it to a slash command, which will require to enter the message id and this is not even user-friendly

[Tolga1452]

Talking about context menu commands btw, they are having the same issue