[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

    Blackstorm72

    I believe this is due to the fact that .yaml files cannot read the character "@".
    I'm sure thats a YAML restriction. It may not be, and instead just may be how YAML configures the usage of "@".

    That sounds great! iConomy is a bit ..eh well I think for the matter complicated but I do know that Niji has something in his iConomy thread about hooking the system into another plugin. You would have to check that out.
    Also, I don't know if has much interest, but I know our server of 8-12 people online do lol :p

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

    Acru

    Interesting, I had not run into that before. From the readout it is being thrown by the yaml parser within CraftBukkit. You can put the string within quotes though, like:

    msg-admin-release: "@@@ has broken it!"

    Its already there, though don't worry, yer not the first that missed it in the advanced section. Try:

    msg-admin-snoop: ""

    Thanks~ :3

    I shall then. :3

    Update: I had a look, and it doesn't seem any worse than hooking into Permissions.

    I still can't reproduce this, it must be another plugin interfering or otherwise not compatible with multiverse.
    I was testing with multiverse 1.5, permissions 2.5.4, cb 556, and Lockette 1.3.2, specifically.

    You could perhaps disable plugins a few at a time, until it works, to narrow it down?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  4. Offline

    mooztik

    i understand the problem.
    if lockette support buttons and pressure plate, the automatic closing process is found. :)
    using iron door, to restrict door usage from a switch/button... et voilà :)
     
  5. Offline

    Acru

    I'll think on this, but the problem with pressure plates and etc is that you can't tell who is using. The redstone could be faked perhaps...

    And there are some new features available in CB build 561+, but its not in common use yet as it breaks everyone's plugins, except Lockette 1.3.2 which I just updated today. :3
     
  6. Offline

    MacVaultDweller

    Just stopped in to say thanks again for all of your hard work I love this plugin.
     
  7. Offline

    Sparx

    Ohhh, thank you. When I saw the "" I figured it meant leave it like this here:
    msg-admin-snoop:
    not like this:
    msg-admin-snoop: ""

    Thanks so much ;D
     
  8. Offline

    Azur

    Would it be possible to make it so that the various (Admin) messages only show to people with a lockette.admin permissions? I like having my admins able to check people's chests, but it does spam the users a bit when there's a bunch of chests.
     
  9. Offline

    Acru

    Yer welcome~

    As I said in the last post, you can set the messages as follows in strings.yml to just disable it;
    msg-admin-snoop: ""
    The snoop messages will still appear in the server log, though.

    It was originally meant as a way for telling other players on the server when a mod was being naughty~ Is there a specific reason why you might like some to get the message and some not?

    Incidentally, I was just reading how LWC's door support was broken, though it is working in Lockette. :3

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  10. Offline

    Azur

    Well, I'd like to see when my mods are being naughty, but would rather not have all my users see it, but disabling it will work for now, so thanks for the help :)
     
  11. Offline

    Acru

    Mkay, and I'll add it to the list.
     
  12. Offline

    MacVaultDweller

    Lockette is locking doors but the group access seems to be not allowing group access.
     
  13. Offline

    Acru

    I know [Everyone] and [Operators] work but as for custom groups, I'll look into it.

    Which permission/group plugin and version are you using?
     
  14. Offline

    MacVaultDweller

  15. Offline

    nanashiRei

    Please add an option to disable the "snooping" message or make it shown only to the owner of the sign. Otherwise very powerfull and nice plugin!
     
  16. how can in prevent op's from breaking the sign?
     
  17. Offline

    leetgamer

    You can't.. don't have op's you don't trust.

    Acru, does this conflict with LWC? I want this for the door lock soo badly. ;)
     
  18. Offline

    Acru

    Read up in the thread, or in the main post, you can turn it off, heh.

    De-op, or take away permission to in a permissions plugin.
    Ops need the power in case someone locks someone else's chest, etc.

    I haven't tested or anything, but I've had no complaints.
    If you have a container locked with both plugins, you would likely need permission to open from both plugins.
    As doors don't work in LWC atm, there probably won't be a conflict there.
     
  19. Offline

    leetgamer

    Code:
    2011-03-26 00:42:31 [SEVERE] Could not pass event BLOCK_RIGHTCLICKED to Lockette
    java.lang.NullPointerException
        at org.bukkit.craftbukkit.block.CraftSign.getLine(CraftSign.java:24)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:755)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:729)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:727)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:611)
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.rightclickDoor(LocketteBlockListener.java:396)
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onBlockRightClick(LocketteBlockListener.java:380)
        at org.bukkit.plugin.java.JavaPluginLoader$20.execute(JavaPluginLoader.java:259)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:255)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:493)
        at net.minecraft.server.Packet15Place.a(SourceFile:57)
        at net.minecraft.server.NetworkManager.a(SourceFile:230)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:76)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    2011-03-26 00:42:32 [SEVERE] Could not pass event BLOCK_DAMAGED to Lockette
    java.lang.NullPointerException
        at org.bukkit.craftbukkit.block.CraftSign.getLine(CraftSign.java:24)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:755)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:729)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:727)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:611)
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onBlockDamage(LocketteBlockListener.java:338)
        at org.bukkit.plugin.java.JavaPluginLoader$22.execute(JavaPluginLoader.java:269)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:255)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:358)
        at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
        at net.minecraft.server.NetworkManager.a(SourceFile:230)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:76)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    2011-03-26 00:42:49 [SEVERE] Could not pass event BLOCK_DAMAGED to Lockette
    java.lang.NullPointerException
        at org.bukkit.craftbukkit.block.CraftSign.getLine(CraftSign.java:24)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:755)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:729)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:727)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:611)
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onBlockDamage(LocketteBlockListener.java:338)
        at org.bukkit.plugin.java.JavaPluginLoader$22.execute(JavaPluginLoader.java:269)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:255)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:358)
        at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
        at net.minecraft.server.NetworkManager.a(SourceFile:230)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:76)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    2011-03-26 00:42:49 [SEVERE] Could not pass event BLOCK_DAMAGED to Lockette
    java.lang.NullPointerException
        at org.bukkit.craftbukkit.block.CraftSign.getLine(CraftSign.java:24)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:755)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:729)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:727)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:776)
        at org.yi.acru.bukkit.Lockette.Lockette.findBlockOwner(Lockette.java:611)
        at org.yi.acru.bukkit.Lockette.LocketteBlockListener.onBlockDamage(LocketteBlockListener.java:338)
        at org.bukkit.plugin.java.JavaPluginLoader$22.execute(JavaPluginLoader.java:269)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:255)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:358)
        at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
        at net.minecraft.server.NetworkManager.a(SourceFile:230)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:76)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    It worked at first, I put it to use in a small bank idea. But after awhile a set of double iron doors wouldn't close, and I had this error. I removed the sign and doors, re-added them, and the problem persisted.
     
  20. Offline

    Calvin

    This is a wonderful plugin, but you need to find a way around people with WorldEdit. There's got to be some way to keep that sign on the chest no matter what command is used. Like maybe you could have it look for something thats removing the sign, like a command and then just have the command not terminate or something I don't know. If you got that sign to not even be considered a sign maybe, or something like that.
     
  21. Offline

    Acru

    This is rather unusual, I traced the problem down to a point where CraftBukkit was saying a block was a sign, but apparently the sign data is null. (I can catch this, but the issue is in CB.)

    This could be due to using a CraftBukkit build older than build 552, and the old chunk ghosting bug. Could you tell me what build of CraftBukkit and such you are using? (If less than 552, I highly recommend updating.)

    Well now, I can't control WorldEdit, but if @sk89q is willing, WorldEdit could support Lockette...
    There is a public function available in Lockette since version 1.3, that WorldEdit could use to check a block's protection.
     
  22. Offline

    leetgamer

    K, I'm using CB531, and waiting on permissions to get sorted out to update. I'll just deal with it for now, thanks. :)
     
  23. Offline

    MacVaultDweller

  24. Offline

    SplenectomY

    Request: A configuration setting that allows block protection to be turned off. That way, on servers with say, Towny, where areas are inherently protected from destruction, the sign and chest still will not be destroyed, but if that person's town runs out of money, squatters or tyrants can take over the land and be able to destroy their chest.

    The latest version of LWC implemented this setting and it is amazing. I would LOVE IT if you were able to do the same so I can still give my users the flexibility of both plugins. We are currently having a problem with locked chests laying around but we fixed the LWC portion of it with his latest release. Thanks in advance!!!
     
  25. Offline

    PlannedBoredom

    What if the name is longer than 1 line? my friend's example name: plumppurplehippo
     
  26. Offline

    nanashiRei

    Read again. My config is as follows:

    Code:
    enable-messages-error: false
    enable-messages-user: false
    enable-messages-help: false
    enable-messages-owner: false
    enable-protection-doors: true
    explosion-protection-all: false
    allow-admin-snoop: true
    
    And everytime i open a door there is a message send to all players about me snooping into a "container" of someone.

    I also tried to do this:

    Code:
    alternate-private-tag: Privé
    alternate-moreusers-tag: Autre Noms
    alternate-everyone-tag: Tout le Monde
    alternate-operators-tag: Opérateurs
    msg-user-illegal: Illegal chest removed!
    msg-user-resize-owned: You cannot resize a chest claimed by ***.
    msg-help-chest: Place a sign headed [Private] next to a chest to lock it.
    msg-owner-release: You have released a container!
    msg-admin-release: (Admin) @@@ has broken open a container owned by ***!
    msg-user-release-owned: You cannot release a container claimed by ***.
    msg-owner-remove: You have removed users from a container!
    msg-user-remove-owned: You cannot remove users from a container claimed by ***.
    msg-user-break-owned: You cannot break a container claimed by ***.
    msg-user-denied-door: You don't have permission to use this door.
    msg-user-touch-owned: This container has been claimed by ***.
    msg-help-select: Sign selected, use /lockette <line number> <text> to edit.
    msg-admin-snoop:
    msg-user-denied: You don't have permission to open this container.
    msg-error-claim: No unclaimed container nearby to make Private!
    msg-error-claim-conflict: Conflict with an existing protected door.
    msg-owner-claim: You have claimed a container!
    msg-error-adduser-owned: You cannot add users to a container claimed by ***.
    msg-error-adduser: No claimed container nearby to add users to!
    msg-owner-adduser: You have added users to a container!
    msg-help-command1: /lockette reload - Reloads the configuration files.
    msg-help-command2: /lockette <line number> <text> - Edits signs on locked containers. Right click on the sign to edit.
    msg-admin-reload: Reloading plugin configuration files.
    msg-error-edit: First select a sign by right clicking it.
    msg-owner-edit: Sign edited successfully.
    
    As you can see i removed the string for the message and yet it is still send to all my players.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  27. Offline

    deadlock989

    Using the plug-in and very much enjoying it, it's superior to the Essentials protection.

    Request for a feature:
    • Private container/door signs display the first [Private] line in a colour (red by default, maybe configurable in options?)
    • Containers with a [Everyone] tag display that line in green (or configurable).
     
  28. Offline

    Acru

    Use a pair of double quotes (the empty string), as it says in the main post. :3
    Like this: msg-admin-snoop: ""
    As for it sending the same message for doors, it needs to be updated yes.

    If you're still on Permissions 2.0/2.1, its not gonna get updated, however it is continued in Permissions (Phoenix), and another option is GroupManager. In the mean time, restarting the server makes the chunk ghosts go away for a while.

    Oh! That is good news, thanks for telling me you got it fixed. :3

    By squatters and tyrants, I assume you don't mean admins?

    If you are using a permissions plugin, you could give everyone the permission to lockette.admin.break and edit the appropriate message to either "" (empty string) or another one of your choosing?

    Let me know if this works for you, with Towny.

    Names are truncated and compared to 15 characters, so just 'plumppurplehipp' works.

    Glad to hear that. :3
    If you just want custom colored signs, you can try the plugin ColorSign, which is compatible with Lockette.
    If you have a way to enter color codes in when placing a sign, that will work too, as Lockette will ignore.
    As for automatic color tagging, I'll put it on the list for now. :3
     
  29. Offline

    SplenectomY

    Excellent idea. Thank you SO much for this amazing plugin.
     
  30. Offline

    NEREVAR117

    People use this to grief on my server. Is there a way to make it to where admins can remove the signs?
     
  31. Offline

    leetgamer

    I'm using 2.5.4 but it doesn't work when I attempt multi-worlds. And from what I can see on the thread, everyone is posting errors with 556.
     

Share This Page