still bugged.
2 Likes
itâs not going to be fixed.
Some people just refuse to slooooooooooooooooooooooow dooooooooooooooooooooown
1 Like
life is to be savored!
If youâre still having an issue with this as of Nov. 2021, an easy work around (in Raid Finder mode, at least. Iâm just grinding for the leather mog set) is to simply leave the instance and requeue. Itâll reset the instance, just not give you the first bossâ drops again. Annoying, but it works.
thatâs not really a bug. Itâs setup to be a multi-phase fight, and youâre killing it too early. This isnât just a Paragons problem, it exists in newer content, such as the opera hall fight in mythic Karazhan, to older content, like the Sunwell, on the second to last boss. Sure it would be nice to see it go away anaways, but seeing as raid fights arenât meant to be soloed right off the bat, they would have to redesign every raid encounter years later to take out the multiple phases of the fights. Thatâs a heck of a lot of work for something that isnât even a bug. I know itâs fun to howling blast down every enemy in battle before you even get to it, but itâs not always gonna work that way. People complain now about lack of content, how bad would it be if they were constantly working on redesigning old raid fights? Multi-phase fights are gonna wig out if they donât get to their phases, itâs not fixable without doing what I said and completely redesigning every fight between expansions. And then the only ones they please are a specific range of solo players that canât wait a few seconds and slow down on damage. Does anyone really believe theyâre gonna do all that for such a small percentage of people? Itâs annoying af, I know, Iâm one of those solo legacy raiders. But I also understand how the fights work, and us bugging it out attacking too fast does not mean the fight is bugged.
itâs sad because soloing even old content used to be something that was assumed to require a bit of effort or patience on some fights. now itâs just âwe should be able to skip to the last boss and one-shot it with a single melee attack and drop rates should be 100% on whatever iâm looking forâ
Just to clarify here. Things like this are a bug. The question youâre proposing is whether or not itâs a priority to fix the bug. Those are two different concepts.
The nature of how phase transitions have to be coded, and how players can interact with them is something that needs to be accounted for in initial design anyway. Think about it - what would have happened if, say, on progression, players had brought three bosses down in health at the same time, synchronised, and killed 3 bosses simultaneously? Would they have just bypased a core mechanic? Sure, you can say people âshouldnâtâ do that, but people in progression have done weirder things. Accounting for that sort of thing is fundamental encounter design.
Another thing to keep in mind is that compared to now, players and specs have a lot more uncontrollable aoe/procs, and content is getting so far old that people are legitimately oneshotting things without trying, and itâs only going to get worse. And if itâs not happening now, it will happen in 2 expansions of greater gear/greater legacy damage. At some point, even stripping down naked, and punching bosses with no weapon equipped will oneshot them. Itâs inevitable. If youâre going to go with legacy damage/loot systems, and act like thatâs content to people, that sort of content needs to be given a good play experience, and having players try to work out how much gear they need to take off, or pray to avoid procs, or whatever, is an objective bad one. Itâs one thing if a game company is hands-off and going âDo what you will, itâs old contentâ, but when theyâre actively taking a part in marketing old content as a legitimate game activity, they take responsibility for handling bugs that come up in the process. As long as they care about having a good/polished product, that is.
The last thing to bear in mind is how software development works. If youâre looking into something like this issue, to the extent that your codebase allows, youâre going to be using shareable/re-usable code as much as possible, or making sure that whatever you touch is. Itâs not like theyâre necessarily spending hours of time on every single mechanic of every single boss fight, if they can cut down the amount significantly by having certain concepts/templates they can share. Fixing a bug like this should therefore get long-term benefits by having âbug-freeâ code thatâs applied to all other fights re-using the same mechanic, or that will ever be able to re-use this code/fix. Given how generic the concepts are, e.g. âTrigger event on boss deathâ, âboss Y activates in when X boss diesâ, âheal other bosses to full, keep raid in combatâ etc., thatâs an entirely plausible consideration to keep in mind.
1 Like
I havenât checked but does the foam sword work on bosses?
There was a quest I was trying to complete in pandaria where you need to get a regular mob down to âlowâ health but not kill it and there was no ability I had that would not kill it. A guildie told me about the foam sword, which is a nice bandaid solution, but doesnât work in every case.
The Soft Form Sword toy? Pretty sure it cannot work in Dungeons, Raids, or against Rare Elite creatures if I remember the discussions about it in 2016 correctly.
1 Like
I kinda wanna test the ârare eliteâ bit but Iâm too lazy to go looking for one thatâd otherwise be eligible for me to try whacking with it. I know that anything flagged as a boss would automatically be permanently ineligible because those are always considered to be three levels above your character, so theyâre never going to be considered âtrivialâ. Itâd be interesting to see other mobs have similar protection despite having fixed levels!
So as far as the initial question goes, bosses in instances are double protected from the toy lol