Understanding the ItemRestrict Plugin for Bukkit, Tekkit, and FTB Servers
Running a modded Minecraft server is an exercise in controlled chaos. You invite players into a world packed with hundreds of new blocks, tools, and mechanics, and sooner or later someone discovers an item that breaks the economy, lags the server, or simply ruins the fun for everyone else. The classic admin horror story always begins with “We decided to make a change…” and ends with “…so we had to reset the world.” That is exactly the nightmare the ItemRestrict plugin is designed to prevent.
Why Server Admins Need ItemRestrict
ItemRestrict is a powerful Bukkit plugin that gives you surgical control over which items and blocks can exist on your server. It works across classic Bukkit setups, Tekkit, and FTB modpacks, all through the familiar Bukkit API. Rather than relying on a dozen fragmented rules or hoping players read a forum post, this plugin actively removes banned items from the world and player inventories—retroactively if needed. The moment you add a problematic block to the ban list, the scanner can purge every placed instance from loaded chunks, so you never have to reset a map just because of one overpowered mod component.
Key Features and Ban Types
The plugin’s strength lies in its three distinct ban categories, each targeting a different stage of item interaction. You can mix and match them to build a custom safety net that fits your server’s philosophy.
Usage Bans
A usage ban stops players from actively using an item in their hand. If someone tries to left-click, right-click, or place a banned block, the action is blocked. This is perfect for disabling tools like the Mining Laser without removing them from the game entirely. However, it won’t prevent passive benefits from modded armors or talismans, and keystroke-activated items (common in Equivalent Exchange) can slip through. For that reason, many admins pair usage bans with ownership bans to close loopholes. A smart practice is to add any usage-banned item to the ownership list as well, so players don’t waste resources crafting something they can never place.
Ownership Bans
An ownership ban is the most thorough defense. It prevents players from picking up a banned item from the ground or a container, and it blocks crafting outright. When a player tries to craft a restricted item, they receive a clear message instead of a useless result. The contraband scanner then silently removes any ownership-banned items from inventories—no warnings, no compensation, just a clean sweep. Because Forge mods don’t always hook into Bukkit perfectly, some workarounds exist (like alchemy-based creation), so you may need to test and ban additional ingredients to seal every path.
World Bans
World bans leverage the Asynchronous World Scanner to retroactively delete placed blocks from the environment. This is invaluable when you realize a block like an energy collector or world anchor is already littering the landscape. The scanner runs with a configurable chance per chunk or player load, so it won’t tank your server’s TPS. One limitation: the plugin doesn’t track who placed a block, so you can’t exempt a specific player’s builds from world removal.
Configuration and Permissions
ItemRestrict is refreshingly straightforward to set up. After dropping the .jar file into your plugins folder and restarting the server (or loading it via a plugin manager), you control everything through a single config.yml. The file is divided into four clear sections: Worlds, Scanner, Bans, and Messages. You list enabled worlds by their folder name—including dimensions and Mystcraft ages—or use the case-sensitive “All” to apply bans globally. The Scanner section lets you set a probability (0 to 1) for scanning players and chunks, so you can dial in performance.
Ban entries are flexible. Use just an item ID like 32 to target all wool colors, or 32-2 for magenta wool specifically. Each entry can include a label and a reason, with color codes via the ampersand (&) and hex format. Permissions are equally granular. By default, opped players bypass all bans. For others, you can grant exceptions with nodes like ItemRestrict.bypass.usage.35 or ItemRestrict.bypass.ownership.35-6. This allows trusted builders to keep a few normally banned items without opening the floodgates.
Managing these configurations across multiple modpacks can become tedious, but tools exist to simplify the workflow. For those juggling several server setups, installing plugins like ItemRestrict can be streamlined using the foxygame.net launcher, a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu, keeping your local testing environment aligned with your live server rules.
Compatibility and Performance
ItemRestrict supports a wide range of legacy versions, from 1.2.5 all the way to 1.7.10, making it a go-to choice for older Tekkit Classic and FTB servers that still thrive today. The code was rewritten from the ground up with performance in mind, replacing the older TekkitCustomizer logic with lean, high-efficiency implementations. The default ban list for Classic Tekkit was generously contributed by BigScary and reflects hands-on testing, so you get a sensible starting point. Before removing any default bans, take a moment to read the included reasons—they often highlight hidden exploits that aren’t obvious at first glance.
Commands are minimal and memorable. /ires reload refreshes the config on the fly, while /ires ban <banType> <id-datavalue> and /ires unban <banType> <id-datavalue> let you adjust restrictions without touching the file directly. The plugin requires no permissions plugin unless you need exceptions, keeping overhead low.
Conclusion
ItemRestrict fills a critical gap for any modded server administrator who values stability and fairness. By combining proactive crafting blocks, reactive inventory purges, and retroactive world cleanup, it eliminates the need for drastic map resets when a broken item slips through. The configuration is human-readable, the performance impact is negligible, and the permission system gives you fine control without complexity. Whether you’re running a small community Tekkit server or a sprawling FTB network, this plugin deserves a spot in your essential toolkit. A well-configured ban list means you can focus on building an engaging experience instead of fighting fires, and that is exactly what every admin wants.