Tags
Creators
Details
4.1.0+mc1.21.11-forge
Compatibility
Required content
Changes
The copper settings work on Forge again.
Fixed
The two copper settings had no effect on the Forge file. Copper generated at vanilla density whatever they were set to. They work now: on the shipped defaults ordinary copper is thinned to 75 percent of vanilla and dripstone cave copper to 50 percent, which is what the other loaders have always done.
Dripstone caves get vanilla copper twice over, once from the ore that generates everywhere and once from a second set of larger veins that only they get, and our variants make that much more visible by matching the ore to the granite around it. Both dials are in the config if you would rather have vanilla numbers back: set either to 100.
Nothing else has changed. The same blocks, the same ids and the same generation as 4.0.1.
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:oWpIIBJu:sfP7gmOu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oWpIIBJu:sfP7gmOu"
}

