[SQL] Audit mob droplist - 31 to 60 #6891
Open
+196
−248
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.
I affirm:
What does this pull request do?
Continues the work outlined in #6756.
Highlights for the first time in these PRs are Nyzul and Beastmen. Vigil Weapons and ??? items are handled in nyzul.lua. These Nyzul SQL drops result in incorrect (unappraisable?) ??? items as well as duplicate drops of vigil weapons. At the same time these dropids are not wasted as the same foes are lacking their ordinary drops which are being added.
Beastmen throughout the sql have incorrect drops and extras they shouldn't or frequently have the same drops and rates across zones. Dungeon beastmen drop equipment but Beastmen in the field do not. In the future you will continue to see Beastmen moving around the file or being merged and their dropid made available. The armor from these Beastmen begins at an ungrouped Very Rare, 1% and quickly becomes rarer as the level of the equipment increases.
Steps to test these changes