FTB Chunks in All the Mods 10

This pack ships FTB Chunks version 2101.1.22, using the NeoForge build of the mod. It has been in the pack since All the Mods 10 0.32 or earlier, so it is a long-standing part of the mod list rather than a recent addition.^[1]

Unverified The sources I was given don't describe what FTB Chunks does in this pack, so I can't confirm its features or any pack-specific changes to it here.

Same as in the All the Mods 10 8.1 guide

Unverified The sources here show no crafting recipes and no quests for FTB Chunks in this pack, so there is no confirmed list of items to craft first. This section only covers what the mod's own setting descriptions say.

What to know before you claim chunks

• Claims belong to teams. By default, FTB Teams ally status decides whether players count as allied, and a server can force everyone to be allied or nobody to be allied.^[2]
• Servers can block claiming in certain dimensions with a blacklist, for example The End, and wildcards that match a whole mod's dimensions are allowed. A whitelist can restrict claiming to the listed dimensions only.^[2]
• The default claim limit can be overridden by the FTB Ranks permission node ftbchunks.max_claimed. Party teams have their limits worked out by a mode setting with the options LARGEST, SUM, OWNER or AVERAGE.^[2]
• If no team member logs in for a set number of days, the team's claims are released. Setting that value to 0 turns auto-unclaiming off.^[2]
• Force-loading is controlled by a mode setting. NEVER only allows it while the owning team has someone online. ALWAYS allows it even when nobody is online. DEFAULT allows it if the team has a player with the FTB Ranks ftbchunks.chunk_load_offline permission.^[2]

Map settings worth a look

• The minimap can scale with your screen. When the proportional option is on, its size is based on 10% of your screen width and can be adjusted with the Scale setting. When it is off, the size is fixed regardless of resolution.^[2]
• Zooming out on the large map can be limited by how many regions you have explored and how much memory is available. If that bothers you, you can turn the max zoom constraint off.^[2]

Same as in the FTB StoneBlock 4 1.22.0 guide

FTB Chunks protects the chunks your team claims, and it can keep those chunks loaded while you are away. You manage both from the claim screen, which you open with C on the large map.^[3]

Claiming and force-loading on the map

The in-game reference screen currently lists these controls. Everything works by dragging over chunks on the claim screen.^[3]

• In the current reference text, left button drag claims an area, and right button drag unclaims an area.^[3]
• In the current reference text, Shift + left button drag force-loads an area, and Shift + right button drag unforce-loads it.^[3]
• The current reference text says to rotate the mouse wheel over a force-loaded chunk to adjust its auto-expiry.^[3]
• The current reference text says to hold Tab to hide the chunk grid, and to hold Alt to show absolute chunk claim and force times.^[3]

On the large map itself, the current in-game text says left button click or drag moves the view, the right button opens a context menu and the wheel zooms. Space centers the view on you, S opens settings and F3+G toggles the chunk grid. Ctrl + S (server settings) and T (teleport to a point) both need op.^[3]

Limits and team rules

How many chunks you can claim or force-load is set on the server side. The base claim and force-load caps can be overridden per player with FTB Ranks permission nodes, namely ftbchunks.max_claimed and ftbchunks.max_force_loaded.^[3]

Party teams have their own rules. According to the mod's current text, a party limit mode decides how the team's claim and force-load limits are worked out: LARGEST uses the member with the largest limits, SUM adds all members together, OWNER uses only the party owner, and AVERAGE averages everyone. Separate hard limits for party claims and party force-loads apply whatever the mode is, and a value of 0 means no hard limit.^[3]

Claims can be released if a team goes quiet. As the mod's current text describes it, if no team member logs in for the configured number of days, the team's claims are released, and the same idle timer exists for force-loaded chunks. Setting either to 0 turns that auto-release off.^[3]

When force-loading actually runs

The force load mode setting decides, as the mod's current text describes it, whether your chunks stay loaded when nobody on your team is online. NEVER only allows force-loading while the owning team has at least one player online. 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]

Dimension rules

Servers can control where claiming is allowed. A dimension blacklist stops claims in listed dimensions, for example minecraft:the_end. A whitelist, if non-empty, means a dimension must be on it and also not on the blacklist. Both accept wildcards such as othermod:*.^[3]

There is also a no wilderness option. When it is on, chunks must be claimed before anyone can build on them. A separate dimension list lets you require this only in certain dimensions, such as minecraft:the_nether.^[3]

What claims protect against

Beyond edits and interactions, the server config has switches for several indirect ways of affecting a claim. Pistons can be stopped from pushing or pulling blocks across claims owned by different teams. Fire can be stopped from spreading between teams' claims, and flowing fluids can be stopped from running horizontally across them. Explosions from sources the mod can't identify, such as Ghasts, can also be blocked in protected chunks.^[3]

The mod's current text says the fire and fluid checks are false by default, with a warning about server performance, especially with lots of burning blocks or big flowing bodies of fluid. If the disable protection option is set to true, those settings are ignored. That option is described as useful for private servers where everyone is trusted and claims are only used for force-loading.^[3]

PvP is handled by a server mode. As the mod's current text describes it, ALWAYS allows it in all claims, NEVER prevents it in all claims, and PER_TEAM lets each team choose through its team property.^[3]

Team settings and allies

Each team also has its own claim properties. These include whether explosions can damage blocks, whether mobs can grief (currently Endermen only, since Creeper explosions fall under the explosions setting), whether PvP is allowed and which block edit and interact mode applies. The team PvP option only works when the server PvP mode is set to PER_TEAM.^[3]

According to the mod's current text, the server's ally mode decides who counts as an ally. DEFAULT checks FTB Teams ally status, FORCED_ALL treats every player as allied and FORCED_NONE treats no one as allied.^[3]

Built-in tag lists

The mod ships tag files for its block, entity and item whitelists and blacklists. Many entries are marked as not required, so they only matter when the other mod is present.^{[4][5][6][7][8][9]}

• Interact whitelist (blocks): Crafting Table and Bell are listed as required entries. Optional entries cover Create table cloths, Tombstone graves, Waystones and sharestones, and the Fabric Waystones variants (waystone and the desert, stone brick, red desert, nether brick, red nether brick, end stone brick, deepslate brick and blackstone brick versions).^[5]
• Edit whitelist (blocks): only the optional gravestone:gravestone block.^[4]
• Entity interact whitelist: only the optional corpse:corpse entity.^[6]
• Mob griefing blacklist: minecraft:enderman.^[7]
• Right click whitelist (items): Shield, Firework Rocket and Map.^[9]
• Right click blacklist (items): Bucket, Water Bucket, Lava Bucket, Lead, Name Tag, Splash Potion and Lingering Potion.^[8]

Map and minimap behavior

The map has its own client-side options, as the mod's current text describes them. Region data is held in 512x512 regions, and a timeout in seconds releases regions that haven't been accessed recently. A separate option releases region data down to a set number when you close the large map. Smaller values use less memory but mean more disk access when regions reload, and 0 disables releasing.^[3]

If you can't zoom out as far as you'd like, the max zoom constraint option limits zoom-out by the number of explored regions and the available memory. Set it to false to remove that limit.^[3]

The minimap can be proportional, sized to 10% of the screen width and modifiable by the Scale setting, or a fixed size regardless of resolution. Waypoints can show their name when your crosshair is close enough, and focused waypoints can grow. Death waypoints can auto-remove the closest one when you come within a set distance of it, if that value is above 0.^[3]

Servers can also require the ftbchunks_mapping game stage before a player may open the map or see the minimap, which needs KubeJS and/or Gamestages. Long-range player tracking updates are sent at a tick interval, where lower values mean more server load and network traffic, and 0 disables the tracking.^[3]

Unverified The sources here do not show which values the pack actually uses for the server settings described above (protection switches, limits, force load mode, game stage requirement or tracking interval), since no FTB Chunks config files are available. Check the pack's FTB Chunks server config or the in-game server settings screen for the real values.

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]}

All the Mods 10 8.2 ships FTB Chunks 2101.1.22. The mod has been in the pack since All the Mods 10 0.32 or earlier, and the pack changelogs record a version bump every time it was updated since then.^[1]

Updates by pack release

• All the Mods 10 8.2: 2101.1.21 to 2101.1.22.^[16]
• All the Mods 10 7.3: 2101.1.20 to 2101.1.21.^[17]
• All the Mods 10 7.1: 2101.1.14 to 2101.1.20.^[18]
• All the Mods 10 6.0: 2101.1.13 to 2101.1.14.^[19]
• All the Mods 10 4.15: 2101.1.11 to 2101.1.13.^[20]
• All the Mods 10 4.12: 2101.1.10 to 2101.1.11.^[21]
• All the Mods 10 4.6: 2101.1.9 to 2101.1.10.^[22]
• All the Mods 10 3.0: 2101.1.8 to 2101.1.9.^[23]
• All the Mods 10 2.40: 2101.1.7 to 2101.1.8.^[24]
• All the Mods 10 2.29: 2101.1.5 to 2101.1.7.^[25]

Unverified What actually changed inside each FTB Chunks update (new features, fixes or config changes) is unverified. The pack changelogs only list the version bumps, and there are no stored changelogs for the shipped jars.