Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 3 hours ago
All versions
1.1.16-1.21.1
Release
Quick Link (Wireless Logistics) 1.1.16-1.21.1last month 56
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
1.1.16
New: FTB Teams / FTB Chunks integration
- With FTB Teams installed, plug networks now require matching team membership in addition to matching color.
- With FTB Chunks also installed, blocks placed inside a claimed chunk join the network of the claim's owning team instead of the placer's own team, and claim-based networks are always kept separate from non-claim networks — even for the same team.
- Both are fully optional soft dependencies — the mod builds and runs identically with or without them installed.
- ⚠️ If you install FTB Chunks on an existing world that already used FTB Teams, some existing networks may split: blocks that end up inside a claim will separate from teammates' blocks standing outside any claim. This is expected — repaint/reassign sides as needed after installing FTB Chunks.
Fixed
- Energy Plug tooltip stats (Out/In FE) no longer stay stuck at 0 when energy is pushed into a Point side or pulled from a Plug side directly by a neighboring block (e.g. via a cable) instead of through the Plug's own active transfer tick.
- Energy transfer is now more robust with generators (e.g. Thermal Series dynamos) that don't correctly honor simulated energy extraction.
Performance
- FTB Teams membership lookups are now cached for a few seconds, cutting down repeated API calls during normal per-tick network scans.
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:3hlve1nD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WuedGJpw:3hlve1nD"
}

