[Warlock] Update destro apex r1 behavior#11002
Merged
nyterage merged 1 commit intosimulationcraft:midnightfrom Feb 21, 2026
Merged
[Warlock] Update destro apex r1 behavior#11002nyterage merged 1 commit intosimulationcraft:midnightfrom
nyterage merged 1 commit intosimulationcraft:midnightfrom
Conversation
596cd69 to
afa4151
Compare
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.
After testing, it turns out that rank 1 of the destro apex talent actually has a per-target 10% proc chance rather than a per-cast 25% proc chance, so updating the default proc rate as well as when the roll occurs.
Need to further validate that FnB doesn't reduce chance with additional targets but initial testing suggests that it doesn't.