1.1.1
Compatibility
Required content
Changes
Revamped the dependencies to now base on Architectuary. This should make releasing in neoforge / fabric easier from now on. Also added custom features in frozen biomes to assist with exploration. Also revamped a lot of backend stuff to be more stable and datapackable.
Revised the way enemy pokemon spawn in dungeons and the aggression mechanic to make them have more variation and easier to customize. This also removes the command blocks that sometimes remain in the dungeon. Fixed some small bugs with the explosion rules, wind charge related redstone works within dungeons now and explosion damage is no longer removed while explosions are turned off.
Optional dependencies
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:bNif2qBB:SUqRuihz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bNif2qBB:SUqRuihz"
}






