85e46e06b2
* Boss re-order * Revert "Boss re-order" This reverts commit 03289cb064ae51c38e3efebba11f3e3882ae350a. * Reworking Ambassador flamelash - Removed timers - Scripting the boss properly, missing event and talk emote * Update boss_ambassador_flamelash.cpp * Update boss_ambassador_flamelash.cpp * Ambassador Flamelash reworked - Burning spirits spawn at the correct places - When they get close to the boss they die, thus buffing the boss with a stackable buff - When encounter begins the runes start burning - Burning Spirits chase the boss around the room * Missing aggro emote and cleanup * travis * Cleaner code Changed the enum usage to a Vector and iterated over every gameobject entry to make them active or ready. * Cleanup Removed not used enum * types * Update boss_ambassador_flamelash.cpp * Added dynamic spawning algorithm Before this commit, Spirits could be summoned on the same rune. After this commit Spirits will not be summoned on the same position. * bad null conversion * declaration and initialization inside function changed randomPosition to an Int inside the getValidRandomPosition(). * wrong type declaration variable needs to be declared outside of while cycle. * useless variable * Bugfixing - New fireblast - When burning spirits die killed by the player, new event to summon new ones - Make them aggro the player and attack them * miss typed ; * Trying to fix mentioned issues - If spirits are in combat, keep summoning new ones - If spirits are in combat, then the boss can't kill them if they get close to them * IsInCombat typo * Exploit fixing * Summoning massive waves fix * Fixing last issue hopefully
AzerothCore
Introduction
AzerothCore is an open source game-server application for World of Warcraft, currently supporting the 3.3.5a game version.
It is written in C++ and based on MaNGOS, TrinityCore and SunwellCore.
💰 You can support the project by financing the resolution of issues using Bountysource.
Why AzerothCore?
Our main goal is to create a playable game server, offering a fully working game experience. In short, we focus on the user experience (UX).
We also believe in software modularity, because the more the software is modular, and the more it will be easy to be maintained, understood, developed, etc... So we organized the structure of AzerothCore as modular as possible, giving the possibility to create new modules to add custom features (instead of patching the core).
Learning project
AzerothCore is a learning project. If you want to learn how to use C++, SQL, git, etc... you came to the right place! We will gladly help you: programming is our passion.
If you want to contribute, in our wiki you fill find a lot of resources that will guide you. Also you can poke us in our discord chat server.
Instructions & Support
Installation instructions are available here.
For help requests, it is recommended to ask your question on StackOverflow and link it in our chat.
Docker
Dockerization of AzerothCore is fully supported. More details about Docker and the setup instructions are available here.
Authors & Contributors
This project is brought to you thanks to:
- The AzerothCore developers and contributors
- The SunwellCore developers xinef and pussywizard
- All the TrinityCore developers and contributors
- All the MaNGOS, ScriptDev2 and UDB developers and contributors
License
- The new AzerothCore source components are released under the GNU AGPL v3
- The old sources based on MaNGOS/TrinityCore are released under the GNU GPL v2
Links
Sponsors
List of organizations that help the AzerothCore project:
