1.7.7-forRelics-0.12.8-1.0
Compatibility
Required content
Changes
More Relics now officially supports Relics 0.12.8!
Attention: This is a special version for the Relics 0.12.8 beta. For modpack creators who use version 1.21.1 and Relics 0.10.7.8, I do not recommend updating because it could cause data corruption in already generated worlds. This applies to updating both More Relics and base Relics, it can cause tons of unintended issues so please at least warn your players. If you're starting a new world it should work fine.
This version will be locked at version 1.7.7 in terms of content and will only receive bug fixes. It will not include updates from future versions (1.7.8 and later). New builds with updated content will be released occasionally, but not for every release.
If you experience any bugs, please report them!
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:NmYBBHLU:vFU5WdGv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NmYBBHLU:vFU5WdGv"
}





