[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

    Machete.Panda

    how do I set the default group? We are going to run a promotion on our server for donor status anyone joining for the week will get donor status. But I cant find how to set 'donor' as the default premission group when people join?

    I tried adding -donor to defaults dependencies, but it seems to make a loop and donors and everyone loose their power.
     
  3. Offline

    Abe27342

    Hello, I'm getting this error (probably silly) upon updating to bukkit 1185.

    Code:
    15:12:37 [SEVERE] Could not pass event PLAYER_JOIN to PermissionsBukkit
    java.lang.ClassCastException: java.lang.Double cannot be cast to java.lang.String
        at com.platymuus.bukkit.permissions.PermissionsPlugin.getNode(PermissionsPlugin.java:215)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.getNode(PermissionsPlugin.java:200)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.getNode(PermissionsPlugin.java:185)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.calculateGroupPermissions(PermissionsPlugin.java:280)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.calculatePlayerPermissions(PermissionsPlugin.java:263)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.calculateAttachment(PermissionsPlugin.java:237)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.setLastWorld(PermissionsPlugin.java:168)
        at com.platymuus.bukkit.permissions.PermissionsPlugin.registerPlayer(PermissionsPlugin.java:146)
        at com.platymuus.bukkit.permissions.PlayerListener.onPlayerJoin(PlayerListener.java:22)
        at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:244)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
        at net.minecraft.server.ServerConfigurationManager.c(ServerConfigurationManager.java:126)
        at net.minecraft.server.NetLoginHandler.b(NetLoginHandler.java:116)
        at net.minecraft.server.NetLoginHandler.a(NetLoginHandler.java:34)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:94)
        at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:464)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
    
    Nevermind, fixed it. Silly me, put a period in my world's name :p

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

    marshystomp

    I love this! But the horrible thing is... I have a server and use this but there arent many plugins that can work with this, it always defaults to OP or something! Anyway I can still make it work, like i had magic carpet and it didnt default to OP since it couldnt find Permissions it let everyone use it! Then everyone was flying on my server! I need a way to fix this!
     
  5. Offline

    Lama_0

    Hey, I got the 'CraftBukkitUpToDate' plugin so it can update plugins automatically, but it says it needs you to add the plugin at dev.bukkit.org... You think you can do this?
     
  6. Offline

    madhatterzz

    any one know when there relasing permission bukkit for 1185? as my server is messed up without it , im having to make beta testing players a op :(
     
  7. Offline

    Scadey

    on my log, everything seems to be fine, but in the parser for some reason a few permissions nodes aren't showing up as taking a new line, and everything seems to default to op, i really don't know whats going wrong, need some help as i've been at this for days now. config below.
    users:
    Scadey:
    groups:
    - Arch-Duke
    Mr_Punter:
    groups:
    - Citizen
    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:
    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:
    inheritance:
    - Lord
    Duke:
    permissions:
    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
     
  8. Offline

    Shelgeyr

    I'm running a neighborhood server for a few friends, with this mod and Stargate.
    In the server properties file, I set the zone protection radius to zero in order to allow people to fully interact with stuff I set up on the spawn point for them. This worked fine when the server was fully "vanilla" (stock server, not CraftBukkit) but for some reason, nobody can destroy or place blocks in the spawn area unless I op them.

    Any thoughts?

    Never mind, I just did what I should have done in the first place.
    Tested with no plugins - still can't build on spawn point without op.
    Apparently, it's a problem with the Bukkit.
     
  9. Offline

    madhatterzz

    permissions is broken , wait for permission bukkit to be updated , the reason it works for ops and admins is because there defult and for your citizen , its custom
     
  10. Offline

    Scadey

    so how can i make my citizen rank the default?,
     
  11. Offline

    Kronos34

    Any update soon?
     
  12. Offline

    ItsHarry

    Okay so I'm really confused now, I read the FAQ, edited my code but it's acting weird. Does anyone have a good tutorial on how to enable permissions for my plugin?
     
  13. Offline

    ZerothAngel

    That's a feature of vanilla, isn't it?

    Edit bukkit.yml and set the spawn-radius to 0. That should turn off spawn protection.

    If you then want to limit who can build at your spawn point, you'll have to use something like WorldGuard (with the dev version of WorldEdit, which supports Bukkit permissions natively). Add your admin group as a member or owner of the spawn region and set up the group permission appropriately. (If your admin group is named "admin", give them the "group.admin" node.)
     
  14. Is it possible to do "superpermbridge.dbstudios.dayjobs.player: true" or something similar? Because I can't seem to get anything other than "superpermbridge.dbstudios" and "superpermbridge.*" working with a plugin I am using.
     
  15. Offline

    Shelgeyr

    Thanks tons! I didn't know that Bukkit was creating it's own version of the properties file. This completely solved my "problem" :)
     
  16. Offline

    Machete.Panda

    Love your plugin.

    First Question:
    How do I set the default group? We are going to run a promotion on our server for donor status anyone joining for the week will get donor status. But I cant find how to set 'donor' as the default premission group when people join?

    I tried adding -donor to defaults dependencies, but it seems to make a loop and donors and everyone loose their power.

    Second Question:
    When will this be updated for build #1185?

    Thank you.
     
  17. Code:
        Moderator:
            permissions:
                permissions.build: true
                chaircraft.sit: true
                permissions.player.setgroup: default,Member
                permissions.player.groups: true
    Is that going to work or how do i restrict what group a Moderator can set to a player?
     
  18. If thats what it's called then yes :)

    Is it available right now or do i need to request it?

    @Machete.Panda It already works with 1185!
     
  19. Offline

    Machete.Panda

    oh... sorry. The thread title currently list its up to 1000. :p I guess I can upgrade then.
     
  20. Offline

    madhatterzz

    UPDATE PERMISSION BUKKIT PLEASE
     
  21. Offline

    beatcomet

    I made a plugin using the following permissions :

    GMC.use
    and
    GMC.create
    but I don't know how to set up the server permissions (the permissions.yml file).
    can you help please?
     
  22. Offline

    godsyn

    That is not currently implemented.
     
  23. Offline

    Jack_Miller

    WTF, what is now...is it broken or not?


    I have a problem with ma permissions.yml.

    U see...the default Group can't Build...thats ok, it works...but when i add me in the user group...i can't Build, too... Help me pls :(



    Code:
    users:
        jack_miller:
            groups:
            - default
            - user
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    debug: false
     
  24. Offline

    ZerothAngel

    Try removing yourself from "default".
     
  25. Offline

    Shubawks

    Is it possible to do something like this...

    Code:
    users:
        RedReapa:
            groups:
            - admin
    groups:
        Founder:
            permissions:
                permissions.build: true
                permissions.help: true
                permissions.reload: true
                permissions.check: true
                permissions.info: true
                permissions.dump: true
                permissions.group.*: true
                permissions.player.*: true
                creativemode: true
        Admin:
            permissions:
                permissions.build: true
                permissions.group.*: true
                permissions.player.*: true
                creativemode: true
        Mod:
            permissions:
                permissions.build: true
                permissions.player: true
                creativemode: true
        Member:
            permissions:
                permissions.build: true
                creativemode: true
        Guest:
            permissions:
                permissions.build: false
                creativemode: false
    messages:
        build: '&cYou do not have permission to build here.'
    I understand that you wouldn't use the the node "creativemode" - but; is there a way that when someone joins the server, they do not have creative mode? Also - how do I make the "guest" node the default node for new users that join the server?

    Thanks,
    Shubawks
     
  26. Offline

    RustyDagger

    note to self never join your server because if you don't understand how to use inheritance you cant be that good of a server owner srsly inheritance means you don't need to give admins every node that user has + some more it carrys it over. so if admin inherited user it would get all of users permissions + what ever you give admin would reduce your file size by 50% false always over rides true also....
     
  27. Offline

    tony687

    is this config file ok?
    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:
        Guest:
            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
        Builder
            permissions:
                essentials.compass: true
            inheritance:
            - Guest
        AdvBuilder
            permissions:
                colorme.*: true
                mothernature.command.*: true
                mothernature.day: true
            inheritance:
            - Builder
        EliteBuilder
            permissions:
                instabreak.toggle: true
            inheritance:
            - AdvBuilder
        Mod
            permissions:
                essentials.item: true
                essentials.time.world: true
                essentials.weather: true
                instabreak.force: true
                magiccarpet.*: true
            inheritance:
            - EliteBuilder
        AdvMod
            permissions:
                essentials.invsee: true
                essentials.unlimited.*: true
                instabreak.bedrock: true
                worldedit.*: true
                mothernature.wand: true
                mothernature.lwand: true
            inheritance:
            - Mod
        Guard
            permissions:
                essentials.god: true
                essentials.god.others: true
                essentials.give: true
                slap.slap: true
                essentials.kill: true
            inheritance:
            - AdvMod
        SemiAdmin:
            permissions:
                essentials.heal: true
                essentials.spawnmob: true
                essentials.clearinventory: true
                essentials.broadcast: true
                worldwarp.wcreate: true
            inheritance:
            - Guard
        VIP
            inheritance:
            - SemiAdmin
        Admin:
            permissions:
                permissions.*: 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
            worlds:
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  28. Offline

    krinsdeath

    @tony687 - The only problem is that you've excluded the 'default' group. Change 'Guest' to 'default' and your configuration file will work fine.

    @Shubawks - Another plugin may offer that functionality, but this one does not.

    @RustyDagger - Please refrain from character attacks. Everyone has their own way of doing things.

    @beatcomet - I'm not sure what you're requesting. permissions.yml is Bukkit's internal parent->child node handler. It is not inherently a part of this plugin.

    @madhatterz - What.

    @Silverlink - What exactly are you requesting, functionality wise? There are a lot of replies and I'm really busy, so digging through the topic for single posts is difficult and time-consuming.


    @all people ever - Please, please use the Ticket Tracker on the BukkitDev page. It makes it much easier for Space and I to coordinate our time spent fixing the problems.
     
  29. Offline

    tony687

    thanks,
    but how can i make it like called Guest rank, but still default?
    And also, how can i have coloured names and prefixes?
     
  30. Offline

    Monkey_nuts

    What type of permissions is everyone using for all the plugins now?
    - PermissionsBukkit?
    - PermissionsEx?
     
  31. Offline

    beatcomet

    no, I want to test my plugin's permissions (I set it using the example in the first page) but I can't test it since I don't know how to use this plugin (I want to test it on my server)
     

Share This Page