Item Restrict: Control Items on Your Minecraft Server
Running a modded Minecraft server is a constant balancing act between giving players freedom and protecting the world from accidental or deliberate destruction. A single misplaced click on a banned wrench or an explosive staff can erase hours of another player's work. Server administrators often find themselves chasing after griefers, restoring chunks, and rewriting config files in a desperate attempt to keep things stable. This is precisely where Item Restrict: Control Items on Your Minecraft Server steps in as a dedicated moderation tool designed for classic modded environments.
Developed by the CraftersLand community for their own projects, this plugin offers a granular approach to item management. Instead of relying on broad, clumsy bans, it lets you define exactly what players can and cannot do with specific items. The system was originally built for Minecraft versions 1.6.4 and 1.7.10, where numerical item IDs were the standard way to identify objects, and it continues to work flawlessly on those legacy builds. For servers still running these classic versions, this tool remains one of the most reliable ways to enforce item restrictions.
Core Features and Restriction Types
What sets this plugin apart from simple config-based bans is its comprehensive set of restriction categories. Each one targets a specific interaction, giving you surgical precision over every item in the game. Here is what you can control:
- Ownership - Confiscates a forbidden item the moment it enters a player's inventory, regardless of how it got there.
- Usage - Blocks any interaction with the item or block, preventing right-click actions and activation.
- Crafting - Disables the crafting recipe for regular players while keeping it available for admins, or removes the recipe entirely from the game.
- Smelting - Removes furnace recipes so players cannot obtain ingots from banned ores or materials.
- Placement and Block Break - Separate toggles for preventing the placement and destruction of specific blocks.
- Brewing - Stops the creation of particular potions in the brewing stand.
- Wearing Armor - Prohibits equipping specific armor pieces, useful for gating high-tier gear.
- Creative, Pickup, Drop - Restricts obtaining items from the creative menu, picking them up from the ground, and throwing them out of the inventory.
- World Banned - A world scanner that removes already-placed banned blocks in loaded chunks, cleaning up existing violations.
This level of detail matters enormously on modpacks with dozens of mods, where a single item can break the server economy or trigger crashes. The world scanning operation runs in a separate thread, so server performance remains unaffected even during large-scale sweeps. You can target specific item IDs and data values, making the plugin compatible with items added by Forge mods as long as they use the numeric ID system.
Configuration and First-Time Setup
Installing the plugin follows the standard procedure. You place the ItemRestrict.jar file into the plugins folder of your server, start the server once to generate the configuration files, and then stop it to edit them. The main work happens in two YAML files: config.yml and RestrictedItems.yml.
The first file contains global parameters, such as EnableOnAllWorlds: true. This option activates restrictions across every dimension, including those added by mods. Without this, players could simply travel to another world to bypass the bans, so enabling it is critical for airtight enforcement.
The second file is where you define the actual restrictions. You specify item IDs, their data values, and the type of restriction to apply. For each item, you can also set a custom ban reason that gets displayed to the player when they try to use it. All messages and the plugin prefix are fully customizable with color code support. When a player attempts to pick up a banned item from the ground, particle effects appear as a visual warning, and sound effects play during interaction attempts. These feedback cues help players understand immediately that their action is not allowed.
Permissions and Command Structure
The permission model is both simple and flexible. The base permission ItemRestrict.bypass allows a player to ignore all restrictions, while ItemRestrict.admin grants access to the config reload command. For more nuanced control, you can issue exceptions for specific items and actions. For example, the permission ItemRestrict.bypass.57.*.craft would allow crafting all variations of item ID 57, while ItemRestrict.bypass.57.10.own permits ownership of only a specific subtype with data value 10.
This granular permission system is a boon for servers with role-playing classes or donor privileges. You can grant a VIP rank the ability to craft a banned item without giving them full bypass rights. The administrative commands are straightforward: /itemrestrict reload applies changes without restarting the server, and /itemrestrict help displays the command reference. After editing the RestrictedItems.yml file, a quick reload makes all new rules take effect immediately, minimizing downtime during configuration tweaks.
Practical Use Cases on Modded Servers
Because the plugin originated from the CraftersLand community's own modded projects, it addresses real-world scenarios that server admins frequently encounter. For instance, if your server runs the Techguns mod and you want to prevent players from wearing power armor until they reach a certain level, you simply add the armor's ID with the wear restriction. To clean up nuclear reactors that new players have already placed in their bases, you activate the world scanner with the world restriction type.
During testing of such configurations, admins often need to switch quickly between clients with different mod sets. A reliable launcher helps here, allowing you to assemble test builds without manual file management. This accelerates the debugging process for server rules and ensures that your restrictions work as intended across different client configurations.
Limitations and Considerations
Despite its powerful feature set, this plugin has clear boundaries. After Minecraft 1.9, many items, particularly potions, began sharing identical IDs and data values, making it impossible to distinguish them without NBT data. The plugin operates exclusively with numerical identifiers, which means it cannot function on versions 1.13 and above where the numeric ID system was completely removed. The author explicitly states that future updates for newer versions are not planned, though the source code remains open for community contributions.
There is also a known bug on Spigot 1.12 related to crafting recipe removal. For servers on this version, the recommended workaround is to use the CraftingBan function as a temporary solution until the issue is resolved. Being aware of these limitations helps you plan your server's security strategy accordingly.
Final Verdict
Item Restrict by CraftersLand is a specialized but highly effective tool for servers running Minecraft 1.6.4 through 1.7.10, with limited usability on 1.12. It requires no dependencies, configures in minutes, and covers nearly every method of interacting with banned items. The background world scanning, flexible permissions, and detailed player feedback messages make server administration transparent and comfortable.
If your modded server still operates on classic builds and needs protection from griefing tools, this plugin deserves a spot at the top of your installation list. To get started, you can download Item Restrict: Control Items on Your Minecraft Server from the official distribution channels, and follow the standard installation guide to set it up. The question of how to install is answered by the simple plugin folder placement and config generation process outlined above. For those looking for Item Restrict: Control Items on Your Minecraft Server for Minecraft, this tool remains a dependable choice for maintaining order on legacy servers.