NoItem
NoItem v3.1.0 - DERP.
What does it do?
NoItem aims to allow server admins to restrict almost any aspect of players actions via permissions. Things such as placing and breaking blocks, interacting with levers and buttons, opening chests and furnaces, even breeding animals can be controlled! There are of course other things that can be restricted as well. For a complete list, check the wiki!
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Downloads:
http://dev.bukkit.org/server-mods/noitem/files/
Beta/Development builds may contain bug fixes, but also may contain new bugs
So before you report a bug, check and see if a new build has fixed it!
Feature List
NoItem can restrict the following:
- Crafting certain items
- Holding certain items
- Having certain items
- Brewing certain potions
- Cooking certain items
- Picking up certain items
- Dropping certain items
- Placing certain blocks
- Breaking certain blocks
- Wearing certain armors
- Interacting with certain items / entities in general
- Left clicking certain items / entities
- Right clicking certain items / entities
- Using certain tools. (right click / left click / in general)
Commands
| Command | Permission | Description |
|---|---|---|
| /noitem | noitem.admin | Prints current NoItem version |
| /noitem reload | noitem.command.reload | Reloads the configuration |
| /noitem debug toggle | noitem.command.debug.toggle | Toggle debugging |
| /noitem debug dump | noitem.command.debug.dump | Write debug file to the servers base directory |
Videos
FAQ
Q: How do I...
A: Check the wiki! If you are still confused and have tried to figure it out, ask in the comments.
Q: There is an error in the console or something is not working as expected
A: Submit a bug report to github! (Link above) DO NOT post the error in the comments section! Also be sure to include the error in your report.
This plugin utilises Hidendra's plugin metrics system, which means that the following information is collected and sent to mcstats.org:
- A unique identifier
- The server's version of Java
- Whether the server is in offline or online mode
- The plugin's version
- The server's version
- The OS version/name and architecture
- The core count for the CPU
- The number of players online
- The Metrics version
Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true.
NoItem 4.X - It's Aliiiveeee!
NoItem 4.X is currently in development and is not finished. There will be bugs, there will be a lack of certain features, there will be questions.
Here is the link to the information page: https://github.com/nala3/Noitem4/wiki
Here is the link to the development builds: http://ci.worldoftomorrow.net/ (Also on the wiki page)
Submit bug reports to the github bug tracker.
Currently known issues are:
- None - Please report any found!
Currently Implemented Features (also their permissions)
- break
- place
- craft
- open
- cook
- pickup
- drop
- hold
- interact.object
- interact.entity
- use - is buggy and needs refinement
Permissions format:
- noitem.action.<action>.<object>[.secondaryValue]
- noitem.object.<object>[.secondaryValue].<action>
- Asterisk values are supported for specific actions and objects. not for all actions or objects at once. (e.g. noitem.action.* is not supported, but noitem.action.break.* is)
I am open to suggestions on what other action to implement on top of the ones I am currently working on.
A wild
button appears!
You use "CLICK". Its super effective!
-
View User Profile
-
Send Message
Posted Feb 7, 2013@lANTHONYl
Pretty much :) It just modularizes the features into drop-in classes. This means that other people can add new functions to NoItem just by writing a single class and putting into the drop-in folder! Of course, this is just more of a side project atm, I am still working on the normal version of NoItem :)
-
View User Profile
-
Send Message
Posted Feb 6, 2013@nala3 I'll be sure to hop on at some point tonight, trying to finish the tier2 professions here.
A *new* version of NoItem!?!
lol. I'm assuming that the nodes are the same, just that the checks can be turned off in the config.
-
View User Profile
-
Send Message
Posted Feb 6, 2013@lANTHONYl
You can try again if you like, I fiddled with it a bit but didn't actually test :P If you want to post a permissions file you can.
In other news, I've started work on a completely modular version of NoItem
-
View User Profile
-
Send Message
Posted Feb 6, 2013@nala3
I'm fine with waiting on detailed anvil control, was just wondering if you had given any thought to the implementation.
Side note:
As a Blacksmith on the NoItem test server I can't place/break anything. Kinda makes it difficult to set up a workshop ;)
I'd be happy to share a config with you that might be appropriate.
-
View User Profile
-
Send Message
Posted Feb 6, 2013@lANTHONYl
blocking it? not right now, I want to get everything else working first :P
-
View User Profile
-
Send Message
Posted Feb 5, 2013@nala3
Any thoughts on the anvil?
-
View User Profile
-
Send Message
Posted Feb 4, 2013@Glacksy
Which CB version are you using?
If you're using CB 1.4.7 you can test dev build 240. An additional null check was implemented.
@Q2Lummox
You could noitem.nohold.351
nointeract is for the block you are clicking on, not the item in hand
nouse. only refers to the items listed in tools.yml. You could put 351 in there under the Misc: section
-
View User Profile
-
Send Message
Posted Feb 3, 2013getting this error: http://pastebin.com/4rDeQn7q can anyone explain it ? :=)
-
View User Profile
-
Send Message
Posted Feb 1, 2013How I can stop the use of bonemeal to grow things?.
I tried with:
- noitem.noiteract.351.*
- noitem.nouse.351.*
- noitem.noplace.351.*
- noitem.nointeract.right.351.*
- noitem.nouse.right.351.*
I just want to disable the right click function of bonemeal.
And I give this spam error in console:
04:07:42 CONSOLE: [SEVERE] Could not pass event PlayerInteractEvent to NoItem v3.0.3-SNAPSHOT-239
04:07:42 CONSOLE: [SEVERE] Could not pass event PlayerPickupItemEvent to NoItem v3.0.3-SNAPSHOT-239
And much more...
-
View User Profile
-
Send Message
Posted Jan 31, 2013@RustyDagger
Yea, recently we configured bperms to the same specifications as PEX and although we had great success in some aspects we hit a new issue, Inheritance. We have used NO-ITEM to work as a tier system. E.G. Chef_Novice, Chef_Expert, Chef_Master. We realise this is to do with tracks, since there are 9+ tracks to arrange it's come with its difficulties. We are still getting that to work, PEX is just a personal preference since it's pretty slick to operate from a user perspective.
-
View User Profile
-
Send Message
Posted Jan 30, 2013@RustyDagger
I agree, but in PM he told me that they did test with bPerms also. And with a 1500+ line perm file... changing is always a PITA... regardless of how good you're find and replace skills are ;)
-
View User Profile
-
Send Message
Posted Jan 30, 2013@imjoebaker @wfuller1
Humor me and change your permissions manager from pex and see if you still have the same issue if your any decent at running a server changing to say Bpermissions from PEX should only take 20 min on the test server.
Why am i saying this? PEX is known for completly screwing with bukkits permissions system actively injecting its own code into bukkit to override what bukkit does It has broken things before and may well be causing this.
Personaly on my main server I found that PEX made lag when i had a bunch of plugins working with it. I moved to Bpermissions Been a ton more stable since but yes its global files suck ass.
-
View User Profile
-
Send Message
Posted Jan 30, 2013@nala3 @wfuller
Myself and Wfuller have tried multiple things as stated below. Just now we double checked our bukkit build and made sure it was 1.4.7 since then there have been no errors. However, the plugin does nothing.
On our test server though it works perfectly although, that's not to say we have had errors. One fix we found was to delete our player.bat although that did not work on our actual server.
We have been trying to fix this for a few months now and we kindly ask you can speak with us briefly in skype or on Teamspeak to find a solution. My username on Skype is "imjoebaker"
-
View User Profile
-
Send Message
Posted Jan 30, 2013@nala3
I updated to the newest version and straight away the errors appear again: http://pastebin.com/VjdL44TU
-
View User Profile
-
Send Message
Posted Jan 29, 2013@wfuller1
Make sure you are updated to the latest dev build.
-
View User Profile
-
Send Message
Posted Jan 29, 2013Hi Nala,
Apologies for hopping back in here with the problems again! We have tried using different permission plugins, disabling every other plugin but noitem, tried different bukkit versions, tried different noitem versions...and every single time it comes up with these errors, and the plugin just doesn't have any effect at all in game: http://pastebin.com/CdGSg85L
I have had a thought though... due to running a multiplay server, our craftbukkit jar has had to be renamed to minecraft_server.jar. Updating to a usual craftbukkit_R879etcetcetc.jar file will not load on our multiplay server.
I noticed that part of the error code was to do with craftbukkit so could this be something to do with the errors we are having?
Also, we have tried the exact same configs with pex, essentials and noitem on another test server and it works fine! So it has to be something to do with how our server works :/.
Thanks in advance for your help.
-
View User Profile
-
Send Message
Posted Jan 28, 2013I'm using 2.0.5 for a Tekkit Classic 3.1.2 server and it works really well, a nice easy way to block / ban items :)
@domentia1
I found that with Tekkit Classic & PEX using .* or .all worked perfectly, BUT it caused multiple items or permissions on one line not to work so for example instead of:
- noitem.(nohold|nocraft|nouse).(27530.*|27533.*)
You'd need to use:
- noitem.nohold.x27530 - noitem.nocraft.x27530 - noitem.nouse.x27530 - noitem.nohold.x27533.* - noitem.nocraft.x27533.* - noitem.nouse.x27533.*
It's not as tidy but works perfectly and doesn't really take too long to type out if you copy and paste everything except the numbers :)
-
View User Profile
-
Send Message
Posted Jan 26, 2013@nala3
I fixed it, it would seem putting the '.all' or '.*' would just negate it from being banned instead I just used the item ID as is for example the cannon:
'x26524' would work but 'x26524.all' or 'x26524.*' wouldn't!
I'm so dumb.
-
View User Profile
-
Send Message
Posted Jan 25, 2013@domentia1
Well, it honestly does depend on the Tekkit version. The old 2.0.X line hooked directly into Tekkit and Craftbukkit, so it would break with updates. But other features such as simple item blocking should still work. (hopefully)
-
View User Profile
-
Send Message
Posted Jan 25, 2013@domentia1
NoItem versions prior to 3.0 use .all instead of .*