Blue wrote:Theres often lots of chaos in our bugreports which causes unnecessary bugfix delays. Because of that I want you to adhere to some rules in the bugreport section.

First of all, read this website to get insight into effective bug reporting. I can tell from my own experience that bugs which are reported chaotic or with missing information often won't get fixed or will just be ignored.


Whats important in a bug report:
------------------------------------------

1.) One thread per bug. Use a meaningful topic for the thread!

2.) What is the bug? (Proof by chat logs, screenshots, videos, own test results)

3.) Desired behaviour? (Proof it by, videos from live servers or even better with own tests on live servers - if this is not possible proof by links to web sites could be used to back up your claims)

4.) How to reproduce the bug? Which steps are exactly needed to reproduce the bug? Please tell every detail.

5.) Which preconditions or settings are needed to reproduce the bug? (Class, Level, Spec, ...)




In a bug thread focus on the bug only. Don't pollute the bugreport with flame or other unrelated stuff. Follow up posts to a bug report should help to better identify the bug or add bug related informations. Never ever start nonsense discussions about the staff or bugfixing policy!

If bugs are reported with complete informations outlined above there is a good chance that a bug is corrected in a timely manner.

Blue



Edit: rewrite of step 3 to make it clear that live tests will always be needed to back up your claim - websites can only be used as evidence when tests are unable to be made (like with volley, and other archery issues that has been changed on live)


Nixian