Tags
Creators
Details
1.1.17-1.20.1
Compatibility
Changes
QuickLink 1.1.17 for 1.20.1 (Beta)
Beta release. The main fix here is hard to hit in short tests but easy to hit in a real world, so it needs testing on live setups before it goes stable. Please report anything odd.
Fixed: networks silently dying when the other end unloads
A block would drop out of its network the moment its chunk unloaded, and it never came back until a player physically walked up to it. The block looked fine, the colors looked fine, nothing moved.
This is why Compact Machines never worked: the room lives in its own dimension where a player is almost never standing, and you cannot put a chunkloader in there. Now blocks stay in the network across unloads, and transfer between the overworld and a Compact Machines room works without anyone being inside.
The same bug hit any remote base, mining outpost, or nether setup that was not force-loaded. If your networks only ever worked while you stood next to them, this was why.
Note that pulling into an unloaded room still needs that room to tick — that part depends on Compact Machines' own chunkloading settings, not on QuickLink.
Changed: FTB Chunks claimed and unclaimed blocks now share a network
This changes existing worlds. Read this if you use FTB Chunks.
Previously, blocks inside a claim were always kept in a separate network from blocks of the same team standing outside any claim, even with identical colors. That separation was never the point — it was a side effect — and it is what made overworld-to-Compact-Machines links impossible.
Now a claim and plain team membership produce the same network. What this means:
- Blocks of one team with one color now link up whether they sit inside your claims or outside them.
- Claiming still does what it is for: a block inside a claim belongs to the claim's team permanently. If the player who placed it leaves the team, it keeps working for the team, while their blocks outside any claim drop out. This is unchanged.
- A block placed inside another team's claim still joins that team's network, not its owner's.
- Installing FTB Chunks on an existing world no longer splits your networks.
If you were relying on "inside claim" and "outside claim" as two separate networks, they will merge on update. Use different colors to keep them apart.
Performance
Every transfer attempt used to load a chunk for each member of the network, in every dimension involved, even when the very first one it tried had the goods. It now checks members one at a time and stops as soon as something moves. Large or cross-dimensional networks should be noticeably lighter on the server.
Housekeeping
- Network registrations are now stored per block, so changing teams, claims, or installing/removing FTB Chunks no longer leaves dead entries piling up in the world's save data.
- Dead entries left by 1.1.16 are cleaned out automatically the first time the world loads.
Before you update
Back up your world — normal advice for a beta, and this version rewrites QuickLink's saved network data.
Downgrading back to 1.1.16 is safe; you will simply get the old behavior back, including the bug above.
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:aaWPO1EF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WuedGJpw:aaWPO1EF"
}

