Developers, please read

Case number:845818-995430
Topic:Game: Social
Opened by:auntdeen
Opened on:Monday, July 1, 2013 - 19:23
Last modified:Tuesday, July 2, 2013 - 00:40

If you want players to use the devprev and report bugs, you need to be more considerate when responding to bug reports.

You had 3 different feedbacks concerning cutpoints and crashes on June 27. Madde was the first to report a symptom (Thursday, June 27, 2013 - 08:55, spvincent reported a different one (Thursday, June 27, 2013 - 22:30 and Susume yet another one (Thursday, June 27, 2013 - 23:50

All three players are vets who are spending time finding your bugs. They all deserve the highest respect from you.

If the cause of all three symptoms was one bug, that doesn't mean that two of these reports were duplicates (and certainly not the first one posted!). Our community has a long standing tradition of trying to give you the most information possible to nail down what is causing a problem.

By mis-labelling any of these as a duplicate, you make players wonder why we should even bother reporting a symptom to you. Do you really want us to not report anything that might be related to something that maybe might already be part of something that someone else has found a symptom for but is probably part of that because it might have something to do with the same tool?

Yes, I wrote that sentence deliberately - it's hard enough to get players to report bugs without them having to go through a lot of maybes, that will make it less likely.

What we really don't ever need on the part of the devs is to get into a hostility match. In one of those feedbacks, one of the devs just couldn't let a player's exasperation slide - or answer with some understanding or honesty about what the player said.

All three players who posted the bugs deserve a thank you - and credit for the bug reports. One player deserves an apology from two devs.

What we don't need is more bricks in the wall between the players and the devs.

(Mon, 07/01/2013 - 19:23  |  3 comments)

Joined: 11/10/2007
Groups: Window Group
Status: Open » Open

Of course we are very thankful for the players reporting bugs, especially in devprev. I marked them as duplicate since they should all be resolved by the same fix. Duplicate isn't dismissive or disrespectful of the issue or the time spent finding it, but informational.

Joined: 04/19/2009

Thank you for the clarification.

Apologies if I am being too picky about this, but shouldn't the first feedback filed be the one "Resolved" and the following feedbacks be "Duplicates"?

In the future, it may be a good idea to expand on your designation from your perspective when you mark a Duplicate - from the players perspective, a Duplicate is just that, the same symptom filed more than once (since we have no way of knowing if the cause of a symptom is the same bug as a different symptom).

Joined: 11/10/2007
Groups: Window Group

Yes, we can try to keep the ordering of submissions in mind in the future.


Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons