1.0.3
Compatibility
Changes
Guess who left a critical mistake in the core rendering the jump blocking functionallyti of all the effects useless? not me thats for sure. (also i think i should have changed the file names instead of just changing the version name this is going to be pretty confusing when someone sees this from the changelog tab)
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:TjdgIZsH:d1O3v7cg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TjdgIZsH:d1O3v7cg"
}

