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.
* Ignore Eclipse build/project artifacts.
* Fix Maven convention: rename src/tests/* to src/test/*
* Update Maven test dir. Remove directory specs for src, test, & rsrc.
${project.basedir} is the default directory. Only add directory
spec if different from convention.
According to #97 hyperconomy loads after GP. See #97 for discussion and etc. on a proper way to fix/avoid requiring this for any other economy plugins that happen to load before GP does.
* Configurable time until sieged claim is resecured
Fixes#113.
Makes the five minute period after winning a siege, during which the claim is
not secured, customizable.
* Make trapped words fully configurable.
Before, it contained hardcoded checks; the value of
`Messages.TrappedChatKeyword` was in addition to the hardcoded ones.
Make it more flexible, so you can override them entirely (and provide as many as
you want, comma-separated), and an empty value disables the message totally.
(Default value is 'trapped;stuck' to provide the same behaviour the hardcoded
checks did.)
In case they actually aren't and lagged out (perhaps due to chunk
loading), they'll have a few seconds to be able to walk out before being
automatically rescued on reconnect.
Also logs when a player has been rescued
Prevent players from creating a claim if _any_ part of their claim includes a worldguard region they cannot build in. (Previous behavior only prevented claiming if the entire claim was within a worldguard region the player could not build inside.)
Show the claim size to those with griefprevention.seeclaimsize when right-clicking with the investigation tool
(stick by default) - it's not exactly private information, the claim boundaries
are visualised so it would be easy to just count the blocks or compare the
coords of the corners to find out.
