Links
Tags
Creators
Details
All versions
1.1.0-beta.6
Beta
1.1.0-beta.6 — MC 1.18-26.2, Spigot e Folialast month 33
Compatibility
Minecraft: Java Edition
26.2
26.1.2
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Widens support from a single version to Minecraft 1.18 → 26.2, and adds Spigot and Folia.
Fixed
- The periodic sweep no longer allocates. It used to build a full state snapshot just to hash it and discard it — 68
ItemStack.clone()calls per linked player per second, each deep copying item metadata. The hash now comes straight off the live inventory. - The Java skin was lost after relogging. It was applied once, at link time — and Geyser sets the Bedrock skin during login, so the first relog undid it. Now re-applied on every join, from a cached texture, with Mojang queried only in the background.
- Pets did not recognise the account in use. Three faults at once: the transfer gave up whenever the other linked account was also online, it only ran at join — before the player's chunks had loaded — and nothing ran afterwards. Ownership now follows the last active account and is refreshed on join, on chunk load, and on interaction.
Added
- Minecraft 1.18 → 26.2 in a single jar (Java 17 bytecode, compiled against the Spigot 1.18.2 API).
- Spigot support. Skin copying still requires Paper and says so.
- Folia support, verified on Folia 26.2 build 7.
sync.armorandsync.offhandindependent ofsync.inventory.- Config migration: new options are merged into an existing
config.ymlon startup, preserving your values and comments. /crosslink pets,claimpetsandretargetpets— see who owns the animals around a player and fix ownership. All three run from the console with a player name, because the account standing next to the animal is usually the Bedrock one, which normally is not op.- SkinsRestorer detection. CrossLink steps aside by default;
link.skin-provider: nativeoverrides.
Notes
Upgrading from 1.0.0 needs no migration.
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:pNoSYwnk:cLylUeJc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pNoSYwnk:cLylUeJc"
}

