Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Apr 27th, 2011  |  syntax: None  |  size: 16.54 KB  |  views: 2,412  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. Lockette v1.3.7 - The sign-based container and door lock for Bukkit! - by Acru Jovian
  2.  
  3.  
  4. Overview:
  5.  
  6. The purpose of this plugin is to restrict access to the contents of chests, dispensers, furnaces, and doors without the use of a database to track containers.
  7.  
  8. To use, simply place a signpost on the floor directly beside a chest or other container to be locked. Enter [Private] as the first line. Your own name will automatically be entered on line 2 as the chest owner. Optionally type in the full names of two other users allowed to access the chest's inventory on lines 3 and 4.
  9.  
  10. When done correctly, the sign will automatically fix itself to the side the target chest, protecting it from unauthorized access! Only the chest's owner can then break the sign or chest. (Warning: Anyone with permission to use WorldEdit commands or similar can circumvent the protection by removing the sign.)
  11.  
  12. 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.
  13.  
  14. The owner of a container can add more users by placing additional signs beside the container with the heading [More Users], where lines 2-4 specify the names of the additional users. You can edit the users on previously placed signs by right clicking the sign, and using the command '/lockette <line number> <text>' to change it.
  15.  
  16.  
  17. Working with Doors:
  18.  
  19. To protect a door, you can use the same method as protecting a container, the sign will attach to the door automatically. In addition, you can attach a [Private] wall sign to any side of the blocks just above or just below a door. For double doors only one side needs a sign. Door support is enabled by default in the config file.
  20.  
  21. Once a door is protected it will only open for someone listed as a user, and will not respond to redstone power or switches unless [Everyone] is listed as a user. Iron doors which usually won't open from clicking will work just as wooden doors. In addition, double doors will open together automatically!
  22.  
  23. You can also use [More Users] signs as with containers, with the caveat that the sign cannot be placed on the block above the door if the [Private] sign is not above the door as well! (This is done to prevent a security uncertainty issue.)
  24.  
  25. Protected doors will be closed automatically if a timer is set. A timer can be set globally with a configuration option, or individually for each door by using the tag [Timer: #] on line 3 or 4 of the [Private] sign, where # is the number of seconds that the door should remain open. If the timer is set to 0, this means the door will never automatically close. If no timer is specified, protected doors will use a global timer set in the configuration file. If the server is shut down cleanly any open doors will be closed, but in the event of a server crash while a door is open, it may remain so.  Note that the initial state of a door is assumed to be closed.
  26.  
  27. Care must me taken to place protected doors on a stable block. Building a door on sand, gravel, leaves, TNT and et cetera are allowed by the plugin, but cannot be secured fully. :3 Additionally, it should be noted that most status messages still refer to locked blocks as containers, so for the purpose of simplicity, doors should be considered as a type of container.
  28.  
  29.  
  30. Features:
  31.  
  32.     * No passwords or databases needed!
  33.     * Permission checks run in constant time, no matter how many protected containers.
  34.           o One owner and up to 11 additional users supported. (17 for double chests!)
  35.           o Allows access to [Everyone] while still protecting the container from vandalism.
  36.           o Allows group names in conjunction with a Permissions plugin.
  37.                 + Native support for GroupManager.
  38.     * Special powers for ops or admins, configurable with permissions.
  39.           o Reports when an admin does something naughty.
  40.     * Protects single and double chests, dispensers, and furnaces.
  41.           o Explosion and block-break protection for the protected container and sign.
  42.                 + Option to protect all containers from explosions.
  43.     * Full support for doors, both wooden and iron!
  44.           o Double doors are handled automatically, with no redstone.
  45.           o Doors can be set to close automatically, via a timer setting.
  46.           o Redstone hacking is disabled for protected doors.
  47.     * Prevents creation of chests larger than 2 blocks.
  48.     * Informative or helpful messages when interacting with containers.
  49.           o The first time a chest is placed, a help message will be shown.
  50.           o Types of messages shown are configurable in settings.
  51.           o Additional language support.
  52.  
  53.  
  54. Advanced Setup:
  55.  
  56. There are a few things you can now customize in the configuration files for the plugin, found in the plugins/Lockette folder. After running the plugin for the first time, two files will be created, config.yml and strings.yml. The first holds the following settings:
  57.  
  58.     * enable-messages-* - Enables or disables groups of messages listed in the strings.yml file. Not counting the broadcast ones.
  59.     * broadcast-*-target - Sets the group or player that specific broadcast messages should be sent to. This can be set to "" for no one.
  60.     * explosion-protection-all - Enabling this extends explosion protection to all containers on the server, not just [Private] ones. Default is disabled.
  61.     * enable-permissions - Allows the use of permission nodes to specify who can do what. If this is disabled, groups will still be used but admin status is taken from the ops file. Defaults to false.
  62.     * allow-admin-bypass - Allows admins to go though any protected door. Default is true.
  63.     * allow-admin-snoop - Allows admins to peek into chests owned by other people. Default is false, and this setting is recommended! A broadcast message will be sent each time an admin snoops in a protected container where the admin doesn't have permission to. The message will be sent to a player or group as specified in another option. Admins can still break protection on chests if this is disabled, however.
  64.     * enable-protection-doors - Enables support for private doors, defaults to true.
  65.     * default-door-timer - Sets the door closing timer for all protected doors on the server, unless overridden by a specific sign. Defaults to 0, which disables the door closing timer.
  66.  
  67. In the strings.yml file, you can set alternate language tags for [Private] and such, in UTF-8 format. The default alternate tags are in French, but server ops are free to translate the whole file into the language of their choice. If you do this, please share it back to me~ :3 If you want to disable only a specific message, you can set it to "", the empty string. Admins can use the command '/lockette reload' after editing the configuration files, to reload them.
  68.  
  69. If a Permissions plugin is not available or the enable-permissions option is set to false, Lockette will use the ops file to determine who are admins. Admins can break the protection on any chest, and look inside protected chests (only if the related option is set), as well as reload the plugins configuration files.
  70.  
  71. If a Permissions plugin is available and the enable-permissions option is set to true, the following nodes will be used instead of the ops file and are included by default in the '*' node:
  72.  
  73.     * lockette.user.create.* - Permission required to create a protected container or door. Possible sub-nodes include chest, dispenser, furnace, and door.  (The permission lockette.create.all is still supported, but obsolete.)
  74.     * lockette.admin.create.* - Allows admins to create containers and doors for other users. Possible sub-nodes include chest, dispenser, furnace, and door. Leave line 2 blank for the default behavior or enter the name of your choice. Capitalization matters.
  75.     * lockette.admin.break - Allows breaking protection on containers.
  76.     * lockette.admin.bypass - Allows opening of any locked door.
  77.     * lockette.admin.snoop - Allows peeking in protected containers. (The setting allow-admin-snoop must be true.)
  78.     * lockette.admin.reload - Allows use of the reload command.
  79.  
  80.  
  81. Technical Information:
  82.  
  83. This plugin has been tested and shown to be working for many builds of CraftBucket though a number of the more recent builds had a serious issue, so I'm suggesting a minimum build of 561 now. If you update past what is listed in the post's title and the plugin seems to break, it is probably not my fault. Post a note anyway and I'll see about fixing. I'll try and keep up with the new recommended build system, but for latest builds that break things, you should expect some time to pass before I take care of the issue, as this plugin is now mature. :3
  84.  
  85. If there are multiple containers by the placed sign, the plugin will use the NESW rule to choose the first container that is not yet private. To elaborate, the plugin will check to the north of the sign first, and if no container or door is available to the north, it will continue checking clockwise around the sign.
  86.  
  87. Due to the current implementation of the explosion event, this plugin will cancel all explosions that would damage the container or sign, rather than just remove the container and sign from the blocks to be damaged. Canceled explosions still knock signs off the walls. Canceled explosions leave signs looking blank, but this is just a graphic glitch, reconnect to fix.
  88.  
  89. Bonus: This plugin will prevent chests bigger than 2 blocks from being created via glitches. (Again, this could be circumvented using WorldEdit commands, so take care who has access to such a plugin.)
  90.  
  91. This plugin was inspired by the old hmod plugins Lock by Roman "kingseta" Pramberger and ChestCapsule by Fernando "Fergo".
  92.  
  93.  
  94. Hooking into Lockette:
  95.  
  96. If you are a plugin author and want to connect to Lockette, you can use a public static function to get information about the protected status of a block.  More info later.
  97.  
  98.  
  99. Future Possibilities:
  100.  
  101. There are a number of things that have been suggested, and they tend to be added to the list below if I think they might be a good idea. However, some sort of locked container limit is requested often but this is not possible without a database to track the number of locked containers someone has. All things considered, this will not be supported. On the up side, without a database you can have literally millions of locked containers without any sort of lag.
  102.  
  103. Aside what has already been implemented, the following may or may not appear in future versions:
  104.  
  105.     * Furnace/dispenser clusters, protected by a single sign.
  106.     * [Log] sign to list recent users of a container or door.
  107.     * iConomy fee for protecting containers/doors.
  108.     * Automatic tagging of keywords with color codes.
  109.  
  110. If you want any of the above features sooner than never, let me know!
  111.  
  112.  
  113. Changelog:
  114.  
  115. Version 1.3.7
  116.     * Worked around a change in MinecartManiaAdminControls breaking door signs.
  117.     * Changed the default value for enable-permissions to false.
  118.           o Too many people had Permissions/GroupManager installed but didn't know how to use.
  119.           o This will not effect existing configuration files.
  120.  
  121. Version 1.3.6
  122.     * Fixed a config file option forcing permissions on if there are no permission plugins.
  123.     * Added an internal warning about builds 685-703.
  124.  
  125. Version 1.3.5
  126.     * Automatically closing doors! (Eg.: Use [Timer: 5] on the private sign.)
  127.           o The global configuration setting can be overridden using an option on the sign.
  128.     * Added a check to see if a user is online, when creating a container for another user.
  129.           o Allowed a group to be set as an owner, but with no permission to modify.
  130.     * Support for using GroupManager and Permissions simultaneously.
  131.           o Fix for some dated or fake versions of permissions plugins.
  132.     * Separate permissions for creating protection on different types of blocks.
  133.           o Also for the admin version.
  134.           o Changed lockette.create.* to lockette.user.create.*, but left in support for the old node.
  135.     * Added a number of new configuration options.
  136.           o Several options to specify who to send the broadcast messages to.
  137.                 + Support for either a group or a specific player.
  138.           o Options for disabling permissions and door bypassing.
  139.     * Fixed a case where the bypass message reported the wrong user.
  140.     * Added a workaround for an mcMMO bug.
  141.     * New undocumented command '/lockette version'.
  142.  
  143. Version 1.3.4
  144.     * Native support for GroupManager, up to date Permissions handling, and three new permissions nodes!
  145.           o Changed snoop behavior for doors, with a new permission, no longer broadcasts.
  146.           o Added a permission for creating locked containers at all.
  147.           o Added an admin permission for creating locked containers for anyone.
  148.     * Improved player listener effeciency in builds 588+.
  149.     * Fixed an exception that was throwing for builds 561-587.
  150.     * Wooden door breakage security fix for change in builds 561+.
  151.     * Blocked tilling dirt under a door in builds 561+.
  152.     * Blocked placing of doors by owned doors in builds 561+.
  153.     * Updated internal minimum recommended build to 561... :3
  154.           o Added an internal warning about builds 605-612.
  155.  
  156. Version 1.3.3
  157.     * Fixed plugin for a breaking change in CB build 600, though backwards compatible.
  158.     * Added a second undocumented public function, for connectivity.
  159.  
  160. Version 1.3.2
  161.     * Enabled redstone for protected doors with [Everyone] as a user.
  162.     * Improved detection of conflicting private doors, when creating new ones.
  163.     * Relaxed restrictions on the placement of [More Users] signs on doors. (See doors section.)
  164.     * Blocked a possible security issue with double doors.
  165.     * Added support for CraftBukkit build 561 and up.
  166.  
  167. Version 1.3.1
  168.     * Increased the internal recommended build version from 522 to 552. (Oops.)
  169.     * Added a config file option to globally enable/disable door support.
  170.     * Slightly changed container search to use the NESW rule, disregarding block types.
  171.  
  172. Version 1.3
  173.     * Full support for protected doors, including double doors.
  174.     * Added [Operators] keyword as a built in user group.
  175.     * Color codes are stripped from signs before processing, for color compatibility.
  176.     * Prevents an issue where one could replace sign text, in CB builds prior to 522.
  177.     * Catches issues with out of date Permissions plugin.
  178.     * Exposes an interface for other plugins to access, to check Lockette protected blocks.
  179.     * Some general speed improvements.
  180.  
  181. Version 1.2.2
  182.     * Workaround for Craftbukkit 454+, though this may break again in the future.
  183.     * Fixed a bug I noticed in sign editing.
  184.  
  185. Version 1.2.1
  186.     * Built against a newer version of Bukkit.
  187.  
  188. Version 1.2
  189.     * Added configurations file for settings, and a strings file for additional language support.
  190.     * Full Nijikokun's Permissions support, both versions 2.0 and 2.1, for groups and admin powers.
  191.           o Defaults to using the ops file, if the plugin isn't available.
  192.     * Allowed the editing of previously placed signs.
  193.     * More helpful messages, and options to disable them if you don't like messages.
  194.     * Many other small details.
  195.  
  196. Version 1.1.4
  197.     * Added a check for the server's CraftBukkit build version on enable. Enable will be aborted if it detects an unsupported version, and says so clearly in the log. (Auto-detects builds 231-326 only.)
  198.     * Strengthened the owner's username check to be case sensitive. (Entered automatically, so no need to be insensitive here.)
  199.     * Removed one unnecessary server log message.
  200.  
  201. Version 1.1.3
  202.     * Added informational server log messages.
  203.     * Added preliminary support for Nijikokun's Permissions plugin. (Not functional yet.)
  204.     * Thought up a better namespace, so changed it again.
  205.  
  206. Version 1.1.2
  207.     * Relaxed all user name checks to be case insensitive.
  208.     * Updated plugin to use a more personal namespace. (Required by craftbukkit soon.)
  209.  
  210. Version 1.1.1
  211.     * Made the check for [Everyone] case insensitive.
  212.  
  213. Version 1.1
  214.     * Protection extended to Dispensers and Furnaces.
  215.     * Explicitly blocked the creation of illegal sized chests. (Chests are 1 or 2 blocks in size only.)
  216.     * Allowed [Everyone] as a user that lets anyone into the container.
  217.     * Allowed more users via additional signs, headed [More Users].
  218.  
  219. Version 1.0.1
  220.     * Improved handling of long user names. (Name matches to 15 characters.)
  221.     * Improved status messages from the plugin.
  222.  
  223. Version 1.0
  224.     * First public release.
clone this paste RAW Paste Data