connection-lost / lockettepro

LockettePro - A much better Lockette plugin for Bukkit [1.8 - 1.12]

LockettePro

LockettePro - A much better Lockette plugin for Bukkit

LockettePro is a block-protection plugin based on Lockette (https://github.com/Acru/Lockette), the code base is entirely re-written. It is 100% compatable with original Lockette, and the plugin behaviors are also 100% same.

LockettePro has a lot of enhancements compared to Lockette:

1. Much better codebase and performance, fixed a lot of issues and glitches.
2. Real UUID support.
3. All blocks can be set to lockable or not. You can even prevent players from locking a chest.
4. Unlimited [Private], [More Users], [Timer:x] signs format.
5. Alert messages are editable, and UTF-8 characters are supported.
6. Lock expircy feature, locks can expire after a certain amount of time.

Links

Spigot release page: https://www.spigotmc.org/resources/lockettepro.20427/
Bukkit release page: http://dev.bukkit.org/bukkit-plugins/lockettepro/
MCBBS release page: http://www.mcbbs.net/thread-567962-1-1.html
MC 1.6~1.7 Port: https://github.com/connection-lost/LockettePro/releases/tag/v1.9.4

lockettepro's Issues

Griefprevention is not supported

My players are able to lock others doors and diamond blocks in other claims. These problem only covers door and diamond blocks. Plugin works fine for locking chests.

Feature: Able to Disable Protection against Explosion

As Brocoee's request on SpigotMC forums. Will be useful on faction servers.

[Feature] ShulkerBox block sign

the signs is NOT working for shulker box blocks.
Can you add support for shulker box? Is similar with chests.

Quick protect

If quick protect is set to true, sneak-clicking should place the sign normally. Otherwise players have no way to place signs on chests and edit the lines, such as with chest shop plugins.

Everyone not working when UUID is enabled

Player who create an [Everyone] sign automatically add the player name and uuid to the second line, so only the player could break or lock the block/chest.

Could not pass event PlayerInteractEvent to LockettePro v2.8.1

[20:06:37] [Server thread/ERROR]: Could not pass event PlayerInteractEvent to LockettePro v2.8.1
org.bukkit.event.EventException: null
	at org.bukkit.plugin.EventExecutor$1.execute(EventExecutor.java:46) ~[patched_1.12.jar:git-Paper-1134]
	at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:74) ~[patched_1.12.jar:git-Paper-1134]
	at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[patched_1.12.jar:git-Paper-1134]
	at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:514) ~[patched_1.12.jar:git-Paper-1134]
	at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:499) ~[patched_1.12.jar:git-Paper-1134]
	at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:235) ~[patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.PlayerInteractManager.a(PlayerInteractManager.java:448) ~[patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.PlayerConnection.a(PlayerConnection.java:948) ~[patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.PacketPlayInUseItem.a(PacketPlayInUseItem.java:37) ~[patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.PacketPlayInUseItem.a(PacketPlayInUseItem.java:5) ~[patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.PlayerConnectionUtils.lambda$ensureMainThread$0(PlayerConnectionUtils.java:14) ~[patched_1.12.jar:git-Paper-1134]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131]
	at net.minecraft.server.v1_12_R1.SystemUtils.a(SourceFile:46) [patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:842) [patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:423) [patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:766) [patched_1.12.jar:git-Paper-1134]
	at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:664) [patched_1.12.jar:git-Paper-1134]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Caused by: java.lang.ClassCastException: org.bukkit.craftbukkit.v1_12_R1.block.CraftBlockState cannot be cast to org.bukkit.block.Sign
	at me.crafter.mc.lockettepro.Utils.updateSign(Utils.java:85) ~[?:?]
	at me.crafter.mc.lockettepro.Utils.putSignOn(Utils.java:61) ~[?:?]
	at me.crafter.mc.lockettepro.BlockPlayerListener.onPlayerQuickLockChest(BlockPlayerListener.java:63) ~[?:?]
	at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor628.execute(Unknown Source) ~[?:?]
	at org.bukkit.plugin.EventExecutor$1.execute(EventExecutor.java:44) ~[patched_1.12.jar:git-Paper-1134]
	... 18 more

Ender Crystal will damage the locked box

Ender Crystal will damage the locked box

Security leak with S*******

Reported by one of my player, people can pull items from a fully-locked chest with S*******. Just simply create a [Slot] shop with S******* and link the sign to the locked chest, then you could easily steal stuffs from it by clicking on the S******* sign.

Tested on S******* version 2.11.0 and LockettePro 2.7.0. Spigot version 1.11.2 with build number 1210.

I'm not sure if it's also broken with the [Buy] shop. May have to give it a try later on.

If you want more info please feel free to ask.

UUID Signs are not Hidden in 1.9

If UUID feature is turned on, signs with UUID in 1.9 will look ugly because UUID part is not hidden. This is due to packet format changes and needs to be reworked.

最新版的LockettePro和Plotsquared插件依然有点问题

如图 成员XYBlues 是可以锁箱子的
但是 可信成员XYBlues1 无法锁上箱子
我需要让可信成员也能锁上箱子
给予成员的指令为/p add 玩家
给予可信成员的指令为/p trust 玩家

Permission Group support

Just like in the original Lockette, group support for permission plugins would be nice. That way we can lock doors to a specific group. See original Lockette discussion.

Additionally, you can enter [Everyone] on lines 3 or 4 instead of a user name to allow everyone access to the contents of a private container, or [Operators] to allow ops access. If a Permissions plugin is available, you can use groups like [Moderator] or [Admins] or others as defined in the Permissions settings files.
https://bukkit.org/threads/sec-lockette-simple-chest-and-door-lock-no-databases-moved-to-bukkitdev.4336/

Feature Request: uSkyBlock compatibility

Can you make this plugin uSkyBlock compatibility? Players can only lock blocks in their islands.

bed explosion can break chest

odd warn exception

09.06 03:12:19 [Server] WARN [LockettePro] Plugin LockettePro v2.7.0 generated an exception while executing task 84
09.06 03:12:19 [Server] INFO java.lang.NoSuchMethodError: org.bukkit.Server.getOnlinePlayers()[Lorg/bukkit/entity/Player;
09.06 03:12:19 [Server] INFO at org.mcstats.MetricsLite.postPlugin(MetricsLite.java:285) ~[?:?]
09.06 03:12:19 [Server] INFO at org.mcstats.MetricsLite.access$200(MetricsLite.java:51) ~[?:?]
09.06 03:12:19 [Server] INFO at org.mcstats.MetricsLite$1.run(MetricsLite.java:173) ~[?:?]
09.06 03:12:19 [Server] INFO at org.bukkit.craftbukkit.v1_11_R1.scheduler.CraftTask.run(CraftTask.java:71) ~[custom.jar:git-Spigot-3fb9445-6e3cec8]
09.06 03:12:19 [Server] INFO at org.bukkit.craftbukkit.v1_11_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:52) [custom.jar:git-Spigot-3fb9445-6e3cec8]
09.06 03:12:19 [Server] INFO at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121]
09.06 03:12:19 [Server] INFO at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121]
09.06 03:12:19 [Server] INFO at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]

Maven repo available?

So we can use the API and not need to copy/paste binary jars everywhere.

User without Lock Permission Can Create Locks with no Own

I use the permission nodes which don't allow use of this plugin until a certain rank. Rank2 is when players can lock stuff on my server, and Rank3 is when they can start editing their Lockette signs. When a player who is not yet in the correct rank (Rank0-Rank1) and does not have the permissions to lock anything, when they try to lock something, the result is a lock which nobody except an Admin can open or break. The [private] tag on the first line remains while the other 3 lines are blank, essentially locking a chest or door for nobody. It's impossible to stop players from trying to lock things before they are in the correct rank, so this bug is a real hassle.

Unable to Lock Chest in Player's Residence Area

Hello,

I use LockettePro with Residence plugin. I'm OP, Residence admin, and lockette admin but i can't
locket a chest in players residence.

Can you add a bypass for op or admin please ?

Thanks you

Timer not working on fence gates

PhanaticD:
https://www.spigotmc.org/threads/lockettepro-uuid-support.133105/page-9#post-1889453

1.12 Interacting with sign cause them to appear invisible

Hi, in 1.12, when placing a LockettePro sign or opening a chest that is protected, causes the sign to appear invisible to the user.

Admin cannot edit More Users Sign if Sign is on the Other Double Door

Feature: Option to Set Lock Expiry Time

Config example:

lock-expire-days: 30

Admin can not edit other players' sign after transfered from the original Lockette

Tested on:
Spigot 1.11 build 1101
LockettePro 2.6.4

(English)
Admin/moderators are unable to right click on other player's signs even with permission lockettepro.admin.edit. So there is no way for editing those. Such an issue occurred with the previous lock signs after I have replaced Lockette with LockettePro. There is no exception from the console while testing.
And this problem seems happened with all the signs created, especially after server restarted, even after LockettePro have been installed.
Yet I have no problem with Ops.

Please consider fix it since LockettePro is a great plugin and I don't want to give it up.

Thank you!

ps: if you want any further tests please feel free to ask me. I'm very happy to help.

(Chinese)
即使设定了lockettepro.admin.edit权限，我的管理员仍然无法右键点选其他玩家创建的牌子锁，所以管理员也无法编辑玩家的牌子锁。这个问题是在我更换Lockette插件为LockettePro之后发现的。右键牌子时后台没有任何报错。
这个问题貌似不仅针对原来由Lockette创建的牌子，即使是更新到LockettePro后新创建的牌子也存在同样的问题，特别是在服务器重启后。
然而OP并没有遇到这个问题。
请修复这个问题。LockettePro是个很好的插件，我不想把它换掉。

谢谢！
ps: 如果你需要人测试欢迎随时联系，我很乐意提供帮助。

Support for PlotSquared and aSkyBlock - 添加对pltosquared和askyblock插件的支持

使用plotsquared地皮插件时
当我给予他人use 开门权限
但是不给予放置权限时
玩家依然能锁住他人的门
请添加对plotsquared支持 谢谢了
askyblock 插件也是同理...

disable-explosion-protection: true is broken

disable-explosion-protection: true is broken with latest version (on spigotmc) of LockettePro, we're not able to blow up Lockette protected chests with TNT/Creepers.

Add Permission regarding Colored Locked Signs

Our server give 'color chat' and 'color code sign' permission for only server sponsor.
But I found default user can add color code sign through /lock command.
How about adding color code permission on this plugin at next update?

Thank you a lot.

Can't find 3.0 download

Ok ok, I know you've probably not built it, definitely haven't released it. But I need it. Specifically, the sign expiry.

It would also be nice if you could add these features:

1. Add configurable requirement that LockettePro signs be made only in the user's GriefPrevention area
2. Add config to allow signs to be removed by LP plugin when GP area expires / is removed by player
3. Add config option to allow Auto-extend expiry of signs in GP area (in case option 1 above is turned off)

I would be OK with the auto-expire part though. Great plugin otherwise, just see a lot of abandoned locked chests that my players can't do anything with, even though the rest of the build can be dismantled and salvaged. Or even claimed.

Any help and progress towards this end would be great!

Thank You :)

Feature: Able to Erase Lines from Sign

Command example:

/lock 3 {nothing here}

Feature Requst: Only quick protect specific blocks

Hi. I made every block lockable. But i only want quick protect feature for chests, hoppers etc. Can you make configurable quick protect blocks?

1.12 Iron Doors

Hi,

In 1.12, iron doors that have lockette signs do not open on right click. Does output noise.

No errors in logs

How do I give you a translation file?

How do I give you a translation file?

#LockettePro

Allow correct handling UUIDs on a mixed-mode server

I have noticed that after setting enable-uuid-support: true, LockettePro can not let offline(cracked) players access to any chests/doors with their name correctly writen on signs. But It is no problem with premium players.

So I'm guessing this is the problem with UUIDs handling inside of LockettePro (not detecting offline player's UUIDs for example). Could you please add support of "offline UUIDs" when enable-uuid-support is set to true? Our server is running on a kind of mixed-mode which allows both premium and offline players join the server. By using a plugin called "FastLogin" (https://www.spigotmc.org/resources/fastlogin.14153/), my offline(cracked) users can have their offline-uuid and all my premium can keep their online-UUIDs(UUIDs assigned by Mojang) allowing them to change names on Mojang.

FastLogin is a great plugin. It is very useful when we decided to switch to online mode without losing all of the previous players we had. I believed that that are a lot of servers using this type of plugin as well. So please consider this feature.

A possible way to support such a feature is just to read the player UUIDs from the server. So LockettePro don's have to query the Mojang API every time when checking "who can open the chest". All you have to do is to get the player's UUID from bukkit/spigot directly then compare it to the storage.

Another way I could think of is to try to generate the offline UUID by name (https://gist.github.com/games647/2b6a00a8fc21fd3b88375f03c9e2e603). Then compare it with the player after he/she failed the premium-UUID check.

Thank you! And if you need any tests please ask me at any time. I can put you dev builds on my server for trial :)

Players without permissions can lock chests

When creating new Lockette sign you put extra white spaces after "[private]" and it allows you to create private signs even if you don't have permissions for it. You also have to type your username in second line in order this to work.

ShulkerBoxes

Even when adding the blocks manually (through id or through white_shulker_box) It will not lock shulkers at all.

using lockette with worldguard

Hello. i have an issue with being able to lock chests in a worldguard'd region.

steps to reproduce: install lockette and worldguard and worldedit. test that lockette works on a chest bydefault. then select and define a region with worldguard using a woodenaxe and /rg define xxxx. test lockette again with all default settings on everything. does not work, and i have all admin prermissions and op.

to go further, giving normal users rights to break and build blocks does not work either, even though they can place and take away the chest just fine and use it too. however placing a sign on the chest is greeted with "you cannot use lockette on this chest" and i don't know why. i've enabled all flags i could think of and it still doesn't work... and its not permissions because even i have all permissions and it still doesn't work.

i've been looking around for hours for anything on this and not one single forum post about using worldguard and lockette together. only in worldguard's page it mentions to use lockette instead of its chest thing and here, says just to give players rights to break blocks. none of that helps.

minecraft version 1.11.2. worldguard 6.2 (the one that supports 1.11.2 because the lastest version does not and would not work.) and most recent version of lockette from this exact page.

is there any suggestions to try... or a known fix for to be able to use worldguard with lockette?

Shulker Box

can't private shulker box

Can not support 1.7.10? 不支持 1.7.10 吗？

Sorry for my bad Chinese:
请问该插件不支持1.7.10吗？经过我的测试我发现1.7.10的确存在很多问题，我使用的是Thermos服务端。感谢您提供这么优秀的插件和给我的答复！
如果不支持1.7.10，那能否让其支持呢？因为现在还有很多的开服的朋友使用1.7.10版本呢。

能用中文交流真是太好了，英文越发无法让我表达清除我说的话的意思，我越来越感觉英文的26个字母与中文的几万亿方块字是无法相比的。中文是一门博大精深的语言。

Timer doesn't work

I'm using Bukkit 1.9.2 and the newest LockettePro plugin version. and the timer function does not work on single or double doors if the sign is used on a bottom block (to hide it). This is true for iron and wooden doors and also for locked doors which were locked with the original Lockette plugin.

Bug LockettePro

Chinese ver : LockettePro 铁门有一个BUG，如果在别人空岛( ASkyBlock )可以锁别人的铁门
即使权限有锁

English ver: LockettePro can lock other player island ( ASkyblock ) 's iron door which locked the permission

Feature Request: Get [Private] name automatically

Request: On a player write to sign's first line [Private] and click done, plugin will automatically set second line his name.

Why i want this:
Players can forget writing their name to sign when first line is [Private] and second line is [Timer:@].

[CRITICAL BUG] Losing blocks

Version Information:
LockettePro: 2.6.4
Spigot: 1.8

Bug Information:
A player sent me a bug report about losing spawners. When you try to put a spawner on locked spawner your spawner is losing and block not being placed. Than i make a video to reproduce. Also is it a bug not to put another block on the blocks?

Video:
https://youtu.be/ov5swAc6wVs

最新版的LockettePro在PlotSquared地皮中有一个问题

当 将被上锁物放在个人地皮的最边缘时，对被上锁物右键牌子，牌子将会被放置在地皮的半砖边界上，无法敲掉。

Feature Request: Make all blocks lockable

Hi. My players can make every block lockable in old Lockette. Can you also add this feature. I don't want add every item id to config.

Suggestion: Auto Lock Blocks

Hi, i have a suggestion. When a player place a block that specified in config, block automatically locks. For example automatically add a lock sign to a mob spawner block when it placed.

Ditch PlayerInteractEvent and use BlockPlaceEvent all the way

Inspired from issue #46

It is currently possible to ditch PlayerInteractEvent in quick-lock and use BlockPlaceEvent + ProtocolLib to deny sign editor to pop up. The potential gain is remove all unnecessary permission check and increase compatibility with block loggers.

"Fix" Residence Compatibility

The residence api has changed unexpectedly since version 4.5._13.2 286. LockettePro had to update in order to be compatible with that version, but support for previous versions breaks.
There are a lot of people got frustrated with this problem, mostly because they failed to use the correct plugin version. This need to be addressed.

Feature: [Fee] tag

No other chest/door lock plugin has a feature to charge economy money for use.

The idea is to add a fee to a door/chest so that anyone not listed on the sign could use it for a fee, using iconomy / Vault, the money should go to the first person on the sign, or perhaps split evenly between all names. If a locked door/chest doesn't have the fee tag, it works as normal. A permission node for adding the 'fee' tag would be useful, or else a "reverse node" like you have for making and editing. I also think it would be a good idea to have a confirmation message for paying the fee since i know people would hide the sign and charge ridiculous amounts of money.

Unhandled exception occured in onPacketSending(PacketEvent) for LockettePro

[17:33:15 ERROR]: [LockettePro] Unhandled exception occured in onPacketSending(PacketEvent) for LockettePro
com.comphenix.protocol.reflect.FieldAccessException: No field with type net.minecraft.server.v1_8_R3.NBTTagCompound exists in class PacketPlayOutUpdateSign.
        at com.comphenix.protocol.reflect.StructureModifier.readInternal(StructureModifier.java:219) ~[ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.reflect.StructureModifier.read(StructureModifier.java:198) ~[ProtocolLib.jar:4.3.0]
        at me.crafter.mc.lockettepro.DependencyProtocolLib$1.onPacketSending(DependencyProtocolLib.java:71) ~[LockettePro.jar:?]
        at com.comphenix.protocol.injector.SortedPacketListenerList.invokeSendingListener(SortedPacketListenerList.java:195) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.SortedPacketListenerList.invokePacketSending(SortedPacketListenerList.java:149) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.PacketFilterManager.handlePacket(PacketFilterManager.java:588) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.PacketFilterManager.invokePacketSending(PacketFilterManager.java:564) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ProtocolInjector.packetQueued(ProtocolInjector.java:338) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ProtocolInjector.onPacketSending(ProtocolInjector.java:298) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ChannelInjector.processSending(ChannelInjector.java:386) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ChannelInjector.access$500(ChannelInjector.java:77) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ChannelInjector$5.handleScheduled(ChannelInjector.java:352) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ChannelInjector$5.onMessageScheduled(ChannelInjector.java:320) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.ChannelProxy$2.schedulingRunnable(ChannelProxy.java:127) [ProtocolLib.jar:4.3.0]
        at com.comphenix.protocol.injector.netty.EventLoopProxy.execute(EventLoopProxy.java:95) [ProtocolLib.jar:4.3.0]
        at net.minecraft.server.v1_8_R3.NetworkManager.a(NetworkManager.java:192) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.NetworkManager.handle(NetworkManager.java:141) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.PlayerConnection.sendPacket(PlayerConnection.java:911) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.EntityPlayer.a(EntityPlayer.java:571) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.EntityPlayer.t_(EntityPlayer.java:263) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.World.entityJoinedWorld(World.java:1650) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.World.g(World.java:1617) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.World.tickEntities(World.java:1450) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.WorldServer.tickEntities(WorldServer.java:600) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:846) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:378) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:713) [patched.jar:git-PaperSpigot-"4c7641d"]
        at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:616) [patched.jar:git-PaperSpigot-"4c7641d"]
        at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
[17:33:15 ERROR]: Parameters:
  net.minecraft.server.v1_8_R3.PacketPlayOutUpdateSign@171eb2f3[
    a=net.minecraft.server.v1_8_R3.WorldServer@392e6b21
    b=BlockPosition{x=-44, y=112, z=76}
    c={TextComponent{text='', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}},TextComponent{text='', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}},TextComponent{text='', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}},TextComponent{text='', siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}}
  ]

>

>ver
[17:34:02 INFO]: This server is running CraftBukkit version git-PaperSpigot-"4c7641d" (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)
[17:34:02 INFO]: Checking version, please wait...
[17:34:03 INFO]: Error obtaining version information
>ver ProtocolLib
[17:34:06 INFO]: ProtocolLib version 4.3.0
[17:34:06 INFO]: Provides read/write access to the Minecraft protocol.
[17:34:06 INFO]: Authors: dmulloy2 and comphenix
>ver Lo
LogBlock      LockettePro
>ver LockettePro
[17:34:11 INFO]: LockettePro version 2.8.1
[17:34:11 INFO]: LockettePro is a chest protection plugin for Bukkit. It is 100% compatible with original Lockette, but delivers a lot of performance enhancements and feature options.

[17:34:11 INFO]: Author: connection_lost
>

Server crash

[08:07:23] [Paper Watchdog Thread/ERROR]: ------------------------------
[08:07:23] [Paper Watchdog Thread/ERROR]: Current Thread: Server thread
[08:07:23] [Paper Watchdog Thread/ERROR]:   PID: 19 | Suspended: false | Native: false | State: RUNNABLE
[08:07:23] [Paper Watchdog Thread/ERROR]:   Stack:
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$5.isSatisfiedBy(Pattern.java:5251)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$5.isSatisfiedBy(Pattern.java:5251)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$5.isSatisfiedBy(Pattern.java:5251)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$CharProperty.match(Pattern.java:3776)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$Curly.match(Pattern.java:4227)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$GroupHead.match(Pattern.java:4658)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$Branch.match(Pattern.java:4602)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$GroupHead.match(Pattern.java:4658)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$Branch.match(Pattern.java:4604)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Pattern$Start.match(Pattern.java:3461)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Matcher.search(Matcher.java:1248)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.regex.Matcher.find(Matcher.java:637)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.util.CraftChatMessage$StringMessage.<init>(CraftChatMessage.java:62)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.util.CraftChatMessage$StringMessage.<init>(CraftChatMessage.java:42)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.util.CraftChatMessage.fromString(CraftChatMessage.java:146)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.util.CraftChatMessage.fromString(CraftChatMessage.java:142)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.block.CraftSign.sanitizeLines(CraftSign.java:68)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.block.CraftSign.update(CraftSign.java:55)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.block.CraftBlockState.update(CraftBlockState.java:150)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.block.CraftBlockState.update(CraftBlockState.java:146)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.Utils.setSignLine(Utils.java:72)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.Utils.updateLineByPlayer(Utils.java:205)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.LocketteProAPI.isUserOnSign(LocketteProAPI.java:389)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.LocketteProAPI.isUserSingleBlock(LocketteProAPI.java:192)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.LocketteProAPI.isUser(LocketteProAPI.java:131)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.LocketteProAPI.isUserUpDownLockedDoor(LocketteProAPI.java:436)
[08:07:23] [Paper Watchdog Thread/ERROR]:       me.crafter.mc.lockettepro.BlockPlayerListener.onAttemptInteractLockedBlocks(BlockPlayerListener.java:239)
[08:07:23] [Paper Watchdog Thread/ERROR]:       com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor779.execute(Unknown Source)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.plugin.EventExecutor$1.execute(EventExecutor.java:44)
[08:07:23] [Paper Watchdog Thread/ERROR]:       co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:78)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:514)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:499)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:235)
[08:07:23] [Paper Watchdog Thread/ERROR]:       org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:202)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PlayerInteractManager.a(PlayerInteractManager.java:109)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PlayerConnection.a(PlayerConnection.java:871)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PacketPlayInBlockDig.a(SourceFile:40)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PacketPlayInBlockDig.a(SourceFile:10)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PlayerConnectionUtils.lambda$ensureMainThread$0(PlayerConnectionUtils.java:14)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.PlayerConnectionUtils$$Lambda$421/266004364.run(Unknown Source)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.util.concurrent.FutureTask.run(FutureTask.java:266)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.SystemUtils.a(SourceFile:46)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:842)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:423)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:766)
[08:07:23] [Paper Watchdog Thread/ERROR]:       net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:664)
[08:07:23] [Paper Watchdog Thread/ERROR]:       java.lang.Thread.run(Thread.java:745)
[08:07:23] [Paper Watchdog Thread/ERROR]: ------------------------------

Feature: Extend lockettepro.lock.xxx permission

For instance:
lockettepro.lock.chest

Feature Request: Support for SimpleClans

Hi There,

Would it be possible to add in support for SimpleClans, as per the original Lockette, whereby users can put [ClanTag] on a sign in order to allow access to all users in that clan.