[SEC] Lockette - Simple chest and door lock, no databases! [Moved to BukkitDev]

Discussion in 'Inactive/Unsupported Plugins' started by Acru, Feb 14, 2011.

  1. Offline

    Acru

    Lockette - The sign-based container and door lock for Bukkit! - by Acru Jovian

    ElgarL has been assigned as the current maintainer of this project, please forward any important issues to him as well. This post is abandoned, but proceed to BukkitDev for updates.

    Download it at BukkitDev! (Alternate) (JAR) (Source), also view the Change Log on BukkitDev.



    Supported external plugins:
    • Permissions - Permissions/Groups
    • GroupManager - Permissions/Groups
    • PermissionsBukkit - SuperPerms/Groups
    • PermissionsEx - SuperPerms/Groups
    • bPermissions- SuperPerms/Groups
    • Towny - Groups/Zones
    • SimpleClans - Groups
    • mcMMO - Groups (Disabled by default now, due to issues.)
    • Factions - Groups
    • LWC - Zones
    • Register - Economy
    Alternate languages included:
    Confirmed compatible plugins: ColorSign, SpeedSign.
    Conflicting plugins: ChestShop, Most sign editors!


    The active Lockette information page will commute to BukkitDev soon, but the forum thread is still the best place for discussion.



    Overview:

    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.

    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.

    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.)

    [​IMG]

    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.

    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.


    Working with Doors:

    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.

    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!

    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.)

    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.

    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.


    Features:
    • No passwords or databases needed!
    • Permission checks run in constant time, no matter how many protected containers.
      • One owner and up to 11 additional users supported. (17 for double chests!)
      • Allows access to [Everyone] while still protecting the container from vandalism.
      • Allows group names in conjunction with many other plugins.
    • Special powers for ops or admins, configurable with permissions.
      • Reports when an admin does something naughty.
    • Protects single and double chests, dispensers, and furnaces.
      • Explosion and block-break protection for the protected container and sign.
        • Option to protect all containers from explosions.
    • Full support for doors, both wooden and iron!
      • Double doors are handled automatically, with no redstone.
      • Doors can be set to close automatically, via a timer setting.
      • Redstone hacking is disabled for protected doors.
    • Prevents creation of chests larger than 2 blocks.
    • Informative or helpful messages when interacting with containers.
      • The first time a chest is placed, a help message will be shown.
      • Types of messages shown are configurable in settings.
      • Additional language support.

    Advanced Setup (Permissions) (open)

    Advanced Setup:
    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:
    • 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.
    • enable-messages-* - Enables or disables groups of messages listed in the strings.yml file. Not counting the broadcast ones.
    • broadcast-*-target - Sets the group or player that specific broadcast messages should be sent to. This can be set to "" for no one.
    • explosion-protection-all - Enabling this extends explosion protection to all containers on the server, not just [Private] ones. Default is disabled.
    • allow-admin-bypass - Allows admins to go though any protected door. Default is true.
    • 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.
    • enable-protection-doors - Enables support for private doors, defaults to true.
    • 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.
    In the strings.yml file, you can set alternate language tags for [Private] and such, in ANSI format. If you need characters not in ANSI then you might try UTF-8 format, though it seems bugged tight now. 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.

    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. All non-ops will be able to create protected containers for themselves.

    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:
    • 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.)
    • 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.
    • lockette.admin.break - Allows breaking protection on containers.
    • lockette.admin.bypass - Allows opening of any locked door.
    • lockette.admin.snoop - Allows peeking in protected containers. (The setting allow-admin-snoop must be true.)
    • lockette.admin.reload - Allows use of the reload command.

    Technical Information (open)

    Technical Information:

    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

    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.

    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.

    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.)

    This plugin was inspired by the old hmod plugins Lock by Roman "kingseta" Pramberger and ChestCapsule by Fernando "Fergo".

    Hooking into Lockette (open)

    Hooking into Lockette:

    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, perhaps, but if you need the details now then go poke through the source~

    Future Possibilities:

    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, and there are permissions to restrict who can create locked chests. Perhaps only allow Moderators to create locked chests for other users, if you don't want to allow infinite locked chests.

    Aside what has already been implemented, the following may or may not appear in future versions:
    • Furnace/dispenser clusters, protected by a single sign.
    • [Log] sign to list recent users of a container or door.
    • iConomy fee for protecting containers/doors.
    • Worldguard connection.
    • [Protected] tag for viewing only.
    • Specific time range that doors can be opened.
    • DataLog plugin support.
    • More types of protected blocks, such as brewing stands.
    If you want any of the above features sooner than never, let me know! However, I currently see Lockette as functionally complete, for the most part, in that it already has all the functionality it needs. Future updates will mostly be to account for changes in Minecraft and Bukkit.


    Final Note:

    Please leave a reply if there are any bugs or suggestions, and if you like this plugin you can click the like button at the bottom of this post~ Thanks to those few that have donated! [​IMG]
     
  2. Offline

    Grenelvec

    How can I make permissionsBukkit groups work with my lockette signs? Trying to secure a door to Admins, but it just tries to treat Admins at a user, and not a group

    I am running 1.7.9 on 1.4.7R1.0 without issue.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 18, 2016
  3. Offline

    LlmDl

    are you putting [Admins] on line 3 or 4?
     
  4. Offline

    Saiyan

    hello,

    Im trying to change
    to
    But when I change it, still shows with the parentheses....I dont know whats wrong. Running 1.7.9
     
  5. Offline

    geloum

    Hello there,

    I see after one year that this plugin is still updated, i'm really glad to get my Minecraft server back.

    I have one issue with Lockette/Factions I think.

    When a user from another or same faction tries to open a DOUBLE wooden door (with the lockette on it), one of the door just stays open, and the other is closed (he gets the error message telling him that he cannot open it).

    How can I fix this ?

    Thanks for your help.
     
  6. Offline

    Saiyan

    should do the trick. not really sure what causes it.
     
  7. Offline

    midbifroid

    i see lockette is growing and can be much bigger !
    i have 3 request

    1) FEE is not working for me (help!):
    in the enchantment table:
    [Private]
    any user
    [Everyone]
    [Fee:20]
    nothing occurss, no payment

    2) can you add...?:
    - a Gain feature opposite of Fee/payment [Gain:20.3] : you gain 20.3 money for using this
    - a item features for:
    - - "have" [ItemHave:276] : you need diamond sword to use this
    - - "swap" [ItemSwap:276] : you will los your sword when you use this
    - - "give" [ItemGet:276] : you will adquire a sword when you use this
    - user exception (blacklist X or B, and pay list $) when using [Everyone], in another sign or in same sign
    - - [Black List] user1, user2, user3
    - - [private] me X:eek:ther B:eek:ther or something
    - - [private] me 20$another another$20

    3) Can you add flags for shorten? (you previusly see X or B are not flags because isnt inside braces)
    Example: i want timer and fee (pay), or gain
    [Private]
    any...
    [T:2;P:2.5;G:30]
    Example: i want a "everyione" and a "have 2 items" and a "give item" and a "give money" and timer and ban users
    [Private]
    any...
    [E;N:123,276;G:356;M:32;]
    X:noob


    4) can you ad continuous format?
    Ex:
    [Private][Eve
    rione][Flag;Flag
    Flag;Flag] any_us
    er X:noob
     
  8. Offline

    Buzas

    is 1.4.7 update out yet?
     
  9. Offline

    LlmDl

  10. Offline

    Diamondcat117

    Hey, I really love the sound of this plugin but I have one problem.... My name is too long! What do I do? my name is vermittler_young. I tried to put it on the sign, but it's too long. Please help! :'(
     
  11. Offline

    chopstick121

    it kept spamming trapdoor
     
  12. Offline

    stickeric

    What exactly is the lockette support with factions?

    Does it allows us to lock the chests for faction members but still available for raiders? ElgarL
     
  13. Offline

    TDSrock

    made a quick vid explaining some lockette stufs HERE
     
  14. Offline

    HIT_MARK_ER

    I seem to be having some problems with lockette, when a sign is place above a door it doesn't work, when a sign is place on a door only the block sign is on it protected, not the other half of door...any help?
     
  15. Offline

    marubal21

    I continue to see this mesage pop up on my logs from different players, what does it mean?
    [INFO] [Lockette] Player_X just tried to change a non-editable sign. (Bukkit bug, or plugin conflict?)
     
  16. Offline

    Jemrada

    Is it possible to protect doors from Zombies breaking?
     
  17. Offline

    Linex0010

    Hello:
    i'm Minecraft players
    I am from Taiwan
    I hope to be able to obtain your consent
    To finished Lockette
    And publicly so that other players can use
    I am sorry, my English is not very correct
     
  18. Offline

    LlmDl

    Lockette is already being maintained by Elgarl. It is available on dev.bukkit.org.
     
  19. Offline

    Cagalj

    Hello, i am using this plugin on my server and when i want open some chest it say that i am not allow. I set perrmisons to true and set permissons into groupmanager folder. But stil i dont have perrmisons.. Wich permissions i must set to groupmanager foler to i have all permissions of lockette? To open any chest..?
     
  20. Offline

    LlmDl

    From the first post in the thread:
    Code:
    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.
    lockette.admin.break - Allows breaking protection on containers.
    lockette.admin.bypass - Allows opening of any locked door.
    lockette.admin.snoop - Allows peeking in protected containers. (The setting allow-admin-snoop must be true.)
    lockette.admin.reload - Allows use of the reload command.[/code
     
  21. Offline

    Linex0010

    Okey embarrassed
     
  22. Offline

    bobmichael30

    How do we blow up the chest? I have a pvp server and when ever I try to raid it won't let me blow up the chest.
     
  23. Offline

    LlmDl

    privated chests cannot be blown up, sorry.
     
  24. Offline

    lekrosa

    ElgarL I have no idea if this has been pointed out before, but something must be done about Locketted chests and Hoppers. (and this should be configurable)
    Options should be added to... say, block a hopper from inputting or outputting from a Lockette chest, or only allowing Hoppers with a Lockette sign belonging to the owner taking out from the chest could be allowed, but those without a Lockette sign matching the chest's Lockette would be disallowed.

    Mostly everything else still works in 1.5, as partially tested.
     
  25. Offline

    ElgarL

    When bukkit has the required events we will handle them.
     
  26. Offline

    lekrosa

    Temporarily, I have created a plugin to block the Hopper, but hopefully, Bukkit will update their API soon...
     
  27. Offline

    josh3529

    This plugin is completely useless now that the hopper has been added, please update quick so people cant steal with hoppers!
     
  28. Offline

    LlmDl

    The dev just responded 2 posts above yours.
     
    netherfoam likes this.
  29. Offline

    c0de_junkie

  30. Offline

    ElgarL

  31. Offline

    Paxination

    There is an event tho to block other players from adding a hopper to a chest. Its an event that you probably already use to block other players from locking someones elses locked chest.

    PlayerInteractEvent

    event.getaction()=ACTION.RIGHT_CLICK_BLOCK
    or LEFT_CLICK_BLOCK

    since this is what you want to do is block the players from placing a hopper onto a chest that does not belong to them. when this event pops up you check to see if its locked, if it is, compare owner with event.getplayer() and cancel if not equal.

    Doubt bukkit will make an event for it. And even if they do, this method will work.

    Hell I might make a plugin that depends on lockette and will do this itself until you guys update it. LWC allready has a fix for it. But we prefer Lockette.

    Wouldnt that method work?
     
    c0de_junkie likes this.

Share This Page