Use this plugin to ban items and blocks for Bukkit, Tekkit, and FTB servers using the Bukkit API. ItemRestrict removes banned items from the world and player inventories. It is easy to configure, can be applied retroactively, and automatically removes the items. It requires no permissions plugin unless exceptions are need for certain players. It is compatible with 1.2.5, 1.3.2, 1.4.7, 1.5.2, 1.6.4.

Because every story that starts with "We decided to make a change..." shouldn't end with " we had to reset the world."


Copy the .jar file into your plugins folder to install the plugin. Then restart the server or use a plugin manager to load the plugin.


Use the command "/ires reload" to reload the config file.

CommandPermission NodeDescription
/ires reloaditemrestrict.reloadReload the config
/ires ban <banType> <id-datavalue>itemrestrict.banAdd item to the ban list
/ires unban <banType> <id-datavalue>itemrestrict.banRemove item from the ban list


There are 4 major sections in the cofig file (config.yml). Enabled worlds are listed under Worlds. World Ban scanner settings is under Scanner. Ban settings are under Bans. Notification settings to the player are under Messages. A default config for Tekkit was generously created by BigScary.

Worlds listed in the Worlds section are enabled worlds which will be checked by the plugin. You can name normal worlds, dimensions, and mystcraft worlds by using the world's folder name. Add the case sensitive world called "All" to bypass the world check.

The Scanner settings indicate the percentage chance (from 0 to 1) that it scans a loaded player or a loaded chunk.

You can specify the items you wish to ban under the Bans section. Take a look at the different types of bans below. An entry with only the item id (32) will specify ALL wool (all datavalues). An entry with the item id and datavalue separated by a dash (32-2) specifies MAGENTA wool (datavalue 2). Some items have a different values in your inventory as opposed to ones place in the world (eg. a door item in the inventory versus a placed door in the world). A full list of Block IDs will help you add banned items.

The label gives the item a name when notifying the player. The reason provides the reason of why the item was banned for them. You can use colour with both the label and the reason by using the escape character "&" and a hex number corresponding to the minecraft colour.


Making Ban Exceptions

You can make individual ban exceptions to give some players to generally banned items through permission nodes. A player who has /op automatically ignores bans. Specifying the item ID without the datavalue means all data values (-*). Here are various examples, which should help you understand without further explanation.

- ItemRestrict.bypass.usage.35
- ItemRestrict.bypass.ownership.35-6

You can't prevent a specific player's placed block from being removed from the world as this plugin does not track who owns placed blocks in the world.

Types of Bans

Usage Bans

This ban prevents players from using an item, which means left-click or right-click while the item is in-hand. This ban also prevents players from right clicking a block specified by this ban. This ban also prevents a player from building a block in the world. This works well for items like the Mining Laser, but won't stop players from using items which benefit from passive use (eg. modded armors, Talisman of Repair, etc.). You will need an ownership ban to prevent players from getting those items at all. A player that already has an item which is later placement-banned can still trade it with another player or break it down into energy (EE mod) to get some value out of it.

It's not possible for any plugin to prevent a player from using an item when it is activated by a keystroke (eg. R, G, C, etc.), which are common especially for Equivalent Exchange items. This is why many EE items are on the default ownership bans list even though their functions are not all really ban-worthy.

It is recommend to place most or all usage ban items to your ownership ban list. This will prevent your players from unknowingly spending their resources to craft a block which they then can't place in the world like they planned leading to them feeling cheated and likely complaining. The only exception you might make to this rule is for an item which can't be placed, but is still useful because it's an ingredient in another recipe for an item you haven't banned.

Ownership Bans

This ban prevents player from picking up an item from the ground or from a container (eg. a chest). If a player doesn't have permission to own an item, they won't be able to craft it. The contraband scanner will search each player's inventory for ownership-banned items and actually remove them without warning, notification, or compensation.

This ban also prevents players from crafting an item. When the player tries to craft the item, they get a message that they can't. This is the most player-friendly approach to preventing players from getting banned items. Forge mods don't always hook into Bukkit, meaning its possible for players to get banned items through some automatic or non-crafting approach (eg. alchemy). When you crafting-ban an item, test for workarounds, which may lead you to ban additional items to prevent those workarounds.

World Bans

This ban will retroactively remove the placed block from the world through the Asynchronous World Scanner (AWS). This is great if you need to ban an item, but also know it's in the world (eg. energy collectors and world anchors). This will help clean up newly-banned items without having to search your entire world for them. There are exceptions to this removal as the scanner can't determine who owns the block.


This plugin uses the idea from BigScary's TekkitCustomizer. However all components in his code have been replaced with high performing and simple implementations. As a server administrator, I care about performance as much as you. Thus no code is actually used from the TekkitCustomizer plugin and the source code can be found here.

The default ban list is made for Classic Tekkit based on hands on testing done by BigScary. Before deciding to remove items from this list, be sure to read the reasons for default bans to understand why it was originally removed. If you are running FTB, Tekkit Lite, or other mod packs, do your own research for what you want banned and change the config file accordingly.

Save yourself some time! Check our Frequently Asked Questions page for the answer to your question. If you found a bug, make a ticket and include your config file.


Thank you to piritacraft for testing each ticketed issue.

Thank you to our contributers that have helped contribute to this project:

Thank you to our supporters that have generously donated to ItemRestrict:

  • Thundercoyote


Unlike other players who have a choice to play the game, my commitment to development and administration usually means I cannot and I'm fine with that choice. A lot of my free time is actually spent designing, developing, testing, and fixing plugins like this one to make Minecraft more enjoyful for all players. If you like this plugin, please consider sending me a donation by clicking the button below :) Thanks!


You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of ria80 ria80 Oct 18, 2013 at 02:19 UTC - 0 likes

    hi, possible add colors supports for reasons ban item plz ?

  • Avatar of krisdestruction krisdestruction Oct 17, 2013 at 01:08 UTC - 0 likes

    @brienmg: Go

    Yup, just add it in the ownership bans and no players will be able to carry a "God Apple" on them. Any they pick up or carry in their inventory will be removed. Assuming that you need to carry it with you to buy/sell the apple, it should effectively remove all those God Apples from your server.

    Last edited Oct 17, 2013 by krisdestruction

  • Avatar of brienmg brienmg Oct 16, 2013 at 21:20 UTC - 0 likes

    Could I use this to basically delete God Apples from my server? My old donator kits that another admin made had 64 god apples daily.

    Needless to say my economy is very damaged by this, I want to be able to wipe every god apple off the server and start over. Could I use this to effectively do that?

  • Avatar of krisdestruction krisdestruction Oct 14, 2013 at 01:34 UTC - 0 likes

    I will release an awesome update after 1000 downloads! Awesomeness is subjective :3

    Last edited Oct 14, 2013 by krisdestruction
  • Avatar of piritacraft piritacraft Oct 10, 2013 at 21:35 UTC - 0 likes

    @Eyeball114: Go

    This is not a bug. If you want 451:0 use "451-0"

  • Avatar of Eyeball114 Eyeball114 Oct 10, 2013 at 20:44 UTC - 0 likes

    @krisdestruction: Go

    One issue my players are having: World anchors are banned. ID is 451 451:2 and 452:10 I have set in the config:

    But now anything in game with 451, which is 5 or 6 railcraft mod items, are all banned.

  • Avatar of krisdestruction krisdestruction Oct 10, 2013 at 07:13 UTC - 0 likes

    @Eyeball114: Go

    I hope it stays easy to configure and fast! :)

  • Avatar of Eyeball114 Eyeball114 Oct 10, 2013 at 06:47 UTC - 0 likes

    @krisdestruction: Go

    Awesome! I went ahead and put this on my FTB Unleashed server Since I started my community 2 years ago I have used every major item restricting/banning plugin out there. This has been the easiest to configure and the best one I have ever used. As long as you keep this updated, and as long as their are items to ban!, I will be using this plugin!

  • Avatar of krisdestruction krisdestruction Oct 10, 2013 at 05:46 UTC - 1 like

    @Eyeball114: Go

    Ownership Claims. I will be separating ownership claims from crafting claims soon.

  • Avatar of Eyeball114 Eyeball114 Oct 10, 2013 at 03:12 UTC - 0 likes

    Great plugin so far. Im testing it out on my unleashed test server before taking it live. One question. Can you prevent the crafting of items? In testing I could craft it, but not place it. Is their an option to remove banned items from an inventory on a timer?

    Last edited Oct 10, 2013 by Eyeball114

What permissions plugin do you use while using ItemRestrict?

  1. Choice:

  1. Results
  2. 1 comment


Date created
Sep 22, 2013
Last update
Oct 07, 2013
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Recent files