Open
Conversation
Member
|
I'm not sure if this will be backwards compatible (ABI-wise), so you should keep the legacy EVENT type equal to previous one (Keep interface methods on old one and make Player extend it) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, we only have an event for block being broken by a player, but there is no way to detect block being broken for other reasons.
I added the
BlockBreakEvent#WORLDevent to detect any block being broken for any reason. The previous event has been marked as deprecated as it has been renamedBlockBreakEvent#PLAYERfor clarity.