Hey just got out of a great set of heroic Ascendant Council pulls where the fire boss didn’t feel like charging and dropping his fire on the way back from his leap. Really fun, especially since we thought it was player error and wasted time proceeding to avoid potentially LoSing him on top of the stairs, and even having our tank actively run away when the boss leapt only to find out that it was, in fact, just about what we’ve come to expect from Blizzard games, a BS bug. Then as a nice little bonus we learned that this bug was reported in 2010! Wow! 14 years to fix this bug haha, what an experience.
It’s great that the strat for the boss is “just don’t get the bug” but could you maybe get one of the 3 developers working on Cata to take a quick look at this? Preferably a real one and not the fat one who thinks Archaeology is fun.
Shout out to Magmaw throwing his head back, Maloriak not being sure if he wants to summon adds before dark phase, and also Feludius randomly casting glaciate right on the pull, loved those. Add to that all of the great bugs from questing on release and this expansion has just been going swimmingly. Who knew it could be so hard to re-release a game that was already made for you?
Here’s a quick suggestion, if you’re not going to bother fixing bugs from a raid that much better developers than you made, with you just needing to implement their designs, don’t even bother to put up a test environment for guilds to get 100s of pulls in and sleepwalk through the raid on release.
You guys are not making a new game. This game was already made, and shockingly, the original developers fixed most issues. You are standing on the shoulders of giants, and to call what you’re doing standing would be generous. There is no excuse for these bugs. Fix the game, thanks.
3 Likes
We are also having this problem on normal mode. For a group of newbies this is making the fight really hard. Anyone else having this issue?
Yes we’ve also encountered this bug many times and haven’t been able to determine what’s causing it. Any insight into cause/possible fix would be appreciated.
a mouse can’t teach a tiger, you’re worse than flies in a dog’s bum
1 Like
Just a quick update here to remind the three Cataclysm devs that the Ascendant Council fight is still bugged. It was actually just as fun this week to pull this boss and see the fire boss waddling back to the tank with no fire trails as it was last week.
Things that do not work:
Pulling the boss off the stairs
Having melee stack on the tank when he leaps out
Having ranged stack before he leaps
Having the tank move backwards while he leaps
Having the tank stand still while he leaps
Tank swapping
Group prayer sessions before pulls
Things that do work:
Literally nothing
Yeah so we killed it bugged, great. It’s currently week 2 of raiding and I’m not looking forward to the inconsistent buggy pulls for the next x weeks. Firelands is in October (maybe), it is still June. Fix this bug, do your jobs.
Happened multiple times last night…
We just had a range stack, tank on water, and tank with melee on fire. Worked for us.
I’ve seen the fire guy on council not drop a fire trail almost every pull. I was told by a guildie that it’s also possible to remove the debuff by standing in front of his fire breath if you’re ever in that situation.
Hey guys, week 3 update! I can tell you’re hard at work at Blizzard fixing bugs since you fixed the Magmaw slamming his head back so great work Blizzard devs huge round of applause and a pat on the back. Let’s aim for next week you try fixing the council bug maybe? Just in case you forgot, that’s the bug where the fire boss doesn’t drop fire when he leaps out since he strolls back in instead of charging.
Also, another quick bug you might want to look at (maybe)! Sinestra sometimes decides to keep her encounter fire wall up after you wipe, making it impossible to pull the boss until a hard 30 min reset. Probably worth checking that one out at some point too, but the Ascendant Council bug is way more annoying so it’d be nice to fix that one first! Looking forward to week 4 and a bug free fight!!
What worked for us on prog:
tanks position mobs ~7 yds back from stairs
ranged close to max range from that
tank stands still on leap, waits for Ignacious to walk the whole way back
all of ranged stands still on leap
Doing that all together we still got no fire maybe 1/6 of the time. Rather than doing a strat telling ppl to eat the frontal, we had anybody with waterlogged get in melee with Ignacious, and wait for his fire shield pulse to break the debuff - the first shield / waterlogged turning into ice cubes is pretty well synced up if you miss fire on that one, and shouldn’t need a CD up for it - if it’s a later one in the fight need to pop a raid-wide defensive CD or two and AoE heal the crap out of the melee stack
Day 302956, still waiting on Blizzard to fix these bugs. It’s bad enough that heroic clear rates are in the gutter for this tier on both 10m and 25m, it’s even WORSE than Council’s clear rates are artificially inflated by this bug, especially for 10m.
Can we get SOMEONE to fix this bug? We REALLY needed that fix to paid services being reduced to 3 days but I guess progression raiders can just eat the floor because the mechanics just do not work.
@blizzard ETA on an update to fix council? At this rate we’ll see the next phase before you fix this stuff.
w
This bug should have an achievement, really good evasion for devs.