e785b6d386
* scripted Captured Brave's behavior when released from their cages * respawned Armored Quillboars and got rid of duplicate spawns * scripted Armored Quillboar's visual events, combat ability and behavior when ignited via torch * added waypoints to Brave Windfeather * nuked cooler's shitty sai for chief squealer thornmantle and replaced it with a c++ script to handle the death spell cast event * corrected timers for Chief Hawkwind's ceremony texts * spawned a missing spellfocus and removed some gameobject spawns which are suposed to be tempoary * added some emote events to Camp Narache trainers
TrinityCore
Build Status
| 4.3.4 |
|---|
 |
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.68 (Linux) 1.70 (Windows)
- MySQL ≥ 5.7.0
- CMake ≥ 3.8.0 (Linux) 3.8.0 (Windows)
- OpenSSL = 1.0.x
- GCC ≥ 7.1.0 (Linux only) (clang 3.5 heavy recommended)
- MS Visual Studio ≥ 16.4 (2019) (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/The-Cataclysm-Preservation-Project/TrinityCore/releases
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. NOTE: if a fix is valid also for 3.3.5a/master branches submit them also to Github
Copyright
License: GPL 2.0
Read file COPYING
Authors & Contributors
Read file AUTHORS
Links
Documentation (powered by Doxygen)