Improve monster whitelist & blacklist docs #55711
Merged
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.
Summary
None
Purpose of change
Addresses the documentation tag on #30851. Related to #55189.
MONSTER_WHITELIST
is currently undocumented.Describe the solution
Add documentation. Also cleans up a couple related areas.
Describe alternatives you've considered
None
Testing
Additional context
Whitelist/blacklist precedence is in MonsterGroupManager::monster_is_blacklisted()
Swapped out the
No Ants
examples since it's no longer a core mod.The linked issues suggest that the evolution code doesn't check whether a monster is blacklisted. I was not able to reproduce that but this doc at least represents what the feature is supposed to do.