[SEC/MECH] SimpleChestLock 1.2.2 - Simplified chest locking [1.5.1-R0.2]

Discussion in 'Archived: Plugin Releases' started by DemmyDemon, May 16, 2011.

  1. Offline

    DemmyDemon

    IMPORTANT NOTICE:

    This plugin is no longer being developed.
    I know I've said that there will be no replacement for this before the Official Plugin API, but thanks to some very generous donations I've been inspired to make a Bukkit-based replacement.

    It's called KonseptLocks and will hopefully be hosted on dev.bukkit.org as soon as I can get it properly tested.

    While it will be similar to SCL in many ways, it will not feature the "combination lock" system, as feedback tells me it's hardly ever in use.

    It will not be compatible with SCL and will have a completely new locking file system, which will hopefully remedy any and all "oops, all your locks are gone" problems. If you have 3600 locks you fear you will have to re-lock, don't worry; I'll make an SCL importer for KonseptLocks.


    SimpleChestLock - Simplified chest locking:
    Version: v1.2.2

    Veeery simplified (for the users, anyway) chest locking, sort of like LockChest and others, but very simplified.
    Simply slap a chest with a stick, and it's locked. Only you can access it.
    Slap it with a stick again, and it'll be open for everyone.

    [chest]+[stick]=:cool:

    NOTE: May only lock the chest actually slapped with the stick, depending on settings.
    This means that two people can share a double chest, but it also means that if you forget to lock one half you might as well not have bothered.
    Make sure the settings are configured to do what you want!

    Features:
    • Lock chests slapstick-style!
    • Lock jukeboxes, furnaces, dispensers or whatever you want! Configurable!
    • Doors, trap doors, levers, buttons and pressure plates supported, but see the note below!
    • Configure a different key if you don't like sticks.
    • Lock it with a combination, if you want. (see "Using combinations" below)
    • Lock it for someone else, if you need to.
    • Limit locking using WorldGuard region restriction. (Entirely optional!)
    • Trust system, so you can share the stuff you lock. (see "Trust system" below)
    • Limit system, so you can set how many items users can lock. (see "Using limits" below)
    • Decide who locks what (see "Who locks what?" below)
    • Uses the Bukkit built-in permissions system.
    • Share a chest or door with someone by locking half each on a double-chest or double-door (optional, using the lockPair option).
    • Locked chests can be made to suck in items.
    • Protects locked blocks against destruction.
    • Keep those pesky griefers out of your stuff!
    • Your suggestion here (Except iConomy, that's not going to happen)
    Quick Step Guide for Noobs (by Davecraft) (open)

    1. Install SimpleChestLock, see http://wiki.bukkit.org/Installing_Plugins for details.
    2. Add a permission plug-in http://plugins.bukkit.org (search "permissions") to handle the permission nodes.
    3. Watch the video (see the "Video demonstration by BrandonHopkins" part.)
    4. Add permission variables (see the "Permission Nodes" part) in the permissions plug-in directory. See documentation for your chosen plugin on how to do this.
    5. Edit your settings.yml file. See the "Configuration" part for explanation of the values.
    6. To get the permissions working, see the example under "Who can lock what?"
    7. Enjoy!
    Video demonstration by BrandonHopkins (Somewhat outdated) (open)
    Video demonstration by SeaborgiumMC (open)
    Video tutoral in German by Mamuschkas (open)

    A note on doors, levers, pressure plates and buttons

    When it comes to doors, levers, pressure plates and buttons (DLPB), this plugin only affects who can use them and destroy them.
    That means it does not concern itself with iron doors at all, since nobody can use them, and it does not impact how a door reacts to, for example, redstone current.
    Also, if you place an iron door, and then a button beside it, then lock that button, it's still unsafe: Anyone can come along and place a button or lever on the other side of the door.
    That's why the DLPB functionality is only intended to compliment other plugins, such as WorldGuard.
    This is how I use it: The WorldGuard region allow usage of all buttons and levers, but disallows building. Now I can use SCL to lock the levers and buttons I want protected, and nobody can get around it because WorldGuard will keep them from placing buttons and levers, or digging around them.

    Download SimpleChestLock

    Downloaded over 74.000 times!
    Source Code

    Commands (open)
    /scl reload
    Reloads the chests file and settings -- WILL DISCARD ANY CHEST LOCKS SINCE LAST LOAD, so /scl save first if you don't want that!
    Takes an optional argument; the file to save to. If no file name is given, Chests.txt is used.

    /scl trust
    Takes a lot of arguments, but the basics are add, remove, list and clear.
    Read more about trust under the "Trust system" spoiler!

    /scl save
    Save the chests file right now, rather than wait for the plugin to be disabled to do so. Note that the plugin will also autosave every 5 minutes or so, just in case the server crashes.
    Takes an optional argument; the file to save to. If no file name is given, Chests.txt is used.

    /scl limit
    Shows how many items you can lock, if you're limited.

    /scl status
    Tells you how many items each player has locked, and the total amount of locked items.

    /scl as <user>
    If a user is given, all chests locked from now on will be locked in that user's name.
    If no user is given, all chests locked from now on will be in your own name.
    Very handy for admins that don't like it when users risk their life's savings by leaving them open to public access.
    Careful with this! If you have simplechestlock.command.as permission, but not simplechestlock.ignoreowner, you can lock yourself out of chests as you can't unlock it again!
    Permissions nodes (open)
    This plugin uses the following permissions:
    • simplechestlock.command.reload - Access to /scl reload
    • simplechestlock.command.trust - Access to the /scl trust commands
    • simplechestlock.command.save - Access to /scl save
    • simplechestlock.command.status - Access to /scl status
    • simplechestlock.command.as - Access to /scl as <user>
    • simplechestlock.ignoreowner - Unlock any item, use any item.
    • simplechestlock.ignoreRegion - Don't ask for WorldGuard's permission, even when it's enabled.
    • simplechestlock.nolocklimit - Lock as much as you want, even when limiting is on
    • simplechestlock.lock - Access to locking blocks
    • simplechestlock.usecombo - Access to locking with a combination lock
    If you have defined usePermissionsWhitelist in Configuration (details below), you can specify what blocks are lockable using the locktype permission set.
    Note that you still need the simplechestlock.lock permission to lock stuff, even when whitelisting is activated.
    • simplechestlock.locktype.Lockable_Name_Here - Gives permission to lock Lockable_Name_Here blocks (see " Lockable blocks" below)
    • simplechestlock.locktype.chest - ..for example, gives access to lock chests.
    • simplechestlock.locktype.* - Lock any lockable item.
    This plugin also defines the following nodes for convenience:
    • simplechestlock.* - Full access - Sets simplechestlock.command.*, simplechestlock.ignoreowner, simplechestlock.lock, simplechestlock.locktype.*
    • simplechestlock.command.* - Access to the commands - Sets simplechestlock.command.reload, simplechestlock.command.save, simplechestlock.command.status, simplechestlock.as, simplechestlock.trust
    Lockable blocks (open)

    If you want to enable the permissions-based white-list, use these names:
    • chest
    • furnace
    • burning_furnace
    • dispenser
    • jukebox
    • wooden_door
    • lever
    • stone_button
    • trap_door
    • stone_plate
    • wood_plate
    • brewing_stand
    • enchantment_table
    • fence_gate
    This is fully configurable (see "Configuring lockables" section below), but remember that the permissions are all lower case!
    Who can lock what? (open)

    To define who can lock what, you need two components.
    First, you have to enable it in the config.yml:
    Code:
    usePermissionsWhitelist: true
    Next, you have to define permissions.
    In this example a user called someDude will have permission to lock chests and trap doors.

    Note that this is just an example and might look different for your permissions plugin.
    See "Permission nodes" for more details and "Lockable blocks" for the list of blocks you can lock.

    Code:
    users:
        someDude:
            permissions:
                - simplechestlock.lock
                - simplechestlock.locktype.chest
                - simplechestlock.locktype.trap_door
    Please note that even with a locktype allowed you still have to give simplechestlock.lock!
    Configuring lockables (open)
    The term "a lockable" is used here to describe a block that this plugin will facilitate the locking of.
    This is entirely configurable, but unless you know what you are doing you should back everything up before making changes. This can have disastrous consequences for your lock file and possibly your whole server, depending on how things are set up. Handle with care.

    The different lockables sections do this:

    lockable
    This is a simple list of all the blocks that are to be considered lockable. A standard block only needs to appear here.
    Keep in mind that a block must always appear here, even if it's also in a different section.

    protectiveAura
    This is the list of blocks that will have protective auras on them. Useful for stopping people from using hoppers to suck your stuff out of chests.
    Remember that you must also enable the useProtectiveAuras option, which is off by default!

    lockPair
    This is the list of blocks that will be locked in pairs if the lockpair setting is active.
    The default is chests and wooden doors, because of double chests and double doors.

    leftLock
    This bit is obsolete, as it stems from the time when you could still left-click doors to open them etc.

    lockVertical
    This is a list of blocks that have a natural "top" and "bottom" part. Currently, this is only doors, but who knows what might be relevant in the future. When a block listed here is locked SCL will search above and below it for it's other half and lock it as well, ignoring the lockpair setting.

    canSuck
    This section details what blocks will attempt to suck up items. In theory, any block with a container can suck up items (like a furnace), but only chests and dispensers have been tested, so use caution.
    If the lockedChestsSuck option is disabled, this section is entirely irrelevant.

    Default values:
    Code:
    lockables:
        lockable:
            - CHEST
            - DISPENSER
            - JUKEBOX
            - ENCHANTMENT_TABLE
            - BREWING_STAND
            - WORKBENCH
            - FURNACE
            - BURNING_FURNACE
            - LEVER
            - STONE_BUTTON
            - TRAP_DOOR
            - FENCE_GATE
            - STONE_PLATE
            - WOOD_PLATE
            - WOODEN_DOOR
            - BEACON
        protectiveAura:
            - CHEST
            - DISPENSER
        lockPair:
            - CHEST
            - WOODEN_DOOR
        lockVertical:
            - WOODEN_DOOR
        canSuck:
            - CHEST
            - DISPENSER
    So, what blocks can I make lockable?
    Short answer: Pretty much all of them.
    Long answer:
    It has to be a block bukkit knows of, and has a Material associated with.
    For a list of materials, have a look at the Material.java file in the Bukkit project on GitHub.

    Note that materials must be specified in UPPER CASE and otherwise exactly as Bukkit expects them!


    As of 1.0.2 you can also use numerical IDs, allowing custom blocks and stuff.
    Thanks go out to @albatrossen for that little fix.

    Trust system (open)

    In order to manage trust, you need the simplechestlock.command.trust permission!

    To add Bob to your trusted friends: /scl trust add bob
    To list your trusted friends: /scl trust list
    To remove Bob: /scl trust remove bob
    To clear the whole list: /scl trust clear
    To give access to everyone: /scl trust add *

    That last one, giving permission to *, is intended for just locking something so it's protected and can't be locked by anyone else. For example for an admin to lock the donation box to prevent it's destruction, but still have it open for people to put in donations.

    You can trust a whole group!
    Just /scl trust add g:dudes where "dudes" is the name of a group. Note that this isn't magic, it checks for the permission group.dudes, like how WorldGuard checks groups and as is emerging as a group check standard.

    Trust is in the locked item and persists there!
    This means that when you lock something, your current trust list is copied to the item, and stays there. If you want to modify an items trust you'll have to unlock it and lock it again with a new list. Changing your trust list will not alter already locked stuff.
    Perhaps you trust Bob to open that door, but not to access that chest? Perhaps you want * to activate that button, but not that switch?

    The trust lists get saved so you don't need to re-type it all the time. The downside, of course, is that you can get entangled in it and loose track. Just /scl trust clear to get out of that, or /scl trust list if you want to review who you'll trust for the next lock.

    Keep in mind that when you lock a chest for someone, using /scl as Bob for example, you are applying Bob's trust on the item. Keeping an up-to-date list of who he trusts is Bob's problem!

    You can combine combo-locking and trust just fine, and anyone not listed as trusted for that item will have to supply a valid combo.
    Configuration (open)

    Upon first run, the plugin will create plugins/SimpleChestLock/settings.yml
    Default values:
    Code:
    usePermissionsWhitelist: false
    checkUpdates: true
    whitelistMessage: true
    lockpair: true
    lockedChestsSuck: false
    suckRange: 3
    suckInterval: 100
    suckEffect: true
    verbose: false
    preventExplosions: true
    useProtectiveAuras: false
    key: 280
    keyDurability: 0
    comboKey: 352
    comboKeyDurability: 0
    useKeyDurability: false
    consumeKey: false
    openMessage: true
    useLimits: false
    lockLimits:
        example: 10
        anotherexample: 20
    lockables:
        lockable:
            - CHEST
            - DISPENSER
            - JUKEBOX
            - ENCHANTMENT_TABLE
            - BREWING_STAND
            - WORKBENCH
            - FURNACE
            - BURNING_FURNACE
            - LEVER
            - STONE_BUTTON
            - TRAP_DOOR
            - FENCE_GATE
            - STONE_PLATE
            - WOOD_PLATE
            - WOODEN_DOOR
            - BEACON
        protectiveAura:
            - CHEST
            - DISPENSER
        lockPair:
            - CHEST
            - WOODEN_DOOR
        lockVertical:
            - WOODEN_DOOR
        canSuck:
            - CHEST
            - DISPENSER
    usePermissionsWhitelist (boolean, default: false)
    true: Use permissions whitelist and players will only be able to lock blocks specially allowed by their beloved admin. See permission format and list of lockables to use above.
    false: All players can lock any of the lockable blocks.

    whitelistMessage (boolean, default: true)
    true: If a player attempts to lock a block he/she is not whitelisted for, a rather snappy red message is sent informing them of the error of their ways.
    false: If a player attempts to lock a block he/she is not whitelisted for nothing happens, not even a message, and certainly not any locking.

    lockpair (boolean, default: true)
    true: When locking one half of a double chest or double door, the other half is locked too.
    false: Each half is locked indevidually.

    lockedChestsSuck (boolean, default: true)
    true: Locked chests will attempt to "suck" objects in, causing them to disappear and go into the chest for storage. Intended for unattended farms, for example.
    false: Locked chests will leave everything alone, just as if it wasn't locked.
    Note that the sucking can be a little CPU-intensive on very large servers, so tune your suckRange and suckInterval (below) to suck shorter and less often if this gives you lag spikes.

    suckRange (meters, default: 3)
    Defines roughly the number of meters (blocks) away from a chest it will attempt to suck. This counts all directions in 3D, but with simplified math for performance, so it's not entirely accurate, but more than close enough.

    suckInterval (ticks, default: 100)
    Defines the number of ticks to wait between each suck attempt. Note that items must have existed at least one suckInterval before they can be sucked, so if your timing is exactly right you can have an item take exactly twice this time to get sucked in.
    On a well-tuned server there are 20 ticks per second, making the default a 5 second interval.

    suckEffect (boolean, default: true)
    true: When an item is moved from the ground to a chest, make a loud CLICK noise at the chest.
    false: OMGSTFU I CAN'T STAND THE CONSTANT CLICKING!!!!

    useWorldGuard (boolean, default: false)
    true: You need WorldGuard's build permission for the current region to lock stuff.
    false: WorldGuard is not consulted with regard to locking of blocks.

    verbose (boolean, default: false)
    true: The plugin will excessively inform you about all it's inner workings via the console.
    false: The plugin will keep it's console output to a minimum.
    Useful for tracking down problems, for example.

    checkUpdates (boolean, default: true)
    true: The plugin asks http://minecraft.webkonsept.com/plugins/ for the latest version of this plugin and tells you if the one you have isn't the newest release version.
    false: ET does not phone home.
    Note: The check happens when the plugin enables, meaning it only happens when you restart the server. If this is a popular feature I'll add a command to chek it as well.

    useProtectiveAuras (boolean, default: false)
    true: New blocks can not be placed next to locked ones.
    false: Only double-lockables are restricted in placement (old behavior).

    preventExplosions (boolean, default: true)
    true: The plugin will prevent explosions that would take out locked chests.
    false: Ignores explosions and just let them happen.
    Useful for when you have a different plugin protecting chests, or simply want people to be able to "blow the safe".

    useProtectiveAuras (boolean, default: false)
    true: The plugin will prevent the placement of any block right next to a locked block, unless you own that block.
    false: SCL does not meddle in the placement of blocks, meaning stuff like hoppers can be placed to extract items from locked chests.

    key and comboKey (item ID, defaults: 280 and 352)
    This is the item ID of your key. The defaults are Stick and Bone respectively.
    Use a listing like Minecraft Data Values to look up the ID of the item you want to use.

    useKeyDurability (boolean, default: false)
    true: Turn on durability checking (see below option)
    false: Turn the durability checking off.

    keyDurability and comboKeyDurability (damage value, default: 0)
    If your key is an item with multiple durability states, such as a custom Spout item or a sapling, you can use these settings to tune exactly what damage value you want to lock/unlock with.
    Does nothing unless useKeyDurability (above) is enabled.

    consumeKey (boolean, default: false)
    true: When you lock a block, the key disappears in payment of locking.
    false: Locking just locks, and does not eat the key.

    openMessage (boolean, default: true)
    true: A message is displayed when you open a chest, letting you know it's locked, who owns it (if it's not you) and who is trusted to access it besides you (if it's yours).
    false: Opening a chest you have access to gives no chat message.
    Note that regardless of this setting, a message is given if access was denied.

    useLimits (boolean, default: false)
    true: lockLimits as described in "Using limits" below are applied.
    false: all lockLimits are ignored and all users can lock whatever they please.

    lockLimits (configuration section, default is just an example)
    For details on this, please see then "Using limits" spoiler below.
    Using combinations (open)
    Combos are made of wool. To use them, set the first three items in your hotbar as wool. The combination is the colors of the wool.
    Use a bone (by default) to lock with that combination.

    If the setting openMessage is enabled, opening something you locked with a combination will show you the combo.
    To open something someone else locked with a combination you have to have three pieces of wool in the beginning of your hotbar. If you do, you're granted access as if you owned it, with no restrictions.
    If the combination is wrong, you'll be notified.
    Using limits (open)
    To use limits you have to use both permissions and options.
    First, let's have a look at the options.
    Code:
    lockLimits:
        example: 10
        anotherexample: 20
    Here, example and anotherexample are lock limit names.
    Keep an eye on these names when we move into the permissions.

    Remember that these permissions settings might not work with your permissions plugin, and is just an example.
    Code:
    users:
        someUser:
            permissions:
                simplechestlock.locklimit.example
        someOtherUser:
            permissions:
                simplechestlock.locklimit.anotherexample
      oneMoreUser:
            permissions:
                simplechestlock.locklimit.anotherexample
                simplechestlock.locklimit.example
        anAdmin:
            permissions:
                simplechestlock.nolocklimit
    Now someUser can lock 10 items, someOtherUser can lock 20 and oneMoreUser can lock 10 for example and 20 for anotherexample, for a total of 30.
    anAdmin can lock however much he/she wants, because of the nolocklimit permission.

    For details on the lockables section, see the "Configure lockables" above.


    Changelog:
    Version 1.2.2
    • Updated "Check for update" libs and compiled against newer bukkit.
    • Tested and found working very well with both 1.4.7 and 1.5.x
    Version 1.2.1
    • Removed some debug info output accidentally left in (right click entities message)
    Version 1.2
    • Optionally projects an "aura" around locked items. This is for stuff like Tekkit, so pipes can't be placed on chests to pump out the goodies inside.
    • Phones home to ask if there's a new version yet, so it can tell you when it's update time.
    • Some work done on entity protection, but nothing working yet.
    Version 1.1.1
    • (1.1.0 was never released due to bugs)
    • More consistent lockables checks
    • Performance improvements for lock checks
    • Explosion protection is now optional
    Version 1.0.2
    • albatrossen fixed invalid block IDs and added support for numerical IDs (both in "lockables" configuration)
    Version 1.0.1
    • Fixed where interacting with a combo-locked chest could generate a NullPointerException. Thanks to Wondrej for a detailed bug report making it easy to reproduce.
    Version 1.0.0
    • Option to check for WorldGuard build permission before allowing locking
    • Fix for item dupe bug if users are exceptional at item pickup timing and sucking is on
    • Fix for item consumption not happening if you have more than one in your hand.
    • Configurable locking, finally! You can now set what blocks are lockable!
    Version 0.20.1
    • Fixed bug where people could break blocks they didn't own.
    Version 0.20
    • Implemented group trust
    • Implemented key consumption
    • A good deal of cleanup internally, and some minor fixes.
    Version 0.19
    • Implemented suckInterval and suckEffect settings
    • Implemented whitelistMessage setting
    Version 0.18
    • Implemented limiting system so you can control how many items each user can lock
    • Made it possible to specify the durability ("Damage value") of keys, enabling the use of (for example) Spout custom items.
    (Older versions were stripped due to post size limitations)
     
  2. Offline

    DemmyDemon

    There is no whitelist file. Use permissions to define your whitelist on a per-user (or per-group) basis.
    Hence the name usePermissionsWhitelist in the configuration :)
     
  3. Offline

    Tomskied

    Urgh sorry, wasn't reading properly. Thanks for the reply and the delicious plugin :)
    Should the permisson be simplechestlock.lock.CHEST for only the ability to lock chest? Doesn't seem to be working for me
     
  4. Offline

    DemmyDemon

    You're very welcome.
    You'll need the simplechestlock.lock permission as well. I made them separate so you can set the lockables per group and give individuals the overall locking permission, or vice versa.

    If that doesn't help, enable verbose in the configuration to see why it's rejecting.
     
    Tomskied likes this.
  5. Offline

    Tomskied

    Brilliant, thanks again!
     
  6. Offline

    DemmyDemon

    I assume that means it worked? :)
     
    Tomskied likes this.
  7. Offline

    dark_messiah

    players on my server says its not working msg they save is : no permission!
    How to fix it? btw i dont have permissions and i dont want it.
     
  8. Offline

    DemmyDemon

    You have to make everyone a server operator, then...
    Perhaps I should set the default to "everyone can lock everything", but I don't quite like that...

    Why don't you want Permissions? Since Build 1000 and PermissionsBukkit, it's become stunningly easy to deal with, and grants excellent control.
     
  9. Offline

    Raycrash

    Is there an option to turn off all features except chest/door locking ?
     
  10. Offline

    DemmyDemon

    Turn on whitelisting, and only whitelist chests and doors.
     
  11. Offline

    Raycrash

    Thanks didnt see that xD

    Now installed on our server =)
     
  12. Offline

    DemmyDemon

    You're welcome.
    Hope it serves you well.
     
  13. Offline

    Codemunkie

    It's not working for me :( It says access is denied like it is suppose to but people can still access my items!
    I have every command as an admin, and the user testing the plugin is set as a default user with no commands.

    Am i doing something wrong? I'm fairly new to Bukkit and the permissions system.
     
  14. Offline

    DemmyDemon

    What exactly does it say? Perhaps you're getting access denied when locking, not when trying to access?
    I need the exact message, and what version you have of everything (Permissions[Bukkit], Bukkit, the lot)
     
  15. Offline

    Codemunkie

    I'm using Bukkit #1000 and Permissions v3.1.6 (Here).
    It works fine when i lock the chest or a button etc, but when my friend tries to access that chest, it says "Access denied for USERNAME'S chest". Although it still lets him in the chest and he can take things.

    On permissions, i have every command and i've used "--simplechestlock.ignoreowner" on my friends user.
     
  16. Offline

    DemmyDemon

    Okay then... Sounds like some other plugin might be messing with it.
    What else do you have?

    While I wait for that info, I'll look at the code to see where the conflict might be :)

    [Edit]
    Ohwait! What other permissions does he have? Is he an op?
     
  17. Offline

    Codemunkie

    I'm the only OP on the server. He's set as an admin on the groups which has every permission, but in his user i have the "-simplechestlock.ignoreowner" in the permissions to remove that permission.

    I'm running these plugins. World Guard, World Edit, CommandBook, Wireless Redstone, BananaChunk, VoxelSniper.
     
  18. Offline

    DemmyDemon

    Hmmm, I can't figure out what the problem is. I simply can't see it.
    Just to put my mind at ease, can you please share the permissions for this user, and the group he's in?
    Also, please turn on verbose in the settings, and get some log data on what happens when he opens a chest locked by someone else.

    Looks like the event isn't being properly cancelled...
     
  19. Offline

    Codemunkie

    I'm going on holiday for a week, but i'll be back to sort this problem. Hang tight until then! :D
     
  20. Offline

    DemmyDemon

    Roger on that.

    If anyone else has a similar problem, please speak up :)
     
  21. Offline

    JohnPulse

    Hi there!
    I'm having a small issue on Bukkit1000, and just want to know if it's "normal" and if possible a way to get over it.
    I'm getting about 10x this line on the log:
    If I get this right, it's telling me that a chest protected was destroyed. How can I identify it to remove this error? Even with verbose mode it seems that I can't see the location.
    Better yet, could't the plugin remove these type of lines from the Chests.txt when it detects air?
    Regards,
    John
     
  22. Offline

    DemmyDemon

    It does remove them, but the change is only saved when the next save cycle comes around, for example when a new block is locked. You can manually trigger a save with /sclsave.
    If you want the block world and xyz added to that logged line, then sure, I can do that, no problem.

    This problem happens when the locked block is removed by any other means than destroying it. For example by WorldEdit or similar.
     
  23. Offline

    JohnPulse

    Thanks for your feedback :)
    Yes, I think that the xyz coordenates would be useful.
    With this I can try to find out if it's a conflict with a WorldEdit move or another more serious problem.
    Thank you for this awesome plugin!
    Regards,
    John
     
  24. Offline

    DemmyDemon

    I'll be uploading 0.10.3 in a few minutes, where the error message is changed to something like

    AIR not a lockable block at World(world) X(23) Y(110) Z(-54)! DemmyDemon's block was moved or severe configuration change?

    Thank you for your support!

    [Edit]
    File is uploaded, editing OP
    [Edit again]
    Done. Enjoy to the extent possible.
     
  25. Offline

    Boman5

    I have the same problem.

    I lock a door, my friend opens it, the text he gets is Access denied, but the door(chest etc.) opens and he can go inside.
    When he locks a door I get the same message but I can't open it.

    I've set us both in the same permissionsgroup and deop both of us but it's still the same, he can open everything while I can't open his stuff.
     
  26. Offline

    DemmyDemon

    Okay, very strange.
    Can you give me his full effective permissions, and both of your names, please?
    It uses your in-game-name to determine ownership.
    Since it IS denying, it is working right, but then the "open event" is not being cancelled.

    ...or some other plugin is un-canceling it, so please include a list of all loaded plugins as well.
     
  27. Offline

    Boman5

    The permissions group he is in. (I'm actually just setting up permissions, since I switched for a new permissions plugin)

    My name is Boman5 and his name is sexpress

    All the plugins are not set in permissions yet, got stuck at trying to get simplechestlock to work, I've tried another plugin before called ChestLock, had the exact same problem then.
    I'm using Bukkit#1000
     
  28. Offline

    DemmyDemon

    Okay, there's my theory of name similarity out the window.

    I'm left with the theory that some other plugin is causing this by "uncancelling" the event.
    As to which one it is, I have no idea. If the list from the previous guy with the same problem is complete (which I'm starting to doubt) the most likely culprit is ... VoxelSniper.

    That makes no sense at all.

    I guess I could bump up the priority of the events, and see if that helps, but that's a pretty damn rough solution.
    If you have the time, will you please help me out?
    Can you remove all the plugins except PermissionsEX and SimpleChestLock, but keep everything else the way it is, and see if it works?
    If it does, add plugins back one at a time until it breaks?

    I tried installing all those and approximating your setup on my test server, but I could not reproduce the issue. If I could narrow it down to one or two candidates, however, it becomes a much simpler problem to fix.
     
  29. Offline

    Boman5

    Actually I don't think it's your plugin that caused any problem. I did what you wanted, removed all the plugins and added them back one by one. when I added all the plugins and it was working. bu the folder where I used to have my plugins hade a few .zip lefts and some other files... So I guess it had to do with this.

    Thank you for your help!
     
  30. Offline

    DemmyDemon

    You're very welcome.
    I'm just stumped that it worked out that way.

    Oh well.. Enjoy :)
     
  31. Offline

    Mathew Alden

    Are you still thinking about doing this?
     

Share This Page