Allow us to disable the @everyone
role from popping up for ROLE and MENTIONABLE command option types
#4524
Replies: 2 comments 1 reply
-
+1. Now that we have a good UI to collect input we don't need to check users' input (it's a role or not) as the validation is happening on the client side. But this everyone role is causing the same issue again. We need to check and show an error message to the user and they need to rerun the command. There are so many cases where we don't need everyone's role so such an option will be cool. |
Beta Was this translation helpful? Give feedback.
-
I think this could even fit into a similar option restriction as
It would be extra cool to have a few extra utility types too, but there would be some logistics to figure out for them as they overlap the above mentioned types. These would be:
I'm sure there's additional role types that would make sense, but that's what I can think of off the top of my head |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
One of the features of the ROLE and MENTIONABLE command option types is that you can select the
@everyone
"role" as an option. While that may have some use cases, so it should stay, I would love if we had aninclude_everyone_meta_role
boolean (defaulttrue
) or similar that lets us disable it from showing up in the clients (as it would skip a check in our code that the role id provided isn't the guild id).Why to keep the
@everyone
role showing up as an option in the first placeSay you have a command that gives points to any members with the role provided, and you want to give everyone 69 points. You can provide
@everyone
and that will match, well, everyone.Why should
include_everyone_meta_role
existConsider an admin command that adds the specified role to a member. You can't give a member
@everyone
as the role "doesn't exist", and it wouldn't make sense to try to add it or show it.Beta Was this translation helpful? Give feedback.
All reactions