I think negative feedback would hurt more if the devs expected an overwhelmingly positive response to the game after all the effort they put in. There are no doubt things in the game big and small that they're very proud of, and nobody talks about them nearly as much as the faults, or worse, finds fault with those things! I can definitely see that as a possibility. And so I can see how negative feedback could be morale-crushing.
The title of this thread has the answer: "thick-skinned". I would dismiss equally both praise and criticism that is poorly constructed or doesn't state reasons for why it thinks what it thinks. I would respect feedback both positive and negative that comes from a place that ultimately respects the game and its creators.
I would try to sort the facts from the opinions: for instance, there is little respect in which a bug can be considered not to be bad, but other things can be dismissed as a matter of taste and preference. For instance, I think BG2 superior to DA:O on the grounds that it was very oriented around large side-quests that were not connected to the main story, whereas another person may prefer DA:O on the very same grounds, i.e. that it is more focused on the main story. The devs made it one way and not the other for a reason, so you could easily disregard criticism that offers this reason for why it criticises since they consciously chose not to make the game that way
Incidentally, the REASON why I prefer BG on this ground is that, psychologically, it moves the goalpost further away--each quest solved unrelated to the main story mentally puts distance between me and the end of the game and makes it last longer--conversely, each quest solved that is related to the story brings the end visibly closer (although this is illusory if I am going to explore all content anyway)--and ironically it's to DA:O's credit that I can criticise it for this reason, since it implies that I want it to last longer.
I would try to view negative feedback as material for making the game better. If nobody points out holes in the ******, it is going to leak all the same. It's down to the dev's' discretion as to whether a hole is a hole or not, and then what to do about it (I know, not the best metaphor).
David Gaider wrote...
With constructive criticism, certainly. Constructive criticism is awesome. The mistake is assuming that any criticism is constructive. Some people are convinced that because they are RIGHT everyone should listen to them, and that if they aren't being listened to clearly what's called for is a more forceful declaration of how very RIGHT they are -- and constructiveness is thrown out the window. Constructiveness requires listening as well as speaking.
I assume you're speaking generally, rather than consumers giving feedback on the forum. In the latter case the devs would necessarily be predominantly in the role of listener. But I'm listening, if you could make use of it.

RunCDFirst wrote...
They do, and I'm sure some of their co-workers think they are crazy because of it.
Is it taboo or something?
Modifié par fro7k, 04 décembre 2009 - 06:28 .