You’re right - the onus is of course on Funcom here, regardless. I’m just saying that they are obviously listening to the community this time, and they’re trying to actually do something about it - unlike some other developers I’ve dealt with in the past. Humans make mistakes. It’s part of being human. At least these guys can admit to it and they’re trying to do something about theirs. Compared to what they did the last time a mistake was made: this course of action was definitely a better call than the last one they made of simply “boosting” the resource gain for a while and calling it a day so at least we can see that there is some improvement going on here, and that they’re actually listening to their community feedback.
Now they just need to work on taking action QUICKER and making better plans for situations like this in the future. Despite the mess that this fiasco has created, I can see that there’s at least some progress being made here and there’s at least a bit of light shining through at the end of this currently dark and scary tunnel so lets not overreact here (as it seems to be the popular thing to do these days) and try to look at the bright side of things for a change.
1 Like