[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

    Fly007

    Not at all, I was just making sure that was the only problem with it all. It was just with the other times I had setup perm files, I don't remember if I ever even changed the name of default.. But Its all been working fine since I changed it back. I much appreciate your help.
     
  3. Offline

    Yves29Ultra

    I know lots of poeple have this problem but it says for me (on pail) [SEVERE] [PermissionsBukkit] Unable to load configuration! please HELP! :( here's my config

    # 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:
    bigmak3:
    permissions:
    permissions.example: true
    groups:
    - admin
    Yves29Ultra:
    permissions:
    permissions.example: true
    groups:
    - owner
    Maksterx:
    permissions:
    permissions.example: true
    groups:
    - mod
    Jeanmarc13:
    permissions:
    permissions.example: true
    groups:
    - mod
    groups:
    default:
    permissions:
    permissions.build: false
    admin:
    permissions:
    permissions.*: true
    simpleprefix.admin: true
    inheritance:
    - user
    owner:
    permissions:
    permissions.*: true
    simpleprefix.owner: true
    inheritance:
    - user
    mod:
    permissions:
    permissions.*: true
    simpleprefix.mod: 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: true

    HELP ME!
     
  4. Offline

    Snowy007

    It still doesn't work with the fixed config i gave you? PermissionsBukkit is really strict with the config and any small mistake can make it behave incorrectly.

    No problem

    Could you perhaps put your config in code tags? Its really hard to read this way without being able to see indention. At first glance i don't see much wrong with it, but again i can't check for indention errors.
     
  5. Offline

    karrotsrkool

    Yeah I swapped it out and still no luck, its just the op, deop and commands like that, the commands that are native to bukkit and not essentials.
     
  6. Offline

    Snowy007

    Ah, you want the native bukkit commands to work for moderators.
    In that case, you need to use these permission nodes:
    http://wiki.bukkit.org/CraftBukkit_commands
     
  7. Offline

    karrotsrkool

    Ok, this is my new config file which is still not working:
    Code:
    # PermissionsBukkit configuration file
    users:
      ConspiracyWizard:
        permissions:
          permissions.example: true
        groups:
        - admin
      karrot:
        groups:
        - owner
      dr_brian:
        groups:
        - owner
      masamune962:
        groups:
        - owner
      jordan64123:
        groups:
        - moderator
    groups:
      default:
        permissions:
          permissions.*: false
          permissions.build: false
          commandbook.*: false
          simpleprefix.guest: true
      admin:
        permissions:
          permissions.*: true
          simpleprefix.admin: true
          simpleprefix.moderator: false
        inheritance:
        - moderator
      owner:
        permissions:
          simpleprefix.owner: true
          simpleprefix.admin: false
        inheritance:
        - admin
      user:
        permissions:
          Essentials.sethome: true
          Essentials.tpaccept: true
          Essentials.tpdeny: true
          Essentials.pay: true
          Essentials.balance: true
          Essentials.signs.use.*: true
          Essentials.afk: true
          Essentials.list: true
          Essentials.suicide: true
          Essentials.help: true
          Essentials.msg: true
          Essentials.mail: true
          Essentials.mail.*: true
          Essentials.home: true
          permissions.build: true
          simpleprefix.user: true
          simpleprefix.guest: false
        worlds:
          creative:
            coolplugin.item: true
        inheritance:
        - default
      moderator:
        permissions:
          bukkit.command.ban.*: true
          bukkit.command.unban.*: true
          bukkit.command.tempban: true
          bukkit.command.kick: true
          simpleprefix.moderator: true
          simpleprefix.user: false
        worlds:
          creative:
            coolplugin.item: true
        inheritance:
        - user
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    
     
  8. Offline

    mistermsk

    Bukkit.command? Is there a list of these?

    Also, is there a command to not let players build but allow them to push switches, pull levers, and use pressure plates? Also, would be nice if they could put down torches.
     
  9. Offline

    Snowy007

    To be honest, i can't really find anything else wrong with it. Unless i'm missing something myself, this should work fine.
    The only thing i can think of is that you might have used tabs somewhere for indention. When posting a config here it automatically replaces tabs with spaces so that is something i can't really check.

    I already told this literally 2 posts above yours.
    http://wiki.bukkit.org/CraftBukkit_commands

    And no, the only thing that comes close to what you want is the 'permissions.build' node.
    Maybe you can find a plugin that can help you with your exact needs.
     
  10. Offline

    karrotsrkool

    I've just checked it and there was no tabs so I have no idea.
     
  11. Offline

    Darklom

    Well the problem is, the default usergroup isn't working. Players aren't set to it when they login nor if it's set manual does it work. Everything else seems to work fine though.

    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:
        Darklom:
            groups:
            - default
    groups:
        default:
            permissions:
                permissions.build: true
                essentials.realname: true
                essentials.ban.notify: true
                afk: true
                back: true
                chat.shout: true
                clearinventory: true
                compass: true
                delhome: true
                getpos: true
                help: true
                home: true
                ignore: true
                info: true
                itemdb: true
                list: true
                mail: true
                mail.send: true
                me: true
                motd: true
                ping: true
                r: true
                rules: true
                suicide: true
                time: true
        Lead Administrator:
            permissions:
                permissions.*: true
            inheritance:
            - Administrator
        Administrator:
            permissions:
                permissions.build: true
                essentials.give.item: true
                essentials.give.item: true
                essentials.list.hidden: true
                essentials.ban: true
                essentials.clearinventory.others: true
                essentials.ban.offline: true
                essentials.banip: true
                essentials.invsee.modify: true
                essentials.tempban.offline: true
                essentials.unban: true
                essentials.unbanip: true
                essentials.chat.url: true
                essentials.joinfullserver: true
                essentials.protect.alerts.notrigger: true
                nomulti.exception.add: true
                nomulti.exception.remove: true
                nomulti.reload: true
                coreprotect.*: true
                bukkit.command.whitelist.add: true
                bukkit.command.whitelist.remove: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - Moderator
        Moderator:
            permissions:
                permissions.build: true
                essentials.chat.question: true
                essentials.getpos.others: true
                essentials.seen.banreason: true
                essentials.broadcast: true
                essentials.invsee: true
                essentials.kick: true
                essentials.kick.noti: true
                essentials.kill.force: true
                essentials.mute: true
                essentials.tempban: true
                essentials.togglejail.offline: true
                essentials.tp: true
                essentials.tp.others: true
                essentials.teleport.hidden: true
                essentials.teleport.cooldown.bypass: true
                essentials.teleport.timer.bypass: true
                essentials.chat.spy: true
                essentials.protect.admin: true
                essentials.protect.ownerinfo: true
                essentials.signs.protection.override: true
                essentials.signs.trade.override: true
                bukkit.command.ban.list: true
                bukkit.command.list: true
                bukkit.command.say: true
            inheritance:
            - default
        Donator:
            permissions:
                permissions.build: true
                essentials.tpa: true
                essentials.joinfullserver: true
                sethome: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
     
  12. Offline

    Snowy007

    Your permissions in the default group look really strange. Permissions are NEVER just a single word. Its usually 'pluginname.permission: true'
     
  13. Offline

    JBL

    I'm having trouble with my permissions, I don't think it's too complicated and I've basically been going through all my plugins and their commands to add each to which specific groups I want them to be in.

    I'm getting console errors/internal errors whenever I try to list what players are in what groups (permissions group players <group>) and I'm assuming it's something to do with my permissions.

    Any help?

    Code:
        groups:
            Default:
                default: true
                info:
                    build: true
                permissions:
                    - -bukkit.commands.plugins
                    - essentials.help
                    - essentials.home
                    - essentials.motd
                    - essentials.rules
                    - essentials.sethome
                    - essentials.balance
                    - essentials.pay
                    - essentials.worth
                    - essentials.afk
                    - essentials.compass
                    - essentials.getpos
                    - essentials.ignore
                    - essentials.helpop
                    - essentials.info
                    - essentials.list
                    - essentials.mail
                    - essentials.mail.send
                    - essentials.near
                    - essentials.msg
                    - essentials.seen
                    - essentials.suicide
                    - essentials.gc
                    - essentials.ping
            Moderators:
                default: false
                info:
                    build: true
                inheritance:
                    - Default
                permissions:
                    - essentials.tp
                    - essentials.tphere
                    - bukkit.commands.plugins
                    - bukkit.command.help
                    - bukkit.command.kick
                    - bukkit.command.ban.list
                    - bukkit.command.list
                    - bukkit.command.whitelist.list
                    - essentials.balance.others
                    - essentials.balance.top
                    - essentials.afk.kickexempt
                    - essentials.afk.others
                    - essentials.getpos.others
                    - essentials.list.hidden
                    - essentials.helpop.receive
                    - essentials.itemdb
                    - essentials.list.hidden
                    - essentials.msg.url
                    - essentials.seen.banreason
                    - essentials.whois
                    - essentials.invsee
                    - essentials.jails
                    - essentials.mute
                    - essentials.mute.exempt
                    - essentials.socialspy
                    - essentials.sudo.exempt
                    - essentials.tempban
                    - essentials.tempban.exempt
                    - essentials.togglejail
                    - essentials.togglejail.exempt
            HeadModerators:
                default: false;
                info:
                    build: true
                inheritance:
                    - Moderators
                permissions:
                    - essentials.broadcast
                    - essentials.invsee.modify
                    - essentials.kickall
                    - essentials.sudo
                    - essentials.unban.*
                    - essentials.ban.*
            Architects:
                default: false
                info:
                    build: true
                inheritance:
                    - HeadModerators
                permissions:
                    - Orebfuscator.deobfuscate
                    - essentials.fly
                    - essentials.fly.others
                    - essentials.tree
                    - essentials.gamemode
                    - essentials.gamemode.others
            Novelists:
                default: false
                info:
                    build: true
            Admins:
                default: false
                info:
                    build: true
                permissions:
                    - '*'
        users:
     
        messages:
            build: '&cYou do not have permission to build here.'
        debug: false
     
  14. Offline

    Snowy007


    There is so much wrong, i don't even know where to start. xD

    1. There is an empty line in your config just below 'users:'. Never use empty lines.
    2. Where the hell do you people get 'default: true' and 'info:' from? I mean... it has nothing to do with this plugin, it simply doesn't work.
    3. Permission nodes should not start with a - sign.
    4. All permission nodes need 'true' or 'false' behind them.
    5. The permission node '*' is NOT going to work.

    I'm guessing that this configuration file belongs to a completely different permissions plugin. If you are actually using PermissionBukkit and not something else, you probably just want to delete the config and let it regenerate. If you still can't figure out how a config should look like, then take a look at any of the 100 configs in these comments that i have fixed for people.
     
  15. Offline

    JBL

    That was actually really helpful. I think the confusing thing for new server admins like me is that there is so many different Permissions options and trying to find out the right syntax etc to use seems to have ended up with me having a jumble of lots of types.

    I have changed the Permissions config from your suggestions, is it right in using permissions.* to grant ALL permissions for said group or user?

    If you wanted to look again to make sure it's still all good I'd appreciate.. :

    Code:
    groups:
        Default:
            permissions:
                bukkit.commands.plugins: false
                essentials.help: true
                essentials.home: true
                essentials.motd: true
                essentials.rules: true
                essentials.sethome: true
                essentials.balance: true
                essentials.pay: true
                essentials.worth: true
                essentials.afk: true
                essentials.compass: true
                essentials.getpos: true
                essentials.ignore: true
                essentials.helpop: true
                essentials.info: true
                essentials.list: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.near: true
                essentials.msg: true
                essentials.seen: true
                essentials.suicide: true
                essentials.gc: true
                essentials.ping: true
        Moderators:
            inheritance:
                - Default
            permissions:
                essentials.tp: true
                essentials.tphere: true
                bukkit.commands.plugins: true
                bukkit.command.help: true
                bukkit.command.kick: true
                bukkit.command.ban.list: true
                bukkit.command.list: true
                bukkit.command.whitelist.list: true
                essentials.balance.others: true
                essentials.balance.top: true
                essentials.afk.kickexempt: true
                essentials.afk.others: true
                essentials.getpos.others: true
                essentials.list.hidden: true
                essentials.helpop.receive: true
                essentials.itemdb: true
                essentials.list.hidden: true
                essentials.msg.url: true
                essentials.seen.banreason: true
                essentials.whois: true
                essentials.invsee: true
                essentials.jails: true
                essentials.mute: true
                essentials.mute.exempt: true
                essentials.socialspy: true
                essentials.sudo.exempt: true
                essentials.tempban: true
                essentials.tempban.exempt: true
                essentials.togglejail: true
                essentials.togglejail.exempt: true
        HeadModerators:
            inheritance:
            - Moderators
            permissions:
                essentials.broadcast: true
                essentials.invsee.modify: true
                essentials.kickall: true
                essentials.sudo: true
                essentials.unban.*: true
                essentials.ban.*: true
        Architects:
            inheritance:
            - HeadModerators
            permissions:
                Orebfuscator.deobfuscate: true
                essentials.fly: true
                essentials.fly.others: true
                essentials.tree: true
                essentials.gamemode: true
                essentials.gamemode.others: true
        Novelists:
        VIP:
        Admins:
            permissions:
                permissions.*: true
    users:
        jbl:
            groups:
            - Admins
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    Oh and I see a user above was mentioning that their not everyone else was defaulting to the 'default' group, I have users that have already been on the server before you helped me fix the permissions, just checked and none of them have gone into the default group, understandable as it has been changed and I haven't added them manually.. but will in future all users default to the 'default' group? Is that a standard behaviour of PermissionsBukkit?
     
  16. Offline

    Snowy007

    I changed a few small things that probably shouldn't matter much.
    1. I moved the 'users:' part to the top of the file instead of in the middle. Its how it is in a default config and looks a bit better in my opinion.
    2. I moved the 'inheritance:' to the bottom of each group. Same reason as above.
    3. I changed 'Default:' into 'default' (notice that i changed the capital letter to a small one) Not sure if it matters but since this plugin is quite strict with the config you can be sure that this works.

    The 'permissions.*: true' node does NOT give all permissions of all plugins. This plugin does not have a node that grants everything. The node you used gives access to all of PermissionsBukkit commands. (changing peoples groups, etc...) If you want a user to have access to ALL the commands... then you should make him an Operator with the /op command. Operators automatically have everything. For your admin group you should probably just give all permissions of all plugins. For example 'essentials.*: true' will give all the essentials permissions. to the group.

    All the users that are not in the config should automatically have all the 'default' group permissions. They will not actually be added to the config when they join but if the plugin sees that they don't have a group specified, it will automatically know that they should be in the group named 'default'.

    Code:
    users:
        jbl:
            groups:
            - Admins
    groups:
        default:
            permissions:
                bukkit.commands.plugins: false
                essentials.help: true
                essentials.home: true
                essentials.motd: true
                essentials.rules: true
                essentials.sethome: true
                essentials.balance: true
                essentials.pay: true
                essentials.worth: true
                essentials.afk: true
                essentials.compass: true
                essentials.getpos: true
                essentials.ignore: true
                essentials.helpop: true
                essentials.info: true
                essentials.list: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.near: true
                essentials.msg: true
                essentials.seen: true
                essentials.suicide: true
                essentials.gc: true
                essentials.ping: true
        Moderators:
            permissions:
                essentials.tp: true
                essentials.tphere: true
                bukkit.commands.plugins: true
                bukkit.command.help: true
                bukkit.command.kick: true
                bukkit.command.ban.list: true
                bukkit.command.list: true
                bukkit.command.whitelist.list: true
                essentials.balance.others: true
                essentials.balance.top: true
                essentials.afk.kickexempt: true
                essentials.afk.others: true
                essentials.getpos.others: true
                essentials.list.hidden: true
                essentials.helpop.receive: true
                essentials.itemdb: true
                essentials.list.hidden: true
                essentials.msg.url: true
                essentials.seen.banreason: true
                essentials.whois: true
                essentials.invsee: true
                essentials.jails: true
                essentials.mute: true
                essentials.mute.exempt: true
                essentials.socialspy: true
                essentials.sudo.exempt: true
                essentials.tempban: true
                essentials.tempban.exempt: true
                essentials.togglejail: true
                essentials.togglejail.exempt: true
            inheritance:
                - default
        HeadModerators:
            permissions:
                essentials.broadcast: true
                essentials.invsee.modify: true
                essentials.kickall: true
                essentials.sudo: true
                essentials.unban.*: true
                essentials.ban.*: true
            inheritance:
            - Moderators
        Architects:
            permissions:
                Orebfuscator.deobfuscate: true
                essentials.fly: true
                essentials.fly.others: true
                essentials.tree: true
                essentials.gamemode: true
                essentials.gamemode.others: true
            inheritance:
            - HeadModerators
        Novelists:
        VIP:
        Admins:
            permissions:
                permissions.*: true
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
     
  17. Offline

    JBL

    Again, thank you, very helpful. I guess the only use for my Admins group will be IF this permissions plugin has prefix/suffix at all, does it? So I don't NEED to bother adding e.g. essentials.* to my admins because anyone who is in the operator file will have access to absolutely everything anyway.

    Cheers it's all a lot clearer for me now; going through every single command for every plugin to get it all exactly how I want it!
     
  18. Offline

    Snowy007

    Glad to hear!
    If you want prefixes and suffixes, i would recommend 'SimplePrefix'. Thats the plugin i use. But there are probably other alternatives too.
     
  19. Offline

    JBL

    Funny you should say that as I already found that one before reading this! I tried mChat and I was just like; I do NOT need this many features!

    Thanks again.
     
  20. Offline

    decorma

    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:
      Decorma:
        groups:
        - Owner
      treeyoyo:
        groups:
        - Admins
    groups:
      default:
        permissions:
          bukkit.commands.plugins: false
          essentials.help: true
          essentials.home: true
          essentials.motd: true
          essentials.rules: true
          essentials.sethome: true
          essentials.balance: true
          essentials.pay: true
          essentials.worth: true
          essentials.afk: true
          essentials.compass: true
          essentials.getpos: true
          essentials.ignore: true
          essentials.helpop: true
          essentials.info: true
          essentials.list: true
          essentials.mail: true
          essentials.mail.send: true
          essentials.msg: true
          essentials.seen: true
          essentials.suicide: true
          essentials.gc: true
          essentials.ping: true
      Moderators:
        permissions:
          essentials.tp: true
          essentials.tphere: true
          bukkit.commands.plugins: true
          bukkit.command.help: true
          bukkit.command.kick: true
          bukkit.command.ban.list: true
          bukkit.command.list: true
          bukkit.command.whitelist.list: true
          essentials.balance.others: true
          essentials.balance.top: true
          essentials.afk.kickexempt: true
          essentials.afk.others: true
          essentials.getpos.others: true
          essentials.list.hidden: true
          essentials.helpop.receive: true
          essentials.itemdb: true
          essentials.msg.url: true
          essentials.seen.banreason: true
          essentials.whois: true
          essentials.invsee: true
          essentials.jails: true
          essentials.mute: true
          essentials.mute.exempt: true
          essentials.socialspy: true
          essentials.sudo.exempt: true
          essentials.tempban: true
          essentials.tempban.exempt: true
          essentials.togglejail: true
          essentials.togglejail.exempt: true
        inheritance:
        - default
      HeadModerators:
        permissions:
          essentials.broadcast: true
          essentials.invsee.modify: true
          essentials.kickall: true
          essentials.sudo: true
          essentials.unban.*: true
          essentials.ban.*: true
        inheritance:
        - Moderators
      Architects:
        permissions:
          simpleprefix.Architects: true
          essentials.fly: true
          essentials.fly.others: true
          essentials.tree: true
          essentials.gamemode: true
          essentials.gamemode.others: true
        inheritance:
        - HeadModerators
      Admins:
        permissions:
          simpleprefix.Admins: true
          simpleprefix.Architects: false
          permissions.*: true
      Owner:
        permissions:
          simpleprefix.Admins: false
          simpleprefix.Architects: false
          simpleprefix.Owner: true   
          permissions.*: true
        worlds:
          world: {}
    messages:
      build: '&cYou do not have permission to build here.'
    debug: true



    Code:
    23:26:07 [WARNING] Server permissions file permissions.yml is not valid YAML.
    java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Map
            at org.bukkit.craftbukkit.CraftServer.loadCustomPermissions(CraftServer.
    java:573)
            at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:244
    )
            at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:381)
            at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:368)
            at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:197)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:432)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    23:26:08 [INFO] Done (4.851s)! For help, type "help" or "?"
    When I'm in game trying to set perms I get the internal error message, please help?
     
  21. Offline

    Snowy007

    Try this, i removed
    Code:
        worlds:
          world: {}
    from the owner group. If you don't specify specific worlds you don't need this and i have never seen it been used with {} signs. Don't know if it will matter but i can't find anything else that might cause the error.

    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:
      Decorma:
        groups:
        - Owner
      treeyoyo:
        groups:
        - Admins
    groups:
      default:
        permissions:
          bukkit.commands.plugins: false
          essentials.help: true
          essentials.home: true
          essentials.motd: true
          essentials.rules: true
          essentials.sethome: true
          essentials.balance: true
          essentials.pay: true
          essentials.worth: true
          essentials.afk: true
          essentials.compass: true
          essentials.getpos: true
          essentials.ignore: true
          essentials.helpop: true
          essentials.info: true
          essentials.list: true
          essentials.mail: true
          essentials.mail.send: true
          essentials.msg: true
          essentials.seen: true
          essentials.suicide: true
          essentials.gc: true
          essentials.ping: true
      Moderators:
        permissions:
          essentials.tp: true
          essentials.tphere: true
          bukkit.commands.plugins: true
          bukkit.command.help: true
          bukkit.command.kick: true
          bukkit.command.ban.list: true
          bukkit.command.list: true
          bukkit.command.whitelist.list: true
          essentials.balance.others: true
          essentials.balance.top: true
          essentials.afk.kickexempt: true
          essentials.afk.others: true
          essentials.getpos.others: true
          essentials.list.hidden: true
          essentials.helpop.receive: true
          essentials.itemdb: true
          essentials.msg.url: true
          essentials.seen.banreason: true
          essentials.whois: true
          essentials.invsee: true
          essentials.jails: true
          essentials.mute: true
          essentials.mute.exempt: true
          essentials.socialspy: true
          essentials.sudo.exempt: true
          essentials.tempban: true
          essentials.tempban.exempt: true
          essentials.togglejail: true
          essentials.togglejail.exempt: true
        inheritance:
        - default
      HeadModerators:
        permissions:
          essentials.broadcast: true
          essentials.invsee.modify: true
          essentials.kickall: true
          essentials.sudo: true
          essentials.unban.*: true
          essentials.ban.*: true
        inheritance:
        - Moderators
      Architects:
        permissions:
          simpleprefix.Architects: true
          essentials.fly: true
          essentials.fly.others: true
          essentials.tree: true
          essentials.gamemode: true
          essentials.gamemode.others: true
        inheritance:
        - HeadModerators
      Admins:
        permissions:
          simpleprefix.Admins: true
          simpleprefix.Architects: false
          permissions.*: true
      Owner:
        permissions:
          simpleprefix.Admins: false
          simpleprefix.Architects: false
          simpleprefix.Owner: true 
          permissions.*: true
    messages:
      build: '&cYou do not have permission to build here.'
    debug: true
     
  22. Offline

    TheHackerPlayer

    THANK YOU ALOT!!! This is easy to setup. :) At First i didnt know but i found it.

    Here you derserve this: [diamond][diamond][diamond][diamond][diamond] and maybe [diamond][diamond][diamond]
    [stick]
    [stick] (Diamond Pickaxe)
     
  23. Offline

    KingAmles

    I am having problems with my config. This is basically what it looks like -
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        Spirit:
            permissions:
                permissions.build: false
                simpleprefix.spirit: true
            worlds:
                freebuild:
                permissions.build: true
        Deity:
            permissions:
                permissions.*: true
                guardian.rollback: true
                guardian.lookup: true
                simpleprefix.Deity: true
            inheritance:
            - Demigod
        Demigod:
            permissions
                uhome.limit.a
                simpleprefix.Demigod true
            inheritance:
            - Master
        Master
            permissions:
                uhome.limit.b
                commandbin.god: true
                simpleprefix.Master: true
            inheritance:
            - Godling
        Godling:
            permissions:
                uhome.limit.c
                Commandbin.fly: true
                simpleprefix.Godling: true
            inheritance:
            - Architect
        Architect:
            permissions:
                Commandbin.tp: true
                Commandbin.back: true
                uhome.limit.d
                simpleprefix.Architect: true
            inheritance:
            - Aprentice
        Aprentice:
            permissions:
                permissions.build: true
                Commandbin.ask: true
                Commandbin.accept: true
                Commandbin.afk: true
                Commandbin.deny: true
                Commandbin.spawn: true
                uhome.own.warp: true
                uhome.own.set: true
                uhome.own.list: true
                multiverse.access.*
                uhome.limit.e
                simpleprefix.Aprentice: true
            worlds:
                Elrinda:
                permissions.build: false
                Metropolis
                permissions.build: false
            inheritance:
            - Spirit
    messages:
        build: '&cYou do not have permission to build here.'
    Can anyone help. The server says that it is invalid, but I can't find anything wrong with it.
     
  24. Offline

    CrossmoRoar

    can someone help me? my server says it cant access the config.yml is some thing wrong? i placed the config in the permissionbukkit folder in the plugins folder
     
  25. Offline

    Snowy007

    You probably didn't look good enough cause there are plenty of mistakes. :p
    1. There are multiple nodes that don't have ': true' or ': false'. (the 'uhome' and 'multiverse' nodes.)
    2. There are multiple places where you forgot to put a ':' sign. (2 times in the 'demigod' group and at the bottom behind 'Metropolis'.)
    3. The indention for the world specific nodes isn't correct.
    4. You are missing the 'debug:' part in the bottom of the file.

    Here it is with all these things fixed. This should work fine unless i missed something. :p
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        Spirit:
            permissions:
                permissions.build: false
                simpleprefix.spirit: true
            worlds:
                freebuild:
                    permissions.build: true
        Deity:
            permissions:
                permissions.*: true
                guardian.rollback: true
                guardian.lookup: true
                simpleprefix.Deity: true
            inheritance:
            - Demigod
        Demigod:
            permissions:
                uhome.limit.a: true
                simpleprefix.Demigod: true
            inheritance:
            - Master
        Master:
            permissions:
                uhome.limit.b: true
                commandbin.god: true
                simpleprefix.Master: true
            inheritance:
            - Godling
        Godling:
            permissions:
                uhome.limit.c: true
                Commandbin.fly: true
                simpleprefix.Godling: true
            inheritance:
            - Architect
        Architect:
            permissions:
                Commandbin.tp: true
                Commandbin.back: true
                uhome.limit.d: true
                simpleprefix.Architect: true
            inheritance:
            - Aprentice
        Aprentice:
            permissions:
                permissions.build: true
                Commandbin.ask: true
                Commandbin.accept: true
                Commandbin.afk: true
                Commandbin.deny: true
                Commandbin.spawn: true
                uhome.own.warp: true
                uhome.own.set: true
                uhome.own.list: true
                multiverse.access.*: true
                uhome.limit.e: true
                simpleprefix.Aprentice: true
            worlds:
                Elrinda:
                    permissions.build: false
                Metropolis:
                    permissions.build: false
            inheritance:
            - Spirit
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    You shouldn't have to place anything in the permissionsbukkit folder as it automatically creates a config when it can't find any.
    Does it say that the config is 'invalid'?
    If thats the case, then there is something wrong inside of your config.
     
  26. Offline

    CrossmoRoar


    this is what my config looks like users:
    CrossmoRoar:
    permissions:
    permissions.*: true
    groups:
    - &cGod
    tron:
    groups:
    - boss
    groups:
    default:
    permissions:
    permissions.build: true
    spleefultimate.player.join:true
    spleefultimate.player.spectate :true
    boss:
    permissions:
    permissions.*: true
    essentials.*:false

    inheritance:
    - midgets
    midgets:
    permissions:
    permissions.build: true
    spleefultimate.player.join:true
    spleefultimate.player.spectate :true

    inheritance:
    - default
    &cGod:
    permissions.*:true
    inheritance:
    - boss
    messages:
    build: '&cYou do not have permission to build here.'
    debug: false

    and the error that appers is 'could not load the config.yml'

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

    Snowy007

    Next time, put your config in code tags. Its really hard to read like this when i can't see the indention. Also i can't check if you indented everything correctly like this.
    From looking at it like this i can already spot some mistakes though.
    1. There are 2 empty lines. Never use empty lines.
    2. Color codes don't work. You can't see the group name in-game anyway. You have to use another plugin for giving group prefixes in-game.
    3. I see a lot of permission nodes that aren't correct. A node should look like this: 'plugin.permission: true'. A lot of times you forgot the space between the ':' sign and 'true'. Also in 2 nodes you put a space between the node and the ':' sign.

    A bit surprised about the error you are getting though, most people get an error saying that the config is 'invalid', not that it can't load at all... Maybe check if the file permissions are correct and if the file isn't read-only.
     
  28. Offline

    KingAmles

    Thanks so much for that.
     
  29. Offline

    Frenchy777

    I don't know what is wrong with my config file but everytime I try to add someone to a group it says that an internal error has occurred! Here's a copy of my config file, any help would be much appreciated!

    # 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:
    ConspiracyWizard:
    permissions:
    permissions.example: true
    groups:
    - admin
    frenchy7777:
    groups:
    - civilian
    groups:
    default:
    permissions:
    permissions.build: false
    admin:
    permissions:
    permissions.*: true
    inheritance:
    - user
    Moderator:
    permissions:
    permissions.build: true
    - essentials.feed
    - essentials.fly
    - essentials.time
    - essentials.time.set
    - essentials.balance
    - essentials.balancetop
    - essentials.pay
    - essentials.worth
    - essentials.afk
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.getpos
    - essentials.help
    - essentials.help.[pluginname]
    - essentials.info
    - essentials.itemdb
    - essentials.list
    - essentials.list.hidden
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.motd
    - essentials.nick
    - essentials.msg
    - essentials.rules
    - essentials.seen
    - essentials.seen.banreason
    - essentials.suicide
    - essentials.whois
    - essentials.ban
    - essentials.ban.offline
    - essentials.banip
    - essentials.broadcast
    - essentials.burn
    - essentials.clearinventory
    - essentials.ext
    - essentials.invsee
    - essentials.jails
    - essentials.kick
    - essentials.kill
    - essentials.mute
    - essentials.nuke
    - essentials.ping
    - essentials.tempban
    - essentials.tempban.exempt
    - essentials.tempban.offline
    - essentials.thunder
    - essentials.togglejail
    - essentials.unban
    - essentials.unbanip
    - essentials.weather
    - essentials.spawn
    - essentials.back
    - essentials.back.ondeath
    - essentials.home
    - essentials.jump
    - essentials.sethome
    - essentials.setwarp
    - essentials.top
    - essentials.tp
    - essentials.tp.others
    - essentials.tpa
    - essentials.tpaall
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpall
    - essentials.tpdeny
    - essentials.tpo
    - essentials.world.<worldname>
    - essentials.tpohere
    - essentials.tppos
    - essentials.warp
    - essentials.warp.list
    - essentials.warp.otherplayers
    - essentials.world
    - essentials.chat.color
    - essentials.chat.format
    - essentials.chat.magic
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.chat.spy
    - essentials.chat.url
    - essentials.geoip.hide
    - essentials.geoip.show
    - essentials.protect
    - essentials.protect.alerts
    - essentials.protect.damage.contact
    - essentials.protect.damage.creeper
    - essentials.protect.damage.disable
    - essentials.protect.damage.drowning
    - essentials.protect.damage.fall
    - essentials.protect.damage.fire
    - essentials.protect.damage.fireball
    - essentials.protect.damage.lava
    - essentials.protect.damage.lightning
    - essentials.protect.damage.projectiles
    - essentials.protect.damage.suffocation
    - essentials.protect.damage.tnt
    - essentials.protect.entitytarget.bypass
    - essentials.protect.ownerinfo
    - essentials.signs.color
    - essentials.signs.create.balance
    - essentials.signs.create.heal
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.create.time
    - essentials.signs.create.trade
    - essentials.signs.create.warp
    - essentials.signs.magic
    - essentials.signs.use.balance
    - essentials.signs.use.buy
    - essentials.signs.use.disposal
    - essentials.signs.use.sell
    - essentials.signs.use.heal
    - essentials.signs.use.mail
    Legend:
    permissions:
    permissions.build: true
    - essentials.feed
    - essentials.fly
    - essentials.balance
    - essentials.balancetop
    - essentials.pay
    - essentials.worth
    - essentials.afk
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.getpos
    - essentials.help
    - essentials.help.[pluginname]
    - essentials.info
    - essentials.itemdb
    - essentials.list
    - essentials.list.hidden
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.motd
    - essentials.nick
    - essentials.msg
    - essentials.rules
    - essentials.seen
    - essentials.seen.banreason
    - essentials.suicide
    - essentials.whois
    - essentials.clearinventory
    - essentials.ping
    - essentials.back
    - essentials.back.ondeath
    - essentials.home
    - essentials.jump
    - essentials.sethome
    - essentials.top
    - essentials.tp
    - essentials.tpa
    - essentials.tpaall
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpall
    - essentials.tpdeny
    - essentials.world.<worldname>
    - essentials.tppos
    - essentials.warp
    - essentials.warp.list
    - essentials.world
    - essentials.chat.color
    - essentials.chat.format
    - essentials.chat.magic
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.chat.spy
    - essentials.chat.url
    - essentials.geoip.hide
    - essentials.geoip.show
    - essentials.protect
    - essentials.protect.alerts
    - essentials.protect.damage.contact
    - essentials.protect.damage.creeper
    - essentials.protect.damage.disable
    - essentials.protect.damage.drowning
    - essentials.protect.damage.fall
    - essentials.protect.damage.fire
    - essentials.protect.damage.fireball
    - essentials.protect.damage.lava
    - essentials.protect.damage.lightning
    - essentials.protect.damage.projectiles
    - essentials.protect.damage.suffocation
    - essentials.protect.damage.tnt
    - essentials.protect.entitytarget.bypass
    - essentials.protect.ownerinfo
    - essentials.signs.color
    - essentials.signs.create.balance
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.create.trade
    - essentials.signs.magic
    - essentials.signs.use.balance
    - essentials.signs.use.buy
    - essentials.signs.use.disposal
    - essentials.signs.use.sell
    - essentials.signs.use.heal
    - essentials.signs.use.mail
    Elite:
    permissions:
    permissions.build: true
    - essentials.feed
    - essentials.balance
    - essentials.balancetop
    - essentials.pay
    - essentials.worth
    - essentials.afk
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.getpos
    - essentials.help
    - essentials.help.[pluginname]
    - essentials.info
    - essentials.itemdb
    - essentials.list
    - essentials.list.hidden
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.motd
    - essentials.msg
    - essentials.rules
    - essentials.seen
    - essentials.seen.banreason
    - essentials.suicide
    - essentials.whois
    - essentials.clearinventory
    - essentials.ping
    - essentials.back
    - essentials.back.ondeath
    - essentials.home
    - essentials.sethome
    - essentials.top
    - essentials.tp
    - essentials.tpa
    - essentials.tpaall
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpall
    - essentials.tpdeny
    - essentials.tppos
    - essentials.warp
    - essentials.warp.list
    - essentials.chat.color
    - essentials.chat.format
    - essentials.chat.magic
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.chat.url
    - essentials.geoip.hide
    - essentials.geoip.show
    - essentials.protect
    - essentials.protect.alerts
    - essentials.protect.damage.contact
    - essentials.protect.damage.creeper
    - essentials.protect.damage.disable
    - essentials.protect.damage.drowning
    - essentials.protect.damage.fall
    - essentials.protect.damage.fire
    - essentials.protect.damage.fireball
    - essentials.protect.damage.lava
    - essentials.protect.damage.lightning
    - essentials.protect.damage.projectiles
    - essentials.protect.damage.suffocation
    - essentials.protect.damage.tnt
    - essentials.protect.entitytarget.bypass
    - essentials.protect.ownerinfo
    - essentials.signs.color
    - essentials.signs.create.balance
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.create.trade
    - essentials.signs.magic
    - essentials.signs.use.balance
    - essentials.signs.use.buy
    - essentials.signs.use.disposal
    - essentials.signs.use.sell
    - essentials.signs.use.heal
    - essentials.signs.use.mail
    HOOKERZ:
    permissions:
    permissions.build: true
    - essentials.balance
    - essentials.balancetop
    - essentials.pay
    - essentials.worth
    - essentials.afk
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.getpos
    - essentials.help
    - essentials.help.[pluginname]
    - essentials.info
    - essentials.itemdb
    - essentials.list
    - essentials.list.hidden
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.motd
    - essentials.msg
    - essentials.rules
    - essentials.seen
    - essentials.seen.banreason
    - essentials.suicide
    - essentials.whois
    - essentials.clearinventory
    - essentials.ping
    - essentials.back
    - essentials.back.ondeath
    - essentials.home
    - essentials.sethome
    - essentials.top
    - essentials.tp
    - essentials.tpa
    - essentials.tpaall
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpall
    - essentials.tpdeny
    - essentials.tppos
    - essentials.chat.color
    - essentials.chat.format
    - essentials.chat.magic
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.chat.url
    - essentials.geoip.hide
    - essentials.geoip.show
    - essentials.protect
    - essentials.protect.alerts
    - essentials.protect.damage.contact
    - essentials.protect.damage.creeper
    - essentials.protect.damage.disable
    - essentials.protect.damage.drowning
    - essentials.protect.damage.fall
    - essentials.protect.damage.fire
    - essentials.protect.damage.fireball
    - essentials.protect.damage.lava
    - essentials.protect.damage.lightning
    - essentials.protect.damage.projectiles
    - essentials.protect.damage.suffocation
    - essentials.protect.damage.tnt
    - essentials.protect.entitytarget.bypass
    - essentials.protect.ownerinfo
    - essentials.signs.color
    - essentials.signs.create.balance
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.create.trade
    - essentials.signs.magic
    - essentials.signs.use.balance
    - essentials.signs.use.buy
    - essentials.signs.use.disposal
    - essentials.signs.use.sell
    - essentials.signs.use.heal
    - essentials.signs.use.mail
    Civilian:
    permissions:
    permissions.build: true
    - essentials.balance
    - essentials.balancetop
    - essentials.pay
    - essentials.worth
    - essentials.afk
    - essentials.compass
    - essentials.depth
    - essentials.getpos
    - essentials.getpos
    - essentials.help
    - essentials.help.[pluginname]
    - essentials.info
    - essentials.itemdb
    - essentials.list
    - essentials.list.hidden
    - essentials.mail
    - essentials.mail.send
    - essentials.me
    - essentials.motd
    - essentials.msg
    - essentials.rules
    - essentials.seen
    - essentials.seen.banreason
    - essentials.suicide
    - essentials.whois
    - essentials.clearinventory
    - essentials.ping
    - essentials.home
    - essentials.sethome
    - essentials.top
    - essentials.tp
    - essentials.tpa
    - essentials.tpaall
    - essentials.tpaccept
    - essentials.tpahere
    - essentials.tpall
    - essentials.tpdeny
    - essentials.chat.color
    - essentials.chat.format
    - essentials.chat.magic
    - essentials.chat.question
    - essentials.chat.shout
    - essentials.chat.url
    - essentials.geoip.hide
    - essentials.geoip.show
    - essentials.protect
    - essentials.protect.alerts
    - essentials.protect.damage.contact
    - essentials.protect.damage.creeper
    - essentials.protect.damage.disable
    - essentials.protect.damage.drowning
    - essentials.protect.damage.fall
    - essentials.protect.damage.fire
    - essentials.protect.damage.fireball
    - essentials.protect.damage.lava
    - essentials.protect.damage.lightning
    - essentials.protect.damage.projectiles
    - essentials.protect.damage.suffocation
    - essentials.protect.damage.tnt
    - essentials.protect.entitytarget.bypass
    - essentials.protect.ownerinfo
    - essentials.signs.color
    - essentials.signs.create.balance
    - essentials.signs.create.mail
    - essentials.signs.create.protection
    - essentials.signs.magic
    - essentials.signs.use.balance
    - essentials.signs.use.buy
    - essentials.signs.use.disposal
    - essentials.signs.use.sell
    - essentials.signs.use.heal
    - essentials.signs.use.mail




    messages:
    build: '&cYou do not have permission to build here.'
    command: '&cPlease upgrade for use of more commands.'
    debug: false
     
  30. Offline

    Snowy007

    Please put that in code tags. I can't see any indention this way and its really hard to read like this.

    After taking a quick look i can already tell you that pretty much ALL of your permission nodes are incorrect. first of all, don't list them with a - sign. Second, every node needs 'true' or 'false' behind them.
    also there seem to be lots of empty lines at the bottom. Don't use empty lines.
    Look throughout this forum for hundreds of examples of how a config should look like.
     
  31. Offline

    kagecookeh

    Could i request a feature? Make it so an admin can set a player into Multiple Groups? Like an player can be Builder AND a donator, for a donator gets special ranks... i need this feature for a special need on my multiplayer server. Thanks :D , also Thanks ! nice plugin.
     

Share This Page