Skip to content

[Havoc] Preemptive Strike procs on Furious Throws glaive#11114

Merged
ToppleTheNun merged 1 commit intosimulationcraft:midnightfrom
taherbert:fix/dh-preemptive-strike-furious-throws
Mar 9, 2026
Merged

[Havoc] Preemptive Strike procs on Furious Throws glaive#11114
ToppleTheNun merged 1 commit intosimulationcraft:midnightfrom
taherbert:fix/dh-preemptive-strike-furious-throws

Conversation

@taherbert
Copy link
Contributor

@taherbert taherbert commented Mar 7, 2026

Preemptive Strike wasn't proccing on the Furious Throws extra glaive from Screaming Brutality auto glaives. The main throw glaive correctly triggered Preemptive Strike (immediate), but the Furious Throws glaive (delayed 400ms) did not.

Fixed by scheduling a delayed Preemptive Strike event alongside the Furious Throws delayed event in throw_glaive_t::execute().

Affects all throw glaive sources (manual cast + all 3 Screaming Brutality paths: blade dance, death sweep, slash proc).

Verified in-game

Every individual glaive (including Furious Throws) triggers Preemptive Strike on first hit (not bounces). For example, Blade Dance with Screaming Brutality + Furious Throws producing 2 secondary glaives yields 6 Preemptive Strike hits: primary glaive, FT from primary, secondary glaive 1, FT from secondary 1, secondary glaive 2, FT from secondary 2.

Sim comparison (4 targets, Havoc Aldrachi Reaver, 5000 iterations)

Metric Before After
Total DPS 16,395,140 16,688,808 (+1.8%)
Preemptive Strike pDPS 174,713 339,325 (~2x)
Preemptive Strike % of total 1.07% 2.03%

Exhaustive talent interaction testing

Ran debug sims across 18 talent combinations (PS, FT, SB, SG, SC individually, all pairs, key triples, and all together) to verify no duplicate procs or missing interactions.

@taherbert taherbert changed the title [DH] Preemptive Strike procs on Furious Throws glaive [Havoc] Preemptive Strike procs on Furious Throws glaive Mar 7, 2026
@ToppleTheNun ToppleTheNun merged commit 1efef79 into simulationcraft:midnight Mar 9, 2026
55 of 56 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants