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 Dec 23, 2012Thanks. I'm just looking to restrict the use of certain block ID's.
-
View User Profile
-
Send Message
Posted Dec 23, 2012@tocheeba
If you know how to build maven projects, you can pull the development version from github and build it. It is for 1.4.6 and should work for the most part. I am still working on it though. NoUse however has not been added yet, and I am not sure if it will ever be added again. However, noitem.nointeract can prevent the interaction of the player with any block or entity (yes that means you can stop people from breeding animals and using levers, buttons, etc.!) The NoHold and NoHave, NoBrew, NoCraft, NoWear, and NoDrop features are also implemented so you can use those too. I might get around to setting up a Jenkins project later so you can just download the builds from there, but no promises since I am not at home currently.
-
View User Profile
-
Send Message
Posted Dec 23, 2012The NoItem.NoUse permissions don't work for us in 1.4.6. Any idea if it will be updated soon? We're running a contest and need to block certain items at the moment.
-
View User Profile
-
Send Message
Posted Dec 22, 2012@Mortifus7
Nahh, it is just a little re-factoring because I use CB and NMS methods.
-
View User Profile
-
Send Message
Posted Dec 22, 2012Hi Nala, just droppping a line to ask if the recent update to 1.4.6 looks to be incompatible with your current efforts?
-
View User Profile
-
Send Message
Posted Dec 19, 2012@nala3
meh, was just letting you and others know. Looking forward to the new release :) I'm getting ready to start beta testing of my server and NoItem will certainly be put to the test here ;)
-
View User Profile
-
Send Message
Posted Dec 18, 2012@lANTHONYl
Wouldn't doubt it.
-
View User Profile
-
Send Message
Posted Dec 17, 2012/noitem reload does not have any effect.
-
View User Profile
-
Send Message
Posted Dec 17, 2012@wonderdude73
Ehh the current version is riddled with bugs and half compatibility with MC 1.2.5, a new more stable version will be released soon.
-
View User Profile
-
Send Message
Posted Dec 17, 2012The plugin seems great.
However when i add the plugin only ops can craft items.?
-
View User Profile
-
Send Message
Posted Dec 15, 2012@lANTHONYl
I will likely add a permission later to stop tool usage. I already have the framework in place for a list containing tools, similar to the one nowear now uses. This is so that the permission will only work if the item being blocked is actually of the correct type.
For instance, if you put "noitem.nowear.20" it would not do anything because glass is not armor. This is so that if someone has the permission noitem.nowear.* for example, they will not blocked from shift clicking items around their inventory. The same will apply for tools being used, if it is not a tool, the permission won't have any affect.
As I said in my first comment "I am hoping to be done before Christmas for you all!", so hopefully before Dec. 25th I should have an initial version ready.
-
View User Profile
-
Send Message
Posted Dec 14, 2012@nala3
Easy enough to find/replace all of the "all" instances for "*", so no problem there. I'm curious about the removal of nouse and the addition of nointeract though... I suppose weapon/tool usage will be managed by nohave/nohold, and that nointeract will be for blocks and entities only. Could be good.
Will these changes take place in your next version, and do you have a tentative time line for its release?
Also, it would be nice to have a review of the list i put together. Make sure i'm giving people the correct information :)
-
View User Profile
-
Send Message
Posted Dec 14, 2012@lANTHONYl
No, the permissions are still the same, except that the * value is now supported so .all is no longer used. The nouse permission is now nointeract and is limited to, well the block you are interacting with. So noitem.nointeract.lever.* would not allow you to right or left click a lever, this should also work on entities as well. (e.g. noitem.nointeract.cow)
EDIT: Also, I am not sure yet, but I don't think I will be supporting Tekkit custom blocks anymore, however Spout custom blocks I will for sure.
-
View User Profile
-
Send Message
Posted Dec 14, 2012@nala3
This doesn't mean that all the perms i just wrote will be useless does it? Cause that would kinda suck...
-
View User Profile
-
Send Message
Posted Dec 14, 2012Just an update for you guys, I am currently re-writing the entire plugin. But lately I have not had too much time to work on it between school and my job. However progress is being made, the entire plugin framework is done, I am just registering all the events and writing the logic to handle them. I am hoping to be done before christmas for you all!
-
View User Profile
-
Send Message
Posted Dec 14, 2012Well i think i'm finished with the list. I opened a forum thread so that people have a place to comment if i missed something. The link to the doc is there.
I hope this helps the community and helps nala3 with reducing support questions. :)
-
View User Profile
-
Send Message
Posted Dec 13, 2012@Mangerman
Well, i think i have them all... there are 75 possible potion formulas that need nodes by my count. The all inclusive permission list is almost complete now. Just need to do the noitem.nodrink and noitem.noopen permissions and review the nohave and nohold perms and it'll be done... till the next update lol.
-
View User Profile
-
Send Message
Posted Dec 13, 2012The nobrew permissions are pretty straightforward, but tedious to look up: - noitem.nobrew.<basepotion>.<ingredient>
- noitem.nobrew.16.353 will block the product of an Akward Potion (16) + Sugar (353), which is a Potion of Swiftness.
-
View User Profile
-
Send Message
Posted Dec 8, 2012Ah, I was not wrong. Found the nodrink.
189 possible enchants all listed... still working on the permission list if anyone wants/cares to assist :)
And why not just use the enums? Have me running all over your code to try and figure out what noitem expects... Really looking forward to the nobrew perms *shudders*
*EDIT*
189 enchants... and now books can be enchanted... and there's the /enchant command
And writing a permission node for all the possible potion formulas (cause there are more than one for each final potion) plus you have to do the same for splash potions... the list is so ridiculous.
Another question: What do the nodrink perms expect as values. I really don't feel like crawling your code anymore than i have. Would be very nice if it is the standard enum like 373:8257
-
View User Profile
-
Send Message
Posted Dec 8, 2012I remember seeing somewhere that there are 2 new permissions: noopen and nodrink. I've found reference to noopen, but not nodrink. Am i wrong?