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!
@nala3
What do you mean New permissions?
@milkymilkway
Okay, the latest build fixes that NPE being thrown a lot. But it does use a new permissions handler. So some things could not work correctly. I tested holding, picking up and placement. However I did not test the rest. So if you decide to use it, you should test it out on another server first. And if there are any problems just tell me what isn't working (through PM or the bug reports you dread so much) and I will attempt to fix it.
@milkymilkway
it shouldn't. If it does just send me a PM and I'll try to get a temporary fix for ya
@nala3
but wont this crash my server? If someone spams it because my server has crashed from an overload of errors.
@milkymilkway
okay, well by pastie, I meant copy the text of the error out of your server.log :P but w/e. Yeah that's 1/2 implemented feature for supporting custom furnaces / workbenches / etc..
@nala3
Yeah Sure Ill give a picture
@milkymilkway
can you give me a pastie of the error?
@nala3
Im getting errors in console. But it works!
@nala3
Awesome! Thanks man!
@jman10000159
@milkymilkway
Okay, as I suspected, there were a couple more problems with placement and breaking checking. Should be fixed now in build #117.
@milkymilkway
@jman10000159
Okay, the problem may be in the placement permission checking method. I fixed an issue with the holding one. Let me check on that and I'll get back to you
NALA! What permission node would i use if i wanted to block 128 but not 128:1... ive tried a few different ones... block from being placed. i use PEX
@nala3
Ok. I added the permission 'noitem.noplace.128' Because I want them to be able to place 128:1. But it still blocks both. And I am using your Dev build 2.0.6 I believe thats the latest dev.
@milkymilkway
He said it didn't work, but I don't have the problem anymore and he did not reply. If you want to know if it is fixed, than test it out. Now, if something is wrong, please tell me the exact steps I can use to reproduce the problem. Because in my testing "noitem.nohold.128.1" does not block "noitem.nohold.128" and vice versa.
@nala3
No, I saw you say that. But then someone complained and said it didnt work. So I was wandering if you fixed it? Thats all. Are you bi-Polar? lol You get mad to easily. But 128 and 128:1 doesnt work for me either. It still blocks both. Maybe you should add something in the config file that directly targets this issue. Because everything else is fine its just these 2 blocks. And I dont want to fight any more. Coders should be friends because there are very few on this earth. So I apologize man. Please forgive me. And please fix this issue. It would help out a lot of tekkit servers.
@milkymilkway
"You programmed a plugin that doesnt allow someone to craft or hold something...REAL TALENTED!"
If it is so simple why don't you do it? Not to mention, it does much more than that. It's not my fault if that is all you use it for.
"No one had a plugin for shouting so I thought I would do it."
Ohh really? Besides the /me command, there is: http://dev.bukkit.org/server-mods/shouter/ http://dev.bukkit.org/server-mods/easyshout/ http://dev.bukkit.org/server-mods/i-shout/ http://dev.bukkit.org/server-mods/shout/ http://dev.bukkit.org/server-mods/shoutout/ Not to mention pretty much every other command suite in existence
"And did you fix the 181 and 181:1 issue with 2.0.6?"
You really don't read do you?
"@milkymilkway
@jman10000159
This issue is now fixed since development build #114"
Also, I would like to point out that your plugin is in violation of the GPLv2 license it uses because you did not release the source.
@nala3
Oh wow! You programmed a plugin that doesnt allow someone to craft or hold something...REAL TALENTED! Bukkit is the easiest API out there. Making plugins for Bukkit is like Arts And Crafts. It just got boring. No one had a plugin for shouting so I thought I would do it. Theres nothing else to program. And did you fix the 181 and 181:1 issue with 2.0.6?
@jman10000159
What permission node are you using? It could be there is another of the same mistake somewhere.
It still isnt working for me :/ could u gimme the exact permission node if i wanted to block 128 but not 128.1