* 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.
comment in #1107
c7327d4#diff-bd72da6eb91964fbaa474bafcaac56434a55926a9743ec41c3dba6de30eedc86L531
This is when it changed, when he added the multiple accrual rate
permissions.
- /accesstrust for viewing (with a config to disable permission requirement)
- /containertrust for modifying
Closes#537
Co-authored-by: Zedadias Wick <zedwick@gmail.com>
Defaults to true to remain consistent with behavior of preventing
enderman from taking blocks and entities from trampling crops
Closes#530
Also intellij is insistent on replacing tabs
- Claim expiration collects all players (uuids) that own claims, and
iterates this set instead of iterating through every single claim.
- Individual claims had a "last modified" timestamp, so this method was
valid before, but makes no sense now since expiration is based on player
inactivity instead of claim inactivity.
New config option under the advanced node allows controlling the
frequency each player in the aforementioned set is checked for
inactivity.
