A simple plugin to let you make certain items require permissions to use.
This plugin allows you to set up "permission items", so that items which match custom filters that you define will require a specific permission to use. See Configuring for more of an explanation.
- Download either the latest released or development build of the plugin.
- Drop the JAR in your server's
plugins
folder. - Restart your server.
- Edit the config to your liking.
- Reload the config with
/permissionitems reload
.
The basic admin command of PermissionItems.
- Aliases:
pitems
- Permission:
PermissionItems.admin
There are 3 config files for PermissionItems:
config.yml
-- This contains global settings for the plugin.messages.yml
-- This contains the customizable messages for the plugin.items.yml
-- This contains the actual permission items that you have configured.
Both config.yml
and messages.yml
are relatively straightforward, just read the comments in the files.
items.yml
consists of a series of named sections which have a few key properties:
permission
-- The permission required to use this item.filters
-- A list of filter objects that must all match in order for an item to be recognized as this permission item.- (Optional)
prevent
-- Custom overrides for the settings specified inconfig.yml
. - (Optional)
send-messages
-- Custom override for the setting specified inconfig.yml
.
Filters consist of a configuration section with a type
and a value
key. type
must be one of the following:
material
-- Matches the material / type of the item.- Contains an optional
mode
key, which is eitherwhitelist
(only match items of the given type) orblacklist
(only match items other than the given type).
- Contains an optional
durability
-- Matches the durability / damage of an item.- Contains an optional
mode
key, which is eitherequals
,less
, orgreater
.
- Contains an optional
name
-- Matches the custom name of an item. Color codes supported.lore
-- Matches the lore of an item. Color codes supported.- Contains an optional
line
key, which specifies the line number to check (starting with 0 being the first line). If not specified, it will check to see if any line of the lore matches.
- Contains an optional