Nether precision 11.0.5 fix and gone and sayonara

I am so glad that the damn bug is getting fixed and those who wanted the bug well yall had your chance during this whole 11.0.2 patch and I am glad 11.0.5 is fixing the damn thing and so sayonara nether precision bug.

  • Fixed an issue that allowed players to double dip the last stack of Nether Precision with a spell-queued Arcane Barrage.

They just turned it into a talent so the play style isn’t changing at all, we just have to find a spare talent point somewhere to do what we were already doing.

Good luck with that because I bet they will prevent people like you to circumvent.

1 Like

Circumvent what? They literally made it a talent. Blizzard wants that play style, they just wanted it in a way that wasn’t a bug. So that’s what they did.

Well, I guess you people gotten your way again but this time there is an option but I am damn glad that the bug has been resolved in 11.0.5. Atleast they found a way to please both sides.

I mean, it’s already optional now. You don’t have to do it, it’s just a damage loss to not use it. Just like not using the new talent will also be a damage loss.

I really don’t understand the point of this thread.

Damage loss really? They most likely make it comparable in DPS when all said and done in terms of balancing. You can defend the bug and all but I bet there are those like me that will be glad that it’s fixed.

Yes, that talent will almost certainly be the optimal choice and not taking it will be a DPS loss.

So, I don’t know what this thread is actually about. Do you just hate bugs on principle or something? Because they’re just taking the bug and making it a talent.

I doubt it since most talents will get balanced before it gets released. And to think it will be OP like please.

No offense, but it’s clear you don’t really play Mage for anything higher than a Heroic dungeon, so maybe leave the more advanced Mage details to people who are more experienced.

1 Like

I guess you’re offended that the original bug is now fixed and made into a separate talent that will be balanced before the release of the patch.

Do you even play mage? Not to mention you sound like a child through this whole post. Regardless, they turned it into a talent so the play style is the same

1 Like

The only child here is those who would name call others. So please, entertain me with such words. As I said before the new talent will most likely than not will be tuned in a way that will be similarly in numbers. So, continue with your self obsessed bias beliefs.

That is not at all how the talent system works. Every talent isn’t balanced against all the other talents. Some talents are a lot stronger than other talents and they are intentionally designed that way.

Blizzard can’t even balance the specs or hero talents against each other and you expect them to balance individual talents against each other? What?

We’ve been double-dipping on damage increasing buffs through spellqueuing since at least Shadowlands (see: Radiant Spark), possibly longer (but my memory isn’t that good). If double-dip spellqueuing was a bug it’s a bug that Blizzard has allowed to exist for almost 4 years. At that point it’s not a bug, its a feature.

The complaint isn’t that Blizzard is fixing a bug that hurts our DPS. The complaint is that they’re changing something that the community has considered a feature and that they’re singling out one particular spec at a time where said spec feels really good to play, and the original change did not include a way to ensure that the rotation stays the same.

The only difference now is that it’s on a different proc and arcane was a little overtuned compared to other classes, so they finally decided to fix a 4 year old problem. Personally, I’m glad they managed to find a way to fix it, I just wish they could manage our talent tree a bit better so that I didn’t have to give up something I currently have to regain what they’re taking away from me.

10/10 Rage Bait.

2 Likes

But there is nothing sinister about that. They’re only now realizing they don’t like that interaction and calling it a “bug” because this is the first time it’s been an issue. They left it in place before because it wasn’t relevant and likely not even on their radar. There are dozens if not hundreds of those types of unintended interactions that exist in the game and many of them have been around for far longer. But they don’t get looked at until they become a problem and spotlight falls on them which typically happens when a spec starts to suddenly overperform at least in part due to those unintended interactions. And when that happens the first thing they do, and rightly so, is to try and prune away the unintended interactions before doing the blanket nerfs. That’s exactly what’s happened here and it was 100% the right call.

What’s more, all of this is completely moot because they not only addressed everyone’s concerns but also made the desirable playstyle objectively better all at the cost of one measly talent point. The talent trees are a mess already so if we get real for a second no one will even notice the difference.

No one can accuse me of being a defender of Blizzard, and indeed, the overwhelming majority of my posts on these forums have been critical of their handling of the game. Something that I continue to do all the time. But the outrage and indignation I’ve seen over this, frankly, nonissue has been completely unwarranted and overblown.

All your posts just sound like you’re jelly of Mages somehow.