FTB Chunks in FTB Evolution 2

Same as in the All the Mods 10 4.14 guide

FTB Chunks is part of the pack's mod list. This version of the pack ships FTB Chunks 2101.1.11, built for NeoForge.^[1]

It isn't a new addition either. The pack has included it since version 2.2 or earlier, so it has been around for a good while.^[1]

Unverified I couldn't confirm the details of what FTB Chunks does in this pack. I have no mod description, in-jar guidebook, config values, recipes or quests to check against, so I'm not going to guess at its features. The sources also don't show it on the ATM Star path, and no quests in this pack involve it.

Same as in the All the Mods 11 0.8.0-beta guide

FTB Chunks gives you chunk claiming, a minimap, a large map and waypoints. The sources I have for this pack don't show any recipes or quests for the mod, so I can't give you a crafting order. What I can do is walk you through what the mod's own descriptions confirm, in a sensible order.^[2]

Unverified The sources here show no in-pack recipes and no quests involving FTB Chunks, so there is no verified list of first items to craft. If the pack's quest book covers this mod, the sources here do not show where.

Know your claim limits

The setting for maximum claimed chunks is only a default. On a server, the FTB Ranks permission node ftbchunks.max_claimed can override it, so the limit you actually get may come from your rank.^[2]

For parties, the mod can work out the team's limits in several ways: LARGEST uses the member with the largest limits, SUM adds up all members' limits, OWNER uses the party owner's limits only, and AVERAGE uses the average of all members. There is also an optional hard limit for party teams, and 0 means no hard limit.^[2]

Check where you can claim

Servers can stop claiming in specific dimensions with a blacklist, for example minecraft:the_end, and wildcards like othermod:* are allowed. A whitelist also exists: if it isn't empty, a dimension must be on it (and not on the blacklist) to be claimable. If you can't claim somewhere, check these lists.^[2]

Understand protection and force-loading

• If no team member logs in for the configured number of days, the team's claims are released. Setting that option to 0 disables auto-unclaiming.^[2]
• Force-loading depends on the mode. NEVER needs at least one team member online. ALWAYS allows it even with nobody online. DEFAULT allows it only if a team member has the FTB Ranks permission ftbchunks.chunk_load_offline.^[2]
• Fire spread protection and flowing fluid protection between different teams' claims are false by default. The descriptions warn that enabling them can cause server performance issues.^[2]

Set up your map

The minimap size can be proportional to 10% of the screen width (modified by the Scale setting), or a fixed size regardless of resolution. Minimap visibility runs from 255 (fully opaque) down to 0 (fully transparent).^[2]

If the large map won't zoom out as far as you want, the max zoom constraint ties it to the number of explored regions and available memory. You can set it to false if that bothers you.^[2]

FTB Chunks is about land claims, not machines, power or item handling, so the sources here describe a different set of mechanics. You claim chunks to protect them, force-load chunks to keep them running, and a set of server options plus tag lists decide who can do what inside a claim. Here is how each part works.^[3]

Claiming and force-loading on the map

Press C on the large map to open the chunk claim screen. The in-game reference on that screen currently lists the mouse controls:^[3]

• Currently, left button and drag claims an area, and right button and drag unclaims an area.^[3]
• Currently, Shift + left button and drag force-loads an area, and Shift + right button and drag stops force-loading it.^[3]
• Currently, scrolling the mouse wheel over a force-loaded chunk adjusts its auto-expiry.^[3]
• Currently, holding Tab hides the chunk grid, and holding Alt shows the absolute claim and force-load times.^[3]

The large map reference currently lists these other keys: Space centers the view on you, S opens settings, and Ctrl + S opens server settings (op required). T teleports you to a point (op required). F3+G toggles the chunk grid. The unclaim all option asks you to confirm before it unclaims every chunk visible on the map.^[3]

Limits and expiry

How many chunks a team can claim or force-load comes from the server config. The option descriptions say the default maximums can be overridden by the FTB Ranks permission nodes 'ftbchunks.max_claimed' and 'ftbchunks.max_force_loaded'. For party teams, a party limit mode decides how the members' limits combine:^[3]

• As currently described, LARGEST uses the limits of the member with the largest limits.^[3]
• As currently described, SUM adds up all the members' limits.^[3]
• As currently described, OWNER uses the party owner's limits only.^[3]
• As currently described, AVERAGE uses the average of all members' limits.^[3]

The option descriptions currently also mention hard limits for party claims and for party force-loads that apply regardless of member count or limit mode. They say a value of 0 means no hard limit.^[3]

Claims do not last forever if a team goes quiet. The option descriptions currently say that if no team member logs in for the configured number of idle days, the team's claims are released, and force-loaded chunks stop being force-loaded after their own idle timer. They say setting either timer to 0 turns that auto-release off.^[3]

When force-loaded chunks keep running

The force-load mode decides whether chunks stay loaded while the owners are offline. As currently described, NEVER only allows force-loading while the owning team has at least one online player. ALWAYS allows it even with nobody online. DEFAULT allows it if the team has at least one player with the FTB Ranks 'ftbchunks.chunk_load_offline' permission.^[3]

What a claim protects against

Beyond blocking building and breaking, the server config has switches for subtler ways into a claim. Some are off by default because of the server load they can cause:^[3]

• Fire spread protection stops fire spreading between claims owned by different teams. The description says it is false by default and can cause performance issues when many blocks are on fire.^[3]
• As currently described, flowing fluid protection stops fluids flowing horizontally across claims owned by different teams. It is also false by default, and fluid flow ticks are checked very frequently, which is a cost on large bodies of flowing fluid.^[3]
• As currently described, piston protection stops pistons pushing or pulling blocks across claims owned by different teams, unless the block is entering or leaving a claim whose block edit mode is Public.^[3]
• As currently described, unknown explosion protection covers explosion sources the mod cannot identify in code, such as Ghasts. When on, their damage is prevented in protected chunks.^[3]
• PvP mode can be ALWAYS, NEVER, or PER_TEAM, where each team decides through a team property.^[3]
• As currently described, fake player access is handled by a mode: CHECK treats fake players like real players, DENY never allows them, and ALLOW always allows them.^[3]

Each team also has its own toggles. Allow Explosions controls whether explosions can damage blocks in claimed areas. Allow Mob Griefing is described as currently covering Endermen only, with Creeper explosions handled by Allow Explosions instead. The mod's tag data lists minecraft:enderman as the entity type for mob griefing.^[3][4]

Things anyone can still use in a claim

The mod ships tag lists of exceptions, so some things work in other people's claims. Anyone can interact with Crafting Table and Bell blocks. The list also optionally covers Create table cloths, Tombstone graves, and the tags for waystones and sharestones from Waystones. Several waystone blocks in the fwaystones namespace are listed too. Those entries are marked as not required, so they only apply if the other mod is installed.^[5]

There are also optional exceptions for other mods: the gravestone:gravestone block is on the edit whitelist, and the corpse:corpse entity is on the entity interact whitelist.^[6][7]

Item use has its own lists. Right-click is whitelisted for Shield, Firework Rocket and Map. Right-click is blacklisted for Bucket, Water Bucket, Lava Bucket, Lead, Name Tag, Splash Potion and Lingering Potion.^[8][9]

Map memory and performance

The client config has memory options for the map. Region data is held in 512x512 regions, and a timeout in seconds releases regions that have not been accessed recently. When you close the large map, region data is auto-released down to a set number. Smaller values use less memory but mean more disk access when regions are reloaded, and 0 disables releasing. Another option limits max zoom-out by the number of explored regions and available memory, and you can set it to false if that bothers you.^[3]

Unverified The pack's actual claim and force-load limits, the force-load mode and the on/off state of the protection toggles are set in the mod's config. The sources here do not show the pack's values, so the descriptions above explain what each option does, not what this pack sets.

Same as in the All the Mods 10 8.2 guide

Unverified The sources here do not show any quest chapter, crafting recipe or tier breakdown for FTB Chunks, so no progression path is described for this pack.

What the mod does ship in this pack is a set of tag files that list blocks, entities and items with special handling. Here is what each one contains.^{[10][11][12][13][14][15]}

Special-case tags

• Interact whitelist (blocks): Crafting Table and Bell are always listed. Create table cloths, tombstone graves, waystones, sharestones and several fwaystones waystone variants are listed too, but marked as not required.^[11]
• Edit whitelist (blocks): the gravestone:gravestone block is listed, marked as not required.^[10]
• Entity interact whitelist: the corpse:corpse entity is listed, marked as not required.^[12]
• Mob griefing blacklist: the enderman is listed.^[13]
• Right click blacklist (items): Bucket, Water Bucket, Lava Bucket, Lead, Name Tag, Splash Potion and Lingering Potion.^[14]
• Right click whitelist (items): Shield, Firework Rocket and Map.^[15]

Every one of these files has replace set to false, so they add entries on top of whatever else is already in the tag instead of overwriting it.^{[10][11][12][13][14][15]}