merge_pbot #49
Merged
merge_pbot #49
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): 96ec2dc
azerothcore#20746) * File created * Added Disarm immunity * The mighty newline
Referenced commit(s): 3d5d300
azerothcore#20749) fix(DB/Spells): Malacrass Drain Power should stack from different casters
Referenced commit(s): 7fc938d
Create Scarlet_Captains.sql Fix for Scarlet Captains in DK Starting Area.
Referenced commit(s): 6ab70f0
Create Scarlet_Medics_Fix.sql Remove some wrong guids. Add waypoints for Scarlet Medics.
Referenced commit(s): 8a2ffc7
…thcore#20701) * Create Scarlet_miners_and_Cars_Fix.sql * Update Scarlet_miners_and_Cars_Fix.sql Missing Delete waypoint * Update Scarlet_miners_and_Cars_Fix.sql Removed Mine Car spawn points and spawn addon. Modified respawn timers for Scarlet Miners outside the mine. SmartAI Improved. * Update Scarlet_miners_and_Cars_Fix.sql Waypoints Improved. * Update Scarlet_miners_and_Cars_Fix.sql * Update Scarlet_miners_and_Cars_Fix.sql * Update Scarlet_miners_and_Cars_Fix.sql Add Comment in Scarlet Miners DBGuid.
Referenced commit(s): ff650d0
azerothcore#20756) * fix(DB/item_template): add flag CU_DURATION_REAL_TIME to Pilgrim's Bounty items * set duration to 7 days
Referenced commit(s): bcfcdbd
…ore#20754) * Initial Fix for azerothcore#20751 * Tighten timings * Condense Code * Move `ScheduleHealthCheckEvent` into `Reset()`
fix(Scripts/ZulAman)HalazziLynxAbilityTimers
logging stuff inserted into the correct area of the config file
… Hungry Nether Rays (azerothcore#20753) * Created File * Removed the prequiste quests * Space correction
Referenced commit(s): 2ff4788
Referenced commit(s): 9d42213
Referenced commit(s): 6ec4eb5
…azerothcore#20776) add prepared statements to escape special characters in branch name
azerothcore#20780) * fix(Scripts/ZulAman): Fix Vortex not following players and also spell missing * Update boss_zuljin.cpp
Referenced commit(s): 7ab4219
Add MovePointBackwards in MotionMaster.h
Referenced commit(s): 3acf687
Referenced commit(s): 5dfe897
Referenced commit(s): d949192
Referenced commit(s): 8f7fc6d
Referenced commit(s): 0e6fffa
Referenced commit(s): e6cf00a
…zerothcore#21057) Co-authored-by: Nicholas Lee <[email protected]> Co-authored-by: blinkysc <[email protected]>
Referenced commit(s): b6c9573
Referenced commit(s): e837fa8
Referenced commit(s): 106e0ed
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.