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!
I was trying to stop some players from opening chests so I tried to add this permission "noitem.nointeract.right.54" and this just in case "noitem.action.open.54" and it still did not work. Any idea why? D:
@lANTHONYl
Yeah, I re-implemented the permissions as whitelist mode, however I don't think its working correctly currently. So please be sure to let me know of any problems!
This update took so long mostly due to brewing being a pain in the butt to stop, but it is definitely an improvement over that last version :P
@nala3
Good god man, you've come a long way. Well done!
Looks like the rest of us have some work ahead of us too. All them permissions... :)
P.S. Please check the Wiki, there are a lot of changes, specifically to permissions formats! Please, please, PLEASE! Read there before you come and ask for help!
Okay ya'll, I'm still alive!
Just pushed a rather large commit to the new NoItem 4.X repository. You can find the new build on my development builds link up above in the description!
Notable things are all in the commit notes, so read them if your curious. https://github.com/nala3/Noitem4/commit/9f66435b6c64d57b8dabf5a78539bb94d99dd7c2
This version is ONLY compatible with CB 1.7.8
Thank you all for your support.
does there is a permissions like this? - noitem.bypass.<item_id> If player has that permission, hi can bypass this protection. Sorry for my bad English :)
just wondering, does anyone know if this is compatiable with 1.5.2? and if so what version? I use : 3.0 for my 1.6.4 server.
I've tired the same build for 1.5.2 but nothing works. can I use the one for 1.4.7? I noticed there were reports of heavy server lag caused by the pluing for the older versions of this...
- noitem.action.cook.PORK
works, when you put coal first and then with right mouse button the pork.
Its cooking without problems... :/
But i want to block cooking GRILLED_PORK!
Pls help.
@UncleChester14
Yeah the way the 3.x series handled interaction required you to use the bukkit enum for entities. I feel your pain regarding how tedious it is to create a noitem perm for every possible item and such which is why i created this forum thread and the linked google doc spreadsheet. You'll notice that on the spreadsheet i have the entity interact permissions. Idk how your modpack is handling item/entity IDs or enums, but maybe this info will help.
@lANTHONYl
Sorry, I forgot to specifiy that I was using the dev. build. 4.0.0-SNAPSHOT. There is no whitelisting in the config options anymore. I need that build specifically since it's built to better handle entity interaction. I have compiled a modpack that is as tightly based on GTA as I could possibly come up with. The major hangup is that although everything is whitelisted and I am allowing interaction with the -noitem.nointeract.* perm. The previous versions of the plugin do not handle entity interaction to allow the use of the cars. Being that it's based off of a game in which cars are a huge part, this is a pretty serious hangup.
@UncleChester14
I've been using whitelist mode since forever.
@FlOppythp
Really? You're going to spend your time wasting mine when you could have found your own answer already? What am I supposed to do, go research your specific permissions plugin and learn how to use it so that i can teach you how to use it? You've gotta be kidding me.
Is whitelisting still possible? This plugin is amazing for RPG servers but to manually insert items when you need 90% of the items banned, uncraftable, unusable in their own specific way whitelist mode is the only way this is practical. Is it possible to just add the permsaswhitelist line from the 3.X config and it work?
@FlOppythp
Well, i did not make NoItem. All credit goes to nala3. I don't think it's entirely necessary to have NoItem be world specific since many permissions plugins have multi-world capabilities.
@FlOppythp
You will have to consult your permissions plugin documentation as they are all different. Different worlds can have different permissions. It's entirely dependent on your permissions plugin.
I want to restrict mods items, and reserve it for VIP players, is it possible?
@FlOppythp
You would utilize your multi-world capable permissions plugin.
Is it work with mods items?
The same that comment @alizarcivire, but with the 3.1.0 dev version and latest spigot dev build.
http://pastebin.com/hpE77NCC
@SomePersonHere
That's the intended usage. Just use a permissions plugin that has the functionality you need.
Just curious,
Can items be restricted per perm? So say I give rank 'Staff' a perm such as noitem.nopickup.cobblestone they won't be able to pick up cobblestone but everyone else will be able to?
Or even the opposite, give them the perm so that they're the only ones that can pick it up?