Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 3 days ago
All versions
1.1.17-26.1.2
Beta
Quick Link (Wireless Logistics) 1.1.17-26.1.23 days ago 7
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Fixed
- Plugs no longer go dead when their chunk unloads. A plug in an unloaded chunk was silently dropped from its network for good — nothing could ever bring it back, because the network only looks up positions it still knows about. This is what broke cross-dimension transfer with Compact Machines, where the room chunk is unloaded almost all the time and no chunkloader can reach it. Verified against compactmachines-neoforge 7.0.81.
- Plugs no longer lose their network on world reload. A reloaded plug re-registered under a fresh entry while its old one stayed behind, slowly filling the save with dead network members. Registrations now persist with the block.
Changed
- FTB Chunks: claim networks and team networks are now one network. Previously a plug inside a claim was always kept separate from a teammate's plug standing outside any claim, even for the same team. They now connect. Claiming still does what it is for: a plug inside a claim keeps serving the claim's team even after the player who placed it leaves that team, and a plug placed inside another team's claim joins that team's network. Only affects worlds running FTB Chunks — without it, every network key is unchanged. Old claim-only networks are cleaned up automatically on first load; re-check plugs sitting in claims after updating.
- Faster transfers on large networks. Each transfer attempt used to force-load one chunk per network member, across every dimension involved, before moving anything. Members are now resolved one at a time and the attempt stops at the first successful move.
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:WuedGJpw:CdsBxBRy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WuedGJpw:CdsBxBRy"
}

