IrritAnt
08-30-2004, 07:02 PM
HOW TO LOG A BUG
1. SEARCH TO SEE IF IT HAS ALREADY BEEN POSTED
People use many different terms for the same thing, so you might have to search more than once to make sure.
If it's an easy-to-spot bug, it has probably already been posted and logged, but if in doubt, post it anyway.
DO NOT POST UNLESS YOU HAVE SEARCHED.
2. IS IT REALLY A BUG OR JUST FEEDBACK?
A bug is an unintended effect. If you want to give feeddback or ask for a request, please don't post it as a bug. Also please note that we are feature complete, which means no new features will be included in the game. Balance changes and tuning will be considered on merit but they're not bugs.
DO NOT POST EXPLOITS. PM me with them instead.
DO NOT POST BUGS THAT OCCUR AS A RESULT OF EDITING YOUR .INI FILES MANUALLY. If you edit your .ini files and discover an exploit, PM me with the details.
3. GIVE YOUR BUG A MEANINGFUL TITLE
For example, " Chaingun problem" is not a good bug title, but " Firing chaingun makes spinfusor sound" is.
[B]4. INCLUDE A COMPLETE DESCRIPTION OF THE BUG
What happens when you experience the bug?
What map did you see the bug on? Does it happen on other maps? Which ones?
Which server were you playing on? What was your connection like? What was your ping?
What else were you doing when the bug occured? What had just happened in the game?
Is there anything else you think may have contributed to the bug?
We know it may not be possible to include all the above information, but the more information you can include, the easier it is to diagnose the bug.
If the bug caused a crash, copy and paste any information from the crash window.
[B]5. INCLUDE INSTRUCTIONS ON REPRODUCING THE BUG
Where possible, include detailed instructions on how to make the bug occur.
6. LINK TO SCREENSHOTS, VIDEOS OR INI FILES
Where possible.
To take a screenshot, open your console by pressing TAB and type "renderdetail 3", press enter, then press F9 to take the screenshot. The shots show up as BMPs with a "Shot0000" prefix. Convert your BMPs to JPGs!
7. INCLUDE YOUR SYSTEM SPECS
Processor
Motherboard
RAM
Operating System (including which service packs you have installed)
Video card and memory
Sound card
Any other hardware details you think are important.
If you follow these guidelines, we can minimise the number of posts in the forum and work through the posted bugs a lot faster.
Thanks for all the hard work you guys have done so far. Keep it up!
Cheers,
1. SEARCH TO SEE IF IT HAS ALREADY BEEN POSTED
People use many different terms for the same thing, so you might have to search more than once to make sure.
If it's an easy-to-spot bug, it has probably already been posted and logged, but if in doubt, post it anyway.
DO NOT POST UNLESS YOU HAVE SEARCHED.
2. IS IT REALLY A BUG OR JUST FEEDBACK?
A bug is an unintended effect. If you want to give feeddback or ask for a request, please don't post it as a bug. Also please note that we are feature complete, which means no new features will be included in the game. Balance changes and tuning will be considered on merit but they're not bugs.
DO NOT POST EXPLOITS. PM me with them instead.
DO NOT POST BUGS THAT OCCUR AS A RESULT OF EDITING YOUR .INI FILES MANUALLY. If you edit your .ini files and discover an exploit, PM me with the details.
3. GIVE YOUR BUG A MEANINGFUL TITLE
For example, " Chaingun problem" is not a good bug title, but " Firing chaingun makes spinfusor sound" is.
[B]4. INCLUDE A COMPLETE DESCRIPTION OF THE BUG
What happens when you experience the bug?
What map did you see the bug on? Does it happen on other maps? Which ones?
Which server were you playing on? What was your connection like? What was your ping?
What else were you doing when the bug occured? What had just happened in the game?
Is there anything else you think may have contributed to the bug?
We know it may not be possible to include all the above information, but the more information you can include, the easier it is to diagnose the bug.
If the bug caused a crash, copy and paste any information from the crash window.
[B]5. INCLUDE INSTRUCTIONS ON REPRODUCING THE BUG
Where possible, include detailed instructions on how to make the bug occur.
6. LINK TO SCREENSHOTS, VIDEOS OR INI FILES
Where possible.
To take a screenshot, open your console by pressing TAB and type "renderdetail 3", press enter, then press F9 to take the screenshot. The shots show up as BMPs with a "Shot0000" prefix. Convert your BMPs to JPGs!
7. INCLUDE YOUR SYSTEM SPECS
Processor
Motherboard
RAM
Operating System (including which service packs you have installed)
Video card and memory
Sound card
Any other hardware details you think are important.
If you follow these guidelines, we can minimise the number of posts in the forum and work through the posted bugs a lot faster.
Thanks for all the hard work you guys have done so far. Keep it up!
Cheers,