Collection of planned and speculative features. Upvote your favorites!
What is the Feature Roadmap category?
In this category, we collect all the features that we are planning to implement or overhaul in the near or not-so near future or that we think might make for an interesting addition at some point down the line.
At the same time, anyone can upvote their favorite features to give us an idea of what people would like to see next.
How does it work?
We open one thread per feature. Regular users cannot open threads, but are allowed and invited to comment and discuss on feature threads.
If you would like to see a feature added to the roadmap, please use the regular “Ideas and Suggestions” category and when we deem a suggestion relevant enough, we’ll open a thread for it here.
What’s the impact of my votes?
You can upvote threads. This way, you can tell us which features are most important and/or interesting to you.
This does not mean that the overall vote counts determine the exact order of the items on our roadmap. It’s just a clue for us to see what people would like the most. At the end of the day, we will have to decide what makes sense at which point in time. For example, we might not be able to implement a new maintenance feature with C- and D-checks if we haven’t implemented a more powerful ops system first.
How many votes do I have?
The amount of votes anyone can cast depends on their “trust level” on the forums, ranging (right now) from 2 votes for the lowest to 10 votes for the highest trust level.
Votes can be cast for and also removed from any topic on the Feature Roadmap category.
Whenever a topic is closed or archived (aka we either decided shelve it or have implemented it), the respective votes are added back to your pool.
How can I tell which state a roadmap item is in?
All roadmap items are tagged according to their status:
- idea - Idea for a feature or change that might be a good addition to the game, but no concrete concept or plans exist yet.
- draft - Draft for a feature or change that is likely going to be implemented in the medium- to long-term.
- planned - A feature or change with finished specifications that is scheduled for implementation, albeit not necessarily with a specific date.
- in-progress - Feature or change currently being implemented. The respective topic will remain open for discussion, but there is no point in voting for a feature tagged as
in-progress. - done - A completed feature or change. The respective topic will be closed, any votes cast for it will be freed for re-use.
