demotivator Posted January 13, 2022 Share Posted January 13, 2022 (edited) Yet another Feast of Prosperity and this WB is once again bugged, at least on Satele Shan, both in PvE and PvP instance. When are you going to fix it instead of relying on people to kill the adds properly, which will never going to happen between those who simply don't know and those who will break its respawn on purpose? If you can't fix it, when are you going to SIMPLY remove Belsavis from the pool of WB for the mission? You cannot tell me that this hard. Edited January 13, 2022 by demotivator Link to comment Share on other sites More sharing options...
R_e_V_a_N Posted January 13, 2022 Share Posted January 13, 2022 Yep, another Feast event where they can't fix the bugged respawn timer for Primal Destroyer WB on Belsavis... Satele Shan hasn't seen a Primal spawn in either PvE or PvP instances in hours now. Seriously, if you can't fix the issue at least try to mitigate by either removing the Belsavis ingredient quest, or ensure that there are alternative bosses to choose from each day. This happens every time the Feast of Prosperity event rolls around, and it's honestly mind-boggling that no mitigation strategies have been developed yet. Link to comment Share on other sites More sharing options...
demotivator Posted January 22, 2022 Share Posted January 22, 2022 (edited) Another day and again Belsavis since it is the most common WB for whatever reason... and obviously it is once again broken on Satele Shan. Not even a word about investigating possible fixes. They are just relying on the players to police the issue, which will NEVER going to happen. Pulling the adds away, either unknowingly or on purpose to break it should NOT mess with its respawn. The responsibility to fix the issue lies in your hands, not ours. If you don't know how to fix its respawn, there is one simple solution: REMOVE BELSAVIS OFF THE POOL OF WB DAILIES. Edited January 22, 2022 by demotivator Link to comment Share on other sites More sharing options...
NeoBlakkrstal Posted January 24, 2022 Share Posted January 24, 2022 (edited) Hi folks, Thanks for reporting the bug with the respawn time of the World Boss Primal Destroyer during the Feast of Prosperity Event. Our team is aware of this bug. As mentioned in this post: Darth Malgus - Belsavis World Boss not respawning, this issue seems to occur (at least in one case) when players kite the Primeval Destroyer's adds away from the boss area after the boss has been killed. You should follow this new workaround while we're looking into it: Make sure the adds are dead before killing the World Boss. - Updated workaroundNote: If you see another group fighting the world boss, and you want a piece, help them and focus ads to ensure you get your own boss after. I'll update you in this thread when I have more information. This is insufficient. The event only lasts three weeks. This mission is a daily with a weekly tie in. It is impossible to complete this on a toon if Belsavis is the boss that day. The mission reset is too long, and the boss is too bugged. Either fix this, or remove Belsavis from the rotation. This is ridiculous. The bug has existed since the Feasts inception if not longer, and nothing has been done about it except finding a work around, that only works if the entire group is aware of it, and exercises restraint during the encounter, something that cannot be guaranteed. And given that the boss is not there and will not respawn in any instance, at least on Star Forge, that work around obviously isn't. There has been sufficient time for this to have been fixed. Maybe the Devs could spend less time giving us a piece of crap new gearing system, and fix what is actually broken. Please and thank you. Edited January 24, 2022 by NeoBlakkrstal Forgot formatting Link to comment Share on other sites More sharing options...
Saeten Posted January 24, 2022 Share Posted January 24, 2022 This is insufficient. The event only lasts three weeks. This mission is a daily with a weekly tie in. It is impossible to complete this on a toon if Belsavis is the boss that day. The mission reset is too long, and the boss is too bugged. Either fix this, or remove Belsavis from the rotation. This is ridiculous. The bug has existed since the Feasts inception if not longer, and nothing has been done about it except finding a work around, that only works if the entire group is aware of it, and exercises restraint during the encounter, something that cannot be guaranteed. And given that the boss is not there and will not respawn in any instance, at least on Star Forge, that work around obviously isn't. There has been sufficient time for this to have been fixed. Maybe the Devs could spend less time giving us a piece of crap new gearing system, and fix what is actually broken. Please and thank you. Hear hear! It's so disappointing the amount of bugs that have been on the boards for years are still not fixed. 10 year anniversary year of disappointment for the first two months is atrocious. Come on devs and community support. At least communicate more often! Then focus on the highest pain first. Not new changes that at least on the face are broken as F in PTS. Also, communicate what's been recommended by testers and live bug reports and give us hope! Link to comment Share on other sites More sharing options...
NeoBlakkrstal Posted January 25, 2022 Share Posted January 25, 2022 Hi folks, Thanks for reporting the bug with the respawn time of the World Boss Primal Destroyer during the Feast of Prosperity Event. Our team is aware of this bug. As mentioned in this post: Darth Malgus - Belsavis World Boss not respawning, this issue seems to occur (at least in one case) when players kite the Primeval Destroyer's adds away from the boss area after the boss has been killed. You should follow this new workaround while we're looking into it: Make sure the adds are dead before killing the World Boss. - Updated workaroundNote: If you see another group fighting the world boss, and you want a piece, help them and focus ads to ensure you get your own boss after. I'll update you in this thread when I have more information. A "work around" is not sufficient, especially one that is player initiated. You cannot guarantee that every group is going to be aware of this "work around", nor can you guarantee that mistakes will not happen. This needs to be FIXED, REPAIRED, TAKEN CARE OF, by EAware. So please, can we get a hotfix for this ASAP! There is only one week left. Link to comment Share on other sites More sharing options...
Recommended Posts