Incinerate & Mayhem

Support Bug Report
1

There seems to be a massive issue with Incinerate currently! I was playing M+ Karazhan, and minding my own business, having fun — when suddenly, out of the corner of my eyes, I saw a pack of wild mobs rushing towards us at full speed.

I thought it strange, considering the tank hadn’t pulled them, but decided to simply attribute it to a misclick from someone else.

During Moroes, the fight with 4 mini-bosses which you need to CC, we had a bit of a raging issue from the tank barking that the mini bosses were being pulled out of CC somehow by someone. Again, I moved on.

When it happened a third time, a ninja pull in a rather flat room with mobs everywhere (the courtisans), that’s when I noticed what caused it. -ONE- of my Incinerate flames was hitting targets that weren’t in combat, or anywhere NEAR the person I was targeting, that’s what was pulling. I apologized at the end of the run, stating I hadn’t ever seen that bug in Shadowlands before, and I’d played Warlock in the past.

I then did some tests with target dummies and regular dungeons, and realised both Incinerate and Mayhem were guilty of the same problem.

TLDR: Incinerate & Mayhem is targeting enemies OUT of combat + Mayhem is doing the exact same thing. They both also affect CC’d targets. Either that, or Mayhem Havoc is hitting targets that Incinerate has accidentally pulled.

If Mayhem snaps out of CCs, I can understand it, because it is a talent choice and I should be picking Havoc on CC fights.

But Incinerate and Mayhem both affecting targets out of combat is an unfathomably bad idea from a design point of view. It should,

(check if in combat = yes/no = if yes, target. — If no = do not target)
(check if in crowd control = yes/no = if yes, target. — If no = do not target)

Thank you very much for the fix on this in DF!

2

Also have experienced this same issue, with Mayhem activating and sending chaos bolts to Narnia…

3

Possibly related (and maybe intended? I’m not a very experienced Warlock player), I was attacking Doomwalker this week on my Dest Lock with Mayhem and as is fairly usual there were a number of flagged players around from the other faction (people hitting up Doomwalker between Korrok runs).

I never flag on my alts and so I assume nothing I do will interact with those flagged players. But suddenly as I cast Incinerate off shoots a blast at one of those guys and I’m flagged up and in an unanticipated and extremely unwanted PvP situation.

4

I don’t believe its an intended feature of the passive. It would make a cool, very dynamic talent become something that is never chosen. For it to launch into crowds of NPC’s that haven’t been pulled makes for very dangerous situations in M+. It makes you wonder how the talent is choosing targets? On the third boss of Iron Docks specifically, it activated and began throwing chaos bolts into the CC’d venomspitting add.

5

I could understand Mayhem snapping things/people out of CCs in M+, it would unfortunately mean it is rarely ever taken, but it might be an intended ‘drawback’ to it.

But Incinerate, being a generator, choosing targets out of combat/CC’d? And same with Mayhem?

Absolutely not.

Incinerate should NOT target enemies in CCs (or limit the range of it), and Mayhem should NOT target enemies out of combat. Enemies in combat but CC’d?

Means I’ll never use the talent, but acceptable.

But enemies OUT of combat?

It makes the talent literally a ZERO CHANCE pick on any serious content beyond LFR.

6

I had Incinerate spread to an Alliance player during Doomwalker (I am assuming this player had Warmode on, I however, did not) it resulted in my whole party being flagged for PvP and us all taking damage from Alliance AOE, which in turn probably flagged those Alliance players for PvP. Like the original poster, I had no idea that this would occur or work in this manner. So I went to the training dummies in my toon’s garrison and started experimenting with the spells and talents one by one and quickly discovered Mayhem was the culprit.

I never fully trust prepatch changes because of stuff like this. Mayhem is dead to me until I see a blue post saying this is fixed.