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

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 Hide 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 Hide 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 Hide 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) 1. Where are my * nodes? (close)

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) 2. How do I use SuperpermsBridge? (close)

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) 3. How do I use the root permissions.yml? (close)

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) 4. How do I switch from (other Permissions plugin)? (close)

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) 5. Where are prefixes and suffixes (or option nodes)? (close)

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) 6. (Coders) How do I set up my plugin.yml? (close)

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) 7. Is PermissionsBukkit outdated? (close)

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)



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.

 

Thanks for the reply, The guy changed his name, but what about the other issues?

 

I dunno; does falsebook support superperms?

 

I think according to the thread. I can take off Superperms if needed in the config. Here is my config file:

Code:

# PermissionsBukkit configuration file
#
# A permission node is a string like 'permissions.build', usually starting
# with the name of the plugin. Refer to a plugin's documentation for what
# permissions it cares about. Each node should be followed by true to grant
# that permission or false to revoke it, as in 'permissions.build: true'.
# Some plugins provide permission nodes that map to a group of permissions -
# for example, PermissionsBukkit has 'permissions.*', which automatically
# grants all admin permissions. You can also specify false for permissions
# of this type.
#
# Users inherit permissions from the groups they are a part of. If a user is
# not specified here, or does not have a 'groups' node, they will be in the
# group 'default'. Permissions for individual users may also be specified by
# using a 'permissions' node with a list of permission nodes, which will
# override their group permissions. World permissions may be assigned to
# users with a 'worlds:' entry.
#
# Groups can be assigned to players and all their permissions will also be
# assigned to those players. Groups can also inherit permissions from other
# groups. Like user permissions, groups may override the permissions of their
# parent group(s). Unlike users, groups do NOT automatically inherit from
# default. World permissions may be assigned to groups with a 'worlds:' entry.
#
# The cannot-build message is configurable. If it is left blank, no message
# will be displayed to the player if PermissionsBukkit prevents them from
# building, digging, or interacting with a block. Use '&' characters to
# signify color codes.

users:
    Userexample:
        groups:
        - default
    Soap:
        groups:
        - admin
    superzilla:
        groups:
        - admin
    hugh.:
        groups:
        - admin
    Bob:
        groups:
        - special
    E7:
        groups:
        - admin
groups:
    default:
        permissions:
            permissions.build: true
            minecraft.tp: true
            superpermsbridge.falsebook.blocks.*: true
            superpermsbridge.falsebook.destroy.blocks: true
            superpermsbridge.falsebook.ic.standard: true
            superpermsbridge.falsebook.ic.detection: true
            superpermsbridge.falsebook.ic.selftriggered: true
            superpermsbridge.falsebook.cart.*: true
            mothernature.command.umbrella: true
            mothernature.command.help: true
    admin:
        permissions:
            permissions.*: true
            minecraft.*: true
            mothernature.night: true
            mothernature.command.help: true
            mothernature.command.version: true
            mothernature.command.reload: true
            mothernature.command.rain: true
            mothernature.command.thunder: true
            mothernature.command.lightning: true
            mothernature.command.sun: true
            mothernature.command.umbrella: true
            mothernature.wand: true
            mothernature.lwand: true
            mothernature.day: true
            superpermsbridge.falsebook.anyic: true
            superpermsbridge.falsebook.blocks.*: true
            superpermsbridge.falsebook.destroy.blocks: true
            superpermsbridge.falsebook.cart.*: true
    special:
        permissions:
            permissions.*: true
            minecraft.*: true
            mothernature.night: true
            mothernature.command.help: true
            mothernature.command.version: true
            mothernature.command.reload: true
            mothernature.command.rain: true
            mothernature.command.thunder: true
            mothernature.command.lightning: true
            mothernature.command.sun: true
            mothernature.command.umbrella: true
            mothernature.wand: true
            mothernature.lwand: true
            mothernature.day: true
            superpermsbridge.falsebook.anyic: true
            superpermsbridge.falsebook.blocks.*: true
            superpermsbridge.falsebook.destroy.blocks: true
            superpermsbridge.falsebook.cart.*: true
            minecraft.gamemode: true
messages:
    build: '&cYou do not have permission to build here.'

And here is the thread for falsebook: http://forums.bukkit.org/threads/me...t-80-ics-cauldrons-gates-minecarts-1185.7227/

 

Oh silly me. thank you for your help. It works now!

 

Oh derp, its superpermbridge.<permission>
Stupid me, I'll see if that fixes it.

Nope, Not fixed.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

@Superzilla – Since FalseBook apparently supports superperms, you should make sure that it's set up to use them; then you won't need the superpermbridge stuff. (Or make sure FalseBook is set up to use PermissionsBukkit for permissions, if such setup is required.)

 

Is there anyway to make it so a group can do every command so I don't have to list everything out?

 

I'm going to go try another permissions plugin right now, It says it's the first try to implement this, so it's probably buggy.

 

Such a garbage permission plugin.. Just stick with 3.0. nothing wrong with it

Can you make a proper convertor for Permissions 3.X. If im forced to use this piece of garbage i want to at least get a working convertor so i dont have to re write all my permissions because some plugin developer is Ego hungry

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Is there prefix and Suffix? If Not how do I make it so it has a tag before the players name depending on what group there in.

 

You must use a plugin such as mChat for prefixes. I recommend sticking with a different plugin such as PermissionsEx.

 

Thanks a lot! Downloading the new version fixed everything

 

Where in the config file? I've looked and cannot see anything about spawn permissions Etc.

 

There's plenty wrong with Permissions 3.0. You're not forced to use this, though. There are at least three other options: zPermissions, bPermissions, and PermissionsEx are the ones I know of.

@kyle939 - Look for a bukkit.yml file in the same folder as your server jar. That file contains spawn radius settings, the radius within which only ops can place or destroy blocks.

 

I cant seem to get the users to attach to the default group :/ this is what i have set up:

Code:

users:
    04dowie:
        permissions:
        groups:
        - owner

    asgar:
        permissions:
        groups:
        - admin
groups:
    default:
        permissions:
            permissions.build: true
            craftbook.mech.ammeter.use
            craftbook.mech.bookshelf.use
            craftbook.mech.cauldron
            craftbook.mech.elevator
            craftbook.mech.gate
            craftbook.mech.light-switch
            craftbook.ic.safe.*
            train.build.station
            train.build.spawner
            train.build.trigger
            train.build.destructor
            train.build.ejector
            train.build.pushHandler
            train.place.minecart
            train.command.properties
            lwc.protect
            admincmd.tp.home
            admincmd.tp.spawn
            admincmd.player.msg
            admincmd.player.afk

    admin:
        permissions:
            permissions.*: true
            lwc.mod
            lwc.protect
            admincmd.weather.*
            admincmd.player.*
            admincmd.time.*
            admincmd.tp.*
        inheritance:
        - default
    owner:
        permissions:
            permissions.*: true
            lwc.admin
            admincmd.*
        inheritance:
        - default

This is probably irrelevant but i use multiplay and therefore use "clanforge" but when i save it i get this error:

Code:

     error    Config file 'permissions.yml' has an error, this will break your plugin!
         Error at or BEFORE line: 15, column: 8
         Line 15 is: craftbook.mech.bookshelf.use

 

You're missing the ": true" on most of the lines. Also, did you put it in permissions.yml in the same folder as the server jar? It should be in config.yml in the PermissionsBukkit folder within the plugins folder.

 

Thanks for your help its all working now sorry for my silly mistake.. Only problem i have now is whenever a user in the default group places a block the text "you do not have permission to do that" appears, it still places the block but i can see people finding that very annoying

Edit: on further investigation some other commands are not working for the default group either such as admincmd.tp.home

 

I'm looking for some sort of "default: true" to place on a group to make it the default group, or just a way to change the name of the default group. Just altering the name it self in the config makes ungrouped people land in an "invisible" default group.

 

how do I setup users with multi groups properly,
if one of these groups has bukkit.command.gamemode: true
but another inherits to a group with set this to false

in my opion it should not matter in which order the groups are because one group has the allowed permission, the other one only inherits to one, that denies this.

But it looks like the first group is the strongest, the following are weaker.
If (group1.hasPermData()) return group1.perm...
else if (group2.hasPermData()) return group2.perm...
...
else return permdefaults.perm...

In my case i want to deny creative mode to everyone (including ops/admins) except the builder group (with a lot of differnt build permissions, worldedit...)
The builder group may contain non ops and I don't trst them very much.
So users and admins can be in builder group.
admin inherits from users
users deny gamemode
admin inherited deny gamemode
builder allows gamemode

TheUser is in the following groups: admin, builder
because admin is the first listed TheUser cannot use gamemode and nothing will change that except of deleting user inheritance from admins. But admins should not be allowed to gamemode, they should join builder group!
The ingame commands adds the new group at the end of the player's grouplist. So turning builder mode on/off beomes very ugly.

Is there an priority option/value for groups?

 

I am using this with McMyAdmin, and how do I make a group the default group?

 

I just recently updated to Permissions 1.2k on my server. My server is running CB 1185 and McMyAdmin. For some reason I cannot get anyone to build in the server. I updated by replacing both superpermsbridge and permissionsbukkit.jar but not the config files. Should I delete them and have permissionsbukkit start fresh?

I don't know what the issue is but that's the only thing I could think of. Let me know if you need more information. I don't have an error in my logs and I know it's permissions cause when I disable it, people can build.

 

My friends are unable to build or use most commands, but before I updated PermissionsBukkit, the permissions worked just fine...

Can't build
Can use LWC to protect, but are unable to open protected items (Due to no build rights.)

Help please...

Code:

users:
    SilentHopes:
        permissions:
            permissions.example: true
        groups:
        - admin
    XenoTehNoob:
        permissions:
            server.member: true
            permissions.build: true
            essentials.clearinventory: true
            essentials.kit.*: true
            essentials.kit.<kitname>: true
            essentials.kit: true
            essentials.balance: true
            essentials.balance.others: true
            essentials.pay: true
            essentials.sell: true
            essentials.worth: true
            essentials.afk: true
            essentials.help: true
            essentials.list: true
            essentials.ignore: true
            essentials.mail: true
            essentials.mail.send: true
            essentials.motd: true
            essentials.msg: true
            essentials.nick: true
            essentials.rules: true
            essentials.rules: true
            essentials.suicide: true
            essentials.back: true
            essentials.back.ondeath: true
            essentials.sethome: true
            essentials.top: true
            essentials.warp: true
            essentials.warp.list: true
            essentials.home: true
            mobarena.use.*: true
            lottery.buy: true
            mobarena.classes.*: true
            ChestShop.shop.buy: true
            ChestShop.shop.sell: true
            mobarena.arenas.*: true
            lwc.protect: true
            essentials.spawn: true
            essentials.back.*: true
            essentials.signs.use.*: true
            essentials.protect.damage.*: true
            essentials.top: true
            permissions.build: true
            lwc.protect: true
        groups:
        - Member
    fishboyliam:
        permissions:
            permissions.build: true
        groups:
        - Member
groups:
    Member:
        permissions:
            permissions.build: true
            server.member: true
            permissions.build: true
            essentials.clearinventory: true
            essentials.kit.*: true
            essentials.kit.<kitname>: true
            essentials.kit: true
            essentials.balance: true
            essentials.balance.others: true
            essentials.pay: true
            essentials.sell: true
            essentials.worth: true
            essentials.afk: true
            essentials.help: true
            essentials.list: true
            essentials.ignore: true
            essentials.mail: true
            essentials.mail.send: true
            essentials.motd: true
            essentials.msg: true
            essentials.nick: true
            essentials.rules: true
            essentials.rules: true
            essentials.suicide: true
            essentials.back: true
            essentials.back.ondeath: true
            essentials.sethome: true
            essentials.top: true
            essentials.warp: true
            essentials.warp.list: true
            essentials.home: true
            mobarena.use.*: true
            lottery.buy: true
            mobarena.classes.*: true
            ChestShop.shop.buy: true
            ChestShop.shop.sell: true
            mobarena.arenas.*: true
            lwc.protect: true
            essentials.spawn: true
            essentials.back.*: true
            essentials.signs.use.*: true
            essentials.protect.damage.*: true
            essentials.top: true
            permissions.build: true
            lwc.protect: true
    Admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
    Moderator:
        permissions:
            permissions.build: true
        worlds:
            creative:
                coolplugin.item: true
        inheritance:
        - default
messages:
    build: '&cYou do not have permission to build here.'

 

I have a very similar problem to where people are unable to build on my server however I find it not Permissionbukkits fault. I have found that with using the essentials plugin pack and limited command to different user groups (I am using McMyAdmin to do all this) no one is able to build unless their group or a group they inherit permissions from has "essentials.*" defined in their permissions listing.

Where i could just give everyone essentials.* permissions and allow them to build it kinda defeats the purpose of using permissions to limit things another workaround that has shown light to work is to disable the essentials protect plugin that too will allow users to build only problem with that though is half my world would burn to a crisp thanks to some creative block placements so if any one has any ideas throw 'em out there and ill try them. Oh and i have tried things such as "essentials.protect.*"and "essentials.protect" and permissions.build (but this is set to true anyways by default)

 

Whens next update due

 

after I updated to the 1.8.1 compatible build, all my members are unable to build or break blocks. I deopped myself (since im owner i am the only op) and had the same issue, I didnt change anything in my permissions file. whats wrong?

same issue

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Disable the essentials protect plugin, that is where the conflict is. I am using a plugin called safe creeper, which solves the only reason I used essentials protect really.

 

I players on my server have become to rely on the protect plugin keeping their flaming fortreses of various kinds from burnninating the countryside so to speak. I will continue to poke at it in coming days after some upcoming tests in school

 

Bukkit just has permissions in it's plugin API. You still need a plugin to enter the permissions.

 

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)

 

@ Jobi, that looks like the code should work. If you're wondering, ask someone on the server if it works.

To those of you needing EssentialsProtect, I would scrap it. I recommend WorldGuard, you can block creeper explosions, TNT explosions, fire spread, and more. There's a lot of options you can chose to block.