60ac53ff07
* Core/Scripts: Fixed Vaelastrasz bomb mechanic Vaelstraz was suppose to bomb raid members that are mana users every 15 seconds. He was not doing that with the current implementation. This implementation allows him to bomb the raid and to select the proper targets. This is also done in a cleaner way. * Added AuraScript for SPELL_BURNINGADRENALINE Needed to define an AuraScript for custom behavior that would denatonate the damaging aura when the debuff falls off. SpellId - 18173 * Added SQL for Burning Adrenaline Script Ref * Fixed Multiple Application of BA * Add unit null check in lambda * Remove DB name from sql query * Added Newline in SQL update file. * Added SQL delete query for potential existing spell * Fix SQL newline again. * As suggested a simpler SpellCast overload works I don't know if there are any consequences but it seems to function fine in in-game. I'd like more information on the overload that involves an AuraEffect. * Remove duplicate Unit null check in lambda * Update boss_vaelastrasz.cpp
TrinityCore
Build Status
| 6.x | 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
Links
Documentation (powered by Doxygen)