f026a42c20
It will be removed after 2 weeks for several reasons. Some of them: It was heavily abused and creates not obvious and thus dangerous logic in scripts, making them easily breakable. In lots of cases was used as hacky version of Cross Cast(one creature applies aura on another creature) while it should be casted by creature and not applied to it by another creature. In some cases it was used to ensure aura will be applied always (something like casting a spell with triggered cast flag). In nearly all other cases used for no reason. There's no such action in Blizz's scripting system, the reason why some auras are applied without SPELL_START and SPELL_GO has to be different. On top of that some auras in addons are channeling spells, some has effect Spawn, some has on-cast visuals. Using AddAura breaks them. That means if Blizz indeed used some kind of system only for on-spawn spells, all spells are casted or some are handled in another place.
(cherry picked from commit e96c713815)
TrinityCore (master)
- Build Status
- Introduction
- Requirements
- Install
- Reporting issues
- Submitting fixes
- Copyright
- Authors & Contributors
- Links
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 macOS.
Install
Detailed installation guides are available in the wiki for Windows, Linux and macOS.
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; if a bug report exists for the bug, post on an existing ticket.
Copyright
License: GPL 2.0
Read file COPYING.
Authors & Contributors
Read file AUTHORS.