The wiki is located at http://trinitycore.info.
You are welcome to create an account and help us improve and extend the wiki.
Read this before creating a ticket.
If you have problems with TrinityCore instalation, read http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/ and http://www.trinitycore.org/f/topic/10656-updating-or-starting-with-trinitycore-issues/
Platform: Linux, Windows or Mac
Processor with SSE2 support
Boost ≥ 1.4.9
MySQL ≥ 5.1.0
CMake ≥ 184.108.40.206 / 2.8.9 (Windows / Linux)
OpenSSL ≥ 1.0.0
GCC ≥ 4.7.2 (Linux only)
MS Visual Studio ≥ 12 (2013 update 3) (Windows only) (we recommend Visual Studio community 2013)
In case you choose Linux, we recommend to use Debian 7, it's the Linux we use to test compilations.
Remember 4.3.4 and 6.x branches are alpha, only intended for development, we don't recommend this branch to run a server, use git clone -b 3.3.5 http://github.com/TrinityCore/TrinityCore to obtain a playable branch.
When creating patches read:
We suggest you to create one branch for each
C++ based fix: on that way you can continue creating more fixes without having to wait to get one pull request merged.
SQL files of
C++ based fixes the naming schema is:
YYYY_MM_DD is the date of the fix,
ii_database is the ith sql created that day for
When doing changes to
characters database remember to update the base files (
For SQL only fixes create a ticket.
Suggestion: When creating one pull request with sql files attached name the sql file by the PR id it will use.
IE: 2015_02_24_14000_world.sql on that way you don't need to update the filename if the filename you tried to use is used after that by any commit on that day.