All versions
1.20.1-1.3.0
Release
ChainCraft 1.3.0 (Forge 1.20.1)4 days ago 17
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
1.3.0 (Forge 1.20.1)
- Chest contents view: a second tab on the right edge shows everything stored in chests within 10 blocks of the table, with total counts. Left-click takes a stack, shift-click takes all that fits. Hovering an item marks the chests holding it with particles.
- Quick deposit: the hopper button moves items from your main inventory (hotbar excluded) into nearby chests that already hold the same item.
- Favorites: right-click any item to pin it. Pinned items show a star, sort first, and get their own tab. Saved in
config/chaincraft-favorites.json. - Protected chests: a chest named with
!(in an anvil) or with a sign on top is ignored for crafting, pulling and depositing. Either half of a double chest protects both. - Particle trails: materials fly from chests to the table as enchantment glyphs; pulls and deposits show the same trail.
- Network protocol changed: server and all clients must run 1.3.0.
1.2.0 (Forge 1.20.1)
- Category tabs down the left edge, taken from the creative inventory tabs. Items from other mods appear under their own mod's tab automatically. "All items" first, "Other" last.
@modsearch: type@createin the search box to show only that mod's items. Tab and search combine.- Grid is now 6 rows of 9, sorted by item name. The selected tab and search text are remembered until the game closes.
1.1.0 (Forge 1.20.1)
- Chest support: crafting also uses materials from chests within 10 blocks of the table. Your own items are used first; results and leftovers always go to you.
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:ivc4nel3:IRaczgXD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ivc4nel3:IRaczgXD"
}

