Linked Roles - String Option #5760
Replies: 3 comments 3 replies
-
Just string can causes some problems. And probably most of people won't know the correct values. So I think we should be able to add some options to select like this: [
{
"key": "gamerank",
"name": "Rank In Game",
"description": "Rank a user has in game",
"type": 9,
"options": [
"Rank 1",
"Rank 2",
"Rank 3"
]
}
] |
Beta Was this translation helpful? Give feedback.
-
+1 to the idea of having specific choices to select from. I'm planning to build an integration for people who have subscribed to me on various platforms, and I want to be able to link specific roles to specific tiers. I feel like integrations similar to this- where roles are based on a limited set of strings rather than something like a random number- would be best handled with some kind of string choices instead of the current workarounds which would be either:
even if this was purely built with games in mind, there are tons of games with non-numbered ranks. likewise, there are tons of other situations where string options would be useful. i was actually surprised to see that this wasn't included on launch 😅 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Suggestion
ability to have a string thing but the metadata/requirement could act like a boolean
In Action
Requirements
PUT
request tohttps://discord.com/api/v10/applications/clientid/role-connections/metadata
This would be more for display, but in requirements it would act more as a boolean
Metadata body
PUT
request tohttps://discord.com/api/v10/users/@me/applications/clientid/role-connection
not sure if that makes sense, thanks!
Beta Was this translation helpful? Give feedback.
All reactions