LockSecurity
3.0.0Locking containers with keys so only you and your friends can have access to them!
3.0.0latestThe Final Free UpdateJul 10, 2020 LockSecurity has gone premium! Well... sort of... As of July 9th, 2020, LockSecurity will receive its final free update. Any future releases will be made under premium status which is available for purchase here. I would greatly appreciate the support as this is my first premium resource, I have worked hard to ensure this version has next to no bugs. This final release matches the initial release on the premium version of LockSecurity for those that have not updated beyond 1.12.2. Premium version: https://www.spigotmc.org/resources/locksecurity.81282/ Because the changelog is as large as it is, I ask instead that you read the newly updated main page! Many new QOL features, commands, permissions and functionality. Unfortunately this version of LockSecurity does not support any previous versions and will not convert any data from said versions. I apologize, though converting 3 year old data was not a task I planned on taking on. If you have any questions, do not hesitate to contact me through my support Discord, I will reply when available. Thank you for your support!2.0.0Complete Rewrite + 1.12 SupportSep 25, 2017 Yes, I'm aware, this update is long overdue. After 1 year and 4 months since LockSecurity 1.8.2 and over 3 months since 1.12 release, LockSecurity 2.0.0 has been completed! Now... take this release with a grain of salt. There is no guarantee that this will work 100% on any server version other than 1.12.0 -> 1.12.2, and even then, expect issues. I am not certain that everything will work, but certain enough to at least release a beta version of this plugin. Please be aware that by using this file, it is at your own risk and you are willing to report issues to me as soon as possible. LockSecurity has been written from the ground up for 2.0.0 (I literally deleted the whole project and started from scratch about a year ago and only just now finished it), therefore many improvements have been made. See below for a long yet meaningful changelog · Official support for Minecraft 1.12.x · Completely rewrote LockSecurity from scratch. Code improvements, condensed/cleaner source, and just overall efficiency boosts · Data storage changed from MySQL (SQLite) to per-player JSON files · Previous data will be automatically converted · be cautious... backup your data just in case something goes awry. Notify me instantly · Added support for locale files in order to change messages in the plugin · By default, "en_CA" and "fr_CA" are generated · You are welcome to submit your own locale files and submit them to me, or just keep them to yourself :c · Removed and updated a few commands: · /locklistother <player> has been simplified as an optional parameter to /locklist [player] · /forgekey [id] now accepts multiple ID numbers (i.e. /forgekey 3,4,5 will give you a key with ID's 3, 4 and 5) · Local data is handled in a more efficient way. If a locked block is unloaded, it is no longer registered to memory until it is loaded again. This increases efficiency in lookup times for large amounts of locked blocks · Players are now more properly secured in memory. Should not lose information after logout · Added and updated a bunch of new API classes for developers: · LockedBlock: A class that represents a block locked in the world · KeyFactory: A utility class used to create smithed and unsmithed keys in a builder-style pattern · PlayerDuplicateKeyEvent, PlayerInteractLockedBlockEvent, PlayerLockBlockEvent, PlayerUnlockBlockEvent, PlayerMergeKeyEvent · LockedBlockManager: Contains a bunch of methods to interact with registered/loaded locked LockedBlocks · PlayerRegistry: Holds information regarding custom player data (LSPlayer class, which is also new) · LSPlayer: Represents a custom Player wrapper with a bunch of information regarding the player for LockSecurity · All classes have been thoroughly documented with Javadocs and may be found on my website · Removed and added a few configuration options · + Locale: Select the locale to use for LockSecurity · * DatabaseSaveInterval -> DataSaveIntervalTicks: Just a rename. Still an autosave, but now calculated in ticks rather than minutes · - Aesthetics.DisplayNameChangeNotice: Completely removed this "feature" due to the rewrite. Data is not held by names, but rather UUIDs · - Vault category: The entire category was removed because economy is no longer supported. This may change in the future · LockSecurity's repository is now being hosted on GitHub, which means it is now OPEN SOURCED! Go on! Go check it out! Contribute if you can The wiki and code on BitBucket are outdated and will soon be deleted (it's private anyway). The license is now GPLv3 I'm sure there is a lot more to this changelog, but to be quite honest, due to such a large period of time updating this project, I don't remember a lot of what was done. If you have any issues with the project, please don't hesitate to send me a message, and I'll update whenever I get the change. I appreciate those still willing to use this plugin, and I apologize sincerely for the long wait for the update to 1.12.0. Enjoy!1.8.2General FixesMay 25, 2016 * Added support for versoin 1.9.4 of Bukkit/Spigot * Placing a chest next to a locked chest you own (creating a double chest) now locks the block you placed * |-> If you are not the owner of the block, the block will not be placed (Fixes an exploit to enter peoples chests) * Fixed a couple of buggy messages * |-> /transferlock error message, "%targetPlayer%" was not being replaced * |-> Inverted messages for /ignorelocks * Fixed a NullPointerException when putting an item in a crafting inventory with a null result * Added a new recipe. Putting a locked key in a crafting window will now convert it to a reusable unsmithed key once again (Locked keys with no chest to unlock are no longer useless) * Added support for locking iron doors, (IRON_DOOR_BLOCK), and iron trapdoors (IRON_TRAPDOOR), though they are not defaults in the configuration file * Added private modifiers to fields that did not have them previously * Few code optimizations * Added an ItemBuilder utility class to easily construct items within the code * API: Added a "getKeyManager()" method to get the key manager for LockSecurity (I'm probably missing some other changes in this update. I honestly didn't log them while I was making them. Please, let me know if there are any issues, as I've clearly missed quite a few of them whilst I was testing this version that I had no clue about. It's important that you tell me about these issues if they are occurring on your server, and I'd be more than happy to fix them. Thank you to FlOppy95 for informing me about the bugs that were present in the past couple of versions)1.8.1.2Vault-Related Bug FixesMay 24, 2016 * Fixed NullPointerException if Vault is installed but an economy plugin is not * Condensed and organized the lock interaction code a bit more to make it more readable * Added Anvils to the list of default lockable blocks (This can be removed in the config)1.8.1.1General FixesApr 24, 2016 * Attempt to fix occasional asynchronous task errors * Fixed potential lag when loading data on startup1.8.1General FixesMar 21, 2016 * Fixed LockInspect messages being swapped when toggling modes (Confusing * Fixed being able to open blocks if in LockInspect mode * Fixed LockInspect not displaying locked block information * Fixed being able to pull items from locked inventories out of hoppers1.8.0Database management fixes + API overhaul (Biggest update ever)Mar 21, 2016 * Completely rewritten the infrastructure of LockSecurity. Much more complex, yet much more simple at the same time * Removed DarkBlade's ParticleLib and instead used 1.9 methods * Removed old LockedBlockAccessor class and replaced it with LocalizedDataHandler class * Rewrote the whole LockSecurity API (Will modify the Wiki page over the course of the next couple of days to reflect the changes) * Completely fixed all lag/latency issues due to direct database calls. All information is now stored locally, and saved every 5 minutes * Added new configuration option to determine the interval of time (in minutes) between when the local data will save to the database * Added "/locksecurity forcesave" subcommand to force a local data save * Changed the way "LockSecurityModes" are handled. You can now be in more than one mode at once (Modes being unlock mode, transfer mode, etc.) * Fixed not being able to lock blocks if there was more than one unsmithed key in an item stack (There can now be multiple keys in a stack, but only one will be used) * Removed unnecessary ArrayLists that were just taking up memory * Removed many many many methods that were inefficient and pointless * Removed annoying messages when retrieving an instance of LockSecurity (API) * Cleaned up code for most classes * Added javadoc comments to methods that may not have previously had javadocs * Deprecated the LockState API (Replaced by methods in LocalizedDataHandler. See the java doc for references) * Added an object to represent locked blocks where all information is stored (Key id, lock id, owner, and original block) * Reorganized a lot of classes in the API * Added "ADMIN_NOTIFY" in LSMode enum to represent the admin notification mode * Modified some custom events to reflect the new LockedBlock object changes * Made a couple of commands more efficient than prior * Removed listeners when players leave the game (Unnecessary with the LSMode API overhaul) * Made keys more reliable when it comes to using either hand (You're able to lock blocks and access them, even if the key is in your offhand) * Moved many methods into respective classes (Some methods were in classes that made no sense) * |-> Database related methods were moved into an SQLite class * |-> Key related methods were moved into the Keys class * Fixed a few issues present in 1.7.2 With this version, comes an update to LSChestCollector, as the API has been completely changed. Any other addons for LockSecurity will have to update their code as well, otherwise they will not work for version 1.8.0 of LockSecurity. I've worked a good week or so on this update. Spent a lot of my time working on this project over any other project, so I'm quite proud of it. I hope you appreciate the work I've put into this, because it was definitely needed. There were tons of database latency issues persistent in previous versions, ever since database support was implemented. I highly suggest updating to this version as soon as possible. It is stable, and each feature has been tested extensively before release. No errors have appeared in my testing, but if I have missed anything, please do tell me as soon as possible. That's information I need. Enjoy this huge update, and enjoy Minecraft 1.9!1.7.21.9 SupportMar 12, 2016 Not a very large changelog. I've been quite busy with AlchemicalArrows (As some of you may know.) * Added 1.9 support Please be aware that this plugin still needs a bit more work to cooperate with 1.9. Locking blocks requires keys to be in the main hand, for example1.7.1Vault + LockNotifyDec 5, 2015 * Added a new notification for administrators when players lock a block * Added a new /locknotify command for administrators to toggle whether these messages display or not (default, enabled on login) * |-> These messages will display: The player who locked it, type of block, x, y, z, world, lock id, and key id (configurable in messages.yml) * |-> Permission required to enter / leave locknotify mode: locks.locknotify * Renamed a specific class to represent what it does more accurately * Made preparations for a future conversion to LSPlayer's (developer heads-up: LSMode will be removed in 1.8.0) * Added Vault support to allow for a cost to lock block, and a return value for unlocking a block * |-> Added 4 new configuration options and a new configuration section to determine the cost and reward of locks1.7.0SQLite DatabaseNov 24, 2015 * ADDED SQLITE DATABASE SUPPORT!!! * REMOVED locked.yml functionality * |-> There is an automatic conversion method to convert all data in your locked.yml into the database. Please watch your server console to make sure all data is successfully transfered into the database. If something goes wrong, a message will display, and tell you what to do from there. PLEASE follow the warning instructions if they are displayed * Removed the LockedStorageHandler class * Added RecipeYields configuration option to determine how many Unsmithed keys the recipe creates * Removed lockedLockIDs and lockedKeyIDs HashMaps (unused in this update) * Changed absolute variables for recipes to direct recipes in the onEnable() * Removed locked.yml HashMap data loading code block * Added a conversion block of code to automatically transfer all information from the locked.yml into the new database * Removed some logging information from onDisable() method * Removed formatLocation(Location) method in main class * Removed setNextKeyID(int) and setNextLockID() methods * Added database-related methods in main class (openConnection(), closeConnection(), createStatement(), closeStatement(), executeStatement(), queryDatabase(), closeResultSet()) * Removed @SuppressWarnings for deprecation (no more deprecated methods) for most classes * Removed references to LockStorageHandler class in most classes * Removed unnecessary declaration of variables, and used direct Location variable for parameters instead * Removed reload for locked.yml (fixes a NullPointerException) * Moved the removal of key and play sound into the actual moment a block is interacted with (Fixes potential NullPointerException in API) * Moved removeCurrentItem() method from LockedBlockAccessor into InteractWithBlock class * Fixed using multiple ID's and queries for a single ID (more efficient locking of blocks) * LockedBlockAccessor API changes: * |-> Added getLocationFromLockID(int) method to get a specific location from the specified id * |-> Added insertDatabaseInfo(int, String, String, String, Location) method to insert information into the database * |-> Added insertDatabaseInfo(int, int, String, String, String, Location) method to insert information into the database with a specific LockID * |-> Added isInDatabase(int) method to determine whether the id is in the database or not * |-> Removed addLockedYMLInformation() method (no longer to be used) * |-> Modified MANY LockedBlockAccessor methods to reference the database rather than the locked.yml Once updated, you may either do one of the following things with the locked.yml: 1. Delete it 2. Take a backup of it just in case1.6.3Huge fixes: Affects Versions 1.5.0 - 1.6.2Nov 22, 2015 * Fixed combining and duplicating keys not working properly * Fixed the locks.craft permission node not functioning * Fixed the 1 lock limitation if your world was not specified in the list. If not specified, it will default to infinite * Fixed being able to lock 1 over the specified maximum amount (i.e You put 4 in the config, they could lock 5) * Fixed ClassNotFoundException when disabling or reloading server * Added a message when attempting to lock a block when unable to due to maximum locks * Changed the default generation of "MaximumLocks" to have only 1 display rather than 31.6.2Fixes, API Changes, and per/world configNov 20, 2015 * Added a new getLockCount(OfflinePlayer) method to check how many locks a player has * Added a new configuration option, "MaximumLocks", to specify how many locks a player can have per world * |-> To use, list your world (like the example), then put the maximum amount of locks. (-1 is no limit/infinite) * |-> Players with permission "locks.ignorelocks" or oped players may override the block limit (Will change in the future) * API changes: * |-> Added a getPlugin method in LockSecurity class with a parameter of your plugin instance * |-> Deprecated the getPlugin() method without a parameter (Please use "this" in your getPlugin() method parameters) * Fixed NullPointerException when placing a block (Again). This is officially fixed now. Tested 100%1.6.1General FixesNov 19, 2015 * Fixed NullPoinerException when placing a block * Fixed a typo on a permission node description * Made all recipes public absolute variables in the LockSecurity main class * Added new permission node to allow the crafting of an unsmithed key. "locks.craft", default: All Players1.6.0TransferLock and General AdditionsNov 14, 2015 * Added a tabcompleter for the /locksecurity command arguments (reload, and version) * Added an alias for locklist: /locks * Added new transferLock(Block, Player) method in the LockedBlockAccessor class * Added new /transferlock command to transfer the clicked block to a specified player. /transferlock <player_to_transfer_to> * Changed the way player modes (Unlock mode, Ignore Locks Mode, Transfer Lock Mode, etc.) are handled * |-> They are now handled through an Enumeration in the me.choco.locks.api.utils class: LSMode * |-> Added 2 new static methods under LSMode: getMode(Player), setMode(Player, LSMode). * |-> The LSMode class will be replaced in the future, though deprecation will not be necessary. Just be weary, developers * Fixed being able to lock a new block in Unlock mode * Fixed a tiny NullPointerException with the "/locksecurity version" command1.5.2General FixesNov 3, 2015 Let's just all admit... I'm making tons of mistakes as of recently. I apologize * Fixed Unsmithed Keys not being craftable * Fixed NullPointerException with /lockinspect <id> when specifying an invalid ID * Fixed NullPointerException with /unlock <id> when specifying an invalid ID1.5.1API Fixes / Changes / AdditionsNov 2, 2015 * Added new PlayerInteractLockedBlockEvent that fires before a player interacts with a locked block * Added "InteractResult" enumeration in the API to determine the result of the PlayerInteractLockedBlockEvent. * |-> Possible enumerations: SUCCESS, NO\_KEY, and NOT\_RIGHT\_KEY * Added static "getPlugin()" method in the main LockSecurity class to get an instance of the plugin (API reasons). Note to developers, when creating a new LockSecurity instance, use this: Code (Text): LockSecurity ls = LockSecurity.getPlugin();1.5.0LockSecurity APINov 1, 2015 * Started development on an external event API, fully documented the API, as well as uploaded the source code to LockSecurity and the future add-on in development to a private online repository. Click here * Created 4 new Player oriented events: * |-> PlayerLockBlockEvent - Fired before a player successfully locks a block. Is cancellable * |-> PlayerUnlockBlockEvent - Fired before a player successfully unlocks a block. Is cancellable * |-> PlayerCombineKeyEvent - Fired when a player combines two keys in a crafting table. Is not cancellable * |-> PlayerDuplicateKeyEvent - Fired when a player duplicates a key in a crafting table. Is not cancellable * (These events and all their methods have all been tested, and work 100% ) * Added a @See tag to link developers for "LockSecurity.isLockable()" on the "getLockedState()" method * Added an "apiversion" variable in the plugin.yml to keep track of the API version1.4.2Custom Lockable BlocksOct 29, 2015 NOTE: I'd like to take a moment here and note something about this plugin. In the next version, I plan on making an external API for version 1.5.0. This includes events, and creating full documentation on the internal API I have created and been using. With this API, I am already working on an addon of my own for LockSecurity. I hope this will encourage people to create their own addons as well, but I want to get the ball rolling to show you guys what this plugin's API has the potential of doing Alright, that's all I wanted to say. Enjoy version 1.4.2 ^-^ * Added an optional parameter to the /lockinspect command to wirelessly inspect a lock when a LockID is specified * Fixed duplicate KeyID's when combining keys. There will now only be one of each KeyID * Added a new list in the configuration to determine which blocks are lockable. It is limited however... * |-> The only supported lockable blocks are listed in the config already. You can't add blocks other than those. You can remove blocks though1.4.1General Griefing-Protection FixesOct 26, 2015 * Fixed the 4 following grief-related bugs that can destroy blocks: * |-> Fixed zombies being able to break locked wooden doors * |-> Fixed wooden doors, chests, fence gates, and other wooden lockable blocks being able to burn * |-> Fixed being able to remove a locked wooden door by breaking the block under it * |-> Fixed being able to open a gate or door with redstone * Added just an extra few lines of debug info to the onDisable method * Fixed not being able to lock wooden doors (I used the wrong Material enum) * Changed the message when breaking a locked block1.4.0Key Duplication and KeyID Combination! :DOct 24, 2015 * Added Multi-KeyID support!!! Woohoo! * |-> Put 2 locked keys in a crafting table, and the keys will combine into one key with multiple id's * Added duplication key support!!! (I'm on a roll, man) * |-> Put 1 locked key, and one unsmithed key in a crafting table, and the key's will duplicate (so you can share with friends) * Allowed lockinspect to work with a left click as well as a right click * Created a private "displayLockInfo()" method to make lockinspect run a bit more efficiently * Added support for trapdoors, dispensers, droppers, furnaces, hoppers, and fence gates (All of these are now lockable) * Removed support for all iron-related blocks (iron trapdoors, iron doors, etc.). Those are lockable with redstone * Changed recipe formations in the onEnable to be more efficient. Rather than creating 9 new objects, all recipes are now based on 1 object * Added 2 aliases to /lockinspect. (/inspectlock, and /inspectlocks)1.3.3General Fixes and ChangesOct 22, 2015 * Created a createLockedKey() method to create a new ItemStack of a locked key (rather than converting an unsmithed key). This simplifies the /forgekey command * Created two new methods in the LockStorageHandler class. getLocationFromLockID() and getLocationFromKeyID() to gather locations from ID's * Removed the Commands.GiveKey.InvalidInteger & Commands.ForgeKey.InvalidInteger messages.yml path in replacement for Commands.General.InvalidInteger * Added an optional int parameter to the /unlock command. If you specify a LockID ( NOT a KeyID), it will unlock it * Changed the structure of the locks.unlock permission nodes. It will now go as followed: |-> locks.unlock. - The parent node, which includes all of the below * |-> locks.unlock.self - Unlock blocks that you own using the /unlock command (without parameters) * |-> locks.unlock.id - Allow use of the /unlock parameter to unlock a specified ID (Note, can unlock locks that are not yours) * |-> locks.unlock.admin - Unlock blocks that you own or do not own using the /unlock command * Added an unlocking sound when unlocking a chest * Temporarily and minimally fixed interactions with Anti-Griefing plugins (Should prevent users from locking WorldGuarded / Admin claimed chests). Will add a WorldGuard flag later * Fixed an ArrayIndexOutOfBoundsException when using /givekey on an offline player without specifying an amount of keys * Fixed the check for the new KeyID variable in the onEnable method ( Please update if you were having strange KeyID issues before)1.3.2messages.yml and General FixesOct 21, 2015 * Fixed the /forgekey messages being in DARK_AQUA rather than AQUA (Lol, sometimes I get finger happy and type a bit extra) * Fixed /locklist & /locklistother not displaying it's first message * Added support for the Messages.yml file and all messages in the plugin (You don't even know how long this took ._.) * |-> Essentials colour codes are supported for all messages, but will default to gray * Changed a few messages that needed to be changed a long time ago * |-> Changed the message when unregistering a lock to display the LockID rather than the KeyID * |-> Changed the message when locking a block to display the LockID, and the KeyID in brackets * |-> Added consistancy to many of the messages (No permission messages, command messages, etc.) * General code improvements, fixes, and optimizations (not even worth noting the TINY code changes) If the messages.yml doesn't contain any configuration options, just delete the file and let the plugin reload it. It should generate options regardless though, so only do it if necessary1.3.1General fixesOct 18, 2015 * Fixed /ignorelocks not being toggleable anymore * Fixed the "This chest is locked by <player>" message always displaying chest rather than the block type * Fixed a NumberFormatException in the getAllLocks() method (In result, messing up /locklist and /locklistother) * Fixed the console message not displaying when a player changes their name, even if the config is set to true * Changed the console message to display how many indexes were changed as well * Removed the "createLockedKey()" method (Due to Deprecation after a few versions)1.3.0Dual Component Support!!! And /unlock commandOct 18, 2015 * Added a new /unlock command! This can be used for both admins and players: * |-> Players: (Permission: locks.unlock) Allow the ability to unlock blocks YOU OWN by right clicking on it (default: true) * |-> Admins: (Permission: locks.adminunlock) Allow the ability to unlock any block by right click on it (default: op) * Deprecated the "getBlockOwner()" method in replacement for the "getBlockOwnerUUID()" method (UUID support) * Changed the way Block ID's are handled. It will instead return the Key ID (that is how block ID's should have been handled) * |-> This will support dual-component blocks. When checking ID's in the locked.yml, use the KeyID, NOT THE STRING IDENTIFIER * Added a new variable in the locked.yml, known as "NextKeyID". Not to be confused with "NextLockID". These are two variables that should NEVER be changed. This is to differenciate the unbinded String ID and the binded Key ID * Created a private "addLockedYMLInformation()" method to store information in the locked.yml easier * Fixed the "getLockID()" method to return proper mapped values * Created a new LockStorageHandler method to handle the memory stored in RAM for locks * ADDED DUAL-COMPONENT BLOCK SUPPORT!!!! (doors, double chests, double trapped chests, etc.) * Fixed not being able to break locked block whilst in locked blocks mode (assuming the config enables it) * Separated two HashMaps. One for KeyID information, and one for LockID information * Modified the /lockinspect command to display both LockID and KeyID values of the block * Changed the ArrayLists for ignorelocks and lockinspect to store player names rather than Player objects1.2.2Internal Modifications & Name Change Refactor FeatureOct 14, 2015 * Added a new "getAllLocks(player)" method to return a collection of ID's that the player owns * Modified the /locklist command to run more efficiently and using the new "getAllLocks()" method * Added a new login check. If the player has changed their name, it will refactor their name in the locked.yml to their new name. Will log in the console if a change has been made * |-> NOTE: This is experimental and I have no way of guaranteeing this will work. I do not plan on changing my name, so please let me know if someone changes their name and there are bugs with the refactoring * Added a new boolean configuration option to toggle whether the name change will log in the console or not "DisplayNameChangeNotice", default: true1.2.1New Config Option & CommandOct 13, 2015 * Moved the "playerHasUnsmithedKey()" method into the Keys class, and made it a public method * Fixed being able to place down Unsmithed Key's and Key's * Added a new configuration option under the Griefing section, "OwnerRequiresKey", default: true. Determines whether or not the owner of the locked block requires the key or not * Added a new /lockinspect command to gather information about a locked block (Permission: locks.lockinspect, default: op) * |-> This is a toggleable mode. When enabled, right click the block you're curious about * |-> Will gather the following information: LockID, Owner name (and UUID), Location1.2.0Command and Config ChangesOct 11, 2015 * Fixed the /forgekey command not working (like... at all... oops .-.) * Fixed the /forgekey command without any parameters displaying in DarkGray text rather than Gray * Fixed the /forgekey command generating a NullPointerException and not giving a forged key * Added a small smoke particle above a locked chest when attempting to open it without a key * Added a new configuration section "Aesthetics". This will contain configuration options revolved around aesthetic additions * Added a new configuration option under the Aesthetics category. "DisplayLockedSmokeParticle". Will toggle the smoke particle above the chest, default: true * Removed a check if a block was neither Locked or Unlocked (which is impossible ._.) * Added a new main administrative /locksecurity command with the following sub-commands. (Aliases: /ls) * |-> /locksecurity reload - Reloads ALL the configurations (config.yml, locked.yml, and messages.yml) - Permission: locks.reload - Default: op * |-> /locksecurity version - Gather version information / general information about the plugin NOTE: In this version, I added the generation of a messages.yml file in the LockSecurity datafolder. This is currently unused, but will be used in the next version. I have no time to complete it at the moment because it is currently Thanksgiving weekend (I am Canadian, we have it in October here). Enjoy the changes and the fixes I apologize that the /forgekey command bug wasn't discovered sooner. I never tested the last version1.1.2General Update (1.1.2)Oct 7, 2015 * Added the ability for admins ignoring locks to destroy locked blocks as well * Added a new configuration option under the Griefing category: IgnorelocksCanBreakLocks. Default: true * |-> Toggles the ability to destroy locked blocks when ignoring locks * Added a /forgekey <id> command to give a locked key with the specified ID (Permission: locks.forgekey. Default: op)1.1.1Performance Optimizations and FixesOct 5, 2015 * Changed the formatListing() method to return a direct variable rather than an indirect variable * Fixed the format of /locklist not displaying whole numbers for coordinates * Added a declaration of text at the beginning of /locklist determining the player you're looking up * Fixed /locklistother without any parameters returning false * Added a check when enabling the plugin. If the block id at the stored location doesn't match "BlockType", it will automatically remove the lock from the locked.yml. This saves unnecessary data usage on startup * |-> If a block is removed, it will display information in the console. The Lock ID, the location, and the owner1.1.0Command update / RecipesOct 3, 2015 * Added the /locklist command to list every lock the sender owns. Permission: locks.locklist. Default: true * Added the /locklistother command to list every lock the specified player owns. Permission: locks.locklistother. Default: op * Added aliases the following aliases to the following commands: |-> /givekey*. Aliases: /givekeys |-> /ignorelocks*. Aliases: /ignorelock, /il |-> /locklist*. Aliases: /locklists |-> /locklistother*. Aliases: locklistsother, /otherlocklists, /otherlocklist * Added an extra parameter to the /givekey command. It now accepts amounts. /givekey \[player\] \[count\] * Added an extra parameter to the createUnsmithedKey() method to allow an amount of Unsmithed Keys (future use, and compensation for the /givekey modifications) * Changed the key recipe to be semi-shapless. As long as the iron bars and the wooden plank are on opposite ends of the crafting table, and the iron ingot is in the middle, the recipe will work (8 different ways to do it now)1.0.2Fixes, Changes, and OptimizationsSep 30, 2015 * Added JavaDoc comments to the LockedBlockAccessor.class file (A bit better documentation of the methods) * Deprecated the createLockedKey(player) method (will be removed soon), and replaced it with a convertToLockedKey(key, id) method * |-> Added a suplimentary convertToLockedKey(key, id's) method to set multiple key ID's in preparation for future plans * Changed the getKeyID(player) method to getKeyIDs(key), and let it return List<Integer> rather than a String (preparation for future plans) * Fixed the unlock registry saying "Chest" every time instead of the block material id * Fixed the annoying "invisible key after lock" glitch. (Sorry about that. Lazy coding) * Removed unnecessary declarations of the configuration file (might load up ever so slightly faster now?) * Added more console messages on startup to inform the user what's going on whilst starting up * Allowed the RAM storage of locks to continue if a NumberFormatException occurs (This basically means, if something can't be loaded in to RAM, the rest of the locks and the entire plugin will still load. Only the lock that could not be loaded will not be locked anymore) * Fixed the error message above displaying multiple times when there were more than 1 errors * Added an extra error message displaying how many locks could not be loaded1.0.1Griefing FixesSep 27, 2015 * Added sounds to the following events * |-> Locking a chest with an Unsmithed Key * |-> Attempting to open a locked chest * |-> Attempting to open a locked chest with the wrong key (failing to picking a lock) * Fixed being able to explode a locked block with either TnT, Creepers, Ghasts, and EnderDragons (1.9 feature) * Added a new Configuration Section. "Griefing". Will add griefing related configs * Added a config option to enable or disable the ability to destroy locked items with explosions (Griefing.PreventLockedExplosions) * Changed the message when breaking a locked chest to display who owns the chest * Fixed not being able to shift click on a locked chest1.0.0Sep 27, 2015
Similar projects
Plugin →Let Me Despawn
Improves performance by tweaking mob despawn rules. Say bye to pesky unintentional persistent mobs.
26.2MSueta
JourneyMap
Real-time map used for mapping in-game or your browser as you explore.
14.7MSueta
Emotecraft
Create your own emotes in Minecraft.
7.9MSueta
Simple Tpa
A simple tpa plugin which sends requests
5.4MSueta
Common Network
Forge and Fabric Unified Networking Solution
4.7MSueta
Set Home
A lightweight plugin for players to set their homes.
3.8MSueta