Fix Storm Cascade Trigger being affected by accuracy#9248
Merged
LocalIdentity merged 1 commit intoPathOfBuildingCommunity:devfrom Nov 15, 2025
Merged
Fix Storm Cascade Trigger being affected by accuracy#9248LocalIdentity merged 1 commit intoPathOfBuildingCommunity:devfrom
LocalIdentity merged 1 commit intoPathOfBuildingCommunity:devfrom
Conversation
LocalIdentity
approved these changes
Nov 15, 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
2 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.
Closes #9224
Description of the problem being solved:
According to this linked issue the Storm Cascade Trigger is triggered on attack rather than hit which means it should not be affected by hit chance.
This pr simply adds the missing flag to the trigger config.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
See linked issue