It’s great to see that absolutely no bugfixes have gone into this dungeon going into M+. this may be a rhetorical question, but do the devs even come to the bug report forums?
No, they don’t.
QA does and they forward confirmed bugs to the developers to fix according to their own priorities and schedule.
Even if the devs read every word of the big reports forum with their own eyes, what makes you think they’d prioritize your reports over any others?
Sorry if I used “devs” as a catch all for the entire development team considering the difference between QA and Development is insignificant to 99% of the people here. Going forward I will do better to research the entire developmental hierarchy to better cater to you and others like yourself.
With that said, are you suggesting that this post was not assembled and curated well enough by the author to possibly warrant a deeper look? Also considering we are going into the competitive dungeon running season, could possibly key breaking bugs warrant some priority??
2 Likes
I’m willing to believe the bug report was perfectly described and completely actionable. And so are the literally hundreds of other bugs reported here and other ways.
This report is absolutely no less workable than any other. But that doesn’t obligate the developers to fix it now, or perhaps even ever. Their management prioritizes their work, and bug fixes almost always seems to be a comparatively lower priority.
Maybe after the bugs begin to embarrass them in M+ publicity (like esports), they’ll divert some attention to fixing it.
I never said they were obligated to do one thing over the other, I was merely expressing my dissatisfaction for the fact that no BUGFIXES occurred and that the only thing they did to this was add an anvil. Very useful.
However, you continue to write your post from the point of view of an offended employee and are being difficult for difficulties sake. I did not come here to be lectured about corporate structure, but to give my feedback about the choices that impact the game we all are here for, to increase the visibility of issues…
Lots of bugs are trivial and a minor inconvenience and can probably be safely put on the backburner, but most of the bugs here don’t really meet that criteria if Blizzard wants keystones to be content that is taken seriously (which seems to be the case with things like the MDI). These are bugs that will break keys, and will break keys in a lot of different ways.
These bugs also seem very complicated, particularly the ones with collision, so I absolutely understand if they are challenging to fix, and if that is why they still haven’t fixed them after months and months of reports on them. But again, it’s a sign that this dungeon is not ready to be included in a season roster. It should not be apart of season 1 until people can reasonably expect to be able to get through the dungeon without worrying about their hypothetical tank being unable to land on a ship, their healer not being able to see the ship at all, and their moonkin only able to cast certain spells successfully.
Ran this on heroic the other day. Mage flew straight through the deck of one of the ships like it wasn’t there. Had a great laugh once I realized there was nothing I could do but let myself die.
Updating this thread as we are still encountering newer bugs on this dungeon in Mythic+.
Just ran a +6 key where 2 of our party members were not able to see the purple beams that rotate around the boss. In the same run 2 people fell through the boats to their death while flying between ships.
I propose if Blizzard is unable to fix these issues that plague this dungeon they should at least increase the Mythic+ timer to 36 minutes. The idea being give us more time to work through these technical failures and not ruin as many keys.
The last boss kept going invisible on our group in its final phase. That’s a new one. It didn’t really impact that much since he’s stationary anyway, but noting here for records.
Also, are we supposed to die at the end of every key along with the boss because of the darkness? Sincerely not sure if that is a bug or not (since we didn’t on heroic) but it’s consistently happened in every zero or keystone we’ve done of Dawnbreaker.
Hi Tevah,
Thank you for your help in capturing these bugs. I am curious so I can understand the impact. Do you know if when the boss is going invisible is it interrupting any casts that are currently targeting the boss? Or is it purely cosmetic?
It was just a visual bug. You could still cast spells at him and since he doesn’t move and his abilities are telegraphed by more than just his animation, it didn’t end up being detrimental.
However, I did want to note it in case it is somehow correlated with the bug that makes the ship invisible before the first boss or the deck of the ship invisible on the first boss. Those things require collision, so they actually have a huge impact, while mobs don’t have collision so it doesn’t end up being a big deal - but they could be a related issue on the back end!
Thank you for the clarification. I have updated the original post and listed this as a Cosmetic bug.
No problem! I really enjoy mythic plus and this is the only dungeon that has been buggy this expac so far, but it’s been a dishearteningly large amount and severity of those bugs, so I’m going to keep beating this drum until the majority of these issues get addressed.
Just last night in a key, I couldn’t land on the one of the ship deck as the healer (the fall-into-the-hull bug), so I had to just wait on the next ship and hope my party lived without me. Luckily it was just a +4 so they could, but that’s going to get increasing difficult as key levels go up. And what if I had been the tank? Just a dead key I guess.
Also, I saw in another thread in here that Totemic spec resto shaman healing/acid rain does no healing or damage on any of the ships. I kept meaning to confirm it myself before sharing here but I keep forgetting to look when I play Farseer and I haven’t tried Totemic, so I’m just going to relay it here and hope someone else can confirm.
1 Like
Thank you, I feel similarly. Most bugs are dismissible but when they have a critical impact to the functionality of what is supposed to be a competitive/timed game mode I feel they should be addressed with priority. Not adding some “Repair Anvil” to a dungeon where you can already mount using a repair mount or auto-hammer.
Let me know once it is confirmed and I can update the list, I am not sure to add right now because I dont know if it is the Healing Rain spell or the “Surging Totem” that is being impacted.
2 Likes
Warlocks Charhound isnt working
1 Like
Ran into an odd one last night in a mplus dawnbreaker. Mounted up on my raz drake and it pushed me through the floor (seemed there suddenly was no collosion in the ship). Since crates block the entrance to the lower floors of ship had to have someone come back and get on their sanddrake so i could click it to get back on the deck.
slightly off topic but which repair mounts work there? my yak doesn’t.
You actually can’t use any land mounts there, but jeeves/autohammer/repair bots/etc all work.
The Dawnbreaker has an anvil for repairs near the stairs.
right, it was added recently and the person i quoted was complaining that they spent time adding it 