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:
I noticed that a small calculation error was made.
the Error was not due to loot %, but to a missing reference.
In essence, (I don't know if due to inaccuracy or laziness), a double reference was made in reference to the fact that a gem must always be guaranteed. (See screenshot below).
Wrong Reference
Consequently, this double reference led to a double loot with MaxCount "2", one given at 100% chance and the other given at 15% chance, giving rise to an "alteration" of the loot %. (See screenshots below).
Test 1 of 1000 Adamantite (Wrong Loot)
Test 2 of 1000 Adamantite (Wrong Loot)
Test 3 of 1000 Adamantite (Wrong Loot)
So I created an appropriate reference for guaranteed gems. (See screenshot below).
Fixed Reference
In fact, with this change, the loot now comes close to the expectations of the sources cited below
Test 1 of 1000 Adamantite (Fixed Loot)
Test 2 of 1000 Adamantite (Fixed Loot)
Test 3 of 1000 Adamantite (Fixed Loot)
These are the percentages and the tests I did.
Test Percentages
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Live research (checked on live servers, e.g Classic WotLK, Retail, etc.)
-- Prospecting
Adamantite Ore
yields unexpected results #14441-- https://www.youtube.com/watch?v=T0dDBoU0zF0&t=95s
-- https://www.youtube.com/watch?v=F2IM025ZL6s&t=707s
-- Prospecting Adamantite Ore yields too many uncommon gems chromiecraft/chromiecraft#4749 (comment)
Sniffs (remember to share them with the open source community!)
Video evidence, knowledge databases or other public sources (e.g forums, Wowhead, etc.)
The changes promoted by this pull request come partially or entirely from another project (cherry-pick). Cherry-picks must be committed using the proper --author tag in order to be accepted, thus crediting the original authors, unless otherwise unable to be found
Tests Performed:
This PR has been:
How to Test the Changes:
macro:
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.