Tags
Creators
Details
Licensed Apache-2.0
Published 8 months ago
Updated last month
All versions
1.1.0-fabric
Release
Jump Delay Fix 1.1.0 for Fabric2 months ago 352
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.9–1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Jump Delay Fix v1.1.0
- Mod version: 1.1.0
- Minecraft version: 1.21.11
- Fabric versions: 1.21.11
- NeoForge versions: 1.21.9,1.21.10,1.21.11
Added
- Smart Auto-Profile switching: The mod now dynamically adapts to server latency and rollback rates, choosing the best jump profile automatically.
- Server tracking: The optimal profile for each server is now remembered and automatically applied upon joining.
Changed
- Improved Competitive Profile to more strictly enforce latency checks.
- Unified Fabric and NeoForge client integration code for a cleaner architecture.
- Streamlined configuration storage and serialization for faster loading and saving.
Removed
- Removed unused block and item registry abstractions to drastically reduce code bloat.
Technical
- Flattened the package structure to eliminate unnecessary deep nesting (e.g.,
com.kizio.jumpdelayfix.common->com.kizio.jumpdelayfix). - Renamed internal state and management classes to more accurately reflect their runtime responsibilities.
- Optimized event handling by consolidating the listener structure into unified entry points for Fabric and NeoForge.
Compatibility
- Minecraft: 1.21.1
- Fabric: Loader 0.18.4+
- NeoForge: 21.1.174+
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:ZaDE6u1D:RvoP4Nhv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZaDE6u1D:RvoP4Nhv"
}

