[ADMN/DEV] PermissionsBukkit v2.0 - Official Default Groups Plugin [1.5.1-R0.2]

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

     
  1. Offline

    SpaceManiac

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    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:

    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:
    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:
    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:
    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.
    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.
    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)
    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.
    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.
    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).
    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.

    This post has been edited 14 times. It was last edited by SpaceManiac Feb 6, 2013.
    madmac, Gesundheit, tripleX and 23 others like this.
  2.  
  3. Offline

    Kurai Ookami

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

    mercury19

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    I haven't touched my config file for izone yet. I still cant get it to work for players.


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

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



    Thanks, m19

    This post has been edited 1 time. It was last edited by mercury19 Aug 18, 2012.
  5. Offline

    Kurai Ookami

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    that should be permissions-file: permission.yml but aside from that it's fine, it'll still access permission bukkit.
    I'd still like to see both your iZone config file and permissions config in their entirety if that's alright with you.
  6. Offline

    Svedrigailov

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    -I looked, but I couldn't find this problem-

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

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

    Any help is appreciated.

    This post has been edited 2 times. It was last edited by Svedrigailov Aug 19, 2012.
  7. Offline

    Snowy007

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Try removing the empty lines just above and below 'users:'.
  8. Offline

    Svedrigailov

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Thank you for your response. I removed the lines, I can now use the /perm group list command, but I still get this error when trying to add a player to a group ingame via the "/perm player addgroup Johnny_Steele Ops" command

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

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

    Mikirog

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    My console writes me "[SERVERE] [PermissionsBukkit] Unable to load configuration!" and permissions don't works. How I do bad?
  10. Offline

    ohjays

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
  11. Offline

    Snowy007

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

    Mikirog

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    OK, there is my config and anything wrong. I want to make players shot with guns and throw grenades by plugin Armageddon.

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

    This post has been edited 2 times. It was last edited by Mikirog Aug 20, 2012.
  13. Offline

    Snowy007

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    The permission nodes for the armageddon plugin where not correctly indented. They needed to be 4 spaces further. Also i removed 2 empty lines. one at the top and one at the bottom of the file.

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

    Mikirog

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Fixed. I only use a TAB instead od Space :)
  15. Offline

    Snowy007

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Don't use tabs. Tabs don't work.
    Always indent everything with spaces.
  16. Offline

    Surma

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    I'm having a bit of a problem. It appears that setting a wildcard permission (example vanish.*: true) overrides any later more specific nodes (example vanish.effects.smoke: false), even if the wildcard node is inherited or specified earlier in the same group.

    I organise my config.yml such that default is denied everything (example admincmd.*: false) and then granted a subset of specific permissions (example admincmd.server.rules: true). Every group "above" in the power chain inherits from the one below and permissions are granted as appropriate, so I don't have to re-type everything everywhere. It's a sort of "deny by default" policy. I know my first statement is correct, because right now default is set to vanish.*: false and later the admin group (which I am) is granted vanish.normal: true and vanish.op: true but I can't /vanish. Earlier, admin was granted vanish.*: true (which did override the earlier vanish.*: false) but then I had the problem that a bunch of effects were turned on (it goes boom when you go visible/invisible) and I joined vanished by default, even though I set permission nodes such that this behaviour would be turned off (there are nodes to set this behaviour, vanish.*: true turns them on and I set permission nodes later in the file which should turn them off).

    I'm guessing the reason for this is because wildcard nodes are checked before specific ones, so my question is: Is there a way (besides giving player-specific permissions) to make a specific node have higher priority than a general wildcard node, or am I just going to have to expand all the root plugin.*: false nodes under default (which is a lot of unnecessary typing)?
  17. Offline

    Snowy007

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Why you would deny all permissions first? PermissionsBukkit already works with a 'deny by default' policy. If you don't give a 'true' permission to a group, they simply don't have that permission.
    Also using vanish.*: true (or false) and then denying (or allowing) other vanish permissions 'should' work fine. Maybe things might be more clear if you post your config?
  18. Offline

    Surma

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    It does? Sweet! Anyway, here's my config:
    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:
        Surma92:
            groups:
            - owner
        Mataata:
            groups:
            - user
        Ampbox3000:
            groups:
            - user
        LegoPer:
            groups:
            - trusteduser
        Flyyyman:
            groups:
            - trusteduser
        KaeraNeko:
            groups:
            - trusteduser
        Yeppsy:
            groups:
            - trusteduser
        Interpreter:
            groups:
            - trusteduser
        Pads:
            groups:
            - trusteduser
        nissen:
            groups:
            - trusteduser
        C-J:
            groups:
            - trusteduser
        Alexecus:
            groups:
            - trusteduser
        Mikerophone279:
            groups:
            - trusteduser
        Takyodor:
            groups:
            - trusteduser
        drakrytaren:
            groups:
            - trusteduser
        torzanswe:
            groups:
            - trusteduser
        Koschei:
            groups:
            - user
        NieliNinja:
            groups:
            - trusteduser
        Friscomeal:
            groups:
            - trusteduser
        jocken2:
            groups:
            - trusteduser
        oveng190:
            groups:
            - trusteduser
        valthorn:
            groups:
            - trusteduser
        Celestico:
            groups:
            - trusteduser
        dikkebolletje:
            groups:
            - trusteduser
        Meavar:
            groups:
            - trusteduser
        lucaspalsmarker:
            groups:
            - trusteduser
        PonWer92:
            groups:
            - user
    groups:
        default:
            permissions:
                admincmd.*: false
                admincmd.server.motd: true
                admincmd.server.news: true
                admincmd.server.rules: true
                admincmd.player.list: true
                admincmd.player.kill: true
                admincmd.player.whois: true
                admincmd.player.reply: true
                admincmd.maxHomeByUser.1: true
                admincmd.immunityLvl.10: true
                admincmd.maxItemAmount.1: true
                bookworm.*: false
                bukkit.*: false
                multiverse.*: false
                multiverse.help: true
                multiverse.access.Pangaea: true
                multiverse.access.Pangaea_nether: true
                multiverse.access.Pangaea_the_end: true
                multiverse.access.Cherno: true
                multiverse.access.Cherno_nether: true
                multiverse.access.Cherno_the_end: true
                multiverse.teleport.self.Pangaea: true
                multiverse.teleport.self.Cherno: true
                multiverse.core.coord: true
                multiverse.core.info: true
                multiverse.core.list.environments: true
                multiverse.core.list.worlds: true
                permissions.*: false
                spout.plugin.ignorespoutcraft: true
                spout.plugin.forcespoutcraft: false
                spout.client.*: false
                vanish.*: false
                worldedit.*: false
                worldguard.*: false
        user:
            permissions:
                admincmd.player.msg: true
                admincmd.player.mute: true
                admincmd.player.afk: true
                admincmd.player.roll: true
                admincmd.player.played: true
                admincmd.player.pres: true
                admincmd.maxHomeByUser.1: true
                admincmd.immunityLvl.30: true
                admincmd.maxItemAmount.0: true
                bookworm.create: true
                bookworm.write.own: true
                bookworm.place.own: true
                bookworm.place.others: true
                bookworm.copy.own: true
                bookworm.copy.others: true
                bookworm.remove.own: true
                bookworm.destroy.own: true
                multiverse.core.list.who: true
                permissions.build: true
                spout.client.*: true
            inheritance:
            - default
        trusteduser:
            permissions:
                multiverse.access.DragonCity: true
                multiverse.access.DragonCity_nether: true
                multiverse.access.DragonCity_the_end: true
                multiverse.access.WonderField: true
                multiverse.access.WonderField_nether: true
                multiverse.access.WonderField_the_end: true
                multiverse.teleport.self.DragonCity: true
                multiverse.teleport.self.DragonCity_nether: true
                multiverse.teleport.self.DragonCity_the_end: true
                multiverse.teleport.self.WonderField: true
            worlds:
                DragonCity:
                    worldedit.*: true
                    worldguard.*: true
                DragonCity_nether:
                    worldedit.*: true
                    worldguard.*: true
                DragonCity_the_end:
                    worldedit.*: true
                    worldguard.*: true
                WonderField:
                    worldedit.*: true
                    worldguard.*: true
                WonderField_nether:
                    worldedit.*: true
                    worldguard.*: true
                WonderField_the_end:
                    worldedit.*: true
                    worldguard.*: true
            inheritance:
            - user
        admin:
            permissions:
                admincmd.*: true
                admincmd.maxHomeByUser.0: true
                admincmd.immunityLvl.140: true
                bookworm.*: true
                bookworm.write.deny.bookid: true
                bookworm.place.deny.bookid: true
                bookworm.copy.deny.bookid: true
                bookworm.remove.deny.bookid: true
                bookworm.destroy.deny.bookid: true
                bukkit.*: true
                multiverse.*: true
                permissions.*: true
                vanish.standard: true
                vanish.op: true
                vanish.toggle.all: true
                vanish.hooks.essentials.hide: true
                vanish.spout.status: true
                vanish.effects.toggle.all: true
                worldedit.*: true
                worldguard.*: true
            inheritance:
            - user
        owner:
            permissions:
                admincmd.immunityLvl.150: true
            inheritance:
            - admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    You know, I just noticed that default gets permissions.*: false and then user gets permissions.build: true and that works just fine. Do plugins have the ability to check wildcard nodes directly? If that is the case it's possible that it's just vanish that ignores specific nodes if the global vanish.* is false.

    This post has been edited 2 times. It was last edited by Surma Aug 21, 2012.
  19. Offline

    PCGeek971

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    *PC Wonders*
    Is it pssible to give permissions to a group so that they can set players only to a certain group? Such as:
    Admin permission:
    permissions.player.setgroup.vip

    So that admins can set players to the vip rank but not any other ranks.
    Please reply, Thanks
  20. Offline

    Snowy007

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    I edited your config a little.
    I removed all the false nodes at the default level. As i said earlier, permissions are always false unless you give true. :p
    I also changed the admin group inheritance. The admin group was inheriting from the 'user' group and i'm quite sure your intention was to let them inherit from the 'trusteduser' group.
    This should probably work:
    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    #
    # The cannot-build message is configurable. If it is left blank, no message
    # will be displayed to the player if PermissionsBukkit prevents them from
    # building, digging, or interacting with a block. Use '&' characters to
    # signify color codes.
    users:
        Surma92:
            groups:
            - owner
        Mataata:
            groups:
            - user
        Ampbox3000:
            groups:
            - user
        LegoPer:
            groups:
            - trusteduser
        Flyyyman:
            groups:
            - trusteduser
        KaeraNeko:
            groups:
            - trusteduser
        Yeppsy:
            groups:
            - trusteduser
        Interpreter:
            groups:
            - trusteduser
        Pads:
            groups:
            - trusteduser
        nissen:
            groups:
            - trusteduser
        C-J:
            groups:
            - trusteduser
        Alexecus:
            groups:
            - trusteduser
        Mikerophone279:
            groups:
            - trusteduser
        Takyodor:
            groups:
            - trusteduser
        drakrytaren:
            groups:
            - trusteduser
        torzanswe:
            groups:
            - trusteduser
        Koschei:
            groups:
            - user
        NieliNinja:
            groups:
            - trusteduser
        Friscomeal:
            groups:
            - trusteduser
        jocken2:
            groups:
            - trusteduser
        oveng190:
            groups:
            - trusteduser
        valthorn:
            groups:
            - trusteduser
        Celestico:
            groups:
            - trusteduser
        dikkebolletje:
            groups:
            - trusteduser
        Meavar:
            groups:
            - trusteduser
        lucaspalsmarker:
            groups:
            - trusteduser
        PonWer92:
            groups:
            - user
    groups:
        default:
            permissions:
                permissions.build: false
                admincmd.server.motd: true
                admincmd.server.news: true
                admincmd.server.rules: true
                admincmd.player.list: true
                admincmd.player.kill: true
                admincmd.player.whois: true
                admincmd.player.reply: true
                admincmd.maxHomeByUser.1: true
                admincmd.immunityLvl.10: true
                admincmd.maxItemAmount.1: true
                multiverse.help: true
                multiverse.access.Pangaea: true
                multiverse.access.Pangaea_nether: true
                multiverse.access.Pangaea_the_end: true
                multiverse.access.Cherno: true
                multiverse.access.Cherno_nether: true
                multiverse.access.Cherno_the_end: true
                multiverse.teleport.self.Pangaea: true
                multiverse.teleport.self.Cherno: true
                multiverse.core.coord: true
                multiverse.core.info: true
                multiverse.core.list.environments: true
                multiverse.core.list.worlds: true
                spout.plugin.ignorespoutcraft: true
                spout.client.*: false
        user:
            permissions:
                admincmd.player.msg: true
                admincmd.player.mute: true
                admincmd.player.afk: true
                admincmd.player.roll: true
                admincmd.player.played: true
                admincmd.player.pres: true
                admincmd.maxHomeByUser.1: true
                admincmd.immunityLvl.30: true
                admincmd.maxItemAmount.0: true
                bookworm.create: true
                bookworm.write.own: true
                bookworm.place.own: true
                bookworm.place.others: true
                bookworm.copy.own: true
                bookworm.copy.others: true
                bookworm.remove.own: true
                bookworm.destroy.own: true
                multiverse.core.list.who: true
                permissions.build: true
                spout.client.*: true
            inheritance:
            - default
        trusteduser:
            permissions:
                multiverse.access.DragonCity: true
                multiverse.access.DragonCity_nether: true
                multiverse.access.DragonCity_the_end: true
                multiverse.access.WonderField: true
                multiverse.access.WonderField_nether: true
                multiverse.access.WonderField_the_end: true
                multiverse.teleport.self.DragonCity: true
                multiverse.teleport.self.DragonCity_nether: true
                multiverse.teleport.self.DragonCity_the_end: true
                multiverse.teleport.self.WonderField: true
            worlds:
                DragonCity:
                    worldedit.*: true
                    worldguard.*: true
                DragonCity_nether:
                    worldedit.*: true
                    worldguard.*: true
                DragonCity_the_end:
                    worldedit.*: true
                    worldguard.*: true
                WonderField:
                    worldedit.*: true
                    worldguard.*: true
                WonderField_nether:
                    worldedit.*: true
                    worldguard.*: true
                WonderField_the_end:
                    worldedit.*: true
                    worldguard.*: true
            inheritance:
            - user
        admin:
            permissions:
                admincmd.*: true
                admincmd.maxHomeByUser.0: true
                admincmd.immunityLvl.140: true
                bookworm.*: true
                bookworm.write.deny.bookid: true
                bookworm.place.deny.bookid: true
                bookworm.copy.deny.bookid: true
                bookworm.remove.deny.bookid: true
                bookworm.destroy.deny.bookid: true
                bukkit.*: true
                multiverse.*: true
                permissions.*: true
                vanish.standard: true
                vanish.op: true
                vanish.toggle.all: true
                vanish.hooks.essentials.hide: true
                vanish.spout.status: true
                vanish.effects.toggle.all: true
                worldedit.*: true
                worldguard.*: true
            inheritance:
            - trusteduser
        owner:
            permissions:
                admincmd.immunityLvl.150: true
            inheritance:
            - admin
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false

    Unfortunately that is not possible. I'm having the same problem that my moderators could make themselves admin if they want.
    I solved it by disabling the 'setgroup moderator' and 'setgroup admin' commands with another plugin. The downside however is that i have to manually give people moderator status now if i want to promote them to moderator. :p
  21. Offline

    Surma

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Thanks a lot :)
  22. Offline

    mercury19

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Sure. Sorry the reply is late, I have been computerles for a bit.

    iZone:


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


    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:
    groups:
        default:
            permissions:
                iZone*: true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: false



    EDIT: I got isone to work with PermissionsEx...

    This post has been edited 1 time. It was last edited by mercury19 Aug 27, 2012.
  23. Offline

    KrisEike

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    This is the best permissions plugin out, would be nice if you could update it to the newest CBs
  24. Offline

    tr0y

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    I want this too. Came here looking for this.
  25. Offline

    SpaceManiac

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)

    This post has been edited 1 time. It was last edited by SpaceManiac Sep 8, 2012.
  26. Offline

    shark4675

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    umm there's something wrong when someone does /spawn it still says they can't use the commands. i know the person i tied with was in the rank user. it with i have easy essentials i put in the nodes ess.afk ess.home ess.heal and ess.sethome what did i do wrong?
  27. Offline

    Mr__Rainbow__

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    ok sir i try to install a lot f different plugins and all diff times and this is what keeps saying but with plugins name and files says about this plz tell me what i did wrong or what i am doing wrong below is error



    19:23:32 [SEVERE] Could not load 'plugins/PluginManager.jar' in folder 'plugins'
    org.bukkit.plugin.InvalidPluginException: java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:155)
    at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305)
    at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230)
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:222)
    at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:198)
    at net.minecraft.server.ServerConfigurationManagerAbstract.<init>(ServerConfigurationManagerAbstract.java:50)
    at net.minecraft.server.ServerConfigurationManager.<init>(SourceFile:11)
    at net.minecraft.server.DedicatedServer.init(DedicatedServer.java:105)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:378)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
    Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:676)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:44)
    at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:317)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:242)
    at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:144)
    ... 9 more

    This post has been edited 1 time. It was last edited by TnT Sep 28, 2012.
  28. Offline

    Darothane

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Hi All,

    I am really stuck with this plugin. I installed Bukkit Core on my tekkit server and i'm really struggling with the permissions. I'm sure i'm setting them correctly but something is wrong.

    Example:

    my users want to be able to use the /home set of commands. the core documentation states that they need the permissions core.home so to test the permission I gave 1 user the permission core.home.* he is still being told that he doesn't have the permissions to use the command. What am I doing wrong!? Please help.

    Regards

    Daro

    This post has been edited 1 time. It was last edited by TnT Oct 9, 2012.
  29. Offline

    leagris

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    I have a major issue with the new setrank command.
    Setrank superseed or erase all secondary groups.
    I have a permissions setup where players belong to several groups (One main and two others)

    The new setrank alias rank command would be much usefull as add/remove to preserve secondary groups:
    Code:
    addrank <player> <group>
    removerank <player> <group>
    Good point, while I would prefer it for add/remove group:
    Code:
    permissions.player.addgroup.groupname
    permissions.player.removegroup.groupname
    There is already a pull request about it here:
    https://github.com/SpaceManiac/PermissionsBukkit/pull/15

    This post has been edited 2 times. It was last edited by leagris Oct 13, 2012.
  30. Offline

    stoneminer02

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    Questions:

    Can we use something like "/permissionsbukkit import pex"?
    [IMG]


    Can we make custom nodes?
    [IMG]

    This post has been edited 1 time. It was last edited by stoneminer02 Oct 11, 2012.
  31. Offline

    stoneminer02

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    If you use essentials so see the command permission list!
    The link is here.
  32. Offline

    Jemrada

    dev.bukkit.org profile:
    CFUSERNAME
    My Plugins (CFCOUNT)
    When a Player dies, is it possible to remove them from all groups except default?

    Currently, our players can automatically be added to a permission group when a trigger is activated. If they die, I would like them to be removed from all groups except default. Basically a total reset.

Share This Page