Nunatak - Midyear Horrors

Dalsinthus

Colinr1968 wrote: »

8 hours of maintenance and no fix on nunatak guess we have been ripped of by zos again well done zos

I just killed the boss again on my sorc and no achievement. It’s unbelievable that this wasn’t fixed with this morning’s patch. They had an opportunity to correct this and just didn’t. SMH

LAMBinLCTX

Dalsinthus wrote: »

Colinr1968 wrote: »

8 hours of maintenance and no fix on nunatak guess we have been ripped of by zos again well done zos

I just killed the boss again on my sorc and no achievement. It’s unbelievable that this wasn’t fixed with this morning’s patch. They had an opportunity to correct this and just didn’t. SMH

This is infuriating — every part of it, from the bug itself to the pro gankers taking advantage of it — Mayhem indeed!!

It’s a sad state of affairs when a person’s leisure activity inspires more dread than enjoyment, but sometimes this game stops being fun and really feels like a chore.

ZOS_GinaBruno

Dalsinthus wrote: »

Colinr1968 wrote: »

8 hours of maintenance and no fix on nunatak guess we have been ripped of by zos again well done zos

I just killed the boss again on my sorc and no achievement. It’s unbelievable that this wasn’t fixed with this morning’s patch. They had an opportunity to correct this and just didn’t. SMH

This morning's maintenance wasn't for a patch, it was some backend infrastructure work. We know this is a frustrating bug, but it's not something we're able to hotfix and needs to go into a full build.

Xarc

but when you will fix it, the event will be finished... Will you give us the kill for the achievement ?

Colinr1968

ZOS_GinaBruno wrote: »

Dalsinthus wrote: »

Colinr1968 wrote: »

8 hours of maintenance and no fix on nunatak guess we have been ripped of by zos again well done zos

I just killed the boss again on my sorc and no achievement. It’s unbelievable that this wasn’t fixed with this morning’s patch. They had an opportunity to correct this and just didn’t. SMH

This morning's maintenance wasn't for a patch, it was some backend infrastructure work. We know this is a frustrating bug, but it's not something we're able to hotfix and needs to go into a full build.

Well in that case @ginabruno you should give those who have all the other 11 bosses earned in this years mayhem then achievement for it that's fair and not make people wait a full year for it.

Dalsinthus

ZOS_GinaBruno wrote: »

Dalsinthus wrote: »

Colinr1968 wrote: »

8 hours of maintenance and no fix on nunatak guess we have been ripped of by zos again well done zos

I just killed the boss again on my sorc and no achievement. It’s unbelievable that this wasn’t fixed with this morning’s patch. They had an opportunity to correct this and just didn’t. SMH

This morning's maintenance wasn't for a patch, it was some backend infrastructure work. We know this is a frustrating bug, but it's not something we're able to hotfix and needs to go into a full build.

Thanks for the clarification and response. It took me many tries and gankers messing with me, but I did get it done today on a second character for this event. Frustrating bug; I hope you can get it fixed for the next event.

RMerlin

This new patch schedule is a serious step backward, all in the name of a platform (Stadia) that the vast majority of your users don`t care about. It's making the game stay buggy even longer than before just in the name of showing new subscriber numbers to ZOS shareholders. Not a consumer-oriented decision.

Smaxx

[snip]
You're totally missing the point you're trying to make. They couldn't fix the bug ad-hoc and in time, because they do have to make changes and test them first. The exact testing you claim they're lacking is probably the reason they had to delay the fix.

[edited to remove quoted post]

LAMBinLCTX

So...
Just to close the loop on this one, I never did get the achievement.

tinythinker

LAMBinLCTX wrote: »

So...
Just to close the loop on this one, I never did get the achievement.

Me either, but it's good to know they are aware of the issue and put it on the schedule it for their play-testers and bug team to characterize and send to the appropriate person for correction.