did you leave the circle area? cause if you do, it buggers up n often breaks the fight
Still a bug waited till the 3 were down, attacked and now looking at KaâRoz the Locust . . not coming down and stuck in the battle.
1 Like
If you allow the RP to finish, and wait for the first 3 to land before attacking, there should be no problem. This, however, assumes that you understand that pushing more than one of them to zero at the same time will glitch the encounter. Avoid aoe, and make sure you are doing single target damage.
Once again, multiphase encounters can and will go wrong if you do too much damage too quickly.
Itâs a lot more okay than using autistic the way you just did.
It may be, but itâs even more stupid to have such an easy fix available but decide that itâs better to complain and be a jackass on the forums.
2 Likes
Yikes.
/10char
Waiting like 20-30 seconds is too much for you?
You have to wait like 2 minutes for the Garrosh RP to finish before you can fight him, surely 20 seconds or so is something you can live with.
Wait until they are done talking before you start the fight. Then kill only one at a time.
Do kids these days just swallow tide pods and jump on the fanboi bus? Old content that is farmed with the intent of farming should be tuned and bug fixed. Granted you can wait for the RP but that doesnât excuse old content that has bugs that need to be fixed. The old content is meant to be done, by the way, hence why they add pets and legacy buffs. This content will never be bug-free(Klaxxi) but some of these things can be and should be fixed.
1 Like
Okay then smart guy. Keep fighting for that hill. Instead of having to hearth and reset the raid and then raging on the forums, Iâll be eating my tide pods when I finish the raid because I can figure out something simple like not pushing my buttons for a few extra seconds.
But if the idea of a 6 year old multiphase raid boss having the exact same issue that come up in every multiphase raid boss when it gets pushed outside its design expectations is something that violates your sense of principles, then by all means, fight this battle. Itâs nice to know your world is so good that this is the problem you feel needs a crusader.
3 Likes
Raging? ROFL!
Yeah, Iâm flipping out! Asking for the developers to fix their game is
fighting for a hill.
How goes your career as a forum lawyer for Blizzard?
5 Likes
Still bugged after all those years? This bug exists since WoD or so. Oof.
3 Likes
January 2021, this bug still exists.
Some notes:
- Garrosh drops a rare item called Tusks of Mannoroth. Itâs about a .25% drop rate with no other way to farm them. As such, the game design and intention is players continue to farm this raid, even today, 7 years later.
- The same is true for many old raids: rare drops that are intended to be farmed long after the content becomes legacy.
Iâve ran SoO quite a few times now for roughly 6 months, trying to help a bud get the tusks (I do the run and give him the lock-out). We made it a game doing speed-runs, but itâs always frustrating never knowing when the klaxxi will bug out. Sometimes it does, sometimes not.
Putting all other issues aside, if content exists and is clearly intended to be played, yes any bugs should be fixed. This one in particular is quite obnoxious as many classes have no resolution other then hearthing.
Last note: Iâm a software engineer and would be embarrassed (and quickly fired) to produce code with a high-visibility bug, then not fix it for 7 years. After farming SoO for a while, I came across this thread and read it out of curiosity, mostly to see if the bug was even being looked it. I had no intention of posting till I read the extremely toxic posts from Zothlar. Also noting two other people who seem to be boot-posting, tho itâs questionable if its just Zothlar with 3 accounts (not that I care). Especially interesting to see Zothlar come back to post angry and rude comments in the same thread for months⌠and months⌠and months⌠and condemning people for the proper way to save precious seconds. In the end, a bug is a bug and should be fixed. It should get reported and should get fixed. End of story. People who go out of their way to report bugs are super appreciated. As an engineer, one of our greatest fears is zero feedback when thereâs a problem. As for companies like Activision, yeah, things wonât get done unless enough people say something. Those of you who bothered posting about a bug are ultimately helping everyone. Thank you!
2 Likes
Seriously all you people have to do is wait for the paragons to stop their monoloques before clicking the amber to start the fight. Which takes less time than Garroshsâ.
Talk about first world problems and acting entitled.
If you are doing this, at least for heoric mode, you only need to do it once (first boss up to and including Klaxxi). Donât be in the instance when your friend defeats Garrosh and you can extend the lockout for next week (and every week after). Mythic though you cannot do that as mythic uses the ID lockout system.
Or you know, just wait for their monoloques to finish. You have to do it for other bosses like Norushen, Spoils and Garrosh.
You sound like if you donât defeat Paragons within those âprecious secondsâ you will die.
Grow up.
Then report it on the bug forums and or make an in game bug report. The dungeon, raids and scenario forums are not the bug report forums. Reporting bugs is what the bug forum is for. In fact I doubt blizzard actually reads this forum. Also there is a simple work around that literary only takes like 10 seconds or so of waiting.
1 Like
Clearly thatâs not the case here. Pretty sure your subjective experience doesnât apply.
Which part of his responses were âextremely toxicâ? Honestly, I donât think you know what that word means if you describe these responses as toxic. Just because heâs not babysitting someoneâs feelings doesnât mean itâs toxic behavior. Itâs embarrassing that you think that is toxic behavior when there are people using âautisticâ as an insult on this very thread.
Condemning people? Really? Look at what people are saying to prompt a more direct tone. You act like heâs just throwing insults at innocent people. Angry & rude are hardly whatâs taking place on here. Re-think your definition for these terms in addition to âtoxicâ.
Furthermore, âprecious secondsâ pretty much describes what youâre arguing about. You could just wait a few seconds before you start attacking and there is no issue. Seriously, I do it it all of the time. I donât have this issue because I donât go mashing keys too fast.
3 Likes
Thatâs ridiculous. The game design and intention is for the content to be available for players to continue farming, but raids are designed and intended for the players during the current content window.
I explained the conditions that will cause it to bug out in the third post. Theyâre not difficult. Iâm alarmed that a software engineer has been unable to figure out the cause of something that a pleb like me sorted out on my first time seeing the problem.
I acknowledged in my 4th post that maybe it should be fixed, but that there is a more pragmatic solution available than expecting a fix which, realistically isnât coming. There are phase transition bugs like this going back to bosses years older than MoP, and they havenât been addressed. You are welcome to crusade here on a discussion forum about the principle of the issue, and keep bugging them out to your frustration, or you can stop pushing buttons for a few seconds. Itâs your choice.
Letâs make sure youâre comparing apples to apples here. Would you be fired if you were asked to produce code for a product that worked within the design parameters you were given for the time period itâs meant to be active, even if bugs were discovered at places you didnât test because it wouldnât be relevant?
Raid encounters arenât tested to see if they can handle a group one shotting a boss during a phase transition, because that isnât a realistic scenario during the window of intended use. This shouldnât require explanation for someone who designs software.
Thereâs nothing toxic about giving people a reliable workaround to something that people are obviously having trouble with.
YesâŚanyone who agrees with me must be me. Do you have any other conspiracy theories youâd like to share?
Yes, itâs very interesting that when a thread shows up at the top of the page that I should notice and comment on it. Especially when Iâm specifically tagged by the person who resurrected it, placing an alert for me to see on my account. Very suspicious indeedâŚ
And you think the place to do this is a discussion forum with no developers in it? The point of mentioning it the forum is to see if other people are having a similar experience and if there is a known work around. The actual fix comes from bug reports, either in game or in the bug report forum. Are you sure youâre a software engineer?
1 Like
2/20/21
This fight still bugs horribly.
Iâve been doing this fight for about two years now weekly.
I wait for the RP.
I single target down each bug one at a time after the first 3 have come down.
It can still RANDOMLY bug out with the last guy deciding he doesnât wanna come down anyway.
Not sure what else I can do if Iâm already waiting for the RP to finish and waiting for the first 3 to be hitting me. Just hearthing and trying again.
Found this post and figured it wouldnât hurt to give an update.
3 Likes
Bugged out for me twice here too.
On my DK. I canât even death gate out of there. Apparently I didnât have the foresight to wait around for a specific amount of time and then attack them in a specific order. so now i guess iâm stuck here forever, my bad 
at least my $15 a month may not have gone towards more customization but instead went towards fixing things. hmm,
1 Like
If you happen to get stuck on this bug with Hisek, just try and run into a corner out of his fov, this reset the encounter for me.
June 2021 and this bug still exists⌠câmon this is bs
1 Like
It will exist in June 2022, 2023, 2024, etc.
You can complain about it here if that makes you feel better, or you can follow the steps that have been outlined earlier in the thread to completely circumvent the problem.
2 Likes