Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 17 hours ago
All versions
1.1
Release
Chapters 1.16 months ago 692
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Chapters 1.1 — FTB Library / FTB Teams / FTB Quests integration
What's new
- Chapters now plugs into FTB Library as the active stage provider when ftblibrary is installed. FTB Quests built-in Stage Reward, Stage Task, and "Stage Required" field all work with chapter ids out of the box, no extra setup needed.
- When FTBTeams is also installed, chapter unlocks become team-scoped through FTB Teams TEAM_STAGES. Every party member instantly shares unlocks, the inventory auditor and JEI hide/reveal run for all online members, and /chapters add/remove, KubeJS PlayerStages.of(player), and FTB Quests Stage Reward all converge on the same team-wide store.
- One-time migration on first login: pre-existing per-player unlocks on a player's personal team are copied into TEAM_STAGES. Party teams are skipped to avoid leaking personal unlocks.
- New example KubeJS script (examples/kubejs/server_scripts/ftbquests_chapter_reward.js) showing the FTB Quests Custom Reward path for conditional chapter grants
Bug fixes
- Fixed JEI not hiding staged-out items, fluids, and Mekanism chemicals on dedicated servers. The four stage indices are now synced to the client through a single payload, so JEI can hide locked content correctly in multiplayer.
- Worked around an upstream FTB Teams aliasing bug in TEAM_STAGES that caused stage writes on one team to leak into every other team's first read. Chapters now keeps each team's stage set fully isolated.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:kBw6VkrT:jm7ojo3K"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kBw6VkrT:jm7ojo3K"
}

