ExprLastDamage - fix everything #6797
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
sovdeeth
approved these changes
Jun 28, 2024
sovdeeth
added
bug
Pikachu920
reviewed
Jun 30, 2024
| set last damage of {_e} to 3 | ||
| assert last damage of {_e} = 3 with "last damage of entity should be 3 after setting to 3" | ||
|
|
||
| # thank you for your service |
Pikachu920
approved these changes
Jun 30, 2024
sovdeeth
added
the
patch-ready
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.
Description
This PR aims to fix the
last damage of %entity%expression.Someone recently stated in a help channel it threw errors.
Lo and behold it was riddled with errors.
I'm not sure how this got merged, it was horribly broken.
This fixes it, and has been tested well.
Target Minecraft Versions: any
Requirements: none
Related Issues: none