Iskandert Library in FTB Evolution 2

Iskandert Library is a library mod, and this pack ships version 1.12.0.1.0 of it. The jar is iska_lib-1.12.0.1.0-neoforge-26.1.2.jar, and the mod's registry namespace is iska_lib.^[1]

It has been in the pack since version 1.0.2 or earlier, so it is not a recent addition.^[1]

The sources I have for this pack give nothing beyond that version and file information, so I am not going to guess at what the mod adds or where it sits in the quest book. If you spot it in a mod list, that is the whole picture the pack files give for now.^[1]

Iskandert Library is a library mod, so there is no starter item for you to craft here. In this pack, your first steps with it are about knowing which of its settings are active.^[2]

Unverified The sources here show no recipes that produce Iskandert Library items and no quests in this pack that involve the mod, so there is no crafting order to give you. Check the pack's quest book yourself if you want to be sure.

What the pack has set

Everything below lives in the mod's common config file, and these are the values this pack ships with.^[2]

• explosionGriefFtbClaims is false. That means the mod's progressive explosions do not break blocks in claimed FTB Chunks chunks, though entity damage still applies. Your base is safe from block damage, but not from hurting mobs or players.^[2]
• ftbTeamsSyncEnabled is true. With FTB Teams loaded, shop teams can sync with FTB team membership.^[2]
• stages.ultimine.enable_ultimine_stage_gate is false, so Ultimine is not locked behind a stage. If you turn it on, stages.ultimine.ultimine_required_stage names the stage you need. It is empty in this pack. stages.ultimine.ultimine_stage_scope is set to player, and the other options are world or team.^[2]
• bootstrap.datapack_paths lists the places the mod scans for data at startup: kubejs/data, datapacks, config/openloader/data, global_packs/required_data and global_packs/optional_data.^[2]

Checking for explosions

The mod has an explosion info command. It lists active progressive explosions, with their position, radii, progress and block counts. When nothing is running, it reports "No active progressive explosions." The sources here do not show the exact command syntax.^[3]

Iskandert Library is a support mod, and the sources for this pack show it through one common config file and a few command messages. They don't describe machines, multiblocks, power or item automation, so this section sticks to what is confirmed: progressive explosions, team syncing, an Ultimine stage gate and data loading.^[2][3]

Progressive explosions

The mod has progressive explosions, which are tracked while they are running. Its explosion info command lists every active one, and each entry shows where it is, its radii, its percentage, which wave it is on, how many sub-regions it has covered and how many blocks it has affected. If nothing is running, you get the message "No active progressive explosions."^[3]

This pack sets explosionGriefFtbClaims to false. That means these explosions do not break blocks in claimed FTB Chunks chunks, although entity damage still applies. If you turn it on, claimed chunks can be griefed. The option does nothing when FTB Chunks isn't loaded.^[2]

Team syncing

ftbTeamsSyncEnabled is true in this pack. When FTB Teams is loaded, shop teams can sync with FTB team membership.^[2]

Ultimine stage gate

The mod can lock Ultimine behind a stage. In this pack the gate is off: stages.ultimine.enable_ultimine_stage_gate is false, and stages.ultimine.ultimine_required_stage is empty, which means no stage is required.^[2]

If you enable the gate, Ultimine needs the configured stage before use. stages.ultimine.ultimine_stage_scope decides how the stage is checked and can be player, world or team. The pack uses player.^[2]

Data loading

At mod init, the mod scans the folders in bootstrap.datapack_paths. This pack lists kubejs/data, datapacks, config/openloader/data, global_packs/required_data and global_packs/optional_data. The config describes these as the KubeJS data root, Open Loader, Global Packs and instance datapacks.^[2]

A path counts as a pack root if it contains .zip or .jar children, or folders with pack.mcmeta. Otherwise it is treated as a data root.^[2]

These are the Iskandert Library options you are most likely to touch. They cover explosions in claimed chunks, team syncing, an optional Ultimine stage gate and the folders the library scans for data. All of them are in bootstrap.datapack_paths's file, config/iska_lib-common.toml. Here is how this pack sets each one.^[2]

Explosions and claimed chunks

explosionGriefFtbClaims is false in this pack. That means Library progressive explosions do not break blocks in FTB Chunks claimed chunks. Entity damage still applies, so players and mobs inside a claim can still get hurt. The config comment lists false as the default, so the pack leaves it as is. It has no effect if FTB Chunks is not loaded.^[2]

Teams

ftbTeamsSyncEnabled is true. When FTB Teams is loaded, that lets shop teams sync with FTB team membership.^[2]

Ultimine stage gate

The library can lock Ultimine behind a stage. In this pack that gate is switched off, so you do not need any stage to use Ultimine. These options control it:^[2]

• stages.ultimine.enable_ultimine_stage_gate is false. If it is set to true, Ultimine requires the configured stage before use.^[2]
• stages.ultimine.ultimine_required_stage is an empty string, which means no stage. It is the stage id that is required when the gate is enabled.^[2]
• stages.ultimine.ultimine_stage_scope is "player". It is the scope for the Ultimine stage check, and the other choices are world or team.^[2]

Data and datapack folders

bootstrap.datapack_paths tells the library where to scan for data when the mod starts. This pack lists these roots: kubejs/data, datapacks, config/openloader/data, global_packs/required_data and global_packs/optional_data. A path counts as a pack root if it contains .zip or .jar children, or folders with pack.mcmeta. Otherwise it is treated as a data root.^[2]