|
When something is suggested and doesn't appear on the website, it doesn't mean it's not an excellent suggestion. There are a lot of different considerations that go into deciding what gets implemented by our dev team. Sometime a feature doesn't make the cut because it would be too taxing for the servers, or it would take a lot of time and effort to implement. Sometimes it's not the feature itself, but something else that would need to be reworked that would take a lot of effort. And sometimes it's just a matter of priority. Believe it or not, but our dev team is always working on something. The to-do list is very long, and it doesn't always make sense on what needs to be done first. Sometimes what we are working on is invisible -- an internal optimization, or fixing a browser issue that was introduce in the new version of Chrome, or Firefox, or mobile Chrome, or Safari, etc. etc.. Web browsers also sometimes drop support for some features, or web standards change, so we have to fix something before it breaks. But from the user perspective, absolutely nothing changed. Sometimes features get implemented, but don't make the cut during testing, because they end up being not that useful -- and we don't want to add features just for the sake of adding something, as it will make GameKnot too cluttered. All of that is why we have a policy of never commenting on what we might be working on, what might be implemented next, or when, or why. We do appreciate and consider *all* suggestions, of course.
|