Fix Rupture sometimes applying multiple times #8320
Merged
Conversation
This file contains 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
LocalIdentity
approved these changes
Nov 18, 2024
LocalIdentity
changed the title
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.
Fixes #8259 .
Description of the problem being solved:
The global Rupture debuff was not previously not assigned an effect name. Because of that, multiple instances were allowed to apply, as they had different active skills as their source.
I just assigned an effect name, which caused the standard mergeBuff / match functions to be able to properly identify duplicates and only apply the highest values instead.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
https://pobb.in/70IX7nLOCxOZ
Before screenshot:
After screenshot: