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

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

  1. Offline

    SpaceManiac

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

    Downloads:
    Current Version:

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

    [​IMG]

    Changelog:

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

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

    Snowy007

    PermissionsBukkit only takes care of groups and permissions. If you actually want to show the group name of someone in the chat, you need another plugin. I myself use 'SimplePrefix'.
     
  3. Offline

    Crashtopher

    OK, thanx for that, my friends have been whining for ranks. (lol)
     
  4. Offline

    codiack01

    anyone able to see something that would make this config work when i freshly type it up but then the next day not work anymore?
    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:
                announcer.receiver: true
                permissions.build: true
                essentials.sethome: true
                essentials.home: true
                essentials.list: true
                essentials.who: true
                essentials.help: true
                essentials.rules: true
                essentials.balance: true
                essentials.helpop: true
                essentials.info: true
                essentials.motd: true
                essentials.afk: true
                essentials.signs.use.balance: true
                essentials.signs.use.buy: true
                essentials.signs.use.disposal: true
                essentials.signs.use.enchant: true
                essentials.signs.use.free: true
                essentials.signs.use.gamemode: true
                essentials.signs.use.heal: true
                essentials.signs.use.kit: true
                essentials.signs.use.mail: true
                essentials.signs.use.protection: true
                essentials.signs.use.sell: true
                essentials.signs.use.spawnmob: true
                essentials.signs.use.time: true
                essentials.signs.use.trade: true
                essentials.signs.use.warp: true
                essentials.signs.use.weather: true
                essentials.tpaccept: true
                essentials.tpdeny: true
        user:
            permissions:
                essentials.compass: true
                essentials.depth: true
                essentials.ignore: true
                essentials.mail: true
                essentials.me: true
                essentials.msg: true
                essentials.tell: true
                essentials.r: true
                essentials.spawn: true
            inheritance:
            - default
        vip:
            permissions:
                dynmap.webregister: true
                essentials.tpa: true
                essentials.tpahere: true
                essentials.bigtree: true
                essentials.back: true
                essentials.back.ondeath: true
                essentials.sethome.multiple.3: true
                essentials.warp.arcadia: true
                essentials.signs.create.heal: true
                essentials.signs.create.disposal: true
                essentials.signs.create.mail: true
                essentials.kit.vip: true
                essentials.warp.list: true
                essentials.warp: true
            inheritance:
            - user
        assassin:
            permissions:
                essentials.warp.assassin_cave: true
                essentials.warp.jimexit: true
            inheritance:
            - vip
        hero:
            permissions:
                dynmap.render: true
                dynmap.show.self: true
                dynmap.hide.self: true
                dynmap.fullrender: true
                dynmap.radiusrender: true
                dynmap.updaterender: true
                dynmap.cancelrender: true
                dynmap.marker.list: true
                dynmap.marker.listsets: true
                dynmap.marker.listareas: true
                dynmap.marker.listlines: true
                lockette.user.create.*: true
                lockette.admin.create.*: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                permissions.*: true
                essentials.kick: true
                essentials.tempban: true
                essentials.tempban.offline: true
                essentials.gamemode: true
                essentials.togglejail: true
                essentials.invsee: true
                essentials.sethome.multiple.unlimited: true
                essentials.warp.*: true
                essentials.clearinventory: true
                essentials.gc: true
                essentials.broadcast: true
                essentials.ext: true
                essentials.tp: true
                essentials.mute: true
                essentials.jails: true
                essentials.jail: true
                essentials.weather: true
                essentials.spawnmob.*: true
            inheritance;
            - assassin
        seraph:
            permissions:
                factions.*: true
                announcer.*: true
                dynmap.*: true
                permissions.*: true
                essentials.*: true
                lockette.*: true
            inheritance:
            - hero
        god:
            permissions:
            inheritance:
            - seraph
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
     
  5. Offline

    Snowy007

    Code:
            inheritance;
            - assassin
    You used a ; there instead of :
     
  6. Offline

    codiack01

    still did not work, anything else?
     
  7. Offline

    DokuProductions

    I've been having a problem for the past couple of days. I've filled in the information manually but I keep on getting a warning message when starting the server (it actually says SEVERE) and when I tried to look at the coding to see what was wrong by using an online YAML Parser I got the following message:

    Code:
    ERROR:
     
    while scanning for the next token
    found character '\t' that cannot start any token
      in "<unicode string>", line 35, column 1:
            groups:
        ^
    
    What does this mean and how do I fix the Error?

    Here's the message I get while starting the server:

    Code:
    [SEVERE] [PermissionsBukkit] Unable to load configuration!
    
    And here's the actual config set up: http://pastebin.com/Q8hv5byb
     
  8. Offline

    Snowy007

    Can't really find much else. There is one thing though, but i'm not sure if that could be the problem.
    Since your 'god' group has 'permissions:' but hasn't any nodes in it, you should be able to just leave 'permissions:' out. 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.
    #
    # 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:
                announcer.receiver: true
                permissions.build: true
                essentials.sethome: true
                essentials.home: true
                essentials.list: true
                essentials.who: true
                essentials.help: true
                essentials.rules: true
                essentials.balance: true
                essentials.helpop: true
                essentials.info: true
                essentials.motd: true
                essentials.afk: true
                essentials.signs.use.balance: true
                essentials.signs.use.buy: true
                essentials.signs.use.disposal: true
                essentials.signs.use.enchant: true
                essentials.signs.use.free: true
                essentials.signs.use.gamemode: true
                essentials.signs.use.heal: true
                essentials.signs.use.kit: true
                essentials.signs.use.mail: true
                essentials.signs.use.protection: true
                essentials.signs.use.sell: true
                essentials.signs.use.spawnmob: true
                essentials.signs.use.time: true
                essentials.signs.use.trade: true
                essentials.signs.use.warp: true
                essentials.signs.use.weather: true
                essentials.tpaccept: true
                essentials.tpdeny: true
        user:
            permissions:
                essentials.compass: true
                essentials.depth: true
                essentials.ignore: true
                essentials.mail: true
                essentials.me: true
                essentials.msg: true
                essentials.tell: true
                essentials.r: true
                essentials.spawn: true
            inheritance:
            - default
        vip:
            permissions:
                dynmap.webregister: true
                essentials.tpa: true
                essentials.tpahere: true
                essentials.bigtree: true
                essentials.back: true
                essentials.back.ondeath: true
                essentials.sethome.multiple.3: true
                essentials.warp.arcadia: true
                essentials.signs.create.heal: true
                essentials.signs.create.disposal: true
                essentials.signs.create.mail: true
                essentials.kit.vip: true
                essentials.warp.list: true
                essentials.warp: true
            inheritance:
            - user
        assassin:
            permissions:
                essentials.warp.assassin_cave: true
                essentials.warp.jimexit: true
            inheritance:
            - vip
        hero:
            permissions:
                dynmap.render: true
                dynmap.show.self: true
                dynmap.hide.self: true
                dynmap.fullrender: true
                dynmap.radiusrender: true
                dynmap.updaterender: true
                dynmap.cancelrender: true
                dynmap.marker.list: true
                dynmap.marker.listsets: true
                dynmap.marker.listareas: true
                dynmap.marker.listlines: true
                lockette.user.create.*: true
                lockette.admin.create.*: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                permissions.*: true
                essentials.kick: true
                essentials.tempban: true
                essentials.tempban.offline: true
                essentials.gamemode: true
                essentials.togglejail: true
                essentials.invsee: true
                essentials.sethome.multiple.unlimited: true
                essentials.warp.*: true
                essentials.clearinventory: true
                essentials.gc: true
                essentials.broadcast: true
                essentials.ext: true
                essentials.tp: true
                essentials.mute: true
                essentials.jails: true
                essentials.jail: true
                essentials.weather: true
                essentials.spawnmob.*: true
            inheritance:
            - assassin
        seraph:
            permissions:
                factions.*: true
                announcer.*: true
                dynmap.*: true
                permissions.*: true
                essentials.*: true
                lockette.*: true
            inheritance:
            - hero
        god:
            inheritance:
            - seraph
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    You seem to have a lot of tabs in front of nodes. Remove all tabs and only use spaces for indention.
    Also remove any empty lines.
     
  9. Offline

    Fentaur47

    Once I have access to my other computer in a few hours, I'll post a simple config example I wrote up. Once you get the hang of writing the code for it this becomes the simplest and easiest permission system out there.
     
  10. Offline

    Wardx

    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:
      ConspiracyWizard:
        permissions:
          permissions.example: true
        groups:
        - admin
      razzkulz:
        groups:
        - default
        - admin
        - user
    groups:
      default:
        permissions:
          permissions.build: false
      admin:
        permissions:
          permissions.*: true
        inheritance:
        - user
      user:
        permissions:
          permissions.build: true
        inheritance:
        - default
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    
    Guys, I really need some help. I want to let the group "user" be able to build in all of my worlds. I have three worlds, "world", "survival", and "creative". Whenever I set all of those permissions.build to : true it still won't let me build. Every time I try to break a block or something in any of my worlds they just immediately spawn back and prevent me from doing anything. Help is appreciated!
     
  11. Offline

    Wardx

    Can someone please help? It's been almost a week now.
     
  12. Offline

    Mitleidspender

    hello everyone

    i have a craftbukkit server running and installed simplewarps, dynmap and permissionsbukkit
    can anyone see, why none of the permissions are actually doing anything on the server?
    when i dump permissions of a user, the permissions are mostly shown as configured but they are not doing anything. people in groups with bukkit.reload: false can stil do a reload.

    thanks for anyone who can help. all plugins are up to date.

    this is my config.yml:
    Code:
    users:
      mitleidspender:
        groups:
        - admin
      drecksding_net:
        groups:
        - user
      xchr0mex:
        groups:
        - user
      krosmarc:
        groups:
        - user
      iriosys:
        groups:
        - op
      p5ycho_basti:
        groups:
        - op
    groups:
      default:
        permissions:
          bukkit.*: false
          bukkit.command.version: true
          bukkit.command.plugins: true
          bukkit.command.tell: true
          bukkit.command.kill: true
          bukkit.command.me: true
          bukkit.command.help: true
          bukkit.command.list: true
          permissions.*: false
          simplewarps.list: true
          simplewarps.warpothers: false
          simplewarps.addwarp: false
          simplewarps.setsign: false
          simplewarps.usesign: true
          simplewarps.warps.*: true
          dynmap.*: false
      user:
        permissions:
          bukkit.command.teleport: true
          bukkit.command.give: true
          bukkit.command.say: true
          bukkit.command.time: true
          bukkit.command.gamemode: true
          bukkit.command.xp: true
          bukkit.command.toggledownfall: true
          bukkit.reload: false
          permissions.build: true
          simplewarps.addwarp: true
          simplewarps.setsign: true
        inheritance:
        - default
      op:
        permissions:
          bukkit.command.reload: true
          bukkit.command.kick: true
          bukkit.command.ban: true
          bukkit.command.unban: true
          bukkit.command.op: true
          simplewarps.warpothers: true
        inheritance:
        - user
      admin:
        permissions:
          bukkit.*: true
          permissions.*: true
          simplewarps.*: true
          dynmap.*: true
    debug: false
    
     
  13. Offline

    marinov

    Code:
    groups:
      Member:
        default: true
        permissions:
          permissions.build: true
          essentials.rules: true
          essentials.help: true
          essentials.pay: true
          essentials.balance: true
          essentials.tell: true
          essentials.sell: true
          essentials.back: true
          essentials.back.ondeath: true
          essentials.who: true
          essentials.afk: true
          essentials.list: true
          essentials.msg: true
          essentials.nick: true
          essentials.warp.list: true
          essentials.warp: true
          essentials.helpop: true
          essentials.motd: true
          essentials.spawn: true
          essentials.home: true
          essentials.tpa: true
          essentials.tpahere: true
          essentials.tpaccept: true
          essentials.sethome: true
          iConomy.payment: true
          iConomy.holdings: true
          iConomy.holdings.others: true
          iConomy.sell: true
          lwc.protect: true
          ChestShop.buy: true
          ChestShop.sell: true
          multiverse.access.*: true
          multiverse.portal.access.*: true
        worlds:
          Spawn:
            permissions:
              permissions.build: false
          Parkur:
            permissions:
              permissions.build: false
          Creative_VIP:
            permissions:
              permissions.build: false
          Redstone:
            permissions:
              permissions.build: false
      VIP:
        inheritance:
        - Member
        worlds:
          Creative_VIP:
            permissions:
              permissions.build: true
          Redstone:
            permissions:
              permissions.build: true
      Moderator:
        permissions:
          essentials.tempban: true
          essentials.heal: true
          essentials.feed: true
          essentials.ban.notify: true
          essentials.banip: true
          essentials.clearinventory: true
          essentials.eco.loan: true
          essentials.ext: true
          essentials.getpos: true
          essentials.helpop.recieve: true
          essentials.home.others: true
          essentials.invsee: true
          essentials.jails: true
          essentials.jump: true
          essentials.kick: true
          essentials.kick.notify: true
          essentials.mute: true
          essentials.realname: true
          essentials.signs.create.*: true
          essentials.signs.break.*: true
          essentials.time: true
          essentials.protect.alerts: true
          essentials.protect.admin: true
          essentials.protect.ownerinfo: true
          essentials.togglejail: true
          essentials.top: true
          essentials.unban: true
          essentials.unbanip: true
          essentials.whois: true
          essentials.world: true
        inheritance:
        - Member
      Admin:
        permissions:
          essentials.gamemode: true
          essentials.tp: true
          essentials.ban: true
          essentials.god: true
          essentials.invsee: true
        inheritance:
        - Moderator
      Owner:
        permissions:
          '*': true
        inheritance:
        - admin
    messages:
      build: '&cYou do not have permission to build here.'
     
    
    Nothing is working... players can build everywhere, and they can't use portals or anything.... Please help
     
  14. Offline

    ibrahimkhan1212

    if your file says
    groups:
    default:
    Permissions:
    *:false
    User:
    Permissions:
    bukkit.command.tell:true
    bukkit.command.kill:true
    bukkit.command.build:true
    Moderator:
    Permissions:
    *:true
    bukkit.command.stop:false
    bukkit.command.op.take:false
    bukkit.command.op.give:false
    Operator
    Permissions:
    *:true

    Will default be able to do anything?
    Will users be able to do anything other then build, /kill, /tell?
    Will moderators be able to do /stop, /op, /deop?
    Will operators be able to do everything?
     
  15. Offline

    TheRedNinja93

    Ok. So. I'm really starting to despise permissions. I've had more issues with permissions alone than with all other plugins combined. The current problem is that no one who's not OP can't build. The server log shows this message when starting up:

    2012-07-26 21:00:12 [INFO] [PermissionsBukkit] Enabling PermissionsBukkit v1.6
    2012-07-26 21:00:12 [SEVERE] [PermissionsBukkit] Unable to load configuration!
    2012-07-26 21:00:12 [INFO] [PermissionsBukkit] Enabled successfully, 0 players registered

    Here's a copy of my permissions config.yml

    http://pastebin.com/dfm58jYZ

    And one last thing, whenever I edit the permissions, then save and go in game and type /permissions reload it erases the entire config file. All of it. I have no idea why, but it bugs the crap out of me.

    And yes, I *do* have the most current version of PermissionsBukkit.
     
  16. Offline

    tyrs6

    I have a problem thats annoying as poop. I dont know if anyone else has had this problem or if it was answered I didnt want to read through 104 pages of posting. I was doing most of the permissions ingame untill I wanted to add a couple more groups for my freinds to work towards. So I went into the config and instead of it being neatly spaced out it was all compacted into one big paragraph type thing. Its really hard to edit in this form and when i try to edit it it doesnt add the groups at all.

    Wait never mind when I put the config on this post it changed it so it had the right spacing and everything. So i guess ill just do that every time this happens.

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

    Mitleidspender

    i have found my error.
    bukkit.* simplewarps.* dynmap.* just dont exist
     
  18. Offline

    ZJ2741

    Im woundering if u can update this to 1.2.5 R5.o
     
  19. Offline

    willhwilt

    im having trouble getting my server to use the permissions this is my config.yml any errors i put it into this parser http://yaml-online-parser.appspot.com/ and it turned out fine but my server says this: 2012-07-29 14:29:39 [INFO] [PermissionsBukkit] Enabling PermissionsBukkit v1.6
    2012-07-29 14:29:39 [SEVERE] [PermissionsBukkit] Unable to load configuration!
    2012-07-29 14:29:39 [INFO] [PermissionsBukkit] Enabled successfully, 0 players registered everytime i load 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:
    willhwiltjr:
    permissions:
    permissions.example: true
    groups:
    - owner
    kethro:
    permissions:
    permissions.example: true
    groups:
    - admin
    crash2k9:
    permissions:
    permissions.example: true
    groups:
    - admin
    nev53:
    permissions:
    permissions.example: true
    groups:
    - admin
    groups:
    default:
    permissions:
    permissions.build: false
    owner:
    permissions:
    permissions.*: true
    inheritance:
    - admin
    admin:
    permissions:
    permissions.*: true
    inheritance:
    - user
    user:
    permisions:
    permissions.build: true
    messages:
    build: '&cYou do not have permission to build here.'
    debug: false
     
  20. Offline

    SolidCraft

    i get the error when i try to add someone to a group

    2012-07-31 03:46:50 [WARNING] Unexpected exception while parsing console command
    org.bukkit.command.CommandException: Unhandled exception executing command 'permissions' in plugin PermissionsBukkit v1.6
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:484)
    at org.bukkit.craftbukkit.CraftServer.dispatchServerCommand(CraftServer.java:480)
    at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:604)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:573)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:451)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.NullPointerException
    at com.platymuus.bukkit.permissions.PermissionsCommand.createPlayerNode(PermissionsCommand.java:400)
    at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(PermissionsCommand.java:301)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:152)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 7 more
     
  21. Offline

    Elfsovereign

    Normally I wouldn't comment but this was posted over a year ago XD
     
  22. Offline

    soaringeg127

    Is there any way to create new groups? Insted of only having default, admin, and user?
     
  23. Offline

    YourSoSerious

    Update to 1.3 Pleaseee :D
     
  24. Offline

    Snowy007

    Was away for few weeks... lots of questions i just simply don't feel like answering xD
    If anyone is still having problems, please post again. Oh and for god sake, put those configs in code tags. Makes my life a little more easier :p


    It works fine on 1.3 If your having problems getting it to work, Its usually a problem in the config.

    Yes, just add them in the config. Those 3 groups are just examples and you can make as many as you want. You should keep the 'default' group though.
     
  25. Offline

    YourSoSerious

    For my server i want every one to be default when they join the server in Gamemode Adventure untill i update them by going /permissions player setgroup <UserName> user

    How do i go about doing this?
     
  26. Offline

    Snowy007

    Well... its not really possible to change the default gamemode for players using permissions. (perhaps with a separate plugin though) But you are able to deny building for the default group though.
    Actually, thats how the default configuration already does it. The default group has the permission 'permissions.build: false' while the 'user' group has 'permissions.build: true' . So the default group can't build, but when you put someone in the user group, they are able to build.
     
  27. Offline

    BlackDawn187

    Hello,

    I used to use Permissions Bukkit a year ago and, Im in the process of using it again. I've encountered a problem with my server completely disregarding the permissions I've set. I can't find any answers as to why these are not working.....

    http://pastebin.com/TKAzxfFt (config.yml)

    Running Plugins: World Edit, World Guard, MCBans, BukkitCompat, SuperPermsBridge, PermissionsBukkit, PreciousStones, Zport, ChestShop, Essentials, Simple Prefix, Hero Chat & Vault.

    http://pastebin.com/ZiZqmKxN (Console Startup Log)

    If anyone can analyze the supplied configs, my server would really love to have its permissions working... Also, please note I have omitted things in the Console Startup Log using asterisks.
     
  28. Offline

    Snowy007

    Try removing the 2 empty lines. The one at the top just before 'users' and the one at the bottom just above 'debug'
    Also, (don't know if this matters but,) i see you have some permissions like this 'herochat.join.<channel>: true' I'm guessing you should actually fill something in yourself at the <channel> part.
     
  29. Offline

    BlackDawn187

    Hi Snowy,

    Thanks for the prompt reply. I removed the spaces as you mentioned, before users and, before debug. As you mentioned with the herochat.join.channel, I set it as channel for default reasons. The live config has the channel included.

    I am still unable to be granted any permissions with the updated configuration file, is there anything here we've missed?

    http://pastebin.com/mCAFYkyH (New Config.yml)

    The problems Im having are universal and, not specific to hero chat. Nothing works, /kill, /msg, /time, /list, etc. But, I am able to build as default..

    Using this tool (http://yaml-online-parser.appspot.com/) I received the following error:
    Code:
    ERROR:
     
    while scanning for the next token
    found character '\t' that cannot start any token
      in "<unicode string>", line 48, column 40:
        ...      herochat.join.channel: true   
                                            ^
     
  30. Offline

    Snowy007

    Oh, wait. Now i see.
    You have some nodes with tabs behind the nodes.
    Check the nodes and remove the tabs that are behind the nodes.

    For exampe 'herochat.leave.channel: true', most of the 'essentials' nodes and a lot of the preciousstones nodes have tabs behind them.
     
  31. Offline

    BlackDawn187

    Okay, so I've downloaded Notepad ++ and, have received a positive result from the yaml parsers I've been using. But, still no Permissions. I have access to build and, whisper myself.. Also, changed the tabs to spaces as they should be.

    Here is the latest: http://pastebin.com/NEp6sK8T (config.yml)

    Please ignore the Hero Chat nodes.. as that's an entirely different thing of its own and, not specific to Permissions Bukkit.
     

Share This Page