Why Your FTB Server Needs More Chunks Per Player
You’re managing a bustling FTB (Feed The Beast) Minecraft server, and a common plea starts popping up in chat. A dedicated builder can’t expand their automated farm because they’ve hit their chunk limit. A new player feels boxed in, unable to claim enough land for their sprawling reactor setup. The frustration is real: the default max chunks in your ranks system is stifling creativity and progress.
This isn’t just about giving players more digital real estate. It’s about server health, player retention, and enabling the grand, complex contraptions that FTB modpacks are famous for. When players hit an arbitrary wall, their engagement drops. They might start looking for loopholes, asking for admin overrides constantly, or worse, leaving for a server with more generous limits.
Understanding how to adjust the “max chunks” setting within your ranks or permissions plugin is a core administrative skill. It allows you to tailor the gameplay experience, reward loyal players, and create a tiered system where progression feels meaningful. Let’s break down exactly how to grant your players the space they need to thrive.
Understanding Chunk Claims and FTB Essentials
Before we change any numbers, it’s crucial to know what we’re adjusting. In the context of FTB and similar modded servers, “max chunks” almost always refers to the maximum number of chunks a player can claim for protection. This is typically managed by one of two systems: the FTB Utilities mod (and its FTB Ranks addon) or a separate land-claiming plugin like GriefPrevention or Lands.
A “chunk” is a 16×16 block area that extends from the bedrock to the world height. Claiming a chunk marks it as a player’s personal territory. Within a claim, other players usually cannot break blocks, place blocks, interact with chests or machines, or cause explosions. This is the bedrock of a peaceful, cooperative modded server—it prevents griefing and accidental interference with complex redstone or cable networks.
The “max chunks” limit is a per-player or per-rank ceiling. A default “member” rank might allow 10 chunks, while a “veteran” rank might allow 50, and a “donor” rank might allow 100. Your task as an admin is to configure these values logically to match your server’s rules and world size.
Identifying Your Server’s Claim System
The first step is diagnosis. You need to know which plugin or mod is handling claims on your specific server.
Join your server with operator permissions or access the server console. Use these diagnostic commands:
– /ftb teams info (If this shows claim info, you’re using FTB Utilities).
– /claims list (A common command for other plugins).
– /gp info (For GriefPrevention).
– /lands info (For the Lands plugin).
Check your server’s `mods` and `plugins` folders. Look for files like `ftb-utilities.jar`, `ftb-ranks.jar`, `GriefPrevention.jar`, or `Lands.jar`. The presence of these files confirms the system in use. This guide focuses on the FTB ecosystem (FTB Utilities & FTB Ranks), as implied by the search term “ftb ranks”.
Configuring Max Chunks in FTB Utilities and Ranks
FTB Utilities has its own built-in ranks system, which can be enhanced by the separate FTB Ranks mod. Configuration is done via server-side files, not in-game commands. You’ll need file access (like FTP or a server panel’s file manager).
Navigate to your server’s root directory, then find the `world` folder (or the folder for the specific world you want to configure). Inside, locate the `serverconfig` folder. The key file is `ftb-utilities-server.toml`.
Open this file in a text editor. Look for the `[ranks]` section. You might see a default entry like this:
[[ranks]]
id = “player”
name = “Player”
permissions = [
“ftbutilities.chunkloader.max_chunks=0”,
“ftbutilities.claims.max_chunks=50”
]
The line `”ftbutilities.claims.max_chunks=50″` sets the maximum claimable chunks for the “player” rank. To increase it, simply change the number. For example, `”ftbutilities.claims.max_chunks=100″`.
To create a new rank with more chunks, duplicate the [[ranks]] block, change the `id` and `name`, and adjust the `max_chunks` value. For instance, a “vip” rank could have 200 max chunks.
Using the FTB Ranks Mod for Advanced Control
If you have the FTB Ranks mod installed, it adds a more powerful, dedicated rank configuration. The file is usually `ftb-ranks.toml` in the same `serverconfig` directory.
This file uses a different, more verbose syntax. You define ranks and their permissions in a structured list. To set max chunks here, you add a permission node. The exact node can vary, but it is often one of these:
– `ftbutilities.claims.max_chunks`
– `ftbchunks.claims.max_chunks` (for newer FTB Chunks mod)
– `ftbchunks.max_claimed_chunks`
An example rank definition in `ftb-ranks.toml` might look like this:
[[ranks]]
id = “veteran”
name = “Veteran”
permissions = [
“ftbchunks.max_claimed_chunks=150”,
“ftbchunks.force_load_max_chunks=10”
]
After editing these `.toml` files, you must restart your Minecraft server for the changes to take effect. A simple `/reload` is often not enough for mod configuration changes.
Granting Additional Chunks to Specific Players
Sometimes, you don’t want to change a rank for everyone, but need to grant extra chunks to a single trustworthy player or a small group. This is often called an “override” or “bonus chunks” feature.
In FTB Utilities, this can sometimes be done via in-game commands if the permissions are set up. A command like `/ftb teams extra_claims add [player] [number]` might be available. Check the mod’s documentation or use `/ftb help` in-game to see available commands.
A more universal, plugin-agnostic method is to create a custom rank. You can create a new rank in your `ftb-ranks.toml` file called “builder” with a very high chunk limit (e.g., 500). Then, you assign this rank to specific players using an in-game command. The command is typically `/ftb ranks set [player] [rank_id]`. For example, `/ftb ranks set NotchMaster builder`.
This approach keeps your main rank structure clean while giving you the flexibility to reward exceptional contributors without altering the balance for all players of a certain tier.
Troubleshooting Common Chunk Limit Issues
You’ve changed the configs, restarted the server, but a player still says they can’t claim more chunks. Let’s troubleshoot.
Claims Still Not Working After Config Change
First, double-check the syntax in your `.toml` file. A missing quote, bracket, or equals sign will break the entire rank. TOML files are syntax-sensitive. Use an online TOML validator if you’re unsure.
Second, confirm the player’s actual rank. Use `/ftb ranks info [player]` to see which rank they are assigned. They might still be on the default “player” rank instead of the “veteran” rank you updated.
Third, check for permission conflicts. If you are using both a permissions plugin (like LuckPerms) AND FTB Ranks, there might be a conflict where the plugin is overriding the mod. Ensure your permissions plugin is not setting a lower `ftbutilities.claims.max_chunks` node for the same rank or player.
Player Has Unclaimed Chunks But Can’t Load Them
Remember, “max chunks” often refers to two related but separate limits: claimed chunks and force-loaded chunks (chunkloaders). A player might have 100 claimed chunks but only be allowed to force-load 10. Force-loading keeps chunks active even when no player is nearby, which is essential for quarries and farms.
The permission node for force-loaded chunks is usually `ftbutilities.chunkloader.max_chunks` or `ftbchunks.force_load_max_chunks`. You need to increase both values in tandem if a player needs to run many offline machines. Check your rank configuration for both permissions.
World Border or Server-Wide Limits
Some servers impose a global limit on total claimable chunks to manage server performance. This is set in the main `ftb-utilities-server.toml` under a `[general]` or `[claims]` section, with a key like `max_claims_per_world`. If this global cap is hit, individual player limits become irrelevant. Ensure this global limit is set high enough to accommodate your player base’s combined allowances.
Strategic Planning for Your Server’s Chunk Economy
Increasing chunk limits isn’t just a technical fix; it’s an economic decision for your server. Handing out too many chunks too freely can lead to performance degradation as more chunks are permanently loaded and active. It can also reduce the incentive for players to upgrade ranks or donate.
Develop a tiered strategy. Start new players with a modest but sufficient amount (e.g., 25-50 chunks). This allows for a starter base, a few farms, and room to grow. Link chunk increases to meaningful progression: award bonus chunks for playtime milestones (e.g., +10 chunks every 50 hours), for completing major server challenges, or as a benefit for donor ranks.
Communicate this system clearly on your server’s website or Discord. Let players know how to earn more land, not just beg for it. This turns a potential source of admin headaches into a driver of engagement and fair play.
Taking Control of Your Server’s Landscape
Adjusting the max chunks in FTB Ranks is a straightforward process of editing configuration files with the correct permission nodes. The real power lies in using this tool intentionally. By diagnosing your claim system, applying precise increases via `ftb-ranks.toml` or `ftb-utilities-server.toml`, and creating a logical tiered system, you solve the immediate “can’t claim” problem while building a healthier, more scalable server environment.
Your next step is to log into your server panel, locate those TOML files, and audit your current rank settings. Start by increasing the base player rank by a small, reasonable margin, then create one higher-tier rank with a more generous limit. Announce the change, explain how players can achieve the higher tier, and watch as your community expands its ambitions, free from arbitrary borders.
