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!
Comments
-
_ForgeUser6834367 Owner
-
_ForgeUser8494594 Author
-
View User Profile
-
Send Message
Posted Apr 24, 2013@eggmaster24
@welknair
There is a 1.5.1 development build, but it needs extensive testing.
-
View User Profile
-
Send Message
Posted Apr 24, 2013Any ETA on 1.5? I have a server desperately waiting for it.
-
View User Profile
-
Send Message
Posted Apr 23, 2013I apologize if I'm pestering, but I'm a little concerned by the lack of word about 1.5.1. Is it still coming, or should I begin looking for a new plugin? The prior ETA seems to have come and gone.
-
View User Profile
-
Send Message
Posted Apr 22, 2013Hoping 1.5.1 comes out soon! My RP server can't really open without it :P
-
View User Profile
-
Send Message
Posted Apr 21, 2013Where is the 1.5 version ? I search but i don't find it !
-
View User Profile
-
Send Message
Posted Apr 17, 2013@nala3
Splendid! My assumption had been that you did something along those lines, but I wanted to make sure. Thank you very much! My server eagerly awaits the release of the 1.5.1 version :D
-
View User Profile
-
Send Message
Posted Apr 17, 2013@nala3
adding to tools didn't work either :(
guess will need to chalk them both down as bugs?
-
View User Profile
-
Send Message
Posted Apr 17, 2013@nala3
Yep, Sorry Nala3 will wait for an update. Thanks for all your work. Also I would be happy to do some testing for you if you like. I have nothing but time on my hands at the moment, and my config will utilize everyone of your nodes.
-
View User Profile
-
Send Message
Posted Apr 17, 2013@welknair
Well, what I did with crafting, is I create a "fake" crafting table and put all the current things in the players crafting table into it and see what the result would be. So as long as the custom recipe plugin registers the recipes with Bukkit, it should work, even for custom recipes.
To the rest of you having problems;
NoItem 3.0.3 does not support MC 1.5.X! So yes, things will be broken since I use CB and NMS code.
@cheekyvimto
That is interesting, I have used the asterisk myself before and it worked fine :/
Q1) try adding (as silly as it sounds) 392 to the tools.yml list and then use the node "noitem.nouse.392"
Q2) Might just be a bug, but it shouldn't be happening >.>
-
View User Profile
-
Send Message
Posted Apr 17, 2013nocook doesn't seem to be working at all. Have tried using fish and 349. As well any other ID. nocook just won't work. Driving me crazy getting so close to making this all work the way it needs to.
noitem.nocook.349: true noitem.nocook.349.*: true noitem.nocook.fish: true
-
View User Profile
-
Send Message
Posted Apr 17, 2013Joining all of my current questions together to save jumping up and down the comments:
NoItem Version: 3.0.3 (we are using CB1.4.7)
Q1) What is the correct node to use to stop planting of crops on farmland?
currently using noitem.noplace.392 (for potato) and its not restricting it
Q2) using the following node, we can block the use of a tool, but only one that has full durability:
[i]- -noitem.nouse.268
changing it to:
- -noitem.nouse.268.*
EDIT: Update: if we block a tools by default, then use a negative to unblock once a player is part of a new group (we are mimicing classes)
-noitem.nouse.<toolid> allows the tool to be used as long as it does not have full durability.
however newly crafted tools at full durability are still not allowed to be used.
I tried adding, '.*' '.' '.all' '.-1' none of which worked, I also tried using .noitem.nouse.left.<toolid> and all suffixes still no luck.
Q3) Are you guys planning on re-adding custom block support, and if yes, do you have a timeframe on that?
After more testing, it's almost as if the .* addition is what is causing the issue, it happens across all perm nodes, as soon as you use .* it doesn't work.
EDIT2: After still more testing, just using a stonepickaxe, if I manually add the permissions for all 128 uses, the pickaxe works, so now I'm convinced it has something to do with the .*
Any help would be greatly appreciated.
-
View User Profile
-
Send Message
Posted Apr 16, 2013@nala3
v3.0.3
-
View User Profile
-
Send Message
Posted Apr 16, 2013@ ANTHONY
I figured out a way to do it. I'm using noitem to universally rule out players abilities to do things via permissions yml. Then am granting them back in by setting noitem to false in jobs config. Seems to be working. Just a lot of data entry now :(
-
View User Profile
-
Send Message
Posted Apr 16, 2013@rev1design
Ask phrstbrn to add a priority option to the custom permission nodes.
-
View User Profile
-
Send Message
Posted Apr 16, 2013@nala3
My main uncertainty is how restricting the crafting of such items would work. For example, if I were to make a special item which was a modified version of an Iron sword, with a random custom recipe, could I restrict the crafting of that item by restricting what players have the permission to craft iron swords?
-
View User Profile
-
Send Message
Posted Apr 16, 2013Hey I'm trying to use NoItem to restrict items withing Jobs using Job's custom permissions per class. And I think maybe because there's two classes one is overwriting the other IE hunter is loaded after woodcutter and hunter says deny so even though woodcutter has
noitem.nobreak.log: value: false level: 0
It's loaded after hunter which is set to true, and invalidates it. Is there anyway to fix this on the NoItem end with separate permissions or am I just screwed because of how jobs loads it's config?
-
View User Profile
-
Send Message
Posted Apr 16, 2013@welknair
As long as the items ID's are registered with bukkit, they should work fine.
@cheekyvimto
Version?
-
View User Profile
-
Send Message
Posted Apr 16, 2013Ran into our first issue, and hoping its something on our end.
using the following node, we can block the use of a tool, but only one that has full durability:
- -noitem.nouse.268
changing it to:
- -noitem.nouse.268.*
stop the permission from working full stop.
Are we doing something wrong here, if so can you please explain (with a sample node) how we can fix this so you can't use the tool regardless of its durability.
-
View User Profile
-
Send Message
Posted Apr 16, 2013Do you know how NoItem interacts with plugins like RPG Items, which add modified items with new recipes?
-
View User Profile
-
Send Message
Posted Apr 16, 2013@cheekyvimto
No, it doesn't. As I said, it is is only ready for simple testing.
@christianhood
I'll implement that myself since I need to actually create the command system first.
@cheekyvimto
No.