fix(DB/Loot) Clean up loot of bosses in MGT HC #21262
Merged
+21
−0
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:
Remove Normal loot from all HC Bosses
Group items of Kael'thas
Issues Addressed:
SOURCE:
The changes have been validated through:
Counting drops in multiple videos

https://youtu.be/vRjgCtDOzo8
https://youtu.be/eps9m8S4cLc
https://youtu.be/nKSSYAkpW_s
https://youtu.be/o1FaN1_JIug
https://youtu.be/4ZHh5UhkGIE
https://youtu.be/My5ZrCZ8mok
https://youtu.be/L-eWJ_TdMSE
https://youtu.be/g5oA9_0s8CY
https://youtu.be/kVF_Di5CRKo
https://youtu.be/xkJysd5YOHI
https://youtu.be/C7nMa-cM4pI
https://youtu.be/13EsTeJmiPQ
https://youtu.be/kfZoZ5EVNCo
https://youtu.be/AN27RLSZXu4
https://youtu.be/eFILcvIVrEo
https://youtu.be/9MierCOmCmA
https://youtu.be/sQFQbzAk-7s
https://youtu.be/GJcy8cK0d10
https://youtu.be/CTddhJ9g5Lk
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.