Unfortunately, companies are terrified to tell customers they don't know what the problem is. So, we're stuck in the dark. It's a two edged sword really...
drakks1ub17_ESO wrote: »I can say from first-hand experience in Landmark that devs communicating with players is a *great* thing.
Won't happen.Seriously, just make an official announcement and keep us updated. It might only be a game, but it's important to the people affected.
Then you haven't looked at the huge scale of complaints and requests for even acknowledgement of a bug.jamesharv2005ub17_ESO wrote: »The dev tracker is chock full of responses and dev threads. What do you expect? A personal phone call every couple hours?
ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
It's always been there, just a little hidden.ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
Thanks for the reply, @ZOS_GinaBruno
is the dev tracker a new feature? I sure as heck don't remember it being there a few days ago.
ZOS_GinaBruno wrote: »It's always been there, just a little hidden.ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
Thanks for the reply, @ZOS_GinaBruno
is the dev tracker a new feature? I sure as heck don't remember it being there a few days ago.
Yep, that's one of the options we're exploring.@ZOS_GinaBruno is it possible to have the Dev Tracker set to a list format like a thread or just the name of the topic and first 200 characters of the message a dev has posted? Right now it's kind of a mess to read with topics being hugely long or small, this thread for example the Dev Tracker is showing one massive long post for your last reply taking up the entire left side.
ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO? suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
Unfortunately, companies are terrified to tell customers they don't know what the problem is. So, we're stuck in the dark. It's a two edged sword really...
Can you blame them? People get hostile for the most illogical things.
Even when bringing down a server to address issues, for example.
The masses are the reason for the silence, not the development team.
ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO? suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
The issue in this case is two-fold, one of which is directly in your control.
1) Rock solid data integrity is absolutely essential in any online only game. Essential! Players don't have hundreds of saved games to fall back on when things go wrong. We have exactly one saved game and it's located in your datacenter. We trust (and pay) that you maintain 100% rock solid handling of that data. This is clearly not the case here.
ESO right now isn't a game, it's a Russian Roulette simulator. *click* Nothing. *click* Nothing. *bam* Oh, I was only horribly injured (loss of bank slots, banked items, and banked gold). *BAM* I've been killed (add loss of character progression, skills points, mounts, etc.)
Like many players, I can handle "typical" launch issues such as failure to logon, broken quests, blocked content, etc. As a programmer, I understand that stuff happens. This issue isn't "typical."
I know it's not the Community Team's fault that someone or several someone's failed at basic software development. Whether it was not specifying requirements sufficiently, not performing thorough unit or integration testing, or if it was a failure at the functional or performance level, something failed. This game should have never gone live with data reliability as poor as this. But it has, so...
2) Keeping consistent, open, frequent communication is vital when problems are this serious. ZOS has already violated our trust by compromising the data(see #1 above) yet you compound the error by keeping secrets from us now. This is directly under the control of the Community Team.
You should be giving us frequent updates, daily at minimum. Here are just a few examples of what we should've been hearing throughout this process (which, for the record, has now lasted over 2 weeks):
- "A special dev team (consisting of...) has been formed to fix this problem. This team will be focused exclusively on this issue until it is fixed."
- "The dev team has gathered all the data thus far and they are currently evaluating possible scenarios and causes."
- "The dev team has narrowed down possible causes and are now performing extensive testing to eliminate possibilities and isolate the cause(s) of this bug."
- "The dev team has identified the cause(s) and continues working through the weekend to craft a fix. At this point, the fix is expected to fix the following: <list>"
- "The dev team and quality assurance is aggressively regression testing potential fix(es) to ensure this issue will be fixed for good."
- A fix has been verified and will be implemented <data>. It will fix <stuff here>. Items/slots/gold/stats will/will not be restored (and what can players do for what is not restored)."
Having cute, in-character yet generic (and often flat out wrong) messages from CS is not the answer. Those tend to heap inflammables on hot coals. Yes it's just a game. No, this type of bug isn't funny (again, see #1 above).
I realize that marketing (and others) don't want it widely known that ESO is an unstable data nightmare right now (too late!), but only giving occasional generic reassurances that do nothing to address customer concerns is how you burn through the customer goodwill that you started out with. You know the console gamers are watching this with especially keen interest. Have marketing crunch those numbers.
ZOS_GinaBruno wrote: »It's always been there, just a little hidden.ZOS_GinaBruno wrote: »Hey there, everyone! As @jamesharv2005ub17_ESO suggested, a good starting point is the Dev Tracker. We understand that it may be a little overwhelming to sort through, and we're looking at ways to improve the functionality there. Also, we're planning to implement a Dev post signifier so you can easily spot when a Dev has responded in a thread, and also jump right to the next Dev reply. We hope to have this live pretty soon.
In regards to the issues that you may have run across or report, please understand that the severity of each issue varies greatly, and some are more complex than others. Every issue requires some level of investigation, though, and typically this is where you'll find the silence coming into play while we look into all the factors and try to figure things out.
We do encourage everyone to check out the patch notes that get published weekly during our scheduled maintenance, as we'll list out the issues that have been addressed and fixed.
Thanks for the reply, @ZOS_GinaBruno
is the dev tracker a new feature? I sure as heck don't remember it being there a few days ago.