[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

    You're welcome, but did it work? Every fire put out?
     
  3. Offline

    Kurai Ookami

    yeah so far seems to be running perfect, people can lock, unlock and use trust functions. Thanks
     
  4. Offline

    DemmyDemon

    Good to hear, and you're very welcome. Thanks for your feedback!
     
  5. Offline

    milligannn

    Hi,
    This is my first plugin for bukkit and I'm not really understanding permissions. How can I allow everyone to lock chests and doors without making them op? At the moment only ops can lock chests and doors. If someone could tell me how to sort this out or link me to somewhere I can learn about how to fix this then I would be very greatful.
    Thanks
     
  6. Offline

    DemmyDemon

    You need a permissions manager plugin, like bPermissions or PermissionsEx, to manage the permissions for you.
    Please note that any issues or questions related to setting up a permissions manager should be directed at them, and not raised here.

    Thank you.
     
  7. Offline

    Gilbertus

    I have problem with PermissionsEx and SimpleChestLock combination.
    All door, chest, furnaces, etc. are not accessible by default. Its caused by SimpleChestLock permission simplechestlock.limited "If given, denies access to anything but items locked in your name". Since stuff don't have owner by default in SimpleChestLock they cannot be use any more. The problem is that happens even if there completely no SimpleChestLock permission given. PEX wrongly finds simplechestlock.* somehow. This is log from debug mode:
    Code:
    2012-02-12 01:13:31 [INFO] User Gilbertus checked for "simplechestlock.*", no permission found
    2012-02-12 01:13:31 [INFO] User Gilbertus checked for "simplechestlock.limited" = true,  found from "simplechestlock.*"
    2012-02-12 01:13:31 [INFO] User Gilbertus checked for "simplechestlock.ignoreowner" = false,  found from "simplechestlock.*"
    I don't know if this is PermissionsEx or SimpleChestLock bug. I have to explicitly give (negative) -simplechestlock.limited to everybody so they can use any non-locked stuff.
    To reproduce you can just make clean bukkit 1.1-R3 install, log in, craft some chest and door. Then install both plugins PermissionsEx (PEX) v1.18 and SimpleChestLock 0.15.3, no changes in config needed. After this try to open chest and door. Note the misspelled "thigs" in message that SimpleChestLock produce.

    Could you please look at this problem?
     
  8. Offline

    DemmyDemon

    This is a PEX bug.
    SimpleChestLock defines simplechestlock.* as...
    Code:
        simplechestlock.*:
            description: Full access
            children:
                simplechestlock.command.*: true
                simplechestlock.ignoreowner: true
                simplechestlock.locktype.*: true
                simplechestlock.lock: true
                simplechestlock.usecombo: true
                simplechestlock.limited: false
    Note the "false" at the very end.

    Also, what version of PEx? I run it and don't have this problem, except with my "Admin" group that has the '*' permission, which is inelegantly implemented, so I had to give the negative permission.
    [edit]Errr, you said 1.18! I run 1.17 and the changes are minimal. I have no idea what's going on, but I'm positive it's a PEx bug![/edit]

    Besides, with PEx you have to get used to little workarounds like scattering negative permissions here and there. I feel this is okay, seeing as it's pretty good in most other respects.
     
  9. Got a problem , all of my friend can access everything I lock.
    which perm do I need if I not wan't to let them in others chest ?
    I've tested some but it still don't work :/
     
  10. Offline

    DemmyDemon

    Either they have simplechestlock.ignoreowner, or you have included them in your trust list, or you have some other plugin giving access to chests.
     
  11. Offline

    Gilbertus

    I see. So even if I give simplechestlock.* to user he shouldn't have problems.
    One thing is why PEX states that user have permission I didn't give (note that in first line it says user don't have it, and in second line it says that simplechestlock.limited is found from it).
    Second thing is that simplechestlock.* shouldn't give simplechestlock.limited at all. It seems that PEX overwrite * and give all child nodes.
    I will submit this bug to PEX creator.

    Thanks for answer.
    BTW Great plugin.
     
  12. Offline

    DemmyDemon

    Yes, PEX treats * as a magic character even when it's pre-defined, which is (in my opinion) a bug.
    Of course, I could change permissions around so it's simplechestlock.all (or whatever) in stead, but how many are already using the "old" way? That burned me a bit when I switched the whitelisting stuff over, so I'm leaving it as-is.

    Oh, and you're very welcome. Hope it serves you well.
     
  13. I've given them the "-simplechestlock.ignoreowner" and I've especially not placed them in the trustlist when I locked the chest/door/button .
    I'm going to check the other plugins or if you wan't I can send you a copy of my "mysql" permissions ? Just joke I can send you text file of the permissions but I've to make the output-file first. Just to look the commands for PEX :D
     
  14. Offline

    DemmyDemon

    If you have to :(
    I'll also need a list of your plugins and a complete list of what you have already tried to remedy the situation.
    I want a verbose: true log of what happens as well.
     
  15. Offline

    KlixTurner

    PEX Version: 1.18
    SimpleChestLock v0.15.3

    Problem:
    Permissions set (tried several things, always the same).
    When enter the World, at all doors,furnace etc. the message "You can only open thigs that belong to you" will display.
    I want only, that each player locked his chest.

    How can i solve the problem, that standard not all doors,furnace etc. affected and the message displayed ?

    Thanks for any help. :)
     
  16. Offline

    DemmyDemon

    I don't understand why this is still a problem :(
    Exactly what permissions do you have?

    Yes, you already said that!
    Answer my questions, or I can't help you!

    Exactly what permissions do you have?

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

    KlixTurner

    Just realized that probably the permissions.yml the problem is. Sorry for the inconvenience.:oops:
     
  18. All my plugins :
    Orebfuscator, AutoItemBarReload, CreeperHeal, WorldEdit, SpongeRestore, HelpCraft, ShiftMode, NoLagg, SimpleChestLock, AcceptRules, Vault, PermissionsEx, BanHammer, ExpBank, ChatManager, Permissions, AdminCmd, Modifyworld, dynmap

    Permissions:
    Take note of the inheritance!
    Perms

    users:
    ferretsrule:
    group:
    - Co-Owner
    options:
    last-login-time: '1328723511'
    last-logout-time: '1328723505'
    Mansnitor:
    group:
    - Admin
    options:
    last-login-time: '1329059603'
    last-logout-time: '1329060108'
    tvilig456:
    group:
    - Co-Owner
    options:
    last-login-time: '1329237336'
    last-logout-time: '1329237604'
    coolcomputerguy:
    group:
    - Noobie
    options:
    group: Admin
    Osky2918:
    permissions:
    - admincmd.player.spymsg
    group:
    - Owner
    options:
    last-login-time: '1329237226'
    last-logout-time: '1329237970'
    Kebabmaskinen:
    group:
    - Co-Owner
    options:
    last-login-time: '1329236130'
    last-logout-time: '1329237840'
    Muxinator:
    group:
    - Co-Owner
    options:
    last-login-time: '1328552449'
    last-logout-time: '1328552470'
    wired2000:
    group:
    - Admin
    options:
    last-login-time: '1329060068'
    last-logout-time: '1329060071'
    Willepille04:
    group:
    - Co-Owner
    options:
    last-login-time: '1329153888'
    last-logout-time: '1329154079'
    Toarullen:
    group:
    - Co-Owner
    options:
    last-login-time: '1328720584'
    last-logout-time: '1328721984'
    samsala27:
    group:
    - Noobie
    options:
    last-login-time: '1328723623'
    last-logout-time: '1328723742'
    groups:
    Owner:
    prefix: '&4'
    permissions:
    - -simplechestlock.limited
    - simplechestlock.command.trust
    - '*'
    options:
    rank: '0'
    Op:
    prefix: '&b'
    permissions:
    - admincmd.tp.players
    - admincmd.warp.create
    - CreeperHeal.heal
    - chatmanager.chat.color
    - chatmanager.chat.global
    inheritance:
    - Moderator
    options:
    rank: '100'
    Co-Owner:
    prefix: '&1'
    permissions:
    - simplechestlock.command.as
    - spongerestore.*
    inheritance:
    - Admin
    options:
    rank: '0'
    Noobie:
    default: true
    prefix: '&2'
    permissions:
    - Help.user.*
    - admincmd.player.afk
    - admincmd.player.list
    - admincmd.tp.home
    - admincmd.tp.back
    - admincmd.tp.to
    - admincmd.tp.toggle.allow
    - admincmd.server.rules
    - admincmd.server.news
    - admincmd.server.motd
    - admincmd.server.help
    - admincmd.spawn.tp
    - motd.rtp.request
    - motd.rtp.yes
    - motd.who.use
    - motd.vtime.use
    - motd.motd.use
    - -simplechestlock.ignoreowner
    - simplechestlock.locktype.*
    - simplechestlock.command.trust
    - modifyworld.*
    options:
    rank: '1000'
    Builder:
    prefix: '&6'
    permissions:
    - simplechestlock.command.status
    - simplechestlock.command.trust
    - expbank.use
    - admincmd.player.ip
    - admincmd.player.msg
    - admincmd.player.loc
    - admincmd.warp.tp
    - simplechestlock.usecombo
    - deathtpplus.tomb.create
    - deathtpplus.tombstone.*
    - deathtpplus.deathtp.*
    inheritance:
    - Noobie
    options:
    rank: '900'
    Moderator:
    prefix: '&9'
    permissions:
    - admincmd.player.invisible
    - admincmd.player.loc.other
    - admincmd.tp.toggle.*
    - CreeperHeal.trap.remove.own
    - CreeperHeal.trap.create
    inheritance:
    - Builder
    options:
    rank: '500'
    Admin:
    prefix: '&c'
    permissions:
    - Help.user.*
    - simplechestlock.command.status
    - simplechestlock.command.trust
    - expbank.use
    - admincmd.player.afk
    - admincmd.player.invisible
    - admincmd.player.mute
    - admincmd.player.ip.other
    - admincmd.player.ip
    - admincmd.player.msg
    - admincmd.player.kick
    - admincmd.player.loc.other
    - admincmd.player.loc
    - admincmd.player.invisible.other
    - admincmd.player.freeze
    - admincmd.player.ban
    - admincmd.player.list
    - admincmd.warp.*
    - admincmd.server.motd
    - admincmd.server.news
    - admincmd.server.rules
    - admincmd.server.help
    - admincmd.spawn.tp
    - admincmd.time.day
    - admincmd.time.set
    - admincmd.tp.home
    - admincmd.tp.toggle.*
    - admincmd.tp.back
    - admincmd.tp.see
    - admincmd.tp.locations
    - admincmd.tp.player
    - admincmd.tp.from
    - admincmd.weather.rain
    - admincmd.weather.storm
    - admincmd.weather.clear
    - admincmd.tp.to
    - motd.motd.use
    - motd.vtime.use
    - motd.rtp.request
    - motd.rtp.yes
    - motd.who.use
    - motd.ip.use
    - -simplechestlock.ignoreowner
    - CreeperHeal.trap.remove.own
    - CreeperHeal.trap.create
    - CreeperHeal.heal
    - simplechestlock.locktype.*
    - simplechestlock.usecombo
    - acceptrules.notifyonaccept
    - deathtpplus.tomb.*
    - deathtpplus.tombstone.*
    - deathtpplus.deathtp.*
    - chatmanager.override.ranged
    - chatmanager.chat.color
    - chatmanager.chat.global
    - modifyworld.*
    options:
    rank: '0'


    I've tried some of the "lock" node but none of them work :/

    Here is the verbose on startup / reload.

    Verbose/on startup


    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Loading trust relations from config
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] 1 people have registered trust
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Parsing truster osky2918
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] -> tvilig456
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Reading locks from /home/oskar/MC/plugins/SimpleChestLock /Chests.txt
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1020.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1021.0) Y(76.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1019.0) Y(76.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(72.0) Z(198.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1023.0) Y(63.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1024.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1018.0) Y(76.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1011.0) Y(59.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1021.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(ferretsrule) Wo rld(CraftWorld{name=Epic_World}) X(936.0) Y(64.0) Z(246.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1030.0) Y(60.0) Z(195.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1024.0) Y(63.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(76.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1020.0) Y(75.0) Z(192.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1020.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1026.0) Y(63.0) Z(196.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1018.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(62.0) Z(204.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1154.0) Y(11.0) Z(400.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1019.0) Y(76.0) Z(196.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1024.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1023.0) Y(75.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1017.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(ferretsrule) Wo rld(CraftWorld{name=Epic_World}) X(930.0) Y(64.0) Z(232.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(ferretsrule) Wo rld(CraftWorld{name=Epic_World}) X(935.0) Y(64.0) Z(244.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1024.0) Y(64.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1030.0) Y(62.0) Z(205.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1019.0) Y(75.0) Z(196.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1019.0) Y(75.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1030.0) Y(60.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1023.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1013.0) Y(60.0) Z(209.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1021.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1020.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1026.0) Y(63.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1017.0) Y(58.0) Z(191.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1013.0) Y(64.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1024.0) Y(75.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(76.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1031.0) Y(62.0) Z(203.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1011.0) Y(59.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1018.0) Y(75.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1018.0) Y(75.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1015.0) Y(60.0) Z(209.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1153.0) Y(11.0) Z(400.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(ferretsrule) Wo rld(CraftWorld{name=Epic_World}) X(934.0) Y(64.0) Z(244.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1030.0) Y(62.0) Z(203.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(63.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1015.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1011.0) Y(59.0) Z(198.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1020.0) Y(75.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1014.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1021.0) Y(64.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1023.0) Y(75.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(ferretsrule) Wo rld(CraftWorld{name=Epic_World}) X(936.0) Y(64.0) Z(245.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1014.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(75.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(75.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1022.0) Y(63.0) Z(199.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1031.0) Y(62.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(64.0) Z(194.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1015.0) Y(64.0) Z(193.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(77.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1018.0) Y(58.0) Z(191.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1019.0) Y(75.0) Z(197.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(tvilig456) Worl d(CraftWorld{name=Epic_World}) X(1022.0) Y(75.0) Z(192.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1025.0) Y(71.0) Z(198.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1026.0) Y(63.0) Z(198.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1030.0) Y(62.0) Z(200.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Added location to protection list: Player(Osky2918) World (CraftWorld{name=Epic_World}) X(1013.0) Y(64.0) Z(198.0)
    20:31:07 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Done reading protected locations!


    And the verbose of when a user not on my "trust-list" open my chest:
    My friend in this example I've given him the perm "-simplechestlock.ignoreowner"
    But the verboes say that I gave him "simplechestlock.ignoreowner".
    It maybe is something with the inheritance.
    Otherwise I give him "-simplechestlock.ignoreowner" individual instead of by group.

    Verbose/in game


    tvilig456 wants to use Osky2918's chest
    20:42:00 [INFO] [SimpleChestLock 0.15.3 VERBOSE] Permission granted: tvilig456->(simplechestlock.ignoreowner)
    20:42:00 [INFO] [SimpleChestLock 0.15.3 VERBOSE] This block is locked with a normal key
    20:42:00 [INFO] [SimpleChestLock 0.15.3 VERBOSE] tvilig456 was let into Osky2918's chest, ignoring owner.
     
  19. Offline

    DemmyDemon

    Well, why are you giving them '-simplechestlock.ignoreowner'?
    That is only automatically given if a player is op, or you give the simplechestlock.* permission.

    I'm having a REALLY hard time reading your permissions, on account of you posting it all flat.
    Please use a [ code ] tag so the indentation is preserved.


    What I've been able to peice together, including inheritance and all, is that tvilig456 has the following permissions:


    - -simplechestlock.ignoreowner
    - simplechestlock.command.as
    - simplechestlock.command.status
    - simplechestlock.command.trust
    - simplechestlock.locktype.*
    - simplechestlock.usecombo
    Still, permission simplechestlock.ignoreowner is granted. This, I believe, is somehow a PEX bug.
    tvilig456 is checked for the "simplechestlock.ignoreowner" permission, which is set as "ops only" in my plugin.yml, and you have specifically removed it yourself. Why then would PEX give it?
    Are you absolutely sure that tvilig456 is not listed in ops.txt?
    Have you talked to the PEX creator, or opened a ticket there?
    There really is nothing more I can do when PEX returns true when it should return false. I can program a lot of stuff, but I can't make my plugin psychic.

    It would help me a lot if you would please share what the problem was and how you solved it.
    Others would benefit from your solution.

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

    der_robert

    Hello,

    I have a problem with SCL in conjunction with iConomy Chest Store.

    And indeed, when I close a Chest with SCL (which works fine) and a "Chest Shop" sign next to add, I can open it as a non-owner of the Chest.

    My question is, this is a "problem" of SCL or "Chest Shop" or both?

    I use CB1.1-R4 with a few plug-and, of course, SCL and iConomy + "Chest Store".

    Robert
     
  21. Offline

    DemmyDemon

    This is iConomy Chest Shop or Chest Store or whatever it's called (you don't seem sure?) overriding the chest opening event. If you turn on verbose mode you'll likely see SCL denying access.
    This plugin probably has it's own chest protection scheme which overrides SCL.
     
  22. Offline

    KlixTurner

    It was not due to the permissions.yml. With LWC Plugin it works.
    I have the permission "simplechestlock.lock". But it is somehow as and what also identical that problem is always the same. Even without a permission node, it is always the same.
     
  23. Offline

    DemmyDemon

    Never mind. I have no idea what you just said.
     
  24. Thanks for the info! I forget that "code" tag when I did the "spoiler" tag.
    It's not realy easy to see everthing through when youre tired of confusing.
    I'm going to remove the node from him and check "op.txt"
    Overwise I went to PEX .
     
  25. Offline

    DemmyDemon

    Best of luck to you.
     
  26. Just a fast ask : I've removed them from op.txt and removed the negative node so it should work right ?
    If not I'm in search for nodes , I know where to find them !
    I have tested without just op.txt and they start complain about they could not lock at all .
    I have not tested no after removing the node , it's made tomorrow :p
     
  27. Offline

    DemmyDemon

    You're telling me this person was in ops.txt?
    Seriously?

    Gah.

    Okay, remove the player from there, and then --RESTART THE SERVER-- to be sure he's no longer considered an op by any part of the server. The ops system and it's impact on permissions is sketchy at best.
     
  28. Offline

    Captain Seasick

    Right... I'm gonna sound like a douche for saying this, but this plugin is terrible! The trust system is extremely broken, the permissions system doesn't work at all. I'm probably doing something wrong, but all in all, this plugin has caused way more damage than it prevented!
     
  29. Offline

    ACStache

    if you're doing something wrong, ask for help before saying it sucks/is terrible :p
    It works wonders when it's set up right :)
     
  30. Offline

    Jaein

    The /scl trusted works wonders and it's so convenient. No more sharing a half door with someone :) Nice job with the plugin
     
  31. Offline

    DemmyDemon

    Then I suggest you use a psychic plugin that can figure out what you want by ways of telepathy rather than configuration.
    Just don't come back later for support, mm-kay?

    I could not have said it better myself.

    Thank you.

    I just have to comment on your server's name... LotionMotion sounds like a massage parlor that offers happy endings :D Probably just my dirty mind playing up :p

    [edit]
    I stopped by LotionMotion and got a problem report from one of your users.
    If a pressure pad is locked it will spam like crazy if you step on it.

    I'm writing a throttler that will only send one message every three seconds.
     

Share This Page