Tags
Creators
Details
2.0
Compatibility
Changes
Completely overhauled the JSON spawning config method. As the old method is extremely outdated, previous configs will need to be removed and the 1.0 files will be archived to prevent future use. 2.0+ is much more stable and expected to be the method used from here on out.
Corvicraft will now generate a folder for each applicable mod (corvicraftspawns handles Vanilla entries). In this folder is a subfolder named spawn_sets, within which a series of json pools are defined. Each file must have a unique name. These sets can then be paired with a list of biomes in the spawns.json file within the main mod folder. Separating the files like this makes them a little more resilient in regards to errors, as unless spawns.json itself is broken, only the invalid spawn pool file will fail to load.
Several additional ways to customize modded spawns have been added internally, although they do not impact vanilla entries.
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:BmoMEHBA:aP2XR0MB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BmoMEHBA:aP2XR0MB"
}

