Tholis

I am unsure of the size of the development and what you use internally for tracking issues/code management. So this could already be covered or might be more effort than it is worth. My suggestion is to improve the tracking of suggestions and feedback from the user community by implementing some form of tracking. This could be something as simple as a locked sticky with headings for planned features/accepted suggestions/rejected suggestions etc. or as complex as an issue tracking software like JIRA. Having a central place to check to see if a suggestion has been made already would be of benefit to the users reducing the amount of searching that has to be done, and would provide us with solid confirmation as to if the feature would be implemented and perhaps a why if not. The forums are great I'm not attempting to say other wise, I'm just a fan of centralization. This gives both the players and the developers a single place to look, reduces re-posts and helps spur suggestions/creativity. Gathering the listed suggestions into an easily readable place will get people thinking as they read over suggestions other players have made. I expect it might result in an uptick in feedback. Just a few thoughts thanks for Reading!

Thanks for the Video, it was very helpful! A number of my early designs weren't built to be easily upgrade able, so it was very helpful to update components buried at the core of my ships. I was wondering if you or the developer had a list of all of the block types that could be provided, I.E. Hanger XXX, engines are XXY. Doing a full replacement based solely on materiel type would be very counter productive for me. I'm sure I could work out the all of the block IDs Thought I'd save some time though. Thanks again.