Included content
| Name | |
|---|---|
![]() | MidnightLib |
edible_item and modify_enchantment_level from Apugli have made it into the base mod itself, so for these, we have a special case where the content will be aliased to their Apoli counterparts.
Consider this a backwards compatible solution, not a permanent feature, you're best to swap to Apoli's implementations as they'll continue to be supported.
All code for these two power types have been removed from Apugli.
apugli:edible_item to apoli:edible_item.apugli:modify_enchantment_level to apoli:modify_enchantment_level.| Name | |
|---|---|
![]() | MidnightLib |
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.
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:1qeWG44Y:9rWe5cZ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1qeWG44Y:9rWe5cZ4"
}