FTB Chunks guide for All the Mods 10: To the Sky 2.0.0 to 2.0.5

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 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 All the Mods 10 8.1 guide

FTB Chunks is a claiming and mapping mod, so its mechanics are about chunks, teams and protection rather than machines, power or fluids. The sources for this pack only cover the mod's in-game text, so this section sticks to what those tooltips explain.^[2]

Claiming and force-loading from the map

You manage chunks from the chunk claim screen, which you open with C from the large map. The in-game reference lists these controls:^[2]

• Left button and drag: claim an area.^[2]
• Right button and drag: unclaim an area.^[2]
• Shift + left button and drag: force-load an area.^[2]
• Shift + right button and drag: stop force-loading an area.^[2]
• Mouse wheel over a force-loaded chunk: adjust its auto-expiry.^[2]
• Hold Tab to hide the chunk grid, or hold Alt to show absolute claim and force-load times.^[2]

On the large map itself, left click and drag moves the view, right click opens a context menu, and the mouse wheel zooms. Space centers the view on you, S opens settings, and Ctrl + S opens the server settings, which need op. T teleports to a point, also op only. F3+G toggles the chunk grid.^[2]

Claim and force-load limits

The maximum number of claimed chunks and force-loaded chunks are server settings. Both defaults can be overridden with FTB Ranks permission nodes, ftbchunks.max_claimed and ftbchunks.max_force_loaded.^[2]

Party teams get their limits through a party limit calculation mode. LARGEST uses the member with the largest limits, SUM adds up all members' limits, OWNER uses only the party owner's limits, and AVERAGE uses the average. There is also a hard team limit for claims and another for force-loads. They apply regardless of member count or mode, and a value of 0 means no hard limit.^[2]

Claims don't last forever if a team goes quiet. If no team member logs in for the configured number of days, the team's claims are released, and force-loaded chunks stop being force-loaded. Setting either idle-days option to 0 disables that behavior.^[2]

When force-loading works

The force-load mode decides whether your chunks stay loaded while you're offline. NEVER only allows force-loading if 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 permission ftbchunks.chunk_load_offline.^[2]

Protection rules

Claims protect blocks from other teams. The server has a switch to disable protection entirely, which is meant for private servers where everyone is trusted and claims are only used for force-loading. When it is on, the fire, fluid and piston protection settings are ignored.^[2]

There is also a no-wilderness option: if true, chunks must be claimed before anyone can build on them. A separate list lets you require claims only in certain dimensions, such as the Nether, and wildcards like a mod namespace followed by * are allowed. Claiming itself can be restricted with a dimension blacklist and a whitelist. If the whitelist is not empty, a dimension must be on it and must not be on the blacklist.^[2]

• Fire spread protection stops fire spreading between claims of different teams. The tooltip says it is false by default and warns it can cause server performance issues when many blocks are on fire.^[2]
• Flowing fluid protection stops fluids flowing horizontally across claims of different teams. It is also false by default per the tooltip, and the warning is that fluid flow ticks are checked very frequently.^[2]
• Piston protection stops pistons pushing or pulling blocks across claims of different teams, unless the block is entering or leaving a claim whose block edit mode is Public.^[2]
• Unknown explosions, such as those from Ghasts, can't be traced in code. If the protect-unknown-explosions setting is true, damage from them is prevented in protected chunks.^[2]
• PvP mode can be ALWAYS, NEVER or PER_TEAM. With PER_TEAM, each team decides through its own team property.^[2]

Allies and fake players

Ally mode decides who counts as an ally. DEFAULT checks FTB Teams ally status, FORCED_ALL treats everyone as allied, and FORCED_NONE treats nobody as allied.^[2]

Fake players, which automation often uses, have their own server mode. CHECK treats them like any real player, DENY never allows them, and ALLOW always allows them. The tooltip notes that logging of prevented fake player access is not fully implemented yet.^[2]

Team-level settings

Each team also has its own claim settings. You can choose whether explosions can damage blocks in claimed areas, and whether mobs can grief blocks. Right now the mob option only covers Endermen, and Creeper explosions fall under the explosions setting. Team PvP only works if the server PvP mode is set to per_team, and it isn't guaranteed to stop every indirect attack.^[2]

Map and visibility

If the server requires the ftbchunks_mapping game stage, players need it to open the map or see the minimap. This needs KubeJS and/or Gamestages. Teams also have a Location Visibility setting, but a server option can override it so everyone sees each other anywhere on the map.^[2]

The server can send long-range player tracking data at an interval measured in ticks. Lower values mean more updates but more server load and network traffic, and 0 disables long-range tracking.^[2]

On the client, map data is handled in 512x512 regions. A timeout releases regions that haven't been accessed recently, and another setting releases region data down to a set number when you close the large map. Smaller values use less memory but cause more disk access, and 0 disables releasing. You can also turn off the zoom-out limit, which is tied to explored regions and available memory, if it bothers you.^[2]

Unverified No FTB Chunks config files for this pack were available, so the actual values (claim limits, force-load mode, protection toggles and so on) are unconfirmed. The "by default" notes above come from the mod's tooltips and may not match what this pack sets.