Getting Started with FTB Chunks and Claim Protection
When you run a multiplayer Minecraft server, protecting player builds from griefing is a top priority. The FTB Chunks mod has become a staple for many modded servers, allowing players to claim chunks and secure their territory. But out of the box, claims are often too restrictive—preventing friends from opening doors, flipping levers, or even interacting with certain blocks. That is where the Edit & Interact Whitelist for FTB Chunks datapack steps in, giving server owners fine-grained control over what can be touched inside a claim.
Why the Default Claim Rules Need Tweaking
FTB Chunks offers a powerful claiming system. Once a player claims a chunk, other players cannot break or place blocks, open containers, or use redstone components. While this prevents theft and vandalism, it also stops cooperative gameplay. Imagine a team base where your friends cannot open a storage drawer or press a button to activate a farm. The default whitelists included with FTB Chunks cover some basic interactions, but modded blocks often get left out. The Edit & Interact Whitelist datapack gives you the tools to customize exactly which blocks are editable, interactable, or even which entities can be right-clicked.
What the Datapack Actually Does
This datapack extends the existing FTB Chunks claim system by adding separate JSON configuration files. Instead of relying solely on the mod’s built-in tags, you can define your own whitelists and blacklists. The datapack lets you specify:
- Blocks that can be edited (broken or placed) inside claims.
- Blocks that can be interacted with (right-clicked) but not broken.
- Entities that can be interacted with (like villagers or armor stands).
- Items whose right-click actions are allowed or blocked on any block.
This separation gives you surgical precision. For example, you might allow players to open a storage crate (interact) but not break it (edit). Or you might let them use a wrench on a machine (right-click whitelist) without giving full edit access.
Installing and Preparing the Datapack
After downloading the datapack, unzip it and look for the configuration files inside the data folder. The main files you will edit are interact_whitelist.json, edit_whitelist.json, entity_interact_whitelist.json, right_click_whitelist.json, and right_click_blacklist.json. You will want to start by copying the default IDs from the FTB Chunks GitHub repository into each file to maintain all the standard protections before adding your own modded blocks. Managing datapacks like this is made simpler with a modern launcher; for instance, the foxygame.net launcher offers a flexible way to install and update mods directly from its menu, making it easy to add the whitelist datapack to your server or singleplayer world.
Populating the Whitelist Files
Open edit_whitelist.json and add the block IDs you want players to be able to break and place inside claims. This might include decorative blocks from mods like Chisel, building blocks from Quark, or any block that is safe to let other players handle. For blocks that should only be right-clicked—like crafting tables, furnaces, or machine interfaces—add their IDs to interact_whitelist.json. Remember that a block can appear in both files if you want full access.
Controlling Right-Click Interactions
Some items perform an action when you right-click on a block, such as a wrench rotating a machine or a debug stick changing block states. The right_click_whitelist.json file lets you list items that are allowed to trigger their right-click function inside claims. Conversely, right_click_blacklist.json blocks specific items from using their right-click action, even if the block itself is interactable. This is useful for preventing exploits or stopping players from using tools that could bypass claim protection.
Whitelisting Entity Interactions
Many mods add entities that players need to interact with—traders, quest NPCs, or even tamed creatures. By adding entity type IDs to entity_interact_whitelist.json, you allow players to right-click those entities inside claims. Without this, a villager inside a friend’s base would be completely unclickable. Check the default entity whitelist from the FTB Chunks repository to see which vanilla entities are already covered, then extend it with modded mobs.
Finding the Correct Block and Entity IDs
To add modded blocks or entities, you need their full resource location ID, like minecraft:chest or thermal:machine_frame. You can usually find these by pressing F3+H to enable advanced tooltips in-game, then hovering over the item or entity. For entities, you may need to use commands like /summon to see the exact ID. Always test your changes on a small scale before rolling them out to the entire server.
Putting It All Together
Once you have edited all the JSON files, zip the datapack back up and place it in your world’s datapacks folder. Reload the world or restart the server. Now players inside claims will be able to interact with the blocks and entities you specified, while everything else remains protected. This balance between security and cooperation is what makes the FTB Chunks whitelist datapack so valuable for modded communities.
Final Thoughts on Customizing Claim Permissions
The Edit & Interact Whitelist for FTB Chunks datapack turns a rigid claim system into a flexible, server-friendly tool. By carefully curating your whitelists, you can eliminate the frustration of locked doors and unusable machines without sacrificing grief protection. Start with the default IDs, layer in your modded blocks, and watch your players enjoy a seamless multiplayer experience. With a little JSON editing, you will have a server that feels both safe and inviting—exactly what a great Minecraft community needs.