Skip to content
Alan Litz edited this page May 26, 2014 · 13 revisions

NoItem 4.X series is my attempt at a major change in direction from all previous NoItem version. There are some fundamental changes to the way NoItem works and how it was written.

Here are some highlights:

  • Permissions are now different and are more flexible
  • Notification messages now have a configurable delay (in seconds) before they will be shown again
  • Much simpler configuration (although less options, but they weren't really needed)
  • Certain asterisk values are still supported! Woot!

Permissions now follow the format:
noitem.action.<action>.<object>[.second object]
noitem.object.<object>[.second object].<action>
Where <object> is the objects name (e.g. chest or stone) and <action> is the action type (e.g. break or place). The second object is usually a durability value, but may vary depending upon the action type.

These two different kinds of permission make it easier to do what you want with less permissions. They both support the asterisk value after the action type or object name. (Or after the second object in the case of "noitem.object.[.second object].*") This new permission format lets you easily block every action for a specific object, or every object for a specific action.*

*In the case of crafting, only a 2 object permission is checked unless the durability of the item being crafted is 0.

Currently implemented action types are:

  • break
  • place
  • craft
  • cook
  • open
  • pickup
  • drop
  • hold
  • interact.object
  • brew - The format for the brew permission is "noitem.object.potion.<type>[.extended][.splash].brew"

You can use these for the <action> part of the permission.

Item ID's are going away with future releases of MineCraft, so I do not have support for them. Currently only item names work in permissions. You can find all item names by looking at this class and taking any value, and putting it in lower case. (e.g. GOLD_ORE would be gold_ore)

Permissions Overview

noitem.action.<action>.<object>[.second object]
noitem.object.<object>[.second object].<action>

Item ID's are not supported in permissions. Use item names instead (e.g. diamond_pickaxe). Leave the underscores, that is important!

SPECIAL NOTE FOR POTION PERMISSIONS:

Permissions for potions are unique. They use the potions effect name and can be chained with .extended and .splash

For example, a valid potion permission is "noitem.object.potion.water_breathing.extended.brew" You can find all valid potion effects here: http://jd.bukkit.org/rb/apidocs/org/bukkit/potion/PotionEffectType.html


Development Builds Available from My Jenkins Instance

http://ci.worldoftomorrow.net/ <- Jenkins

The Single All-Important Command of Doom: THIS IS NOW IRRELEVANT
/noitem reload <username> [-q (quiet)]
Use the -q flag simply to reload the permissions without a message (good for automated reloads).
You must have the permission noitem.admin (which is not cached) to use this command.