Blizzard, why the hell did you screw up Echo?

Yeah the blue post was really vague but the concrete hotfix notes were on WoWHead.

I mean… I can’t really blame them for overlooking it, honestly. It’s really cheap of Blizzard. But it was there.

same coincidence same day i was conquest capping
i see him and jmy in 3s arena
ofc 226 ilvl bm and havoc stomps enemy teams without their heal pally healing

the dude has a pve and a pvp set

/shrug

The ones that complain the most about it are the fans anyhow. Echo just accepts it. Also i wouldnt blame the Echo raiders for overlooking it but their guys in the background that check everything for them.

2 Likes

Absolutely agreed.

That said, it was hard to hear the disappointment in their voices. It really was. Especially because WoW really needed some positive media attention for this patch, and then we get that… oof.

If the tier would have been completed already this would have sparked a “lululu raids too easy lululu” and you know it. Damned if you do, damned if you dont.

I am not fan of World first race!

It doesn’t mean anything to the game and community.

They should’ve just documented it, honestly.

Nobody likes a game that constantly snatches you away from victory just as you think you’re about to win. It’s… just not fun. I don’t think anybody thought it was fun what happened. Funny… yes. But making your top raiders look like fools with poorly documented hotfixes just doesn’t really inspire people to participate, you know? It makes the game sound like it’s frustrating to play.

Fixing bugs is another matter, but this was not fixing a bug. This was a tuning change.

It does. At the end it still serves as an additional tuning and bug check.

As i said imo they should have asked Blizzard regarding the Aura. Their background guys in the very end should have. We know that both Limit and Echo have a Blizzard contact for that stuff while the race is ongoing. No idea about Pieces, Method and BDGG.

I think Blizzard has the responsibility here. They’re the ones whose job it is to make encounters that are fun to fight and they’re the ones who initiates the change and wrote a big but incomplete blog about what they did and why.

Blizzard “lied by omission” in a sense.

Sure, Echo should’ve checked the hotfix notes. But I feel like we’re sort of arguing that Echo should have trust issues.

Why tho? They never stated how exactly the last tier boss is going to behave. A reason why the fight is also not available on PTR on Mythic. The fight could have gone in so many directions because nobody knew what to expect. Could have easily been another Archimonde or Ragnaros that heals oneself up to a certain percentage.

Rule nr 1 in World of Warcraft: “Never trust Blizzard with absolutely anything”

But they did sortta… I mean they said when all the transitions were happening. Except one.

It shouldn’t be like this. You know it shouldn’t be like this. That’s why I’m blaming Blizzard.

I didn’t really say that everyone knew about it, did I? I’m saying that it was designed that way. It’s not like they changed it overnight to affect the WFR.

I’m also cheering for Echo, but this is just stupid, what people are doing here. Just deal with it.

How is it showing true colors? THEY HAD AN ADVANTAGE EVERY SINGLE TIER. MULTIPLE TIERS WERE VERY CLOSE.

It’s insanity to think that Blizzard is intentionally giving an advantage to Limit, and that Blizzard could’ve predicted exactly how much % 2 teams of players can do with so many RNG elements. Just stop.

Same for china they have a bigger disadvantage tho

2 Likes

Unofficial buffs coming to Guardian, Fatescripe and KT.

http s://twitter.com/Fleks27/status/1417061400338444293

http s://dictionary.cambridge.org/dictionary/english/unofficial

And that one should have been taken with a graint of salt. I mean the hotfix is in WoWhead. The Hotfix was announced. You actually posted how easily its visible that the fight stops at 45% at Mythic (something i didnt even know the Aura stated to begin with. However i didnt bother to check and assumed it was a flat nerf. Im not a world first raider however so its nothing i have to concern myself with). And they announced that a hotfix had taken place. It was falsely assumed the fight stops at 50% because before the first normal/hc kill happened she already got hotfixed while she should have kicked the bucket at 45% straight from the start.

Shouldnt be no. But it is. Never trust Blizzard.

There is nothing about Silvana’s kill health in this patch!!!

  • Sylvanas Windrunner
    • Fixed an issue where the ability sequence of Stage 2 would differ if players skipped the intermission cutscene.
    • Resolved an issue with Stage 3 ability timings.
    • Lady Jaina Proudmoore, Thrall, and Bolvar Fordragon no longer sometimes forget that they were fighting Sylvanas Windrunner or Anduin Wrynn.
    • Fixed an issue where she would fail to cast Wailing Arrow on dead targets under certain circumstances.
    • Fixed an issue where the Banshee’s Fury secondary area-of-effect spell (for player’s afflicted with Banshee’s Bane) could damage player pets and guardians.

Yeah right, thats why people abandon ship and are running towards FFXIV, because its only the 0,1% thats screwed over. Sure thing buddy.

2 Likes

Thats July 12th :stuck_out_tongue:

July 13th has

  • Sylvanas Windrunner
    • The total damage players must deliver to Sylvanas Windrunner has been reduced by approximately 5% in Normal and Heroic difficulties.
    • Sylvanas Windrunner now transitions out of Stage 1 at 84% on Normal and Heroic difficulties.
      • Developers’ notes: We felt that players were losing too much uptime due to mechanics, and getting out of the first phase much later than originally anticipated, so this is meant to curtail the length of the encounter without affecting difficulty too much.
    • Veil of Darkness radius has been reduced in the third stage of the encounter.
    • Banshee Wail and Banshee Scream radius reduced.
      • Developers’ notes: Our goal here was to help ease the space constraints imposed by larger raid sizes, without substantially reducing the difficulty of the encounter.
    • Defeated players will now be correctly moved to the first platform at the start of Stage 3.
    • Dispelling Banshee’s Bane with single-charge dispels now removes all stacks.
    • Mawforged Souljudge’s Lashing Strike initial cooldown increased.
    • Sylvanas Windrunner is now immune to Curse of Tongues.
    • Combat resurrection cooldown timers now take the duration of the mid-fight cinematic into account.
      • Developers’ notes: We don’t want players to feel like there’s a penalty to your battle rez if you skip the cinematic.

But this could have been literally anything involving the number 45 which is why it was only speculation. Add cats X at 45%, ability X is done at 45s instead of 50. Etc.

1 Like

It is like Blizazrd doesn’t want let Echo win. Echo created new strat and it was hotfixed for next pull. Sad.

2 Likes