[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

    x0wNd

    everytime i start up my server i get this:
    22:55:58 [WARNING] Server permissions file permissions.yml is not valid YAML.
    java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Map at org.bukkit.craftbukkit.CraftServer.loadCustomPermissions(CraftServer. java:564) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:238 ) at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:371) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:358) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:187) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:422) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
     
  3. Offline

    Snowy007

    Then that guy has it wrong. :p You should never use tabs when working with yml files.

    Have you read the 1st line of the error? It obviously states that there is a problem with your 'permissions.yml' file. So i really can't help much if you don't show it.

    I have this feeling though that i already know what you did wrong. For some reason there are more people that this wrong. The permissions.yml is NOT the file where you have your users and groups. The users and groups should go into the 'plugins => permissionsbukkit => config.yml' file. The permissions.yml is only for grouping multiple nodes into a single node.
     
  4. Offline

    Gotomtom95

    can you guys build in that grouped permission nodes like so:
    Code:
    groups:
      user:
        permissions:
          commandbook:
            who: true
            motd: true
            rules: true
            time.check: true
            spawn: false
          bukkit.command:
            tell: true
            kill: true
            me: true
            save.perform: true
            list: true
            version: true
            plugins: true
        worlds:
          CreaSky:
            worldedit:
              wand: true
              history.undo: true
              region:
                set: true
                replace: true
              selection:
                outset: true
                inset: true
                expand: true
                contract: true
                pos: true
                hpos: true
              navigation:
                unstuck: true
                ascend: true
                descend: true
                thru: true
    stay that way after permissions reload.
    It currently does know how to handle it if I enter it like so, but it displays an error and edits everything back to normal nodes.

    I find this way would increase readability of the permissions file
     
  5. Offline

    Riolu

    I'm sorry, I got one more problem.
    I set up all permissions nodes (for WorldEdit, CommandBook, etc.) for user group, but default group players (that players which can't build) still can use all (even OP's only) functions of plugins exept that they still can't build.
    Even when I set up permissions nodes and set false flag dor that default group, players still can use any functions.

    HTML:
    users:
        Riosha:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            permissions:
                commandbook.who: true
                commandbook.motd: true
                commandbook.intro: true
                commandbook.rules: true
                commandbook.kit.*: true
                commandbook.time.check: true
                commandbook.biome.*: true
                commandbook.call: true
                commandbook.say.*: true
                commandbook.msg: true
                commandbook.away: true
                commandbook.whereami.*: true
                commandbook.clear: true
                commandbook.whois.*: true
                commandbook.ip-address: true
                lwc.protect: true
                permissions.build: true
                worldguard.region.claim: true
                worldguard.region.info.*: true
                worldguard.region.addowner.*: true
                worldguard.region.removeowner.*: true
                worldguard.region.addmember.*: true
                worldguard.region.removemember.*: true
                worldguard.region.list.own: true
                worldguard.region.flag.regions.*: true
                worldguard.region.setpriority.*: true
                worldguard.region.setparent.*: true
                worldguard.region.remove.*: true
        inheritance:
        - default
        admin:
            permissions:
                permissions.*: true
        inheritance:
        - user
    messages:
        build: '&cYou not avalible to build.'
    debug: false
     
  6. Offline

    Gotomtom95

    you should try raising your inheritance a level, its now on the same level as the groups.

    so, according to this, you have a group 'default', 'user', 'admin' and two times a group 'inheritance'

    asuming this is all exactly like it is in your permissions file

    ps, did you configure this in notepad++?
    yaml config.png
    (sorry, mine is in dutch, but i hope you get the idea)
     
  7. Offline

    Riolu

    Sorry, I don't get it. Can you explain by fix my code?
    PHP:
    users:
        
    Riosha:
            
    groups:
            - 
    admin
    groups
    :
        default:
            
    permissions:
                
    permissions.buildfalse
        user
    :
            
    permissions:
                
    commandbook.whotrue
                commandbook
    .motdtrue
                commandbook
    .introtrue
                commandbook
    .rulestrue
                commandbook
    .kit.*: true
                commandbook
    .time.checktrue
                commandbook
    .biome.*: true
                commandbook
    .calltrue
                commandbook
    .say.*: true
                commandbook
    .msgtrue
                commandbook
    .awaytrue
                commandbook
    .whereami.*: true
                commandbook
    .cleartrue
                commandbook
    .whois.*: true
                commandbook
    .ip-addresstrue
                lwc
    .protecttrue
                permissions
    .buildtrue
                worldguard
    .region.claimtrue
                worldguard
    .region.info.*: true
                worldguard
    .region.addowner.*: true
                worldguard
    .region.removeowner.*: true
                worldguard
    .region.addmember.*: true
                worldguard
    .region.removemember.*: true
                worldguard
    .region.list.owntrue
                worldguard
    .region.flag.regions.*: true
                worldguard
    .region.setpriority.*: true
                worldguard
    .region.setparent.*: true
                worldguard
    .region.remove.*: true
        inheritance
    :
        - default
        
    admin:
            
    permissions:
                
    permissions.*: true
        inheritance
    :
        - 
    user
    messages
    :
        
    build'&cYou not avalible to build.'
    debugfalse
     
  8. Offline

    shanko

    Im tempted to switch permissions plugins, reloading this config is absoloutly horrible and nearly crashes the server
     
  9. Offline

    Gotomtom95

    what you had:
    Code:
    groups:
        user:
            permissions:
                [...]
        inheritance:
        - default
        admin:
            permissions:
                permissions.*: true
        inheritance:
        - user
    how it should be:
    Code:
    groups:
        user:
            permissions:
                [...]
            inheritance:
            - default
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
    you had the inheritance wrong, and like so it is correct

    bumping this

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

    iCnHunter

    Can someone please help me with this. People on my server are not getting the commands I have tried to give them. If I give them "permissions.build" they still cant build. I have rewritten my config code a couple times hoping I would fix it the next time. Here is my current one I am trying to test everything with and its not working:

    Code:
    Users:
      mrnox:
        group:
        - user
      permissions:
        permissions.build: true
        group:
        - admin
    groups:
      default:
        permissions:
          permissions.build: false
          server.basics: true
      user:
        permissions:
          permissions.build: true
          zp.use: true
          inheritance:
          - default
      Admin:
        permissions.build: true
        jaillikehell.wand: true
    messages:
      build: "&cYou do not have permission to build!"
    
    I am doing this on NotePad++ by the way.
     
  11. Offline

    Gotomtom95

    It Could be your permissions.yml not working. I'm not saying it's not configured incorrectly, but I noticed on my own server that the permission nodes created in permissions.yml stopped working. So any of those nodes don't actually work :(

    your permissions file looks just fine by the way, only that you have forgotten to add "permissions:" to the admin group.
     
  12. Offline

    iCnHunter

    Ok thanks. I am not very good with the .yml one I copied one I found online for the sake of testing but it still did not work. It looks like this:

    Code:
    server.basics:
      description: Basic permissions for iCnHunter.
      default: true
      children:
        commandbook.motd: true
        commandbook.say: true
        commandbook.say.me: true
        commandbook.time: true
    server.admin:
      description: Admin permissions of iCnHunter.
      default: Admin
      children:
        commandbook.broadcast: true
        commandbook.teleport: true
        commandbook.kick: true
        commandbook.ban: true
     
  13. Offline

    Gotomtom95

    That looks ok to me :p
    taking that you actually have commandbook, that is.

    so as far as I know, these nodes currently don't work
     
  14. Offline

    iCnHunter

    Is there anything I can do to fix my problem?
     
  15. Offline

    Gotomtom95

    put the nodes in your permissions config file.
     
  16. Offline

    iCnHunter

    I dont understand what you mean. explain?
     
  17. Offline

    Riolu

    That didn't help me, I'm sorry.
     
  18. Offline

    Gotomtom95

    everything that you now have defined in your permissions.yml you now put like normal permissions in your config.yml of permissionsbukkit
     
  19. Offline

    Kidd0Elite

    Hi, I heard it was possible to make it so Admins can't be banned, sorry to bother you but I can't figure out how to do this, could you please give me an explanation as to how I would be able to do this?

    Thank you for your time
     
  20. Offline

    PickMaster1119

    EDIT: I didn't do enough spaces, so I fixed it now. Thx for this plugin!

    While I was using PB and Simple Prefix, I tried to change my group with /perms player setgroup [name] owner, and it came up with this error:
    15:44:19 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'perm
    s' in plugin PermissionsBukkit v1.6
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:16
    6)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:4
    73)
    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:7
    8)
    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.createPlayerNode(
    PermissionsCommand.java:400)
    at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(Per
    missionsCommand.java:286)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(Permiss
    ionsCommand.java:152)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 12 more
    and these are my files:
    Simple Prefix:
    Template:
    format: '<[world] [prefix][name][suffix]> '
    time: '[h:mm aa]'
    Worlds:
    world:
    nickname: '&e[World]&f'
    Group:
    owner:
    prefix: '&2[Owner]&f'
    suffix: ''
    admin:
    prefix: '&4[Admin]&7'
    suffix: ''
    user:
    prefix: '&1[Member]&2'
    suffix: ''
    default:
    prefix: '&8[Guest]&0'
    suffix: ''
    User:
    Flabaliki:
    prefix: '&c[Who?]&f'
    suffix: ''
    PermissionsBukkit:
    users:
    ConspiracyWizard:
    permissions:
    permissions.example: true
    groups:
    - admin
    pickmaster1119:
    groups:
    - owner
    groups:
    default:
    permissions:
    permissions.build: false
    simpleprefix.default: true
    admin:
    permissions:
    permissions.*: true
    simpleprefix.admin: true
    inheritance:
    - user
    user:
    permissions:
    permissions.build: true
    simpleprefix.user: true
    worlds:
    world:
    coolplugin.item: true
    inheritance:
    - default
    owner:
    permissions:
    permissions.*: true
    simpleprefix.owner: true
    inheritance:
    - user
    messages:
    build: '&cYou do not have permission to build here.'
    debug: false
     
  21. Offline

    space_invader

    hello,

    this mite seem of a bit stupid question but how do i configer it so they cant get creative?
     
  22. Offline

    Slizz3r

    I need some help, I'm pretty sure I'm doing everything right, but for some reason i cant use the command "/permissions player setgroup <name> <group>"
    Here is my tiny permissions config: http://pastebin.com/J2SLZfNq

    All I really need to do, is set everyone to the default group. I know you start out as default, but for this, you dont seem to start out as any group. Just help me xD
     
  23. Offline

    Gotomtom95

    that is because every line of the user part you wrote is part of "ConspiracyWizard"

    you need take a tab (4 spaces) from every line that holds the name of a player
     
  24. Offline

    Riolu

    Well, it's actually already there. My permissions.yml (that one in server folder) is empty.
     
  25. Offline

    Snowy007

    Oh my god.... the amount of questions in this topic is too damn high! xD
    Ok.. sorry if not all questions get answered.. i'm not a miracle worker. :p


    I never used any nodes like nor have i seen anyone else use them like this. As far as i know this is not possible and you just have to list the nodes like normal. If you are hoping for a reply by the developer you'r out of luck. He doesn't really seem to reply on comments any more.


    What? I never have any problems with reloading the config. Do you have other problems like commands or permissions not working?


    There's some mistakes there. The smallest mistakes can cause the whole plugin to not function correctly.
    First of all, you used 'groups:' 2 times below 'mrnox'.
    2nd, 'permissions:' and 'permissions.build' under the 'mrnox' user should be 2 spaces further. It is now at the same level at a user and obviously 'permissions' is not a user.
    3rd, as Gotomtom95 already mentioned, you are missing 'permissions:' below the admin group.
    4th, there should be a 'debug:' node at the bottom. Not sure if it matters but as i said, smallest mistake can cause it.
    This is with all the above fixes:
    Code:
    Users:
      mrnox:
        permissions:
          permissions.build: true
        group:
        - admin
    groups:
      default:
        permissions:
          permissions.build: false
          server.basics: true
      user:
        permissions:
          permissions.build: true
          zp.use: true
          inheritance:
          - default
      Admin:
        permissions:
          permissions.build: true
          jaillikehell.wand: true
    messages:
      build: '&cYou do not have permission to build in this world.'
    debug: false
    The 'inheritance:' should be 2 spaces further like this:
    Code:
    users:
        Riosha:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            permissions:
                commandbook.who: true
                commandbook.motd: true
                commandbook.intro: true
                commandbook.rules: true
                commandbook.kit.*: true
                commandbook.time.check: true
                commandbook.biome.*: true
                commandbook.call: true
                commandbook.say.*: true
                commandbook.msg: true
                commandbook.away: true
                commandbook.whereami.*: true
                commandbook.clear: true
                commandbook.whois.*: true
                commandbook.ip-address: true
                lwc.protect: true
                permissions.build: true
                worldguard.region.claim: true
                worldguard.region.info.*: true
                worldguard.region.addowner.*: true
                worldguard.region.removeowner.*: true
                worldguard.region.addmember.*: true
                worldguard.region.removemember.*: true
                worldguard.region.list.own: true
                worldguard.region.flag.regions.*: true
                worldguard.region.setpriority.*: true
                worldguard.region.setparent.*: true
                worldguard.region.remove.*: true
          inheritance:
          - default
        admin:
            permissions:
                permissions.*: true
          inheritance:
          - user
    messages:
        build: '&cYou not avalible to build.'
    debug: false
     
  26. Offline

    Riolu

    Well, fine. Now default group players can build, whatever they actually have only one node permissions.build: false
    Uhh, I yeti style of permissions.
     
  27. Offline

    Snowy007

    Banning is not something this permissions plugin handles. You should check for plugins that let you ban players and check if those have an option to prevent certain players/groups from being banned.

    Depends on the plugin you are using that allows the /gamemode command to be used by non-op's. Just don't give players the node for it or give them the node with 'false'.

    As Gotomtom95 already mentioned, your users are not aligned correctly. Also there are 2 empty lines in your config. Corrected version:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
        Stuey1996:
            groups:
            -default
        Blake1996:
            groups:
            -default
        on_the_rise:
            groups:
            -default
        Pr3ddzk:
            groups:
            -default
    groups:
        default:
            permissions:
                permissions.build: true
                permissions.player.setgroup: true
                permissions.player.addgroup: true
                permissions.player.setperm: true
                essentials.tpa: true
                essentials.tpaccept: true
                essentials.tpdeny: true
                simplechestlock.lock: true
                simplechestlock.locktype.chest : true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here umad?.'
    debug: false
    wait.. sorry, my mistake. You use 4 spaces indention each level not 2....
    This should be better:
    Code:
    users:
        Riosha:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            permissions:
                commandbook.who: true
                commandbook.motd: true
                commandbook.intro: true
                commandbook.rules: true
                commandbook.kit.*: true
                commandbook.time.check: true
                commandbook.biome.*: true
                commandbook.call: true
                commandbook.say.*: true
                commandbook.msg: true
                commandbook.away: true
                commandbook.whereami.*: true
                commandbook.clear: true
                commandbook.whois.*: true
                commandbook.ip-address: true
                lwc.protect: true
                permissions.build: true
                worldguard.region.claim: true
                worldguard.region.info.*: true
                worldguard.region.addowner.*: true
                worldguard.region.removeowner.*: true
                worldguard.region.addmember.*: true
                worldguard.region.removemember.*: true
                worldguard.region.list.own: true
                worldguard.region.flag.regions.*: true
                worldguard.region.setpriority.*: true
                worldguard.region.setparent.*: true
                worldguard.region.remove.*: true
            inheritance:
            - default
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
    messages:
        build: '&cYou not avalible to build.'
    debug: false
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  28. Offline

    Riolu

    Well, now they can't build, yes, but still can use unallowed (actually is) commands.
    Let me explain correctly:
    I change my name at
    PHP:
    users:
        
    Riosha:
            
    groups:
            - 
    admin
    to name "someone" (just to being like not admin and test).
    Right, I transformed to default group and can't build because of node build false
    PHP:
    groups:
        default:
            
    permissions:
                
    permissions.buildfalse
    But I still can use ANY command from any plugins. Even is I don't even add node in user group.
    I guess default group somehow use permissions.*: true node. But even when I add it there and set false
    PHP:
    groups:
        default:
            
    permissions:
                
    permissions.buildfalse
                permissions
    .*: false
    That didn't help me. And they still can use any command. :(
     
  29. Offline

    Snowy007

    Are you OP?
    If i remember correctly there is an option in Commandbook that lets all OP's have access to all permissions.
     
  30. Offline

    Riolu

    No, I don't add myself at OP's.
    But wait, I guess I was always must RESTART server, not just realod.
    Now I did and everything work (I hope).

    Thank you for help, anyway :)
     
  31. Offline

    Kidd0Elite

    Snowy007, you mentioned a plugin, don't go out of your way but do you know of any plugins that are able to this?
     

Share This Page