New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several blocks are not protected in claims #642
Comments
Seems something with beacons changed, even VNP spits out exceptions on it. |
It looks like some of the 1.14 blocks are protected where others are not. |
Hmm, I guess all of these don't extend Inventory or whatever it is that the containertrust check looks for. |
Ok so it seems all those blocks that aren't protected each have a special inventory but for some reason I can't find their respective blockstate... do they all not have their own blockstate? Or what is it that they inherit? |
Looks like blocking access to any TileState (barring lecterns, of course) would be a good way to go. |
Thanks for the fix. Do you have CI where I can download it from or do I need to compile it by myself @RoboMWM |
What happened:
I was able to edit and interact with beacons in claimed areas.
What you expected:
Beacons should be protected and only accessible with permission or trust access
Steps to reproduce:
This may include a build schematic, a video, or detailed instructions to help reconstruct the issue
Here's a gif: https://i.gyazo.com/5fa0a0fd0fcda41feef239f9eb7af2c3.mp4
Server and GriefPrevention version:
This can be found by running
/version
and/version GriefPrevention
on your server.Paste of
/version
: This server is running Paper version git-Paper-213 (MC: 1.14.4) (Implementing API version 1.14.4-R0.1-SNAPSHOT)Paste of
/version GriefPrevention
: GriefPrevention version 16.12.0-d4d7ac4Stack trace/error or server log
No stacktrace.
Or, paste the server.log at gist.github.com and paste the link here:
https://gist.github.com/N0tMyFaultOG/90eaaadc9415cc919818f90891acb1e6
GriefPrevention config.yml
Plugin list (if applicable):
GriefPrevention
The text was updated successfully, but these errors were encountered: