Exactly. But there's also a certain point I think a lot of people on these threads don't quite appreciate when giving feedback: that the devs will gauge feedback based on what is reasonable.
Some feedback would make a job overpowered or goes against its design philosophy; some would require far more work to accommodate than players understand due to system structures; some depreciates with time and changes in content; some is controversial, destructive or just plain bad faith. Now in my opinion as I'm sure with your own, there's plenty of honest and recent feedback about DRK's issues that evades those failings.
But when people spew insults, spread hyperbolic conspiracies ("dice theory"), or say "just delete the class already" (as I have seen dozens of times in these threads with regards to DRK since Endwalker dropped) in the official forums in the hopes the devs will read just what they think of them, they present their personal feedback as unreasonable and bad faith, focusing more on "giving a piece of my mind" than actually citing actionable criticism. (Especially once their demands are actually met and they don't bother to retract those conspiracies, either, just pocketing them for the next time.)
And when people start doing so in droves inside feedback threads, it makes large parts of the community seem unreasonable, and just as importantly buries the honest feedback.
There's a line between "They're ignoring our feedback and in fact actively making the job worse to spite us" and "They're sifting through a mountain of bile to find the gems, and working with what they can until they have enough." And there's already enough delay on that with the language gaps between the playerbase and dev team.
Even in the case of Ghostcrawler, what people didn't quite appreciate was that he was actively making himself the face of the dev teams because players would bash the devs until they got their way, and he often drew that attention to himself instead of the devs working on those jobs so they wouldn't crumble under the stress.



Reply With Quote

