Una seems to have been hit the hardest, but Enviska has been reported as well
Not entirely sure what you mean in the case of this thread about server issues – the issue was reported, escalated to ops which I shared so players could know they were heard, changes were made, and now players are reporting the issue has improved. I am not sure how I am expected to resolve things without letting the team know, and I would prefer to let players know we are aware while we are working on the resolution instead of waiting until it is fixed and waiting to share any info. We will make additional improvements in an upcoming maintenance, so I am letting players know what to expect looking ahead.
In terms of “fixing what is convenient for you,” I think there is a misunderstanding. Different branches of game development/publishing and the processes and requirements to make changes. For example, for something like server issues, we have a live ops team on deck that can make real time adjustments, changes or restarts to help improve these things quickly. For something like a game bug or issue, it will take QA testing, game dev/coding support, more testing, and a build deploy and downtime. When it comes to making bigger changes and employing player feedback, that takes even more design discussions on top of development, coding, and building, none of which happens overnight. These different types of issues are not 1:1, so comparing why certain things can be addressed more quickly than others is like comparing apples to oranges; we have different teams and paths that are involved in addressing different pieces of the game.