Tags
Creators
Details
1.1.2
Compatibility
Required content
Changes
- Separate singleplayer teleport data per world while preserving legacy data.
- Add atomic saves, backups, and protection against overwriting unreadable data.
- Improve Elevator compatibility performance.
- Recheck permissions and dimensions before teleporting.
- Fix particle cleanup and clear runtime state on shutdown.
Legacy singleplayer data requires manual import into the correct world (NOT ON SERVERS):
Worlds no longer share teleport data. Before importing legacy singleplayer data, close the world and copy config/enderlink/teleports.json to saves/<correct-world>/enderlink/teleports.json.
Back up any existing destination file first; do not overwrite a world that already has its own pads.
The legacy file has no world identifier, so EnderLink never automatically assigns it to a world or deletes it. Keep the original until you have verified the imported pads.
Optional dependencies
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:1EdUpHRe:myRUXlw3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1EdUpHRe:myRUXlw3"
}

