* Update to include 1.17 materials and tags
* Use world height for claim max height
* Account for worlds with min height < 0
Fix restore not working under y 0
Change default max claim depth to integer min value
Fix creative claims always going to 0, not world min height
* Update material listings to include new blocks
* Fixes a few missed cases from previous versions
* Replaced claim to bounding box bandaid for world max height increase with actual world limit
* Account for worlds with min height less than zero
* New default maximum depth is now integer min value (-2147483648) to not restrict users no matter how weirdly they set up worlds
* Creative claims always extend to world min height, not 0
* RestoreNature restores to a max depth of world min height instead of 0
Closes#1309Closes#1431
Also contains a bit of refactoring on internal logic. Modifies (secondary) siege mechanics.
* Un-couple siege from core claim functions
* UUID overload, documentation, naming clarity
* Add internal special message override support
* Fix permission calculation issues in subclaims
* Migrate egg handling to new methods
* Use suppliers for denial message
In many use cases addons don't care why a denial occurred, only that it did. On-demand calculation is vastly preferable to reduce server impact.
Very likely I was going to refactor this class, but then stopped since
it's abstract and thus can't have any constructor... but apparently I
forgot to revert that line.
Closes#377
1. Claim creation event... this is fired once all the claim creation checks have been passed. It can be cancelled. It contains the claim and the creating player
2. Claim modification event - this is fired as the claim is modified - it cannot be cancelled. It contains the claim and the modifier...which can be null.
Use Case:
This could be used so other plugins can hook gp and perform an action if a claim is created or changed. Something as simple as logging claim creations/modifications and deletions.
akastijn
Teriuihi