LockettePro - UUID Support [Abandoned - restarting]

This build fixed invisible sign issue for LockettePro 2.8.0 + Minecraft 1.12. Fixes for MassiveCraft will come out later because this might be a little hard... For LockettePro 2.8.0 update and lock expiry, take a look at the update below. ↓↓↓

(Old version of LockettePro works for 1.12 as well, in case you have issues) Residence Users... This version of LockettePro requires latest version of Residence (4.5._13.2 286) or newer. If you are not able to use the latest one, stay with 2.6.4 Lockette for now. Bug Fix * Fix right clicking on locked iron doors does not open it. (1.12 only) * Fixed villagers opening locked doors. * Enderman can no longer pick up locked blocks (nobody found this issue lol) * Removed Metrics. New Feature - Lock Expiry (Experimental - Please Read Thoroughly) You can not set a lock expiry timer to all lock signs. By default it is turned off. It works pretty complicated at this moment, think twice before turning it on. I will put up a detailed guide on GitHub wiki page soon. What is it 1. Setting an expire time to any sign. This timer is a real-world time, not an in-game time. 2. Able to create no expire signs. (with permission lockettepro.noexpire) To Configure 0. Use ProtocolLib. It is not required, but your signs will become ugly. 1. Turn it on in config (lock-expire: true) 2. Set an expiry time in days (lock-expire-days: 60). The unit is days. Decimal numbers are acceptable. 3. For legacy support, which are those chests locked before lock expiry feature was introduced, set a default lock time (lock-default-create-time-unix: 1493596800). That is a unix time, converters could be found everywhere on the web. The number you see on the left was May 1st, 2017. The number means, that for all chest with unknown lock time, treat them with that time stamp. Setting the number to -1 will make those legacy locks never expire. 4. The lock line ([Private] line) can change depending on whether the chest is expired. (lock-expire-string: '&3[Expired]') Color code char is '&' as usual. 5. Players with permission 'lockettepro.noexpire' will create locks that won't expire. Important notes 1. Using expiry feature will make you no longer able to downgrade to original Lockette, or any LockettePro version lower than 2.8.0 due to sign format changes. 2. Due to the limitations, noexpire permission will allow players to "create locks that won't expire" instead of "their lock won't expire". Which means noexpire players' signs are not effective to those old signs. Admins, re-lock your chests unless 'lock-default-create-time-unix' is set to -1. 3. How expiry lock works: Upon creation of a lock (sign), the lock line ([Private]) will read "[Private]#created:1231231230". If you have ProtocolLib, the extra data will be hidden. That is the original lock line with a unix timestamp. 4. Changing lock expire days will affect the chests that have already been locked. This is due to locked chests stores lock creation date only. 5. You can use number with decimals at "lock-expire-days". For instance, if you set it to 2.5, this will mean 2 days and 12 hours.

* If you are using Residence: This version of LockettePro requires latest version of Residence (4.5._13.2 286). If you are not able to use the latest one, stay with 2.6.4 Lockette for now. * Added a debug command feature: /lockettepro debug. This is useful when letting users reporting issues. * Other minor code improvements.

Dear fractions server owners, You can now disable protection for specific incidents. For instance, using the following config will no longer protect blocks due to explosion: Code (Text): protection-exempt: - explosion You may also disable protection for tree growth, piston or redstone. See wiki for details. Enjoy! I will add additional checks for protection exemption upon request after thanksgiving. For instance, I can also specify explosion into creeper, ghast-fireball, tnt, bed etc.. (Too many people ask me for this ugh...)

This update will fix signs showing messy uuid on 1.11 servers. Sorry that 2.6.2 did not fix this issue completely.

Fixed an issue that caused signs are messy in 1.11 if uuid support is on.

This version of LockettePro adds potential support to Spigot 1.11. Q: WHAT? 1.11 is still not out yet! A: Yes, this version of LockettePro will correctly recognize Spigot 1.11 after it comes out. So the features will be tuned correctly according to that version. Q: WAIT! Did you just released 2.6.0? A: Well I just realized Minecraft 1.11 is right off the corner lol. Please see version 2.6.0 (which I typed the version number wrong too) to see previous changelog.

Oops, the version number should be 2.6.0, I cannot change it now * Fixed a critical issue that it is possible for a malicious client to exploit the plugin. There is currently no malicious client targeting this issue yet. Credit goes to an anonymous developer. * Fixed "trusted player" role of PlotSquared's plot cannot lock chests. * It is now impossible for players to create a sign for other player by default. This is due to any player could potentially create un-unlockable blocks by accident. Permission "lockettepro.lockothers" will be required to lock blocks for other people. If the player does not have the permission, the lock will always fall back to the player's name. Please PM me if you are concerned or need additional information regarding the issue above.

There is a compile time issue that caused timer not working. Damn Eclipse.

Vault with permission group: Players can now use [GroupName] as a user line to grant access to all users to of that group. Requires Vault. ASkyBlock and PlotSquared: Players are no longer able to lock chests protected in ASkyblock and PlotSquared protected area.

This is the definite fix for UUID appearing on signs. Make sure you have the latest ProtocolLib installed on your server. However due to a ProtocolLib bug (?), this fix does not and not possible to work on spigot 1.9.2.

* Fix UUID showing up in 1.9+ Still broken... * Fix [Everyone] sign will be replaced with player's name if [Everyone] is the only valid line and uuid support is on. Sorry for slow updates... I am in China.

* Fix a rare case lock-picking exploit, see GitHub.

Greetings everyone, I am now finally back from vacation but I am currently in China. Expect some delays because of some major internet censorship and outages (maybe). Here are changes & fixes in 2.1.6: · Able to use /lock <line number> to erase a line · Able to disable explosion protection (disable-explosion-protection in config) · Add German translation (thanks HeartCore!) · Fix user without lock permission can create blank [private] locks with no names under it. · Fix admin cannot edit [More Users] sign if the sign is on the other double door/chest block. Known Issues & TODO: · UUID signs in 1.9 looks ugly · Lock expire time · [Fee:xx] tag

Fix timer sign won't work if sign is at the bottem block (Thanks Hayden2006!) Known issues: There is a known issue that on 1.9 servers, LockettePro will not prevent sending the UUID strings in the sign. This is due to protocol change in 1.9, and needs some effort to fix. Upcoming features: * Lock expire time * [Fee]

Minor update. Change event priroty to High instead of Monitor. This may prevent having conflict with some other plugins such as silk spawner.

* Fix for admins not being able to do anything inside Factions with /f admin (Overriding Factions) active. (Thanks Maxetto!) * Fix not able to open iron doors in 1.9.

Actually a minor exploit, see GitHub commit for details.

· Added Italian language (thanks Maxetto!) · Better Factions Wilderness support (thanks Maxetto again!) · A little code cleanup (thanks liach!)

Oops... Sorry for the late update. I had something going on last week... * Support for Factions · Players are not able to lock chests in other factions. · You can grant locked block access for other faction member by adding a [Faction Name] line just like a user on it. · I'm not 100% confident with my knowledge to the Factions plugin. Please tell me if I have done anything wrong. * Fixed a minor issue where double door's additional sign is not editable if the additional sign is not the same block that lock sign is on.

Fix plugin load error if ProtocolLib is not installed regardless UUID support is turned off. (BTW in case you are asking, Factions support is coming out this week, lock expiry is coming out no later than next week.

1. Fix signs will look ugly if UUID support is turned off 2. Fix exception thrown when shutting down the server if UUID support is turned off and ProtocolLib does not present. (Nothing will go bad because of this) 3. Fix Towny [NationSign] and [TownSign] are not working

STOP - PLEASE READ BEFORE UPDATING I am glad to announce LockettePro update v2.0 with UUID support is here. If you are going to use UUID support feature, please read the following. (If you are not going to use this feature, you don't have to read them ) This is a minor update that fixes a little issue. Version 2.0 will make this plugin freak out if you enable UUID support but don't have ProtocolLib. Sorry about that. Requirement UUID support requires ProtocolLib, if you don't have it installed and attempt to use UUID support, the signs will be ugly. Shall I enable UUID support? This really depends. If you want players to be able to access their locks after they change their names, turn it on. If you hate players changing names because they will confuse others or potentially break other plugins, turn it off. I have tested UUID support feature several times and maybe this works perfectly. In case you are hesitated about the consistency of UUID support, you can hold for just a few days before turning it on. How to turn on UUID support? Is it on by default? UUID support is turned off by default. The config line to turn it on is "enable-uuid-support: true". If your config.yml is missing entries, you may add them manually referring to this detailed guide, or delete config.yml and let it regenerate. How does UUID stored on the sign? Detailed information is available on GitHub wiki page. TL;DR: Storage format is "username#uuid", for instance, "connection_lost#15e68dc9-5454-411a-8023-668b3877fe9b". Also, client will not see the uuid (those characters behind "#") so the signs will always be clean. How signs will be updated? If you choose to enable UUID support, all new lock signs will be contain UUID information, and old signs will be updated upon the valid user is interacting with the block or sign. What will happen if I turn off UUID support? Unfortunately, there is currently no way to just convert all UUID lock signs to normal signs. If you turn off UUID support in the future, all signs will be treated as normal name lock signs even UUID are present. LockettePro will correctly interpret those signs, but original Lockette cannot.

STOP - PLEASE READ BEFORE UPDATING I am glad to announce LockettePro update v2.0 with UUID support is here. If you are going to use UUID support feature, please read the following. (If you are not going to use this feature, you don't have to read them ) Requirement UUID support requires ProtocolLib, if you don't have it installed and attempt to use UUID support, the plugin may probably freak out. (Sorry about this, I will fix this later) Shall I enable UUID support? This really depends. If you want players to be able to access their locks after they change their names, turn it on. If you hate players changing names because they will confuse others or potentially break other plugins, turn it off. I have tested UUID support feature several times and maybe this works perfectly. In case you are hesitated about the consistency of UUID support, you can hold for just a few days before turning it on. How to turn on UUID support? Is it on by default? UUID support is turned off by default. The config line to turn it on is "enable-uuid-support: true". If your config.yml is missing entries, you may add them manually referring to this detailed guide, or delete config.yml and let it regenerate. How does UUID stored on the sign? Detailed information is available on GitHub wiki page. TL;DR: Storage format is "username#uuid", for instance, "connection_lost#15e68dc9-5454-411a-8023-668b3877fe9b". Also, client will not see the uuid (those characters behind "#") so the signs will always be clean. How signs will be updated? If you choose to enable UUID support, all new lock signs will be contain UUID information, and old signs will be updated upon the valid user is interacting with the block or sign. What will happen if I turn off UUID support? Unfortunately, there is currently no way to just convert all UUID lock signs to normal signs. If you turn off UUID support in the future, all signs will be treated as normal name lock signs even UUID are present. LockettePro will correctly interpret those signs, but original Lockette cannot.

1. Supports additional language by changing language-file-name in config.yml. Spanish and Chinese (Simplified) files are included, help me translating! 2. Code clean up. This will potentially help increase a little performance and also get plugin ready for UUID support. 3. Minor bug fix. * Next major update will be 2.0 and including UUID support. The drawback of UUID support is this not 100% backward-compatible. If you enable UUID support with LockettePro, you may disable UUID support and use LockettePro with no issue, but you cannot go back to Lockette.

Also now uses better API method provided by Towny. Shouldn't break more things from now on.

Fix permission node typo for Towny: Locking a chest in wilderness should be lockettepro.towny.wilds

If you don't have Towny installed the plugin will break in plugin version 1.9! 1.9.1 fixes this issue. Sorry for this Original plugin version 1.9 update changelog here

THIS VERSION IS BUGGED IF YOU DON'T HAVE TOWNY! PLEASE USE 1.9.1! Added Towny Support * Note: Although I have tested this feature several times, I am still not good at Towny, if I made some mistake regarding Towny support, please inform me immediately in the discussion! 1. Player can now share a chest across town or nation. Simply add [TownName] or [NationName] as a user. For example, right-click a sign, then enter /lock 3 [AwesomeTown] 2. Players cannot lock chests in the wilderness by default. Permission node to lock chest in the wilderness is lockettepro.towny.wilds Added Everyone Signs If you are updating LockettePro from previous versions, please add those missing entries in your config.yml, or delete config.yml and plugin will generate a new one with missing entries. Code (Text): everyone-signs: - '[Everyone]' - '[everyone]' A chest shared with everyone will look like this by default:

* Fix hopper minecart handling is incorrect * Fix locked chests cannot accept items if block-transfer-out * Added command /lock version * Console can now run /lock reload * Admins with permission lockettepro.edit.admin can now edit any lock signs * All doors can use timer signs even they are not locked I will now move on to UUID support

· Fixed a bug that causing players unable to quick-protect a chest inside any claimed area.

* Fixed double doors are not able to close automatically according to timer when you open the second door (with no signs attached above or below) instead of the main door. Fixed console complaining " is not an item!" while you use "*" in lockable-blocks.

1. Support for Residence & WorldGuard 2. Player now default have the permission to edit a lock sign "lockettepro.edit"