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

 

No I have a large config file with over 50 people to add ranks to, if I make the config small like some of the ones posted here its fine, but with the amount of people I have to keep track of ranks for, the server nearly crashes when I reload it. Is there a more effecient way of storing people to groups than through the config?

 

Well, i use commandbook right now. It ads a lot of basic commands including banning and kicking. (you can disable all the other commands if you want) It includes permission nodes that prevent the group/user from being banned.

I have 4 year old computer and a config with over 300 players and it finishes reloading like a millisecond after using the perm reload command.
Really a server doesn't need to be that powerful to reload a single text file. If the server is able to run a minecraft server than reloading a config file should be easy. Maybe if you are running your mc server on a really old computer that is only barely able to run an mc server. Than it might give problems.
A more efficient way would be when the plugin would use MySQL to store the users and groups. But unfortunately this plugin does not use this.

 

My server has 80/80 people on it most of the time and runs fine, trust me its not the server, could you PM me your config so I can see how you are handling that many users? I feel like I'm not doing it right if thats the case.

 

Hey, found a bug with the new permissionbukkit update, unless I'm wrong (I'm new to server administrating), when I use the console (or the in game chat) to add a player to a group, set a perm, etc., it messes up all the config rendering it un-usable. Just wanted to let you know, and I really hope for a fix or something. Thanks.

 

just changed all my perms to work with inheritance and it still lags on /permissions reload

 

That... is really small text...
anyway, I've seen more people here with that problem and this usually happens when there is something wrong in the config file. Make sure that the config file is absolutely correct without mistakes and it should work just fine.
The newest version (1.6) seems to be a little bit more strict than 1.2 and doesn't allow any mistakes.

 

Will this plugin be updating?

 

There is no need for an update because it works fine. Why update something that works? xD
If you are wondering if he is going to add any new stuff to the plugin... probably not.

 

As Gotomtom95 already mentioned, your users are not aligned correctly. Also there are 2 empty lines in your config. Corrected version:

Code:

users:
    ConspiracyWizard:
        permissions:
            permissions.example: true
        groups:
        - admin
    Stuey1996:
        groups:
        -default
    Blake1996:
        groups:
        -default
    on_the_rise:
        groups:
        -default
    Pr3ddzk:
        groups:
        -default
groups:
    default:
        permissions:
            permissions.build: true
            permissions.player.setgroup: true
            permissions.player.addgroup: true
            permissions.player.setperm: true
            essentials.tpa: true
            essentials.tpaccept: true
            essentials.tpdeny: true
            simplechestlock.lock: true
            simplechestlock.locktype.chest : true
    admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
    user:
        permissions:
            permissions.build: true
        worlds:
            creative:
                coolplugin.item: true
        inheritance:
        - default
messages:
    build: '&cYou do not have permission to build here umad?.'
debug: false

[/quote]
Thanks for the reply! You have well I guess, half-solved my problem. All I need to have done is make it so that everyone who joins the server be in the default group. Now, if this already the case then something else isn't right because whenever I try to use commands such as /tpa <name> or /tpaccept It says " You don't have access to that command." However, when I try to use a command relating to the permissions commands like /permissions It says "You do not have permissions to do that" Now I'm not that experienced with Permissions, so sorry if I'm wasting your time with such a dumb question!

PS. If someone could kindly configure the permissions for me (Fix what I did wrong) I would love them forever and ever <3

 

I see i left a mistake in...
I changed "simplechestlock.locktype.chest : true" to "simplechestlock.locktype.chest: true" (Removed the space before the ':' sign)
When a user joins and he is not already in another group, he should automatically be in the 'default' group.
I think this should work now.

Code:

users:
    ConspiracyWizard:
        permissions:
            permissions.example: true
        groups:
        - admin
    Stuey1996:
        groups:
        -default
    Blake1996:
        groups:
        -default
    on_the_rise:
        groups:
        -default
    Pr3ddzk:
        groups:
        -default
groups:
    default:
        permissions:
            permissions.build: true
            permissions.player.setgroup: true
            permissions.player.addgroup: true
            permissions.player.setperm: true
            essentials.tpa: true
            essentials.tpaccept: true
            essentials.tpdeny: true
            simplechestlock.lock: true
            simplechestlock.locktype.chest: true
    admin:
        permissions:
            permissions.*: true
        inheritance:
        - user
    user:
        permissions:
            permissions.build: true
        worlds:
            creative:
                coolplugin.item: true
        inheritance:
        - default
messages:
    build: '&cYou do not have permission to build here umad?.'
debug: false

 

Update To 1.2.5-R1.0?????????

 

Not needed. It works fine with 1.2.5

 

can u make someone admin and sethome

 

Hello, please can somebody help me ?? I can make running PermissionBukkit with any plugin i tested (jcommands, CommandBin, .. ) .. Looks i'm missing something but no idea what .. anyway - until i didn't set "op" for my user, for ALL installed plugins and all commands i get "you have no permission" message :-(( I spend maybe 6-10 hours with trying found what is problem and nothing :-((

what i did:

- copyied PermissionBukkit to plugins/
- executed server
- stopped server
- edited plugins/PermissionBukkit/config.yml

Code:

users:
    myuserlogin:
        permissions:
          jcommands.*: true
        groups:
        - admin
groups:
    default:
        permissions:
            permissions.*: false
    user:
        permissions:
            permissions.build: true
        inheritance:
        - default
    admin:
        permissions:
            permissions.*: true
        inheritance:
        -user

i have in plugins/ folder JUST only "PermissionBukkit" and "jcommands" (but tried it with maybe 3-4 plugins where each one had info that it is compatible with PB... with same result as with jcommands) ...

but when i log in as "myuserlogin" .. i still have't permission to use any jcommands command .. only when i add "OP" permissions to "myuserlogin", then i can use commands..

pleaase please, what i'm doing wrong ?? i'm already very frustrated, my job is coder !!! so i'm not common noob.. but i simply can't hack it and found what i'm doing wrong :-((

 

how do you right the config to be world specific

 

It keeps on saying that everyone that I set for different groups is in Default. Did I mess something up in the config? Can you tell me where I went wrong?

 

Actually, Thats Quite The Opposite, My Friend. It Is Broken When I Run It, So YEAH.

 

That its not working for you does not mean its not working for anyone. It works fine for me and the 100 people i helped in the last couple of comment pages.
If it's not working, there is probably a mistake somewhere in your config.

The config seems fine though you are missing the 'messages:' and 'debug:' part.
Did you use spaces for indention? (not tabs)
Are there any errors in the console? Or any errors when using a YAML parser?

Like this:

Code:

groups:
  examplegroup:
    permissions:
      permissions.build: true
      example.permission: true
    worlds:
      creative:
        example.permission2: true
      survival:
        example.permission3: true
    inheritance:
    - default

You went wrong during the part where you did not give any useful information to me so i could search for the cause of this problem. Are there any errors? How does the config look like?

 

it sounds like you had the same problem I did - my patch on github seems to work fine for me regarding these commands. (for 1.2.5R1.0 )

 

UPDATE?

 

Not sure if trolling.... or just too lazy to read the first 2 comments on this page...

 

My config file looks like this

Code:

users:
    trout121234:
        permissions:
            permissions.*: true
            permissions.example: true
        groups:
        - admin
    Vidgamewiz:
        permissions:
            permission.node
        groups:
        - Mayor
    Jorge1397:
        permissions:
            permission.node
        groups:
        - TownsFolk
    ksmckim:
        permissions:
            permission.node
        groups:
        - TownsFolk
       
       
    SKAMPERS:
        permissions:
            permission.node
        groups:
        - TownsFolk
    pacr11397:
        permissions:
            permission.node
        groups:
        - Outsider
groups:
    default:
        permissions:
            permissions.build: false
    Owner:
        permissions:
            permissions.*: true
        inheritance:
        - user
    TownsFolk:
        permissions:
            permissions.build: true
        inheritance:
        - default
    Mayor:
        permissions:
            permissions.build: true
        inheritance:
        - Peasant
messages:
    build: '&cYou do not have permission to build here.'
 
debug: false

 

1. There are 2 empty lines between 'ksmckim' and 'SKAMPERS'
2. There is an empty line between 'build:' and 'debug:'
3. Never write a 'permission.node' without true or false after it.

Here is it with the those fixes:

Code:

users:
    trout121234:
        permissions:
            permissions.*: true
            permissions.example: true
        groups:
        - admin
    Vidgamewiz:
        permissions:
            permission.node: true
        groups:
        - Mayor
    Jorge1397:
        permissions:
            permission.node: true
        groups:
        - TownsFolk
    ksmckim:
        permissions:
            permission.node: true
        groups:
        - TownsFolk
    SKAMPERS:
        permissions:
            permission.node: true
        groups:
        - TownsFolk
    pacr11397:
        permissions:
            permission.node: true
        groups:
        - Outsider
groups:
    default:
        permissions:
            permissions.build: false
    Owner:
        permissions:
            permissions.*: true
        inheritance:
        - user
    TownsFolk:
        permissions:
            permissions.build: true
        inheritance:
        - default
    Mayor:
        permissions:
            permissions.build: true
        inheritance:
        - Peasant
messages:
    build: '&cYou do not have permission to build here.'
debug: false

 

I'd like for my moderators to be able to add a default user (Newbie) to a trusted or builder group or back down to default if necessary. However, I'd like for them not be be able to player addgroup to the level at theirs or above. Is this possible?

 

I can't seem to find any helpful info on how to display messages like the one that would tell someone they don't have permission to build. Based on what I have found, I kinda figured it would go like this;

Pay attention to the "default" group and keep in mind that this is for a server I am making from scratch.

Code:

users:
  MisfireXVII:
    groups:
    - default
groups:
  admin:
    permissions:
      permissions.*: true
  default:
    permissions:
      permissions.build: false
    messages:
      messages.nobuild: true
  member:
    permissions:
      permissions.build: true
  moderator:
    permissions:
      permissions.build: true
  owner:
    permissions:
      permissions.*: true
  veteran:
    permissions:
      permissions.build: true
  vip:
    permissions:
      permissions.build: true
messages:
  nobuild: '&cYou do not have permission to build. Please contact an Admin.'
debug: false

What am I doing wrong?

 

I have a server running permissionsbukkit 1.6 with no issues.
Now i am setting up a test server on a different machine and get this error.
What am i doing wrong????

14:18:21 [SEVERE] Could not load 'plugins\PermissionsBukkit-1.6.jar' in folder 'plugins'
org.bukkit.plugin.InvalidDescriptionException: Invalid plugin.yml
at org.bukkit.plugin.java.JavaPluginLoader.getPluginDescription(JavaPluginLoader.java:201)
at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:132)
at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:207)
at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:183)
at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:53)
at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:156)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:422)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader.getPluginDescription(JavaPluginLoader.java:189)
... 7 more

 

1.2.5?!

Why do I get error? My config is this:

Code:

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

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

 

Snowy007: no errors at console .. anything .. everything looks OK .. when i set "OP" privileges to my user, i can use all comands from jCommands.. it only looks that all permission set in PermissionBukkit are simply ignored

here i packed ALL config files of my server http://dl.dropbox.com/u/7116402/all_configs.zip

i you will so kind look at it and check what is wrong i will be strongly thanksfull

i was blind !!! there is one error in my server log ....

Code:

18:55:53 [SEVERE] [PermissionsBukkit] Unable to load configuration!

but no idea what is wrong, why it is unable to load cfg...

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

 

I can't get my plugins to work at all. It just doesn't give groups except admins/op access to the commands.

Here is my code for the permissions.yml file:

Code:

users:
    seven50six6:
        permissions:
            permissions.*: true
            permissions.example: true
        groups:
        - admin
    JoshSizemore:
        permissions:
            permission.*: true
        groups:
        - admin
groups:
    default:
        permissions:
        essentials.afk
        essentials.help
            permissions.build: true
            essentials.list
            essentials.mail.send
            essentials.mail
            essentials.me
            essentials.nick
            essentials.realname
            essentials.rules
            essentials.suicide
            essentials.spawn
            essentials.home
            essentials.sethome]
            essentials.warp
            lockette.user.create.*
    moderator:
        permissions:
            permissions.build: true
            essentials.ban
            essentials.broadcast
            essentials.unban
            essentials.mute
            essentials.kick
        inheritance:
        - default
messages:
    build: '&cYou do not have permission to build here.'
debug: false

 

It's 'build', not 'nobuild'. Start there.

YAML is extremely finicky...you're spacing is off in the default group and you have no space between false and the colon in permissions.build for medlem.

All of these need a true/false switch with permissions...and your sethome has an illegal character.

Hope I helped.