Difficulty of pinging a role using slashcommands. #3776
Unanswered
Mitmocc
asked this question in
API Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have found it incredibly tedious how permissions are handled with slashcommands in regards of trying to mention and ping a role.
The problem is that the initial reply to a slashcommand will ignore the bots permissions and instead default to the public role.
This means the bot is only able to ping a role that is allowed to be pinged by the public role.
You can't defer and then mention the role either, because its considered an edit and doesn't ping.
The only alternative is therefore to reply to the interaction and then send another message to the channel containing the mention. Which is very awkward, having to reply and send a message, then potentially delete the useless reply.
A possible solution would be to either fix the initial reply permissions to inherit the bots permission instead of the public role if the bot is present. Or to not count the first reply after deferring as an edit.
I feel this should be addressed if we are going to be forced to use slashcommands in the future.
Beta Was this translation helpful? Give feedback.
All reactions