Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sage stole my gender (Roles being removed when adding a new role) #293

Open
iclyn-taero opened this issue Sep 2, 2022 · 1 comment
Open
Assignees
Labels
bug Something isn't working Priority Low Should be the lowest priority of developers

Comments

@iclyn-taero
Copy link

When using the drop down menu to add new roles that are released like when you guys added the ctf role. When I click the button to add ctf, Sage removes all other roles like my pronouns for that category. It also happens when I add a new class. My other classes get removed so I have to click the new class and the other classes I am in to make sure I don't get the role removed

@sbrugel
Copy link
Contributor

sbrugel commented Sep 2, 2022

this problem owes to a bug/limitation with Discord, it has been like this since we introduced dropdowns. The client doesn't cache/save what items you select in a dropdown, so when you restart Discord it will look as if you have selected nothing, and the handler assumes that what you select is the ONLY stuff you want, removing any roles you have that aren't selected.

Will this be fixed any time soon? I highly doubt it. There is unfortunately not an intuitive solution we know (as of yet) of that doesn't involve an ungodly amount of extra code and/or refactoring. Keep in mind we have to account for people deciding to intentionally, manually remove roles they have already selected, doing that and accounting for roles people want to keep that aren't selected would be difficult. Least we can hope is that discord realizes this is an issue and caches any selected items.

Temporary solution: If you lose any roles unintentionally, you can just re-add them by re-intereacting with the dropdown, as you said.

@sbrugel sbrugel added the bug Something isn't working label Sep 2, 2022
@bladetyr bladetyr self-assigned this Jan 5, 2023
@bladetyr bladetyr added the Priority Low Should be the lowest priority of developers label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority Low Should be the lowest priority of developers
Projects
None yet
Development

No branches or pull requests

3 participants