Select Menu Persistence #4827
Unanswered
paperclover
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.
-
It would be very nice if the per-user state of a select menu for messages persisted past refreshes/devices, as currently that state is not saved anywhere.
Example Use Case: Role selection menus.

I've had this select menu for a while, but now that I'm revisiting these types of interfaces, and trying to make a public bot to do these role menus, I've been thinking about this more. I've noticed most people don't get confused about it, though a couple people asked why their preference disappeared in the select menu.
An alternative to this would be having the Select Menu be in an ephemeral message or modal (when selects get added there), where I can customize the
default
based on what's stored in a database (or for the role selections, just observe the active roles).Beta Was this translation helpful? Give feedback.
All reactions