[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

    Aelanna

    Will this plugin be updated to 1.4.7? I'm running version 2.1, which states it's for MC 1.3.1 R2, which is quite a bit outdated...
     
  3. Offline

    13era

    Having a lot of issues getting the latest dev version to work with 1.4.7 - the config.yml namely.

    Here is what happens.

    My config file is as follows:
    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:
    13era:
    permissions:
    bukkit.commands.op: true
     
    bukkit.commands.deop: true
     
    permissions.build: true
     
     
    groups:
    default:
    permissions:
     
    essentials.tpaccept: true
     
    essentials.tpdeny: true
     
    essentials.sethome: true
     
    essentials.home: true
     
    essentials.delhome: true
     
     
    admin:
    suffix: A
    permissions:
     
    permissions.*: true
     
    essentials.*: true
     
    worldguard.*: true
     
    worldedit.*: true
     
    silkspawners.*: true
    groupmanager.*: true
     
    alchemicalcauldron.*: true
     
    inheritance:
     
    - mods
     
     
    mods:
    suffix: M
    permissions:
    essentials.kick: true
     
    essentials.kill: true
     
    essentials.tempban: true
     
    essentials.ban: true
     
    essentials.unban: true
     
    essentials.tpa: true
     
    essentials.tp: true
     
    inheritance:
    - default
    when doing /permissions reload, it says reload was completed fine. However upon doing /permissions group list it replies with NOTHING, and behaves as if there is not a single group present except default.
    Upon reopening the file after doing the reload, the file changes to:

    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.
     
     
     
     
    bukkit.commands.op: true
    bukkit.commands.deop: true
    permissions.build: true
    essentials.tpaccept: true
    essentials.tpdeny: true
    essentials.sethome: true
    essentials.home: true
    essentials.delhome: true
    suffix: M
    permissions.*: true
    essentials.*: true
    worldguard.*: true
    worldedit.*: true
    silkspawners.*: true
    groupmanager.*: true
    alchemicalcauldron.*: true
    inheritance:
    - default
    essentials.kick: true
    essentials.kill: true
    essentials.tempban: true
    essentials.ban: true
    essentials.unban: true
    essentials.tpa: true
    essentials.tp: true
    
    No matter what i do, how i save, what i change, it just keeps reverting to this. And i cant get it to work :/
     
  4. Offline

    Vern8k

    AFAICT, Bukkit's permissions API hasn't been changed for a while, hence PermissionsBukkit doesn't need to be updated. It runs fine on my 1.4.7-R1.0 server.

    Your config.yml as posted doesn't have the spaced indents as shown in the PermissionsBukkit config page or in my example posted here. Also, suffix (and prefix) isn't built into Superperms (which PermissionsBukkit is based on). If you're using Essentials chat, configure prefixes/suffixes in the Essentials config.
     
  5. Offline

    Chriskerr0

    My Permissions... why cant my mods add people to groups. i want my mods to be able to add peope to the builder group


    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:
     
      elliottb92:
     
        permissions:
     
          bukkit.command.teleport: true
     
          bukkit.command.time.set: true
     
          bukkit.command.ban.player: true
     
          bukkit.command.kick: true
     
          bukkit.command.weather: true
     
        groups:
     
        - Admin
     
      chriskerr0:
     
        permissions:
     
        groups:
     
        - Owner
     
      Jugglerwill:
     
        permissions:
     
          bukkit.command.weather: true
     
          bukkit.command.time.set: true
     
        groups:
     
        - Mod
     
      Scorpion812:
     
        permissions:
     
          bukkit.command.weather: true
     
          bukkit.command.time.set: true
     
          bukkit.command.ban.player: true
     
          bukkit.command.kick: true
     
        groups:
     
        - SuperMOD
     
      65_mustang_kid:
     
        permissions:
     
          bukkit.command.weather: true
     
          permissions.*: true
     
        groups:
     
        - MOD
     
      commando710:
     
        groups:
     
        - builder
     
      ceejayjaydub:
     
        groups:
     
        - builder
     
      dog124579:
     
        groups:
     
        - builder
     
      diamondking130:
     
        groups:
     
        - builder
     
      diamondlord130:
     
        groups:
     
        - builder
     
      flower38:
     
        groups:
     
        - builder
     
      kubekrusher1:
     
        groups:
     
        - builder
     
      matt105321:
     
        groups:
     
        - builder
     
      minininja2018:
     
        groups:
     
        - builder
     
      ninjaryry:
     
        groups:
     
        - builder
     
      jaydubceejay:
     
        groups:
     
        - builder
     
    groups:
     
      default:
     
        permissions:
     
          simpleprefix.default: true
     
          permissions.build: false
     
          bukkit.command.seed: true
     
      Admin:
     
        permissions:
     
          permissions.*: true
     
          simpleprefix.Admin: true
     
          bukkit.command.teleport: true
     
          bukkit.command.time.set: true
     
          bukkit.command.ban.player: true
     
          bukkit.command.kick: true
     
          bukkit.command.weather: true
     
        inheritance:
     
        - MOD
     
        - builder
     
      Owner:
     
        permissions:
     
          permissions.*: true
     
          simpleprefix.Owner: true
     
        inheritance:
     
        - builder
     
        - admin
     
      MOD:
     
        permissions:
     
          permissions.*: true
     
          simpleprefix.MOD: true
     
          bukkit.command.weather: true
     
          bukkit.command.time.set: true
     
        inheritance:
     
        - builder
     
      SuperMOD:
     
        permissions:
     
          permissions.*: true
     
          simpleprefix.SuperMOD: true
     
          bukkit.command.weather: true
     
          bukkit.command.time.set: true
     
          bukkit.command.ban.player: true
     
          bukkit.command.kick: true
     
        inheritance:
     
        - builder
     
        - MOD
     
      Builder:
     
        permissions:
     
          permissions.*: false
     
          simpleprefix.Builder: true
     
          permissions.build: true
     
        inheritance:
     
        - default
     
     
     
    messages:
     
      build: '&cYou do not have permission to build here.'
     
    debug: false
     
    
     

    Attached Files:

  6. Offline

    Alundra

    Feel like an idiot but we can't get default users to be able to place blocks or use items like picks and so on :(

    http://pastebin.com/1JfLn2V4

    EDIT: Okay I fixed it, it was Essentials Anti Build... I added this and everything is dandy!
    essentials.build: true

    Thanks :D.
     
  7. Offline

    elWanderero

    Are they using the setrank? permissions.* does not map to this, you have to add one for each rank, permissions.setrank.builder: true, permissions.setrank.MOD: true, etc. Also I hope that you realise that by giving permissions.*: true to people you are giving them complete control of everything bar server console. They can just change the permissions to give themselves perms to whatever they want to do, such as making themselves ops... You might want to be more restrictive.
     
  8. Offline

    wowmaster196

    Hello, my name is wowmaster196 and I have been having some permissionsbukkit problems. I first use bpermissions and that did not work out so I tried permissionsbukkit. It took me about two days to figure out the format and stuff. I created my permissions (basic) and everything worked. The default group could do /spawn and /home and all of their commands. After that I decided I needed to set more groups and more perms (mod, admin, etc.) So I added a whole bunch of new permissions and I load my server... No one can do anything (accept OPs) So I go back into my config files and everything is still there. When i am on my server and I do /permissions group list it says and internal error has occured and if I try and do anything with perms in-game it resets my config back to normal. Please help, here is my config file.

    (Config File In Post Below)

    If there is anything anyone can do please tell me. I would really like to open my server as soon as possible.
    If you have any questions or think you know the solution please do not hesitate to msg me or reply.

    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.
     
    groups:
      default:
        permissions:
          essentials.spawn: true
          essentials.tpa: true
          essentials.tpaccept: true
          essentials.signs.use.disposal: true
          essentials.signs.use.sell: true
          essentials.signs.use.buy: true
          essentials.delhome: true
          essentials.help: true
          essentials.home: true
          essentials.helpop: true
          essentials.ignore: true
          essentials.list: true
          essentials.mail: true
          essentials.mail.send: true
          essentials.motd: true
          essentials.msg: true
          essentials.rules: true
          essentials.spawn: true
          essentials.tpaccept: true
          essentials.who: true
          multiverse.access.*: true
          multiverse.portal.access.*: true
          simplespleef.command.spleef: true
          arena.paintball.join: true
          essentials.kit: true
          essentials.balance: true
          essentials.balancetop: true
          essentials.pay: true
          essentials.afk.auto: true
          essentials.mute.notify: true
          essentials.kit: true
        world:
          Sky:
            permissions:
              permissions.build: true
              essentials.sethome: true
              essentials.spawn: false
              skybukkit.island.create: true
              skybukkit.island.destroy: true
              skybukkit.island.replace: true
              skybukkit.tp.home: true
              skybukkit.tp.spawn: true
              skybukkit.party.invite: true
              skybukkit.party.kick: true
              skybukkit.party.promote: true
              skybukkit.party.accept: true
              skybukkit.party.decline: true
              skybukkit.party.leave: true
              skybukkit.party.members: true
      vip:
        permissions:
          essentials.enderchest:true
          essentials.keepxp: true
          essentials.balance.others: true
          essentials.whois: true
          essentials.nick.color: true
          essentials.workbench: true
          essentials.ptime: true
          essentials.feed: true
        inheritance:
        - default
      tr-mod:
        permissions:
          essentials.tempban: true
          essentials.mute: true
          essentials.kick: true
          essentials.balance.others: true
          essentials.togglejail: true
          essentials.chat.ignoreexempt: true
        inheritance:
        - default
      mod:
        permissions:
          essentials.ban: true
          essentials.helpop.receive: true
          essentials.banip: true
        inheritance:
        - tr-mod
      tr-admin:
        permissions:
          essentials.unban: true
          essentials.fly: true
          essentials.fly.safelogin: true
          essentials.sudo.exempt: true
          essentials.vanish.see: true
          essentials.weather: true
          essentials.joinfullserver: true
          essentials.back: true
          essentials.list.hidden: true
          essentials.feed.others: true
          essentials.broadcast: true
          essentials.invsee: true
          essentials.enderchest.others: true
          essentials.workbench: true
        inheritance:
        - mod
      admin:
        permissions:
          permissions.*: true
          essentials.gamemode: true
          essentials.give: true
          essentials.god: true
          essentials.heal: true
          essentials.repair: true
          essentials.time.set: true
          essentials.socialspy: true
          essentials.vanish: true
          essentials.invsee.modify: true
          essentials.invsee.preventmodify: true
          essentials.kick.exempt: true
          essentials.burn: true
          essentials.enderchest.modify: true
          essentials.heal: true
          essentials.more: true
          essentials.kits.*: true
          skybukkit.admin.destroy: true
          skybukkit.admin.tp: true
        inheritance:
        - tr-admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
       
    
    Thanks,
    Wowmaster196

    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.
     
    groups:
      default:
        permissions:
          essentials.spawn: true
          essentials.tpa: true
          essentials.tpaccept: true
          essentials.signs.use.disposal: true
          essentials.signs.use.sell: true
          essentials.signs.use.buy: true
          essentials.delhome: true
          essentials.help: true
          essentials.home: true
          essentials.helpop: true
          essentials.ignore: true
          essentials.list: true
          essentials.mail: true
          essentials.mail.send: true
          essentials.motd: true
          essentials.msg: true
          essentials.rules: true
          essentials.spawn: true
          essentials.tpaccept: true
          essentials.who: true
          multiverse.access.*: true
          multiverse.portal.access.*: true
          simplespleef.command.spleef: true
          arena.paintball.join: true
          essentials.kit: true
          essentials.balance: true
          essentials.balancetop: true
          essentials.pay: true
          essentials.afk.auto: true
          essentials.mute.notify: true
          essentials.kit: true
        world:
          Sky:
            permissions:
              permissions.build: true
              essentials.sethome: true
              essentials.spawn: false
              skybukkit.island.create: true
              skybukkit.island.destroy: true
              skybukkit.island.replace: true
              skybukkit.tp.home: true
              skybukkit.tp.spawn: true
              skybukkit.party.invite: true
              skybukkit.party.kick: true
              skybukkit.party.promote: true
              skybukkit.party.accept: true
              skybukkit.party.decline: true
              skybukkit.party.leave: true
              skybukkit.party.members: true
      vip:
        permissions:
          essentials.enderchest:true
          essentials.keepxp: true
          essentials.balance.others: true
          essentials.whois: true
          essentials.nick.color: true
          essentials.workbench: true
          essentials.ptime: true
          essentials.feed: true
        inheritance:
        - default
      tr-mod:
        permissions:
          essentials.tempban: true
          essentials.mute: true
          essentials.kick: true
          essentials.balance.others: true
          essentials.togglejail: true
          essentials.chat.ignoreexempt: true
        inheritance:
        - default
      mod:
        permissions:
          essentials.ban: true
          essentials.helpop.receive: true
          essentials.banip: true
        inheritance:
        - tr-mod
      tr-admin:
        permissions:
          essentials.unban: true
          essentials.fly: true
          essentials.fly.safelogin: true
          essentials.sudo.exempt: true
          essentials.vanish.see: true
          essentials.weather: true
          essentials.joinfullserver: true
          essentials.back: true
          essentials.list.hidden: true
          essentials.feed.others: true
          essentials.broadcast: true
          essentials.invsee: true
          essentials.enderchest.others: true
          essentials.workbench: true
        inheritance:
        - mod
      admin:
        permissions:
          permissions.*: true
          essentials.gamemode: true
          essentials.give: true
          essentials.god: true
          essentials.heal: true
          essentials.repair: true
          essentials.time.set: true
          essentials.socialspy: true
          essentials.vanish: true
          essentials.invsee.modify: true
          essentials.invsee.preventmodify: true
          essentials.kick.exempt: true
          essentials.burn: true
          essentials.enderchest.modify: true
          essentials.heal: true
          essentials.more: true
          essentials.kits.*: true
          skybukkit.admin.destroy: true
          skybukkit.admin.tp: true
        inheritance:
        - tr-admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
       
    
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  9. Offline

    nuke21

    wowmaster196
    First thing I notice, is you have a class called "World" so that is probably messing things up.

    Try using this instead:
    Code:
        Sky:
            permissions:
                permissions.build: true
                essentials.sethome: true
                essentials.spawn: false
                skybukkit.island.create: true
                skybukkit.island.destroy: true
                skybukkit.island.replace: true
                skybukkit.tp.home: true
                skybukkit.tp.spawn: true
                skybukkit.party.invite: true
                skybukkit.party.kick: true
                skybukkit.party.promote: true
                skybukkit.party.accept: true
                skybukkit.party.decline: true
                skybukkit.party.leave: true
                skybukkit.party.members: true
    Also, remember you DO NOT use tab.

    The group names (SKY) is indented 4 spaces from the very left. The permissions tab (permissions is indented 8 spaces, and finally the actual permissions (permissions.build: true, essentials.spawn: false etc) are indented 12 spaces. This has to be done for it all to work. You might have accidently added a tab somewhere and that will mess things up. Or the fact that you had the word world as a class might have done it. Also, I don't know if it was intended, but your Sky class does not have an inheritance.
     
  10. Offline

    wowmaster196

    Ok so I was looking around and I added a few perms and used the proper spacing. It still did not fix it. Here is what console is saying and my new config file.

    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:
        wowmaster196:
            groups:
            - default     
    groups:
        default:
            default: true
            permissions:
                essentials.spawn: true
                essentials.tpa: true
                essentials.tpaccept: true
                essentials.signs.use.disposal: true
                essentials.signs.use.sell: true
                essentials.signs.use.buy: true
                essentials.signs.use.enchant: true
                essentials.signs.use.free: true
                essentials.signs.use.heal: true
                essentials.signs.use.repair: true
                essentials.signs.use.warp: true
                essentials.delhome: true
                essentials.help: true
                essentials.home: true
                essentials.helpop: true
                essentials.ignore: true
                essentials.list: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.motd: true
                essentials.msg: true
                essentials.rules: true
                essentials.spawn: true
                essentials.tpaccept: true
                essentials.who: true
                multiverse.access.*: true
                multiverse.portal.access.*: true
                simplespleef.command.spleef: true
                arena.paintball.join: true
                essentials.kit: true
                essentials.balance: true
                essentials.balancetop: true
                essentials.pay: true
                essentials.afk.auto: true
                essentials.mute.notify: true
                essentials.kit: true
            world:
                Sky:
                    permissions:
                        permissions.build: true
                        essentials.sethome: true
                        essentials.spawn: false
                        skybukkit.island.create: true
                        skybukkit.island.destroy: true
                        skybukkit.island.replace: true
                        skybukkit.tp.home: true
                        skybukkit.tp.spawn: true
                        skybukkit.party.invite: true
                        skybukkit.party.kick: true
                        skybukkit.party.promote: true
                        skybukkit.party.accept: true
                        skybukkit.party.decline: true
                        skybukkit.party.leave: true
                        skybukkit.party.members: true
        vip:
            permissions:
                essentials.enderchest:true
                essentials.balance.others: true
                essentials.whois: true
                essentials.nick.color: true
                essentials.workbench: true
                essentials.ptime: true
                essentials.feed: true
                essentials.hat: true
            inheritance:
            - default
        builder:
            permissions:
                modifyworld: true
                permissions.build: true
                essentials.gamemode: true
                essentials.mute: true
                essentials.kick: true
                essentials.tempban: true
                essentials.togglejail: true
                essentials.chat.ignoreexempt: true
                essentials.balance.others: true
            inheritance:
            - default
        tr-mod:
            permissions:
                essentials.tempban: true
                essentials.mute: true
                essentials.kick: true
                essentials.balance.others: true
                essentials.togglejail: true
                essentials.chat.ignoreexempt: true
            inheritance:
            - default
        mod:
            permissions:
                essentials.ban: true
                essentials.helpop.receive: true
                essentials.banip: true
            inheritance:
            - tr-mod
        tr-admin:
            permissions:
                essentials.unban: true
                essentials.fly: true
                essentials.fly.safelogin: true
                essentials.vanish.see: true
                essentials.weather: true
                essentials.joinfullserver: true
                essentials.back: true
                essentials.list.hidden: true
                essentials.feed.others: true
                essentials.broadcast: true
                essentials.invsee: true
                essentials.enderchest.others: true
                essentials.workbench: true
            inheritance:
            - mod
        admin:
            permissions:
                permissions.*: true
                essentials.gamemode: true
                essentials.give: true
                essentials.god: true
                essentials.heal: true
                essentials.repair: true
                essentials.time.set: true
                essentials.socialspy: true
                essentials.vanish: true
                essentials.invsee.modify: true
                essentials.invsee.preventmodify: true
                essentials.kick.exempt: true
                essentials.burn: true
                essentials.enderchest.modify: true
                essentials.heal: true
                essentials.more: true
                essentials.kits.*: true
                skybukkit.admin.destroy: true
                skybukkit.admin.tp: true
            inheritance:
            - tr-admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: true
     
    
    and console. These messages pop up when I do /permissions group list and it returns "An internal error has occurred"

    13.04 17:54:58 [Server] INFO ... 15 more
    13.04 17:54:58 [Server] INFO at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44)
    13.04 17:54:58 [Server] INFO at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:168)
    13.04 17:54:58 [Server] INFO at com.platymuus.bukkit.permissions.PermissionsCommand.groupCommand(PermissionsCommand.java:189)
    13.04 17:54:58 [Server] INFO Caused by: java.lang.NullPointerException
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.ThreadServerApplication.run(SourceFile:573)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.MinecraftServer.run(MinecraftServer.java:409)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.MinecraftServer.q(MinecraftServer.java:476)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.DedicatedServer.r(DedicatedServer.java:225)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.MinecraftServer.r(MinecraftServer.java:580)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.DedicatedServerConnection.b(SourceFile:30)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.ServerConnection.b(SourceFile:35)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.PlayerConnection.d(PlayerConnection.java:113)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.NetworkManager.b(NetworkManager.java:292)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.Packet3Chat.handle(Packet3Chat.java:44)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.PlayerConnection.a(PlayerConnection.java:840)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.PlayerConnection.chat(PlayerConnection.java:885)
    13.04 17:54:58 [Server] INFO at net.minecraft.server.v1_5_R1.PlayerConnection.handleCommand(PlayerConnection.java:967)
    13.04 17:54:58 [Server] INFO at org.bukkit.craftbukkit.v1_5_R1.CraftServer.dispatchCommand(CraftServer.java:514)
    13.04 17:54:58 [Server] INFO at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:186)
    13.04 17:54:58 [Server] INFO at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46)
    13.04 17:54:58 [Server] INFO org.bukkit.command.CommandException: Unhandled exception executing command 'permissions' in plugin PermissionsBukkit v2.0
    13.04 17:54:58 [Server] SEVERE null
    13.04 17:54:41 [Server] INFO list

    Thank you for the first fix now if we can only finish the job.
     
  11. Offline

    nuke21

    Make sure all of the plugins are up to date and make sure the tags are correct. For instance I didn't even know essentials did : essentials.socialspy : true. Is this maybe through another application called Social Spy? If so it shouldn't have essentials. infront of it. Also, to use this server version: http://dl.bukkit.org/downloads/craftbukkit/get/02084_1.5.1-R0.2/craftbukkit-beta.jar

    If that doesn't get rid of the errors then I think it is still your default : sky thing I talked about above.
     
  12. Offline

    wowmaster196

    Ok so I know essentials.socialspy: true is correct, I updated my craftbukkit.jar, and I took out Sky all together. it still did not work :/. I just don't know what to do. I might try to use permissonsex. I put it through a YML parser and it just said to take out all of the : after essentials.spawn: true. Thanks for your help. If you come up with anything else msg me.
     
  13. Offline

    nuke21

    When I had errors, I removed all the * commands. Meaning I manually added all the commands the asterix made. So like an top of my head example, instead of essentials.tpa*: true I added every one of the commands. Like essentials.tpa.accept: true, essentials.tpa. deny: true, essentials.tpa.change: true, bla bla bla. Also, I believe permissions.*: true for admin does not work. Last time I did that it didn't anyways, which is why I just went through and manually did each specific one for everything.

    This is my permissions and essentials yml. You should back up yours try these and just change your name from mine to yours in them and see if it works for you. If mine doesn't work for you then it is indeed a problem other than your yml. I, like you, made mine from scratch, but mine works flawlessly so check mine out and see if you still get problems.

    Permissions: <Edit by Moderator: Redacted mediafire url>

    Essentials: <Edit by Moderator: Redacted mediafire url>
     
    Last edited by a moderator: Nov 27, 2016
  14. Offline

    wowmaster196

    Thank you SO much!!! I changed around your config and uploaded it.. EVERYTHING WORKS! There is no way for me to show you how grateful I am right now! If you want to come on my server or anything ip is 198.12.126.169. You are already a mod :D Thank you so much and I wish for you to have a VERY nice day!
    Thanks,
    Wowmaster196
     
  15. Offline

    tomayas

    Need help some of my permissions arent working unless they are specifically put for a player and would not work if i just put it in the group they are in
     
  16. Offline

    nuke21

    wowmaster196

    No problem, glad I could help. If you ever need any help with anything else, let me know.
     
  17. Offline

    wowmaster196

    One more thing. The players on my server can not open chests, open doors, eat food, etc. Is there a permission node for that or do I need a separate plugin? If it is a plugin would you mind linking it?
    Thanks,
    Wowmaster196
     
  18. Offline

    nuke21

    You shouldn't need to change something at all. What group are the people that can not eat in? It might be a plugin you have effecting it. What other plugins are you using?
     
  19. Offline

    wowmaster196

    Sorry it has been so long since I responded, I had a few issues with my computer and stuff like that. Now on the topic of permissionsbukkit. Only OPs can eat food, interact with blocks, and open chests/doors. I am currently running the following plugins:
    ArenaPaintball
    ArenaSpleef
    BattleArena
    BattleTracker
    LogBlock
    DisguiseCraft
    Essentials (chat, spawn, protect, and antibuild)
    MobArena
    Multiverse-Core
    Multiverse-Inventories
    Multiverse-NetherPortals
    Multiverse-Portals
    Multiverse-SignPortals
    NPCWarehouse
    PermissionsBukkit
    PlayerHeads
    PluginMetrics
    SignShop
    SignUtilities
    Simple Prefix
    SimpleSpleef
    SkyBukkit
    SkyGrid
    WorldEdit
    WorldGuard
    If you find anything wrong with them please post. You have been so helpful.
    Thanks, Wowmaster196
     
  20. Offline

    nuke21

    Obviously one of those plugins are doing it. Your first thing you need to do is go to every single one and see if they are completely up to date. There actually might be a plugin to check for you. And then if that doesn't fix it, you need to backup your entire folder, then delete half of them and run the server. If it is fixed, it is a problem with one you deleted. If it still is broken, the ones you deleted are not the problem. You need to keep doing this until you find the one that is the problem. I run only a handful of plugins on my server, so I never encounter these conflicting issues.

    I assume one of your plugins need permission to eat, openchests, etc. Now you just have to figure out which one it is.
     
  21. Offline

    stoneminer02

    Uhm... "Essentials (chat, spawn, protect, and antibuild)"
    Antibuild -.-
    Remove this jar!
     
  22. Offline

    sniperdoc

    Sorry, minecraft permissions noob here. I just installed PermBukkit and I'm finding the wiki lacking in some of the rudimentary information. Maybe you folks can help...

    1. I am assuming that you can create additional groups in PermissionBukkit?
    2. Do I just manually add the groups in the config;
    3. and add the appropriate inheritances including whatever deny/allow permissions I want to add?
    4. Also, I find the order for the group's sub categories, such as permissions and inheritances illogical. Personally I'd prefer to see the inheritance of each group first, not last. Can I just change the order of the sub-categories?
    I feel that maybe a few examples of some modified permissions configs might help people understand (maybe preface them with the fact that if people try to copy and paste them into their configs and they don't have the appropriate plugins, the permissions may not function).

    Here's an error I get... and I don't understand, because the config file looks just fine??? It's the colon right after the first "permissions" statement...???

    Show Spoiler
    19:48:43 [SEVERE] [PermissionsBukkit] Failed to load configuration
    org.bukkit.configuration.InvalidConfigurationException: mapping values are not a
    llowed here
    in "<string>", line 4, column 16:
    permissions:
    ^

    at org.bukkit.configuration.file.YamlConfiguration.loadFromString(YamlCo
    nfiguration.java:55)
    at org.bukkit.configuration.file.FileConfiguration.load(FileConfiguratio
    n.java:138)
    at org.bukkit.configuration.file.FileConfiguration.load(FileConfiguratio
    n.java:105)
    at com.platymuus.bukkit.permissions.PermissionsPlugin.reloadConfig(Permi
    ssionsPlugin.java:78)
    at com.platymuus.bukkit.permissions.PermissionsPlugin.onEnable(Permissio
    nsPlugin.java:39)
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:217)
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader
    .java:457)
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManage
    r.java:381)
    at org.bukkit.craftbukkit.v1_5_R2.CraftServer.loadPlugin(CraftServer.jav
    a:282)
    at org.bukkit.craftbukkit.v1_5_R2.CraftServer.enablePlugins(CraftServer.
    java:264)
    at org.bukkit.craftbukkit.v1_5_R2.CraftServer.reload(CraftServer.java:60
    5)
    at org.bukkit.Bukkit.reload(Bukkit.java:185)
    at org.bukkit.command.defaults.ReloadCommand.execute(ReloadCommand.java:
    23)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:18
    9)
    at org.bukkit.craftbukkit.v1_5_R2.CraftServer.dispatchCommand(CraftServe
    r.java:523)
    at org.bukkit.craftbukkit.v1_5_R2.CraftServer.dispatchServerCommand(Craf
    tServer.java:512)
    at net.minecraft.server.v1_5_R2.DedicatedServer.am(DedicatedServer.java:
    261)
    at net.minecraft.server.v1_5_R2.DedicatedServer.r(DedicatedServer.java:2
    26)
    at net.minecraft.server.v1_5_R2.MinecraftServer.q(MinecraftServer.java:4
    76)
    at net.minecraft.server.v1_5_R2.MinecraftServer.run(MinecraftServer.java
    :409)
    at net.minecraft.server.v1_5_R2.ThreadServerApplication.run(SourceFile:5
    73)
    Caused by: mapping values are not allowed here
    in "<string>", line 4, column 16:
    permissions:
    ^


    Here's the config:
    Show Spoiler

    Code:
    # PermissionsBukkit configuration file
    users:
      Sniperdoc
        permissions:
          lwc.admin: true
        inheritance:
        - admin
      Machismo69
        permissions:
          lwc.mod: true
          lwc.admin.remove: false
        inheritance:
         - admin
    groups:
      default:
        permissions:
          permissions.build: false
          lwc.protect: false
      admin:
        permissions:
          permissions.*: true
        inheritance:
         - user
      user:
        permissions:
          permissions.build: true
          lwc.protect: true
        worlds:
          creative:
            coolplugin.item: true
        inheritance:
         - default
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    
     
  23. Offline

    Kittsforhitts

    Hello!
    I'm myself an PEX user(thus: i'm not really familiar with how PermissionBukkit works..). But i saw your post and i think this will work fine for you.

    Corrected version:
    Show Spoiler
    Code:
    users:
        Sniperdoc:
            permissions:
                lwc.admin: true
            inheritance:
                - admin
    users:
        Machismo69:
            permissions:
                lwc.mod: true
                lwc.admin.remove: false
            inheritance:
                - admin
    groups:
      default:
        permissions:
          permissions.build: false
          lwc.protect: false
      admin:
        permissions:
          permissions.*: true
        inheritance:
        - user
      user:
        permissions:
          permissions.build: true
          lwc.protect: true
        worlds:
          creative:
            coolplugin.item: true
        inheritance:
        - default
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
     
    


    I've corrected it with http://yaml-online-parser.appspot.com/ which is a REALLY cool site. It updates real time, as you move things around. So you'll see when there's no error anymore.

    I hope it all works out fine for you, be well!
     
    sniperdoc likes this.
  24. Offline

    sniperdoc

    Kittsforhitts: Thanks... I should have come back and updated that I found the error... it was a missing ":" after the users names. I found this out after I deleted the config and let it rebuild a default one... thank you for your response and effort though. Much appreciated.
     
  25. Offline

    brixazure

    okay so i down loaded and installed the plugin and i cant figure out how to configure it for the people on my server to use addons that require OP mode,( that i dont want them to have.) if i can get help in any way that would be great. :) two names im working on are my own (brixazure) and nathanbim once i get these 2 down i can do everyone i hope..​
    the add ons i want the users to use are​
    Simple Redstone Teleport​
    TARDIS and all its features​
    Multiverse​
    Secret Switches​
    Thank you all so much for the help/ configs.. :D
    Brixazure​
     
  26. Offline

    CBUJoshua345

    Okay, so I do everything right, except one class:
    Adminerator(Gold)
    permissions:
    permissions.*: true
    inheritance:
    - Operator (Iron)
     
  27. Offline

    1adog1

    Hey guys, I'm having a bit of a problem with my permissions, it was working fine on my mac back in June, but when I copied the files to my pc, it just stopped working, only ops can do anything, and when I try and change my permissions using the console, it deletes the config file altogether!

    Here's my permissions file, I am using Essentials, but not antibuild, Iconomy, Reporter, Enchanter, MobArena, CookieMonster, Worldedit, quickshop, Itree, and plugin metrics (The Indents are all in place, it just doesn't show when I copy it):

    # 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:
    1adog1:
    permissions:
    permissions.*: true
    bukkit.commands.op: true
    permissions.build: true
    groups:
    - Creator
    gearitz:
    permissions:
    permissions.*: true
    bukkit.commands.op: true
    permissions.build: true
    groups:
    - Creator
    silentninja2012:
    permissions:
    Enchanter.*: false
    groups:
    - Administrator
    wandomwill:
    groups:
    - Moderator
    mysticloss1:
    groups:
    - Adminstrator
    deathlord691:
    groups:
    - Moderator
    kline5:
    groups:
    - Moderator
    groups:
    default:
    permissions:
    essentials.build: true
    permissions.build: true
    griefprevention.buysellclaimblocks: true
    worldedit.biome.list: true
    worldedit.biome.info: true
    simplespawn.home.set: true
    simplespawn.home.use: true
    simplespawn.home.remove: true
    quickshop.use: true
    quickshop.create.sell: true
    quickshop.create.buy: true
    quickshop.create.double: true
    quickshop.find: true
    iConomy.holdings: true
    iConomy.help: true
    iConomy.payment: true
    iConomy.accounts.create: true
    iConomy.accounts.remove: true
    iConomy.accounts.give: true
    iConomy.accounts.take: true
    iConomy.accounts.status: true
    mcmmo.chat.partychat: true
    mcmmo.commands.skillreset: true
    reporter.report
    essentials.signs.use.warp: true
    essentials.chat.color: true
    essentials.chat.format: true
    essentials.chat.magic: true
    essentials.warp: true
    essentials.warp.list: true
    essentials.tpa: true
    essentials.tpaccept: true
    essentials.tpdeny: true
    essentials.spawn: true
    essentials.delhome: true
    essentials.home: true
    essentials.sethome: true
    essentials.sethome.bed: true
    essentials.sethome.multiple: true
    essentials.back: true
    essentials.back.ondeath: true
    essentials.protect: true
    essentials.msg: true
    essentials.rules: true
    essentials.suicide: true
    essentials.signs.use.kit: true
    essentials.signs.break.protection: true
    essentials.signs.create.protection: true
    essentials.signs.use.protection: true
    essentials.signs.create.warp: true
    essentials.signs.use.weather: true
    essentials.signs.use.time: true
    essentials.signs.break.disposal: true
    essentials.signs.create.disposal: true
    essentials.signs.use.disposal: true
    essentials.afk: true
    essentials.afk.auto: true
    essentials.help: true
    simplespawn.use: true
    essentials.list: true
    essentials.motd: true
    essentials.me: true
    essentials.balance: true
    essentials.balancetop: true
    essentials.nick: true
    itree.tree: true
    essentials.signs.create.trade: true
    essentials.signs.break.trade: true
    essentials.signs.use.trade: true
    ranks.commands.ranklist: true
    Creator:
    permissions:
    permissions.*: true
    worldedit.*: true
    essentials.*: true
    ranks.admin: true
    ranks.commands.rankcreate: true
    ranks.commands.rankdelete: true
    ranks.commands.rankedit: true
    worldedit.regen: true
    reporter.request
    reporter.complete
    reporter.delete
    Gearitz: true
    1adog1: true
    inheritance:
    - Administrator
    Administrator:
    permissions:
    griefprevention.admineavesdrop: true
    griefprevention.deathblow: true
    permissions.*: true
    essentials.tppos: true
    essentials.warps.*: true
    essentials.ban.exempt: true
    essentials.kick.exempt: true
    essentials.jail.exempt: true
    essentials.protect.admin: true
    essentials.gamemode: true
    essentials.gamemode.others: true
    essentials.give: true
    essentials.itemspawn.exempt: true
    essentials.god: true
    essentials.oversizedstacks: true
    essentials.god.pvp: true
    essentials.heal: true
    essentials.setjail: true
    worldedit.*: true
    essentials.spawner: true
    essentials.spawner.*: true
    essentials.deljail: true
    essentials.kill.exempt: true
    essentials.kill: true
    essentials.killall: true
    essentials.mute.exempt: true
    essentials.signs.create.kit: true
    essentials.signs.create.weather: true
    essentials.signs.create.time: true
    essentials.signs.break.time: true
    essentials.signs.break.weather: true
    mobarena.setup: true
    essentials.setspawn: true
    essentials.itemspawn.meta-head: true
    essentials.vanish.see: true
    griefprevention.adminclaims: true
    essentials.break.bedrock: true
    essentials.bigtree: true
    worldedit.regen: false
    Enchanter.*: true
    reporter.list
    reporter.view
    reporter.respond
    SILENTNINJA2012: true
    inheritance:
    - Moderator
    Moderator:
    permissions:
    permissions.build: true
    reporter.report.nolimit
    essentials.setwarp: true
    essentials.delwarp: true
    essentials.tempban: true
    essentials.tempban.unlimited: true
    essentials.togglejail: true
    essentials.unban: true
    essentials.unbanip: true
    essentials.ban: true
    essentials.banip: true
    essentials.fly: true
    essentials.kick: true
    essentials.fly.safelogin: true
    essentials.tp: true
    essentials.mute: true
    essentials.lightning: true
    essentials.fireball: true
    essentials.lightning.others: true
    Wandomwill: true
    Mysticloss1: true
    inheritance:
    - default
    Tester:
    permissions:
    permissions.build: false
    essentials.vanish: true
    essentials.tp: true
    essentials.fly: true
    essentials.tppos: true
    essentials.speed: true
    essentials.god: true
    essentials.build: false
    worlds:
    Starsty:
    permissions.build: true
    essentials.build: true
    inheritance:
    - default
    messages:
    build: '&cAuthorization is not adequate to build in this area.'

    debug: false






    Please Help!
     
  28. Offline

    gijsbouwse

    Trying to get users into group 1 automatically when they join for the first time ever. Doesn't seem to work, even when I put default: true. Any known bugs with this? I followed a guide on the internet and it said to put default: true above the permissions.

    Config:
    Group 1:
    default: true
    permissions:
    permissions.build: true
    essentials.balance: true
    essentials.pay: true
    essentials.motd: true
    essentials.msg: true
    essentials.realname: true
    essentials.ignore: true
    essentials.spawn: true
    essentials.seen: true
    essentials.warp: true
    essentials.helpop: true
    essentials.tpa: true
    essentials.tpaccept: true
    mchat.prefix.group 1: true
    mchat.prefix.default: false
    mchat.prefix.group 2: false
    inheritance:
    - default
    worlds:
    creative:
    coolplugin.item: true
    Group 2:
    permissions:
    essentials.workbench: true
    essentials.nick: true
    essentials.hat: true
    essentials.kits.[xp]: true
    mchat.prefix.group 2: true
    mchat.prefix.member: false
    mchat.prefix.default: false
    inheritance:
    - Member


    I had a group called default at first, but I removed it. Didn't help.

    So, what am I doing wrong? I'm not going to be able to put all users into the default group myself.
     
  29. Offline

    Kellis

    Hello.
    Can you help me with permossions? :)
    Problem is that normal user (non-admin) cannot use any plugins' command.
    My plugins:
    AuthMe.jar
    CommandBook.jar
    dynmap-1.9-alpha-3.jar
    Dynmap-CommandBook-0.50.jar
    dynmap-mobs-0.80.jar
    Dynmap-WorldGuard-0.50.jar
    LavaFurnace.jar
    PermissionsBukkit-2.1.jar
    ServerLogSaver.jar
    Vault.jar
    WorldEdit.jar
    WorldGuard.jar
    PermBukkit config:
    http://pastebin.com/DDXQwCE7
    AuthMe config:
    http://pastebin.com/cq4B1duE
     
  30. Offline

    Necromanhcer

    Hello world,
    I'm having some trouble with my permissions. My default players cant break blocks in the hub, and that normal, but i'm looking for the ability to stop the chat spam from block interactions. Also, I have signs to teleport to various worlds but permissions is blocking them from interacting. They can't right click on any block. Thanks!

    Plugins: Multiverse-Core, Multiverse-Inventories, Multiverse-SignPortals, PermissionBukkit, Essentials, EssentialsSpawn, EssentialsAntiBuild
     
  31. Offline

    KingDingbat

    Can anyone tell me if I have to restart my server if I add/remove nodes? I'm trying to troubleshoot a permissions issue with another plugin, and I'm fairly new to bukkit, so I'm not sure if I have to restart or not before the permissions take effect.
     

Share This Page