FTB Chunks guide for FTB StoneBlock 4 1.1.1 to 1.8.1

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 4.14 guide

Good news: FTB Chunks doesn't make you craft anything to get going. Your first job is learning the map and the claim screen, so you can protect your base before you start building.^[2]

Unverified The sources I was given don't show any crafting recipes or quests for FTB Chunks in this pack. I can't confirm any starter item, so there are no recipe blocks in this section.

Your first steps

1. Open the large map. Click and drag with the left mouse button to move the view, and use the mouse wheel to zoom. Press Space to center the view back on yourself.^[2]
2. Press C on the large map to open the chunk claim screen.^[2]
3. Drag with the left mouse button to claim an area around your base. Drag with the right mouse button to unclaim an area.^[2]
4. Only if you want your farms and machines to keep running while you're away, hold Shift and drag with the left button to force-load chunks. Shift plus the right button unforceloads them.^[2]
5. Rotate the mouse wheel over a force-loaded chunk to adjust its auto-expiry.^[2]
6. Press S on the large map to open your settings screen.^[2]

Things to know early

Claims and force-loads can expire. If no team member logs in for the configured number of days, the team's claims are released. The same goes for force-loaded chunks, which stop being force-loaded. Setting either option to 0 disables that auto-release. The sources don't show this pack's actual day counts, so check your settings.^[2]

Force-loading while you're offline depends on the force-load mode. NEVER only allows it when the owning team has at least one player 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. Which mode this pack uses isn't confirmed in the sources.^[2]

Your claim limit can be overridden per player with the FTB Ranks 'ftbchunks.max_claimed' permission node. Likewise, 'ftbchunks.max_force_loaded' overrides the force-load limit. The sources don't give this pack's default limits, so the claim screen is the best place to check yours.^[2]

Same as in the All the Mods 10 4.14 guide

FTB Chunks has no machines, multiblocks, power or fluids. It works through claims: you mark chunks as yours, and the mod protects them, can keep them loaded, and shows them on a map. The sources I have are the mod's own tooltips and descriptions, so this section covers how those systems behave. It does not cover the pack's actual settings.^[2]

Claiming and force-loading

You do all the claiming from the chunk claim screen, which you open with C from the large map. The in-game reference lists the controls below.^[2]

• Left button, drag: claim an area.^[2]
• Right button, drag: unclaim an area.^[2]
• Shift + left button, drag: force-load an area.^[2]
• Shift + right button, 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 the absolute claim and force-load times.^[2]

Force-loading keeps a chunk active even when you are not standing near it. Which teams are allowed to do this while nobody is online depends on the force-load mode. NEVER only allows it when the owning team has at least one player online. ALWAYS allows it even with nobody online. DEFAULT allows it only if the team has a player with the FTB Ranks permission ftbchunks.chunk_load_offline.^[2]

Limits and expiry

The default limits for claimed and force-loaded chunks can be overridden per player with the FTB Ranks permission nodes ftbchunks.max_claimed and ftbchunks.max_force_loaded.^[2]

Party teams add a few more rules. The party limit calculation mode decides how a party's claim and force-load limits are worked out from its members. LARGEST uses the member with the biggest limits, SUM adds all members together, OWNER uses only the party owner, and AVERAGE uses the average. Separate hard limits for claims and for force-loading cap a party regardless of member count or calculation mode, and a value of 0 means no hard limit.^[2]

Claims also expire. If no team member logs in for the configured number of days, the team's claims are released. A separate idle timer does the same for force-loaded chunks, which just stop being force-loaded. Setting either timer to 0 turns that auto-release off.^[2]

Where you can claim

Dimensions can be controlled with a blacklist and a whitelist. The blacklist stops claiming in the listed dimensions; adding minecraft:the_end, for example, disables claiming in The End. If the whitelist is not empty, a dimension must be on it and not on the blacklist. Both lists accept wildcards, so othermod:* matches every dimension added by that mod.^[2]

There is also a no-wilderness option. When it is on, chunks must be claimed before anyone can build in them. A separate dimension list applies the same rule only to specific dimensions, such as minecraft:the_nether, and it supports wildcards too.^[2]

What a claim protects against

Each team has its own settings for who may edit blocks, interact with blocks, or interact with entities in its claims. Block edit mode covers placing and breaking. Block interact mode covers right-clicking, such as opening a chest or flipping a lever. A combined edit-and-interact mode and an entity interact mode also exist. Left-clicking non-living entities such as paintings and item frames has its own mode.^[2]

• Pistons: with piston protection on, pistons cannot push or pull blocks across claims owned by different teams. The exception is a block entering or leaving a claim whose block edit mode is Public. This is ignored if protection is disabled entirely.^[2]
• Explosions: each team can choose whether explosions may damage blocks in its claims. Some sources, such as Ghasts, cannot be identified in code, so a separate option can block their damage in protected chunks.^[2]
• Mob griefing: a team setting decides whether mobs can damage blocks in claims. Right now it applies to Endermen only, and Creeper explosions fall under the explosions setting instead.^[2]
• PvP: the server-wide mode can be ALWAYS, NEVER or PER_TEAM. Teams can only choose for themselves when the server mode is PER_TEAM. Protection is not guaranteed against every indirect attack, because damage has to be traceable to a player.^[2]
• Disabling protection: this is meant for private servers where everyone is trusted and claims are used only for force-loading.^[2]

Allies and fake players

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

Automation from other mods often acts through fake players. The server-wide fake player setting can be CHECK, which treats them like real players, DENY, which never allows them, or ALLOW, which always allows them. Teams can also let fake players that carry a real player's ID in, but only if that real player would be permitted. You can also name specific fake players to treat as allies. The sources warn that allowing all fake players, or adding named ones, could let hostile players into your claims, so leave those off if you are unsure. The mod also keeps logs of prevented fake player access, but the tooltip says that feature is not fully implemented yet.^[2]

Map, minimap and visibility

On the large map you drag with the left button to move, 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. Teleporting to a point with T needs op, and so does the server settings screen on Ctrl + S.^[2]

Teams control who can see their claims on the map and who can see their location. The location setting applies outside the normal vanilla tracking range. A server option can override this so all players see each other anywhere. Long-range player tracking is sent at a set interval in ticks. Lower values mean more updates but more server load and network traffic, and 0 disables it.^[2]

If the pack requires the ftbchunks_mapping game stage, you need it before you can open the map or see the minimap. This needs KubeJS and/or Gamestages.^[2]

Memory handling for the map

Map data is stored in 512x512 regions, and the mod releases regions that have not been accessed recently. Smaller timeouts use less memory but mean more disk access when regions reload. A separate option releases region data down to a set number when you close the large map. Setting either to 0 disables releasing. By default, how far you can zoom out is limited by how many regions you have explored and how much memory is available. You can turn that limit off if it bothers you.^[2]

Unverified The pack's actual values for claim limits, force-load mode, PvP mode, idle timers and the dimension lists could not be confirmed. No config files for this mod were available, so everything above describes how the options work, not what this pack sets them to.