fix: encumbrance indicator doubling on status change #1644
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
Have the dead condition check both lifeblood and stamina and not just lifeblood. Change healing order default for these systems too
github-actions bot
pushed a commit
that referenced
this pull request
Sep 26, 2024
## [5.8.4](v5.8.3...v5.8.4) (2024-09-26) ### Bug Fixes * encumbrance indicator doubling on status change ([#1644](#1644)) ([92a71e4](92a71e4))
|
🎉 This issue has been resolved in version 5.8.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bug fix
What is the current behavior? (You can also link to an open issue here)
Encumbrance can be double applied on status change
What is the new behavior (if this is a feature change)?
Encumbrance applied only once
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: