Allow testing protection rules without an entity event source #64
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
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.
Most players will want to test what protection rules apply to non-operator players with the
/protect testcommand, but running/protect testas an operator will almost always result in the "There are no authorities that apply to you at your current location!" feedback, which is a concern addressed in #38.This pull request changes the default behavior of
/protect testto not use an entity as context, with/protect test @sbeing similar to the current behavior.This pull request also fixes a null pointer exception when running the
/protect testcommand with a non-player entity command source.