Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 3 weeks ago
All versions
0.4.0+mc26.1-snapshot-6.fabric
Beta
Logistics v0.4.0 for fabric 26.1-snapshot-65 months ago 83
Compatibility
Minecraft: Java Edition
26.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
0.4.0 (2026-03-27)
Features
- add logistics network with provider, supplier, requester, and sink modules; supports multiple supply modes (BULK50, BULK100, INFINITE, FULL), concurrent crafting orders, supply reconciliation, and in-transit item tracking (#161, #165, #174, #175, #178, #183, #184, #185, #186, #188, #228, 3281871)
- add chassis pipes with modular, swappable module slots (MkIāMkV) (#194, #195, #203)
- add crafting pipe with autocrafter integration, tiered ingredient buffers, capacity limits, and recipe import (#189, #193, #200, #204, 381c99d)
- add processing, satellite, and mod sink pipe modules with GUIs (#206, #207)
- add beta build workflow for release branches and register kiln recipe type and serializer (#154, #155)
Bug Fixes
- fix asset and presentation issues: missing particle textures, item tag names, and pipe loot tables (#167, #169, #181)
- fix kiln screen issues: empty recipe display and missing menu registration (#168, #219)
- fix logistics network bugs: crafting order logic, dispatch edge cases, craftable item display, requester search sorting, provider screen GUI, extractor filter, and memory leak (#173, #176, #179, #180, #192, #198, #201, #205, #208, 2f51bc8, 3281871)
- fix build and configuration issues: schemaVersion placement and beta workflow branch naming (#157, #166)
- fix crash caused by jar remapping collision in IPipeAccess (#222)
- resolve quarry test failures by improving terrain handling (#227)
Performance
- throttle provider pipe extraction to 8 items per cycle at 6-tick intervals (3281871)
Refactorings
- redesign network architecture: replace request system with standing-order dispatch controller, restructure network package, and introduce dispatch planning with partial supply and explicit commands (#177, #182, #187, #190, 381c99d)
- reorganize pipe module interfaces, sink management, filter slots, and components into core library; clarify supplier mode names and remove unnecessary buffer handling (#199, #202, #213, #214, #215, #216, #218, 3281871)
- clean up imports, NBT abbreviations, and packet organization (#209, #210, #211, #212)
Testing
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:NEVM5MLs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cyW2SS1x:NEVM5MLs"
}

