Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated last month
All versions
26.1.2-1.10.0
Release
LogisticsNetworks - 26.1.2-1.10.0last month 83
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Combined applicable updates from the 1.21.1 releases 1.10.0 through 1.14.2.
- Added multithreaded item transfer planning, with bounded queues, stale-plan checks, and synchronous fallback.
- Added configurable team, ally, or public access for nodes and networks.
- Added a "Scan attached storage" button to fill filters with items or fluids from the connected storage.
- Recolored filter UI icons for better visibility.
- Replaced hardcoded interaction controls with remappable keybinds.
- Improved Sophisticated Core compatibility, including bulk insertion, partial acceptance, and upgraded storage slots.
- Reduced repeated bulk insertion checks by caching rejected transfers.
- Fixed Round Robin distribution so items are shared between destinations instead of behaving like Priority mode.
- Fixed item transfers between nodes attached to the same storage, including opposite halves of a double chest.
- Made ordering consistent for nodes with equal priority.
- Improved filter processing by stopping match-all checks after a filter fails.
- Fixed tag-based filters ignoring NBT, durability, or enchantment constraints in some matching and amount checks.
- Fixed the raw NBT editor not accepting input or reliably saving changes when pressing Enter or clicking outside it.
- Fixed remapped interaction keys interrupting network name and color editing.
- Moved filter configuration and wrench state to data components, with migration for existing data.
- Removed hidden faces from computer and node models.
- Updated English guides and control hints for filters, scanning, access settings, distribution, mass placement, and
.lnetsave/load.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:yJwXUwvS:At9QW8Ke"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yJwXUwvS:At9QW8Ke"
}
