-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
Falling Blocks bypass Build perms #6312
Comments
I should add this isn't really an issue; I was working on patching for my own use but I didn't find any mention of it so I thought it was worth noting in-case it's not intended |
Is there even an event for when sand goes airborn? |
Not that I can find - my way of patching was (in my mind so maybe doesn't work out this way) to try and block it when the sand block is created; if the origin was a falling block In saying that; it would break falling sand from people who do have perms so it's 50/50 I can't find anything on Spigot for becoming a falling block however |
Apparently EntityChangeBlockEvent can record both it changing into & from a falling block In theory then the location can be checked on both? |
If that's teh case then something can be done. |
Warriorrrr with PR #6307. - Displays a player's nation name or, if no nation, their town name or, blank if they have no town. - Closes #6294. - Prevent falling blocks from being launched into towns, courtesy of Warriorrrr with PR #6314. - Requires your server to be using Paper, Spigot does not have this in their API. - Closes #6312.
What steps will reproduce the problem?
What is the expected output?
I guess that the sand breaks on landing like when it lands on slabs?
Towny version
Reproduced on multiple servers; but on my own: Towny-0.98.4.0
Server version
1.19.2 PaperMC
Please use Pastebin.com to link the following files
(optional) If this is to do with permissions,
5. Your permissions file: No perms used besides TownyPerms
(optional) If this is to do with chat,
6. Your chatconfig.yml:
7. Your channels.yml:
The text was updated successfully, but these errors were encountered: