FTB Chunks in All the Mods - Gravitas

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.

FTB Chunks is a claiming, force-loading and map mod. The sources I have for this pack only cover its settings tooltips. They don't show any crafting steps, so I can't give you a first-items list for it.^[2]

Unverified I couldn't confirm any in-pack recipes, quests or craftable items for FTB Chunks, so there is no 'first thing to craft' step here. I also couldn't confirm the pack's actual setting values, only what each option does.

What to know before you claim anything

• Claims protect an area. Block editing, block interaction (like opening a chest or flipping a lever), entity interaction and attacks on things like paintings and item frames each have their own team permission mode.^[2]
• Some servers use the no-wilderness option. If it's on, chunks must be claimed before anyone can build in them. Check this early, especially on a server.^[2]
• Claims can be released automatically. 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 after their own idle limit. Setting either limit to 0 turns that behavior off. I couldn't confirm the pack's values.^[2]
• Force-loading while you're offline depends on the force-load mode. NEVER requires an online team member, ALWAYS allows it regardless, and DEFAULT allows it if the team has a member with the right permission or the offline-forceloading option is on.^[2]

Teams and parties

If you play with friends, the party limit mode decides how claim and force-load limits are worked out. It can use the largest member's limits, the sum of all members, the owner's limits only, or the average. There is also a hard claim limit and a hard force-load limit for party teams, which apply whatever the member count or mode.^[2]

Explosions in claimed areas are controlled by a team setting. Some explosion sources, like Ghasts, can't be identified in code. A separate option prevents damage from those in protected chunks when it's enabled.^[2]

The map

The map and minimap can be gated behind the 'ftbchunks_mapping' game stage, but only if the require-game-stage option is on and KubeJS and/or Gamestages are present. If you can't open the map, that's one thing to check. I couldn't confirm whether this pack turns it on.^[2]

Team settings also control who can see your claims on the map and who can see your location beyond normal vanilla tracking range.^[2]

FTB Chunks is mostly a claiming, protection and map system rather than a machine mod, so there are no multiblocks, power or fluids to manage. The mechanics below all come from the mod's own option descriptions. This pack doesn't ship config files I can read, so I can't tell you which values the pack actually sets. Treat everything here as how each option behaves, not as the pack's settings.^[2]

Claims and protection

A claim protects the chunks you own. A few global options change how strict that protection is. With the no-wilderness option on, chunks must be claimed before anyone can build in them. The disable-protection option is meant for private servers where everyone is trusted and claims only exist for force-loading.^[2]

Explosions are handled in a couple of ways. Each team can choose whether explosions damage blocks in its claimed areas. On top of that, some explosion sources, such as Ghasts, can't be identified in code. If the protect-unknown-explosions option is true, damage from those explosions is prevented in protected chunks.^[2]

There is also a dimension blacklist where chunks can't be claimed. For example, you could add the End to it to disable claiming there.^[2]

Team permissions

Each team has its own permission modes, which decide who can do what inside its claims. The modes cover these actions:^[2]

• Block edit and interact mode: used when blocks are placed, broken or interacted with. Block edit mode covers only placing and breaking.^[2]
• Block interact mode: used when you right-click blocks, such as opening a chest or flipping a lever.^[2]
• Entity interact mode: used when you right-click entities.^[2]
• Non-living entity attack mode: used when you left-click non-living entities such as paintings and item frames.^[2]
• Claim visibility: controls who can see your claims on the map or minimap.^[2]
• Location mode: controls who can see you on the map or minimap outside the normal vanilla tracking range.^[2]

The ally mode setting decides who counts as an ally. DEFAULT checks FTB Teams ally status. FORCED_ALL treats every player as an ally. FORCED_NONE means nobody is ever an ally.^[2]

Fake players and automation

Fake players are what many automation blocks use to act in the world, so these settings matter if you automate inside claims. The server-wide fake players setting takes CHECK, DENY or ALLOW. CHECK treats a fake player like any real player. DENY never allows them. ALLOW always allows them.^[2]

Teams get finer control. An allow-all option treats every fake player as an ally of the team. Another option allows fake players that carry the ID of a real player, but only if that real player would be permitted as an ally or team member. A named list lets you treat specific fake players as allies, and its description says to leave it empty if you're unsure.^[2]

Force-loading

Force-loading keeps claimed chunks loaded. The Forceloading Mode setting controls whether that works when nobody is online:^[2]

• NEVER: force-loading only works while the owning team has at least one online player.^[2]
• ALWAYS: force-loading always works, even with no players online.^[2]
• DEFAULT: force-loading works if the team has at least one player with the chunk-load-offline FTB Ranks permission, or if Allow Forceloading for Offline Players is true.^[2]

The chunk-load-offline option is the fallback offline behaviour used when Forceloading Mode is set to default.^[2]

Party limits

Party teams get claim and force-load limits that depend on the party limit mode. LARGEST uses the limits of the member with the largest limits. SUM adds up all members' limits. OWNER uses only the party owner's limits. AVERAGE uses the average of all members' limits.^[2]

There are also hard claim and hard force-load limits for party teams. These apply regardless of member count or the limit calculation mode.^[2]

Inactive teams

Idle teams get cleaned up automatically. If no team member logs in for the configured number of days, the team's claims are released. A matching setting does the same for force-loading, so those chunks stop being force-loaded. Setting either to 0 disables it.^[2]

Map, minimap and performance

If the require-game-stage option is true, players need the ftbchunks_mapping game stage to open the map or see the minimap. That needs KubeJS and/or Gamestages. I can't confirm from the sources whether this pack turns it on.^[2]

Long-range player tracking sends updates to clients at an interval measured in ticks. Lower values mean more frequent updates but more server load and network traffic. Setting it to 0 disables long-range tracking. The death waypoint option works differently: if its value is above 0, your closest death point is removed automatically once you get closer to it than that distance.^[2]

The memory options trade RAM for disk access. Smaller values use less memory but reload released regions more often.^[2]

• Region release time: a timeout in seconds after which data for 512x512 regions that haven't been accessed recently is released. 0 disables releasing.^[2]
• Auto-release on map close: when you close the large map, region data is released down to the configured number. 0 disables releasing.^[2]
• Max zoom constraint: when true, the maximum zoom-out is limited by the number of explored regions and the available memory. Set it to false if that bothers you.^[2]

Unverified The pack's actual values for these options, including the claim and force-load limits, the Forceloading Mode and the fake player handling, couldn't be confirmed because the sources here include no config files for this mod.