Legacy Raid Boss Health Scaling Is Hosed

Honestly, the health pools don’t matter IF the legacy buff is adjusted to scale up our damage accordingly. The legacy buff for Legion just isn’t working properly. It’s either not tuned nearly high enough, or is just broken (it’s not mitigating incoming damage enough either).

I just ran my Alliance shaman alt through LFR Antorus. A couple fights I barely squeaked through. At 163 ilvl. This is ridiculous.

2 Likes

Absolutely correct, but the health issue does show just how little thought went into all of this, and the failure to adjust the Legion legacy buff to account for the lack of thought just further makes this a complete joke. It’s purely disgusting at this point.

1 Like

What really ticks me off the most about this is I honestly doubt it would be a huge lift for them to just add the debuff to Legion raids that have been added to other legacy raids already…and they’ve had ample opportunity to toss them into the sometimes 3-5 “hotfixes” they put out almost every single day…and nothing. Crickets.

1 Like

Yet another day without a blue in any of the threads.

1 Like

Oh, fun…this scaling issue is also affecting wintergrasp. The wall health was not properly changed when 9.0 changed things, so it’s now impossible for offense to ever win.

1 Like

Same, I have no clue why it is so difficult suddenly figuring out how to apply that de-buff to legacy raids. Still hoping this gets fixed for fellow mog hunters!

1 Like

For fun I went into LFR Aggy last night to see if any changes were made and to my surprise: ok not surprised, no changes.

Wishful thinking that anything will change after reset today, right? -_-

1 Like

I haven’t logged into the game since Saturday. My time runs out early tomorrow morning (around the time I wake up for work), so I’m done, at least for now, unless they fix all this later. Then I MIGHT come back, but it’s not a guarantee. Due to my time running out early tomorrow morning, tonight will be the last time I’m able to post here (unless I find a way to post while I’m sleeping).

1 Like

Well Vralok, you’ll be happy to know…

…that you’re going to be saving money. Weekly reset has happened, just ran LFR Aggy. Still has 1155k health, still only taking 8x damage, still taking 40 seconds to kill a 2-xpac old LFR boss.

And Mythic Frida still has less health than the first ICC heroic boss.

Good times.

1 Like

Oh yeah, I don’t expect them to do anything until 9.1 at the earliest, when they will practically beg casuals to come back. “You can solo old raids now, we even added a BFA solo LFR queue!” And advertise it as a new feature.

We tried to be constructive, and report these issues through the proper channels. It got completely ignored. So the only thing left to do is speak with the old wallet.

2 Likes

Vralok, if you’re still reading this: nothing’s changed yet, carry on.

1 Like

My initial GD thread has 1.4k posts without a blue, this one has no blue post either.

You mind communicating with us on this Blizzard? This isn’t an F2P game - we do pay you every month and expect some semblance of customer service. Cable companies provide better customer service than this.

3 Likes

I have tested this on 9.0.5 PTR and the issue is still present. For example, damage appears to only be 8x still while M Goroth still has 3013k health. So far it looks like nobody is bothering to address this problem, even with 9.0.5. This is disgraceful.

3 Likes

Fix your game blizzard.

1 Like

Reawakening this thread. I’ve done several tests for raiding at Nighthold.

Guldan on normal has around 1.3m health.
Guldan on heroic has about 1.6m or so.
But mythic? Try a whopping nearly 5 million + the 4 million Demon Within encounter.

The absolute contrasting jump between Heroic and Mythic is not only absurd but absolutely unnecessary. It makes farming far more tedious if you’re running multiple alts, especially if you have little intention to level every alt to 70 (or 62, as I’ve tested. Some classes struggle/take longer at 62, though.)

Surely something can be done to fix this nonsense. Squeeze a fix into 10.1, perhaps?

1 Like