[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

    nskjunky

    could it be that Worldguard (or WorldEdit) has some problems with lockette? because everytime an admin or op tries to go through a door, the door (if it is a double-door) only opens one half and lets the other one closed. after a specified timer (normally the whole door would close automatically) the doors just "switch".
     
  3. Offline

    Maxis010

    Yes that is worldguard conflicting
     
  4. Offline

    boksa

    This plugin is great! I have one problem though. Door placement works correctly, and will restrict everyone but the owner of the door to go through it. But anyone can simple break blocks around the door, even if they dont have the admin bypass privilege in Permissions. How can i solve this problem?
     
  5. Offline

    Maxis010

    You will need to use another protection plugin to secure areas like that
     
  6. Offline

    boksa

    Darn. Is there a plugin that does this with signs, or a plugin that works with lockette?
     
  7. Offline

    Maxis010

    If you have MySQL support I would recommend PreciousStones, it works with blocks so you might be able to make it work if you set the 2 sign IDs (Floor Sign and Wall Sign, not the 300 something item code) if not then there are alternatives, one I was looking in to before I moved to a VPS was bZone, unfortunately it doesn't have any in-game zone builders so it's not good if you want to build a series of zones quickly and easily
    Look around and see what you find, if PreciousStones becomes your best option but you lack MySQL then get in touch via a private message and I'll send you a copy of PreciousStones before they moved to MySQL, it won't have any new features or support though so I'll be your best bet for set-up assistance
     
  8. Offline

    Jadedwolf

    I'm getting this same issues, also randomly the plugin just lets people access protected chest it's random without any console errors or notices.
     
  9. Offline

    Aeron

    Will Lockette support custom doors/chests? With ItemCraft it is now possible to add new blocks/items to a bukkit server, so... could you consider making it work with a config file, where there would be block ids for blocks like chests and doors, and basically it would disalow interaction with that block, regardless weather it is a door, chest, workbench, furnace, custom container etc?
     
  10. Offline

    Blackstorm72

    Doing some additional research, it appears to be a map issue.
    Reloading the server doesn't fix the issue on my end, but restarting the server did.

    What appears to be happening as maps are slower to load in 1.5 the plugin doesn't recognize that there are entity of chests/doors/etc. that are there, and therefore not locking them.

    It appears to affect a few other plugins but nothing major (it did occur as well with a sign shop), it isn't map corruption, its just the plugin not seeing the chests because the map did not load them.
    It also appears to be client-side--server-side communication errors. It seems very common in 1.5. Several times, SEVERAL, have I had problems with clients not syncing with the server, and people joining and leaving the game is the most common 15 minute break thing to do.

    I don't think its possible to fix this - but it all depends on if my testing is true, its whats happening here.
     
  11. Offline

    Color42

    CB 798 Lockette 1.3.6./1.3.7/1.3.8 Same error with all 3 versions

    2011-05-21 11:12:30 [INFO] [Permissions] version [2.7.3] (Phoenix) loaded

    2011-05-21 11:12:34 [INFO] Lockette version 1.3.7 is being enabled! Yay! (Core version 1.0)
    2011-05-21 11:12:34 [INFO] Lockette: Detected craftbukkit build [798] ok.
    2011-05-21 11:12:34 [SEVERE] Error occurred while enabling Lockette v1.3.7 (Is it up to date?): loader constraint violation: loader (instance of org/bukkit/plugin/java/PluginClassLoader) previously initiated loading for a different type with name "com/nijiko/permissions/PermissionHandler"
    java.lang.LinkageError: loader constraint violation: loader (instance of org/bukkit/plugin/java/PluginClassLoader) previously initiated loading for a different type with name "com/nijiko/permissions/PermissionHandler"
    at org.yi.acru.bukkit.PluginCore.setupPermissions(PluginCore.java:181)
    at org.yi.acru.bukkit.Lockette.Lockette.onEnable(Lockette.java:121)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:125)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:750)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:253)
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:131)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:109)
    at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:218)
    at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:205)
    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:145)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:265)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
     
  12. Offline

    $p!k3

    helpz?
    Code:
    20:47:23 [SEVERE] Could not pass event PLAYER_INTERACT to Lockette
    java.lang.IllegalArgumentException: Illegal group reference
            at java.util.regex.Matcher.appendReplacement(Matcher.java:713)
            at java.util.regex.Matcher.replaceAll(Matcher.java:813)
            at java.lang.String.replaceAll(String.java:2189)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(LocketteBlockListener.java:1304)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.rightclickDoor(LocketteBlockListener.java:508)
            at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(LockettePlayerListener.java:269)
            at org.bukkit.plugin.java.JavaPluginLoader$9.execute(JavaPluginLoader.java:280)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:289)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:162)
            at net.minecraft.server.ItemInWorldManager.dig(ItemInWorldManager.java:64)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:438)
            at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
            at net.minecraft.server.NetworkManager.a(NetworkManager.java:196)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:372)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:287)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
    20:47:40 [SEVERE] [Achievements-0.981] executing Console-Command 'time set 13500'
    20:47:40 [INFO] Error: /time only supports day/night.
    20:48:06 [INFO] 0.0
    20:48:17 [INFO] Lockette: (Admin) kevin has bypassed a door owned by $p!k3
    20:48:17 [SEVERE] Could not pass event PLAYER_INTERACT to Lockette
    java.lang.IllegalArgumentException: Illegal group reference
            at java.util.regex.Matcher.appendReplacement(Matcher.java:713)
            at java.util.regex.Matcher.replaceAll(Matcher.java:813)
            at java.lang.String.replaceAll(String.java:2189)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.canInteract(LocketteBlockListener.java:1304)
            at org.yi.acru.bukkit.Lockette.LocketteBlockListener.rightclickDoor(LocketteBlockListener.java:508)
            at org.yi.acru.bukkit.Lockette.LockettePlayerListener.onPlayerInteract(LockettePlayerListener.java:269)
            at org.bukkit.plugin.java.JavaPluginLoader$9.execute(JavaPluginLoader.java:280)
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:59)
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:289)
            at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:162)
            at net.minecraft.server.ItemInWorldManager.dig(ItemInWorldManager.java:64)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:438)
            at net.minecraft.server.Packet14BlockDig.a(SourceFile:42)
            at net.minecraft.server.NetworkManager.a(NetworkManager.java:196)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:372)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:287)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:394)
     
  13. Offline

    Maxis010

    Try to recreate the error and provide steps as to how you did it, I'm guessing (because I have no clue whatsoever) that this might be from giving a group access to a door but the group doesn't exist, pure guess so if I'm right then yay for that, if not then someone that has some remote shred of a clue can point you in a better direction
     
  14. Offline

    Jadedwolf

    I agree, as this happens mainly in areas that are less used. Like far away from my main city areas.
    I honestly think you are right in this assumption of whats going on.
     
  15. Offline

    Ratchet

    feature request: unlock things after X days of the player not being on the server. then I could set it to say, 3 weeks and if a player hasn't logged in in that long, they probably aren't coming back and I don't want random chests and crap locked forever littering the server
     
  16. Offline

    Felonu

    anybody with correct permissions (or OPs if you don't use permissions) can break locked containers... so they should be able to remove excessive locked containers
    quote from OP
    • lockette.admin.break - Allows breaking protection on containers.
    • lockette.admin.bypass - Allows opening of any locked door.
    I'm not saying that time limits should not be implemented. Hopefully, though, this helps you with your problem for now.

    I also want to say that I would worry about the amount of resources required to check last time someone logged in every time someone opens a chest (or whether it's even possible to check that without a DB).
     
  17. Offline

    Maxis010

    This is either going to take a database or minecraft is secretly tracking the last connected on the server
     
  18. Offline

    Ratchet

    what if it used a database from another plugin? Netstats tracks when each player was last seen online, if it just read from that table of the DB it should be good to go. dunno how the author would feel about integrating it with another plugin like that though, might just be easier to setup his own database thing? I dunno
     
  19. Offline

    Felonu

    Author has said on several occasions that this plugin will not have a database .
     
  20. Offline

    Ratchet

    oh I see. shame. going around and destroying possibly unused chests after X time is not really viable for an admin to be doing all the time :/ some automation would be good
     
  21. Offline

    GladGulGubbe

    Is it able to make only 1 specific person open EVERYONES chests?
    Like for example me, the owner only, and not the admins.

    allow-admin-snoop --> allow-owner-snoop (or something) , possible?
    Thanks in advance! /Glad
     
  22. Offline

    Maxis010

    Get permissions, give yourself the snoop node and take it away from your admins
     
  23. Offline

    Clownz27

    I use multiple pluggins and now that i added a recent 1 (idk which 1) it wont let normal members access doors. it says they dont have permission to access it. Any Ideas?
     
  24. Offline

    AriesT

    My "strings.yml"
    Code:
    alternate-private-tag: личное
    alternate-moreusers-tag: ещё
    alternate-everyone-tag: все
    alternate-operators-tag: модер
    alternate-timer-tag: таймер
    ...

    But [личное], [ещё], [всё] , [модер], [таймер] does not working.. ([private] - work fine)

    What i do wrong?
     
  25. Offline

    Dokuohtei

    But you know people can destroy the signs, right?
     
  26. Offline

    Maxis010

    Unless you have another plugin interfering with Lockette then no they can't unless they own the sign or have the break permission
     
  27. Offline

    Color42

    Update please

    2011-05-26 18:34:30 [INFO] Lockette version 1.3.8 is being enabled! Yay! (Core version 1.0)
    2011-05-26 18:34:30 [INFO] Lockette: Detected craftbukkit build [812] ok.
    2011-05-26 18:34:30 [SEVERE] Error occurred while enabling Lockette v1.3.8 (Is it up to date?): loader constraint violation: loader (instance of org/bukkit/plugin/java/PluginClassLoader) previously initiated loading for a different type with name "com/nijiko/permissions/PermissionHandler"
    java.lang.LinkageError: loader constraint violation: loader (instance of org/bukkit/plugin/java/PluginClassLoader) previously initiated loading for a different type with name "com/nijiko/permissions/PermissionHandler"
    at org.yi.acru.bukkit.PluginCore.setupPermissions(PluginCore.java:181)
    at org.yi.acru.bukkit.Lockette.Lockette.onEnable(Lockette.java:121)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:125)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:750)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:253)
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:134)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:112)
    at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:229)
    at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:216)
    at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:146)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:282)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
     
  28. Offline

    Maxis010

    Wait for Recommended Build, updating to every dev built that is released is pointless
     
  29. Offline

    Color42

    its been broke since last recommend build 798 with the same error
     
  30. Offline

    Acru

    First of all, thanks to @Maxis010, @ElementalBliss, and everyone else to replied to others on this thread while I was gone.

    My computer made a puddle last week, (factory sealed liquid cpu cooler came unsealed), but I am back running again and going through the backlog now, trying to pick out what needs replying to.

    Incidentally, I am looking to update the plugin as needed for the more recent recommended builds and also MC 1.6, but aside from bug fixes or update issues I consider the Lockette plugin functionally complete, and I do not plan to add any more major or minor features.

    Replies to page 27;

    Are you still having this issue?

    You can use the alternate-private-tag in strings.yml to set an alternate tag more appropriate for your needs.
    Eg, you could use 'Stuff for' so the sign will read [Stuff for] [Everyone].

    This idea is more appropriate for a personal shop plugin, perhaps?

    Ah, thanks. It does fail, but usually only from unintended interactions with other plugins, which I have to deal with as they arise, heh.

    For larger constructions, you may want to look into a cuboid type protection plugin, rather than putting a sign on every valuable block~ Heh.

    The only time signs can change to a [?] is if someone fails to create a locked chest. It sounds as if someone else may have found the glitch in version 1.3.7, that was fixed in 1.3.8. Let me know if you have had troubles since.

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

    Pencil

    Hmm, nobody has reported it for a while but there hasn't been many new people on the server recently so it might be that, but they successfully done the protection, it worked for a few days and then bam the sign turns into [?] and everyone can open it :/
     

Share This Page