The TrinityCore issuetracker and you
Posted 27 December 2010 - 11:24 PM
What we require when you file an issue :
VERY IMPORTANT, WHY THERE IS NO LATEST: on github after 1 month we can't known the date the issue was posted, and because that we can't known the revision
Never ever test things with GM accounts
- Update your core before reporting a bug, the bug of ancient cores can be fixed on newer cores.
- Add which revision of Trinitycore you're running on (this is the CORE revision, not your client version)
- Add which database, and what revision, you run on. Remember, you can get the most updated TDB from Downloads · TrinityCore/TrinityCore · GitHub
- Add a list of which modifications that has been done to the core (if any) if those modifications aren't public available you must share the code if you/we see that they can be reason of bug, if you don't use a clean core and you don't share the code if it afects the bug or the files of the bug (crash) the ticket will be closed.
- Supply links, spell ids, full spell names, npc ids, npc guids, npc names, gameobject ids, gameobject names detailed, we don't must guess what mob/instance/spell you are talking about.
addon to help you with ids: http://www.curse.com...other-downloads get 3.3.5a version.
Example CORE revision number : b1e2cdb905d6a92edeb505eff968d26c453b252b (LAST is not a valid number), there are 40 Time Zones from UTC−12 to UTC+14, we don't known on what Time Zone you live, for me Today is 31 of July, for someone on Honolulu it's 30 of July.
Read Howto properly install git on Windows. - Help and Support - TrinityCore if you can't get something like TrinityCore Hash: c4818f189216+ (Win32, Release (little-endian)) (worldserver-daemon) when you use server info on console.
Example DB revision number : TDB 335.51
The above is VERY important, so add this when reporting! Any ticket without this info will be closed without notice.
If today is the first day of the rest of your life, what the hell was yesterday?
Posted 03 June 2013 - 08:43 PM
Issues · TrinityCore/TrinityCore · GitHub
Supplement your crash reports with back traces - any issues reported as a crash report and not having a back trace attached will be deleted on sight.
DO NOT DIRECT-PASTE CRASH DUMPS INTO THE COMMENTARY FIELD - USE ATTACHMENTS OR A PASTEBIN THAT DOES NOT EXPIRE (avoid to use paste2.org)
Don't post Release mode crashlogs, they are useless for devs, any crashreport on release mode is almost imposible to fix. On windows machines copy .pdb files to your server's directory, Linux uses read How-to:Advanced:GDB - TrinityCore Wiki
Please note that you MUST search through the existing issues to avoid duplicate reports - duplicate reports are bad, and you're way better off adding to existing reports if they are of the same type.
Also, for the simplicity of it, when filing reports, our trackers attachment feature when attaching fixes, code snippets etc.
DO NOT USE PASTEBINS THAT EXPIRE FOR FIXES OR CODE SNIPPETS, IT MAKES IT WAY HARDER FOR US TO KEEP TRACK OF YOUR ISSUE/REPORT/SUGGESTION
Posted 03 June 2013 - 08:46 PM
- Patches : MUST be attached as a file in diff/patch format
- SQL-files : MUST be attached as a file
- Do NOT paste patches/SQL-files into the tracker as regular text in the commentary field
- Make sure the diff/patch uses CORRECT PATHS (no subdir diff of a random directory on your machine)
- When multiple diff/patch/sql-files are involved, or require more than 4-5 files to be uploaded, consider attaching it as an archive ( .zip file )
Also, it seems like certain elements in the community like to think the issue tracker is a forum, and attempts to "BUMP" issues. Here's some news to those of you that think so :
Our tracker's issues CAN NOT be "bumped" - the only thing you do is add noise to the issues you attempt to bump.
In short making it harder for us to actually SEE what a problem might be; don't do it!
Posted 03 June 2013 - 08:50 PM
- Make sure you are running on the latest revision of the source (we are constantly pushing changes, so your issue might have been resolved already)
- When testing for bugs, make sure you are NOT running a modified core (test without ANY custom patches at all, even if it's just a tiny text change)
- Don't ask when something will be fixed (it will be sorted as fast as we can, or when someone has the time to look at it)
- Don't claim that your issue is "very important" (every issue is equally important to us - the only exception is when it crashes the core AND have a proper crash dump attached)
- Don't claim that a change "makes function XXX unusable/unplayable" (give a FULL and DETAILED report)
- Don't posts multiple bug reports on a single ticket, unless they are directly related, and no, reporting all the bugs of one raid don't fits on "directly related", because if no, we can put all the bugged quests on a single ticket
Posted 03 June 2013 - 08:51 PM
- Levels over 80 into master branch.
- Gear modification (increased damage/hp/mana/custom models/etc).
- Custom spells/items/npcs.
- Ancient revisions, when reporting a bug please update at least to the current TDB version.
- Non-TDB databases.
- 3rd party TC branches.
And to make it a little not-so-harsh for those that actually DO understand what the tracker is and use it correctly :
Your feedback is, as always, important to us, and we appreciate the testing and information that you assist us with.