FTB Chunks in FTB Skies 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 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]

FTB Chunks doesn't work like a machine mod. There are no multiblocks, power or fluid handling to wire up. As the mod's own in-game text currently describes it, its systems are chunk claiming, chunk force-loading, protection rules for claimed land, and the map. Here is how they work.^[3]

Claiming and force-loading

The mod's in-game reference currently says everything starts on the chunk claim screen, which you open with C from the large map. You paint claims with the mouse, much like a drawing tool.^[3]

• The claim reference currently lists: left button and drag to claim an area, right button and drag to unclaim an area.^[3]
• It currently lists Shift + left button and drag to force-load an area, and Shift + right button and drag to stop force-loading it.^[3]
• It currently lists rotating the mouse wheel over a force-loaded chunk to adjust its auto-expiry.^[3]
• It currently lists holding Tab to hide the chunk grid and holding Alt to show the absolute claim and force-load times.^[3]

Per the mod's current tooltips, force-loading is controlled by a server setting called force_load_mode. 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 permission ftbchunks.chunk_load_offline.^[3]

Limits and expiry

The default maximum number of claimed chunks can be overridden by the FTB Ranks permission ftbchunks.max_claimed. The same goes for force-loaded chunks and ftbchunks.max_force_loaded. The pack's actual limit values aren't in the sources I have, so check them in-game.^[3]

Party teams have their own rules. The mod's current tooltip says the party limit mode decides how a party's claim and force-load limits are worked out:^[3]

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

According to the mod's current tooltips, hard team limits for claims and for force-loading apply to party teams whatever the member count or mode. A value of 0 means no hard limit. Claims also expire. If no team member logs in for the configured number of idle days, the team's claims are released and its force-loaded chunks stop loading. Setting either idle value to 0 turns that auto-release off.^[3]

Where claiming is allowed

Servers can restrict claiming by dimension. A dimension blacklist stops claiming in the listed dimensions, for example minecraft:the_end, and wildcards like othermod:* are allowed. A whitelist works the other way: if it isn't empty, a dimension must be on it and not on the blacklist.^[3]

There is also a no_wilderness option. When it's true, chunks must be claimed before anyone can build on them. A separate list of dimensions can require claiming only in specific places, such as the Nether.^[3]

Protection rules

Claims protect blocks from other teams. As the mod's tooltips currently describe them, some of the extra protections are optional and cost performance, so they're off by default:^[3]

• Fire spread protection stops fire spreading across claims owned by different teams, unless the target claim has public edit block permissions. It is false by default and can cause server performance issues when many blocks are on fire.^[3]
• Flowing fluid protection stops fluids flowing horizontally across claims of different teams, with the same public-edit exception. It is false by default, and fluid flow checks happen very often, so large bodies of flowing fluid can cost performance.^[3]
• Piston protection currently stops pistons pushing or pulling blocks across claims of different teams, unless the block is entering or leaving a claim with block edit mode set to Public.^[3]
• The tooltips currently say fire, fluid and piston protection are all ignored if disable_protection is true. That option is meant for private servers where everyone is trusted and claims are only used for force-loading.^[3]

Explosions from sources the mod can't identify in code, such as Ghasts, are only blocked in protected chunks if protect_unknown_explosions is true. PvP is set server-wide to ALWAYS, NEVER or PER_TEAM. With PER_TEAM, each team decides through its own team property.^[3]

Each team also has its own settings for explosions and mob griefing. The mob griefing option currently covers Endermen only, and creeper explosions are handled by the explosions option instead. Team settings also cover how fake players (automation players from other mods) are treated. The server-wide fake player option can be CHECK, DENY or ALLOW. CHECK treats them like any real player. Be careful with the team options that trust fake players, because the mod warns that hostile players could get into your claims through them.^[3]

Allies are decided by the ally mode. DEFAULT checks FTB Teams ally status. FORCED_ALL always treats everyone as allied, and FORCED_NONE never does.^[3]

The map

The mod's in-game reference currently says that on the large map you drag with the left button to move the view, use the right button for a context menu, and scroll to zoom. Space centers the view on you, S opens settings, and F3+G toggles the chunk grid. Ctrl + S opens the server settings and T teleports to a point, and both need op.^[3]

The map keeps explored regions in memory. Region data is released after a timeout, and the large map can also release data when you close it. Smaller values use less memory but mean more disk access when regions reload. A value of 0 turns releasing off. By default, how far you can zoom out is limited by the number of explored regions and your available memory, and you can switch that off if it bothers you.^[3]

Servers can also require the ftbchunks_mapping game stage before a player can open the map or see the minimap. That needs KubeJS and/or Gamestages.^[3]

What the pack changes

The pack adds a list of entities to the ftbchunks:entity_mob_griefing_blacklist entity tag with a KubeJS script. The list is all the Enderman Overhaul enderman variants plus the primed tiny TNT from AE2.^[4]

Unverified The sources don't spell out exactly how FTB Chunks uses that tag, so check in-game how these entities behave next to claims.

There isn't a tier ladder or quest path to walk through for FTB Chunks in this pack, so this section stays short. The only pack-specific change to the mod that I can confirm is a script that edits one entity tag.^[4]

What the pack changes

The pack's server script adds a list of entities to the ftbchunks:entity_mob_griefing_blacklist entity tag. That list holds the Enderman Overhaul endermen named in the script, such as the badlands, cave, coral, end and swamp variants, plus the primed tiny TNT from Applied Energistics 2.^[4]

The tag name points at mob griefing, but the script doesn't spell out exactly how FTB Chunks uses the tag, so treat the precise behaviour as unconfirmed. If you want to know how it plays out, test it on your own claimed chunks.^[4]