zPermissions

Herocraftonline.com has been testing zPerms for over 3 years in production, its beast, use it!

zPermissions is primarily an SQL database-backed Superperms (aka Bukkit permissions) implementation. It also supports flat-file storage. Notable features are: multi-world support, ranks with multiple tracks/ladders, group inheritance of arbitrary depth (within reason), and optional region-specific permissions using WorldGuard regions, Residence residences, Factions territories, or Factoid lands.

There is no built-in build protection (I rely on other plugins for that). zPermissions focuses on permissions and only permissions.

I aim to keep zPermissions a simple, yet feature-rich, Superperms provider.

zPermissions supports UUIDs as of the 1.3beta1 release! See the notes for that release for details.
[ Quick start documentation | For Server Admins | FAQ | More documentation below! ]

Questions? Problems?
First, please check the known issues as well as the FAQ.

If your question is still unanswered, please post on the forum.

Finally, for any bugs/issues, please create ticket.

Unless I already know you, PMs will be ignored.

Features

• A variety of storage options, from SQL to flat-file. Uses Bukkit database to store permissions (i.e. settings in bukkit.yml). Should work with most databases supported by Avaje Ebean — I've specifically tested with PostgreSQL, MySQL, and H2. The default Bukkit database, SQLite, isnot supported. zPermissions will automatically fall back to flat-file storage if it is used.
  
  
• Group inheritance. Groups may inherit permissions from a multiple parent groups.
  
  
• Players may be members of more than one group. The order of which group permissions are applied is well defined and based on group weight (which is configurable, of course).
  
  
• Multi-world support. Permissions granted to players and groups may be associated with a specific world.
  
  
• Optional region support. Permissions may also be associated with WorldGuard regions or Residence residences.
  
  
• Multiple promotion tracks! Using permissions, you can also limit who can promote/demote others and which tracks they may use. In addition, each player may be promoted/demoted along multiple tracks.
  
  
• Short-term temporary permissions. Give a player a permission node that lasts anywhere from a few seconds to a few minutes.
  
  
• Temporary group assignments. Assign a group to a player and have their membership expire after 1 day... a few months... or a year! Whatever duration you want.
  
  
• Players and groups can be assigned chat prefixes and suffixes. A Vault-compatible chat-formatting plugin is still required, like Herochat, zChat, etc.
  
  
• API. zPermissions offers a comprehensive read-only API that other plugins can use. (Though I would recommend coding against Vault instead.)
  
  
• Metadata support. Players and groups may have arbitrary metadata associated with them. Metadata values may be strings, integers, reals (floating point), and booleans. Metadata may be queried via the native API or Vault Chat API.
  
  
• Automatic group permissions. With the advent of Superperms/Bukkit permissions, the recommended way of testing group membership is by using permissions. zPermissions can automatically set a permission based on the group's name for each group. By default, this configurable permission is group.<groupname> (compatible out-of-the-box with WorldEdit and WorldGuard!).