[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

    Seven50six6

    Well I added that to it and it still didnt work.

    Here is my Permissions.yml file now:

    Code:
    users:
        seven50six6:
            permissions:
                permissions.*: true
                permissions.example: true
            groups:
            - admin
        JoshSizemore:
            permissions:
                permission.*: true
            groups:
            - admin
    groups:
        default:
            permissions:
                essentials.afk: true
                essentials.help: true
                permissions.build: true
                essentials.list: true
                essentials.mail.send: true
                essentials.mail: true
                essentials.me: true
                essentials.nick: true
                essentials.realname: true
                essentials.rules: true
                essentials.suicide: true
                essentials.spawn: true
                essentials.home: true
                essentials.sethome: true
                essentials.warp: true
                lockette.user.create.*: true
        moderator:
            permissions:
                permissions.build: true
                essentials.ban: true
                essentials.broadcast: true
                essentials.unban: true
                essentials.mute: true
                essentials.kick: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to do that...'
    debug: false
    
    I've got it working now I believe!
     
  3. Offline

    b4ux1t3

    I hate to be one of those people, but I can't seem to get this to work with craftbukkit 1.2.5 R1.

    I'm following the procedure outlined here, but my plugin doesn't seem to want to start. It doesn't even make a "config.yml", nor does it make a folder called "PermissionsBukkit".

    I stuck the jar file in the plugins folder, along with my essentials (which does work, by the way), but it doesn't seem to want to run when I start up the server. Any ideas?
     
  4. Offline

    Matthiaswagg

    PLEASE UPDATE FOR AT LEAST 1.2.3 PREFERABLY 1.2.5

    Okay. I'm not very good at this complex stuff... But I was trying to add the chairs.sit node to all the groups, as I have the Chairs plugin, and wish the non-op people could sit down... Btw my build is 1.2.5R1.0
    Here is my config, I think I may have done it wrong.

    users:
    pirate12345:
    permissions:
    permissions.build: true
    chairs.sit: true
    groups:
    - admin
    groups:
    default:
    permissions:
    permissions.build: true
    chairs.sit: true
    admin:
    permissions:
    permissions.*: true
    inheritance:
    - user
    user:
    permissions:
    permissions.build: true
    chairs.sit: true
    worlds:
    creative:
    coolplugin.item: true
    inheritance:
    - default
    messages:
    build: '&cYou do not have permission to build because you don't have a high enough rank.'

    debug: false

    This is really confusing to me... Then, when I do /permissions group list it says internal error, and the problem is:

    2012-04-29 22:32:42 [SEVERE] [PermissionsBukkit] Unable to load configuration!
    2012-04-29 22:32:47 [SEVERE] null
    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:473)
    at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821)
    at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764)
    at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.NullPointerException
    at com.platymuus.bukkit.permissions.PermissionsCommand.groupCommand(PermissionsCommand.java:167)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:146)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 12 more


    Please help... :(

    Nvrmind fixed it! Awesome plugin, helps alot.

    Would be great if there was like... A config file that was perfect, but easily customizable that you gave that someone could copy...

    Sorry for bothering... fixed it. Awesome!

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

    dendy77

    I deleted whole config.yml for Permission Bukkit, executed serer, and edited again new generated script .. now i haven't '[SEVERE] Unable to load ...' problem.. now really whole startup log is error-empty :

    Code:
    ./start_server.command 
    182 recipes
    27 achievements
    09:12:05 [INFO] Starting minecraft server version 1.2.5
    09:12:05 [INFO] Loading properties
    09:12:05 [INFO] Starting Minecraft server on *:25565
    09:12:05 [INFO] This server is running CraftBukkit version git-Bukkit-1.2.5-R1.0-b2149jnks (MC: 1.2.5) (Implementing API version 1.2.5-R1.0)
    09:12:05 [INFO] [jCommands] Loading jCommands v1.0.6
    09:12:05 [INFO] [PermissionsBukkit] Loading PermissionsBukkit v1.6
    09:12:05 [INFO] Preparing level "world"
    09:12:05 [INFO] Default game type: 0
    09:12:05 [INFO] Preparing start region for level 0 (Seed: -4260975644299510506)
    09:12:06 [INFO] Preparing start region for level 1 (Seed: -4260975644299510506)
    09:12:06 [INFO] Preparing spawn area: 77%
    09:12:06 [INFO] Preparing start region for level 2 (Seed: -4260975644299510506)
    09:12:06 [INFO] [jCommands] Enabling jCommands v1.0.6
    09:12:06 [INFO] [jCommands] Initializing Commands.
    09:12:06 [INFO] [jCommands] Initializing Events
    09:12:06 [INFO] [jCommands] jCommands v1.0.6 enabled.
    09:12:06 [INFO] [PermissionsBukkit] Enabling PermissionsBukkit v1.6
    09:12:06 [INFO] [PermissionsBukkit] Enabled successfully, 0 players registered
    09:12:06 [INFO] Server permissions file permissions.yml is empty, ignoring it
    09:12:06 [INFO] Done (1.565s)! For help, type "help" or "?"
    
    this is my config file:
    http://dl.dropbox.com/u/7116402/config.yml
    but it simply DOESN'T work ... :-( when i wlog on as dendy77, i can't use jcommands .. and same problem with any other plugin which i add to server and i add rights to PermissionBukkit config.yml file :-( i checkede multiple times if there are really spaces and correct indentation ... everything is ok .. without success :-(

    what is funny ? when i enter any jcommands cmd (logged as dendy77), i even didn't get error message 'You do not have permission to build here' ... it simply doesn't nothing .. but when i make /op dendy77 in server console, all jcommands works correctly ...
     
  6. Offline

    Arimanio

    I doubt it matters but I order my permission groups in the order that they inherit. So I'd put admin last. Not sure if YAML is a procedural language, but if it is, it doesn't get a chance to read the USER group before you ask it to inherit that group in admin. Also, ditch the entire permissions example under your name unless you're going to assign yourself specific nodes. 'permissions.example' is just that, a non-existent example and when the file goes looking for it, it will crash when it doesn't find it. Same with coolplugin.item. Also, ditch the worlds section under users unless you are going to have different permissions for different worlds on your server. With YAML, less is more.

    Edit: When I say procedural, I mean it's not Object Oriented. It can't bounce back and forth in the code but reads from top to bottom...nothing exists until it gets to that line. I verified that YAML is indeed procedural. So the order of your groups IS important if you are going to inherit from one group to the next.
     
  7. Offline

    TheMadProton

    What am i doing wrong? my permission file won't work:

    # 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:
    themadproton:
    permissions:
    permission.*: true
    groups:
    - admin
    dp519:
    permissions:
    permission.*: true
    groups:
    - mod
    comanderren98:
    groups:
    - guardian
    rideallday:
    groups:
    - builder
    complex69:
    permissions:
    permission.*: true
    groups:
    - imod
    groups:
    default:
    permissions:
    permissions.build: false
    simpleprefix.guest: true
    essentials.warp: true
    essentials.warp.*: true
    essentials.msg: true
    essentials.rules: true
    essentials.motd: true
    builder:
    permissions:
    permissions.build: true
    simpleprefix.builder: true
    pvparena.user: true
    essentials.kit.stonetools: true
    essentials.kit.minecart: true
    essentials.kit: true
    essentials.afk: true
    essentials.help: true
    essentials.msg: true
    essentials.near: true
    essentials.motd: true
    essentials.rules: true
    essentials.suicide: true
    essentials.whois: true
    essentials.back: true
    essentials.delhome: true
    essentials.home: true
    essentials.sethome: true
    essentials.warp: true
    essentials.warp.*: true
    essentials.ping: true
    essentials.back.ondeath: true
    inheritance:
    - default
    donator:
    permissions:
    permissions.build: true
    simpleprefix.donator: true
    pvparena.user: true
    essentials.fly: true
    essentials.feed: true
    essentials.kit.stonetools: true
    essentials.kit.minecart: true
    essentials.kit: true
    essentials.afk: true
    essentials.help: true
    essentials.msg: true
    essentials.near: true
    essentials.motd: true
    essentials.rules: true
    essentials.suicide: true
    essentials.whois: true
    essentials.back: true
    essentials.delhome: true
    essentials.home: true
    essentials.sethome: true
    essentials.warp: true
    essentials.warp.*: true
    essentials.ping: true
    essentials.teleport.timer.bypass: true
    inheritance:
    - builder
    guardian:
    permissions:
    permissions.build: true
    simpleprefix.guardian: true
    pvparena.user: true
    permissions.build: true
    simpleprefix.premium: true
    pvparena.user: true
    essentials.ext: true
    essentials.fly: true
    essentials.feed: true
    essentials.kit.stonetools: true
    essentials.kit.minecart: true
    essentials.kit: true
    essentials.afk: true
    essentials.help: true
    essentials.msg: true
    essentials.near: true
    essentials.motd: true
    essentials.rules: true
    essentials.suicide: true
    essentials.whois: true
    essentials.back: true
    essentials.delhome: true
    essentials.home: true
    essentials.sethome: true
    essentials.warp: true
    essentials.warp.*: true
    essentials.ping: true
    essentials.ban.notify: true
    essentials.weather: true
    essentials.tooglejail: true
    essentials.tooglejail.offline: true
    essentials.mute: true
    essentials.killall: true
    essentials.unban: true
    essentials.ban: true
    essentials.setwarp: true
    essentials.tp: true
    essentials.others: true
    essentials.tempban: true
    essentials.jump: true
    essentials.kick: true
    essentials.kick.notify: true
    inheritance:
    - donator
    mod:
    permissions:
    permissions.build: true
    simpleprefix.mod: true
    pvparena.*
    permission.*
    inheritance:
    - guardian
    admin:
    permissions:
    permission.*: true
    simpleprefix.admin: true
    inheritance:
    - mod
    messages:
    build: '&cYou do not have permission to build here.'
    debug: false



    when i try to type /perm group list this comes up:
    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:166)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:473)
    at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821)
    at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764)
    at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113)
    at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
    Caused by: java.lang.NullPointerException
    at com.platymuus.bukkit.permissions.PermissionsCommand.groupCommand(PermissionsCommand.java:167)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:146)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 12 more
     
  8. Offline

    dendy77

    no YAML isn't procedural.. order doesn't matter .. of course just to be sure i tried it, i also removed unused items, but it didn't help ...

    hm.. looks like PermissionsBukkit doesn't work on OSX .. i tried PermissionsEx and this works fine without troubles ...

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

    TheLavaGuy

    OOOOHHHH Thank you so much :D
     
  10. Offline

    hAAg108

    Anyone any ideas?
    Even with blank setup the config.yml en permissionsbukkit folder are not created.
     
  11. Offline

    Arimanio

    Post up your config.yml file.
     
  12. Offline

    hAAg108

    I have no config.yml file. It is not created nor is the folder.
     
  13. Offline

    Arimanio

    What O/S are using? If linux, consider changing the permissions on the plugins folder to 777, if it isn't already. I'm wondering if their are no permissions to write the folder and default config.yml file in the new server.
     
  14. Offline

    Snowy007

    Oh **** i missed a lot of questions...
    This is gonna take some time reading and thinking of answers. xD

    Unfortunately.. no thats not possible.

    Try re-downloading the plugin.

    The permissionsbukkit config contains empty lines. Remove those.

    Any errors in the console? Maybe try redownloading the plugin.

    Always put your configs in code tags please. This is totally unreadable. But from a quick look at it i noticed
    pvparena.*
    permission.*
    Those should have :true or :false behind them.

    The error this guy is having has nothing to do with the config.yml. (a miracle since 99.9% of the times its the config file) The error mentions it can't load the jar file because of an error in the 'plugin.yml'. The plugin.yml is a file inside the jar file.

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

    hAAg108

    New download did the trick. Thanks!

    Still think it's weird. I took a fresh download size 32 kb.
    Today's download is 20 kb......
    Will take a look at the difference in the plugin.yml file one day
     
  16. Offline

    ravenbomb

    im having problems :/
    Code:
     [WARNING] Server permissions file permissions.yml is not a valid YAML mapping values are not allowed here.
    in "<reader>", line 3, column 20:
                      Permissions:
                                 ^ 
    This is my perm file:
    Code:
     Users
        Ravenbomb:
            Permissions:
                permissions.*:true
                worldedit.*:true
            Groups:
            - &gOwner
     
    groups:
        Newbie:
            permissions:
                permissions.build: false
        &gOwner:
            Permissions:
                Worldedit.*:true
                Permissions.*:true
         
            
     
  17. Offline

    Snowy007

    Multiple things here are wrong.
    1. This should be in the 'config.yml' and not the 'permissions.yml'. The config.yml is in 'plugins/permissionsbukkit'
    2. There is an empty line. Never use empty lines.
    3. 'Users' is missing the : sign.
    4. Between : and true/false should be a space.
    5. You can't use color codes in the config. &g in front of 'owner' won't do a thing.
    This should be correct:

    Code:
    Users:
        Ravenbomb:
            Permissions:
                permissions.*: true
                worldedit.*: true
            Groups:
            - Owner
    groups:
        Newbie:
            permissions:
                permissions.build: false
        Owner:
            Permissions:
                Worldedit.*: true
                Permissions.*: true
     
  18. Offline

    ravenbomb

    how do i use color then?
     
  19. Offline

    Lego_Dude999

    It is pretty buggy for me i can't place blocks. [sheep]
     
  20. Offline

    RyGuy147

    A list of the default permissions that ship with Bukkit (the Bukkit commands) would be helpful.
     
  21. Offline

    GlowingIceicle

    Can someone tell me whats wrong with my code?

    Code:
    plugin:
        permissions:
            system: default
            copies:
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
                - 'essentials.help'
                - 'essentials.home'
                - 'essentials.motd'
                - 'essentials.rules'
                - 'essentials.sethome'
        Moderator:
            default: false
            info:
                prefix: '&d'
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'essentials.tp'
                - 'essentials.tphere'
        Admins:
            default: false
            info:
                prefix: '&c'
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    users:
        GlowingIceicle:
            group:Admins
            permissions
     
  22. Offline

    Snowy007

    This plugin does not change the chat to display someones group name. You need another plugin for that. I am using SimplePrefix for that but there are others too.

    Than you probably don't have the correct permisssion.

    http://wiki.bukkit.org/CraftBukkit_commands

    Everything is wrong with it. This is NOT how a config for PermissionsBukkit should look like. This is from a completely different permissions plugin.
     
  23. Offline

    PvtJelo

    Code:
    users:
        PvtJelo:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
        admin:
            permissions:
                coreprotect.inspect: true
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
    For some reason, when I try to do /co i (the command for the node) it doesn't work for admin, but when I put myself in default and put the /co i node there, it does work?
    Help please
     
  24. Offline

    Elements11997

    AHAHAHAHAHAA HE'S USING GROUPMANAGER, AHAHAHHAHAAHAHAHA
     
  25. Offline

    GlowingIceicle

    That actually helps. I had no idea what the heck I was doing.
     
  26. Offline

    Elements11997

    that's because according to your yml, the group 'admin' is higher in rank than your group 'user'. to fix this, simply put the group 'admin' after the group 'user'
     
  27. Offline

    Snowy007


    As far as i know the sequence of the groups does not matter. Its the inheritance that defines if a group is a 'higher' rank by giving the group the same permissions as the defined group.
    How else are you supposed to create 2 groups with completely different permissions. None of them would be any higher or lower than the other. xD
     
  28. Offline

    PvtJelo

    Than what's wrong with my permissions?
     
  29. Offline

    TheLavaGuy

    Why do I get error HERE then? :I

    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
      xfoondom:
        groups:
        - Owner
    groups:
      default:
        permissions:
          permissions.build: true
          essentials.kit: true
          essentials.kit.tools: ture
          essentials.motd: true
          creativegates.create: false
      VIP:
        permissions:
          essentials.motd: true
          essentials.enchant: true
          creativegates.create: false
      Admin:
        permissions:
          essentials.motd: true
          essentials.enchant: true
          permissions.command.give: true
          essentials.weather: true
          permissions.command.kick: true
          creativegates.create: false
      Mod:
        permissions:
          essentials.motd: true
          essentials.enchant: true
          permissions.command.give: true
          essentials.weather: true
          permissions.command.kick: true
          essentials.time: true
          permissions.command.time.set: true
          essentials.nick: true
          creativegates.create: false
      Executive:
        permissions:
          essentials.motd: true
          essentials.enchant: true
          permissions.command.give: true
          essentials.weather: true
          permissions.command.kick: true
          essentials.time: true
          permissions.command.time.set: true
          essentials.nick: true
          permissions.command.ban: true
          essentials.ban: true
          creativegates.create: false
      GM:
        permissions:
          essentials.motd: true
          essentials.enchant: true
          permissions.command.give: true
          essentials.weather: true
          permissions.command.kick: true
          essentials.time: true
          permissions.command.time.set: true
          essentials.nick: true
          permissions.command.ban: true
          essentials.ban: true
          essentials.broadcast: true
          creativegates.create: 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
     
  30. Offline

    GlowingIceicle

    Yah, I hope this is PermissionsBukkit, but i keep getting an error for the first chest shop nodes

    EDIT-I get the error that "chestshop.shop.buy" is "not valid YAML: while scanning a simple key" and for "chestshop.shop.sell" I got "could not find expected ':'"

    EDIT2-Did I mention I also cannot build?

    EDIT3 ^ Never mind the cross out!!! I still can't build and it's not because of spawn since i was well over 3000 blocks away!!!

    EDIT4 I Think if I add a space behind the nodes it works, but I dont know for sure. Could someone confirm this?

    EDIT5 WOW I made a lot of edits

    My plugins are:

    Essentials
    Factions
    MyHungerGames
    iConomy
    Jail
    Jobs
    Lockette
    MagicSpells
    MobArena
    NoCheat+
    Residence
    Towny
    TreasureHunt
    WorldEdit/Guard

    My code:

    Code:
    users:
        GlowingIceicle:
            groups:
            - Owner
    groups:
        Default:
            permissions:
                permissions.build: false
                essentials.spawn: true
                essentials.rules: true
                essentials.motd: true
                essentials.list: true
                essentials.helpop: true
                essentials.help: true
        Builder:
            permissions:
                permissions.build: true
                chestshop.shop.buy.itemID
                chestshop.shop.sell.itemID
                chestshop.shop.create.itemID
                factions.kit.halfplayer
                hungergame.user.join
                hungergame.user.leave
                hungergame.user.rejoin
                hungergame.user.list
                hungergame.user.stat
                hungergame.user.vote
                hungergame.user.sponsor
                hungergame.user.help
                jail.usercmd.jailstick
                jail.usercmd.jailstatus
                jail.usercmd.jailpay
                permissions.build. true
                essentials.afk. true
                essentials.back. true
                essentials.back.ondeath. true
                essentials.balance. true
                essentials.balance.others. true
                essentials.balancetop. true
                essentials.chat.color. true
                essentials.chat.shout. true
                essentials.chat.question. true
                essentials.compass. true
                essentials.depth. true
                essentials.home. true
                essentials.ignore. true
                essentials.kit. true
                essentials.kit.tools. true
                essentials.mail. true
                essentials.mail.send. true
                essentials.me. true
                essentials.msg. true
                essentials.nick. true
                essentials.pay. true
                essentials.ping. true
                essentials.powertool. true
                essentials.protect. true
                essentials.sethome. true
                essentials.signs.use.*. true
                essentials.signs.create.disposal. true
                essentials.signs.create.mail. true
                essentials.signs.create.protection. true
                essentials.signs.create.trade. true
                essentials.signs.break.disposal. true
                essentials.signs.break.mail. true
                essentials.signs.break.protection. true
                essentials.signs.break.trade. true
                essentials.suicide. true
                essentials.time. true
                essentials.tpa. true
                essentials.tpaccept. true
                essentials.tpahere. true
                essentials.tpdeny. true
                essentials.warp. true
                essentials.warp.list. true
                essentials.worth. true
            inheritance:
            - Default
        Moderator:
            permissions:
                permissions.build: true
                towny.claimed.*
                chestShop.mod
                factions.kit.fullplayer
                hungergame.add.game
                hungergame.add.spawnpoint
                hungergame.add.chest
                hungergame.remove.game
                hungergame.remove.spawnpoint
                hungergame.remove.chest
                hungergame.set.enabled
                hungergame.set.spawn
                hungergame.game.start
                hungergame.admin.reload
                hungergame.admin.kick
                hungergame.admin.help
                jail.command.jailcreate
                jail.command.jailcreatecells
                jail.command.jaildelete
                jail.command.jaildeletecells
                jail.command.jail
                jail.command.unjail
                jail.command.jailtransfer
                jail.command.jailtransferall
                jail.command.jailcheck
                jail.command.jailtelein
                jail.command.jailteleout
                jail.command.jaillist
                jail.command.jaillistcells
                jail.command.unjailforce
                jail.command.jailclear
                jail.command.jailclearforce
                jail.command.jailmute
                jail.command.jailstop
                essentials.ban. true
                essentials.ban.notify. true
                essentials.banip. true
                essentials.broadcast. true
                essentials.clearinventory. true
                essentials.delwarp. 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.kill. true
                essentials.mute. true
                essentials.nick.others. true
                essentials.realname. true
                essentials.setwarp. true
                essentials.signs.create.*. true
                essentials.signs.break.*. true
                essentials.spawner. true
                essentials.thunder. true
                essentials.time. true
                essentials.time.set. true
                essentials.protect.alerts. true
                essentials.protect.admin. true
                essentials.protect.ownerinfo. true
                essentials.ptime. true
                essentials.ptime.others. true
                essentials.togglejail. true
                essentials.top. true
                essentials.tp. true
                essentials.tphere. true
                essentials.tppos. true
                essentials.tptoggle. true
                essentials.unban. true
                essentials.unbanip. true
                essentials.weather. true
                essentials.whois. true
                essentials.world. true
            inheritance:
            - Builder
        Admin:
            permissions:
                permissions.*: true
                permissions.build: true
                towny.claimed.alltown.*
                Chestshop.*
                factions.kit.mod
                jail.modifyjail
                jail.openchest
                essentials.backup. true
                essentials.essentials. true
                essentials.setspawn. true
                essentials.reloadall. true
                essentials.*. true
            inheritance:
            - Moderator
        Owner:
            permissions:
                permissions.build: true
                towny.town*
                taien.th.admin
                worldguard.god
                worldguard.god.other
                worldguard.heal
                worldguard.heal.other
                worldguard.slay
                worldguard.slay.other
                worldguard.locate
                worldguard.stack
                worldguard.region.define
                worldguard.region.redifine
                worldguard.region.claim
                worldguard.region.select
                worldguard.region.info
                worldguard.region.list
                worldguard.region.flag
                worldguard.region.setpriority
                worldguard.region.setparent
                worldguard.region.remove
                worldguard.region.addmember
                worldguard.region.addowner
                worldguard.region.removemember
                worldguard.region.owner
                worldguard.fire-toggle.stop
                worldguard.reload
                worldguard.report
                worldguard.region.bypass.*
                worldedit.*
                -factions.kit.admin
                -essentials.backup. true
                -essentials.essentials. true
                -essentials.setspawn. true
                -essentials.reloadall. true
            inheritance:
            - Admin
    messages:
        build: '&cYou do not have permission to build here.'
    Really? 45 minutes and NO reply?

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

    Choppercon

    permissionsbukkit loads then i get this:

    Permission system not detected, defaulting to OP

    any help?
     

Share This Page