* Issue 22974: Initial bugfix suggestion. * Fixed allignment. * Removed unused call. * Initial spider spawn targeting is done. * Resolves issue 22874. Initial implementation suggestion. * Commenting out dead code. * Reordered private members to meet standards of member initializer list. * Removing unused parameter and changing data structure from list to vector. * Changed list to vector in the grid notifier. * Removing comments and fixing identation. * Stupid collapsed blocks. * Scripts/Misc: Change IsSummonedBy(Unit*) to IsSummonedBy(WorldObject*) * Scripts/Misc: Fix build * Core/TempSummons: Rename GetSummoner() to GetSummonerUnit() * Core/TempSummons: Add support to TempSummons::GetSummoner() to return GameObject too * Fix build * Core/TempSummons: Allow GameObject to be owner of TempSummon * Core/TempSummons: Add support to SAI for GameObject owner of TempSummon * Scripts/Misc: Fix no-pch build * Cleaned up all the core changes and scripted eggs and spell according to pull request comments. * Fix no-pch build. * Fix no-pch build 2. * Added sql file for the spell and gameobject script. * Update 2019_05_20_00_world.sql * Added conditions to spell thanks @xvywh and some minor changes to the code. * Removed some strange leftovers. * Removed obsolete brackets. * Rename 2019_05_20_00_world.sql to 2019_05_24_00_world.sql
TrinityCore (3.3.5)
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.