What is the enhancement in mind? How should it look and feel?
Since CoreProtect already logs block breaks and placement via MySQL so effectively and efficiently, would it be possible to add an option in the config or a permission that would prevent players from breaking blocks another player had placed?
In essence, a check, occurring at a logged break, to see if the block was placed by another player. If the block was placed by another player, then automatically roll back the breakage.
I imagine it wouldn't need to query every player name, just check if the block location was logged, and if the player name was /= to the player who placed it.
Please provide any additional information below.
This is by far one of the best, most efficient MySQL plugins I've ever used. We're dealing with hundreds of players and tens of thousands of blocks breaking daily without any noticeable impact on performance. I think adding something like automated rollback support would just further cement CoreProtect's awesomeness.
To post a comment, please
or register a new account.