[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

    travja

    I am using permissionsbukkit if that makes a difference

    Still not working. Is this plugin updated to 1.1 or still with 1.0?
    I am using a 1.0 sever

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

    DemmyDemon

    Neither one makes any difference as it uses Bukkit's built-in permissions handling

    Are you reloading the permissions in between, and the user is logging out and back in?
     
  4. Offline

    travja

    just reloading

    tried deoping and it didn't work after that and gave the same error as before.

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

    DemmyDemon

    What about after logging out and back in?
    Yes, I realize you're not supposed to have to do that, but I've found it sometimes helps.
    What are the permissions for that user now?
     
  6. Offline

    travja

    After logging back in it did the same thing. The permissions are just
    - simplechestlock.*
    - simplechestlock.lock
    - -simplechestlock.ignoreowner

    And that is just in the groups .yml file

    Do I need to put these permissions in the users.yml file?

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

    DemmyDemon

    Haven't you read what I wrote?
    You need to give simplechestlock.locktype.*
    But let me get this straight... You've given simplechestlock.lock, but verbose mode says permission denied on that exact permission?
    Then I fear the problem is in your permissions plugin, and not in my code :-/
    That shouldn't matter at all.
     
  8. Offline

    travja

    Yes sorry, I put simplechestlock.locktype.* and yes I have simplechestlock.lock and yes it gives the error... The thing I don't get is I am using permissionsbukkit which you said should work.

    And I think I know the problem... I don't actually have permissionsBukkit, I have permissions by TheYeti

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

    DemmyDemon

    ... that changes everything.
    What version of Permissions? Does it support Superperms?
     
  10. Offline

    travja

    Just installed PermissionsBukkit and everything is working perfectly with the new permissions. Thanks for sticking with me through all of my troubles. Derp! Everything works. I have had problems with other plugins not doing the right thing before... now I have the default permissions and EVERYTHING that I want works.

    EDIT: No need to fear PermissionsBukkit is here!
     
  11. Offline

    DemmyDemon

    Glad to hear you got it going! :D
     
  12. Offline

    Howsn

    Hello and thanks for this awsome plugin! :) the only problem I have with this plugin right now, is that everyone can lock a door that is not locked yet. Same with chest and everything els.. Is there something I can edit so only the player who placed the block can lock it? what I mean is if I want to leave a door open so everyone can use it but not å random player to lock it. I hope you understand this, sorry for my bad english.

    Thanks :)
     
  13. Offline

    DemmyDemon

    Yes, I understand perfectly.
    Tracking who placed a block is not trivial. There are entire huge plugins dedicated to doing that and only that.
    The way I've solved the problem of people locking other people's stuff on my server is to punish the person that locked it for griefing/abuse/shenanigans. That put a stop to it within a few hours.
    Since it's plain who did it by the name on the door, finding the culprit is trivial.
     
  14. Offline

    Howsn

    I understand. thank you so mutch for a fast reply :)
     
  15. Offline

    DemmyDemon

    No problem, I hope it works out for you.
     
  16. Offline

    rossi37

    Hi, I installed your plugin and i think it's really nice, but it does not work on my server.
    Whenever I hit a chest it says: ' You can't lock or unlock blocks! Permission denied.'
    Maybe you can help me. Excuse my bad English please. :)

    Code:
    20:26:21 [INFO] [SimpleChestLock 0.13.1 VERBOSE] Done reading protected location
    s!
    20:26:21 [INFO] [SimpleChestLock 0.13.1] Enabled!
    20:26:21 [INFO] Server permissions file permissions.yml is empty, ignoring it
    20:26:21 [INFO] Done (4,401s)! For help, type "help" or "?"
    20:26:48 [INFO] rossi37 [/5.157.193.59:3796] logged in with entity id 91 at ([HP
    -Minecraft] 62.91350883003446, 66.0, 427.56443845665393)
    20:26:51 [INFO] [SimpleChestLock 0.13.1 VERBOSE] Permission denied: rossi37->(si
    mplechestlock.lock)

    this is my permissions: groups.yml
    Code:
    groups:
        Gast:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: false
            permissions:
                - essentials.help
                - essentials.info
                - essentials.rules
        Builder:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Gast
            permissions:
                - 'warpplugin.warp'
                - 'econplugin.basic.*'
                - essentials.afk
                - essentials.mail
                - essentials.mail.send
                - essentials.suicide
                - essentials.spawn
                - essentials.sethome
                - essentials.delhome
                - essentials.ignore
                - essentials.home
                - foodfiller.food
                - foodfiller.freeze
                - simplechestlock.locktype.*
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Builder
            permissions:
                - essentials.afk.others
                - essentials.ban
                - essentials.unban
                - essentials.kick
                - essentials.tpohere
        Admin:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Moderator
            permissions:
                - '*'
                - essentials.setspawn
                - simplechestlock.command.*
     
  17. Offline

    DemmyDemon


    You haven't given the correct permission.
    You need to give simplechestlock.lock permission. The locktype permission is for the permissions-based whitelisting (if enabled).
     
  18. Offline

    rossi37

    It doesn't work anyway :(
     
  19. Offline

    DemmyDemon

    What permissions system are you using?
     
  20. Offline

    Kurai Ookami

    so I have an issue, I'm not completely sure how the whitelist works. I've enabled it in simplchestlock's config file. but every time anyone who is in my user group attempts to lock something it says they don't have the permission to do so. right now this is what my permissions look like.
    Code:
    users:
     
    ConspiracyWizard:
     
    permissions:
     
    permissions.example: true
     
    groups:
     
    - admin
     
    ryudanx:
     
    groups:
     
    - user
     
    dkl5r:
     
    groups:
     
    - user
     
    kurai_ookami:
     
    groups:
     
    - admin
     
    altereego
     
    groups:
     
    - user
     
    groups:
     
    default:
     
    permissions:
     
    permissions.build: false
     
    admin:
     
    permissions:
     
    permissions.*: true
     
    simplechestlock.*: true
     
    worlds:
     
    creative: {}
     
    world:
     
    launchme.cannon: true
     
    launchme.teleporter: true
     
    world_nether:
     
    launchme.teleporter: true
     
    inheritance:
     
    - user
     
    user:
     
    permissions:
     
    expminer.use: true
     
    permissions.build: true
     
    simplechestlock.lock: true
     
    simplechestlock.locktype.chest: true
     
    simplechestlock.locktype.trap_door: true
     
    simplechestlock.locktype.wooden_door: true
     
    simplechestlock.usecombo: true
     
    inheritance:
     
    - default
     
    messages:
     
    build: '&cYou do not have permission to build here.'
    I've also tried it without the simplechestlock.lock: true line and no difference
     
  21. Offline

    DemmyDemon

    I'm very confused by this. Is this what your actual permissions file looks like? This is not valid YAML at all.
    What permissions manager is this?
    Also, please include your simplechestlock config.yml so I can see how it's set up.
     
  22. Offline

    Kurai Ookami

    PermissionsBukkit 1.1 it's only a slightly modified version of the default. I copy and pasted from notepad ++ which is what I use to edit it. the spacing pasted is a bit off but otherwise it's the same and all of the other plug-ins and permissions function. Also my file is labeled simply as a YML not YAML not sure if that matters or not but it's how it built itself.
     
  23. Offline

    DemmyDemon

    The spacing being "a bit off" means I have no way to check if the YAML is valid, and no way to use "your" YAML on my test server to reproduce the problem.

    You also forgot to share your config.yml. Please do so.
     
  24. Offline

    Kurai Ookami

    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
        ryudanx:
            groups:
            - user
        dkl5r:
            groups:
            - user
        kurai_ookami:
            groups:
            - admin
        altereego
            groups:
            - user
         
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                simplechestlock.*: true
            worlds:
                creative: {}
                world:
                    launchme.cannon: true
                    launchme.teleporter: true
                world_nether:
                    launchme.teleporter: true
            inheritance:
            - user
        user:
            permissions:
                expminer.use: true
                permissions.build: true
                simplechestlock.locktype.chest: true
                simplechestlock.locktype.trap_door: true
                simplechestlock.locktype.wooden_door: true
                simplechestlock.usecombo: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
    Code:
    usePermissionsWhitelist: true
    lockpair: false
    lockedChestsSuck: false
    verbose: false
    comboKey: 352
    suckRange: 3
    key: 280
    
    I hope this helps, and thanks for your time
     
  25. Offline

    DemmyDemon

    No problem, I'll do what I can to assist, of course.

    You have to give simplechestlock.lock. Without it, it never even checks the locktypes.
    If that still doesn't work, please set "verbose: true" in config.yml and tell me what it says in console or log when you try to lock something.
     
  26. Offline

    Kurai Ookami

    okay I attempted adding that permission in both cases I got
    Code:
    [INFO] [SimpleChestLock 0.13.1 VERBOSE] Permission denied: DKL5R->(simplechestlock.lock)
    
    also when I reloaded permissions I recieved
    Code:
    13:49:56 [INFO] [PermissionsBukkit] Loading PermissionsBukkit v1.1.
    2012-01-26 13:49:56 [SEVERE] Error occurred while enabling PermissionsBukkit v1.1 (Is it up to date?)
     
  27. Offline

    DemmyDemon

    Seems to me you have problems with PermissionsBukkit. Invalid YAML? If the YAML you actually use is anything like what you pasted, there is a colon missing after alter "altereego".

    I suggest you validate your YAML using an online YAML parser.

    Until PermissionsBukkit is happy there is no way simplechestlock can use any permissions at all.
     
  28. Offline

    Kurai Ookami

    awesome fixed all the punctuation errors and it works fine now, thank you very much.
     
  29. Offline

    DemmyDemon

    Glad to be of assistance :)
     
  30. Offline

    DCBSupafly

    I use Essentials Group Manager for my permissions. In the past it has worked with your plugin, but do I understand that I need something else or something different now?

    All other users are now unable to lock/unlock, though they can access old locked chests. I, the admin, also have the ability to lock/unlock. Users first reported the error msg to me soon after upgrading to 1.1.1 (was using a dev build of bukkit, now using the recommended). I also installed Multiverse 2 at that time, but I don't believe it's causing the error as the rest of my permissions work in each world.
     
  31. Offline

    DemmyDemon

    I really don't know if Essentuals Group Manager implements SuperPerms or not.
    If it doesn't, then you need to get yourself a Permissions handler that is still compatible with the way things work in Bukkit now.
    If it does, then there's some kind of misunderstanding here, and I need to know...
    • What is "the error message"?
    • What permissions do the relevant users have?
    • What does your simplechestlock config.yml look like?
    • What version did you upgrade from? (Not essential, but if you upgraded from something really old that might be a little troublesome)
     

Share This Page