[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


    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.

    • 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.

    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:
                permissions.example: true
            - admin
                permissions.build: false
                permissions.*: true
            - user
                permissions.build: true
                    coolplugin.item: true
            - default
        build: '&cYou do not have permission to build here.'

    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:
            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:
        description: Basic permissions for My Cool Server.
        default: true
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
        description: Admin permissions for My Cool Server.
        default: op
            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:
    da-name-format: '+prefix+name&e'
    date-format: HH:mm:ss
    message-format: '+prefix+name&f: +message'
            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.

    Current Version:

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



    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


    @md_5 @daredevilk Oh, I see.

    You can't promote people directly within PB, but a extra plugin like SetRankPB should be able to do it.

    It contains a /promotion command
    /promotion [Option] <Arguments>
  3. Offline


    He is talking about direct promotion, like I said.
  4. Offline


    Yeah, and a promotion that could only be used on their self.
    I have a server that's We're Alive based and I'm trying to figure out a way to make it so that when people first join they can pick a side they want to be on (Tower people, Maller or a Stranded) and I was thinking Promotion but I don't want people to be able to set group on other people.
  5. Offline


    @daredevilk plugins can do this, try SignRank. It allows them to choose a rank through clicking a sign made by people with the correct permissions
  6. Offline


    This uses almost no storage.
  7. Offline


    Can you put out screenshots? I wanted to see how it worked.
  8. Offline


    Hey, ive been hosting my bukkit server for a while now. And it feels like permissions would be great, since ive restored bacups because of griefers several times.. And i think that permisions would prevent this, atleast in many cases. But since ive never been dealing with permissions before i would need som new-user guide for dealing with permissions. Because all ive found is pretty advanced, atleast too advanced for me.. So my question is if anyone here knows a good page with information for a new permission user i would be thankful if you gave me a link or something, to get started with.

    /thanks oskis
  9. Offline


    I hope that in PermissionsBukkit 1.3, there will be support for Mysql
    GameFAQsRolo likes this.
  10. Offline


    So, is anyone going to A) continue working on this, B) going to be updated anytime soon?
  11. Offline


    It's apparently being updated soon.
    I wanted to continue work on it :(
    saul100 likes this.
  12. Offline


    I'm pretty sure hundreds of people told you to update this plugin. But, will you update it? This is my favorite permission plugin, and I only use this. Notify me when (or if) you update the plugin, with a PM to me, or just quote me.
    Thanks, :)
  13. Offline


    Hey this may sound newbish and possibly be in the wrong thread but, are there permission nodes for the default commands like /give? If no, is there a way to make permission nodes that would correspond to those? Thanks.
  14. Offline


  15. Offline


    Aww. At least it's going to be updated soon, though, lol

    SpaceManiac, if you ever read this, at least you can settle with the fact that a lot of people bothering you to update the plugin can only mean that just that many people use it and love it!
    md_5 likes this.
  16. Offline


    Hey guys i have purchased a server and i really want to get it up but i dont know how to config my permissions plugin. So I was wondering if someone could help me. I will gladly make them an admin on my server.
  17. Offline


    I'm assuming you're using PermissionsBukkit? Is your server 1.0.0? If so, the plugin will not work until updated.

    However, if you want to figure out how to configure it, you'll first want to look up the permissions nodes for each plugin. Let's say you're using the plugin WorldEdit by sk89q. You can find the permission nodes at http://wiki.sk89q.com/wiki/WorldEdit/Permissions. Let's say you want to give your Default user class the permission to use the SuperPickaxe.

    The permission node for SuperPickaxe is worldedit.superpickaxe.

    To give your Default user class this plugin, you'd type the following in your config.yml found in /minecraft/plugins/PermissionsBukkit/ directory,
        default:[I] <- has four spaces[/I]
            permissions: [I]<- has eight spaces[/I]
                worldedit.superpickaxe: true [I]<- has twelve spaces[/I]
    NOTE: You MUST have FOUR spaces between each line. NOT TABS. Another syntax note is that you always, always, always need to remember that a permission node is CaSEsenSiTIVe. If a permission node is somePlugin, you CANNOT use someplugin or SomePlugin. Neither will work. if the node is somePlugin, you MUST type somePlugin. Also, remember that you need a space before the true or false when assigning a permission. I made that mistake multiple times early on in my admin-ing life.

    If you want to add more permissions, just add the permissions on the next line with the same number of spaces in front.

    Also before I go on, you'll want to learn what the asterisk (*) symbol means. First, I don't know how much you know about parent/child nodes, but basically, you can think of permissions much like how a file directory works on your computer.

    somePlugin.childNode.anotherChildNode.abilityToDoSomething: true

    In the above line, we know that we are using the plugin, somePlugin. In this plugin, we have a child node called childNode. Below this, we have another child node called anotherChildNode. Note, a plugin can basically have as many child nodes as it wants, though it's usually limited to maybe two at most (for the sake of keeping things organized) Now within anotherChildNode, we have the permission, abilityToDoSomething. This permission is set to true, meaning the class can use said permission.

    In a more practical example, let's look at an example permission from the plugin CommandBook.

    commandbook.home.teleport: true
    commandbook.home.teleport.other: false

    Here, we see that the plugin we're using is commandbook. The child node to that is home. Within home, we have the actual permission, teleport. Now, let's say there are about three or four other child nodes under home, but I don't want to go through the hassle of typing all of them. if I type an asterisk after home, it basically acts like a wild card. By that, I mean that ANY child node that comes after home will be set to true if you typed

    commandbook.home.*: true

    Vice versa, if you did

    commandbook.home.*: false

    you would set all permissions under commandbook.home to FALSE.

    Now for an example of a real permission file. This is my default user class permission list

                ChestShop.shop.*: true
                clear.admin: false
                clear.other: false
                clear.self: true
                commandbook.give: true
                commandbook.give.stacks: true
                commandbook.home.other: false
                commandbook.home.set: true
                commandbook.home.set.other: false
                commandbook.home.teleport: true
                commandbook.home.teleport.other: false
                commandbook.msg: true
                commandbook.say.me: true
                commandbook.warp.set: false
                commandbook.warp.teleport: true
                commandbook.warp.teleport.others: false
                iConomy.accounts.create: true
                iConomy.help: true
                iConomy.holdings: true
                iConomy.payment: true
                ichat.color: true
                ichat.reload: false
                mobsterbox.set: false
                monsterbox.drops: false
                monsterbox.free: false
                monsterbox.place: false
                monsterbox.spawn.*: false
                monsterbox.view: false
                multiverse.teleport.self.w: true
                multiverse.access.*: true
                multiverse.help: true
                multiverse.core.info: true
                multiverse.core.list.worlds: true
                multiverse.core.list.who: true
                multiverse.core.list.environments: true
                multiverse.core.coord: true
                multiverse.core.confirm: true
                niftywarp.admin.delete: false
                niftywarp.admin.rename: false
                niftywarp.admin.set: false
                niftywarp.use.add: true
                niftywarp.use.delete: false
                niftywarp.use.home: false
                niftywarp.use.homeset: false
                niftywarp.use.list: true
                niftywarp.use.rename: false
                niftywarp.use.set: true
                niftywarp.use.version: false
                niftywarp.use.warp: true
                niftywarp.use.warptocoord: false
                permissions.build: true
                playerfreeze.freeze: false
                playerfreeze.freezeall: false
                playerfreeze.warn: false
                playerfreeze.warnall: false
                runecraft.*: true
                runecraft.adminpick: false
                runecraft.faith: false
                runecraft.solarflare: false
                runecraft.topsyturvy: false
                superpermbridge.lockette.admin.*: false
                superpermbridge.lockette.user.*: true
                warpz0r.*: false
                worldedit.*: true
                worldguard.*: false
                xauth.register: true
                OpenInv.*: false
            - default
                Survival World:
                    runecraft.*: false
                    worldedit.*: false
                    commandbook.*: false
                    commandbook.give: false
                    commandbook.give.stacks: false
                    clear.*: false
    You also have inheritance which is basically like "If there is no permission node specified in this class, take the permissions from class X."

    Let's say in your admin class, you want the exact same permissions as default, BUT want to add more.

                permission1.*: true
                permission2.*: true
                - default
                permission3.*: true
                - default
    In the above stated example, the admin, since it has inheritance from the default class, will have permission1.*, permission2.*, AND permission3.*, even though I only have permission3.* set to true in the admin class. Note, you NEED to have the hyphen(-) before the class you're inheriting from.

    Finally, the one last thing you'll want to know to get the basics is assigning a custom user class.

    So you make an admin class. All's good and such. Now, how do you make yourself or anyone else an admin? Simple. At the beginning of the config.yml, you'll notice that you have something like

            - admin
    That's copied from my config.yml, but those are the very first lines of the file. In order to set a user to a certain class, you simply have to follow the syntax of

            - CLASSNAME
    If you wanted to make the user ILovePie to Moderator, you'd type
            - Moderator

    The "four spaces and not tab" rule still applies. You'll want to keep in mind that this applies to EVERYTHING in the permission file. No two spaces, no five spaces. Always four. Also something to note, when assigning the class of Moderator, you don't do four spaces, but rather a hyphen. (-) Don't ask me why, because I don't know.

    You can also set custom permission for just ONE single person. This can be done by
            - Moderator
            plugin1.*: true
    This will set all the permissions for plugin1 to true, ONLY FOR ILovePie. This can be handy if you want to give one specific user elevated privileges but don't want to make an entirely new class.

    That should cover the basics of how to use the permissionsbukkit plugin. If you have any other questions, feel free to PM me or reply on here. Don't worry about making me admin or anything. I like helping people. (If you need server administration help, feel free to ask me, though!)
    Snipes01 likes this.
  18. Offline


    Are the dev builds at getspout official? I noticed the old jenkins for PermissionsBukkit removed it, but I recently saw it on getspout so I'm wondering it it's ok to test those builds out?

    Also, will there be support for info nodes (prefix and suffix) in a future build? Prefixes and suffixes are really the only feature this plugin is missing that the others do have.
  19. Offline


    All the builds are the same. @SpaceManiac hasn't changed anything in several months.
  20. Offline


    Thanks for the info. I guess I was just hoping development was active again. I'd really like to see MySQL and prefix/suffix added.
  21. Offline


    Has anyone continued developing this plugin then? I've been using this plugin since it came out all the way up to 1.8, but I'm reluctant to put this on 1.0 because of compatibility issues. Can anyone confirm this plugin still works correctly in 1.0?
  22. Offline


  23. Offline


    could anyone help me out on my config file
    for some reason my permissions has stopped working
    i cant post the log because our main admin isnt present and hasnt' given me acess to all the stuff by now
  24. Offline


    This plugin works fine for me and I'm using the latest RB?
  25. Offline

    Celtic Minstrel

    @IncendiaDrakon – I haven't confirmed as of yet, but there is no reason not to believe that it'll work on 1.0.

    EDIT: Gah, shanko ninja'd me with a better answer. <_<
  26. Offline


    hello I have some troubles with my permissions.
    I'm in the Admin group and when I use the following commands it says I don't have the perms:

    Please help me ;)

    Here is my config file:

                permissions.example: true
            - admin
            - admin
            - admin
            - user
            - user
            - user
            - user
            - user
            - user
            - builder
            - user
            - user
            - user
                permissions.build: false
                essentials.rules: true
                essentials.spawn: true
                essentials.home: true
                essentials.portal: true
                lwc.deny: true
                commandbook.spawn: true
                commandbook.motd: true
                cfworldman.tp: true
                permissions.*: true
                bukkit.command.gamemode*: true
                commandbook.who: true
                commandbook.clear.other: true
                commandbook.setspawn: true
                worldedit.analysis.count: true
                worldedit.analysis.distr: true
                worldedit.clipboard.save: true
                essentials.god.others: true
                essentials.antioch: true
                essentials.backup: true
                essentials.ban: true
                essentials.ban.notify: true
                essentials.ban.offline: true
                essentials.banip: true
                essentials.broadcast: true
                essentials.burn: true
                essentials.clearinventory.others: true
                essentials.deljail: true
                essentials.essentials: true
                essentials.jails: true
                essentials.kick: true
                essentials.kick.exempt: true
                essentials.kick.notify: true
                essentials.kickall: true
                essentials.kill: true
                essentials.lightning: true
                essentials.setjail: true
                essentials.spawnmob: true
                essentials.tempban: true
                essentials.tempban.exempt: true
                essentials.tempban.offline: true
                essentials.thunder: true
                essentials.jail.exempt: true
                essentials.togglejail: true
                essentials.togglejail.offline: true
                essentials.unban: true
                essentials.unbanip: true
                superpermbridge.dynmap: true
                superpermbridge.worldguard: true
                creativegates.destroy: true
                creativegates.create: true
                cfworldman.create: true
                cfworldman.unload: true
                - builder
                bukkit.command.gamemode: true
                commandbook.time: true
                commandbook.give*: true
                commandbook.give.other: true
                commandbook.time.lock: true
                commandbook.time.check: true
                commandbook.weather: true
                commandbook.weather.thunder: true
                commandbook.teleport.other: true
                commandbook.thor: true
                permissions.build: true
                worldedit.clipboard.copy: true
                worldedit.clipboard.flip: true
                worldedit.clipboard.rotate: true
                worldedit.clipboard.cut: true
                worldedit.clipboard.paste: true
                worldedit.clipboard.clear: true
                worldedit.fast: true
                worldedit.generation.cylinder: true
                worldedit.generation.sphere: true
                worldedit.generation.forest: true
                worldedit.generation.pyramid: true
                worldedit.history.undo: true
                worldedit.history.redo: true
                worldedit.history.clear: true
                worldedit.navigation.ascend: true
                worldedit.navigation.descend: true
                worldedit.navigation.ceiling: true
                worldedit.navigation.thru: true
                worldedit.navigation.jumpto: true
                worldedit.region.set: true
                worldedit.region.walls: true
                worldedit.region.faces: true
                worldedit.region.smooth: true
                worldedit.region.move: true
                worldedit.selection.pos: true
                worldedit.selection.hpos: true
                worldedit.wand: true
                worldedit.wand.toggle: true
                worldedit.brush.options.mask: true
                worldedit.superpickaxe: true
                worldedit.tool.tree: true
                worldedit.tool.replacer: true
                worldedit.brush.sphere: true
                worldedit.brush.cylinder: true
                worldedit.brush.clipboard: true
                worldedit.brush.smooth: true
                worldedit.brush.ex: true
                worldedit.tool.data-cycler: true
                worldedit.drain: true
                worldedit.fixlava: true
                worldedit.fixwater: true
                worldedit.butcher: true
                essentials.give: true
                essentials.bigtree: true
                essentials.item: true
                essentials.itemspawn.item-: true
                essentials.itemspawn.item-all: true
                essentials.compass: true
                essentials.give: true
                essentials.give.item-: true
                essentials.give.item-all: true
                essentials.itemspawn.item-: true
                essentials.item: true
                essentials.god: true
                essentials.time: true
                essentials.time.set: true
                essentials.tree: true
                essentials.lightning: true
                essentials.weather: true
                essentials.setspawn: true
                essentials.home.others: true
                essentials.jump: true
                essentials.tp: true
                essentials.tpa: true
                essentials.tpaall: true
                lwc.admin: true
                lwc.mod: true
                waypoints.admin.create: true
                waypoints.admin.delete: true
                waypoints.admin.save: true
                waypoints.basic.help: true
                creativegates.destroy: true
                creativegates.create: true
                cfworldman.create: true
                cfworldman.unload: true
                - user
                permissions.build: true
                essentials.rules: true
                essentials.spawn: true
                essentials.home: true
                essentials.sethome: true
                essentials.portal: true
                essentials.compass: true
                essentials.help.: true
                essentials.list: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.motd: true
                essentials.clearinventory: true
                essentials.sethome.multiple.unlimited: true
                lwc.protect: true
                magiccarpet.mc: true
                magiccarpet.ml: true
                waypoints.basic.go: true
                waypoints.basic.return: true
                waypoints.basic.list: true
                commandbook.motd: true
                commandbook.clear: true
                commandbook.spawn: true
                creativegates.use: true
                cfworldman.tp: true
                    coolplugin.item: true
        build: '&cYou do not have permission to build here.'
  27. Offline


    Bug: permissions do not respect spawn radius in other worlds. Players can destory (bad), but not build (good) in spawn.
    permissions.build: true
    I don't want to have to install another plugin to just protect spawn of other worlds, as this should be handled by permissions/bukkit's spawn setting.
  28. Offline


    Is this continued?

    I really need different colors for the groups (Prefix, Suffix), EssentialsChat can not handle that and i don't want to many Plugins working with the Chat (already have Factions and Jobs...).

  29. Offline


    I'm not sure about the development of this plugin, but I know that iChat works great for coloring and it's a really lightweight plugin.

    Have you opped yourself? It might be the problem. /op

    Also, you can just use essentials.* and worldedit.* instead of typing all of that...
  30. Why is it that this plugin hasn't been updated since August?? It's been 4 months?? Is this plugin still active?

    On another note.... Players aren't automatically added to the default group when they login... Why is this?
  31. Offline


    Hello, I need your service, be able to help me or get in touch using GMAIL: [email protected] if you need to pay you or I can make a donation to you

Share This Page