<< Reporting an Issue? Read Here First >>

[Mystique]

Please read this entirely before posting a bug. Below you will find the instructions on how to report a bug and the format it needs to be in.

Before posting, search our forums for possible issues already posted.



Bug Requirements

• No double-posting will be allowed. Search the forums for your issue BEFORE opening a new thread.
  
  • This allows the developers to quickly resolve an issue as well as help keep the forums organized.
  
  
• Tag your threads appropriately.
  
  • This helps your fellow community members and the dev team to quickly search for related items
    
  
  
• Must follow bug format listed below
  
  • Use the 'Table' functionality in the forums (must have WYSIWYG editing enabled)
  
  
• Include your computer specs in your topic
  
  
  • This will help members and the dev team to assist you in finding a solution to your problem
    
  • You can find your computer's specs by following this link, or you can use a 3rd party program called Speccy
    
  
  
• Email your DxDiag to [email protected]
  
  
  • Doing this will allow the dev team to better find the source of your issue
  
  

Bug Report Format

[Bug Title]	One sentence that easily describes the issue
Description of Issue	In detail, explain the bug encountered during gameplay
Expected Results	Let us know what you think the actual behavior should be. Example: When player hits 'Save and Quit', game should save and player should be able to resume game from last save point.
Repro Steps	These should numbered. Example: Launch the Ascend beta Create a Caos Etc.
Repro Rate	Let us know how many times you attempted to reproduce the bug and out of those attempts, how many times were you successful in reproducing the issue. Example: Repro Rate 6/10
Notes	This can be used for any notes you feel will be helpful to the development team.

[XShadowStormX]

I know this is asking a ton of information but if you can't give ALL this info upfront, please try to give as much as you can to help not only the QA process but the Development process.

Rule of thumb is: The more info you can get us, the quicker we can see it and the quicker we can fix it*! (*Hopefully*)

-Logan

Update: Thank you all for posting on each others questions and trying to limit the amount of posts I need to sort through.

Update-2: Thank you also for helping each other with steps to work around issues and going the extra mile to work as a community. You all make this job so awesome!

[Sean]

Remember everyone that all of this information is very important and including your computer's specs and emailing your DxDiag can really help fix the problems, as it's always better to include as much information as possible in the bug reports.