fix(Core/Comments): Clarify quest level hiding configuration comments #23805
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:
Minor comment fix. Current comment implies that quests that are EQUAL TO Low/HighLevelHideDiff or more are hidden, when it's actually only quests that are MORE THAN Low/HighLevelHideDiff that are hidden. The logic can be seen at PlayerQuest.cpp with
CONFIG_QUEST_LOW_LEVEL_HIDE_DIFFandCONFIG_QUEST_HIGH_LEVEL_HIDE_DIFF.Screenshot for example. If the comment was correct, then at default value of 4, this level 14 marker should be hidden from level 18:

Second,
-1 - (Disabled, Show all available quest marks)is removed as a possible option. Note the comment and code logic in WorldConfig.cpp:A config of -1 is rejected as the bound is MAX_LEVEL. It errors out if you use it:
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.