f8d9d954d1
* Add new method Map::getFullVMapDataForPosition to get area info and liquid info in a single vmap lookup * Use this lookup in Map:: relocation methods to update m_areaId and m_zoneId fields on WorldObject * Adjust GetZoneId/GetAreaId on WorldObject to always return these cached fields * Clean up liquid state handling on Unit and Player * Hand floor's Z coord up through GetFullTerrainStatusForPosition, use it to update a new field in WorldObject, and use that to feed a new GetFloorZ call on WorldObject.
TrinityCore
Build Status
| 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 Gitlab 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.55 (Linux) 1.63 (Windows)
- MySQL ≥ 5.1.0
- CMake ≥ 3.0.2 (Linux) 3.3.2 (Windows)
- OpenSSL = 1.0.x
- GCC ≥ 4.9.2 (Linux only) (clang 3.5 heavy recommended)
- MS Visual Studio ≥ 14 (2015) (Windows only)
- zlib ≥ 1.2.7
- ZeroMQ:
- apt-get install libzmq-dev (Linux only)
- x64 - https://miru.hk/archive/ZeroMQ-4.0.4~miru1.0-x64.exe (Windows only)
- or x86 - https://miru.hk/archive/ZeroMQ-4.0.4~miru1.0-x86.exe (Windows only)
Install
Detailed installation guides are available in the wiki for Windows, Linux and Mac OSX. You can get database from https://github.com/TrinityCoreLegacy/TrinityCore/releases
Reporting issues
Issues can be reported via the Gitlab 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. NOTE: if a fix is valid also for 3.3.5a/6.x branches submit them also to Github
Copyright
License: GPL 2.0
Read file COPYING
Authors & Contributors
Read file THANKS
Links
Documentation (powered by Doxygen)