fix chest swapping after getting an error with pitch40 #4637
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.
Type of change
Description
When chestswap is set to 'always' and you get an error while enabling Pitch40 elytra fly (
"Player must be above uppper bounds!"
), the module itself remains disabled while your chestplate still gets swapped as if the module was active.Now the module has a chance to call its
toggle()
in peace without the chestplate getting swapped again by ElytraFly'sonActivate()
.How Has This Been Tested?
By seeing if it still swaps the chestplate for an elytra.
Checklist: