Custom input components #3704
Unanswered
Logan9312
asked this question in
API Feature Requests & Ideas
Replies: 3 comments
-
I think, A would be good option for my purpose, and I feel like C) is the best approach. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This is already "planned". (It will be implemented, but we don't have much info about it) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Already planned as seperate component. |
Beta Was this translation helpful? Give feedback.
0 replies
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'd love to have a custom option for on-message interactions, as it would allow us to much more easily get and use user input.
For example, right now If I want to edit a message based on user input, there's a couple ways to do it. Either get the message somehow by forcing the user to run a slash command with message ID and channel, then running a get message function, that returns the message you want to edit. That's not super user friendly, especially if they don't know how to grab the message ID. Otherwise, I could store the message somewhere, and have a bot update that message when they run a specific command. That works too but it complicates things.
It would be much better if we could add a custom input on message, I'm thinking any of the following would be good:
A) A button that when clicked transforms into a text bot for input
B) An option on select menus that transforms into a text bock for input when selected.
C) A separate interaction type which is just custom input, and linked to the message somehow.
Another good use case for something like this could be using a custom input select menu to survey users upon joining a guild, or set a custom role name for themselves. I think this would be an extremely useful feature to have
Beta Was this translation helpful? Give feedback.
All reactions