[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

    kyle939

    Someone help me with the plugin?

    Here are my settings which I need help with

    Code:
    users:
        kyle939:
            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.'
    That is all working fine okay.

    Now how do I add friends into the plugin, only allowing them to build and destroy. Do the usual Minecraft stuff, but not use the Admin commands?

    I've removed my name from the Admin, and I try to build or destroy and it says you do not have permissions..... and doesn't work.

    Need help.
     
  3. Offline

    Jobi

    Code:
    users:
        1:
            permissions:
            groups:
            - admin
        2:
            permissions:
            groups:
            - admin
        3:
            permissions:
            groups:
            - admin
        4:
            permissions:
            groups:
            - admin
        5:
            permissions:
            groups:
            - user
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                bukkit.command.ban: true
                bukkit.command.unban: true
                bukkit.command.save.*: true
                bukkit.command.save: true
                bukkit.command.tell: true
                bukkit.command.say: true
                bukkit.command.reload: true
                bukkit.command.kill:true
                bukkit.command.help:true
                bukkit.command.list:true
                bukkit.command.stop:true
                bukkit.command.kick:true
                bukkit.command.teleport:true
                iconomy.*: true
                chestshop.*: true
                commandSigns.*: true
                essentials.ptime.others: true
                essentials.seen: true
                essentials.jump: true
                worldguard.*
                worldedit.*
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                ChestShop.shop.*: true
                iConomy.accounts.create: true
                iConomy.accounts.give: true
                iConomy.accounts.take: true
                iConomy.help: true
                iConomy.holdings: true
                iConomy.payment: true
                commandSigns.create: true
                commandSigns.use: true
                essentials.afk: true
                essentials.getpos: true
                essentials.mail.*: true
                bukkit.command.list:true
                essentials.ignore: true
                essentials.msg: true
                essentials.home: true
                essentials.sethome: true
                essentials.warp.*: true
                essentials.setwarp: true
            inheritance:
            - default
    messages:
        build: '&cDu darfst hier leider nicht bauen!.'
    
    (yes, 1, 2, 3... are names)

    Why i don't have any permissions? (my name is 1) Did i something wrong? Please help.
     
  4. Offline

    Scadey

    can someone please tell me what the problem with my config file here is?

    Code:
    users:
        Scadey:
            groups:
            - Arch-Duke
        Mr_Punter:
            groups:
            - Arch-Duke
        Mr_Oulds:
            groups:
            - Duke
        Kieran1236:
            groups:
            - Duke
        Furyheritage:
            groups:
            - Duke
        xoclaraox:
            groups:
            - Lady
        CptMadge:
            groups:
            - Lord
        Condor95:
            groups:
            - Citizen
    
    groups:
        Citizen:
            permissions:
                permissions.build
                essentials.help
                essentials.rules
                essentials.who
                essentials.back
                essentials.back.ondeath
                essentials.sethome
                essentials.home
                essentials.tpa
                essentials.tpahere
                essentials.tpaccept
                essentials.tpdeny
                essentials.me
                essentials.msg
                essentials.mail
                essentials.mail.send
                essentials.spawn
                essentials.me
                essentials.suicide
                lockette.user.create.*
        Lord:
            permissions:
                permissions.build
                essentials.tp: true
                essentials.tphere: true
                essentials.warp: true
                essentials.warp.list: true
                essentials.home.others: true
                essentials.nick: true
                essentials.kick: true
                essentials.depth: true
            inheritance:
            - Citizen
        Lady:
            permissions:
            permissions.build
            inheritance:
            - Lord
        Duke:
            permissions:
                permissions.build
                essentials.ban: true
                essentials.item: true
                lockette.admin.create.*: true
                lockette.admin.snoop: true
                lockette.admin.bypass: true
                superpermbridge.worldedit.*: true
            inheritance:
            - Lord
        Arch-Duke:
            permissions:
                permissions.*:true
                superpermbridge.*:true
            inheritance:
            - Duke
    
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  5. Parse your YML file contents online here: http://yaml-online-parser.appspot.com/
    By doing so you will notice that it spews errors. There should always be a Space(" ") between the ':' and the 'true'.
    Second there are no wildcards '*' if they are not defined within the plugin. IIRC WorldEdit would need superpermsbridge to access this node: superpermsbridge.worldedit.*: true
     
  6. Offline

    Shubawks

    First time being an owner of a server, I'm sure you were new at some point.

    Note to self; Never join a server of an incredible douche bag that thinks he's king of the world because he knows how "inheritance" works. Seriously, screw you.

    @krinsdeath: Thank you very much!
     
  7. Offline

    halfer

    Hi there. In my log I have a lot of these messages:
    Code:
    at com.platymuus.bukkit.permissions.PermissionsPlugin.calculateGroupPerm
    issions(PermissionsPlugin.java:241)
    Nobody on the server seems to complain, but the problem is still there. I checked my YML here, and it seems fine.
     
  8. Offline

    RustyDagger

    Sorry I wasted my time explaining it to the newb. i could of worded the start of it better i guess but whats done is done.
     
  9. Offline

    Celtic Minstrel

    @Jack_Miller – That config you posted should be in the plugins/PermissionsBukkit folder and should be called config.yml. It should not be in the server folder and called permissions.yml.

    @Jobi – Using numbers as keys causes problems. You need to quote them to force them to be a string, eg:
    Code:
    users:
        '1':
            permissions:
     
  10. Offline

    Flinta

    .* = all. Dont work for me.

    bukkit.command.gamemode: true <--- work
    bukkit.command.*: true <--- dont work
    bukkit.*: true <--- dont work

    help?
     
  11. Offline

    Celtic Minstrel

    Drop the .*; the bukkit permissions don't use it. bukkit.command has the effect that you are expecting from bukkit.command.*
     
  12. Offline

    Flinta

    well that might work

    but not these?

    worldedit.*: true
    or
    worldedit: true

    ?!
     
  13. Offline

    3x3mpt

    My permissionsbukkit isn't letting CFbanner see that there is a default class. Does anyone know a fix?
     
  14. Offline

    Axiol

    Hum... This is my config.yml, juste changed my nickname ans remove the permission's exemple ans it doesn't work, I can't do any admin command :/ Any idea ?

    Code:
    users:
        Axiol:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            inheritance:
            - default
    messages:
        build: 'Vous ne pouvez pas construire ici.'
    Nice, thank you :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  15. Offline

    ZNickel

    hey i've got this plugin called wormholextreme it's a multi-dialing, multi-world portal plugin which i've been using even though it's outofdate. It only works with permissions 2.7 or later. I'm just wondering how to get it to recognise this plugin for permissions
     
  16. Offline

    srmorris2

    Is there anyone that would mind helping me migrate my 3.1.4 permissions to this plugin? I tried and practically broke everything. I would love if you could PM me or email me if you wouldn't mind helping.

    admin@redhallow.com
     
  17. Offline

    Ben1853

    Hi, I'm having problems trying to use this plugin... I have iConomy and im just trying to get that to work but it seems to only work for admins, probably cause our names are in the OP.txt. Here's my config:
    Code:
    groups:
        default:
            permissions:
                iConomy.help: true
                iConomy.holdings: true
                iConomy.holdings.others: true
                iConomy.payment: true
                permissions.build: 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.'
    I've tried other plugins other than iConomy and nothing seems to work. The players can't even access /help. The only thing that works is building. Any suggestions?

    Also, I'm fairly new, so please excuse my noobness :p
     
  18. Offline

    Flinta


    do

    admin:
    permissions:
    bukkit.command: true
    inheritance:
    - user
     
  19. Offline

    Jobi

    Ok, i changed some things:
    Code:
    users:
        a:
            permissions:
            groups:
            - admin
        b:
            permissions:
            groups:
            - admin
        c:
            permissions:
            groups:
            - admin
        d:
            permissions:
            groups:
            - admin
        e:
            permissions:
            groups:
            - user
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                bukkit.command.ban: true
                bukkit.command.unban: true
                bukkit.command.save.*: true
                bukkit.command.save: true
                bukkit.command.tell: true
                bukkit.command.say: true
                bukkit.command.reload: true
                bukkit.command.kill: true
                bukkit.command.help: true
                bukkit.command.list: true
                bukkit.command.stop: true
                bukkit.command.kick: true
                bukkit.command.teleport: true
                superpermsbridge.iconomy.*: true
                superpermsbridge.chestshop.*: true
                superpermsbridge.commandSigns.*: true
                essentials.ptime.others: true
                essentials.seen: true
                essentials.jump: true
                superpermsbridge.worldguard.*
                superpermsbridge.worldedit.*
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                superpermsbridge.ChestShop.shop.*: true
                iConomy.accounts.create: true
                iConomy.accounts.give: true
                iConomy.accounts.take: true
                iConomy.help: true
                iConomy.holdings: true
                iConomy.payment: true
                commandSigns.create: true
                commandSigns.use: true
                essentials.afk: true
                essentials.getpos: true
                superpermsbridge.essentials.mail.*: true
                bukkit.command.list: true
                essentials.ignore: true
                essentials.msg: true
                essentials.home: true
                essentials.sethome: true
                essentials.warp.*: true
                essentials.setwarp: true
            inheritance:
            - default
    messages:
        build: '&cDu darfst hier leider nicht bauen!.'
    
    could this work? (i've installed SuperpermsBridge)
     
  20. Offline

    kyle939

    I had this problem.

    What I noticed and what I did is placed my name in the ops file which is in the same location as the server. It's just called "ops" and just put you're name in there, save and try again.

    Worked for me!
     
  21. Offline

    krinsdeath

    @Celtic Minstrel - Thanks, man. It's so hard to keep up ;_;

    @Axiol - The node permissions.* only applies to PermissionsBukkit's commands. If you want to be able to use your other plugins' commands, you need to add their permissions nodes to your config.yml.

    @3x3mpt - I recall CainFoool asking about implementing PermissionsBukkit groups on IRC one day. I don't know the specifics of his plugins, but I'm sure you could request information about setting it up in one of his threads.

    @Flinta - In order to figure out which plugins use which nodes, you should refer to their documentation. However, for WorldEdit, you need the latest dev version (4.7+, I believe) in order to access Superperms. Once you have that, you should be able to use nodes like worldedit.*: true normally.

    @halfer - I need the entire stack trace (the start being "An exception occurred at...") in order to figure out the problem. After a brief glance at the source code, however, I believe you should update your PermissionsBukkit to the latest (build 1.2k, here).

    @Lathanael - Thanks for the help!

    @kyle939 - Try moving a decent distance away from your spawn area. Bukkit provides a simple internal protection system in a radius of 16 blocks around your spawn point, wherein you cannot destroy or break blocks. You can disable this protection by changing the value in bukkit.yml (in your server root) to 0.

    @beatcomet - Simply set the permissions to a group (nodes are case-insensitive, since bukkit runs string.toLowerCase() on all permissions strings) and test them by doing the action that you've set as a requirement (either a command, some event, or what-have-you). Follow the format set by the main post in this thread, and you'll be fine.
     
  22. Offline

    thedog

    Is this 1185 now and if so where is download thingy
     
  23. Offline

    Celtic Minstrel

    Whether you use a * depends on the plugin. I think WorldEdit does use a *; Bukkit doesn't.
     
  24. Offline

    Superzilla

    Ok, I'm trying to install falsebook for my clan's server, I'm pretty sure I have everything set up right and I don't know why it wont work. I tried using SuperPermsBridge on the permissions but I can't use it still. Can anyone help, or should I post this on the falsebook thread? Other plugins work right though. Ugh... and 1 more question. someone in the server has a . in their name and i would like some help on adding them to the player list 'cause it won't work when I do it normally. I can post the config file and the file with the permissions listed later.

    soz, I think I need another post so I can watch this tread.

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

    Jack_Miller

    Yeah :D thank you, workz

    No No No, it workz now ^^

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

    Sir Markus

    Is there a way i can prefend people from adding people to a given group?
    like: "Mods" not beeing able to add people to group "Admin", but the can add people to group "Builders"
     
  27. Offline

    tony687

    ummm heres my updated config.yml:
    Code:
    users:
        tony687:
            permissions:
                permissions.example: true
            groups:
            - Owner
        gravel625:
            groups:
            - Admin
        jayden687:
            groups:
            - EliteBuilder
        ezio687:
            groups:
            - VIP
        Tysonhe0:
            groups:
            - EliteBuilder
        Brian687:
            groups:
            - AdvBuilder
        jackinator99:
            groups:
            - Builder
        Justin:
            groups:
            - Builder
        beckasith:
            groups:
            - Builder
        nickshak:
            groups:
            - AdvBuilder
        zombiekill007
            groups:
            - Builder
        BlackAllis:
            groups:
            - VIP
    groups:
        default:
            permissions:
                permissions.build: true
                essentials.help: true
                essentials.home: true
                essentials.motd: true
                essentials.rules: true
                essentials.sethome: true
                essentials.warp: true
                essentials.spawn: true
                essentials.afk: true
                essentials.list: true
                worldwarp.wwarp: true
                worldwarp.wlist: true
                xauth.register: true
                iConomy.*: true
                iConomy.admin: false
                ChestShop.shop.*: true
                armageddon.*: false
                essentials.tp: true
                essentials.tpa: true
                essentials.tpaccept: true
                lwc.protect: true
                multiverse.portal.access.*: true
                mchat.prefix.Guest: true
                mchat.suffix.Guest: true
        Builder
            permissions:
                essentials.compass: true
                mchat.prefix.Guest: false
                mchat.prefix.Builder: true
                mchat.suffix.Guest: false
                mchat.suffix.Builder:true
            inheritance:
            - default
        AdvBuilder
            permissions:
                colorme.*: true
                mothernature.command.*: true
                mothernature.day: true
                mchat.prefix.Builder: false
                mchat.prefix.AdvBuilder: true
                mchat.suffix.Builder: false
                mchat.suffix.AdvBuilder: true
    
            inheritance:
            - Builder
        EliteBuilder
            permissions:
                instabreak.toggle: true
                mchat.prefix.AdvBuilder: false
                mchat.prefix.EliteBuilder: true
                mchat.suffix.AdvBuilder: false
                mchat.suffix.EliteBuilder: true
            inheritance:
            - AdvBuilder
        Mod
            permissions:
                essentials.item: true
                essentials.time.world: true
                essentials.weather: true
                instabreak.force: true
                magiccarpet.*: true
                mchat.prefix.EliteBuilder: false
                mchat.prefix.Mod: true
                mchat.suffix.EliteBuilder: false
                mchat.suffix.Mod: true
            inheritance:
            - EliteBuilder
        AdvMod
            permissions:
                essentials.invsee: true
                essentials.unlimited.*: true
                instabreak.bedrock: true
                worldedit.*: true
                mothernature.wand: true
                mothernature.lwand: true
                mchat.prefix.Mod: false
                mchat.prefix.AdvMod: true
                mchat.suffix.Mod: false
                mchat.suffix.AdvMod: true
            inheritance:
            - Mod
        Guard
            permissions:
                essentials.god: true
                essentials.god.others: true
                essentials.give: true
                slap.slap: true
                essentials.kill: true
                mchat.prefix.AdvMod: false
                mchat.prefix.Guard: true
                mchat.suffix.AdvMod: false
                mchat.suffix.Guard: true
            inheritance:
            - AdvMod
        SemiAdmin:
            permissions:
                essentials.heal: true
                essentials.spawnmob: true
                essentials.clearinventory: true
                essentials.broadcast: true
                worldwarp.wcreate: true
                mchat.prefix.Guard: false
                mchat.prefix.SemiAdmin: true
                mchat.suffix.Guard: false
                mchat.suffix.SemiAdmin: true
            inheritance:
            - Guard
        VIP
            permissions:
                mchat.prefix.SemiAdmin: false
                mchat.prefix.VIP: true
                mchat.suffix.SemiAdmin: false
                mchat.suffix.VIP: true
            inheritance:
            - SemiAdmin
        Admin:
            permissions:
                permissions.*: true
                mchat.prefix.Owner: false
                mchat.prefix.Admin: true
                mchat.suffix.Owner: false
                mchat.suffix.Admin: true
            inheritance:
            - Owner
        Owner:
            permissions:
                permissions.build: true
                permissions.*: true
                essentials.*: true
                slap.*: true
                worldwarp.*: true
                instabreak.*: true
                magiccarpet.*: true
                mothernature.*: true
                colorme.*: true
                economy.*: true
                lwc.*: true
                armageddon.*: false
                ChestShop.*: true
                xauth.*: true
                worldedit.*: true
                multiverse.*: true
                mchat.prefix.Owner: true
                mchat.suffix.Owner: true
            worlds:
    messages:
        build: '&cYou do not have permission to build here.'
    
    And, this is what i get in the console. Help?
    Code:
    10:57:26 [SEVERE] Could not load 'plugins/PermissionsBukkit-1.2.jar' in folder 'plugins':
    while scanning a simple key
     in "<reader>", line 63, column 5:
            zombiekill007
            ^
    could not found expected ':'
     in "<reader>", line 64, column 15:
                groups:
                      ^
    
    	at org.yaml.snakeyaml.scanner.ScannerImpl.stalePossibleSimpleKeys(ScannerImpl.java:400)
    	at org.yaml.snakeyaml.scanner.ScannerImpl.needMoreTokens(ScannerImpl.java:231)
    	at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:182)
    	at org.yaml.snakeyaml.parser.ParserImpl$ParseIndentlessSequenceEntry.produce(ParserImpl.java:536)
    	at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:163)
    	at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:148)
    	at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:203)
    	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:158)
    	at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
    	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    	at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
    	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    	at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
    	at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
    	at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
    	at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
    	at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:124)
    	at org.yaml.snakeyaml.Yaml.load(Yaml.java:264)
    	at org.bukkit.util.config.Configuration.load(Configuration.java:82)
    	at org.bukkit.plugin.java.JavaPlugin.initialize(JavaPlugin.java:157)
    	at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:175)
    	at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:213)
    	at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:136)
    	at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:138)
    	at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:103)
    	at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:52)
    	at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:136)
    	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:348)
    	at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
     
  28. Offline

    shtoobs

    I'm new to this, and how do I make it so everything I hit doesn't regenerate?
     
  29. Offline

    Armaxxx

    Can you make this work with craftbukkituptodate!? both permissions and superperms bridge please
     
  30. Offline

    tony687

    i think u need the 'permissions.build: true' node
     
  31. Offline

    Celtic Minstrel

    Nope, there's a Watch/Unwatch thread link at the top.

    I suspect there's nothing you can do about the guy with a . in his name. I don't think it's possible to make that work at the moment.

    @Sir Markus – Sorry, not currently possible.

    @tony687 – That error message tells you exactly what's wrong: a missing colon on line 63.
     

Share This Page