From: Brooklyn, NY
Here's some tips for making effective and useful tech support posts.
Is it a feature request?
If you would like a feature added, we have a dedicated thread for feature requests that includes polling. That is the best place to put your feature request. Here on the tech support forum, feature requests are likely to get overshadowed by more pressing issues.
Is it a database request?
There are dedicated threads for DB3K and CWDB database update requests, which have dedicated staff to monitor and manage them. Again, here on the Tech Support forum these items are likely to get overshadowed by more pressing issues.
Is it a bug?
Every post here gets attention from the dev team, and our time is limited. Before posting please be sure that what you're reporting is something that genuinely needs attention.
Use a descriptive title and avoid entering your own [Tags]
Summarise the issue into one sentence. This is your post title
Titles like 'Strange issue...' 'Bug?' 'Something not right' etc aren't descriptive at all and don't help in prioritising issues.
While it's well intentioned, adding tags or comments in square brackets doesn't help us--since that is what we use to mark posts for our reference, it actually means your post is more likely to be overlooked!
Build numbers are sometimes helpful, but please avoid using square brackets in your post title.
One issue per thread
If you have multiple issues, please post them in separate threads. Multiple posts on the forum are not a problem, but reporting two issues in one thread means that there is a possibility of one being overlooked (and more work for us to split the issue into two tickets whether it's overlooked or not)
Provide detailed information, and a save file wherever possible
In order to resolve an issue, we first need to replicate it. In a game as complex as Command, replicating a particular set of circumstances independently can be almost impossible.
The easiest way for us to replicate the exact game conditions that relate to your report is to provide a save file.
If we ask for a save file, please provide one. It takes less time to save the game, zip it up and upload it than it does to write back and tell us we don't need a save. If we're asking for a save, we are asking because it will help in getting your issue resolved--not because it's fun to ask for saves
Beyond save files, detailed information is crucial. A thorough explanation of what happened, what the expected behaviour was, and step-by-step walkthrough of the events leading up to it will see your issue resolved much faster.
Thanks for reading!
< Message edited by VPaulus -- 12/24/2019 3:12:27 PM >