Stop support gems from using minionTypes to determine compatibility with minion attack skills#4628
Merged
LocalIdentity merged 1 commit intoPathOfBuildingCommunity:devfrom Dec 8, 2022
Conversation
…determine whether a support gem can support a given minion attack.
QuickStick123
added
bug
LocalIdentity
approved these changes
Dec 8, 2022
This was referenced Dec 12, 2022
This was referenced Mar 5, 2023
3 tasks
This was referenced Jun 22, 2025
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
3 participants
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.
Fixes #4497 .
Description of the problem being solved:
Minion skills such as ChaosElementalCascadeSummoned and MinionInstability would use minionSkillTypes from the summoning gem to determine compatibility instead of the skillTypes from the minion skill it self.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
https://pobb.in/v2X-xHNx3_jaBefore screenshot:
After screenshot: