Not tested, but other than maintaining SQL storage "compatibility" I've
removed all usages of it. It doesn't seem to be used at all anyways
other than to be stored since commit
f935806b45 removed its purpose.
Addresses a request in #22
Seems like this check was intended for the
"portalCreationRequiresPermission," so when he threw in the portal trap
check, he didn't account for this check possibly breaking in worlds
where claims aren't enabled.
- Cancel existing rescue tasks on successful teleport
- Send the player a message when they are rescued (unfinished)
Someday, I will make this OOP-compliant
Wait longer before deciding the player is trapped, since some players
stand still and wait longer while chunks load around them. (10 seconds
-> 60 seconds)
If they log out while trapped but before the auto-rescue task runs, this
will save them when they log back in as long as the plugin hasn't
rebooted since they left.
Easily replaced if 'stolen', and might actually belong to a player who
drove the boat into the land claim. Allow well meaning visitors to take
their boats with them when they go rather than leave boat litter behind.
New problem in 1.9. Fix: GP's claim modification tool now exclusively
works with GP and doesn't have any other functionality (Vanilla or other
plugins, unless other plugins subscribe to cancelled player interact
events).
Mostly these are deprecations from the Spigot team which I believe
shouldn't be deprecated. For example, players refer to each other by
name, not UUID - so there will always be a need for player lookup by
name. Also the block IDs are a well-documented standard that everyone
understands, even if they're not very human-friendly. Plugins use those
IDs and data values to specify block types for example in config files.
As for the rest of the ignores, I either decided the warnings are just
noise based on the situation, or that I'm comfortable with the risks.
Possibly for the first time in 5 years of dev work on this plugin, I
just compiled without any warnings. :)
And whispers. Doesn't soft mute player or explain, just cancels the
command. If player is brazen and goes to standard chat, then he'll get
muted there.
