All versions
1.3.0
Release
Double Jump Enchant 1.3.02 weeks ago 42
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
1.3.0
Ports
- New: Fabric 1.19.2, 1.20.1, 1.21.11, 26.2, 26.3; Forge 1.21.1, 1.21.11; NeoForge 26.2, 26.3
- Removed: Minecraft 26.1 and 26.1.1 (Fabric and NeoForge) — use 26.1.2 instead
Fixes
- Creative / spectator mid-air while wearing Double Jump boots no longer removes that mode’s flight
- NeoForge 1.21.11: jar loads (1.1.0 / 1.2.0 were rejected as invalid mod files)
- Fabric: missing keys in
config/doublejumpenchant-server.jsonkeep defaults (no longer treated as off / 0); if you upgraded from 1.0.0, check treasure-book keys already written back - Fabric: trailing comma in
levelBoostsno longer crashes on startup - Non-finite
levelBoosts/treasureBookChancevalues no longer break jumping or treasure books (ignored / sane fallbacks) - Fabric 1.21.1 declares Fabric API (required for treasure books)
- NeoForge 1.21.1 requires NeoForge 21.1.186+
- Each jar targets exactly its Minecraft version (no wider version ranges)
- Forge 1.21.1 / 1.21.11: no Experimental Settings warning for this mod’s enchantment alone (datapack worlds still warn as usual)
Anvil
- Combining no longer raises Double Jump above the configured max level (default 3); already-higher levels keep working and jump like the max configured level
allowBookUpgradesstill only controls the mod’s fixed-price book upgrade
Dependencies
- Fabric: Fabric API + Architectury API (Architectury new)
- NeoForge: Architectury API (new)
- Forge: Forge only
- Fabric 26.1.2: Fabric Loader 0.19.5+
Unchanged
- Jump feel, treasure books, anvil book upgrade (aside from the level cap), config keys, and translations
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:Ktu67fXz:5Ln8f8Cv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ktu67fXz:5Ln8f8Cv"
}

