TrinityCore : The TrinityCore issuetracker and you

Proper issue self checklist

 Am I using an ancient revision/version and should update before reporting a possibly fixed issue?

 Am I using any modification to core or database that could cause this issue?

 Did I include the revision of the core I am using?

 Did I include the version of the database I am using?

 Did I include the operating system I am using?

 Did I include the steps to reproduce the problem?

 Did I explain what is wrong and what is the expected behavior/output?

Frequently Asked Questions

Why isn't last or latest a valid revision?

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.

Also, few hours after you describe your issue, the repository is likely to have more commits. That means that "latest" has changed and no longer describes the state of your core.

What constitutes a proper version/revision?

• Core example

  • TrinityCore Hash: c4818f189216 (Win32, Debug (little-endian)) (worldserver-daemon)

• Database example

  •  TDB 335.11.49

Why does my core display "0000-00-00 00:00:00" as version information?

Read How-to properly install Git on Windows

Issue description template

**What steps will reproduce the problem?**
1. 
2. 
3. 
 
**What is the expected output? What do you see instead?**

 
**What version of the core and database are you using? On what operating system?**

 
**Please provide any additional information below.**
 
 

While it is not mandatory to use the example above, we recommend it. (Adapted from Google Code)