# ![logo](http://www.trinitycore.org/f/public/style_images/1_trinitycore.png) TrinityCore [![Coverity Scan Build Status](https://scan.coverity.com/projects/435/badge.svg)](https://scan.coverity.com/projects/435) `3.3.5`: [![3.3.5 Build Status](https://travis-ci.org/TrinityCore/TrinityCore.svg?branch=master)](https://travis-ci.org/TrinityCore/TrinityCore) `4.3.4`: [![4.3.4 Build Status](https://travis-ci.org/TrinityCore/TrinityCore.svg?branch=4.3.4)](https://travis-ci.org/TrinityCore/TrinityCore) ## 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](https://github.com/TrinityCore/TrinityCore). For further information on the TrinityCore project, please visit our project website at [TrinityCore.org](http://www.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](http://collab.kpsn.org/display/tc/Win), [Linux](http://collab.kpsn.org/display/tc/Linux) and [Mac OSX](http://collab.kpsn.org/display/tc/Mac). ## Reporting issues Issues can be reported via the [Github issue tracker](https://github.com/TrinityCore/TrinityCore/issues?labels=Branch-3.3.5a). Please take the time to review existing issues before submitting your own to prevent duplicates. In addition, thoroughly read through the [issue tracker guide](http://www.trinitycore.org/f/topic/37-the-trinitycore-issuetracker-and-you/) 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](http://www.trinitycore.org/f/topic/6037-howto-maintain-a-remote-fork-for-pull-requests-tortoisegit/). ## Copyright License: GPL 2.0 Read file [COPYING](COPYING) ## Authors & Contributors Read file [THANKS](THANKS) ## Links [Site](http://www.trinitycore.org) [Wiki](http://trinitycore.info) [Documentation](http://www.trinitycore.net) (powered by Doxygen) [Forums](http://www.trinitycore.org/f/)