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

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

  1. Offline

    SpaceManiac

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

    Downloads:
    Current Version:

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

    [​IMG]

    Changelog:

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

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

    Snowy007


    already possible.
    /permissions player addgroup <player> <group>
     
  3. Offline

    Gesundheit

    How do I set the priority of each usergroups? For example:
    default: 1
    beginnerbuilder:2
    builder:3
    advancedbuilder:4
    admin:5

    Why I need this, is because I want to allow rank "builders" the right to set lower ranks under specific groups (default, beginnerbuilder).
    At the moment, when assigning permission "permissions.player.setgroup" to a builder he is able to set any rank to any user, for example taking admin rights from an administrator, or giving admin rights to whoever.

    Help is much appreciated.
     
  4. Offline

    Snowy007

    Not possible unfortunately. Had the same problem, my moderators where able to give themselves admin rights. :p
    Only solution is to give the permission only to trustworthy people. :p
    In my case, i just used the plugin 'CommandHelper' to block the command to set someone admin.
    Downside is that i can't use it either any more, but i only have 1 admin (me) and can always change that through config if i want to test something.
     
  5. Offline

    Gesundheit

    I'm really surprised to read that, because it would seem logical for a default/official permissions plugin to have such feature included. Very disappointing.

    But thank you for your advice, I'm also pretty much the only "ruler" and wish to stay that way, so I'll give CommandHelper a try :).

    Kind regards.
     
  6. Offline

    Snowy007

    CommandHelper is actually for creating aliases for commands and also macro's. The way i did it was by creating an alias leading to a bogus command. :p
    for example.
    usually u can make an alias like this:
    /t = /time
    but instead i did:
    /perm player setgroup $player admin = /NotExistingCommand
    So every time a moderator tries to use the setgroup command to turn someone into an admin, it tells him that the command doesn't exist because it tries to run /NotExistingCommand. :p
     
  7. Offline

    Gesundheit

    That's one way to do it :p, I had a little different approach:

    defaultgroup:/tee $p1 vaatlejaks = runas('~op', sconcat(/permissions player removegroup $p1 ehitaja-))
    ehitajagroup:/tee $p1 ehitajaks = runas('~op', sconcat(/permissions player addgroup $p1 ehitaja-))

    While having access to the aliases labeled "defaultgroup" and "ehitajagroup", the builder still need permissions.player.addgroup and -.-.removegroup, so to bypass that, builders have to run the alias-command as OP.

    Of course it doesn't really matter how you approach to it, but with your version alot more aliases have to be made just to disallow the /perm /permissions /perms (more?) to every single higher/same ranking.

    So basically, I believe your configuration is something like this:
    /perm player setgroup $player admin = /NotExistingCommand
    /perms player setgroup $player admin = /NotExistingCommand
    /permissions player setgroup $player admin = /NotExistingCommand
    /perm player setgroup $player moderator = /NotExistingCommand
    /perms player setgroup $player moderator = /NotExistingCommand
    /permissions player setgroup $player moderator = /NotExistingCommand
    etc

    while mine is a little more compact, but that just about it, both are a way to approach to this and I thank you for letting me know of this useful plugin! I appreciate this alot! :)

    Kindest regards,
    Gesundheit
     
  8. Offline

    W&L-Craft

    The first time i opened the config i saw this:
    user:
    permissions:
    permissions.build: true
    worlds:
    creative:
    coolplugin.item: true
    inheritance:
    - default

    My question is: what does that world: creative: thing mean??
     
  9. Offline

    purloi

    I'm trying to set up CraftBook on my server. We had an issue with players not having permission to use any of CraftBook's features. It tell's them they don't have permission. So I installed PermissionsBukkit. I know this worked, because before I edited the config, players were not allowed to do anything! I added a couple names to the Trusted group, and now they seem to have normal playable access, but still no CraftBook abilities. The CraftBook site (http://wiki.sk89q.com/wiki/CraftBook/Configuration) only list a handfull of possible permissions. I will post my config below. What did I miss?

    Code:
    groups:
        Default:
            default: true
            prefix: '[Guest]'
            suffix: ''
            permissions:
            - bukkit.command.list
            - bukkit.command.help
            - -bukkit.command.version
            - -bukkit.command.plugins
        Trusted:
            prefix: '[Member]'
            suffix: ''
            permissions:
            - bukkit.command.version
            - bukkit.command.plugins
            - craftbook.mech.ammeter.use
            - craftbook.mech.bridge
            - craftbook.mech.bookshelf.use
            - craftbook.mech.cauldron
            - craftbook.mech.elevator.use
            - craftbook.mech.door
            - craftbook.mech.door.use
            - craftbook.mech.gate
            - craftbook.mech.light-switch
            - craftbook.ic.safe.*
            - craftbook.ic.restricted.*
            inheritance:
            - Default
        Moderator:
            prefix: '[Mod]'
            suffix: ''
            permissions:
            - bukkit.command.kick
            - bukkit.command.ban.*
            - bukkit.command.unban.*
            inheritance:
            - Trusted
        Admin:
            prefix: '[Admin]'
            suffix: ''
            permissions:
            - '*'
            inheritance:
            - Moderator
    users:
        purloii:
            group:
            - admin
        zunft:
            group:
            - trusted
        mcmoo:
            group:
            - trusted
    
     
  10. Found an issue with 1.6, [SEVERE] unable to load configuration!
    Then on the next line it says : Enabled successfully, 0 players registered.

    Doesn't seem to be working, I'm going to have to use 1.2.
     
  11. Offline

    Milkywayz

    To be honest this plugin was pretty awesome for a long time, on my server I just today switched to PEX because space hasn't updated this in so long.
     
  12. Offline

    Exigo

    Could somebody help me.
    I built a flame and arrow turret put a sign on it etc, but when I want to trigger it by taking the redstone, I get some weird long errors in my console!
     
  13. Offline

    Snowy007

    Its an example showing how to give permissions to a group, only in certain worlds. In this case 'creative' is the name of the world.

    Delete the config and start over. This looks nothing like how a PermissionsBukkit config should look like. If you want an example, it generates one when it can't find any. If you want more examples, look throughout this forum. You should be able to find hundreds.

    You did something wrong in your config.

    Why would he update? Its working perfectly fine. As long as you don't make any mistakes in the config. It seems though that the standard generated config has mistakes in it... It leaves an empty line at the bottom just above 'debug:'

    What does that have to do with this plugin? I think your in the wrong forum xD
     
  14. Offline

    Milkywayz

    I didn't make any mistakes in the config, and i've used permissions bukkit since it came out last year. What does he need to update? Coming from a server owner, a lot. The plugin is ancient, no per world permissions is a big loss. You can't remove people from your config who haven't been on in awhile. Those are just features, a lot of people have had issues with his plugin yet he has not supported it in a long time. I made the switch to permissions ex and I do miss permissions bukkit But I'm not going to stick with a plugin that's vastly outdated. Other permissions plugins have features that make permissions bukkit extinct.
     
  15. Offline

    Snowy007

    True, there are things that he could add and things that he could have done better. But its working fine though and it does have per-world permissions.

    Code:
      builder:
        permissions:
          permissions.build: true             /global permissions
          simpleprefix.default: false
          simpleprefix.builder: true
        worlds:
          world:
            server.creative.builder: true      /per-world permissions
          survival:
            server.survival.builder: true
        inheritance:
        - default
     
  16. Offline

    Milkywayz

    What about the fact that you can't change the default rank, the fact that in order to rank somebody you need to use a long command, and that you need to type : true for every permission unlike PEX where you only type extra if your negating something which isnt often.
     
  17. Offline

    Snowy007

    1. changing default rank
    why would you want to? Its not like the name appears in-game. I do agree though that group prefixes should be something a permissions plugin should do. Now you need to download a different plugin for that. The good thing about this though, if you use something like 'SimplePrefix' you can change the prefixes however you want, and even different prefixes per-world.

    2. Long command
    Yea, that was something i didn't like either. I however use 'CommandHelper' so i was easily able to shorten the command myself. I think there was a way to create command aliases in a CraftBukkit config file somewhere too.

    3. Needing ': true'
    Well... to be honest, i think it makes it more clear to have true or false at each node. But that is just a personal opinion.

    But yea, it does indeed miss a few things that you would expect from a permissions plugin. Nothing really important in my own opinion though.
     
  18. Offline

    Milkywayz

    I used to defend permissions bukkit but i found it was just easier to move to a perms plugin that was actively supported by the author.
     
    dark_hunter likes this.
  19. Offline

    dark_hunter

    Correct, I moved to PEX, best thing I did in the world.
     
  20. Offline

    AcelinH98

    Help! I just did my permissions perfectly I use to set-up permissions (This one) for other servers and they have alway's worked. But for some reason when I join my server my name is white and it has no tag infront, when I used MChat.
    Why is this?
     
  21. Offline

    Chartax

    I searched around for this, and I'm sorry if there has been an answer:

    Is there support for MySQL in the latest version?

    Thanks,
    Chartax.
     
  22. Offline

    RaptorSB

    Okay, brand new at all of this, and so very confused. I know absolutely nothing about doing the permissions, what commands need to be put in where or how they need to be put. Right now, I've got the base config.yml and have just put the player into the groups.

    These are the plugins I have:
    BOSEconomy
    ChestShop
    Essentials
    LWC
    PermissionsBukkit
    Residence
    McMMO
    mcjobs

    Once I added PermissionsBukkit, my players lost almost all the base commands that were available. I 'think' that I only need to worry about Essentials commands, so where do I go to find out what those are and how to put them into the permissions for groups? Here is how I'm basically wanting to setup the groups: Default just come in and look around, 1 group that can do basic stuff (current permission levels), 2nd group that can msg/home/spawn/warp, a moderator group and finally the Admin. With my current setup, I'm thinking I only need help with the 2nd group and moderator.

    Any help and suggestions would be greatly appreciated. Thanks!
     
  23. Offline

    Snowy007


    Well... you must have done 'something' wrong. Either a small mistake somewhere in the PermissionsBukkit config, or a mistake in the MChat config.



    No, PermissionsBukkit unfortunately does not support MySQL

    You can usually find the permission nodes on the plugin pages.
    For example "essentials.item" will allow access to the /item command. So if you put "essentials.item: true" at one of your groups, everyone in that group will be able to use that command. And if you use inheritance, all the higher rank groups will also have it.
     
  24. Offline

    Brian McNamara

    Hey having somewhat of a weird problem that im not sure where its coming from.

    I have 3 users, myself (op/admin) and two users with only certain commands. They are able to build and modify however there are spots on the map they cant build or modify the blocks. A weird example was one user built a fence but when he went to add a second layer onto the fence some posts would not allow it, it would just flash the post being built and than dissapear. Does anyone have any idea what may cause this? Im running the stable version of bukkit 0222 i think, 1.6 permissionsbukkit and the latest of essentials.

    Anyone have any ideas?

    btw, not getting any errors in the server log, when the server starts up or when they place a unplaceable block
     
  25. Offline

    Snowy007

    Might be caused by lag?
    Other than that, i don't really know what else could be the problem. If they are able to build, they should be able to build everywhere. Unless you use another plugin like WorldGuard to create private regions.
     
  26. Offline

    RaptorSB

    Snowy007, thanks for the help!

    I had things setup and it people could play, it said people were in the correct groups. Then... I made some changes to the names of the groups and added a user (I've been manually adding the users, since for some reason I can't get it to do so in the game). Here's my config (without the user's), hope this pastes correctly...


    groups:
    default:
    permissions:
    permissions.build: false
    Apprentice:
    permissions:
    permissions.build: false
    simpleprefix.apprentice: true
    Adpet:
    permissions:
    residence.admin: true
    permissions.*: true
    simpleprefix.adept: true
    inheritance:
    - Master
    - Journeyman
    - Apprentice
    Master:
    permissions:
    essentials.back: true
    essentials.home: true
    essentials.list: true
    essentials.mail: true
    essentials.msg: true
    essentials.getpos: true
    permissions.build: true
    simpleprefix.master: true
    worlds:
    creative:
    coolplugin.item: true
    inheritance:
    - Apprentice
    - Journeyman
    Journeyman:
    permissions:
    essentials.spawn: true
    essentials.itemdb: true
    essentials.worth: true
    permissions.build: true
    simpleprefix.journeyman: true
    worlds:
    creative:
    coolplugin.item: true
    inheritance:
    - Apprentice
    messages:
    build: '&cYou do not have permission to build here.'
    debug: false

    So, my question is... Where am I doing something wrong? This is off of the template that the base permissions.yml has. Thanks for any help or suggestions!
     
  27. Offline

    Crashtopher

    I'm having troubles with this. Every time I redownload this permissions plugin, I nor anyone else can edit anything. I've added permissions and everything via instructions, but it still does it. When i delete the plugin, it works fine.
     
  28. Offline

    Snowy007

    Try putting it in code tags. Its really difficult to read this way without indention. Also please include the users. At first sight i can't really see anything wrong with this part of your config. Since you have been manually adding users, you might have made a mistake with group names or something.
    Also check that you don't have any empty lines in your config. PermissionsBukkit doesn't seem to like empty lines. xD
    Oh, and also important. Make sure that you use spaces for indention and not tabs. (4 spaces = 1 tab).

    Make sure that the group that should be able to build, has the 'permissions.build: true' node.
     
  29. Offline

    Crashtopher

    Yeah, already triple checked that before I posted that.
     
  30. Offline

    Snowy007

    So basically, nobody is able to build with this plugin, even though they have 'permissions.build: true' ?
    Maybe try posting your config here. 'something' must be wrong in the config or its another plugin causing it. (perhaps denied build rights globally with worldguard or something?)
     
  31. Offline

    Crashtopher

    Well, I don't have Worldguard. I'll redownload PermissionsBukkit and show you config.

    It seems I can't find the permissionsbukkit zip that i had the other times.

    Wait, I just took it out of the recycle bin. Here's the config:

    Code:
    # PermissionsBukkit configuration file
    #
    # A permission node is a string like 'permissions.build', usually starting
    # with the name of the plugin. Refer to a plugin's documentation for what
    # permissions it cares about. Each node should be followed by true to grant
    # that permission or false to revoke it, as in 'permissions.build: true'.
    # Some plugins provide permission nodes that map to a group of permissions -
    # for example, PermissionsBukkit has 'permissions.*', which automatically
    # grants all admin permissions. You can also specify false for permissions
    # of this type.
    #
    # Users inherit permissions from the groups they are a part of. If a user is
    # not specified here, or does not have a 'groups' node, they will be in the
    # group 'default'. Permissions for individual users may also be specified by
    # using a 'permissions' node with a list of permission nodes, which will
    # override their group permissions. World permissions may be assigned to
    # users with a 'worlds:' entry.
    #
    # Groups can be assigned to players and all their permissions will also be
    # assigned to those players. Groups can also inherit permissions from other
    # groups. Like user permissions, groups may override the permissions of their
    # parent group(s). Unlike users, groups do NOT automatically inherit from
    # default. World permissions may be assigned to groups with a 'worlds:' entry.
    #
    # The cannot-build message is configurable. If it is left blank, no message
    # will be displayed to the player if PermissionsBukkit prevents them from
    # building, digging, or interacting with a block. Use '&' characters to
    # signify color codes.
    users:
        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.'
    debug: false
    EDIT:I added a permissions folder to it, cause it wasn't already there the time i downloaded it. EDIT:But i just moved the permissions notepad page into the 'permissions' folder' I just restored.
    EDIT: I just went on my server and I can place blocks. But I still see no ranks at all (IDK if you're supposed to add it in the permissions document or somewhere else :/)

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

Share This Page