eveboufa wrote: »

So, zos employees have closed down other threads on this issue and redirected people to this one, yet no one from zos has officially posted on the forums with a resolution . Maybe I missed it?

The response from zos to this major issue was apparently aired on a stream which most of us likely didn’t watch because we work 9-5 jobs.

@ZOS_BillE @ZOS_GinaBruno , is anyone going to follow up on this thread? There is a reason most of us have quote you both in our messages, it’s because you tend to be more responsive. Yes it is the holiday season but I would expect that in your absence, for sake of customer service, someone would have been assigned to monitor and respond. Your clients are not happy. We love this game and it’s unplayable.

The response from ZOS was posted in this thread yesterday. I'm pretty sure the only reasons it was briefly mentioned by Gina in the stream this afternoon were (1) in anticipation of the chat being spammed by people wanting to raise the issue during the stream, and (2) to let anyone who doesn't follow the forums know that the issue had been identified and was going to be addressed in an update. Her response was basically identical to what Kevin had posted yesterday. You want a definite time, and are anxious for a fix right now, but they said they don't have a definite time although they are trying to get it out as soon as they can. If it were the PC version, they could just shut down the servers on any day of week and any time of day, but as I understand it that's not how it works for the consoles-- which is not something ZOS controls.

I guess I don’t understand why something this bad has to go through a lengthy certification process and can’t get a hot fix.

This is not new functionality being introduced in a new patch like Companions, it is an unintentional bug that is rendering gameplay unplayable. I don’t use the term “unplayable” here often. The skills not firing is annoying and makes playing difficult, but I can do something at least part of the time. There is no point in going to Cyrodiil if you get disconnected every time there is a siege, and it’s not much fun just standing around in a keep doing nothing.

Why are other games able to do emergency updates and ESO isn’t???

Also in what world does ZoS live in where they should not have IMMEDIATELY rolled the update back? We can stop all pretending like it is only Cyrodiil as well, the crashes are more prevalent in EVERY SINGLE ASPECT of the game, bgs, dungeons, over world, dueling, housing I have crashed multiple times from all of it. The update clearly broke something crucial so roll it back and figure it out before you release it live.

Honestly the only thing NOT showing an increase in crashes is the Crown Store… hmm, weird.

AwakeOhSleeper wrote: »

Also in what world does ZoS live in where they should not have IMMEDIATELY rolled the update back? We can stop all pretending like it is only Cyrodiil as well, the crashes are more prevalent in EVERY SINGLE ASPECT of the game, bgs, dungeons, over world, dueling, housing I have crashed multiple times from all of it. The update clearly broke something crucial so roll it back and figure it out before you release it live.

Honestly the only thing NOT showing an increase in crashes is the Crown Store… hmm, weird.

The issue is the maintenance patch was specifically for New Life, unless I'm mistaken, in which case they can't roll it back (not that they ever rolled back a build, as far as I can remember). I have to scratch my head while wondering what about New Life festival broke Cyrodiil siege. The conspiracy theorists will tell you that the reason why they won't do an emergency patch is to not bring the game down during the event. I don't fully believe that, but I do think it's irresponsible to everyone, from players to investors, to leave this game in its current state for weeks.

If this is going to take weeks to fix, we deserve a better explanation than blaming the XB certification process, and some sort of compensation for our lost time. I've lost out on at least 1 mill AP because every time we try to siege, someone DCs everyone. Like I said earlier, DCing has become a valid defense mechanism for some people because if your keep is getting sieged by a ram (which does work) and you can't hit them with a treb (which also seems to be okay) your only options are ballistas, lancers and meat bags. Of course meat bags suck for defending from inside the keep, so that leaves ballistas and lancers, and I don't know anyone who is willing to put down a lancer right now.

Yes, there are also oils, but it's been a long time that oils were effective at all against players, save NBs.

Edit: Just wanted to add one thing.

I don't want anyone to have to work on Christmas day to fix this issue, and I think most people would agree with that. At the same time, however, I suspect a vast majority of ESO players are working class people, many of whom have jobs where they don't get a choice on whether or not to work on holidays. Those employers just make you work, often with no additional compensation. I spent 15 years not having a choice.

I have a hard time believing that ZOS can't offer enough money to get enough volunteer developers to work up to the holiday and immediately after to A: fix this, and B: get it through the accelerated certification process so that we can enjoy the product we have paid for.

We've been using it to our advantage. We call it 'ballista bombing'. Have a troublesome hammer on it's way? No problem! Just drop a bunch of ballistas and dashboard hammer. Problem solved.
Keep a guy outside of the blast radius and have him pick it up.
It's a brave new world.

malistorr wrote: »

Patch incoming for Xbox NA 12-22 looks like. No idea what's in it. One can hope I guess? It would be nice if they fixed other things too like heavy attacks that are completely screwed up and doors in dungeons that won't let people pass. It's not just PVP crashing that is ruining the game right now.

Until we see the notes don't assume it has a fix for this. That would be very fast turnaround if they went through certification. Hope that it's fixed though.

malistorr wrote: »

Yeah I said hope because I don't actually expect a fix based on past history on this game. The heavy attack problems have been around now for a few weeks and still no fix on those. Nevermind the other bugs that have been around for months and years.

Yeah I miss heavies all the time which sucks because I'm having to run a build this patch that uses them.

Good luck with that Microsoft needs more billions. $$$

ZOS_Kevin wrote: »

Hi Everyone,

We have an update regarding the blue screen issues console players are having in Cryodiil, IC and BG. We last noted that we have identified the issue and working on a fix. We can now confirm that a fix is complete, has passed certification, and will be included in Wednesday's incremental patch.

Thank you all for the continued patience.

Thank you!!!!

TheEndBringer wrote: »

The frustrating thing about this is people were reporting this immediately after the game came back up from maintenance. Everyone got the usual "delete your local save" suggestion. It wasn't until over a day later we got the beginnings of an official response. This seems to be a recurring issue where it seems support always assumes it's the player's issue first.

That's pretty boiler plate when it comes to steps to tracking down an issue. It's always the first step to determine if the issue being reported can be resolved by the user before escalating it to the larger team. No one wants to spent development time hunting down a bug that could have been resolved by the user. As more reports came in, they did escalate and provided a response. But the initial feedback will always, and should always, be to ensure that the issue isn't isolated to a specific user or users.

jaws343 wrote: »

TheEndBringer wrote: »

The frustrating thing about this is people were reporting this immediately after the game came back up from maintenance. Everyone got the usual "delete your local save" suggestion. It wasn't until over a day later we got the beginnings of an official response. This seems to be a recurring issue where it seems support always assumes it's the player's issue first.

That's pretty boiler plate when it comes to steps to tracking down an issue. It's always the first step to determine if the issue being reported can be resolved by the user before escalating it to the larger team. No one wants to spent development time hunting down a bug that could have been resolved by the user. As more reports came in, they did escalate and provided a response. But the initial feedback will always, and should always, be to ensure that the issue isn't isolated to a specific user or users.

I realize that it's boiler plate but...

If I get a ticket that says everyone is disconnecting at once every time someone sieges, it's an easy thing to confirm. Someone go log in and see if it happens. Like, even if all you did was sign into Xbox Cyrodiil, you'd see the zone chat filled with complaints confirming it.

It points to a larger issue that I don't think they have people actively playing the game on all platforms. If they had one employee in Xbox Cyrodiil...

ZOS_Kevin wrote: »

Hi Everyone,

We have an update regarding the blue screen issues console players are having in Cryodiil, IC and BG. We last noted that we have identified the issue and working on a fix. We can now confirm that a fix is complete, has passed certification, and will be included in Wednesday's incremental patch.

Thank you all for the continued patience.

Yay!!! I sure hope this fixes it. Every year for some reason new life drops and breaks Cyrodiil in some way. Could it be an old bug?