Npc bots #3
Closed
Npc bots #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Referenced commit(s): ec2dc73
Referenced commit(s): a78c751
Referenced commit(s): c097ffd
Referenced commit(s): 0191eed
Referenced commit(s): d05929b
* fix(Scripts/quest): Improve The Force of Neltharaku * update
Referenced commit(s): c6ae678
Referenced commit(s): 1050059
…core#17778) chore(Game/OutdoorPvP): cleanup ptr's, private fields
* chore(Cleanup): sort includes * fix build * fix build again
* fix(DB/Creature): Delete previous spawn of Leotheras * Update rev_1700326661784669100.sql * Update rev_1700326661784669100.sql
Referenced commit(s): 6c04b32
azerothcore#17781) * fix(DB/Gameobject): Sniffed Values for remaining 'Alliance Bonfire' spawns * update for compact DELETE statement
Referenced commit(s): 957dfeb
Referenced commit(s): 8feca90
azerothcore#17786) * fix(Scripts/SSC): Fix being able to damage Leo's minions if you are not the target player * implement helper * Update Creature.cpp * Update Creature.h
…ns (azerothcore#17783) * fix(DB/Gameobject): Sniffed Values for remaining 'Horde Bonfire' spawns * update for compact DELETE statement
Referenced commit(s): 8ea3d81
Referenced commit(s): e4f9dc4
Referenced commit(s): 2208bff
Referenced commit(s): c3f1181
…erothcore#17990) * fix(Scripts/Commands): fix wpgps and add sai option for formating * ???
Referenced commit(s): 65e88d2
Referenced commit(s): 0ab4931
azerothcore#17957) fix(DB/Creature): Sniffed Values for 26258 '[DND] Midsummer Bonfire Faction Bunny - A'
Referenced commit(s): b6a88ce
Referenced commit(s): f9e4edc
…azerothcore#17956) * fix(DB/Creature): Sniffed Values for 17066 'Ribbon Pole Debug Target' * add missing DELETE for creature_addon
…7964) * fix (Event/Midsummer): miscellaneous cleanups of spawns * update comments * add missing id1 filter to where clause * add missing ticks
Referenced commit(s): 0cb43f9
azerothcore#18002) * fix(Scripts/SerpentshrineCavern): Use proper spells to handle the Lurker spout rotation * Update boss_lurker_below.cpp
azerothcore#18003) fix(Scripts/SerpentshrineCavern): fix Hydross not casting Water Tomb & Vile Sludge
Referenced commit(s): a84a565
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.