[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

    goatpig

    I owe you Snow! It's working now, for the first time in months. :D
     
  3. Offline

    Snowy007

    Glad it is working now. :p


    @Disparate
    I've got it working for pretty much everyone except for you, by only changing things in their configs. was421 Thanked me through pm and even madmac (who also claimed it could not be his config and of who you said you where getting the exact same error.) is now very happy that it is working for him.
    I just want to say, my offer to take a look at your config still stands. You can even sent it through pm like madmac did if you don't want to just post it here.

    Also a mistake that some people seem to make as well... make sure that your config with groups and users is in your config.yml in the 'plugins/permissionsbukkit' folder and NOT the permissions.yml in the root.
     
  4. Offline

    budpup67

    Im Positive. when i say /pl it says Permissionsbukkit in the list of Plugins
     
  5. Offline

    Snowy007

    Try this, not only did i remove the empty line at the bottom but also the empty line at the top. The rest seems to be fine.
    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
     
  6. Offline

    I3eny

    Hey, Where can i find a total noobs guide to setting this up, im guessing this is for separating PLAYERS from ADMINS, and Donators (VIP) from other players.
     
  7. Offline

    KrisEike

    Awesome plugin, thanks for it!
     
  8. Offline

    ForsakenRealmz

    So.. I'm having some trouble. I've been using PermissionsBukkit for over 4 months, and now I'm running into problems.

    PermissionsBukkit v1.2 works exactly how I want it to work for me. But the only ONLY problem is that there are no in-game/cmd commands for it. I cannot type in /permissions and reload the config or anything.

    PermissionsBukkit v1.6 works exactly how I DON'T want it to work. It doesn't place the people in the default group and there is no choice for people to be automatically placed in it. Is this a problem for everyone or just me?
     
  9. Offline

    Snowy007

    Yes that is correct, you can create multiple groups and you can decide which permissions these groups (or individual players) should have. I don't really know of any guide though but i would suggest you just install it on a test server and try to figure out how it works. Just read the description and take a look at the example config file.
    Most plugins have different nodes you can give to groups. They should mention the nodes on their plugin page or a wiki page or something.

    You probably have a minor mistake somewhere in your config. The plugin seems to be a lot more strict in 1.6 and minor mistakes could make the whole plugin to not load your config and/or make the commands unusable.
    If you can show me the config i could take a look at it.
     
  10. Offline

    Disparate

    I may take you up on that. I have spent 5 days trying to get this POS to work and for about 48 hours it DID work, right up until it deleted its own config.

    The way I got it to even begin to work was, oddly, deleteing all members bar me. That at least made it load! However, the real crazy then began. Ever single time I promoted or demoted someone, it would reformat the ENTIRE config, one moment having it spaced normally, the next grouping all related permisisons under sub nodes and then the next putting it back to normal.:eek:

    I will PM you my config when I get a chance and give you my email and I will take any help you are willing to give me because I am at my wits end. Even if it ends up working though, SpaceManiac should be dragged out into the street and slapped about for this incompetence...:mad:
     
  11. Offline

    shazman333

    I have been trying to make this work and google the problem, cant solve it.
    Would really appriciate if someone could help me!
    Well, i want to make that the group "User" not to be able to use the "give" command at all.
    Well thats my problem. Help appreciated.



    This is what i tried to do
    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:
      Sebbe:
        permissions:
          permissions.example: true
        groups:
        - user
    groups:
      default:
        permissions:
          permissions.build: false
      admin:
        permissions:
          permissions.*: true
        inheritance:
        - user
      user:
        permissions:
          permissions.build: true
          Give.*: false
          worlds:
          creative:
            coolplugin.item: true
        inheritance:
        - default
    messages:
      build: '&cYou do not have permission to build here.'
    debug: false
    
     
  12. Offline

    budpup67

    Works again ty. any way to make people join a group automaticly? and does MChat make the chat turn colorfull?
     
  13. Offline

    Tallsword

    I am trying to use a plugin named "Heroes", but I am running into an error, at the plugin's forum I was told that the problem's with my permissions... I tried every single thing I found (searched with google for a lot of hours in the last 2 days), but cant get it to work. :(
    I am just too 'new' to bukkit to run this perfectly, help me plz.

    Code:
    users:
      Tallsword:
        groups:
        - admin
      ConspiracyWizard:
        permissions:
          permissions.example: true
        groups:
        - admin
      thelivestrong:
        groups:
        - user
      jawzx:
        groups:
        - user
      garahof:
        groups:
        - user
    groups:
      default:
        permissions:
          permissions.build: false
      admin:
        permissions:
          permissions.*: true
          worldedit.*: 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
    This is my config when after I deleted all the permissions what did not work...

    Thanks for your help and patience and sorry for takeing your time... :(

    Edit: The error is that the players when they wanna choose a 'profession' they get a messenge: "You dont have permission for [profession's name]" and they cant see the classes...
     
  14. Offline

    Disparate

    Snowy007
    After an IMMENSE amount of tooling around, I have now managed to get it working BUT it is far from completely working.

    The group functionality of this plugin is more or less broken as it cannot handle queries regarding groups (for plugins like falsebook that rely on this) and it is constantly reformatting itself and deleting lines. This morning, when I launched it on my live server, everything was fine then an op pointed out I had forgotten to add the node to allow OPs to GOD themselves (commandbook.god). I added this and all was well until we noticed that their ability to god other players had gone (commandbook.god.other) . I re-added this (it was there earlier) and reloaded the perms. PermisisonsBukkit then instantly removed the node for god! You can have one or the other but not both. It is doing this in other places too with other plugins.

    The issue with groups is paramount though as this was one of the main purposes of this god forsaken heap of a plugin, to allow group queries.

    Essentially, it is just about functional but far, far , FAR from fully functional or competently written and the ludicrous, laughable fits it has when you stray one micron outside of its formatting parameters are just insane.

    A better alternative is very badly needed.
     
  15. Offline

    DarkByte7

    Have you tried giving them the permission to run the command? That would be a start. Your permissions file looks correctly setup I don't see any errors.
     
  16. Offline

    viXy

    When I'am trying to use /permissions player addgroup , I get this error:

    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.createPlayerNode(PermissionsCommand.java:400)
    at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(PermissionsCommand.java:301)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:152)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 12 more

    Plugins on my server:
    Towny, VanishNoPacket, iConomy

    Sorry for my bad english.

    My config.yml:

    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin 
    groups:
        guest:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - mod
        mod:
            permissions:
                permissions.*: true
                towny.chat.mod: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                towny.town.*: true
                towny.chat.general: true
                towny.chat.town: true
                towny.chat.local: true
                towny.wild.*: true
                towny.nation.*: false
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - guest
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: false
     
  17. Offline

    Snowy007

    hmm.. getting 'bad gateway' errors when clicking 'reply'.... anyway...

    Disparate
    Might be a problem with indention or some structure problem perhaps.. Have you tried running it through a YAML parser?

    budpup67
    People will automatically join the group that is called 'default'.
    MChat... i don't know i don't use it. But it sounds like a chat plugin and most chat plugins allow to change colors.

    Can't edit posts either right now... the same 'bad gateway' error.

    viXy
    You have an empty line at the bottom of your config. This should be better:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        guest:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - mod
        mod:
            permissions:
                permissions.*: true
                towny.chat.mod: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                towny.town.*: true
                towny.chat.general: true
                towny.chat.town: true
                towny.chat.local: true
                towny.wild.*: true
                towny.nation.*: false
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - guest
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  18. Offline

    RyGuy147

    How do I make it so new users are added to the "users" permission group?
     
  19. Offline

    Snowy007


    You don't. New users are always automatically added to the group that is named 'default'.
    If you wan't your your users to start in a different group, then just name that group 'default'.
     
  20. Offline

    {AuGs}Reaper

    Hello,
    I installed Permissionsbukkit and set up my config.yml file and every time I use this command
    /permissions player addgroup <playername> <group>
    to set a player into a group and I get this error

    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.createPlayerNode(PermissionsCommand.java:400)
    at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(PermissionsCommand.java:301)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:152)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 12 more

    This is how I have my config set.

    Code:
    groups:
        default:
            permissions:
                permissions.build: true
                ultimatearena.player: true
                towny.claimed.build: true
                towny.claimed.alltown.block.*: true
                iConomy.list: true
                iConomy.payment: true
                iConomy.rank: true
                ChestShop.shop.buy: true
                ChestShop.shop.sell: true
        admin:
            permissions:
                worldedit.*: true
                iConomy.access: true
                ChestShop.admin : true
            inheritance:
            - mod
        mod:
            permissions:
                spectate.use: true
                towny.admin: true
                ultimatearena.admin: true
                Punishment.*: true
                worldguard.*: true
                iConomy.admin.*: true
                iConomy.bank.*: true
            inheritance:
            - member
        member:
            permissions:
                permissions.build: true
                essentials.setspawn: true
                essentials.spawn: true
                essentials.tempban.exempt: true
                essentials.kick.exempt: true
                essentials.ban.exempt: true
                essentials.mute.exempt: true
                essentials.ban: true
                essentials.ban.notify: true
                essentials.ban.offline: true
                essentials.banip: true
                essentials.kick: true
                essentials.kick.notify: true
                essentials.kill: true
                essentials.mute: true
                essentials.tempban: true
                essentials.tempban.offline: true
                essentials.unban: true
                essentials.unbanip: true
            inheritance:
            - helper   
        helper:
            permissions:
                permissions.build: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.me: true
                essentials.msg: true
                essentials.tp: true
                essentials.essentials: true
                ChestShop.shop.create: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
    If someone can help me, that would be great!
     
  21. Offline

    Tacotime47

    Uh for some reason it says
    16:18:15 [WARNING] Permissions not found! All Operations are allowed!
    and i dont want that
     
  22. Offline

    ImagineCraft

    I use the code below to allow people who join my server (just a little 24/7 server for friends) to teleport. I don't want to make them al OP because it would go to a mess, but i will allow a little lazyness to let them teleport.
    So what i did, is add to the default group, bukkit.command.teleport: true.
    now when i reload the config file via the "/perms reload" command, it says its correctly reloaded, but i don't see any commands added to the default group.
    What am i doing wrong? How to make this work? Because when i ask with the right command in which group i am it says they putted me in the default group so i should have the teleport command right?


    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: true
                bukkit.command.teleport: true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: false
    Can somebody help me with this?
    Teoctist
     
  23. Offline

    Snowy007

    Remove the empty line at the bottom between 'build:' and 'debug:'
     
  24. Offline

    Riolu

    Excuse me, but how can I set any group to default?
     
  25. Offline

    Snowy007

    Just rename the group you want to be default as 'default' (And obviously make sure there is only 1 group named 'default')
    It really doesn't matter as you won't see the group name in-game anyway.
     
  26. Offline

    Riolu

    Isn't worked for me. I guess it because of this:
    When I type "perm group list" in console I got this

    >perm group list
    21:17:14 [WARNING] Unexpected exception while parsing console command
    org.bukkit.command.CommandException: Unhandled exception executing command 'perm
    ' in plugin PermissionsBukkit v1.6
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:16
    6)
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:4
    73)
    at org.bukkit.craftbukkit.CraftServer.dispatchServerCommand(CraftServer.
    java:469)
    at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:596)
    at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:565)
    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(Perm
    issionsCommand.java:167)
    at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(Permiss
    ionsCommand.java:146)
    at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
    ... 7 more
    >
     
  27. I think this plugin needs updating because the last update was nearly 2 months ago and loads of people keep getting reoccurring problems, including me. Anyone here got any ideas? I for one would hate to have to use a different plugin because they suck frankly...
     
  28. Offline

    Snowy007

    There is probably a mistake somewhere in the config. Even the smallest mistake can be a big problem for this plugin to function correctly. You can try posting it here. (or pm it if you don't want it public) And i can take a look at it if you can't find anything yourself.


    The plugin works fine IF the config is correct. And believe me.. 2 months is nothing. Before 1.2 he didn't update it for like 6 months or something. Then when it broke with 1.2 he updated it in just a few days. And as long as it is still working correctly he probably won't update it again. If it works, it works. He just isn't adding any new features and is just keeping it working.
    The problem with this plugin isn't really a problem if you do everything right. Its just really strict on how your config looks like. There should be 0 mistakes or it will give errors and perhaps delete the entire config. As you can see when you look back through a few pages, i was able to help pretty much everyone to get it working perfectly just by changing some minor mistakes in their configs.
     
  29. Offline

    Riolu

    Yes, I think you right. But you better to check this out.
    HTML:
    users:
        Riosha:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            permissions:
                permissions.build: true
            inheritance:
            - visitor
        admin:
            permissions:
                permissions.*: true
    messages:
        build: '&cYou not avalible to build.'
    Look also http://s019.radikal.ru/i602/1204/ee/f5986edad0da.png
    There is all red! :(
     

    Attached Files:

  30. Offline

    Snowy007

    yes, red is never good. :p
    It means that you are using tabs instead of spaces. Just remove all the tabs and use spaces to indent everything. (1 tab = 4 spaces)
    Also you seem to be missing a 'debug:' node at the bottom.. Don't think that is such a problem though.

    Code:
    users:
        Riosha:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            permissions:
                permissions.build: true
            inheritance:
            - visitor
        admin:
            permissions:
                permissions.*: true
    messages:
        build: '&cYou not avalible to build.'
    debug: false
     
  31. Offline

    Riolu

    Ah, I tough so! :D
    But guy in video tutorial said, that I have to use tab. Okay, thanks for help.
     

Share This Page