Fix undefined charges-max handling #36723
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ymber
added
<Bugfix>
|
You may want to add a "Fixes #35416" line to your PR description. This will the automatically close the linked issue when this PR gets merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
SUMMARY: Bugfixes "Fix spawn quantities with no max specified"
Purpose of change
Fixes #35416
Itemgroup entries that defined
charges-minbut nocharges-maxwere supposed to spawn the specified minimum up to the max of a container determined later. The actual behavior did not reflect the behavior described in the documentation.Describe the solution
Implement the behavior described in documentation.
Testing
Bleach and ammonia don't always spawn as 2 charges now.