Unsatisfied with a number of other permissions management plugins publicly available, I sought to create a lighter and more elegant plugin to handle group-based permissions. With a focus to making all of the commands understandable at a glance and providing helpful details when queried. You should be able to get on with permissions management simply through typing /help GroupPermsLite and reading the command descriptions.

If you are unfamiliar with Bukkit permissions, please see the Wiki Article and the Forum FAQ


  • Simple and elegant
  • Easy to use and understand
  • Allows setting up an unlimited number of groups (names are case-insensitive)
  • Has a default group called "all" that all players start in
  • Has a unique group for each player called "personal_[player name]" that allows individual permissions settings
  • Saved in YAML format, advanced users can read and manage on disk and reload while the server is running using a command
  • Simple and easy to use commands to add/remove players from groups and grant/revoke permissions from groups
  • Allows use of the wildcard (*) to match any value for a node in a permission string when granting permissions using a command
  • Allows adding negative permissions using the (-) operator to prevent a particular group from receiving the given permission from any other source

Ideas for future development

  • /hasPermission ([player]) [permission node] - For manually checking permissions of a player and for use in command blocks
  • Tab auto-completion for registered permission nodes
  • Support for Vault for better compatibility with plugins such as the LWC group feature
  • A command to rename a player in order to support upcoming Mojang name changing feature


/GroupCreate [group]group.adminCreates a group without adding a player or permission
/GroupAddPlayer [group] [player]group.adminAdds a player to the given group (creates the group if it doesn't already exist)
/GroupRemovePlayer [group] [player]group.adminRemoves a player from the given group
/GroupGrantPerms [group] [(-)permission-string]group.adminGrants the given permission(s) to the specified group (creates the group if it doesn't already exist)
/GroupRevokePerms [group] [permission-string]group.adminRevokes the given permission(s) from the specified group
/GroupListPerms [group] ([page number])group.adminLists all of the permissions for a given group
/GroupListPlayers [group]group.adminLists all players in a given group
/GroupListgroup.adminList all groups
/GroupDelete [group]group.adminDeletes a given group
/GroupReloadgroup.adminReloads config from disk
/RegisterPerm [permission node] [default(op/not-op/true/false)]group.adminManually register an unregistered permission node

Most commands have a "silent" feature that is activated by placing a "-s" (without quotes) at the end. This is intended to be used with command blocks and command scripting plugins to allow you to manage your permissions through these without generating lots of console spam. You will still get a response if the command fails however.


  • RankDisplayNames - Create ranks with chat prefixes that update automatically with permissions set through GroupPermsLite


It says the permission is not registered, what can I do?

Sometimes plugin developers will forget or simply not bother to register their permissions with Bukkit, but still use them in their code. Fortunately, the bukkit permissions.yml file can come to the rescue here. You should be able to find the permissions.yml file in the server directory. It is used by server owners to manually register additional permissions in bukkit. See for details about editing the Permissions YAML. It is usually used to group permissions together so that they can all be assigned at once (this is compatible with GroupPermsLite!), however there is also nothing stopping you from registering all of the unregistered permissions for a plugin manually.

For example, here is how to register all of the permissions for Essentials (the most notorious for not registering their permissions): You can cut and paste these into your permissions.yml if you use essentials. Be aware that permissions with square brackets [ ] around a permission node mean that you have to change that to the specific type you want in order for it to work.

Coming in v0.4: Added support for unregistered permissions - You will be able to grant unregistered permissions to a group with a prompt for confirmation

This plugin uses Java 7

If you get the followed error on starting up the server with this plugin installed "Unsupported major.minor version 51.0". This means you are using an out of date version of Java. If you don't know how to upgrade, please contact your server hosting provider and ask them for help in upgrading to Java 7, or contact Oracle customer support. Mac OS X users require JDK 7 instead of JRE 7.


If you like my work, please consider donating using the Donate button in the top-right corner of the screen. As a freelance professional, I rely on donations and payments to support my work. Anything you can contribute to support my work will allow me to spend more time making plugins for Bukkit and supporting the plugins I publish. Thank you.

Everything I create here will be 100% free to download and use as you please, just keep the license attached and give me credit for the original work if you decide to redistribute.



If you need help you can leave a comment below and I will get back to you as soon as I can. You can also join my IRC chatroom using the following link. Please note, I am not always at my keyboard!

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of XHawk87 XHawk87 Jan 28, 2015 at 21:27 UTC - 0 likes

    @njojo11: Go

    Just missed out one argument. You have to tell it which group to grant perms to:

    /GroupGrantPerms [Group] [permissions]

    So it'd be:

    /GroupGrantPerms Owner ranks.membership.1Owner

    If you have trouble remembering which way around the arguments go, it is always the same was as in the command name. /GroupGrantPerms write the Group then the Perms.

    P.S. /GroupReload is only needed if you change the configuration files and want them to be updated while the server is running

    Last edited Jan 28, 2015 by XHawk87: P.S.

    I am currently working on: Security

  • Avatar of njojo11 njojo11 Jan 28, 2015 at 20:50 UTC - 0 likes

    <<reply 2467169>>

    Okay well I am still a bit confused! I have little experience with promotion plugins. Can you type the commands to make a group then give the name perms? I did ./rankcreate 1Owner %5[Owner]    then I did /groupcreate Owner  after that I did /groupgrantperms ranks.membership.1Owner  then I did ./groupreload.  Did I completely fail?

  • Avatar of njojo11 njojo11 Jan 28, 2015 at 12:05 UTC - 0 likes

    <<reply 2467169>>

    Oh I am so stupid! Haha, thanks for the quick response!

  • Avatar of XHawk87 XHawk87 Jan 28, 2015 at 02:57 UTC - 0 likes

    @njojo11: Go

    A rank and a group are different things. A rank is displayed by name, and groups are used to determine what permissions a player has.

    You need to create a group for those players, and give that group the ranks.membership.1Owner permission, along with whatever other permissions you want that group to have. Then you can start adding people to the group to give them those permissions and that rank beside their name.

  • Avatar of njojo11 njojo11 Jan 28, 2015 at 01:02 UTC - 0 likes

    I need help! I did ./rankcreate 1Owner %5[Owner]
    And it created the rank. I after that did ./groupaddplayer 1Owner [Person]
    and it said 1Owner group doesn't exsist! I don't understand It was created!

  • Avatar of giano2 giano2 Jan 22, 2015 at 11:09 UTC - 0 likes

    @XHawk87: Go

    okay i shall double check everything and thanks again for quick responds

  • Avatar of XHawk87 XHawk87 Jan 21, 2015 at 17:56 UTC - 0 likes

    @giano2: Go

    It sounds like you forgot to tell it which group to grant permissions to. It is:

    /GroupGrantPerms [group] [permission]

    So you would type:

    /GroupGrantPerms all bukkit.command.teleport

    All CraftBukkit permissions will already be registered, so if it says the permission is unknown then you should double check that it was typed exactly right. You only need to use /RegisterPerm for plugins that do not register all of their permissions.

  • Avatar of giano2 giano2 Jan 21, 2015 at 13:58 UTC - 0 likes

    okay im back i think im just stupid but i want dat one group has permission to use the teleport command from bukkit without needed to being OP

    i tried the command /GroupGrantPerms bukkit.command.teleport but then he said there is no registered permission with that match so i tried /RegisterPerm bukkit.command.teleport but he always say info: /RegisterPerm [permission-string] [default(true false op notop) so i dont know what i do wrong i have tried /GroupGrantPerms bukkit.command.teleport true notop and default true notop but nothing works so here by i ask if you can help me with it

  • Avatar of giano2 giano2 Jan 21, 2015 at 10:41 UTC - 0 likes


    thanks for the quick responds i will try what you said


  • Avatar of XHawk87 XHawk87 Jan 20, 2015 at 23:35 UTC - 0 likes

    @giano2: Go

    The command to add permissions to a group is:

    /GroupGrantPerms [group] [(-)permission-string]

    The "all" group is the default one that all players are in. To grant all players a permission, you would do: "/GroupGrantPerms all the.permission.node"

    If you want to create a group that only includes the new players that join your server, I suggest setting up a little Skript to add players to that group on first join.

    on first join:
        execute console command "/GroupAddPlayer newbies %player%"


Date created
Jan 15, 2013
Last update
Sep 11, 2014
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Recent files