In Application Commands, allow role
options to be restricted to either managed
or non-managed
#6390
Unanswered
cssinate
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'm working on a bot that monitors an external service for some event. Users in a server can choose to subscribe to the bot, in which case the bot assigns them a specific role, and then mentions that role when the event happens.
I thought I might allow the server administrator to configure which role gets that assignment. So I created an Application Command that takes an option of
"type": 8
to accept a role. Among the auto-complete list of roles the user can select from is the managed role that belongs to the bot. This is not a valid role to assign to users who want to subscribe to the notification.In a similar way to how "channel" options (
"type": 7
) have an optional parameter"channel_types"
(which takes an array of allowed channel types), it would be great to either have a boolean optional parameter"allow_managed"
or"allowed_roles"
with a new "Role Types" enum withmanaged: 0, unmanaged: 1
or something along those lines.Beta Was this translation helpful? Give feedback.
All reactions