Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE
README.md
_config.yml

README.md

TBC5ManTracker

Bug Tracker for TBC 5 Man www.tbc5man.com

(Old Tracker - https://github.com/TBC5ManTracker/TBC5ManIssues)

Report should be named in a way that would identify the problem at the first sight. You have to write what’s the problem about in square brackets (which raid, class, etc.). For example: [Warrior] Sweeping Strikes, [Black Temple - Mother Shahraz] Adds deal too much damage, [Warsong Gulch] wrong flag respawn timer.

Every bug has to be described thoroughly. “Quest X doesn’t work” is simply not enough. You have to write what exactly is happening and what should happen.

Every bug should be reported with the following pattern:

Decription: How it works: How it should work:

To make things get fixed faster, you should write the steps to reproduce said bug under “Steps to Reproduce”.

“Additional Information” section should contain IDs of every spell, item, game objects, etc. You need to add them via link: https://tbcdb.com/. Additionally, you should show here evidences that this is indeed a bug, not an intended action.

It is very important to provide as much data as possible so we can spend more time fixing your issue instead of trying to figure out what you are communicating. Screenshots or other visuals are highly recommended!

Reports that do not meet requirements listed above can be closed without further investigation.

You can’t perform that action at this time.