By tkrokli Closes #17334 (cherry picked from commit 951d0f579480773f4f9f2c9dca8ec0a97ac680a2) DB/Quest: Improvements for quest "Bitter Rivals" By SnapperRy Closes #17267 (cherry picked from commit 16fa58176820a458eae0f7a2be1e527a33dd1d6b) DB/SAI: Mebok Mizzyrix By Rushor (cherry picked from commit 51a34eb135b27061f49349ca6af35479fac773c7) DB/SAI: Cabal Ritualists By Malcrom Closes #17212 (cherry picked from commit cc7adf9f9cf49633ba76b5ebc86e69af382ea839) DB/Creature: RP event with Jane, Nova & Jessel Closes #17164 By lyn1337 (cherry picked from commit cf398f2d2e946a91cebf791ebaac993ef890c283) DB: Fix a DB error (cherry picked from commit 88f1de12e42d6b1c21ca17f050a4b4d8172cf28d) DB/Loot: Fix some drop rates Closes #17139 (cherry picked from commit bd3bfc4ce127cdacb4b0e582609bf495bb6186ab) DB/Creature: Add FLAG_EXTRA_NO_PLAYER_DAMAGE_REQ to some npcs Closes #17045 (cherry picked from commit 777910141c187db5c241b98b558f65d5dc7d1cd3) DB/Quest: Fix locales for Nessa Shadowsong quest Closes #17345 (cherry picked from commit 0676622f4ea2d766f124211c99756a77d3376cf5)
TrinityCore (master)
Build Status
| master | 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
Software requirements are available in the wiki for Windows, Linux and OS X.
Install
Detailed installation guides are available in the wiki for Windows, Linux and OS X.
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
C++ 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. For SQL only fixes open a ticket or if a bug report exists for the bug post on existing ticket.
Copyright
License: GPL 2.0
Read file COPYING.
Authors & Contributors
Read file THANKS.