Tags
Creators
Details
All versions
v1.2.0+1.21.11
Release
Soul Link Speedrun v1.2.0+1.21.119 months ago 646
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
New features
- Settings GUI - Added settings GUI for configuring difficulty, half-heart mode, shared jumping, and shared potions
- New modes - Implemented jump and potion effect synchronization among players
- Manual Reset Command – Added a /reset command, allowing players to instantly restart the active run without requiring Gamemaster permissions.
- Discord Integration – Added a "Report Bug" button in the settings GUI that provides a direct invite link to the Discord server for feedback.
- Difficulty Settings – World difficulty in the settings GUI now correctly reflects and updates the actual game difficulty.
Improvements
- Normalized Regeneration – Health regeneration from potion effects is now properly normalized to account for shared health pools, preventing unbalanced healing.
- Smoother Shared Jumping – Refined the Shared Jumping mechanic to process at the end of ticks, preventing race conditions and ensuring a consistent experience for all linked players.
- Welcome Message – Simplified the join message to be cleaner and added a helpful tip for accessing the settings menu.
- Spawn Finder - Improved spawn location detection algorithm in temporary worlds.
Bug Fixes
- Critical Damage Fix – Fixed a major issue where Iron Golems and explosions calculated damage incorrectly, often leading to unfair one-shots on linked players.
- Bossbar Cleanup – The Ender Dragon bossbar now correctly clears from the screen when a new run is started.
- Visual Rounding – Damage and health values in the UI now round to the nearest 0.5 hearts for a cleaner, more accurate display.
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:KZMNviZI:dbE32DNb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KZMNviZI:dbE32DNb"
}

