FTB Chunks guide for All the Mods 11 0.1.0 to 0.9.0-beta

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 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 claiming land, keeping chunks loaded and showing you a map. The material I have for this pack covers those systems through the mod's tooltips and descriptions, so this section sticks to them. Most of what follows is a setting you can tune, and I can't confirm what value the pack uses for any of them.^[2]

Unverified The sources do not cover machines, multiblocks, power, fluids or item automation for FTB Chunks. The pack's actual values for the options below are also unconfirmed, because no config files for this mod were available.

Claiming chunks

The mod's in-game claiming reference lists the controls on the claim screen. Dragging with the left button claims an area, and dragging with the right button unclaims one. Holding Tab hides the chunk grid, and holding Alt shows the absolute chunk claim and force-load times.^[2]

The admin mode description says that when it is enabled you can modify chunks regardless of ownership.^[2]

Force-loading

According to the same reference, Shift plus left button dragging force-loads an area, and Shift plus right button dragging unloads it. Rotating the mouse wheel over a force-loaded chunk adjusts its auto-expiry.^[2]

The server's force-load mode setting is described like this: NEVER only allows force-loading if the owning team has at least one online player. ALWAYS allows it even if no players are online. DEFAULT allows it if the team has at least one player with the FTB Ranks permission ftbchunks.chunk_load_offline.^[2]

Limits and expiry

The tooltips say the default maximum number of claimed chunks and force-loaded chunks can be overridden with the FTB Ranks permission nodes ftbchunks.max_claimed and ftbchunks.max_force_loaded.^[2]

For party teams, the party limit mode setting is described as the method for calculating claim and force-load limits. LARGEST uses the limits of the member with the largest limits, SUM adds up all the members' limits, OWNER uses the party owner's limits only, and AVERAGE uses the average. The tooltips also describe a hard claim limit and a hard force-load limit for party teams, regardless of member count or mode, where a default of 0 means no hard limit.^[2]

Claims can also expire. Per the tooltips, 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-day setting. Setting either value to 0 disables that behavior.^[2]

Server owners can restrict where claiming works. The dimension blacklist is described as listing dimensions where chunks may not be claimed, such as minecraft:the_end. The whitelist, if non-empty, means a dimension must be on it and not on the blacklist. Both accept wildcards, so othermod:* matches every dimension added by that mod.^[2]

What claims protect against

The disable protection option is described as useful for private servers where everyone is trusted and claims are only used for force-loading. Otherwise, the tooltips describe several separate protections that can be toggled:^[2]

• Fire spread protection: if true, fire is prevented from spreading across claims owned by different teams, unless the target claim has public edit-block permissions defined.^[2]
• Flowing fluid protection: if true, fluids are prevented from flowing horizontally across claims owned by different teams, with the same public edit-block exception.^[2]
• Piston protection: if true, pistons may not push or pull blocks across claims owned by different teams, unless the block is entering or leaving a claim with block edit mode set to Public.^[2]
• Unknown explosion protection: some explosion sources, such as Ghasts, can't be determined in code. If this setting is true, damage from them is prevented in protected chunks.^[2]
• PvP mode can be ALWAYS, NEVER, or PER_TEAM, where teams decide through a team property.^[2]
• The no-wilderness option, if true, requires chunks to be claimed before they can be built on. A separate dimension list does the same for chosen dimensions, for example minecraft:the_nether.^[2]

Teams, allies and fake players

The ally mode setting decides who counts as allied in claims. In DEFAULT, FTB Teams ally status is checked. FORCED_ALL means all players are always considered allied, and FORCED_NONE means none ever are.^[2]

Fake players, such as those used by automation blocks from other mods, are handled by a server setting: CHECK checks them like real players, DENY never allows them, and ALLOW always allows them. Teams also have their own options. They can allow explosions, allow mob griefing (currently Endermen only, since creeper explosions fall under the explosions option), and allow PvP. They can also treat all fake players, or named ones, as allies.^[2]

The map and minimap

The large map help screen lists the controls. Click and drag with the left button to move the view, use the right button for a context menu, and rotate the wheel to zoom. Space centers the view on the player, C opens the chunk claim screen, S opens the settings screen, and F3+G toggles the chunk grid. T teleports to a point and Ctrl+S opens the server settings screen, and both require op.^[2]

The require game stage option, if true, means players must have the ftbchunks_mapping game stage (KubeJS and/or Gamestages required) to open the map or see the minimap. Team location visibility settings are ignored when the location mode override is true, so all players can see each other anywhere on the map.^[2]

The long-range tracker interval is the number of ticks between updates of long-range player tracking data sent to clients. The tooltip says lower values mean more frequent updates but more server load and network traffic, and that setting it to 0 disables long-range tracking.^[2]

Map memory use

A few client settings control memory use for the map. One is a timeout in seconds to release data for 512x512 regions that haven't been accessed recently. Another auto-releases region data down to a set number when the large map is closed. Smaller values use less memory but cause more disk access when released regions reload, and 0 disables releasing.^[2]

When the max zoom constraint is true, the max map zoom-out is limited by the number of explored regions and the amount of available memory. If this is bothersome, the tooltip says to set it to false.^[2]

Other client options include the minimap blur mode, where Auto blurs only when fully zoomed out. When the proportional option is true, the minimap size is proportional to 10% of the screen width, modified by the Scale setting, and when false it is a fixed size. Visibility runs from 255 (fully opaque) to 0 (fully transparent).^[2]