Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

I cannot for the life of me figure out how permissions.yml works for a CraftBukkit Minecraft Server. Here is what I want:

I would like three groups: admin, user, and default.

  • Admins should have complete access to all commands
  • Users should be able to use /tp and maybe a couple other commands
  • Defaults should not be able to use any command.

Here's what I have:

  5 users:
  6     my-name:
  7         groups:
  8         - admin
  9 groups:
 10     default:
 11         permissions:
 12             bukkit.command.*: false
 13     admin:
 14         permissions:
 15             bukkit.command.*: true
 16         inheritance:
 17         - user
 18     user:
 19         permissions:
 20             bukkit.command.teleport: true
 21             bukkit.command.tell: true
 22             bukkit.command.me: true
 23             bukkit.command.kill: true
 24         inheritance:
 25         - default
 26 messages:
 27     command.*: '&cYou do not have permission to use that command'

Can someone please do me a huge favor and help.

share|improve this question
I' m not the best at explaing this, so here is a tip instead. I would recommend using permissionsEX as it allows for easier use of permission nodes and integrates features such as name prefixes, suffixes, and in-game commands. NOTE: If you want to use essentials, it will not be compatible. Other plugins may not be either, but the more popular ones tend to be alright. –  Jonny Feb 15 '12 at 5:45

2 Answers 2

up vote 4 down vote accepted

Quite simply, the permissions.yml file that is in the root directory of your server does nothing on its own. It's a somewhat odd and misleading feature, so it's understandable that you'd be confused. The permissions.yml file is used only to create custom permissions node aliases and group nodes. To be perfectly honest, I find it fairly useless.

The format you are using does not go in the root permissions.yml, it goes in the config.yml of a plugin known as PermissionsBukkit. This is a plugin that actually manages the permissions for you, and you need some kind of permissions plugin to use the system effectively. You should be able to cut/paste your current permissions.yml file into the PermissionsBukkit config.yml, and it should work just fine.

This is a somewhat opinionated note, but I think it's worth pointing out that there are other permissions plugins out there besides PermissionsBukkit. There are two other main permissions plugins out there, PermissionsEX (my personal favorite) and bPermissions. These have a format slightly different from PermissionsBukkit, but they have many more features, including a good command system and much better APIs, so they might save you trouble in the long run.

share|improve this answer

Looks pretty good

Things to check:

This is the permissions file in your plugins/PermissionsBukkit folder.

You are missing users--you need to assign groups to each user (just like your name)

Don't use tabs, make sure everything is spaces.

I'm not sure how much indentation matters, but the default file is indented 2, not 4.

permGroup.* is not specifically implemented in permissionsbukkit, it's generally passed through to the plugin which seems to often implement it, but there is no guarantee. I give bukkit.* to my admin and that seems to work.

To test, put your account in the group you want to test, get on the game, muck with the permissions file then go to the console and type "reload", then use:

"perms dump myplayername"

to page through the permissions and see if you got it right. (Please add comments if you have better ways to test this, I've had a hell of a time with permissions)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.