Bugtracker

From BattleMaster Wiki
Revision as of 14:32, 3 November 2008 by Jmadsen (talk | contribs)
Jump to navigation Jump to search

The Battle Master Bugtracker for logging bugs and feature requests.

http://bugs.battlemaster.org/


How to use the Bugtracker

Reporting a new issue:

  • Login - you may log in as Guest, but we really do appreciate it if you give us a way to contact you. Many times we need clarification on an issue, and if we can't ask you, we will often just close the case because we don't understand.
  • Search - Search - At the top left of this page you will see "Search", and edit box, and "Apply Filter". Please try to search first on the most important words or error message (just as you would with Google, for example). Adding to an existing report is very helpful; creating duplicate reports slows us down.
  • Report - Report Bugs - If you cannot find anything that looks like the same case, report it as a new case.
  • Category - type of problem occurring. If you are not sure, go ahead and say "not sure".
  • Reproducibility - can you make it happen again? If possible, try again before reporting.
  • Severity (need to find list from docs)
  • Priority (need to find list from docs)
  • Summary - VERY IMPORTANT! Imagine you are going to search the web for this issue - Try to make it short but informative. Don't say it's a "bug" - we know.
  • Description - now you can say as much as you want. Try to reproduce the steps as best as you remember, and tell us your char's name, if he has a position or title, etc.
  • Game World - FEI and Beluaterra are testing islands, and run slightly different code, as does Dwilight, so this is important to us.


What next? Feedback:

Many cases will need us to contact you for more info, or to check if we fixed it. If we ask for feedback, please do your best.

What NOT to give us as feedback:

  • Silence - we are all volunteers. You asked us to take the time to look at a problem for you, so please follow up with us the best you can.
  • Related issues - we need you to open a separate case for related issues, unless you think that the same code bug might be causing it. For example, if the bug is "Priest cannot preach in enemy realm", don't add a separate issue about priests losing hours just because they are both "priest issues"
  • Discussions - the bug tracker is for collecting info on bugs. If you think a change should be made to the code, a value should be changed, etc., please take it to the D-list first. We are coders and can't make those decisions anyway, so you are just wasting everyone's time.
  • I can't check right now - this may be a necessary answer, but if you can ask a realm mate to look at something and get the answer, please do. We also use this:

Please Help - Issues the developers would like your help with in collecting data.