Another Permissions Problem

Discussion in 'Bukkit Help' started by Ethan, May 15, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    Ethan

    I just downloaded Permissions v 2.7.3 and it won't let anyone place and break anything, anywhere in the server.

    Code:
    # System is no longer used, but may become used in the future
    # Copies is for multiple-world support
    #   Put the name of the world you wish for it to be a clone of, otherwise leave it empty.
    #   If this file is for your default world (the one in server.properties) then you must
    #   leave copies blank.
    #  Example: copies: Derp    -  This will clone the permissions of the world Derp
    #
    # Make sure to rename this file to the name of the world that is in sever.properties under
    # level-name.  So if it is level-name: world  then this should be world.yml and in the
    # plugins/Permissions directory (ie. plugins/Permissions/world.yml)
    #
    # NOTE: Do not use tabs while editing this document.  Use only spaces.  A good way to avoid
    # doing this is to use Notepad++ and replace the tab with 4 spaces.
    plugin:
        permissions:
            system: default
            copies:
    
    ##
    # AntiBuild is included with this.  To disable a group from being able to build then
    # set the build: flag to false (build: false).  If you want a group to be able to build
    # then set it to true.
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another
    #   group simply place the groups name in the "inheritance:" like so:
    #
    #   Example:
    #       inheritance:
    #           - Default
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'foo.bar'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'foo.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    #   If you give a group this permissions, do not have the group inherit any permissions
    #   from other groups.  Any users assigned to this group should NOT be given any additional
    #   permissions either.
    ##
    #   To exempt a node use the - prefix like so:
    #       - '-foo.bar'
    ##
    #   prefix: and suffix: do not do anything on their own.  You need another outside plugin
    #   such as iChat or HeroChat in order for these to do anything.
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: false
            inheritance:
            permissions:
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'bar.foo'
        Admins:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Moderator
            permissions:
                - '*'
    
    ##
    # Users denote which users are included in which group.
    # TheNo1Yeti is in the Admin group
    # Herpina is a member of the Moderator group but also has access
    # to the herp.derp permissions
    # Derpina is a member of the admin group but does not have access
    # to the derp.derp permission node
    # Users can also have a prefix and suffix as seen with Herpina
    ##
    users:
        TheNo1Yeti:
            group: Admins
            permissions:
        Herpina:
            group: Moderator
            info:
                prefix: 'Moo'
                suffix: 'Cow'
            permissions:
                - 'herp.derp'
        Derpina:
            group: Admins
            permissions:
                - '-derp.derp'
    Code:
    [Lnet.minecraft.server.Statistic;@131f71a
    146 recipes
    [Lnet.minecraft.server.Statistic;@131f71a
    16 achievements
    16:11:31 [INFO] Starting minecraft server version Beta 1.5_02
    16:11:31 [WARNING] **** NOT ENOUGH RAM!
    16:11:31 [WARNING] To start the server with more ram, launch it as "java -Xmx102
    4M -Xms1024M -jar minecraft_server.jar"
    16:11:31 [INFO] Loading properties
    16:11:31 [INFO] Starting Minecraft server on *:25565
    16:11:31 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-729-
    g5ee3f0f-b766jnks (MC: 1.5_02)
    16:11:31 [INFO] Preparing level "Town"
    16:11:31 [INFO] Preparing start region
    16:11:32 [INFO] Preparing spawn area: 85%
    16:11:33 [INFO] [Permissions] (Phoenix) was Initialized.
    16:11:33 [INFO] Loaded Essentials build 2.2.17 by Zenexer, ementalo, Aelux, Bret
    tflan, KimKandor, snowleo, ceulemans and Xeology
    16:11:33 [INFO] [iConomy] Logging is currently disabled.
    16:11:33 [INFO] [iConomy] v5.01 (Eruanna) loaded.
    16:11:33 [INFO] [iConomy] Developed by: [Nijikokun]
    16:11:33 [INFO] [Essentials] Payment method found (iConomy version: 5)
    16:11:33 [INFO] [Permissions] version [2.7.3] (Phoenix)  loaded
    16:11:33 [INFO] [iConomy] hooked into Permissions.
    16:11:33 [INFO] Found permissions. Using them for SpyerAdmin.
    16:11:34 [SEVERE] SpyerAdmin script update failed: http://dl.dropbox.com/u/16258
    042/SpyerAdminRepos/Essentials/http://dl.dropbox.com/u/16258042/SpyerAdminRepos/
    Vanilla/script.js
    16:11:34 [INFO] SpyerAdmin module version 1.0, a spying utility for administrato
    rs and moderators, is active. Part of the Spyer package by [nickguletskii200]
    16:11:34 [INFO] Found permissions. Using them for SpyerAdmin.
    16:11:34 [INFO] SpyerFun module version 1.0, a spying utility for normal players
    , is active. Part of the Spyer package by [nickguletskii200]
    16:11:34 [INFO] WorldEdit 4.4 enabled.
    16:11:34 [INFO] WorldEdit: Permissions plugin detected! Using Permissions plugin
     for permissions.
    16:11:34 [INFO] WorldGuard: Permissions plugin detected! Using Permissions plugi
    n for permissions.
    16:11:34 [INFO] WorldGuard: (Town) Single session is enforced.
    16:11:34 [INFO] WorldGuard: (Town) TNT ignition is PERMITTED.
    16:11:34 [INFO] WorldGuard: (Town) Lighters are PERMITTED.
    16:11:34 [INFO] WorldGuard: (Town) Lava fire is blocked.
    16:11:34 [INFO] WorldGuard: (Town) Fire spread is UNRESTRICTED.
    16:11:34 [INFO] WorldGuard: Loaded configuration for world 'Town"
    16:11:34 [INFO] WorldGuard 5.0-alpha10 enabled.
    16:11:34 [INFO] Done (0.258s)! For help, type "help" or "?"
    >
     
  2. Offline

    Flenix

    Admins:
    default: false
    info:
    prefix: ''
    suffix: ''
    build: true
    inheritance:
    permissions:
    - '*'



    You need to set the inheritance ;)
     
  3. Offline

    Ethan

    I set inheritance, still you can't break or place any blocks....updated code.

    And I will put what the console reads when I turn on the server
     
  4. Offline

    Jeyge

    That isn't 2.7.3 of permissions. 3.0 uses different files that go in different locations. I would roll back to 2.7.3.
     
  5. Offline

    Ethan

    I rolled back....it worked for like 2 seconds. I added my permissions back in. It doesn't work anymore....I got rid of them, still doesn't work.

    Permission file updated....again
     
  6. Offline

    TBK

    If you use craftbook, then add this node to the Moderators:
    Code:
    - 'craftbook.mech.*'
     
  7. Offline

    Ethan

    um....I don't use craftbook.....how does that have anything to do with my problem?
     
  8. Offline

    TBK

    Because Craftbook doesn't allow you to build before you have added the permission node.
    Might sound stupid, but have you added your name to the admin group?
     
  9. Offline

    Ethan

    yes....It isn't just me who can't place or build. It is everyone
     
  10. Offline

    Jeyge

    As TBK said above, did you add your name to the users list though. If not, you are going to the default group which doesn't have build permissions.
     
  11. Offline

    Ethan

    Yes....like I said before....I did add my name to the admin list.
     
  12. Offline

    Jeyge

    You should be able to understand our confusion though. You say your permissions file is in the first post but yet it doesn't include any users but the default. I can understand if you don't want to post your userid, but you can at least give us the file you are using with the userid changed. As it is right now, all we can do is look at the default permissions file and know it works fine as it is.

    How about any errors? When you can't break or place blocks, you will sometimes see BLOCK_PLACE/BLOCK_BREAK errors in the console.
     
  13. Offline

    Ethan

    I have seen Block Place errors
    It says "Could not pass event BLOCK_BREAK to Permissions"
    Also if I change the config file to "Town" which is the name of the world then that's when I can't place or break blocks.
    Here's my Permissions file.
    Code:
    # System is no longer used, but may become used in the future
    # Copies is for multiple-world support
    #   Put the name of the world you wish for it to be a clone of, otherwise leave it empty.
    #   If this file is for your default world (the one in server.properties) then you must
    #   leave copies blank.
    #  Example: copies: Derp    -  This will clone the permissions of the world Derp
    #
    # Make sure to rename this file to the name of the world that is in sever.properties under
    # level-name.  So if it is level-name: world  then this should be world.yml and in the
    # plugins/Permissions directory (ie. plugins/Permissions/world.yml)
    #
    # NOTE: Do not use tabs while editing this document.  Use only spaces.  A good way to avoid
    # doing this is to use Notepad++ and replace the tab with 4 spaces.
    plugin:
        permissions:
            system: default
            copies:
    
    ##
    # AntiBuild is included with this.  To disable a group from being able to build then
    # set the build: flag to false (build: false).  If you want a group to be able to build
    # then set it to true.
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another
    #   group simply place the groups name in the "inheritance:" like so:
    #
    #   Example:
    #       inheritance:
    #           - Default
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'foo.bar'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'foo.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    #   If you give a group this permissions, do not have the group inherit any permissions
    #   from other groups.  Any users assigned to this group should NOT be given any additional
    #   permissions either.
    ##
    #   To exempt a node use the - prefix like so:
    #       - '-foo.bar'
    ##
    #   prefix: and suffix: do not do anything on their own.  You need another outside plugin
    #   such as iChat or HeroChat in order for these to do anything.
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: false
            inheritance:
            permissions:
                - 'jobs.job.miner'
                - 'craftbook.mech'
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'bar.foo'
        Admins:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    
    ##
    # Users denote which users are included in which group.
    # TheNo1Yeti is in the Admin group
    # Herpina is a member of the Moderator group but also has access
    # to the herp.derp permissions
    # Derpina is a member of the admin group but does not have access
    # to the derp.derp permission node
    # Users can also have a prefix and suffix as seen with Herpina
    ##
    users:
        wam19:
            group: Admins
            permissions:
                -'*'
     
  14. Offline

    Jeyge

    You need a space after the - for your users permissions.
     
  15. Offline

    Ethan

    There is a space after all the - in the users permissions.


    I really need help, the console is being spammed with the Block place errors. You can't even look at something.
     
  16. Offline

    Jeyge

    BLOCK_PLACE/BLOCK_BREAK errors show up when the permissions.yml file isn't named correctly or isn't in the right place. Make sure your file is in plugins\permissions and is named <world name>.yml unless you have file extensions turned off. If they are off, the name will be just <world name>.
     
  17. Offline

    Ethan

    I am positive the permissions file is named after the world
     
  18. Offline

    Jeyge

    One final thing to check is to actually break your permissions file just to make sure it is reading it. Put a tab in the file and see if you get the error saying that tabs aren't allowed.
     
  19. Offline

    killinmaniac

    watch my vid :)
     
Thread Status:
Not open for further replies.

Share This Page