Tags
Creators
Details
Licensed Apache-2.0
Published 8 months ago
Updated last week
All versions
1.4.1-neoforge
Release
Jump Delay Fix 1.4.1 for NeoForge2 weeks ago 47
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client-side
Changes
Jump Delay Fix v1.4.1
- Mod version: 1.4.1
- Minecraft version: 26.3
- Fabric versions: 26.3
- NeoForge versions: 26.3
Added
- In-game "Reset to Defaults" button in the settings screen for both Fabric and NeoForge, allowing quick restoration of default configuration.
- Enhanced player lifecycle validity checks (sleeping state, alive check, entity instance validation across respawns and dimension changes) to immediately reset transient jump delay tracking.
- Client connection and respawn event listeners on both loaders to cleanly reset transient jump states upon joining worlds or respawning.
- Localized reset button strings (
gui.jumpdelayfix.reset_defaults) across all 10 supported languages (en_us,pl_pl,de_de,es_es,fr_fr,it_it,ja_jp,pt_br,ru_ru,zh_cn). - Dedicated
docs/installation.mdanddocs/troubleshooting.mdguides along with updated documentation and wiki instructions. - Unified release script (
scripts/release.sh) with multi-branch awareness,--dry-runand--publishmodes, and verification gates.
Changed
- Strengthened concurrency thread safety in
JumpDelayFixby ensuring synchronized access across runtime state queries (isEnabled(),getProfile()). - Corrected Polish localization diacritics in
pl_pl.json. - Updated GitHub Actions CI and CodeQL workflows for broader support branch coverage and reliable build performance.
Compatibility
- Minecraft: 26.3
- Fabric: Loader 0.18.4+ / Fabric API 0.160.6+26.3
- NeoForge: 26.3.0.1-beta+
- Java: 25
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:7pVB28ir"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZaDE6u1D:7pVB28ir"
}

