ChromieCraft.com Bugtracker
FOR PLAYERS: how to report bugs
-
Check the bug list and see if the bug has already been reported. If yes, open the report and write a comment "confirmed".
-
If the bug has not been reported yet, please create a new one. Please fill all the requested details.
FOR CONTRIBUTORS: how to triage/report bugs
Triage
It is duty of the AzerothCore contributors, or anyone in general that wants to contribute with the ChromieCraft project, to:
-
Verify the issues reported by the users (check validity, duplicates, etc...). All issues awaiting to be triaged are marked as [needs triage].
-
If the issue is not valid (missing information, not a bug, etc...) it should be closed (or ask the user for clarification).
-
If the issue is valid and the bug can be reproduced on a clean AC server (at a recent version), it's needed to open a report on the main AC repo. You can literally copy-paste the issue from ChromieCraft to AzerothCore, as the template already contains all information needed for AC. In addition, add the link of the original issue reported on ChromieCraft ("Originally reported LINK-TO-CHROMIECRAFT-ISSUE"). This way GitHub will automatically link the two reports.
-
On the issues reported in the AC repo, it's needed to add the proper label, for example [1-19].
-
On the issues reported on the ChromieCraft repo, mark them as LINKED adding the proper tag. Once the linked issue on AC has been closed, we can add FIX-READY to the ChromieCraft report.
-
Admins will close all FIX-READY marked issues as soon as ChromieCraft gets updated with the latest AC
Report
If you find a bug yourself, you can report directly to the AC repo. You can copy paste this template and just fill the bug description.
Links
Project by Brackets: LINK - Here you can find the projects subdivided by brackets to check the status of the technical progression
AzerothCore bugtracker: LINK - This is the official bugtracker of our gaming core