Lock Security 1.0.1

Download

Details

  • Filename
    LockSecurity.jar
  • Uploaded by
    View Choco's Profile
    Choco
  • Uploaded
    Sep 26, 2015
  • Size
    32.43 KB
  • Downloads
    196
  • MD5
    eb73ecbd5a52546281389f254ef7a250

Supported Bukkit Versions

  • 1.8.3

Changelog

Version 1.0.1

  • 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 chest

Version 1.0.0

  • Crafting recipe for an *Unsmithed Key* (found on main page)
  • /givekey command for administrators to give an *Unsmithed Key* (permission: locks.givekey)
  • Right clicking on a chest or trapped chest with an *Unsmithed Key* (Tripwire Hook) will lock the object clicked
  • |-> Required permission: locks.lock. This is default to true, and all players have this permission
  • The *Unsmithed Key* will transform into a *Key*, with a unique ID on the lore
  • When right clicking on the chest with that binded key, the chest will open
  • Right clicking on the chest without that binded key, the chest will remain unopened
  • Breaking a chest that is locked will unlock it
  • |-> Only the Owner of the chest (player that locked it), may break the chest. Otherwise, the chest is not breakable
  • Administrators are able to use the /ignorelocks command to override all locks (permission: locks.ignorelocks)

There are TONS of future plans for this project, and they will be added as soon as time is available. Please leave suggestions for ideas to add in to this plugin, as I am widely open to them. Submit a ticket if you have found a bug (also leave your suggestions in the ticket section for organization purposes). Don't leave a bug alone and hope that it'll be fixed, because 9 times out of 10, most people don't come and report bugs. No bug reports, no bug fixes :(.