I think it's better to work on something quietly until it's ready rather than make sweeping promises that might not come true.
But I also think there's more to it.
How to say this? Hmm.
First, I think it's evident that they're reading the feedback.
So. What's the want? What is it that the "upset" people in the community want? Feedback on their feedback?
Consider, what would that feedback *actually* look like? People keep giving these vague examples of what they want. Things like, "We read your feedback and while we're considering blah, we haven't implemented it for blah reason..."
Well, what's that "blah" reason? Because when we start exploring this potential response, some reason ahs to be given.
And it doesn't serve Larian to get into an argument with some customer by having to tell them that their idea isn't any good. "We're not using your idea because we don't think your ideas are any good. In fact, we roll our eyes every time we read one of your suggestions."
You can ask that it be done tactfully, but there's only so many tactful ways of saying it, and I guarantee people will push for more and more in the way of explanations. They won't just accept a simple, "Great feedback, but that's not the direction we decided to go in." They'll want to know why. They'll demand that they be convinced. Which inevitably leads to: we don't like your idea. We don't think you're half as clever as you think you are.
What's the benefit of that? It takes two to argue, as they say. Luckily, Larian is above that. At least in my opinion.
