Tags
Creators
Details
Licensed Apache-2.0
Published 8 months ago
Updated last week
All versions
1.1.1-neoforge
Release
Jump Delay Fix 1.1.1 for NeoForge2 weeks ago 10
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.9โ1.21.11
Platform
NeoForge
Supported environments
Client-side
Changes
Jump Delay Fix v1.1.1
- Mod version: 1.1.1
- Minecraft version: 1.21.11
- Fabric versions: 1.21.11
- NeoForge versions: 1.21.9,1.21.10,1.21.11
Added
- In-game "Reset to Defaults" option in the settings GUI for quickly restoring baseline configuration.
- Diagnostic inspection queries on
JumpDelayFixfor active server, confirmed jumps, and rejected jumps. - Comprehensive installation and troubleshooting guides with multiplayer anti-cheat notices.
Fixed
- Fixed thread-safety synchronization on
JumpDelayFix.getProfile()to align getter and setter concurrency. - Added player state validation (
isAlive(),!isSleeping(), entity ID transition check) to prevent unwanted jump attempts during respawn, death, and bed usage. - Corrected Polish localization diacritics in
pl_pl.json.
Technical
- Upgraded NeoForge toolchain to
21.11.48baseline with cross-version compatibility (KeyMapping.Category.MISC,FMLEnvironment.getDist()) tested across NeoForge21.9.16-beta(1.21.9),21.10.64(1.21.10), and21.11.48(1.21.11). - Updated GitHub Actions CI/CD workflows to include
support/**branch coverage and disable build cache in CodeQL analysis. - Cleaned and extended unit and integration test coverage.
Compatibility
- Minecraft: Fabric: 1.21.11; NeoForge: 1.21.9, 1.21.10, 1.21.11
- Fabric: Loader 0.18.4+ / Fabric API 0.141.6+1.21.11
- NeoForge: 21.9.16+ (loader range
[21.9,), game version range[1.21, 1.22)) - Java: 21
Optional dependencies
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:w0L1R4ib"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZaDE6u1D:w0L1R4ib"
}

