[UPDATED JANUARY 24] Dragonflight: 10.0.5 Content Update Notes

I was going to say, the absolute unwashed audacity of that take was staggering.

Blizzard mostly uses beta keys as a marketing tactic, not a solicitation of actual feedback. And while arguably a lot of people only go into the beta to see the shiny new stuff, a large number of people have also dug in and given Blizzard a wealth of live, realtime, incredibly well-researched feedback in every beta only to have it resoundingly ignored starting in about BFA.

Some of it can be written off as people just wanting the class that they play to be overtuned, but there were so many critical issues brought up by testers that made it to the live game with each expansion that they had to eventually, grudgingly, resentfully walk back after people’s general good will had already been damaged. Timegates, Pathfinder systems promising flight at some future indeterminate point without further details, alternate currency droughts like azerite and anima, going all-in on confusing and pointless mission tables, the Covenant-switching ripcord, dungeon and raid balance issues, broken abilities, people have done the math for them multiple times only to have it completely ignored because some new system is someone’s baby and they won’t allow it to be touched until the player base is in full revolt.

Looking at the current beta forum, yeah, since the 10.0.5 update is mostly a class balancing patch most of the feedback is about that, and that never goes…well. I generally don’t play at a level where I would have a horse in that race. But historically, people give a ton of really good feedback in the betas and I’ve rarely seen anything change as a result of it.

4 Likes

There are frequently-reported bugs with class abilities that have been documented by testers for weeks and are going live on Tuesday.

Because Blizzard doesn’t read any of the feedback.

8 Likes

can we not fix some of the bugged stuff in dragon flight before you worry about past stuff like the archivist codex. seriously like the horde /alliance achieve that’s not counting and hasn’t since launch. cosmetics really fix the bugs before adding more junk. and a lot more this happens every time we get new anything and after years and years of the game being out you’d think that would be the concern i do not care about more cosmetics blizzard. Save your comments for something important not bashing me for having any opinion what’s so ever.

What does a mage rework look like? Never mind, we will find out next season. When everyone finally gives up on the class. All 5 of us that are still playing it that is…

1 Like

That’s great but when are you going to acknowledge all the broken world quests we keep telling you about and you actually fix them not just say you did and a few weeks later it comes back.

Wow! You’re not kidding!! It’s very inconvenient when you can’t see your quests. The only way to have them show is to find an area with dark background so you can read them. Pretty bad planning…as in…none!

Is this patch going to fix the level dungeon bug where some bosses take 10mins to kill and the constant overscaling causing groups to wipe over and over?

Is this patch going to fix the stutter introduced to the client in prepatch?

Is this patch going to fix the plethora of bugs while doing WQ, interacting with NPCs, Timer icons disappearing, unbearable lag in zones while events are going on, multiple interface bugs, sometimes all profiles completely deleting themselves…

I could go on. Is this patch going to fix these problems?

2 Likes

Please don’t let Mage Tower get face-rolled; keep it’s difficulty level from the SL release in place.

Also, PTR fails every time I try to copy the evoker over (let me do other toons). Did Evoker get added to the challenges at all? Or are they just up in the wind?

What is the reason behind not allow level 60+ to stop experience gains?

I am glad it isnt just me that has those issues you mentioned in the last part of your post. Please fix blizz

I’m incredibly shocked at the gutting of MM’s burst. I’ve seen interactions in PVP where it was arguably overpowered, but seriously, removing DT altogether is just poorly thought. Does Blizzard not have a team (or, multiple teams) of people dedicated to brainstorming effective fixes? The removal of DT is just wild, unthought, half-baked, and short-sighted.

Allowing MM to choose when ES would proc from AoE is a decent enough idea. It doesn’t seem extremely impactful to me with the pacing of M+ and VotI as it’s pretty rare for it to proc at inconvenient times. However, having that control still feels decent. Removing DT, however? That’s an outright nerf on a spec that was arguably performing exactly as it should have been.

I’ve been the victim of being one tapped by Rapid Fire by numerous hunters over the weekend.

2 Likes

No you haven’t. DTRF doesn’t even do 250k dmg on the 0armor 0versa PvP dummy in Valdrakken.

Maybe you got Chakram+ES+Volley+DT+RF+KS’d but not “onetapped” (six globals and a 3 second channel lol).

Many specs in the game are capable of more burst with fewer buttons (Ret, Dev, Ele) and they didn’t have their offensive cooldown simply deleted.

Edit: unless you’re wearing leveling greens

1 Like

This.

That’s what baffles me so much. MM has been a really good benchmark as it really seems to have been performing exceptionally well. Not overpowered, not underpowered. It consistently performed as you’d expect DPS to perform. If this was a reaction to PVP, I’m in awe that other specs are allowed to maintain a higher burst potential while DT is removed. No matter how much I try, I cannot reconcile it in my head. The logic (or lack thereof) does not compute with me.

I promise you the Warlock profile I’m posting on right now would burst you down quicker than my MM alt (and you’d be CC’d for the entire duration of the burst). If your gauge is a level 69 being “one tapped” by a geared level 70, that’s a foolish gauge.

1 Like

Nothing for BM Hunters? :frowning:

1 Like

No im judging it by being 396 in instanced PvP and being literally one tapped by an MM with rapid fire. 396 isnt exactly super high as I just made this guy but still its one button.

Then read this, as it’s exactly right. You’re not dying to one DTRF.

Also, it’s not one button. DT is one button and it deals 0 damage. RF is another button and actually performs the attack (which is empowered by DT). There’s a GCD in between as well. That’s a far cry from “it’s still one button”. As mentioned, you’re not dying to one DTRF, either. You just aren’t.

Even if it’s a DT + RF + KS + KS, that’s a lucky proc, 3 second channel, multiple GCDs, and a good amount of time to pop defensives. Considering MM’s opener is ES, I’d be shocked if anyone immediately opened with DTRF as well. That claim alone is outlandish and extremely difficult to believe. Tsavoka’s above rotation is more likely to be correct with Chakrum + ES + Volley (which would apply more ES) + DT + RF + KS.

1 Like

You can’t just say “hunters”. It’s MM only, and as a hunter main I agree with DT removal. When I can burn a target down in two globals I can’t imagine it’s very fun for the other players. Mainly in arena.

1 Like

Problem is we don’t really have anything else to offer… outside of immunity to interupts other range just bring more dmg and more durability.

Would be nice if we could get a [dragonridable] macro condition that returns true when Dragonriding is available so we can stop using API scripts or the fact that mounts are off the GCD to make our mount macros work.

1 Like