MC-WIKI.net
FTB Chunks Wiki › Guides › FTB Chunks Claiming, Unclaiming, and Forceloading Guide

FTB Chunks Claiming, Unclaiming, and Forceloading Guide

guide

FTB Chunks lets you mark out territory on a server and keep parts of the map running even when nobody is nearby, and this guide explains how to claim, release, and forceload chunks through the mod's own interface.

Opening the claim screen

The claim screen is where all chunk work happens. Open it with the corresponding hotkey (set it in the controls menu), or use the Open Claim Manager entry, which is labelled FTB Chunks: Claim Manager. A key/mouse reference is available on the large map under Key/Mouse Reference, and the claim screen itself carries a Chunk Claiming Reference panel. If the mod is missing on the server side, you will see a notice that FTB Chunks requires the mod on the server.

Claiming and unclaiming

Inside the claim screen, drag with the left mouse button to claim an area, and drag with the right mouse button to release an area back to unclaimed status. A Rectangular Claiming mode is available for box-shaped selections. Claiming is refused when the chunk already belongs to someone — the screen reports that the chunk is already claimed by another party — and when you are not the owner, when you have hit your chunk limit, or when the dimension does not permit claiming at all. Claimed chunks can be shown on the map, either all of them or only your own.

Forceloading

Forceloading keeps chunks active. Hold Shift while dragging with the left button to forceload an area, and hold Shift with the right button to stop forceloading it. Rotating the mouse wheel over a forceloaded chunk adjusts when its forceloading expires. A chunk that is already loaded reports that status, and the interface tracks how many chunks are forceloaded versus how many remain available out of your total claimed count.

Limits and expiry

Two per-player caps apply: Max Claimed Chunks per Player and Max Forcedloaded Chunks per Player. Both defaults can be overridden through permission nodes. Party teams may also face a Hard Max Team Claim Limit and Hard Max Team Forceload Limit, where zero means no ceiling. How a party's allowance is worked out depends on the Party Limit Calculation Mode: the largest member's limits, the sum of all members, the owner's limits alone, or the average across members. Claims can also lapse: Max Idle Days Before Unclaim releases a team's claims after that many days without a login, and Max Idle Days Before Unforceload stops forceloading under the same condition. Zero disables each. Offline forceloading behaviour is set by Offline Forceloading Mode.

Protection rules

Claim protection governs what others may do inside your territory. Separate modes exist for Block Edit/Interact, Block Interact, Entity Interact, and Non-living Entity Attack, plus a Location Visibility setting controlling who appears on maps. Server-side options decide whether explosions damage claimed blocks, whether mobs may damage blocks, whether PvP is permitted, and whether fake players are treated as allies. Protect Unclaimed Regions, with a per-dimension variant, requires claiming before building. Pistons, flowing fluids, and fire spread can each be blocked from crossing between differently owned claims. Disable Claim Protection turns the whole system off for trusted private servers. When protection blocks you, the game tells you that you must claim the chunk to interact, or that interaction was prevented by claim protection.

Admin tools

Admin Mode can be toggled on or off; while enabled you may modify chunks regardless of who owns them. A Bypass Protection state is likewise shown as enabled or disabled. Admins can also unclaim every chunk currently visible on the map, and dimension whitelists and blacklists restrict where claiming is allowed at all.