Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 3 weeks ago
All versions
0.6.0+mc26.1.fabric
Release
Logistics v0.6.0 for fabric 26.13 months ago 20
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
0.6.0 (2026-05-31)
Features
- Added NeoForge support, including platform services, capabilities, networking/lifecycle hooks, client rendering, and storage adapters. #378, #379, #380, #381, cdeb6a7
- Added power cables. f2cc460
Bug Fixes
- Improved logistics network reliability and safety by handling failed deliveries, validating/sanitizing config fields, and clamping energy values and transfer amounts to non-negative values. #397, #398, #399
- Fixed NeoForge and multi-loader content issues, including JEI Macerator recipe visibility, marking fluid recipe separation, and missing
META-INFservice files. #382, #390, affc30f - Fixed power cable compilation errors for Minecraft 26.1. #357
- Preserved item components in filter pipe slots across save/reload. #386
Refactorings
- Reworked the project for multi-loader support, including NeoForge groundwork, loader-agnostic bootstrap flow, service-based platform access, cleaner module boundaries, and build configuration updates. #306, #318, #320, #341, #342, #343, #344, #347, #348, #360, #361
- Introduced loader-agnostic storage, energy, fluid, fuel, item matching, and client model abstractions. #340, #349, #351, #356, #364, #389, #400
- Cleaned up common code organization and removed remaining Fabric-specific dependencies/imports from shared sources. #345, #350, #352, #355
Testing
Optional dependencies
Any compatible version
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:cyW2SS1x:rwUTorFn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cyW2SS1x:rwUTorFn"
}

