Gaming breaking bug: Unyielding Will talent no longer correctly interacts with Spellwarden PVP talent, we cannot remove magic cc with AMS in rated PVP and I do not think this is intentional at all. None of the patch notes / Hotfixes mentioned this.
Second bug is that Abomination no longer continuously apply plague, and it appears to be on a proc basis. I remember a couple of weeks ago if your abomination is up you don’t have to worry about plague falling off. Either I misremembered this or this change was added without any notes.
People have been posting frequently here and the bug forum regarding this change in abomination all last week no longer continuously applying plague. I have a sneaky suspicion Bliz stealth nerfed it to only apply it at the initial cast, which is basically what I’m seeing from it since I have to hit outbreak once plague falls off even with abom up.
I’m glad I wasn’t misremembering this. I almost gaslit myself.
I’m not sure if bliz intended to shadow-nerf DK this way or someone messed up, but I do think the unable to remove magic using Unyielding Will talent and Spellwarned PVP talent is for sure unintentional.
They’ve had the issue like this in the past where if a spell is upgraded by talent or PVP talent, then it has a different spell ID and doesn’t interact normally with other talent/spells/glyphs/etc.
This garbage better not be intentional. The documented nerfs were already super heavy-handed. To wreck the abom in the process is absolutely ridiculous. Unyielding Will also being a mess doesn’t help either.
Unyielding Will literally loses 3s and solo at key moment at higher rating. Abomination issue makes the gameplay so much worse and forces us to reapply dots on regular basis in burst window. UH DK already has a lot of buttons to push, resources and debuff to track. It also means mastery build is much worse given how long GCD is. The worst part about this is Blizz made zero announcement about this, took me a few losses to figure this out. If they fix that they better announce it in hotfix notes, otherwise I would have no way to tell since I no longer run Unyielding Will talent.
I’m not going to hold my breath on it getting fixed. Seems like the sort of thing they’ll just “conveniently” forget to address, particularly given the nature of the nerfs they already handed out.
They drove the spec into the ground because of all the meaningless padding from the dot cleave in lower rating brackets, never bothering to look at the damage inflicted on individuals. Bearing this in mind, I have a hard time thinking the abom thing wasn’t intentional. The Unyielding change, however, I could believe wasn’t intended. …Still doubt it’ll get fixed. Hope I’m wrong.
I was looking at 3s ratings. DK is a popular class without that many people at the top. War only has 1 person in top 100. I feel like the nerf is people whining about dueling when the horsemen only have 1 target. My problem is that fourms are managed by community managers, we don’t know if they see these posts, and I don’t know if they will pass any info to the devs.
I won’t claim to know one way or the other for a fact, but I’ll certainly say the things I’ve witnessed over the years regarding balancing choices and the like would seem to indicate the devs either don’t get told what’s here or just don’t care.
There are class designers and there are coders. With bugs it is the fault of the coders, unless there’s a conspiracy to shadow-nerf through the use of bugs… It’s 2024 so you may never know lol
I would also suggest putting in a ticket or posting on the bug forums as anything you post here will most certainly go unseen.
Also, I should mention, I did see abom apply plague after the initial summons but it took him a few seconds once plague fell off completely, which is a huge dps loss, so it’s totally borked. I also still don’t really see him applying it to new targets once they get in range. On queen abom just refuses to put plague on the roots to break people out, I always have to outbreak with abom up which should not be the case and wasn’t the case 2 weeks ago.