[ADMN/DEV] PermissionsBukkit v2.0 - Official Default Groups Plugin [1.5.2-R1.0]

Discussion in 'Archived: Plugin Releases' started by SpaceManiac, Jul 17, 2011.

  1. Offline

    SpaceManiac

    PermissionsBukkit - the Official Default Groups Plugin
    Current Version: v2.0
    Find PermissionsBukkit on BukkitDev!

    If you are getting a specific error or cannot determine what is wrong with your permissions file, filing a ticket on BukkitDev will make me much more likely to respond to you; general questions are best to ask in this thread or on the forums on BukkitDev.

    It's been a long time coming, but with the accomplishment of build 1000 Bukkit has finally accomplished a built-in Permissions system (codenamed Superperms). For more info on how they work, and how to integrate them with your plugin, see the official Permissions FAQ. Keep in mind that you should rarely, if ever, have to hook this plugin directly; instead keep things in the realm of checking player.hasPermission("yourplugin.node"). The FAQ thread has more info on how to use Superperms with things like chat prefixes/suffixes.

    Features:
    • Storage of users and groups in plugins/PermissionsBukkit/config.yml.
    • Both users and groups can be assigned individual permissions and parent groups to inherit permissions from.
    • Support for global and per-world permissions.
    • Reload configuration from file with out reloading the plugin.
    • Ability to check if a player has a specific permission node.
    • Ability to dump all permissions a player has and the plugins that set them.
    • Ability to print plugin, description, and default for a given permission node.
    • Ability to modify the permissions of groups and users and the groups of a user in-game.
    • Built-in antibuild via the "permissions.build" node (defaults to allowing anyone to build).
    • A minimalistic bridge from Permissions 3.0 to Superperms is available as a separate plugin, which does not depend on PermissionsBukkit.
    Command Usage:

    Show Spoiler
    PermissionsBukkit uses the command /permissions, with aliases /perms and /perm.

    /permissions reload - reload the configuration from disk.
    /permissions check <node> [player] - check if a player or the sender has a permission (any plugin).
    /permissions info <node> - prints information on a specific permission.
    /permissions dump [player] [page] - prints info about a player's (or the sender's) permissions.
    /permissions setrank <player> <group> - set a player to be in a group with per-group permissions.
    /permissions group - list group-related commands.
    /permissions group list - list all groups.
    /permissions group players <group> - list players in a group.
    /permissions group setperm <group> <[world:]node> [true|false] - set a permission on a group.
    /permissions group unsetperm <group> <[world:]node> - unset a permission on a group.
    /permissions player - list player-related commands.
    /permissions player groups <player> - list groups a player is in.
    /permissions player setgroup <player> <group,...> - set a player to be in only the given groups.
    /permissions player addgroup <player> <group> - add a player to a group.
    /permissions player removegroup <player> <group> - remove a player from a group.
    /permissions player setperm <player> <[world:]node> [true|false] - set a permission on a player.
    /permissions player unsetperm <player> <[world:]node> - unset a permission on a player.

    All commands have in-game help and are usable from the server console.

    Configuration:
    Show Spoiler
    A permission node is a string like 'permissions.build', usually starting with the name of the plugin. Refer to a plugin's documentation for what permissions it cares about. Each node should be followed by true to grant that permission or false to revoke it, as in 'permissions.build: true'. Some plugins provide permission nodes that map to a group of permissions - for example, PermissionsBukkit has 'permissions.*', which automatically grants permissions for all PermissionsBukkit commands. You can also specify false for permissions of this type.

    Users inherit permissions from the groups they are a part of. If a user is not specified here, or does not have a 'groups' node, they will be in the group 'default'. Permissions for individual users may also be specified by using a 'permissions' node with a list of permission nodes, which will override their group permissions. World permissions may be assigned to users with a 'worlds:' entry.

    Groups can be assigned to players and all their permissions will also be assigned to those players. Groups can also inherit permissions from other groups. Like user permissions, groups may override the permissions of their parent group(s). Unlike users, groups do NOT automatically inherit from default. World permissions may be assigned to groups with a 'worlds:' entry.

    The cannot-build message is configurable. If it is left blank, no message will be displayed to the player if PermissionsBukkit prevents them from building, digging, or interacting with a block. Use '&' characters to signify color codes.

    An example configuration file might look like this:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    

    Permissions:
    Show Spoiler
    PermissionsBukkit checks for the following permission nodes:
    • permissions.build - Allows a player to build. Defaults to true.
    • permissions.help - Allows viewing of usage for /permissions.
    • permissions.reload - Allows use of /permissions reload.
    • permissions.check - Allows use of /permissions reload.
    • permissions.info - Allows use of /permissions reload.
    • permissions.dump - Allows use of /permissions reload.
    • permissions.group.help - Allows viewing of usage for /permissions group.
    • permissions.group.list - Allows use of /permissions group list.
    • permissions.group.players - Allows use of /permissions group players.
    • permissions.group.setperm - Allows use of /permissions group setperm.
    • permissions.group.unsetperm - Allows use of /permissions group unsetperm.
    • permissions.player.help - Allows viewing of usage for /permissions player
    • permissions.player.groups - Allows use of /permissions player groups.
    • permissions.player.setgroup - Allows use of /permissions player setgroup.
    • permissions.player.addgroup - Allows use of /permissions player addgroup.
    • permissions.player.removegroup - Allows use of /permissions player removegroup.
    • permissions.player.setperm - Allows use of /permissions player addgroup.
    • permissions.player.unsetperm - Allows use of /permissions player removegroup.
    Also, the following parent nodes are provided for convenience:

    • permissions.* - Maps to permissions.help, .reload, .check, .info, .dump, and to permissions.group.* and permissions.player.*. Defaults to op.
    • permissions.group.* - Maps to permissions.group.help, .list, .players, .setperm, and .unsetperm.
    • permissions.player.* - Maps to permissions.player.help, .groups, .setgroup, .addgroup, .removegroup, .setperm, and .unsetperm.


    Frequently Asked Questions:
    1. Where are my * nodes? (open)
    Bukkit's Superperms has no built-in concept of a global '*' node that automatically gives all permissions, which is intentional - a player can instead be given all permissions by being given 'op' status (that is, listed in ops.txt). Additionally, individual plugins define a parent node (which could be 'pluginname.*' or 'pluginname.all' or anything else) which maps to whatever subpermissions in that plugin the author desires.

    An example is PermissionsBukkit, which provides three such permissions: 'permissions.group.*' for all /permissions group commands, 'permissions.player.*' for all /permissions player commands, and'permissions.*' for all /permissions commands (including permissions.group.* and permissions.player.*).

    If you are using SuperpermsBridge, you can do something similar to '*' nodes for plugins which use Permissions 2.7/3.1 - see the next FAQ for more information.
    2. How do I use SuperpermsBridge? (open)
    SuperpermsBridge is kind of like FakePermissions for GroupManager or PermissionsBridge for PermissionsEx. Once it's installed, it pretends to be the Permissions plugin and converts any plugins that use Permissions 2.7 or Permissions 3.1 to use Superperms instead.

    You can have PermissionsBukkit without SuperpermsBridge or SuperpermsBridge without PermissionsBukkit if you like, but both of these are limited in functionality. If you install SuperpermsBridge without PermissionsBukkit you will not be able to make use of PermissionsBukkit's groups feature or admin commands, and if you install PermissionsBukkit without SuperpermsBridge, plugins that have not updated to use Superperms directly will not function.

    For plugins that use Permissions 2.7/3.1, you can use the special node 'superpermbridge.*' to give the equivalent of what used to be the '*' node for plugins that do not use Superperms directly. If you don't want to give the * node, you can also use the node 'superpermbridge.pluginname' to do the equivalent of what used to be the 'pluginname.*' node. Once again, these only apply to plugins that SuperpermsBridge handles and not to plugins using Superperms directly.
    3. How do I use the root permissions.yml? (open)
    The file 'permissions.yml' in the root of your server can be used to set up custom parent permissions. Parent permissions are a single node that, when given to a player or group, automatically give all their children node. Here's a simple example:
    Code:
    server.basics:
        children:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    
    Now, if you give a player the node 'server.basics', they automatically get all the nodes listed here. Children may also say 'false' instead of 'true', in which case giving the parent will remove the child instead of giving it.

    You can also specify a description if you like, which can be used by plugins to provide information on your node (such as PermissionsBukkit's /perm info command). If you want, you can also provide a default, which can be one of "true", "false", "op", or "notop". CraftBukkit will automatically assign everyone, no one (default), ops, or non-ops the children permissions based on the specified default. Without any plugin like PermissionsBukkit, you can use this defaults system as a limited way to assign people permissions. Here's a more complex example:
    Code:
    server.basics:
        description: Basic permissions for My Cool Server.
        default: true
        children:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    server.admin:
        description: Admin permissions for My Cool Server.
        default: op
        children:
            commandbook.broadcast: true
            commandbook.teleport: true
            commandbook.kick: true
            commandbook.ban: true
    
    You can also define permissions without children, but this is of limited usefulness in permissions.yml (though is important in plugin.yml; see question #6)
    4. How do I switch from (other Permissions plugin)? (open)
    Depends on the Permissions plugin! If you were using PEX's YAML backend, I have a converter done and available on the PermissionsBukkit Tools page. Also available on the tools page is an automatic converter for Essentials GroupManager users.yml and groups.yml files. Automatic converters for Permissions 2.7 and 3.x are on their way, but in the meantime you can still convert your configurations manually.
    5. Where are prefixes and suffixes (or option nodes)? (open)
    Bukkit Superperms has no built-in prefix/suffix settings or non-boolean permission nodes, so individual chat plugins will have to start supporting Superperms in order to make use of non-Permissions-plugin based prefixes and suffixes. Herochat, iChat, and Simple Suffix are all aware of the Superperms update, but in the meantime you can use mChat, which already supports Superperms.

    Once you install mChat and configure the mchat.prefix, mchat.suffix, and mchat.group names in its configuration file (see the example), use PermissionsBukkit to give players or groups the permissions "mchat.prefix.admin", replacing "admin" with whatever node you configured. For example, with an mchat configuration that looks similar to this:
    Code:
    da-name-format: '+prefix+name&e'
    date-format: HH:mm:ss
    message-format: '+prefix+name&f: +message'
    mchat:
        prefix:
            admin: '&4DtK [SO] &7 '
            sadmin: '&9DtK [SA] &7 '
            jadmin: '&aDtK [JA] &7  '
            member: '&cDtK [M] &7 '
    
    You can assign players or groups the mchat.prefix.admin node to get the "SO" prefix, mchat.prefix.sadmin to get the "SA" prefix, and so on.
    6. (Coders) How do I set up my plugin.yml? (open)
    Take a look at this post in Dinnerbone's FAQ for an example. This is a lot like the setup of permissions.yml (see above), but you can also define non-parent permissions (just include description and default and leave out children).
    7. Is PermissionsBukkit outdated? (open)
    No! PermissionsBukkit 2.0 was last updated for 1.3.1-R2.0, is verified to work on 1.4.7-R1.0, and is unlikely to break on future releases.

    Downloads:
    Current Version:

    PermissionsBukkit v2.0 (jar) (details)
    Old Versions:
    PermissionsBukkit v1.6 (jar) (details)

    [​IMG]

    Changelog:

    Friday 7 September 2012 (2.0)
    • Fixed a case-sensitivity issue with setting per-world permissions that could cause some permissions to fail to apply.
    • Added /perm setrank <player> <group> subcommand (alias rank) with per-group permissions (permissions.setrank and permissions.setrank.<group>)
    • Added plugin metrics via http://mcstats.org/plugin/PermissionsBukkitMCStats (disableable in plugins/PluginMetrics/config.yml)
    Wednesday 29 February 2012 (1.6)
    • Fixed some massive issues that were caused due to having uploaded a buggy, in-development version instead of 1.5.
    • Note: If your configuration was messed up as a result of this issue, the new build should gradually correct it as needed.
    Saturday 25 February 2012 (1.5b)
    • Revamped to be compatible with R5.
    • Fixed issues with permissions not carrying properly on world change.
    • Many internal improvements for performance and stability.
    • SuperpermsBridge: in honor of R5 removing deprecated code, SuperpermsBridge is officially gone!
    Monday 18 July 2011 (1.1/1.2)
    • Fix BukkitContrib incompatibility issues.
    • Improved the output of the /perm check command.
    • Fixed issues when 'users:' is not specified in the config file.
    • Fixed the /permissions reload command.
    • SuperpermsBridge: improve wildcard handling; in addition to 'superpermbridge.*' and 'superpermbridge.pluginname', now supported are 'superpermbridge.plugin.*', 'superpermbridge.plugin.subnode.*', and so on.
    Monday 18 July 2011 (1.0/1.1)
    • SuperpermsBridge: adding the special 'superpermbridge.*' and 'superpermbridge.pluginname' nodes (see #2 in the FAQ for details).
    Sunday 17 July 2011 (1.0/1.0)

    • Initial release of PermissionsBukkit v1.0 and SuperpermsBridge v1.0.
     
    madmac, Gesundheit, tripleX and 23 others like this.
  2. Offline

    Snowy007

    There are still a lot of permission nodes with tabs BEHIND them though. Try removing those too.
     
  3. Offline

    BlackDawn187

    Are you talking about between the colons and 'true'? or after 'true'?
     
  4. Offline

    Kurai Ookami

    Brief question there are a few plugins that have certain permissions default to true for admins. I've manually set them to false in the admin groups yet the default seems to still override them. Is this a prioritising issue in permissions bukkit or an issue with the plugins?
     
  5. Offline

    Snowy007

    After 'True'.

    Honestly... i don't know.
    The way i do it, is that i'm not even an OP on my own server. I handle everything with permissions. As you, i don't always like to automatically get all permissions for being an OP. Sometimes there are just things you don't want to have.
     
  6. Offline

    Kurai Ookami

    actually this might help, so does this mean that I can set up an admin group on permissions bukkit and perform basically the same functions as an op, so long as the proper permissions have been given?

    EDIT: I tried it out and have been able to reach my desired affects. So the long and short of it, as long as the admin group has bukkit.command: true and bukkit.command.*: true you can perform all OP functions without receiving OP defaults
     
  7. Offline

    Snowy007

    Exactly like that yes. :p
     
  8. Offline

    Minimeg

    Guys, i need help with something. In the plugin izone, i cant make more zones than 3 because there is a limit. And i need to give myself as admin the rights to do it with permissionsbukkit. I have tried many things, and ive also contacted clanforge and the could not do it either.

    Here's the config files of both plugins:


    Code:
    ###################################################################
    # This is the default configuration template for this            #
    # plugin, PermissionsBukkit. Please consult these                #
    # guides on our wiki for more information on how to              #
    # use PermissionsBukkit:                                          #
    #                                                                #
    # http://wiki.multiplay.co.uk/Minecraft/Bukkit/PermissionsBukkit  #
    #                                                                #
    # http://wiki.multiplay.co.uk/Minecraft/Bukkit/Understanding_YAML #
    #                                                                #
    # Thanks, and good luck!                                          #
    ###################################################################
     
    users:
        'Minimeg':
            groups:
            - owner
    groups:
        default:
            permissions:
                group.default: true
                permissions.build: false
        user:
            permissions:
                group.default: false
                group.user: true
                permissions.build: true
            inheritance:
            - default
        mod:
            permissions:
                group.user: false
                group.mod: true
            inheritance:
            - user
        admin:
            permissions:
                group.mod: false
                group.admin: true
                permissions.*: true
            inheritance:
            - mod
        owner:
            permissions:
                group.owner: true
                # this node sets all permissions for commandbook to true
                commandbook.*: true
                # this node sets all permissions for worldedit to true
                worldedit.*: true
                # this node sets all permissions for worldguard to true
                worldguard.*: true
                izone.*: true
                izone.zone.max-zone.unlimited: true
            inheritance:
            - admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    Izone:

    Code:
    on-create:
      protection: true
      monster: false
      animal: false
      welcome: false
      farewell: false
      heal: false
      hurt: false
      pvp: false
      creeper: false
      tnt: false
      explosion: false
      fire: false
      restriction: false
      jail: false
      lightning: false
      deathdrop: false
      safedeath: false
      drop: false
      interact: true
      enderman: false
      god: false
      gamemode: false
      takeitem_in: false
      takeitem_out: false
      giveitem_in: false
      giveitem_out: false
      texturepack: false
      melt: false
    tools:
      check: 268
      define: 269
    healing:
      time: 3
      amount: 1
    hurting:
      time: 7
      amount: 2
    restriction:
      size:
        (-1, -1, -1): izone.zone.max-size.unlimited
        (50, 256, 50): izone.zone.max-size.1
      zone:
        '-1': izone.zone.max-zone.unlimited
        '4': izone.zone.max-zone.1
    
     
  9. Offline

    Snowy007

    I don't know. The only thing i would say is to delete the empty line at the top of your PermissionsBukkit config. But if all other permissions except the unlimited izone permission work fine, then i don't think that would be the problem.
     
  10. Offline

    mercury19

    Show Spoiler


    I also have a question about giving permissions for izone.

    I run a small private server, its the tekkit one if that makes a difference, and got the izone plugin.
    I wanted to give the players full power over there own zones and such, because there are no admins.
    However, when I try to use any of the commands, I get a "you don't have permission message"


    I noticed that under the group "owner", you put iZone.*: true

    From my little understanding of this code, that means it accesses a different file?
    If so, what file does it access? do I have to write anything? what do I write?



    Thanks, m19
     
  11. Offline

    Snowy007

    The 'iZone.*: true' node automatically sets all the iZone permissions to 'true' for the group.
     
  12. Offline

    mercury19

    So I don't have to write anything anywhere? Except that line?


    EDIT: In the case that I have to op everyone to get them to use the izone, because the above line didnt work, is there a way to take the regular op commands away from them?

    Or would creating a group, and adding that node, then adding the players to that group work?
     
  13. Offline

    Snowy007

    If you give the 'iZone.*: true' permission to the 'default' group, everyone should be able to use all the izone permissions.
    You could also create a group with the permission so only the users you put in that group can use the izone permissions instead of just giving everyone full rights without having to promote the players first.
     
  14. Offline

    mercury19

    It still isn't working. Here is my file, if that helps




    Code:
    users:
     
           
    groups:
        default:
            permissions:
                iZone.*: true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                iZone.*: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: false
     
  15. Offline

    Snowy007

    Remove any empty lines. The plugin doesn't seem to like empty lines. xD
    Also make sure that you don't use tabs for indention. Only spaces.
     
  16. Offline

    mercury19

    Are you sure there aren't any other files I have to write in?

    Because it still only works if I op myself.:(

    EDIT: does it matter where I put the config file?
     
  17. Offline

    Snowy007

    It definitely matters where you put the config file yes. It should be in you 'server => plugins => permissionsbukkit' folder.
     
  18. Offline

    Bowbender

    I'm hoping someone can help with a permissions issue that I'm having.

    We use WorldGuard to protect areas. I setup a large area that is protected from building. This area is priority 0. I am the owner. I then create a smaller area within that larger one and put it to priority 1.

    I check the permission of the "default" group and "permissions.build" is set to true.

    I check if our users are in that group by using "/perms group players default". This reveals that there are "0" in that group. However, if I use "/perms player groups PLAYERNAME", it states that they are in the default group.

    On the smaller region I want them to build in, I've tried "/rg addmember regionname g:default", and I've also set that region to "passthrough allow" and "construct default".

    However each of the above results in players still not able to build/destroy in that smaller region.

    I know the above is long winded, but I wanted to give as much info as I can.

    Any help would be greatly appreciated.

    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    users:
      RealNameOmited:
        groups:
        - admin
    RealNameOmited:
        groups:
        - admin
    groups:
      default:
        permissions:
          permissions.build: true
          simplechat.msg: true
          simplechat.reply: true
      admin:
        permissions:
          permissions.*: true
        inheritance:
        - user
      user:
        permissions:
          permissions.build: true
        worlds:
          creative:
            coolplugin.item: true
        inheritance:
        - default
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    Thanks!
     
  19. Offline

    mercury19

    I have it in there, before it was just in the plugins folder, and I also have the jar in the plugins folder.

    Should the config be the only file in the PermissionsBukkit folder?

    Here is my code again, its been changed:

    Code:
    users:
        mercury19:
            permissions:
                izone.*: true
            groups:
            -user
    groups:
        default:
            permissions:
                iZone.*: true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                izone.*: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false

    Thanks, m19
     
  20. Offline

    Kurai Ookami

    I use iZone as well and wanted to add something in.
    Code:
    '3': izone.zone.max-zone.1
    the config for iZone itself sets up restrictions as separate permissions like this ^. what I'm thinking is the restrictions may overpower the allowances so when using iZone.*: true it's possible that your only getting the minimal allowances. would you mind posting your iZone config file as well?
     
  21. Offline

    mercury19

    I haven't touched my config file for izone yet. I still cant get it to work for players.


    However, I think I found the answer. In the bukkit.yml, there is a line that says permissions: permissions.yml

    How should I change that to make it access the file in the permissionsbukkit folder?



    Thanks, m19
     
  22. Offline

    Kurai Ookami

    that should be permissions-file: permission.yml but aside from that it's fine, it'll still access permission bukkit.
    I'd still like to see both your iZone config file and permissions config in their entirety if that's alright with you.
     
  23. Offline

    Svedrigailov

    -I looked, but I couldn't find this problem-

    Here is my error (Occurs whenever I try see the contents of a group via "/perm grouplist Ops" ingame. The second one occurred when I tried to add a player to a group via the command ingame.)
    Code:
    195 recipes
    27 achievements
    01:44:56 [INFO] Starting minecraft server version 1.3.1
    01:44:56 [INFO] Loading properties
    01:44:56 [INFO] Default game type: SURVIVAL
    01:44:56 [INFO] Generating keypair
    01:44:56 [INFO] Starting Minecraft server on *:25565
    01:44:57 [INFO] This server is running CraftBukkit version git-Bukkit-1.3.1-R1.0
    -b2320jnks (MC: 1.3.1) (Implementing API version 1.3.1-R1.0)
    01:44:57 [SEVERE] ebean.properties not found
    01:44:57 [INFO] DataSourcePool [NiftyWarp] autoCommit[false] transIsolation[SERI
    ALIZABLE] min[2] max[20]
    01:44:58 [INFO] SubClassFactory parent ClassLoader [org.bukkit.plugin.java.Plugi
    nClassLoader]
    01:44:58 [INFO] Entities enhanced[0] subclassed[1]
    01:44:58 [INFO] [Orebfuscator] Loading Orebfuscator v1.5.14
    01:44:58 [INFO] [Backup] Loading Backup v2.1-dev
    01:44:58 [INFO] [BOSEconomy] Loading BOSEconomy v0.7.3.1
    01:44:58 [INFO] [EnderChestblock] Loading EnderChestblock v1.0
    01:44:58 [INFO] [Vault] Loading Vault v1.2.17-b224
    01:44:58 [INFO] [WorldEdit] Loading WorldEdit v5.3
    01:44:58 [INFO] [ChunkVisualizer] Loading ChunkVisualizer v0.2.2
    01:44:58 [INFO] [NiftyWarp] Loading NiftyWarp v1.3.3
    01:44:58 [INFO] [PermissionsBukkit] Loading PermissionsBukkit v1.6
    01:44:58 [INFO] [Factions] Loading Factions v1.6.9
    01:44:58 [INFO] [ChestShop] Loading ChestShop v3.46
    01:44:58 [INFO] [Orebfuscator] Enabling Orebfuscator v1.5.14
    01:44:58 [INFO] [OFC] Version 1.5.14 enabled!
    01:44:58 [INFO] [Vault] Enabling Vault v1.2.17-b224
    01:44:58 [INFO] [Vault][Economy] BOSEconomy7 found: Waiting
    01:44:58 [INFO] [Vault][Permission] PermissionsBukkit hooked.
    01:44:58 [INFO] [Vault][Permission] PermissionsBukkit found: Waiting
    01:44:58 [INFO] [Vault][Permission] SuperPermissions loaded as backup permission
    system.
    01:44:59 [INFO] [Vault] Enabled Version 1.2.17-b224
    01:44:59 [INFO] Preparing level "world"
    01:44:59 [INFO] Preparing start region for level 0 (Seed: 7744535373623758956)
    01:45:00 [INFO] Preparing spawn area: 97%
    01:45:00 [INFO] Preparing start region for level 1 (Seed: 7744535373623758956)
    01:45:01 [INFO] Preparing spawn area: 77%
    01:45:01 [INFO] Preparing start region for level 2 (Seed: 7744535373623758956)
    01:45:02 [INFO] [Backup] Enabling Backup v2.1-dev
    01:45:02 [INFO] [Backup] Save-All will be performed every 30 minute(s).
    01:45:02 [INFO] [Backup] Backup v2.1-dev has completed loading!
    01:45:02 [INFO] [BOSEconomy] Enabling BOSEconomy v0.7.3.1
    01:45:02 [INFO] BOSEconomy v0.7.3.1 enabled.
    01:45:02 [INFO] [Vault][Economy] BOSEconomy hooked.
    01:45:02 [INFO] [EnderChestblock] Enabling EnderChestblock v1.0
    01:45:02 [INFO] EnderChestBlock has been enabled
    01:45:02 [INFO] [WorldEdit] Enabling WorldEdit v5.3
    01:45:02 [INFO] WEPIF: Using the Bukkit Permissions API.
    01:45:02 [INFO] [ChunkVisualizer] Enabling ChunkVisualizer v0.2.2
    01:45:02 [INFO] [NiftyWarp] Enabling NiftyWarp v1.3.3
    01:45:02 [INFO] [NiftyWarp] - Integrated with PermissionsBukkit
    01:45:02 [INFO] [NiftyWarp] - NiftyWarp v1.3.3 has been enabled
    01:45:02 [INFO] [PermissionsBukkit] Enabling PermissionsBukkit v1.6
    01:45:02 [INFO] [PermissionsBukkit] Enabled successfully, 0 players registered
    01:45:02 [INFO] [Factions] Enabling Factions v1.6.9
    01:45:02 [INFO] [Factions v1.6.9] === ENABLE START ===
    01:45:02 [INFO] [Factions v1.6.9] Loading board from disk
    01:45:02 [INFO] [Factions v1.6.9] Economy integration through Vault plugin succe
    ssful.
    01:45:02 [INFO] [Factions v1.6.9] NOTE: Economy is disabled. You can enable it w
    ith the command: f config econEnabled true
    01:45:02 [INFO] [Factions v1.6.9] === ENABLE DONE (Took 263ms) ===
    01:45:03 [INFO] [Backup] Plugin is up to date, at version: 2.1-dev.
    01:45:03 [INFO] [ChestShop] Enabling ChestShop v3.46
    01:45:03 [INFO] [ChestShop] Vault loaded - using BOSEconomy
    01:45:03 [INFO] Server permissions file permissions.yml is empty, ignoring it
    01:45:03 [INFO] Done (4.520s)! For help, type "help" or "?"
    01:45:06 [INFO] Johnny_Steele[/192.168.1.1:58241] logged in with entity id 157 a
    t ([world] -6.630501852927469, 70.77377943533278, -61.030283139638044)
    01:45:25 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'perm
    ' in plugin PermissionsBukkit v1.6
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
            at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:16
    8)
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:4
    92)
            at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.
    java:878)
            at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:825)
     
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:807)
            at net.minecraft.serverhook.NetServerHandlerProxy.a(NetServerHandlerProx
    y.java:124)
            at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:44)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:281)
            at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:109)
            at net.minecraft.server.ServerConnection.b(SourceFile:35)
            at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30)
            at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:583)
            at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:212)
            at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:476)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:408)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
    Caused by: java.lang.NullPointerException
            at com.platymuus.bukkit.permissions.PermissionsCommand.groupCommand(Perm
    issionsCommand.java:185)
            at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(Permiss
    ionsCommand.java:146)
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
            ... 16 more
    01:46:02 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'perm
    ' in plugin PermissionsBukkit v1.6
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
            at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:16
    8)
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:4
    92)
            at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.
    java:878)
            at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:825)
     
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:807)
            at net.minecraft.serverhook.NetServerHandlerProxy.a(NetServerHandlerProx
    y.java:124)
            at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:44)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:281)
            at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:109)
            at net.minecraft.server.ServerConnection.b(SourceFile:35)
            at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30)
            at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:583)
            at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:212)
            at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:476)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:408)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
    Caused by: java.lang.NullPointerException
            at com.platymuus.bukkit.permissions.PermissionsCommand.createPlayerNode(
    PermissionsCommand.java:400)
            at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(Per
    missionsCommand.java:301)
            at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(Permiss
    ionsCommand.java:152)
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
            ... 16 more
    >

    Here is my Config.yml
    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
     
    users:
     
    groups:
      Players:
        permissions:
          permissions.build: true
          niftywarp.use.home: true
          niftywarp.use.homeset: true
          niftywarp.use.list: true
        inheritance:
        - default
      Ops:
        permissions:
          permissions.*: true
          permissions.group.*: true
          permissions.player.*: true
          niftywarp.use.add: true
          niftywarp.use.delete: true
          niftywarp.use.rename: true
          niftywarp.use.set: true
          niftywarp.use.warp: true
          niftywarp.use.warptocoord: true
          niftywarp.use.version: true
          niftywarp.admin.delete: true
          niftywarp.admin.rename: true
          niftywarp.admin.set: true
        inheritance:
        - Players
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    

    Any help is appreciated.
     
  24. Offline

    Snowy007

    Try removing the empty lines just above and below 'users:'.
     
  25. Offline

    Svedrigailov

    Thank you for your response. I removed the lines, I can now use the /perm group list command, but I still get this error when trying to add a player to a group ingame via the "/perm player addgroup Johnny_Steele Ops" command

    Code:
    195 recipes
    27 achievements
    10:35:54 [INFO] Starting minecraft server version 1.3.1
    10:35:54 [INFO] Loading properties
    10:35:54 [INFO] Default game type: SURVIVAL
    10:35:54 [INFO] Generating keypair
    10:35:54 [INFO] Starting Minecraft server on *:25565
    10:35:55 [INFO] This server is running CraftBukkit version git-Bukkit-1.3.1-R1.0
    -b2320jnks (MC: 1.3.1) (Implementing API version 1.3.1-R1.0)
    10:35:55 [SEVERE] ebean.properties not found
    10:35:55 [WARNING] ----- Bukkit Auto Updater -----
    10:35:55 [INFO] DataSourcePool [NiftyWarp] autoCommit[false] transIsolation[SERI
    ALIZABLE] min[2] max[20]
    10:35:55 [WARNING] Your version of CraftBukkit is out of date. Version 1.3.1-R2.
    0 (build #2340) was released on Sun Aug 19 12:52:49 CDT 2012.
    10:35:55 [WARNING] Details: http://dl.bukkit.org/downloads/craftbukkit/view/0137
    1_1.3.1-R2.0/
    10:35:55 [WARNING] Download: http://dl.bukkit.org/downloads/craftbukkit/get/0137
    1_1.3.1-R2.0/craftbukkit.jar
    10:35:55 [WARNING] ----- ------------------- -----
    10:35:56 [INFO] SubClassFactory parent ClassLoader [org.bukkit.plugin.java.Plugi
    nClassLoader]
    10:35:56 [INFO] Entities enhanced[0] subclassed[1]
    10:35:56 [INFO] [Orebfuscator] Loading Orebfuscator v1.5.14
    10:35:56 [INFO] [Backup] Loading Backup v2.1-dev
    10:35:56 [INFO] [BOSEconomy] Loading BOSEconomy v0.7.3.1
    10:35:56 [INFO] [EnderChestblock] Loading EnderChestblock v1.0
    10:35:56 [INFO] [Vault] Loading Vault v1.2.17-b224
    10:35:56 [INFO] [WorldEdit] Loading WorldEdit v5.3
    10:35:56 [INFO] [ChunkVisualizer] Loading ChunkVisualizer v0.2.2
    10:35:56 [INFO] [NiftyWarp] Loading NiftyWarp v1.3.3
    10:35:56 [INFO] [PermissionsBukkit] Loading PermissionsBukkit v1.6
    10:35:56 [INFO] [Factions] Loading Factions v1.6.9
    10:35:56 [INFO] [ChestShop] Loading ChestShop v3.46
    10:35:56 [INFO] [Orebfuscator] Enabling Orebfuscator v1.5.14
    10:35:56 [INFO] [OFC] Version 1.5.14 enabled!
    10:35:56 [INFO] [Vault] Enabling Vault v1.2.17-b224
    10:35:56 [INFO] [Vault][Economy] BOSEconomy7 found: Waiting
    10:35:56 [INFO] [Vault][Permission] PermissionsBukkit hooked.
    10:35:56 [INFO] [Vault][Permission] PermissionsBukkit found: Waiting
    10:35:56 [INFO] [Vault][Permission] SuperPermissions loaded as backup permission
    system.
    10:35:56 [INFO] [Vault] Enabled Version 1.2.17-b224
    10:35:56 [INFO] Preparing level "world"
    10:35:57 [INFO] Preparing start region for level 0 (Seed: 7744535373623758956)
    10:35:58 [INFO] Preparing start region for level 1 (Seed: 7744535373623758956)
    10:35:58 [INFO] Preparing spawn area: 3%
    10:35:59 [INFO] Preparing start region for level 2 (Seed: 7744535373623758956)
    10:35:59 [INFO] Preparing spawn area: 0%
    10:35:59 [INFO] [Backup] Enabling Backup v2.1-dev
    10:35:59 [INFO] [Backup] Save-All will be performed every 30 minute(s).
    10:35:59 [INFO] [Backup] Backup v2.1-dev has completed loading!
    10:35:59 [INFO] [BOSEconomy] Enabling BOSEconomy v0.7.3.1
    10:35:59 [INFO] BOSEconomy v0.7.3.1 enabled.
    10:35:59 [INFO] [Vault][Economy] BOSEconomy hooked.
    10:35:59 [INFO] [EnderChestblock] Enabling EnderChestblock v1.0
    10:35:59 [INFO] EnderChestBlock has been enabled
    10:35:59 [INFO] [WorldEdit] Enabling WorldEdit v5.3
    10:35:59 [INFO] WEPIF: Using the Bukkit Permissions API.
    10:36:00 [INFO] [ChunkVisualizer] Enabling ChunkVisualizer v0.2.2
    10:36:00 [INFO] [NiftyWarp] Enabling NiftyWarp v1.3.3
    10:36:00 [INFO] [NiftyWarp] - Integrated with PermissionsBukkit
    10:36:00 [INFO] [NiftyWarp] - NiftyWarp v1.3.3 has been enabled
    10:36:00 [INFO] [PermissionsBukkit] Enabling PermissionsBukkit v1.6
    10:36:00 [INFO] [PermissionsBukkit] Enabled successfully, 0 players registered
    10:36:00 [INFO] [Factions] Enabling Factions v1.6.9
    10:36:00 [INFO] [Factions v1.6.9] === ENABLE START ===
    10:36:00 [INFO] [Backup] Plugin is up to date, at version: 2.1-dev.
    10:36:00 [INFO] [Factions v1.6.9] Loading board from disk
    10:36:00 [INFO] [Factions v1.6.9] Economy integration through Vault plugin succe
    ssful.
    10:36:00 [INFO] [Factions v1.6.9] NOTE: Economy is disabled. You can enable it w
    ith the command: f config econEnabled true
    10:36:00 [INFO] [Factions v1.6.9] === ENABLE DONE (Took 300ms) ===
    10:36:00 [INFO] [ChestShop] Enabling ChestShop v3.46
    10:36:00 [INFO] [ChestShop] Vault loaded - using BOSEconomy
    10:36:01 [INFO] Server permissions file permissions.yml is empty, ignoring it
    10:36:01 [INFO] Done (4.216s)! For help, type "help" or "?"
    10:36:03 [INFO] Johnny_Steele[/192.168.1.1:49492] logged in with entity id 150 a
    t ([world] -10.25540157817736, 70.0, -47.599672269839104)
    10:36:35 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'perm
    ' in plugin PermissionsBukkit v1.6
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
            at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:16
    8)
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:4
    92)
            at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.
    java:878)
            at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:825)
     
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:807)
            at net.minecraft.serverhook.NetServerHandlerProxy.a(NetServerHandlerProx
    y.java:124)
            at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:44)
            at net.minecraft.server.NetworkManager.b(NetworkManager.java:281)
            at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:109)
            at net.minecraft.server.ServerConnection.b(SourceFile:35)
            at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30)
            at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:583)
            at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:212)
            at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:476)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:408)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
    Caused by: java.lang.NullPointerException
            at com.platymuus.bukkit.permissions.PermissionsCommand.createPlayerNode(
    PermissionsCommand.java:400)
            at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(Per
    missionsCommand.java:301)
            at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(Permiss
    ionsCommand.java:152)
            at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
            ... 16 more
    >
    In case you need it, here is my config.yml in my permissions bukkit folder

    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    users:
    groups:
      Players:
        permissions:
          permissions.build: true
          niftywarp.use.home: true
          niftywarp.use.homeset: true
          niftywarp.use.list: true
        inheritance:
        - default
      Ops:
        permissions:
          permissions.*: true
          permissions.group.*: true
          permissions.player.*: true
          niftywarp.use.add: true
          niftywarp.use.delete: true
          niftywarp.use.rename: true
          niftywarp.use.set: true
          niftywarp.use.warp: true
          niftywarp.use.warptocoord: true
          niftywarp.use.version: true
          niftywarp.admin.delete: true
          niftywarp.admin.rename: true
          niftywarp.admin.set: true
        inheritance:
        - Players
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    
     
  26. Offline

    Mikirog

    My console writes me "[SERVERE] [PermissionsBukkit] Unable to load configuration!" and permissions don't works. How I do bad?
     
  27. Offline

    ohjays

  28. Offline

    Snowy007

    Try manually adding the first user like this:
    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    users:
      Johnny_Steele:
        groups:
        - Ops
    groups:
      Players:
        permissions:
          permissions.build: true
          niftywarp.use.home: true
          niftywarp.use.homeset: true
          niftywarp.use.list: true
        inheritance:
        - default
      Ops:
        permissions:
          permissions.*: true
          permissions.group.*: true
          permissions.player.*: true
          niftywarp.use.add: true
          niftywarp.use.delete: true
          niftywarp.use.rename: true
          niftywarp.use.set: true
          niftywarp.use.warp: true
          niftywarp.use.warptocoord: true
          niftywarp.use.version: true
          niftywarp.admin.delete: true
          niftywarp.admin.rename: true
          niftywarp.admin.set: true
        inheritance:
        - Players
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    Obviously there is something wrong with your configuration. If you post it here we can check it for mistakes.
    Also as ohjays already said, running your config through the online parser can tell you where any mistakes might be. It doesn't detect all mistakes though. For example, empty lines is correct YML, however this plugin doesn't seem to function correctly if you have any empty lines.
     
  29. Offline

    Mikirog

    OK, there is my config and anything wrong. I want to make players shot with guns and throw grenades by plugin Armageddon.

    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    #
    # The cannot-build message is configurable. If it is left blank, no message
    # will be displayed to the player if PermissionsBukkit prevents them from
    # building, digging, or interacting with a block. Use '&' characters to
    # signify color codes.
     
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: false
            armageddon.guns.*: true
            armageddon.grenades.*: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cNie masz uprawnien, by tu budowac.'
     
    debug: false
    
     
  30. Offline

    Snowy007

    The permission nodes for the armageddon plugin where not correctly indented. They needed to be 4 spaces further. Also i removed 2 empty lines. one at the top and one at the bottom of the file.

    This should work:
    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    #
    # The cannot-build message is configurable. If it is left blank, no message
    # will be displayed to the player if PermissionsBukkit prevents them from
    # building, digging, or interacting with a block. Use '&' characters to
    # signify color codes.
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: false
                armageddon.guns.*: true
                armageddon.grenades.*: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cNie masz uprawnien, by tu budowac.'
    debug: false
     
  31. Offline

    Mikirog

    Fixed. I only use a TAB instead od Space :)
     

Share This Page