Tags
Creators
Details
1.11.0.38
Compatibility
Changes
[752b4b4] fix AT for NeoForge to correctly transform constructor for LootContext (way2muchnoise)
[eb1f7ed] add AT for NeoForge (way2muchnoise)
[d7ef0ca] remove command for profiling from NeoForge (way2muchnoise)
[295b903] remove Forge from build scripts (way2muchnoise)
[4d79752] remove travis as we use GH actions now (way2muchnoise)
[919b36f] update deprecated setting for runDir in gradle (way2muchnoise)
[b7ff03f] cull profiling, moving profiling to out of scope for JER (way2muchnoise)
[db7a0fb] bump version as I will start to cull code (way2muchnoise)
[4d915e1] remove Forge as JEI has no forge version and I want to stop dragging old code (way2muchnoise)
[44a0f81] switch back to terraformersmc maven (way2muchnoise)
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:uEfK2CXF:DB3TsOrm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uEfK2CXF:DB3TsOrm"
}

