Change the damage effect calling EntityDamageEvent twice #3719
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
blek-id
reviewed
Jan 30, 2021
blek-id
approved these changes
Jan 31, 2021
FranKusmiruk
approved these changes
Feb 20, 2021
APickledWalrus
approved these changes
Mar 1, 2021
Whimsyturtle
approved these changes
Mar 21, 2021
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.
Description
Fix the damage effect calling EntityDamageEvent twice by adding an option to disable the damage checking. Mainly for developers that don't want the event to be called twice. Also cleaned up the coding and fixed a potential null pointer exception.
Related Issues: #3715