356f3b6bc5
Suggest everyone attempt to remember this: TC_LOG_TRACE = extreme debugging (debuginfo with packetstructures/data) TC_LOG_DEBUG = debugging (detailed activity of functions and activites inside core) TC_LOG_INFO = normal runstate (regular info like logins/logouts/levelups/passwordchanges etc) TC_LOG_WARN = possible issue with config/data etc - things that are not how they should be) TC_LOG_ERROR = actual error that has been either caought or must be fixed at some point TC_LOG_FATAL = crash or data corruption imminent Using the right logmech also helps distinguishing between 'regular runtime info' and stuff that might lead to a pissy situation later on... :)
TrinityCore
6.x: 
4.3.4: 
3.3.5: 
Introduction
TrinityCore is a MMORPG Framework based mostly in C++.
It is derived from MaNGOS, the Massive Network Game Object Server, and is based on the code of that project with extensive changes over time to optimize, improve and cleanup the codebase at the same time as improving the in-game mechanics and functionality.
It is completely open source; community involvement is highly encouraged.
If you wish to contribute ideas or code please visit our site linked below or make pull requests to our Github repository.
For further information on the TrinityCore project, please visit our project website at TrinityCore.org.
Requirements
- Platform: Linux, Windows or Mac
- Processor with SSE2 support
- Boost ≥ 1.49
- MySQL ≥ 5.1.0
- CMake ≥ 2.8.11.2 / 2.8.9 (Windows / Linux)
- OpenSSL ≥ 1.0.0
- GCC ≥ 4.7.2 (Linux only)
- MS Visual Studio ≥ 12 (2013) (Windows only)
Install
Detailed installation guides are available in the wiki for Windows, Linux and Mac OSX.
Reporting issues
Issues can be reported via the Github issue tracker.
Please take the time to review existing issues before submitting your own to prevent duplicates.
In addition, thoroughly read through the issue tracker guide to ensure your report contains the required information. Incorrect or poorly formed reports are wasteful and are subject to deletion.
Submitting fixes
Fixes are submitted as pull requests via Github. For more information on how to properly submit a pull request, read the how-to: maintain a remote fork.
Copyright
License: GPL 2.0
Read file COPYING
Authors & Contributors
Read file THANKS
Links
Documentation (powered by Doxygen)