Sanity's Edge - Exarchanic Yaseyla frost bomb broken

MuMuQ

@ZOS_Kevin @ZOS_GinaBruno @ZOS_JessicaFolsom

Is there anything new here? This bug ist halting the progress of many groups and the silence about it is getting deafening.
This does not only affect endgame hardmode and trifecta players but also the less experienced groups trying to clear the veteran mode for the first time.

Personofsecrets

Still interested in this one.

SaintJohnHM

MuMuQ wrote: »

@ZOS_Kevin @ZOS_GinaBruno @ZOS_JessicaFolsom

Is there anything new here? This bug ist halting the progress of many groups and the silence about it is getting deafening.
This does not only affect endgame hardmode and trifecta players but also the less experienced groups trying to clear the veteran mode for the first time.

@ZOS_GinaBruno @ZOS_Kevin do you guys know why your company lets bugs like this go on for so long without any communication to players? We don't understand why anyone would think it's ok to let all these bugs go on for so long in an update that was supposed to fix bugs.

tomofhyrule

Most issues that come up in one patch need to be fixed in the second incremental since it happened since the process of making a fix -> testing a fix -> releasing the patch takes a few weeks. I'm not expecting this (or other new U39 bugs) to be fixed until the 18th.

It sucks, but unless this was found on PTS, we're not likely to see a fix before the 18th.

And yes, I get it. I have a regular Sanity's run where I got iced as the MT five times in a row. It made the fight utterly chaotic. Honestly, after having my game be unplayably bugged because of the quest state thing for six weeks, it's really doing a lot to drive me away. I would have liked if we had gone back to more frequent patching after Stadia was canned, but... I realize that a bug found immediately after a patch drops will not be fixed until at least two incremental cycles afterwards because of this slow cadence.

So while I am disappointed that we have no news, I understand that the fix isn't even likely for another two weeks. However, I will also say that that is far too long to wait, and I would hope that ZOS's team will decide to return to weekly incrementals in the case of major detrimental bugs like this.

SaintJohnHM

tomofhyrule wrote: »

Most issues that come up in one patch need to be fixed in the second incremental since it happened since the process of making a fix -> testing a fix -> releasing the patch takes a few weeks. I'm not expecting this (or other new U39 bugs) to be fixed until the 18th.

It sucks, but unless this was found on PTS, we're not likely to see a fix before the 18th.

And yes, I get it. I have a regular Sanity's run where I got iced as the MT five times in a row. It made the fight utterly chaotic. Honestly, after having my game be unplayably bugged because of the quest state thing for six weeks, it's really doing a lot to drive me away. I would have liked if we had gone back to more frequent patching after Stadia was canned, but... I realize that a bug found immediately after a patch drops will not be fixed until at least two incremental cycles afterwards because of this slow cadence.

So while I am disappointed that we have no news, I understand that the fix isn't even likely for another two weeks. However, I will also say that that is far too long to wait, and I would hope that ZOS's team will decide to return to weekly incrementals in the case of major detrimental bugs like this.

They told us Stadia was the reason why they couldn't do faster patches before, I guess that wasn't the real reason. I wonder what's stopping them from communicating about their progress etc.

fizl101

@TheDarkRuler have a look here - Kevin mentioned it will be in the second incremental which I guess would be the next patch not the one just completed

MuMuQ

Here is a direct link to the other thread where Gina and Kevin gave an update about this:
https://forums.elderscrollsonline.com/en/discussion/642569/update-9-1-6-came-without-sanity-edge-hotfix

The fact that this information was not provided here, where the bug was reported speaks for itself.

TKo_ROUSE

We did achieve MindMender last night regardless of the bugs. The fix did not work in the slightest. We had main tanks and healers getting it just as often as last week. It is most definitely possible but that doesn't necessarily make it okay. An educated guess is that this bug added almost a month of prog time overall to this trial.

I am not sure what the patch was trying to fix. There should NOT be a less likely to get frost tomb fix. It should just go back to the closest members who do not have taunt. That is how it worked before and I just wonder why that isn't the target fix now.

Arch_Angel

This was most definitely not fixed, getting tomb on Main Tank 4 times on a row does not coincide with the fix stated in the most recent notes.

I also believe this cannot be intended or one of the situations where a long going bugg is shrugged of as intended now, because the tomb will with high chance oneshot the tank.

Being oneshot is not fun content because a bugg was made into an intended mechanic.

It can also not be intended because one of the mechanics is placing fire bombs, which is not possible and will either wipe the group because it spawns smack in the middle or the MT gets ignited with the very fun mechanic of overtuned bleed from the boss.

vgabor

Definitely not fixed and still entirely broken. Yesterday (2023 Sep 20) we had a run where the two tank were getting most of the frost bombs, the first is the main tank on the boss the second is the off-tank on the wamashu.



@ZOS_Kevin @ZOS_GinaBruno

SaintJohnHM

We tried vSE HM last night and tanks kept getting frost tombs which made a mess of fire bombs and wamasu, etc.

It's not fixed at all.

Do they bother testing before they release updates?

Are they capable about communicating about huge game-breaking bugs like this?

tomofhyrule

SaintJohnHM wrote: »

Are they capable about communicating about huge game-breaking bugs like this?

From the other thread:

ZOS_GinaBruno wrote: »

Thanks all. We've seen these reports and have a new, better fix going into the next incremental patch.