Fix Imbued Support Control buggy indexing#9763
Merged
LocalIdentity merged 2 commits intoPathOfBuildingCommunity:devfrom Apr 16, 2026
Merged
Conversation
stop click through of the GemSelectControls behind the Imbued dropdown
LocalIdentity
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the problem being solved:
The index for the gemSelectControl for the imbuedSupport was not being updated enough/correctly, which causes issues of the logic/calcs for the tooltip to replace other existing gems in the displayGroup instead of always being an extra gem tacked on to the end. Updating the index in real time before the calcs.
I'm also adding some code the ProcessInputEvents to stop the click-through of the controls behind the Imbued Support dropdown. If it's too crude we can remove the changes to that file for now and take a look later, but it's not a good experience currently.
Link to a build that showcases this PR:
Before screenshot:
After screenshot: