Defensive Weapon Passives Falling Off?

tomofhyrule

Is there an update on this hotfix yet? I have a feeling that this is at least as important as getting Tribute leaderboards fixed.

PB prog, and I'm getting wrecked because I have no passives. This is pretty unplayable at present.

Not to mention that Bahsei is breakdancing now for some reason? We all asked her to stop teabagging us, but she's not listening; can we report her for toxicity?


U48 was the smallest patch we've had in a while. How did it end up breaking this much?!?

Renato90085

tomofhyrule wrote: »

Is there an update on this hotfix yet? I have a feeling that this is at least as important as getting Tribute leaderboards fixed.

PB prog, and I'm getting wrecked because I have no passives. This is pretty unplayable at present.

Not to mention that Bahsei is breakdancing now for some reason? We all asked her to stop teabagging us, but she's not listening; can we report her for toxicity?


U48 was the smallest patch we've had in a while. How did it end up breaking this much?!?

At least, her bug is more funny than the two events

SaintJohnHM

They broke the game almost a week ago and still no fix.

All the ex-New World players are looking for something fun to jump to just as ESO turned to a broken pile of garbage and no sense of urgency from the devs to fix it.

code65536

ZOS_Kevin wrote: »

Hi All, following up here. We have found this issue that is causing the passive dropoff. We are currently testing a fix. Once we have that done, we will be able to schedule the date for this hotfix. We will follow up once we have confirmed the fix works and ready to schedule.

@ZOS_Kevin What's the status of this? Will you be slipping this hotfix into the Monday morning maintenance?

SaintJohnHM

code65536 wrote: »

ZOS_Kevin wrote: »

Hi All, following up here. We have found this issue that is causing the passive dropoff. We are currently testing a fix. Once we have that done, we will be able to schedule the date for this hotfix. We will follow up once we have confirmed the fix works and ready to schedule.

@ZOS_Kevin What's the status of this? Will you be slipping this hotfix into the Monday morning maintenance?

I haven't seen any word on what they're fixing, communication here is obviously terrible though so maybe they posted about it somewhere else. It's sad that they would let these bugs go on for a whole week, but maybe it'll at least be better today.

StihlReign

Any news on this bug? Did maintenance fix this one too?

ZOS_Kevin

Hi All, just wanted to follow up and confirm that this was fixed during today's maintenance. We pushed a hotfix to resolve this issue.

adamsmith42

ZOS_Kevin wrote: »

Hi All, just wanted to follow up and confirm that this was fixed during today's maintenance. We pushed a hotfix to resolve this issue.

Not trying to be a jerk or anything, just want to point something out: this is a perfect example of the communication issues with ZOS. In your previous post you stated that the problem had been identified and a fix was being tested, that you would get back to us when the fix was confirmed to work and let us know when it would be scheduled... and then we got left sitting here for a week with gamebreaking bugs and no communication from you guys until after the fact; it would have been so much better if you had just dropped a message here when it was confirmed that the fixes would be included in todays maintenance.

ZOS_Kevin

adamsmith42 wrote: »

ZOS_Kevin wrote: »

Hi All, just wanted to follow up and confirm that this was fixed during today's maintenance. We pushed a hotfix to resolve this issue.

Not trying to be a jerk or anything, just want to point something out: this is a perfect example of the communication issues with ZOS. In your previous post you stated that the problem had been identified and a fix was being tested, that you would get back to us when the fix was confirmed to work and let us know when it would be scheduled... and then we got left sitting here for a week with gamebreaking bugs and no communication from you guys until after the fact; it would have been so much better if you had just dropped a message here when it was confirmed that the fixes would be included in todays maintenance.

Totally get that. I was out of the office on Friday, so I was not around when the decision was made that the fix would occur on Monday. Otherwise I would have followed up then. But fully note the point and understand the frustration there.

adamsmith42

ZOS_Kevin wrote: »

adamsmith42 wrote: »

ZOS_Kevin wrote: »

Hi All, just wanted to follow up and confirm that this was fixed during today's maintenance. We pushed a hotfix to resolve this issue.

Not trying to be a jerk or anything, just want to point something out: this is a perfect example of the communication issues with ZOS. In your previous post you stated that the problem had been identified and a fix was being tested, that you would get back to us when the fix was confirmed to work and let us know when it would be scheduled... and then we got left sitting here for a week with gamebreaking bugs and no communication from you guys until after the fact; it would have been so much better if you had just dropped a message here when it was confirmed that the fixes would be included in todays maintenance.

Totally get that. I was out of the office on Friday, so I was not around when the decision was made that the fix would occur on Monday. Otherwise I would have followed up then. But fully note the point and understand the frustration there.

Well... that kind of highlights the problem... out of the entire staff there it seems like you are the only person who has any engagement with the community, which is crazy to me for a AAA game, especially when it's dealing with bugs that are so game breaking that it makes content virtually unplayable for basically any level of group.