Important notice #2: You are not be able to respond to threads in this forum; this was done because fully moderating this forum is no longer an option for technical reasons.
Welcome, bug hunters!
First of all, thank you for taking the time to help improve the quality of Natural Selection by reporting any bugs that you find. Having quality bug reports from a broad base of users is extremely important in order to quickly find and fix as many bugs as possible. Please keep the following in mind, especially if the current build is a public beta:
* Some known bugs will remain unfixed in each future release. This has been true of every NS release to date and is true of pretty much any software release ever.
* Please do not contact the NS team directly (via any method) with bug information unless specifically asked to do so. This forum is the official place to submit all bug reports. The only time you should ignore this rule is in the case of an exploit that allows users to crash the server or other players, or would in other ways render the game unplayable. In these instances PM, via the forums, JazzX or Grepdashv with relevant information.
* This forum is to be used exclusively for reproducing and reporting bugs. Posts that simply complain about bugs or posts on any other subject (such as gameplay or balance) will be moved or deleted without notice.
Bug reporting process:
Here's the process to follow if you think that you've found a bug.
1. Determine whether or not the observed behavior was really a bug or not. If it was a gameplay, balance, or configuration issue, then do not report it here. The only (and very rare) exception to this rule is if you find a perfectly valid configuration option that doesn't work as expected (such as not being able to use a certain key for a certain command). Check the release changelogs to make sure that what you're seeing wasn't simply an intended feature or change.
2. Check the list of Known and Logged NS Bugs and search this forum to see if the bug has already been reported. If it has been reported but the thread is still open and more than 60 days old, you may report it again with a link to the old thread.
3. If the suspected bug you found is not already mentioned in the forums or the database, try to reproduce it reliably. Try it on different maps and under different circumstances. Take good notes on exactly what the issue is, plus how to simply and reliably reproduce it. If it occurs seemingly at random, do your best to make it occur as often as possible before moving on to the next step. If you are only able to reproduce a bug some of the time, please use the
icon for your post, and prefix the title of your post with "Suspect:".4. Give your bug notes to a few friends, and have them attempt to reproduce the bug independently. If they are all able to reproduce the bug, then move on to the reporting step. Please do not report issues that happen only to you. If you suspect that a valid configuration option is causing the problem, then have two friends try using the same settings as you. If the problem happens to them, too, then it may be a bug, so please do report it in that case. If you need help with this step, you may request help from other users in this forum, but please use the
icon for your post, and prefix the title of your post with "Repro:".5. Report the bug by posting a new topic in this forum. Please include only one bug per topic. Do not report bugs using any other method. When writing your post, choose an appropriate title and description. Titles like "new bug" or "problem with onos" are not likely to receive prompt attention. Browse the titles in the bug database to get an idea of what is appropriate. In the main body of your bug report, always cite the exact build in which the bug was found. Please use the
icon when creating a bug report post, and prefix the title of the topic with "Report:".Have fun playing and testing!