FTB Chunks in Project Infinity 0.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.

Good news: the sources I have show no items to craft for FTB Chunks. Your first steps are all done on the map screen, so there's nothing to gather before you start.^[2]

Step by step

1. Open the large map. Left-click and drag to move the view, scroll the mouse wheel to zoom, and press Space to center the view back on yourself.^[2]
2. Press C on the large map to open the chunk claim screen. This is where you protect your base.^[2]
3. Hold the left mouse button and drag over the chunks you want to claim. Drag with the right button to unclaim chunks you no longer need.^[2]
4. If you want a claimed area to keep running while you're away, hold Shift and drag with the left button to forceload it. Shift plus right-drag unforceloads it.^[2]
5. Rotate the mouse wheel while pointing at a forceloaded chunk to adjust its auto-expiry.^[2]
6. Press S on the large map to open the settings screen and tune the minimap and map options to your taste.^[2]

Handy claim screen tricks

• Hold Tab to hide the chunk grid when you want a clear view of the terrain.^[2]
• Hold Alt to show the absolute times at which chunks were claimed or forceloaded.^[2]
• Press F3+G to toggle the chunk grid in the world.^[2]

Unverified The exact claim limits, force-load limits and idle-day values this pack uses are not confirmed by the sources, and neither is whether chunks must be claimed before building. Check the in-game settings screens for the real values. The sources also show no recipes or quests for this mod in the pack.

The material available for FTB Chunks describes no machines, multiblocks, power, fluids or item handling, so there is nothing of that kind to cover here. What the mod's own text does explain is how claiming, force-loading, protection and the map work, so that is what this section covers.^[2]

Claiming and force-loading

According to the mod's in-game claiming reference, you claim chunks on a map screen. Drag with the left mouse button to claim an area, and drag with the right button to unclaim one. Hold Shift while dragging to do the same for force-loading: Shift + left button force-loads an area and Shift + right button unforceloads it.^[2]

• The same reference says to rotate the mouse wheel over a force-loaded chunk to adjust its auto-expiry.^[2]
• It says to hold Tab to hide the chunk grid.^[2]
• It says to hold Alt to show the absolute claim and force-load times.^[2]
• The large map's key list says C opens the chunk claim screen and F3+G toggles the chunk grid.^[2]

The mod's tooltip for the force-load mode option describes three settings. 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'.^[2]

Limits and expiry

The default maximum number of claimed and force-loaded chunks can be overridden per player with the FTB Ranks permissions 'ftbchunks.max_claimed' and 'ftbchunks.max_force_loaded'.^[2]

The party limit mode tooltip explains how party teams combine their members' limits: LARGEST uses the member with the largest limits, SUM adds all members' limits, OWNER uses only the party owner's limits, and AVERAGE uses the average. The tooltips also describe hard claim and hard force-load limits for party teams that apply whatever the mode. A value of 0 means no hard limit.^[2]

The tooltips describe idle expiry too. If no team member logs in for the configured number of days, the team's claims are released, and a separate setting does the same for force-loaded chunks. Setting either to 0 disables it.^[2]

Protection rules

Claimed chunks are protected, and teams choose who may do what. Team settings cover block edit mode (placing or breaking), block interact mode (right-clicking things like chests or levers), a combined edit and interact mode, entity interaction (right-clicking entities), and attacking non-living entities such as paintings and item frames.^[2]

• Explosions and mob griefing: teams can choose whether explosions may damage blocks in their claims. Mob griefing currently covers Endermen only, while creeper explosions fall under the explosion setting. Some explosion sources, such as Ghasts, can't be identified in code, so a server setting decides whether their damage is prevented in protected chunks.^[2]
• Pistons: when piston protection is on, pistons can't push or pull blocks across claims owned by different teams, unless the block is entering or leaving a claim whose block edit mode is Public.^[2]
• PvP: the server mode tooltip lists ALWAYS, NEVER or PER_TEAM. Only PER_TEAM lets each team decide through its own PvP setting, and the team tooltip says that setting is not guaranteed to stop every indirect attack.^[2]
• Allies: the ally mode tooltip lists DEFAULT (FTB Teams ally status decides), FORCED_ALL or FORCED_NONE.^[2]
• Fake players: the server mode is CHECK (checked like any real player), DENY or ALLOW. Teams can also treat all fake players, or named ones, as allies, but the mod warns this could let hostile players in through them. Fake players carrying a real player's ID can be allowed if that real player would be permitted.^[2]

A few server options change how much protection applies. Disabling protection is meant for trusted private servers where claims are only used for force-loading, and it also makes piston protection ignored. The no-wilderness option requires chunks to be claimed before anyone can build on them, and a separate list sets which dimensions require it, for example the Nether. Claiming itself can be restricted with a dimension blacklist and whitelist, and both accept wildcards such as 'othermod:*'.^[2]

The map and minimap

The mod's large map reference says to drag with the left button to move the view, use the right button for the context menu, and scroll to zoom. Space centers the view on you, S opens settings, and Ctrl + S opens server settings (op required). T teleports to a point, which also needs op.^[2]

Team settings decide who can see your claims on the map and who can see your location outside normal vanilla tracking range. A server option can override the location settings so all players see each other anywhere. Long-range player tracking is sent at a set tick interval: lower values update more often but cost more server load and network traffic, and 0 disables it.^[2]

Map data is kept in memory in 512x512 regions. Regions that haven't been accessed recently are released after a timeout, and the large map also releases region data when it closes. Smaller values use less memory but cause more disk access when regions reload, and 0 disables releasing. The maximum zoom-out can be limited by the number of explored regions and the available memory, which you can turn off if it bothers you.^[2]

The server can also require the 'ftbchunks_mapping' game stage before a player can open the map or see the minimap. This needs KubeJS and/or Gamestages.^[2]

Unverified The values this pack actually uses for the limits, modes and timeouts above are set in the FTB Chunks configuration, and the sources here do not show them, so check the in-game settings before relying on any default.