You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dropdown before removing gems
Dropdown after moving gems
showing without dropdown
It seems to work with or without anything else in the build. It's easiest to demonstrate with awakened gems.
I think its probably tied to incomplete UI updating on gem deletion (moving the row up, but not doing so for all elements), in part because the affected listboxes are correct for the gem that was previously in that row.
The no listbox image is attached to show that there is something populating a normally empty and disabled listbox after removing the link
The text was updated successfully, but these errors were encountered:
Thank you for reporting an issue.
Before reporting a bug, please make sure that you are running the latest version.
You can get the latest version number from CHANGELOG.md
Please try to fill in as much of the template below as you're able.
What happened?
The alternate quality listbox became incorrectly associated after removing a link from the setup
What were you trying to do?
Delete Links from skill setup
What steps will reproduce the bug?
Remove a gem that is not the bottom row gem from the setup.
Does it reproduce every time?
Yes
Provide a build code:
https://pastebin.com/YpeHLX0t
Screenshots:
Dropdown before removing gems



Dropdown after moving gems
showing without dropdown
It seems to work with or without anything else in the build. It's easiest to demonstrate with awakened gems.
I think its probably tied to incomplete UI updating on gem deletion (moving the row up, but not doing so for all elements), in part because the affected listboxes are correct for the gem that was previously in that row.
The no listbox image is attached to show that there is something populating a normally empty and disabled listbox after removing the link
The text was updated successfully, but these errors were encountered: