Summary:
The Fury Warrior, Mountain Thane, hero talent Thunder Blast does not trigger from Bloodthirst benefiting from the multi target Whirlwind buff.
Description:
The Thunder Blast talent states that Bloodthirst has a 35% chance to trigger Thunder Blast. However it seems that this only works if Bloodthirst is striking a single target. If Bloodthirst benefits from Whirlwind, striking multiple targets, Thunder Blast never procs.
Reproduction Steps:
- Select the Improved Whirlwind talent
- Strike a target with Whirlwind
- Strike a target with Bloodthirst
- Repeat steps 1-3 multiple times (Thunder Blast never triggers)
Strike a target multiple times with Bloodthirst without whirlwind, and Thunder Blast will Trigger.
I’ve tried this with Whirlwind and Bloodthirst probably 40 times and never once received a proc. It’s possible that I’m just very very unlucky. I know that Slayer is the more common choice, but I suspect this issue is causing a massive drop in damage for Fury Mountain Thane, especially for multi target damage.
1 Like
BIG if true.
Each strike should potentially proc Thunder Blast. (So long as you’re hitting 4 targets it SHOULD be 100%). Going to test this now.
I’m not sure if it’s because I’m hitting training dummies but I’ve done this probably 60 times now and I can’t get a single Thunder Blast proc from multi target Blood Thirst. I wonder if I have another talent interacting with this?
I just did 12 more, zero procs. That’s a VERY low 35%.
I did 10 Bloodthirst just now with Whirlwind buff on multiple targets and got 2/10 Thunder Blast proc.
Not nearly close to what it should be, but it does trigger…
I did another 15 Bloodthirst without the Whirlwind buff and got 4 Triggers.
It seems to not include the additional Targets being Hit by Bloodthirst through the Whirlwind buff, which is very weird and should be fixed for sure. Definitely a bug there.
This does not appear to be the case; since being brought up in the Discord, I and multiple other players have confirmed that Thunder Blast does trigger when hitting multiple targets with Bloodthirst.
I also have confirmed the proc rate does average to 35%, though please note that’s per cast, not per target hit. It’s just a 35% chance when you press BT, not 35% chance for each target, or it would be nearly guaranteed to trigger when hitting 5 targets.
1 Like
I think there’s definitely a bug. There seems to be some type of interaction (maybe talent?) that doesn’t play nicely with that talent. If there’s a way to upload a video I would be happy to. I’m testing it now and after around 15 Blood Thirst, not a single one proced Thunder Blast. I also have Logs from Details showing the number of BloodThirst / Whirlwind and zero Thunder Blasts.
Mine is in no way 35% per cast. The majority of times that I’m in combat, I’ve casted Bloodthirst/Bloodbath 10+ times with 0 Thunder Blast Procs.
I cast bloodthirst 1 time and it didn’t trigger, so I’m just gonna say it has a 0% proc chance. I hope you understand that 10 casts is in no way significant.
It’s pretty consistent. There is no way it has a 35% proc chance if I am continuously casting Bloodthirst/Bloodbath during combat and it does not proc at all during combat, no matter how often I am casting it.
It’s a 35% proc chance and its functioning properly.
Then how can i consistently cast Bloodthirst/Bloodbath 10+ times with no proc? I have to cas it around 15 times before it gets a proc. Half the time I end up casting Avatar again before it procs, and I am casting Bloodthirst on cooldown.
Its been working properly as far as I can tell.
Maybe its bloodbath thats not proccing it? I havent tested it myself
Bloodthirst and Bloodbath both proc it, both when and when not cleaved. The bug appears more invasive, and has been tested using several talent setups by players who report it working and those who don’t with no change in behavior.
The only thing I’ve found as a potential fix is (first backing up) nuking the WTF folder. I have no idea why this works, as that should have absolutely no bearing on a proc, but it has been observed to fix the issue for at least a couple players… until the bug resurfaces after an indeterminate amount of time.