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 Sep 10, 2012Something like "- noitem.nodrop.214" bans the sub ids like 214:1 and 214:2. Anyway to prevent this? (ID 214 is a Tekkit item)
Also negating a permission node with permissionsex doesn't want to work for me. Is this a known flaw or did I do something wrong?
negation looks like this: "- -noitem.nodrop.214"
Great mod btw.
-
View User Profile
-
Send Message
Posted Sep 10, 2012@Sarge22234
Probably damage values like you said.
-
View User Profile
-
Send Message
Posted Sep 9, 2012I found some weird error. One specific player can wear 90% of the stuff the should be restricted.... He should be able to only wear leather he can wear anything but diamond chest legs and boots.
Actualy through further thought is this perhaps the wearing damaged items problem? I'll try the .* at the end. If that doesn't work I'll make a ticket.
-
View User Profile
-
Send Message
Posted Sep 9, 2012Maybe I'm mistaken, but if i don't want my "Group 1" list to access an item, we'll say item 321, i'd give group 1 the following:
noitem.nopickup.321 noitem.nodrop.321 noitem.noplace.321 noitem.nobreak.321 noitem.nohold.321 noitem.nowear.321 noitem.nocraft.321 noitem.nobrew.321 noitem.nocook.321 noitem.nouse.321
Now if i wanted Group 2 to be able to access use this item, I could negate the perms (the no-use is inhereited). Am I correct in saying that a player in Group 2 who can access the item can put an item into a chest, which a player in Group 1 can get out of the chest? They can't do anything with the item, but they can get it out of the chest, right?
-
View User Profile
-
Send Message
Posted Sep 8, 2012Just a heads up, in the permissions section it says noitem.nobew instead of noitem.nobrew
-
View User Profile
-
Send Message
Posted Sep 8, 2012@nala3
ok i have set these nodes..
- noitem.noopen.x27526.1 - noitem.nohold.x27526.1
and they can still open and use the philo stone any idea's?
-
View User Profile
-
Send Message
Posted Sep 8, 2012@Craig_1690
That is not what that node is for. Use noopen to prevent them from opening, and nohold to prevent them from holding it.
-
View User Profile
-
Send Message
Posted Sep 8, 2012can someone help me? i am trying to disable the opening of the crafting bench with a philosopher stone and people can still do it i have this permissions node - noitem.nouse.x27526.1 and they can still craft and hold it.. please help
-
View User Profile
-
Send Message
Posted Sep 7, 2012@lonjonsilver
Okay, that good! Is blocking the opening of the philosopher stone working now?
-
View User Profile
-
Send Message
Posted Sep 6, 2012@nala3
it seemed to work fine. I assumed that it was the Beta3 but still was called beta2. I'll download the new one when it's up but the one posted still worked.
-
View User Profile
-
Send Message
Posted Sep 5, 2012@lonjonsilver
Sorry, but if you downloaded the beta 3 file from here, it was the wrong one xD I clicked on the wrong file to upload like an idiot! The correct one should be approved soon.
-
View User Profile
-
Send Message
Posted Sep 5, 2012@lonjonsilver
Well, hopefully I can fix that in the final release!
-
View User Profile
-
Send Message
Posted Sep 5, 2012Thank you the 2.0.6Beta3 Worked like a charm! I tested it and it is preventing crafting on everything except the Philosopher's Stone. Which is unfortunate but I can live with. Thank you for the release =)
-
View User Profile
-
Send Message
Posted Sep 3, 2012@misterjpc819
I would like to help but I need some basic information to help!
-
View User Profile
-
Send Message
Posted Sep 3, 2012So, I'm confused. I put in the permissions correctly according to everything I have read but still nothing is blocked...what could I be doing wrong?
-
View User Profile
-
Send Message
Posted Sep 3, 2012@kuba1638
add .all to the end of the node. Normal furnaces and chest use data to determine the direction they face.
@foersk
.all works, I know it works because I use it when I test things all the time. Hell, looking at the code it works very simply. If you don't think it works, turn on debugging and look at the permission nodes the plugin checks! In short, either your doing something wrong or you need to update the plugin.
@Tetdoss
There was a bug in an old version that did this. Now, the configuration simple replaces missing lines unless of course the configuration is broken/unreadable in which case the entire thing is remade.
-
View User Profile
-
Send Message
Posted Sep 3, 2012Is it normal if the config file regenerate itself ? I'm tired to reconfigure the config file before each server start ^^
Thanks ;)
-
View User Profile
-
Send Message
Posted Sep 3, 2012ok i gave everyone the perission noitem.nocraft.27555 which blacklists darkmatter hammers but i have people still seem to make items after i gave them the node that shouldnt be able to craft them. Please help.
Its weird i blacklisted mk2/mk3 colls and people cant make them, but it seem that they are able to make anything that isnt a block - ex mining lazer, dm hammer, ect and also .all i dont believe works for me
-
View User Profile
-
Send Message
Posted Sep 3, 2012I can not block the furnace or chest. - noitem.noplace.54 - noitem.nobreak.54
-
View User Profile
-
Send Message
Posted Sep 2, 2012@Blank7201
Okay, the reason things are not working properly is because I was trying my very best not to have to hook into any mods to do this. However I literally just pushed a new version a few minutes ago that works for at least the project table (with the custom block configured of course). So progress is being made!
You can keep tabs on it if you like by either watching the github repo (link above) or checking the development builds every once and awhile! (also above).
As for the lack of documentation, I realize this is an issue and will fix it as soon as I get everything working properly, because if I do it now, the documentation can become out of date very quickly. For instance, custom block configurations are now stored in a separate file in the latest dev builds, which is not the case for the second beta release.
@EpicKetchup
Interesting, what version are you using? because adding .all has never been an issue in my testing :P